Re: Kernel k_deflt-2.4.21-144.i586.rpm initrd-Problem...
Ok, I downdated the system to the original Kernel to be found on cd. Then I tried to install the kernel downloaded at ftp://ftp.gwdg.de/pub/suse/i386/update/9.0/rpm/i586/k_deflt-2.4.21-192.i586.rpm But I still have the same problem. When I do mybox:~ # rpm -Uhv k_deflt-2.4.21-192.i586.rpm Preparing... ########################################### [100%] 1:k_deflt ########################################### [100%] Changing symlink /boot/vmlinuz from vmlinuz-2.4.21-99-default to vmlinuz-2.4.21-192-default Changing symlink /boot/initrd from initrd-2.4.21-99-default to initrd-2.4.21-192-default Root device: /dev/hda6 (mounted on / as ext2) No initrd required Using grub, re-install of bootloader not required. And no initrd is there in /boot. And another mkinitrd outputs Root device: /dev/hda6 (mounted on / as ext2) No initrd required I don't have another box which would need the default kernel so I can't figure out wether it's the default kernel package or my box. Does anybody have the the same problem? Could someone please help me? Thanx. Kind regards Marius Heidenstecker
Marius, you have no module entries in the file /etc/sysconfig/kernel for the variable INITRD_MODULES (most likely there is only INITRD_MODULES = "" in the file). Gernerally, this is no prblem. It simply means that for your computer no additional drivers are required. The script mk_initrd detects this and gives the message that no initrd is required. Unfortunately there is still the entry in grub's config file /boot/grub/menu.lst So grub expects to find an initrd which is not present. To fix this, simply comment out the line(s) starting with 'initrd' in the menu.lst file (put a '#' at the beginning of the line(s)). Hth, Jürgen On Sunday 29 February 2004 18:21, Security wrote:
Ok, I downdated the system to the original Kernel to be found on cd. Then I tried to install the kernel downloaded at
ftp://ftp.gwdg.de/pub/suse/i386/update/9.0/rpm/i586/k_deflt-2.4.21-19 2.i586.rpm
But I still have the same problem. When I do
mybox:~ # rpm -Uhv k_deflt-2.4.21-192.i586.rpm Preparing... ########################################### [100%] 1:k_deflt ########################################### [100%] Changing symlink /boot/vmlinuz from vmlinuz-2.4.21-99-default to vmlinuz-2.4.21-192-default Changing symlink /boot/initrd from initrd-2.4.21-99-default to initrd-2.4.21-192-default Root device: /dev/hda6 (mounted on / as ext2) No initrd required Using grub, re-install of bootloader not required.
And no initrd is there in /boot. And another mkinitrd outputs
Root device: /dev/hda6 (mounted on / as ext2) No initrd required
I don't have another box which would need the default kernel so I can't figure out wether it's the default kernel package or my box. Does anybody have the the same problem? Could someone please help me?
Thanx.
Kind regards Marius Heidenstecker
Am Sonntag, 29. Februar 2004 20:11 schrieb Jürgen Mell:
Marius,
you have no module entries in the file /etc/sysconfig/kernel for the variable INITRD_MODULES (most likely there is only INITRD_MODULES = "" in the file). Gernerally, this is no prblem. It simply means that for your computer no additional drivers are required. The script mk_initrd detects this and gives the message that no initrd is required.
Ok, then it had nothing to do with the athlon-kernel. I was wondering why the initrd existed on the other boxes with athlon-kernels. In these two machines we are using hardware-raid-controller which are - as I understood it correctly - loaded into the ramdisk, right?
Unfortunately there is still the entry in grub's config file /boot/grub/menu.lst So grub expects to find an initrd which is not present. To fix this, simply comment out the line(s) starting with 'initrd' in the menu.lst file (put a '#' at the beginning of the line(s)).
I did it with YaST and deleted the initrd-sections. Now it works fine. Thank you for your help. I didn't know that initrd is not needed on that box. Thanks. Regards Marius Heidenstecker
On Sunday 29 February 2004 18:21, Security wrote:
Ok, I downdated the system to the original Kernel to be found on cd. Then I tried to install the kernel downloaded at
ftp://ftp.gwdg.de/pub/suse/i386/update/9.0/rpm/i586/k_deflt-2.4.21-19 2.i586.rpm
But I still have the same problem. When I do
mybox:~ # rpm -Uhv k_deflt-2.4.21-192.i586.rpm Preparing... ########################################### [100%] 1:k_deflt ########################################### [100%] Changing symlink /boot/vmlinuz from vmlinuz-2.4.21-99-default to vmlinuz-2.4.21-192-default Changing symlink /boot/initrd from initrd-2.4.21-99-default to initrd-2.4.21-192-default Root device: /dev/hda6 (mounted on / as ext2) No initrd required Using grub, re-install of bootloader not required.
And no initrd is there in /boot. And another mkinitrd outputs
Root device: /dev/hda6 (mounted on / as ext2) No initrd required
I don't have another box which would need the default kernel so I can't figure out wether it's the default kernel package or my box. Does anybody have the the same problem? Could someone please help me?
Thanx.
Kind regards Marius Heidenstecker
On Sunday 29 February 2004 13:36, Security wrote:
Ok, then it had nothing to do with the athlon-kernel. I was wondering why the initrd existed on the other boxes with athlon-kernels. In these two machines we are using hardware-raid-controller which are - as I understood it correctly - loaded into the ramdisk, right?
Depends on the hardware raid. Some work completely in their onboard bios and the raid is invisable to the os, it appears as one drive. (This is the way all hardware raid should be IMHO, but unfortunatly some - expecially scsi) require drivers in the initrd. Apparently yours is not one of them. -- _____________________________________ John Andersen
participants (3)
-
John Andersen -
Juergen.Mell＠t-online.de -
Security