[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [PATCH] Add a boot target for the xdriver=vesa parameter and document it.
- From: Jeremy Katz <katzj redhat com>
- To: Discussion of Development and Customization of the Red Hat Linux Installer <anaconda-devel-list redhat com>
- Subject: Re: [PATCH] Add a boot target for the xdriver=vesa parameter and document it.
- Date: Fri, 23 Jan 2009 11:08:58 -0500
On Friday, January 23 2009, Bill Nottingham said:
> Chris Lumens (clumens redhat com) said:
> > - If you have an installer update disk, type: 01linux updates <ENTER>07.
> >
> > + - If you have video driver problems, type: 01linux xdriver=vesa <ENTER>07.
> > +
> > - To test the memory in your system type: 01memtest86 <ENTER>07.
> > (This option is only available when booting from CD.)
>
> This says 'linux xdriver=vesa'
>
> > diff --git a/bootdisk/i386/syslinux.cfg b/bootdisk/i386/syslinux.cfg
> > index 012e6f6..a158a9a 100644
> > --- a/bootdisk/i386/syslinux.cfg
> > +++ b/bootdisk/i386/syslinux.cfg
> > @@ -25,6 +25,10 @@ label linux
> > menu default
> > kernel vmlinuz
> > append initrd=initrd.img
> > +label vesa
> > + menu label Install system with ^basic video driver
> > + kernel vmlinuz
> > + append initrd=initrd.img xdriver=vesa
> > label rescue
> > menu label ^Rescue installed system
> > kernel vmlinuz
>
> ... but this implies you can just type 'linux vesa'.
>
> If we end up with more of these, we may just want a stock 'safe' boot
> option that disables other weirdness.
Actually, it implies that you can type just 'vesa'. But making it
explicit in the help text will clue people in to other things that might
be able to do. Most people are just going to get the menu anyway
Jeremy
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]