On Monday 17 October 2005 05:25 am, Greg Wallace wrote:
I once had a device problem where I had a kernel module being loaded that shouldn't have been. The solution was to do a modprobe -r so that the kernel wouldn't load that module. I'm wondering if you might have just the opposite problem; I, e, a kernel module that should be getting loaded but isn't. I'm way out of my league here, but since you've pretty much given up on this, I thought I'd throw this out as a WAG. I may be completely off in left field here (wouldn't be the first time) but maybe someone with better kernel knowledge could step in and say it this is a possibility.
I was going to suggest this same thing based on the following: When the kernel moved from 2.6.11.xx to 2.6.12+ something changed drastically in the way it loaded and booted because I found that if I didn't add modules that covered the NICs and USB modules, these devices wouldn't show up when the system was booted. Once added to /etc/sysconfig/kernel list for initrd modules, then things worked fine. If you compare the initrd module lists between 9.3 and 10.0 I think you'll find a lot more things getting loaded. And it's possible that SuSE has a bug in the way they make up that list... Simple as that.