[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Modprobe errors after second kernel compile.

I upgraded to kernel 2.4.19 to allow me to add the i810 framebuffer patch.
everything went fine except I had missed the generic-scsi support
and so my cdrw didn't work. I turned this option on and recompiled. This
time when I went to install the resulting .deb I received a warning
about installing the same revision of kernel (I did change the -rev on the
kpkg command) and modules.dep could be wrong but this would be sorted on a
However now when I boot up I get a handful of modprobe errors for things
that are working just fine (sound, usb mass storage and the like). The
system is 
working fine but I hate these errors. What did I do wrong, and how can I
resolve it?

I'm using Woody with 2.4.19 kernel

PS. Sorry for the disclaimer. This is added by our mail server. I am looking
to change my subscription to use my home email.

This message including any associated files is intended only
for the use of the individual or entity to which it is addressed 
and may contain information that is privileged, confidential, 
copyrighted or constitutes a trade secret. If you are not the 
intended recipient you are hereby notified that any dissemination, 
disclosure, reproduction or distribution of this message or 
files associated with this message is strictly prohibited. 
If you have received this message in error, please permanently 
delete the message and any attached files, then contact us so 
we may investigate the delivery error. 
Whilst we have taken every effort to ensure that all attachments 
are virus free, use is at the recipients own risk 
and in no event will either Scotcomms Technology Group 
or any of its subsidiaries be liable for any form of damage or 
loss, be it material or financial, incurred by their use. 

_________________ANTI_VIRUS PROTECTION___________________ 

This message has been checked for all known viruses by Norman Anti-Virus. 
For further information visit http://www.norman.com 

Reply to: