root filesystem

root filesystem

[Igor Gueths]

Hi listers. I built a 2.4.17 kernel because this is what I happen to have, and rebooted the machine. It came up talking and it probed hardware successfully. However, it can't mount the root filesystem and it terminates with a kernel panic: fs: Unable to mount root filesystem. I checked system.map to make sure it said root=/dev/hda2 because this is my root partition, and it is also in lilo.conf as root=/dev/hda2. Here's basiclly what it looks like:
image=/boot/vmlinuz-2.4.17
label=Kernel1
read-only
root=/dev/hda2
alias=1

It also says root=/dev/hda2 closer to the top of the lilo.conf. What could I be missing? I alias back to the kernel with 2, and it boots fine. Any help would be great! Thanks in advance.

Igor


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

Re: root filesystem

[Janina Sajka]

Hi, Igor:

Are you using Red Hat? If you first configured and partitioned your system 
with a recent Red Hat you are probably using ext3 file system. This is 
good, but I don't know if it's supported in 2.4.17 by default.

Someone here will tell us, I'm sure.

I offer this up, because I've run into this a few times. 

PS: You can always move down to ext2fs using tune2fs -- read the man page 
for tune2fs to learn its commands -- but that would be too bad, because 
ext3 seems pretty helpful. If this is the issue, there's probably a patch 
for 2.4.17, though that will mean recompiling.
 On Thu, 14 Mar 2002, Igor 
Gueths wrote:

> Hi listers. I built a 2.4.17 kernel because this is what I happen to have, and rebooted the machine. It came up talking and it probed hardware successfully. However, it can't mount the root filesystem and it terminates with a kernel panic: fs: Unable to mount root filesystem. I checked system.map to make sure it said root=/dev/hda2 because this is my root partition, and it is also in lilo.conf as root=/dev/hda2. Here's basiclly what it looks like:
> image=/boot/vmlinuz-2.4.17
> label=Kernel1
> read-only
> root=/dev/hda2
> alias=1
> 
> It also says root=/dev/hda2 closer to the top of the lilo.conf. What could I be missing? I alias back to the kernel with 2, and it boots fine. Any help would be great! Thanks in advance.
> 
> Igor
> 
> 
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 

-- 
	
				Janina Sajka, Director
				Technology Research and Development
				Governmental Relations Group
				American Foundation for the Blind (AFB)

Email: janina@afb.net		Phone: (202) 408-8175

Chair, Accessibility SIG
Open Electronic Book Forum (OEBF)
http://www.openebook.org

Re: root filesystem

[Igor Gueths]

Hi Janina. Actually, I'm running Debian potato. Actually, the exact error is: Kernel panic: vfs: Unable to mount root filesystem on 0302. I'm not sure quite what 0302 refers to, I might just try playing with system.map some more trying different combinations. I used fdisk to partition the disk to ext2, and it boots fine with the old kernel. I just want to make sure there's nothing that I'm missing. And if you want, just let me know if you want me to post system.map to the list. Thanks again!
----- Original Message ----- 
From: Janina Sajka <janina@afb.net>
To: <speakup@braille.uwo.ca>
Sent: Thursday, March 14, 2002 4:44 PM
Subject: Re: root filesystem


