With 2.5.51 (gcc-3.2, Athlon, mostly modules, DEVFS=y, DEVFS_DEBUG=y),
boot panics with "VFS: Cannot open root device "hda1" or
03:01".
I had the same problem with 2.5.50, avoidable by disabling devfs entirely.
-Eric
On Tue, Dec 10, 2002 at 11:18:35AM -0500, Eric Buddington wrote:
> With 2.5.51 (gcc-3.2, Athlon, mostly modules, DEVFS=y, DEVFS_DEBUG=y),
> boot panics with "VFS: Cannot open root device "hda1" or
> 03:01".
>
> I had the same problem with 2.5.50, avoidable by disabling devfs entirely.
Sounds similar to http://bugzilla.kernel.org/show_bug.cgi?id=110
Does enabling UNIX98 pty's fix your problem ?
Dave
> > I had the same problem with 2.5.50, avoidable by disabling devfs entirely.
>
> Sounds similar to http://bugzilla.kernel.org/show_bug.cgi?id=110
> Does enabling UNIX98 pty's fix your problem ?
I have the same issue, even with
CONFIG_UNIX98_PTYS = Y
CONFIG_DEVFS_FS = Y
CONFIG_DEVFS_MOUNT = Y
CONFIG_DEVFS_DEBUG = Y
CONFIG_DEVPTS_FS = Y
I am trying to invistigate problem closely for now.
All the Best!
Serge.
Eric I have a bug open on bugzilla for this.
The only workaround I know is by enabling CONFIG_UNIX98_PTYS=Y under
character devices.
Mohamed El Ayouty
> > > I had the same problem with 2.5.50, avoidable by disabling devfs entirely.
> >
> > Sounds similar to http://bugzilla.kernel.org/show_bug.cgi?id=110
> > Does enabling UNIX98 pty's fix your problem ?
>
> I have the same issue, even with
> CONFIG_UNIX98_PTYS = Y
> CONFIG_DEVFS_FS = Y
> CONFIG_DEVFS_MOUNT = Y
> CONFIG_DEVFS_DEBUG = Y
> CONFIG_DEVPTS_FS = Y
>
> I am trying to invistigate problem closely for now.
>
I've got email with recomendations, and removed CONFIG_DEVFS_DEBUG. The issue has been solved.
All the Best!
Serge.
This fixed my problem (though now it doesn't find init, *sigh*)
-Eric
On Tue, Dec 10, 2002 at 04:44:43PM +0000, [email protected] wrote:
> Are you using grub to boot? If so try using something
> like /dev/discs/disc0/part1 or the full ide /dev pathname for devfs to boot
> with instead of /dev/hda1. I have a scsi disk subsystem and have to
> use /dev/discs/disc0/part9 instead of /dev/sda9 to get devfs to work.
>
> Jordan
> > With 2.5.51 (gcc-3.2, Athlon, mostly modules, DEVFS=y, DEVFS_DEBUG=y),
> > boot panics with "VFS: Cannot open root device "hda1" or
> > 03:01".
> >
> > I had the same problem with 2.5.50, avoidable by disabling devfs entirely.
> >
> > -Eric
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to [email protected]
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
Eric Buddington wrote:
>
> With 2.5.51 (gcc-3.2, Athlon, mostly modules, DEVFS=y, DEVFS_DEBUG=y),
> boot panics with "VFS: Cannot open root device "hda1" or
> 03:01".
>
> I had the same problem with 2.5.50, avoidable by disabling devfs entirely.
>
> -Eric
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
Booting anything later than 2.5.48 with devfs configured
either needs an extra kernel parameter, or a code change.
Something broke when do_mounts.c were reorganized.
It doesn't matter wether devfs is used or not, as long as it
is configured.
The lilo solution:
lilo tend to have a "root=/dev/hda1" or similiar.
This gets converted to "root=0301" on the kernel command line.
(Look at dmesg after a successful boot)
But this don't work for some reason when devfs is configured.
Use the following:
append="root=/dev/hda1"
to solve the problem. This isn't converted to numbers and works.
Of course if you use auto-mounted devfs then you don't
have a /dev/hda1 but a /dev/ide/host0/bus0/target0/lun0/part1
instead. If so, use that as root instead. You still have
to use the append= trick.
The code solution:
Edit init/do_mounts.c
Remove the following lines from the beginning of
the function prepare_namespace:
#ifdef CONFIG_DEVFS_FS
sys_mount("devfs", "/dev", "devfs", 0, NULL);
do_devfs = 1;
#endif
Then recompile, and the kernel should work with any lilo setup that
worked for 2.5.47 and earlier. At least it worked for the setups
I tried.
This has no effect on kernels without devfs, and helps for kernels
comiled with devfs wether devfs is used or not.
I posted a patch for this, but there were no interest at all.
Helge Hafting
On Wed, Dec 11, 2002 at 11:00:08AM +0100, Helge Hafting wrote:
TREMENDOUS: without those four ligns, I can boot 2.5.51 ;-)
Thank you very much!!!
> Booting anything later than 2.5.48 with devfs configured
> either needs an extra kernel parameter, or a code change.
> Something broke when do_mounts.c were reorganized.
> It doesn't matter wether devfs is used or not, as long as it
> is configured.
>
> The lilo solution:
> lilo tend to have a "root=/dev/hda1" or similiar.
> This gets converted to "root=0301" on the kernel command line.
> (Look at dmesg after a successful boot)
>
> But this don't work for some reason when devfs is configured.
> Use the following:
>
> append="root=/dev/hda1"
>
> to solve the problem. This isn't converted to numbers and works.
> Of course if you use auto-mounted devfs then you don't
> have a /dev/hda1 but a /dev/ide/host0/bus0/target0/lun0/part1
> instead. If so, use that as root instead. You still have
> to use the append= trick.
>
> The code solution:
> Edit init/do_mounts.c
> Remove the following lines from the beginning of
> the function prepare_namespace:
> #ifdef CONFIG_DEVFS_FS
> sys_mount("devfs", "/dev", "devfs", 0, NULL);
> do_devfs = 1;
> #endif
> Then recompile, and the kernel should work with any lilo setup that
> worked for 2.5.47 and earlier. At least it worked for the setups
> I tried.
>
> This has no effect on kernels without devfs, and helps for kernels
> comiled with devfs wether devfs is used or not.
> I posted a patch for this, but there were no interest at all.
Gr?goire
________________________________________________________________
http://ulima.unil.ch/greg ICQ:16624071 mailto:[email protected]