hi folks
bit of a saga here, but please bear with me. I'm stuck fixing too many problems, and being new to Linux isn't helping me!
1. I'm trying to get my system to multi-boot:
toshiba A70 laptop
40 GB internal HD (WinXP)
usb2.0 external HD (Suse9.3, hopefully FC3 or FC4 soon too.)
2. I installed Suse on the ext HD without too many problems except for network card issue. It turns out I can't modprobe or insmod because those commands look for "/lib/modules/<uname -r>/...". The out put of 'uname -r' is 2.6.11.4-20a-default, but there is no directory "/lib/modules/2.6.11.4-20a-default". My conclusion is that I should be booting the kernel 2.6.11.4-20a-smp which
does have a folder in /lib/modules/.
3. next problem: I enter YaST and select "peropose new boot configuration" in the grub config window. It goes ahead and finds my 2.6.11.4-20a-smp kernel and a bunch of others which is good so I click "next".
the progress gets stuck at 50%, and In KSysGuard I can see a process ag_bootloader taking about 95-100% of the cpu power. It hangs up like this until I kill it, no new boot config

.
Wait, before anyone says "stick in the Suse CD and do "system repair". I did that too and I can write a new boot config without crashing anything. However if I select "propose new config", it won't find anything but the "default" and failsafe modes, not the 2.6.11.4-20a-smp which to my knowledge is the only one where my network card works ........
Sorry for the long post, but if anybody can make sense of this, I'd be really happy for a clue on where to go from here. I've read through the suse documentation, and I think the next step will be manually changing grub. That's pretty delicate stuff, and shouldn't be required afaik.
cheers
Will