> Hi, Igor:
> 
> Are you using Red Hat? If you first configured and partitioned your system 
> with a recent Red Hat you are probably using ext3 file system. This is 
> good, but I don't know if it's supported in 2.4.17 by default.
> 
> Someone here will tell us, I'm sure.
> 
> I offer this up, because I've run into this a few times. 
> 
> PS: You can always move down to ext2fs using tune2fs -- read the man page 
> for tune2fs to learn its commands -- but that would be too bad, because 
> ext3 seems pretty helpful. If this is the issue, there's probably a patch 
> for 2.4.17, though that will mean recompiling.
>  On Thu, 14 Mar 2002, Igor 
> Gueths wrote:
> 
> > Hi listers. I built a 2.4.17 kernel because this is what I happen to have, and rebooted the machine. It came up talking and it probed hardware successfully. However, it can't mount the root filesystem and it terminates with a kernel panic: fs: Unable to mount root filesystem. I checked system.map to make sure it said root=/dev/hda2 because this is my root partition, and it is also in lilo.conf as root=/dev/hda2. Here's basiclly what it looks like:
> > image=/boot/vmlinuz-2.4.17
> > label=Kernel1
> > read-only
> > root=/dev/hda2
> > alias=1
> > 
> > It also says root=/dev/hda2 closer to the top of the lilo.conf. What could I be missing? I alias back to the kernel with 2, and it boots fine. Any help would be great! Thanks in advance.
> > 
> > Igor
> > 
> > 
> > _________________________________________________________
> > Do You Yahoo!?
> > Get your free @yahoo.com address at http://mail.yahoo.com
> > 
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > 
> 
> -- 
> 
> Janina Sajka, Director
> Technology Research and Development
> Governmental Relations Group
> American Foundation for the Blind (AFB)
> 
> Email: janina@afb.net Phone: (202) 408-8175
> 
> Chair, Accessibility SIG
> Open Electronic Book Forum (OEBF)
> http://www.openebook.org
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

Re: root filesystem

[Ron Marriage]

Hello Igor,

Did you make a seperate boot partition.  If so how big?
The VFS error can occure if there is not enough room in the
/boot partition.
This is especially true if you included source headers and
recompiled a kernel.

I had the same error and elimenated it when I made /boot 75
or 80 megs instead of the smaller sizes that I used to.

Hope this helps
Ron



Igor Gueths wrote:
> 
> Hi Janina. Actually, I'm running Debian potato. Actually, the exact error is: Kernel panic: vfs: Unable to mount root filesystem on 0302. I'm not sure quite what 0302 refers to, I might just try playing with system.map some more trying different combinations. I used fdisk to partition the disk to ext2, and it boots fine with the old kernel. I just want to make sure there's nothing that I'm missing. And if you want, just let me know if you want me to post system.map to the list. Thanks again!

-- 
===
Ron Marriage
Home Page http://www.seidata.com/~marriage/
Blind Links http://www.seidata.com/~marriage/rblind.html
Linux  http://www.seidata.com/~seilug/
Email  mailto:marriage@seidata.com

Win door prizes!  Meet old and new friends!  
See the latest technology and gadgets for your everyday
living!  
Learn how the NFB is helping to knock down barriers 
to make your life better! 
All this and more at the 2002 NFB National Convention 
July 3 - 9 -- for details go to: http://www.nfbk.org

Re: root filesystem

[Gregory Nowak]

2.4.17 has an ext3 configuration option in it by default.
Greg


On Thu, Mar 14, 2002 at 04:44:42PM -0500, Janina Sajka wrote:
> Hi, Igor:
> 
> Are you using Red Hat? If you first configured and partitioned your system 
> with a recent Red Hat you are probably using ext3 file system. This is 
> good, but I don't know if it's supported in 2.4.17 by default.
> 
> Someone here will tell us, I'm sure.
> 
> I offer this up, because I've run into this a few times. 
> 
> PS: You can always move down to ext2fs using tune2fs -- read the man page 
> for tune2fs to learn its commands -- but that would be too bad, because 
> ext3 seems pretty helpful. If this is the issue, there's probably a patch 
> for 2.4.17, though that will mean recompiling.
>  On Thu, 14 Mar 2002, Igor 
> Gueths wrote:
> 
> > Hi listers. I built a 2.4.17 kernel because this is what I happen to have, and rebooted the machine. It came up talking and it probed hardware successfully. However, it can't mount the root filesystem and it terminates with a kernel panic: fs: Unable to mount root filesystem. I checked system.map to make sure it said root=/dev/hda2 because this is my root partition, and it is also in lilo.conf as root=/dev/hda2. Here's basiclly what it looks like:
> > image=/boot/vmlinuz-2.4.17
> > label=Kernel1
> > read-only
> > root=/dev/hda2
> > alias=1
> > 
> > It also says root=/dev/hda2 closer to the top of the lilo.conf. What could I be missing? I alias back to the kernel with 2, and it boots fine. Any help would be great! Thanks in advance.
> > 
> > Igor
> > 
> > 
> > _________________________________________________________
> > Do You Yahoo!?
> > Get your free @yahoo.com address at http://mail.yahoo.com
> > 
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > 
> 
> -- 
> 	
> 				Janina Sajka, Director
> 				Technology Research and Development
> 				Governmental Relations Group
> 				American Foundation for the Blind (AFB)
> 
> Email: janina@afb.net		Phone: (202) 408-8175
> 
> Chair, Accessibility SIG
> Open Electronic Book Forum (OEBF)
> http://www.openebook.org
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: root filesystem

