On Tuesday 30 September 2003 11:50 am, eja@urbakken.dk wrote:
I'm just guessing but i assume you updated your kernel, with a SuSE or mantel version.
I'm not sure if it has, but there's some complaining around the Athlon kernel module, that cannot be found, I can see in the logfiles.
You could try to reinstall k_athlon from the cds as a last resort. What is the error? What kernel do you have installed? check with yast or kpackage or synaptic. Did you compile a kernel? or just upgrade with apt?
Have you run mk_initrd? SuSEconfig?ldconfig?
The first one cannot be executed, and the last 2 runs fine.
As root you did # mk_initrd and nothing happened? No messages? Here's the output of mine ... VMXLinux:/home/framau # mk_initrd using "/dev/hda8" as root device (mounted on "/" as "ext3") creating initrd "/boot/initrd" for kernel "/boot/vmlinuz" (version 2.4.20-4GB-athlon) - insmod aic7xxx (kernel/drivers/scsi/aic7xxx/aic7xxx.o) - insmod jbd (kernel/fs/jbd/jbd.o) - insmod ext3 (kernel/fs/ext3/ext3.o) - splash picture (1024x768) creating initrd "/boot/initrd.shipped" for kernel "/boot/vmlinuz.shipped" (version 2.4.20-4GB-athlon) - insmod aic7xxx (kernel/drivers/scsi/aic7xxx/aic7xxx.o) - insmod jbd (kernel/fs/jbd/jbd.o) - insmod ext3 (kernel/fs/ext3/ext3.o) - splash picture (1024x768) You could try mkinitrd, one is a link to the other. I forget which is the real command.
Maybe have yast rewrite your bootloader.
Maybe, and how to be aware of that ?.
Yast2 > system >bootloader config > root password > there is an option for rereading configuration > then finish/ ok. But I doubt that is the problem most likely it has to do with the kernel. Unless you are using Lilo than it may be the problem. But most likely you are using grub. -- Franklin Maurer Using SuSE 8.2 Pro