Guest darteaga Posted October 1, 2004 Report Share Posted October 1, 2004 Hi all, I have a P4 with a single Serial ATA 160 GB HD. Until now I was using Mandrake 10 with kernel 2.6.3 without any problem. Recently I decided to update to Mdk 10.1 Community through urpmi. When updating the kernel to 2.6.8.1 and rebooting I get: "error 6 mounting ext3" and "kernel panic: no init found". I would say that lilo is correctly configured and initrd images are correct. Comparing startup messages, one sees that kernel 2.6.3 recognized appropiately all devices: dvd/dvd+rw in hda/hdb (ide0) and hard disk in hde (ide2). In contrast, the hard disk is not recognized with the new kernel. I presume that this is the reason why I get the kernel panic. Has anybody found the same problem? Any idea? Many thanks in advance, Dani Arteaga Quote Link to comment Share on other sites More sharing options...
arctic Posted October 1, 2004 Report Share Posted October 1, 2004 welcome aboard darteaga :) i do think that the problem is your lilo.conf. i do not use 10.1 yet but i do know (from experience with other distros) that sometimes the lilo.conf does not get updated properly. so check it, if the vmlinuz-file, the initrd and the kernel-file in lilo match the names given to them in /boot . maybe they have a kernelsuffix now. (e.g. "vmlinuz-2.6.8.1-mdk" vs. "vmlinuz") Quote Link to comment Share on other sites More sharing options...
pmpatrick Posted October 1, 2004 Report Share Posted October 1, 2004 The old kernel, 2.6.3 designated the first sata as /dev/hde; the new kernel designates the first sata as /dev/sda, i.e. it treats sata drives as scsi drives. This is probably the crux of your problem. Post your lilo.conf. and fstab. You can probably fix it by adding "root=/dev/sdax" to your append line for the 2.6.8 kernel entry in lilo, where 'x' corresponds to your root partition on the sata drive. Quote Link to comment Share on other sites More sharing options...
Steve Scrimpshire Posted October 2, 2004 Report Share Posted October 2, 2004 Right. I'm sure that is ging to be the problem as well. I have an Asus A7V600 with a Maxtor SATA drive. Here is my /etc/fstab and /etc/lil.conf for comparison: fstab: /dev/sda1 / ext3 defaults 1 2 /dev/sda5 swap swap defaults 0 0 /dev/sda6 /home ext3 defaults 1 2 /dev/sda7 /files ext3 defaults 1 2 none /dev/pts devpts mode=0620 0 0 /dev/hdc /mnt/cdrom auto umask=0,user,iocharset=iso8859-1,codepage=850,noauto,ro,exec 0 0 /dev/hdd /mnt/cdrom2 auto umask=0,user,iocharset=iso8859-1,codepage=850,noauto,ro,exec 0 0 none /proc proc defaults 0 0 lilo.conf: default="263i686up4G-7" boot=/dev/sda map=/boot/map keytable=/boot/us.klt prompt nowarn timeout=100 message=/boot/message menu-scheme=wb:bw:wb:bw disk=/dev/sda bios=0x80 image=/boot/vmlinuz label="linux" root=/dev/sda1 initrd=/boot/initrd.img append="devfs=mount resume=/dev/sda5 splash=silent" vga=788 read-only image=/boot/vmlinuz label="linux-nonfb" root=/dev/hda1 initrd=/boot/initrd.img append="devfs=mount resume=/dev/hda5" read-only image=/boot/vmlinuz-2.6 label="263-4" root=/dev/hda1 initrd=/boot/initrd-2.6.img append="devfs=mount resume=/dev/hda5 splash=silent" read-only image=/boot/vmlinuz label="failsafe" root=/dev/hda1 initrd=/boot/initrd.img append="failsafe acpi=ht resume=/dev/hda5 devfs=nomount" read-only image=/boot/vmlinuz-2.6.7-0.rc2.1mdk label="267-0rc21" root=/dev/hda1 initrd=/boot/initrd-2.6.7-0.rc2.1mdk.img append="devfs=mount resume=/dev/hda5 splash=silent" vga=788 read-only optional image=/boot/vmlinuz-2.6.3-7mdk-i686-up-4GB label="263i686up4G-7" root=/dev/sda1 initrd=/boot/initrd-2.6.3-7mdk-i686-up-4GB.img append="devfs=mount resume=/dev/sda5 splash=silent" vga=788 read-only optional image=/boot/vmlinuz-2.6.7-2mdk-i686-up-4GB label="267i686up4G-2" root=/dev/hda1 initrd=/boot/initrd-2.6.7-2mdk-i686-up-4GB.img append="devfs=mount resume=/dev/hda5 splash=silent" vga=788 read-only image=/boot/vmlinuz-i586-up-1GB label="linux-i586-up-1GB" root=/dev/sda1 initrd=/boot/initrd-i586-up-1GB.img append="devfs=mount resume=/dev/sda5 splash=silent" vga=788 read-only image=/boot/vmlinuz-2.6.8.1-10mdk-i586-up-1GB label="2681i586up1GB-10" root=/dev/sda1 initrd=/boot/initrd-2.6.8.1-10mdk-i586-up-1GB.img append="devfs=mount resume=/dev/sda5 splash=silent" vga=788 read-only image=/boot/vmlinuz-2.6.7-2mdk-i686-up-4GB label="alt_267i686up4G-2" root=/dev/sda1 initrd=/boot/initrd-2.6.7-2mdk-i686-up-4GB.img append="devfs=mount resume=/dev/sda5 splash=silent" vga=788 read-only optional image=/boot/vmlinuz-2.6.8.1-10mdk label="2681-10" root=/dev/sda1 initrd=/boot/initrd-2.6.8.1-10mdk.img append="devfs=mount resume=/dev/sda5 splash=silent" vga=788 read-only Quote Link to comment Share on other sites More sharing options...
Guest darteaga Posted October 5, 2004 Report Share Posted October 5, 2004 Thank all of you very much for your help, and sorry for not having anwered before. I'll try out your suggestions, and post the result this evening. In case of problems I'll post as well my lilo.conf and fstab. Quote Link to comment Share on other sites More sharing options...
Guest darteaga Posted October 6, 2004 Report Share Posted October 6, 2004 Finally I succeeded in booting with the new kernel. As you suggested, the SATA hard drive is now recognized as sda instead of hde, so I had to replace hde by sda in lilo.conf and fstab. However this was not enough: I also had to load some sata kernel modules into the initrd image, creating a new image via mkinitrd. I just loaded the same modules that were loaded with the old kernel (just looking at the bootup information). I had never had to do this; I don't know why this time it has been necessary. In any case, many thanks for your help. By the way, this is not the only problem I have with mkd 10.1 ce. I have other problems as well: slow bootup, sometimes the keyboard stops responding, desktop slightly taller than the screen size, problems with accented characters, misconfiguration of gnome and kde... I hope to be able to solve these, but anyway... I presume that many problems come from having updated through urpmi and not updating the normal way via cds, next time I'll burn the cds and I'll forget experiments. Quote Link to comment Share on other sites More sharing options...
ianalis Posted February 9, 2005 Report Share Posted February 9, 2005 (edited) How did you run mkinitrd? I tried running it with mkinitrd preload sd_mod preload scsi_mod with=ata_piix /boot/initrd-2.6.8.1-12mdksmp-sata.img 2.6.8.1-12mdksmp but it says it cannot open initial console after detecting the sata drive. EDIT: I've solved it! I'm actually moving my / to a new sata drive. Apparently, cp -ax / /newroot will not copy the contents of /dev. What I did was to cp -a /dev/* /newroot/dev after that. It works fine now except the bootsplash is not displayed. Probably, bootsplash needs to be added to the initrd. I'll stfw first Edited February 11, 2005 by ianalis Quote Link to comment Share on other sites More sharing options...
Kjel Oslund Posted February 9, 2005 Report Share Posted February 9, 2005 [quote name='darteaga' date='Oct 6 2004, 03:52 AM']By the way, this is not the only problem I have with mkd 10.1 ce. I have other problems as well: slow bootup, sometimes the keyboard stops responding, ... [right][post="148523"]<{POST_SNAPBACK}>[/post][/right][/quote] RE the slow startup and keykboard not responding. You might want to check your /var/log/messages for possible CUPS printer initialization problem in 10.1. I have an HP printer connected on a parallel port using an office jet driver (ptal-mlcd/ptal-printd). There is a nasty loop in the udev/hotplug/cups/printer-config init scripts that causes the printer to be repeatedly re-initialized with the parport module being repeatedly loaded and unloaded. It seems to eventually settle down (never did figure out how) but untill it does the whole system is sluggish, especially keyboard response. If you see this, the fix is to comment out the printer line (lp) in /etc/dev.d/default/dynamic.dev This may not be your problem, but it looks familiar. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.