[Igor Gueths]

Hi. I actually fixed that problem, but now have to deal with modprobe errors that it can't locate module netBF. Could doing a depmod-a in the old kernel fix this problem? Thanks in advance. 
----- Original Message ----- 
From: Ron Marriage <marriage@seidata.com>
To: <speakup@braille.uwo.ca>
Sent: Thursday, March 14, 2002 9:20 PM
Subject: Re: root filesystem


> Hello Igor,
> 
> Did you make a seperate boot partition.  If so how big?
> The VFS error can occure if there is not enough room in the
> /boot partition.
> This is especially true if you included source headers and
> recompiled a kernel.
> 
> I had the same error and elimenated it when I made /boot 75
> or 80 megs instead of the smaller sizes that I used to.
> 
> Hope this helps
> Ron
> 
> 
> 
> Igor Gueths wrote:
> > 
> > Hi Janina. Actually, I'm running Debian potato. Actually, the exact error is: Kernel panic: vfs: Unable to mount root filesystem on 0302. I'm not sure quite what 0302 refers to, I might just try playing with system.map some more trying different combinations. I used fdisk to partition the disk to ext2, and it boots fine with the old kernel. I just want to make sure there's nothing that I'm missing. And if you want, just let me know if you want me to post system.map to the list. Thanks again!
> 
> -- 
> ===
> Ron Marriage
> Home Page http://www.seidata.com/~marriage/
> Blind Links http://www.seidata.com/~marriage/rblind.html
> Linux  http://www.seidata.com/~seilug/
> Email  mailto:marriage@seidata.com
> 
> Win door prizes!  Meet old and new friends!  
> See the latest technology and gadgets for your everyday
> living!  
> Learn how the NFB is helping to knock down barriers 
> to make your life better! 
> All this and more at the 2002 NFB National Convention 
> July 3 - 9 -- for details go to: http://www.nfbk.org
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

Re: root filesystem

[Gregory Nowak]

Doing "depmod -a" in the old kernel isn't relevent, because the new kernel won't give a hoot. You should instead do that in the new kernel.
Greg


On Thu, Mar 14, 2002 at 09:31:04PM -0500, Igor Gueths wrote:
> Hi. I actually fixed that problem, but now have to deal with modprobe errors that it can't locate module netBF. Could doing a depmod-a in the old kernel fix this problem? Thanks in advance. 
> ----- Original Message ----- 
> From: Ron Marriage <marriage@seidata.com>
> To: <speakup@braille.uwo.ca>
> Sent: Thursday, March 14, 2002 9:20 PM
> Subject: Re: root filesystem
> 
> 
> > Hello Igor,
> > 
> > Did you make a seperate boot partition.  If so how big?
> > The VFS error can occure if there is not enough room in the
> > /boot partition.
> > This is especially true if you included source headers and
> > recompiled a kernel.
> > 
> > I had the same error and elimenated it when I made /boot 75
> > or 80 megs instead of the smaller sizes that I used to.
> > 
> > Hope this helps
> > Ron
> > 
> > 
> > 
> > Igor Gueths wrote:
> > > 
> > > Hi Janina. Actually, I'm running Debian potato. Actually, the exact error is: Kernel panic: vfs: Unable to mount root filesystem on 0302. I'm not sure quite what 0302 refers to, I might just try playing with system.map some more trying different combinations. I used fdisk to partition the disk to ext2, and it boots fine with the old kernel. I just want to make sure there's nothing that I'm missing. And if you want, just let me know if you want me to post system.map to the list. Thanks again!
> > 
> > -- 
> > ===
> > Ron Marriage
> > Home Page http://www.seidata.com/~marriage/
> > Blind Links http://www.seidata.com/~marriage/rblind.html
> > Linux  http://www.seidata.com/~seilug/
> > Email  mailto:marriage@seidata.com
> > 
> > Win door prizes!  Meet old and new friends!  
> > See the latest technology and gadgets for your everyday
> > living!  
> > Learn how the NFB is helping to knock down barriers 
> > to make your life better! 
> > All this and more at the 2002 NFB National Convention 
> > July 3 - 9 -- for details go to: http://www.nfbk.org
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> 
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: root filesystem

