On Fri, Oct 23, 2009 at 11:04 AM, Florian Gleixner
in the "good old times" this was possible with Suse and other Linux distros. They included a "monster initrd" that probed all hardware and you could swap harware like mad. One thing windows never was able to handle. Yesterday i found out how to build this monster initrd (mkinitrd -A) and all Hardware runs now. But the next kernel patch will build a new initrd and if i don't take care, i have to rebuild the monster initrd in a rescue system again.
I run into something similar because I build madwifi from source since the ath5k driver in 2.6.25 isn't reliable. Keep in mind that there are a lot of things that are actually in the kernel as well, because you can go from an intel to an amd usually and it will still at least boot.
So my proposals: - Add a grub entry with a monster initrd - Add a Yast module or something else to put the loaded and in use modules to your configuration (initrd, modprobe.conf, ....)
This could make Linux as flexible as it was in the "good old times". Or am i missing something?
Having that monster initrd could make booting slower. I dunno. I still get errors for AMD Powernow on Intel chips. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org