Re: 2.4.18 doesn't find my root device.
On Thu, 12 Sep 2002 08:17:19 -0400 Jim Lynch <[EMAIL PROTECTED]> wrote: > Well it seems that supporting IDE devices isn't the default at 2.4.18. > I had to turn them on, as Jerome suggested. Strange system. scsi > emulation still doesn't work. It can't find the cdrom driver. Of > course it can't you fool. I compiled it into the kernel. What a piece > of trash. If you use the kernel-image-2.4.18 as intended (with an initrd image), it does work. It does support IDE by default and various SCSI controllers. I've used several variations of the kernel-image-2.4.18 package to include: -586tsc -686-smp -686 -k6 -k7 All with no problem. -- Jamin W. Collins -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 2.4.18 doesn't find my root device.
Well it seems that supporting IDE devices isn't the default at 2.4.18. I had to turn them on, as Jerome suggested. Strange system. scsi emulation still doesn't work. It can't find the cdrom driver. Of course it can't you fool. I compiled it into the kernel. What a piece of trash. Thanks, Jim. Jerome Acks Jr wrote: > > On Wed, Sep 11, 2002 at 02:30:06PM -0400, Jim Lynch wrote: > > Simple description: 2.4.18 kernel panics and says it can't find the root > > device on 03:06. 2.2.19 finds it fine. I had a root=/dev/hda6 on the > > loadlin line, and it failed, so I took it off. Rdev of the kernel also > > says root > > on /dev/hda6. > > > > Background: > > I upgraded to woody and found that my cdrom no longer worked. I figured > > something had broken the modules but recompiling and depmod and modprobe > > didn't seem to fix the problem. lsmod showed everything OK, but it > > still didn't work. I'm running a ide-scsi setup since this is a > > writer. > > So I decided to upgrade the kernel to 2.4.18. I got the > > kernel-source-2.4.18 via apt-get. Unbziped it. Copied my .config from > > 2.2.19 to 2.4.18 and did a make oldconfig. I pretty much answered all > > I don't think copying your .config from your 2.2.19 is a good way to > start. There have been a lot of changes. The config file for a 2.4.18 > is about three times the size of a 2.2 config file. I would suggest > starting with the .config file that came with kernel-source-2.4.18. > > > the questions as no, which was default. This is a 600 Mhz celeron > > system. Plain Jane. Did the make dep, make bzImage, make modules, make > > modules_install. Copied the bzImage to the DOS C: drive, modified a dos > > script to use loadlin to boot and rebooted. > > > > It looks like maybe there is a dump first thing, but the boot process > > rushes by so fast I really can't tell. Anyway somewere down the line, > > it fails telling me it can't find a root device on 03:06. The first > > time it said something about not finding anything on hda6. The loadlin > > command is identical to the one I use for 2.2.19. Is there something > > else going on that I'm not aware of? I saw a warning about using > > initrd, whatever that is in my browsing the web. Does that have > > anything to do with it? > > The stock debian kernel-images are configured to use initrd. If you > compile your own, you don't have to use initrd. > > If you don't use initrd, make sure the .config file has these settings: > > # CONFIG_BLK_DEV_INITRD is not set > CONFIG_IDE=y > CONFIG_BLK_DEV_IDE=y > CONFIG_BLK_DEV_IDEDISK=y > CONFIG_[your-root-file-system-module]_FS=y > CONFIG_JBD=y #if your root file system is ext3 > > > > > I've got another system that I attempted to compile 2.4.18 on. Similar > > setup. Upgraded to woody, apt-get the kernel source. Compiled, > > installed, rebooted with loadlin and it gets through spitting out the > > . line, blanks the screen and reboots. I'm not having a lot of > > luck with 2.4.18. > > > > Suggestions? > > > > Thanks, > > Jim. > > > > > > -- > Jerome > > >Part 1.2Type: application/pgp-signature -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 2.4.18 doesn't find my root device.
On Wed, Sep 11, 2002 at 02:30:06PM -0400, Jim Lynch wrote: > Simple description: 2.4.18 kernel panics and says it can't find the root > device on 03:06. 2.2.19 finds it fine. I had a root=/dev/hda6 on the > loadlin line, and it failed, so I took it off. Rdev of the kernel also > says root > on /dev/hda6. > > Background: > I upgraded to woody and found that my cdrom no longer worked. I figured > something had broken the modules but recompiling and depmod and modprobe > didn't seem to fix the problem. lsmod showed everything OK, but it > still didn't work. I'm running a ide-scsi setup since this is a > writer. > So I decided to upgrade the kernel to 2.4.18. I got the > kernel-source-2.4.18 via apt-get. Unbziped it. Copied my .config from > 2.2.19 to 2.4.18 and did a make oldconfig. I pretty much answered all I don't think copying your .config from your 2.2.19 is a good way to start. There have been a lot of changes. The config file for a 2.4.18 is about three times the size of a 2.2 config file. I would suggest starting with the .config file that came with kernel-source-2.4.18. > the questions as no, which was default. This is a 600 Mhz celeron > system. Plain Jane. Did the make dep, make bzImage, make modules, make > modules_install. Copied the bzImage to the DOS C: drive, modified a dos > script to use loadlin to boot and rebooted. > > It looks like maybe there is a dump first thing, but the boot process > rushes by so fast I really can't tell. Anyway somewere down the line, > it fails telling me it can't find a root device on 03:06. The first > time it said something about not finding anything on hda6. The loadlin > command is identical to the one I use for 2.2.19. Is there something > else going on that I'm not aware of? I saw a warning about using > initrd, whatever that is in my browsing the web. Does that have > anything to do with it? The stock debian kernel-images are configured to use initrd. If you compile your own, you don't have to use initrd. If you don't use initrd, make sure the .config file has these settings: # CONFIG_BLK_DEV_INITRD is not set CONFIG_IDE=y CONFIG_BLK_DEV_IDE=y CONFIG_BLK_DEV_IDEDISK=y CONFIG_[your-root-file-system-module]_FS=y CONFIG_JBD=y #if your root file system is ext3 > > I've got another system that I attempted to compile 2.4.18 on. Similar > setup. Upgraded to woody, apt-get the kernel source. Compiled, > installed, rebooted with loadlin and it gets through spitting out the > . line, blanks the screen and reboots. I'm not having a lot of > luck with 2.4.18. > > Suggestions? > > Thanks, > Jim. > > -- Jerome msg01883/pgp0.pgp Description: PGP signature
RE: 2.4.18 doesn't find my root device.
try dmesg Jim, that will output the startup messages to your monitor :-) that will allow you to view all the messages. I'm not familiar with loadlin at all (i've only ever used lilo b4 so i'll leave loadlin issues to those that know what they're talking about). Dave -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, 11 September 2002 4:30 AM To: Debian users; David Pastern Subject: 2.4.18 doesn't find my root device. Simple description: 2.4.18 kernel panics and says it can't find the root device on 03:06. 2.2.19 finds it fine. I had a root=/dev/hda6 on the loadlin line, and it failed, so I took it off. Rdev of the kernel also says root on /dev/hda6. Background: I upgraded to woody and found that my cdrom no longer worked. I figured something had broken the modules but recompiling and depmod and modprobe didn't seem to fix the problem. lsmod showed everything OK, but it still didn't work. I'm running a ide-scsi setup since this is a writer. So I decided to upgrade the kernel to 2.4.18. I got the kernel-source-2.4.18 via apt-get. Unbziped it. Copied my .config from 2.2.19 to 2.4.18 and did a make oldconfig. I pretty much answered all the questions as no, which was default. This is a 600 Mhz celeron system. Plain Jane. Did the make dep, make bzImage, make modules, make modules_install. Copied the bzImage to the DOS C: drive, modified a dos script to use loadlin to boot and rebooted. It looks like maybe there is a dump first thing, but the boot process rushes by so fast I really can't tell. Anyway somewere down the line, it fails telling me it can't find a root device on 03:06. The first time it said something about not finding anything on hda6. The loadlin command is identical to the one I use for 2.2.19. Is there something else going on that I'm not aware of? I saw a warning about using initrd, whatever that is in my browsing the web. Does that have anything to do with it? I've got another system that I attempted to compile 2.4.18 on. Similar setup. Upgraded to woody, apt-get the kernel source. Compiled, installed, rebooted with loadlin and it gets through spitting out the . line, blanks the screen and reboots. I'm not having a lot of luck with 2.4.18. Suggestions? Thanks, Jim. -- 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]
2.4.18 doesn't find my root device.
Simple description: 2.4.18 kernel panics and says it can't find the root device on 03:06. 2.2.19 finds it fine. I had a root=/dev/hda6 on the loadlin line, and it failed, so I took it off. Rdev of the kernel also says root on /dev/hda6. Background: I upgraded to woody and found that my cdrom no longer worked. I figured something had broken the modules but recompiling and depmod and modprobe didn't seem to fix the problem. lsmod showed everything OK, but it still didn't work. I'm running a ide-scsi setup since this is a writer. So I decided to upgrade the kernel to 2.4.18. I got the kernel-source-2.4.18 via apt-get. Unbziped it. Copied my .config from 2.2.19 to 2.4.18 and did a make oldconfig. I pretty much answered all the questions as no, which was default. This is a 600 Mhz celeron system. Plain Jane. Did the make dep, make bzImage, make modules, make modules_install. Copied the bzImage to the DOS C: drive, modified a dos script to use loadlin to boot and rebooted. It looks like maybe there is a dump first thing, but the boot process rushes by so fast I really can't tell. Anyway somewere down the line, it fails telling me it can't find a root device on 03:06. The first time it said something about not finding anything on hda6. The loadlin command is identical to the one I use for 2.2.19. Is there something else going on that I'm not aware of? I saw a warning about using initrd, whatever that is in my browsing the web. Does that have anything to do with it? I've got another system that I attempted to compile 2.4.18 on. Similar setup. Upgraded to woody, apt-get the kernel source. Compiled, installed, rebooted with loadlin and it gets through spitting out the . line, blanks the screen and reboots. I'm not having a lot of luck with 2.4.18. Suggestions? Thanks, Jim. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