[Shaun Oliver]

On Thu, 14 Mar 2002, Gregory Nowak wrote:

> Doing "depmod -a" in the old kernel isn't relevent, because the new kernel won't give a hoot. You should instead do that in the new kernel.
> Greg
>
>
> On Thu, Mar 14, 2002 at 09:31:04PM -0500, Igor Gueths wrote:
> > Hi. I actually fixed that problem, but now have to deal with modprobe errors that it can't locate module netBF. Could doing a depmod-a in the old kernel fix this problem? Thanks in advance.
hi there,
well, I think you won't ve needing netpf unless you're serving files to an
apple computer somewhere on your network.

-- 
qShaun Oliver

Marriage is a three ring circus:
engagement ring, wedding ring, and suffering.
                -- Roger Price

Email: shauno@goanna.net.au
Icq: 76958435

Re: root filesystem

[jwantz]

Hi Igor,
In case noone has replied to you yet, ext3 is definitely an option in 
2.4.17.  Rebuild 2.4.17 and make sure you include ext3.  

      Good Luck,
       Jim Wantz
On Thu, 14 Mar 
2002, Janina Sajka wrote:

> Hi, Igor:
> 
> Are you using Red Hat? If you first configured and partitioned your system 
> with a recent Red Hat you are probably using ext3 file system. This is 
> good, but I don't know if it's supported in 2.4.17 by default.
> 
> Someone here will tell us, I'm sure.
> 
> I offer this up, because I've run into this a few times. 
> 
> PS: You can always move down to ext2fs using tune2fs -- read the man page 
> for tune2fs to learn its commands -- but that would be too bad, because 
> ext3 seems pretty helpful. If this is the issue, there's probably a patch 
> for 2.4.17, though that will mean recompiling.
>  On Thu, 14 Mar 2002, Igor 
> Gueths wrote:
> 
> > Hi listers. I built a 2.4.17 kernel because this is what I happen to have, and rebooted the machine. It came up talking and it probed hardware successfully. However, it can't mount the root filesystem and it terminates with a kernel panic: fs: Unable to mount root filesystem. I checked system.map to make sure it said root=/dev/hda2 because this is my root partition, and it is also in lilo.conf as root=/dev/hda2. Here's basiclly what it looks like:
> > image=/boot/vmlinuz-2.4.17
> > label=Kernel1
> > read-only
> > root=/dev/hda2
> > alias=1
> > 
> > It also says root=/dev/hda2 closer to the top of the lilo.conf. What could I be missing? I alias back to the kernel with 2, and it boots fine. Any help would be great! Thanks in advance.
> > 
> > Igor
> > 
> > 
> > _________________________________________________________
> > Do You Yahoo!?
> > Get your free @yahoo.com address at http://mail.yahoo.com
> > 
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > 
> 
> 

Re: root filesystem

[Igor Gueths]

