RE: kernel 2.4.7 doesn't work
I have been trying to get a 2.4 kernel working in different forms for some time now. The problems that have been posted with the results of: VFS: Cannot open root device 302 or 03:02 Please append a correct root= boot option Kernel panic: VFS: Unable to mount rootfs on 03:02 or similar are typical for those that have downloaded a 2.4.x kernel image through dselect (or equiv) and have tried to get it to work. The solution has been to make sure that your /etc/lilo.conf includes the line: initrd=/boot/initrd-2.4.7-686 for the 2.4.7 kernel for a 686 or greater. This will get the kernel to boot and start working for my desktop machine. The suggested solutions about making sure ext2 has been compiled in don't apply here since it is a pre-built kernel image. Although this will finally work on my desktop, it still won't work on my laptop. I can't get my pcmcia network card to come up. Since the 2.2.18 kernel, that works, I havn't found out what is different in the modules used or how to get the right ones loaded. I've found that just downloading the source and building my own kernel can eliminate the initrd issues that have caused a lot of the posted problems, I still haven't been able to get pcmcia services to bring up my network card either! I'd prefer to use my own built kernel as my final solution as I dislike the pre-built kernels initrd solution. I could really use some help here. Anyone know how to make it all happen? -Craig -Original Message- From: John Griffiths [mailto:[EMAIL PROTECTED] Sent: Saturday, July 28, 2001 11:05 PM To: [EMAIL PROTECTED] Cc: debian-user@lists.debian.org Subject: Re: kernel 2.4.7 doesn't work have you got the line initrd=/boot/initrd-2.4.7-686 after the vmlinuz stanza in lilo.conf? that fixed my trouble with that one add the run lilo and boot At 12:36 PM 7/29/01 +0800, Tao Liu wrote: I upgraded my potato to sid today, and I installed the packageKernel-image-2.4.7-686 When I reboot, my computer shows: ... Linux IP multicast router 0.06 plus PIM-SM request_module[block-major-3]: Root fs not mounted VFS: Cannot open root device 302 or 03:02 Please append a correct root= boot option Kernel panic: VFS: Unable to mount rootfs on 03:02 I can still use kernel 2.2.19pre17 now, and it works very good my /etc/fstab shows: # /etc/fstab: static file system information. # # file systemmount point type options dump pass /dev/hda2 / ext2defaults,errors=remount-ro 0 1 /dev/hda1 noneswapsw 0 0 proc /proc procdefaults0 0 /dev/fd0 /floppy autodefaults,user,noauto0 0 /dev/cdrom /cdrom iso9660 defaults,ro,user,noauto 0 0 /dev/hda3 /boot ext2 rw0 2 /dev/hda5 /usr ext2 rw 0 2 /dev/hda6 /var ext2 rw 0 2 /dev/hda7 /home ext2 rw0 2 /dev/hda8 /base ext2 rw0 2 Now, what shall I do to use kernel 2.4.x? -- Regards, Tao Liu _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel 2.4.7 doesn't work
Am 29. Jul, 2001 schwäzte Tao Liu so: Yes! The problem is resolved! I am using 2.4.7 now. Thank you! But what does initrd mean? Is it new for 2.4? The initial-ramdisk ( initrd ) is a way for Linux to cheat. It needs to because x86 architecture sucks :). There's a very small amount of adressable memory for the kernel to load from. If the kernel is too big, you can't load all of it. The initrd is a way of pulling a secondary chunk of kernel off disk after the main chunk of kernel has been loaded. I don't know the particulars of how it it works. On Sunday 29 July 2001 22:50, you wrote: have you got the line initrd=/boot/initrd-2.4.7-686 Instead of this, put initrd=/boot/initrd and if linux.OLD uses and initrd, then put initrd=/boot/initrd.old in the stanza for it. In /boot soft link from the initrd-version to initrd for the kernel you're trying to use and from initrd-version to initrd.old for the old kernel. This is better than specifying initrd-version in lilo.conf because the upgrade tools seem to recognize the soft links and update them you you install new kernel-image packages. In other words, when you install kernel-image-newversion everything will automagically point at the right thing and continue working. It seems that starting with 2.4.x the kernel image packages are depending on initrds. I've had to fix the soft links and lilo.conf on every box I've updated to 2.4.x via packages, though. Don't know why that's borken and haven't researched it enough to file a bug report. Maybe I should anyway as it keeps coming up on this list... ciao, der.hans -- # [EMAIL PROTECTED] home.pages.de/~lufthans/ www.DevelopOnline.com # ... the social skills of a cow on acid. - der.hans
Re: kernel 2.4.7 doesn't work
Thank you (-: I think I can upgrade the kernel without initrd trouble in the futer. And I am trying to compile a kernel without initrd. On Wednesday 01 August 2001 03:33, der.hans wrote: Am 29. Jul, 2001 schwäzte Tao Liu so: Yes! The problem is resolved! I am using 2.4.7 now. Thank you! But what does initrd mean? Is it new for 2.4? The initial-ramdisk ( initrd ) is a way for Linux to cheat. It needs to because x86 architecture sucks :). There's a very small amount of adressable memory for the kernel to load from. If the kernel is too big, you can't load all of it. The initrd is a way of pulling a secondary chunk of kernel off disk after the main chunk of kernel has been loaded. I don't know the particulars of how it it works. On Sunday 29 July 2001 22:50, you wrote: have you got the line initrd=/boot/initrd-2.4.7-686 Instead of this, put initrd=/boot/initrd and if linux.OLD uses and initrd, then put initrd=/boot/initrd.old in the stanza for it. In /boot soft link from the initrd-version to initrd for the kernel you're trying to use and from initrd-version to initrd.old for the old kernel. This is better than specifying initrd-version in lilo.conf because the upgrade tools seem to recognize the soft links and update them you you install new kernel-image packages. In other words, when you install kernel-image-newversion everything will automagically point at the right thing and continue working. It seems that starting with 2.4.x the kernel image packages are depending on initrds. I've had to fix the soft links and lilo.conf on every box I've updated to 2.4.x via packages, though. Don't know why that's borken and haven't researched it enough to file a bug report. Maybe I should anyway as it keeps coming up on this list... ciao, der.hans _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
Re: kernel 2.4.7 doesn't work
have you got the line initrd=/boot/initrd-2.4.7-686 after the vmlinuz stanza in lilo.conf? that fixed my trouble with that one add the run lilo and boot At 12:36 PM 7/29/01 +0800, Tao Liu wrote: I upgraded my potato to sid today, and I installed the packageKernel-image-2.4.7-686 When I reboot, my computer shows: ... Linux IP multicast router 0.06 plus PIM-SM request_module[block-major-3]: Root fs not mounted VFS: Cannot open root device 302 or 03:02 Please append a correct root= boot option Kernel panic: VFS: Unable to mount rootfs on 03:02 I can still use kernel 2.2.19pre17 now, and it works very good my /etc/fstab shows: # /etc/fstab: static file system information. # # file systemmount point type options dump pass /dev/hda2 / ext2defaults,errors=remount-ro 0 1 /dev/hda1 noneswapsw 0 0 proc /proc procdefaults0 0 /dev/fd0 /floppy autodefaults,user,noauto0 0 /dev/cdrom /cdrom iso9660 defaults,ro,user,noauto 0 0 /dev/hda3 /boot ext2 rw0 2 /dev/hda5 /usr ext2 rw 0 2 /dev/hda6 /var ext2 rw 0 2 /dev/hda7 /home ext2 rw0 2 /dev/hda8 /base ext2 rw0 2 Now, what shall I do to use kernel 2.4.x? -- Regards, Tao Liu _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel 2.4.7 doesn't work
Hi, Do you use lilo? If so could you please post that file? And also the output of ls -l /boot/vm* Thanks, Jimmy Richards On Sun, Jul 29, 2001 at 12:36:03PM +0800, Tao Liu wrote: I upgraded my potato to sid today, and I installed the packageKernel-image-2.4.7-686 When I reboot, my computer shows: ... Linux IP multicast router 0.06 plus PIM-SM request_module[block-major-3]: Root fs not mounted VFS: Cannot open root device 302 or 03:02 Please append a correct root= boot option Kernel panic: VFS: Unable to mount rootfs on 03:02 I can still use kernel 2.2.19pre17 now, and it works very good (snipped fstab file) Now, what shall I do to use kernel 2.4.x? -- Regards, Tao Liu _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: kernel 2.4.7 doesn't work
Yes! The problem is resolved! I am using 2.4.7 now. Thank you! But what does initrd mean? Is it new for 2.4? On Sunday 29 July 2001 22:50, you wrote: have you got the line initrd=/boot/initrd-2.4.7-686 after the vmlinuz stanza in lilo.conf? that fixed my trouble with that one add the run lilo and boot -- Regards, Tao Liu _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
Re: kernel 2.4.7 doesn't work
Bigger brains than mine will have to answer that I experienced this trauma myself ast week and someone suggested it and it works. shame the kernel packagers haven't automated that one. At 01:13 PM 7/29/01 +0800, Tao Liu wrote: Yes! The problem is resolved! I am using 2.4.7 now. Thank you! But what does initrd mean? Is it new for 2.4? On Sunday 29 July 2001 22:50, you wrote: have you got the line initrd=/boot/initrd-2.4.7-686 after the vmlinuz stanza in lilo.conf? that fixed my trouble with that one add the run lilo and boot -- Regards, Tao Liu _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
Re: kernel 2.4.7 doesn't work
On Sunday 29 July 2001 06:13, Tao Liu wrote: Yes! The problem is resolved! I am using 2.4.7 now. Thank you! But what does initrd mean? Is it new for 2.4? Initial Ram Disk. It's been there for sometime as I needed it to get ide-scsi emulation going for my cdburner back on Mandrake 6.0 (2.0.36 or early 2.2). I *think* it's the equivalent of the debian root disk you use on a floppy install after the rescue disk - but I could be way out on this one ;-) It didn't seem to be required in later versions, and I don't currently need one for 2.4.4-ac6 (I recompile for hardware support so I don't use stock debian kernels). Regards, Martin -- [EMAIL PROTECTED] / [EMAIL PROTECTED] http://www.dbg400.net DBG/400 - DataBase Generation utilities Open Source test environment tools for the AS/400 / iSeries and miscellaneous database spooled file management commands.
