Scott Kirkpatrick wrote: > It's a 2.6 kernel. That's my next step in debugging it. I couldn't > find anything in the archives and didn't know if this was a known issue. Could it be possibly this one? http://www.busybox.net/lists/busybox/2004-October/012936.html It only affects modprobe, but not insmod, though. egor