Hi Shaun. I don't think I compiled support for appletalk, in fact I didn't. So why could modprobe be complaining that it can't find the module? And the worst about is, that as a result of the modprobe error, the kernel won't boot. And everything checks out fine up to that point. Would you know how to fix it so Modprobe doesn't probe for that module when booting my new kernel? Note: I'm going to try to boot the 2.4.18 kernel, but the same thing might happen. Thanks in advance! 
----- Original Message ----- 
From: Shaun Oliver <shauno@goanna.net.au>
To: <speakup@braille.uwo.ca>
Sent: Thursday, March 14, 2002 11:33 PM
Subject: Re: root filesystem


> On Thu, 14 Mar 2002, Gregory Nowak wrote:
> 
> > Doing "depmod -a" in the old kernel isn't relevent, because the new kernel won't give a hoot. You should instead do that in the new kernel.
> > Greg
> >
> >
> > On Thu, Mar 14, 2002 at 09:31:04PM -0500, Igor Gueths wrote:
> > > Hi. I actually fixed that problem, but now have to deal with modprobe errors that it can't locate module netBF. Could doing a depmod-a in the old kernel fix this problem? Thanks in advance.
> hi there,
> well, I think you won't ve needing netpf unless you're serving files to an
> apple computer somewhere on your network.
> 
> -- 
> qShaun Oliver
> 
> Marriage is a three ring circus:
> engagement ring, wedding ring, and suffering.
>                 -- Roger Price
> 
> Email: shauno@goanna.net.au
> Icq: 76958435
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

Re: root filesystem

[Gregory Nowak]

That modprobe error is happening exactly bedcause you don't have apple talk. See my other post on how to take care of it.
Greg


On Fri, Mar 15, 2002 at 07:29:21PM -0500, Igor Gueths wrote:
> Hi Shaun. I don't think I compiled support for appletalk, in fact I didn't. So why could modprobe be complaining that it can't find the module? And the worst about is, that as a result of the modprobe error, the kernel won't boot. And everything checks out fine up to that point. Would you know how to fix it so Modprobe doesn't probe for that module when booting my new kernel? Note: I'm going to try to boot the 2.4.18 kernel, but the same thing might happen. Thanks in advance! 
> ----- Original Message ----- 
> From: Shaun Oliver <shauno@goanna.net.au>
> To: <speakup@braille.uwo.ca>
> Sent: Thursday, March 14, 2002 11:33 PM
> Subject: Re: root filesystem
> 
> 
> > On Thu, 14 Mar 2002, Gregory Nowak wrote:
> > 
> > > Doing "depmod -a" in the old kernel isn't relevent, because the new kernel won't give a hoot. You should instead do that in the new kernel.
> > > Greg
> > >
> > >
> > > On Thu, Mar 14, 2002 at 09:31:04PM -0500, Igor Gueths wrote:
> > > > Hi. I actually fixed that problem, but now have to deal with modprobe errors that it can't locate module netBF. Could doing a depmod-a in the old kernel fix this problem? Thanks in advance.
> > hi there,
> > well, I think you won't ve needing netpf unless you're serving files to an
> > apple computer somewhere on your network.
> > 
> > -- 
> > qShaun Oliver
> > 
> > Marriage is a three ring circus:
> > engagement ring, wedding ring, and suffering.
> >                 -- Roger Price
> > 
> > Email: shauno@goanna.net.au
> > Icq: 76958435
> > 
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> 
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

re: root filesystem

[Toby Fisher]

On Thu, 14 Mar 2002, Adam Myrow wrote:

> Did you compile IDE support in your kernel?  What about PCI?  Did you try
> building the kernel based on the .config from the old one if they are both
> 2.4 kernels?  This stuff may seem obvious, but my first kernel build was a
> disaster because I misread something and turned off PCI support when I
> have a PCI/EISA hybrid system.  The result was basically a non-functioning
> serial port and lots of error messages.  BTW, kernel 2.4.17 has EXT3 as an
> option.

Hehehe, I once compiled a kernel without ext2fs support, I was using
2.0.36 at the time.  Fortunately, I realised what I'd done before I tried
to boot it. *grin*

