[TriLUG] Mandrake 8.0->8.1 upgrade problem

[Matt Jezorek]

I am wondering if the initrd.img boots up the devfs I had problems with this
before on mandrake and when i took at the append=" devfs=mount" option it
worked fine. Sorry I dont know what else it might be in that case
----- Original Message -----
From: "Chris Merrill" <cmerrill at nc.rr.com>
To: <trilug at trilug.org>
Sent: Tuesday, October 30, 2001 1:13 PM
Subject: Re: [TriLUG] Mandrake 8.0->8.1 upgrade problem


> Matt Jezorek said:
> > go into /etc/lilo.conf
> > and remove devfs=mount from the append line and reboot
>
> I tried this, but it did not help.
>
> Here is my lilo.conf file
> The 1st boot image (label=linux) is what I use during boot, and
> it is also the one that I removed the line you mentioned:
>
> boot=/dev/hda
> map=/boot/map
> install=/boot/boot.b
> vga=normal
> default=linux
> keytable=/boot/us.klt
> lba32
> prompt
> timeout=50
> message=/boot/message
> menu-scheme=wb:bw:wb:bw
> image=/boot/vmlinuz
> label=linux
> root=/dev/hda5
> initrd=/boot/initrd.img
> append=" quiet"
> vga=791
> read-only
> image=/boot/vmlinuz-2.4.6-5mdk
> label=old_linux
> root=/dev/hda5
> append=" quiet"
> vga=791
> read-only
> image=/boot/vmlinuz-2.4.6-5mdk
> label=old1_linux-nonf
> root=/dev/hda5
> read-only
> image=/boot/vmlinuz-2.4.6-5mdk
> label=old2_failsafe
> root=/dev/hda5
> append=" failsafe"
> read-only
> image=/boot/vmlinuz
> label=linux-nonfb
> root=/dev/hda5
> initrd=/boot/initrd.img
> append=" devfs=mount"
> read-only
> image=/boot/vmlinuz
> label=failsafe
> root=/dev/hda5
> initrd=/boot/initrd.img
> append=" devfs=mount failsafe"
> read-only
> image=/boot/vmlinuz-2.2secure
> label=linux-2.2
> root=/dev/hda5
> initrd=/boot/initrd-2.2secure.img
> append=" devfs=mount"
> vga=788
> read-only
> other=/dev/fd0
> label=floppy
> unsafe
>
>
> > ----- Original Message -----
> > From: "Chris Merrill" <cmerrill at nc.rr.com>
> > To: <trilug at trilug.org>
> > Sent: Tuesday, October 30, 2001 10:38 AM
> > Subject: [TriLUG] Mandrake 8.0->8.1 upgrade problem
> >
> > > My upgrade did not go as well as I had initially hoped...I can no
> > > longer mount my CDROM...this is what I get:
> > >
> > >   [root at rx8 chris]# mount /mnt/cdrom
> > >   mount: special device /dev/cdrom does not exist
> > >   [root at rx8 chris]# mount /dev/cdrom
> > >   mount: special device /dev/cdrom does not exist
> > >
> > > So, I went to find if the directory did or did not exist:
> > >
> > >   [root at rx8 chris]# cd /dev
> > >   [root at rx8 dev]# ls -l cd*
> > >   lr-xr-xr-x    1 root     root           16 Oct 30 08:17 cdrom ->
> >
> > ../cdroms/cdrom0
> >
> > >   lr-xr-xr-x    1 root     root           13 Oct 30 03:17 cdrom1 ->
> >
> > cdroms/cdrom1
> >
> > >   cdroms:
> > >   total 0
> > >   lr-xr-xr-x    1 root     root           33 Dec 31  1969 cdrom1 ->
> >
> > ../ide/host0/bus1/target0/lun0/cd
> >
> > > Those links look to be intact (although I have no idea what I'm
looking
> >
> > at), so
> >
> > > I followed the links a little farther and found:
> > >
> > >   [root at rx8 lun0]# cd /dev/ide/host0/bus1/target0/lun0
> > >   [root at rx8 lun0]# ls -l
> > >   total 0
> > >   brw-------    1 chris    cdrom     22,   0 Oct 30 08:13 cd
> > >
> > > Is this what I should see?
> > > Anybody know what I should do next?  Obviously, having a working
> > > CDROM is kinda important to me...
> > >
> > > *********************************
> > > Chris Merrill
> > > cmerrill at nc.rr.com
> > > *********************************
> > > _______________________________________________
> > > TriLUG mailing list
> > > http://www.trilug.org/mailman/listinfo/trilug
> >
> > _______________________________________________
> > TriLUG mailing list
> > http://www.trilug.org/mailman/listinfo/trilug
>
> --
> *********************************
> Chris Merrill
> cmerrill at nc.rr.com
> *********************************
> _______________________________________________
> TriLUG mailing list
> http://www.trilug.org/mailman/listinfo/trilug
>