Hi, On Tue, Jun 01, Andrew Tuson wrote: [...]
The problem was caused by a serial port conflict, caused by SuSE 6.1 loading its own serial driver as well as the one I compiled into the kernel. The clue was my boot sequence which contained:
This is a problem of kernel 2.2.x: It allows you to load some driver as module even when it's already contained in the kernel. In the case of sd_mod this can have much worse effects than with the serial driver ;) We have a quick hack for the serial driver, but are working on a more general solution to the problem (registering drivers or capabilities). For the moment we should maybe add the some hints to the documentation: If you want to recompile your kernel, do a "rpm -e kernmod" before, so there are only the modules around you really need. [...]
Andrew Tuson -o) Hubert Mantel Goodbye, dots... /\\ _\_v
-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>