Cheers.
-- 
Toby Fisher	Email: toby@g0ucu.freeserve.co.uk
Tel.: +44(0)1480 417272	Mobile: +44(0)7974 363239
ICQ: #61744808

Re: root filesystem

[Gregory Nowak]

I don't know what you're running, but in slackware, take a look at /etc/rc.d/rc.modules, and comment out the line that tries to load that module.
Greg


On Fri, Mar 15, 2002 at 07:21:14PM -0500, Igor Gueths wrote:
> Hi Greg. Yes I did fix the problem with my controller, the problem was that I had only compiled in the driver which supported only a single controller, and it turns out I have two ide controllers. However, the only thing that is happening with 2.4.17 is that I get the following when booting: Modprobe Modprobe: Can't locate Module Net BF or something like that. I am now compiling the bzImage for 2.4.18 to see if I can fix the problem with a new kernel. But why would I get that error? Considering that the dependencies file was created properly, and the rest of the kernel compiled fine. It doesn't really make sense. This is why I asked about depmod in the last message. Thanks for any help regarding this!
> ----- Original Message ----- 
> From: Gregory Nowak <gnowak1@uic.edu>
> To: <speakup@braille.uwo.ca>
> Sent: Thursday, March 14, 2002 9:33 PM
> Subject: Re: root filesystem
> 
> 
> > Does your kernel have support for your controller?
> > Greg
> > 
> > 
> > On Thu, Mar 14, 2002 at 06:19:33PM -0500, Igor Gueths wrote:
> > > Hi listers. Sorry to post so many messages, but I was looking through the boot-up messages from my kernel 2.4.17, and discovered the following: When probing for /dev/hda, I got a message that said autoprobe failed. I have a macsterdrive, and when I boot into my old 2.2.18pre21-idepci kernel, it probes everything fine, including the hard drive. Is there anything I have to compile into the 2.4.17 kernel that I might have missed? I don't think so, but you never know. If anyone is interested, I can record an mp3 of my dec-talk express reading all the boot-up messages up to the kernel panic, and then post it to the list if anyone would like a clearer explanation. Does anyone know how to fix this problem? Or has anyone encountered this before and has fixed it? Thanks for the help and sorry about all the posts! I was just updating everyone as I found out new information. 
> > > 
> > > 
> > > _________________________________________________________
> > > Do You Yahoo!?
> > > Get your free @yahoo.com address at http://mail.yahoo.com
> > > 
> > > 
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> 
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: root filesystem

[Igor Gueths]

Hi Greg. Yes I did fix the problem with my controller, the problem was that I had only compiled in the driver which supported only a single controller, and it turns out I have two ide controllers. However, the only thing that is happening with 2.4.17 is that I get the following when booting: Modprobe Modprobe: Can't locate Module Net BF or something like that. I am now compiling the bzImage for 2.4.18 to see if I can fix the problem with a new kernel. But why would I get that error? Considering that the dependencies file was created properly, and the rest of the kernel compiled fine. It doesn't really make sense. This is why I asked about depmod in the last message. Thanks for any help regarding this!
----- Original Message ----- 
From: Gregory Nowak <gnowak1@uic.edu>
To: <speakup@braille.uwo.ca>
Sent: Thursday, March 14, 2002 9:33 PM
Subject: Re: root filesystem


> Does your kernel have support for your controller?
> Greg
> 
> 
> On Thu, Mar 14, 2002 at 06:19:33PM -0500, Igor Gueths wrote:
> > Hi listers. Sorry to post so many messages, but I was looking through the boot-up messages from my kernel 2.4.17, and discovered the following: When probing for /dev/hda, I got a message that said autoprobe failed. I have a macsterdrive, and when I boot into my old 2.2.18pre21-idepci kernel, it probes everything fine, including the hard drive. Is there anything I have to compile into the 2.4.17 kernel that I might have missed? I don't think so, but you never know. If anyone is interested, I can record an mp3 of my dec-talk express reading all the boot-up messages up to the kernel panic, and then post it to the list if anyone would like a clearer explanation. Does anyone know how to fix this problem? Or has anyone encountered this before and has fixed it? Thanks for the help and sorry about all the posts! I was just updating everyone as I found out new information. 
> > 
> > 
> > _________________________________________________________
> > Do You Yahoo!?
> > Get your free @yahoo.com address at http://mail.yahoo.com
> > 
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

