>Again, randomly copying .config files and not checking what might >have changed is asking for trouble. What made you expect that >the .config for a particular kernel would work on another kernel?
That it had always worked for me in the past, for quite a few minor version increments in the 2.4.x series? >Y'mean like this?? > - Do a "make config" to configure the basic kernel. "make config" needs That's basically what I've always done. After copying my old .config, I'd run "make menuconfig" or "make xconfig", browse the menus and then save the new config file before doing the actual build. It just seems that when upgrading from 2.4.18 to 2.4.19, this specific procedure no longer avoids generating inconsistent or illegal combinations of configuration parameters that aren't apparent until run time, after the new kernel has been booted and all the modules had apparently loaded successfully. So I manually configured 2.4.19 from scratch, and all is well again. Thanks for the tip. My intent was simply to reduce the chances of error by starting with a closer set of configuration defaults than those provided in a "virgin" distribution. For example, I use ext3fs but it's configured off by default. Forgetting to turn it back on could result in my system becoming unbootable. Oh, with regard to the correct list for reporting bugs, it was not clear which of the two USB mailing lists given in the MAINTAINERS file should be used. Thanks, Phil ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
