On Mon, May 05, 2008 at 02:12:20PM +0200, NN_il_Confusionario wrote: ...
> and what about > > find /lib/modules/ -iname \*berry\* > > and then > > insmod $THE_COMPLETE_PATH_FOUND_AS_ABOVE > > (if there is a module in /lib/modules/`uname -r`/ which probably is not > true given the depmod -a result above) /home/carlf# find /lib/modules/ -iname \*berry\* /lib/modules/2.6.22-2-k7/kernel/drivers/usb/misc/berry_charge.ko /lib/modules/2.6.22-3-k7/kernel/drivers/usb/misc/berry_charge.ko /home/carlf# modprobe /lib/modules/2.6.22-3-k7/kernel/drivers/usb/misc/berry_charge.ko FATAL: Module /lib/modules/2.6.22_3_k7/kernel/drivers/usb/misc/berry_charge.ko not found. So, is refusing to admit that a file which is clearly present in fact exists a bug in the kernel worth reporting? I may just go ahead and compile a custom kernl with berry_charge integral. -- Carl Fink [EMAIL PROTECTED] Read my blog at blog.nitpicking.com. Reviews! Observations! Stupid mistakes you can correct! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