Re: root filesystem

[Janina Sajka]

Igor:

You don't need to mp3 anything. All the data is available in /var/log. 
Much easier than trying to hear the data as you boot.
On Thu, 14 Mar 2002, 
Igor Gueths wrote:

> Hi listers. Sorry to post so many messages, but I was looking through the boot-up messages from my kernel 2.4.17, and discovered the following: When probing for /dev/hda, I got a message that said autoprobe failed. I have a macsterdrive, and when I boot into my old 2.2.18pre21-idepci kernel, it probes everything fine, including the hard drive. Is there anything I have to compile into the 2.4.17 kernel that I might have missed? I don't think so, but you never know. If anyone is interested, I can record an mp3 of my dec-talk express reading all the boot-up messages up to the kernel panic, and then post it to the list if anyone would like a clearer explanation. Does anyone know how to fix this problem? Or has anyone encountered this before and has fixed it? Thanks for the help and sorry about all the posts! I was just updating everyone as I found out new information. 
> 
> 
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 

-- 
	
				Janina Sajka, Director
				Technology Research and Development
				Governmental Relations Group
				American Foundation for the Blind (AFB)

Email: janina@afb.net		Phone: (202) 408-8175

Chair, Accessibility SIG
Open Electronic Book Forum (OEBF)
http://www.openebook.org

re: root filesystem

[Adam Myrow]

Did you compile IDE support in your kernel?  What about PCI?  Did you try
building the kernel based on the .config from the old one if they are both
2.4 kernels?  This stuff may seem obvious, but my first kernel build was a
disaster because I misread something and turned off PCI support when I
have a PCI/EISA hybrid system.  The result was basically a non-functioning
serial port and lots of error messages.  BTW, kernel 2.4.17 has EXT3 as an
option.

Re: root filesystem

[Gregory Nowak]

Does your kernel have support for your controller?
Greg


On Thu, Mar 14, 2002 at 06:19:33PM -0500, Igor Gueths wrote:
> Hi listers. Sorry to post so many messages, but I was looking through the boot-up messages from my kernel 2.4.17, and discovered the following: When probing for /dev/hda, I got a message that said autoprobe failed. I have a macsterdrive, and when I boot into my old 2.2.18pre21-idepci kernel, it probes everything fine, including the hard drive. Is there anything I have to compile into the 2.4.17 kernel that I might have missed? I don't think so, but you never know. If anyone is interested, I can record an mp3 of my dec-talk express reading all the boot-up messages up to the kernel panic, and then post it to the list if anyone would like a clearer explanation. Does anyone know how to fix this problem? Or has anyone encountered this before and has fixed it? Thanks for the help and sorry about all the posts! I was just updating everyone as I found out new information. 
> 
> 
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

root filesystem

[Igor Gueths]

Hi listers. Sorry to post so many messages, but I was looking through the boot-up messages from my kernel 2.4.17, and discovered the following: When probing for /dev/hda, I got a message that said autoprobe failed. I have a macsterdrive, and when I boot into my old 2.2.18pre21-idepci kernel, it probes everything fine, including the hard drive. Is there anything I have to compile into the 2.4.17 kernel that I might have missed? I don't think so, but you never know. If anyone is interested, I can record an mp3 of my dec-talk express reading all the boot-up messages up to the kernel panic, and then post it to the list if anyone would like a clearer explanation. Does anyone know how to fix this problem? Or has anyone encountered this before and has fixed it? Thanks for the help and sorry about all the posts! I was just updating everyone as I found out new information. 


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com