David G. Miller
2007-Dec-06 15:24 UTC
[CentOS] 5.x install - loses display when launching, anaconda
Tom Lanyon <tom at netspot.com.au> wrote:> On 06/12/2007, at 8:20 AM, James A. Peltier wrote: >> > Tom Lanyon wrote: >> >>> >> Hi all, >>> >> Trying to install 5.0 or 5.1 (i386 or x86_64) on a new system from >>> >> an install DVD. As soon as the installer launches anaconda, the >>> >> screen shuts off and from this point I'm unable to switch to any >>> >> other tty. This is an Intel core2duo machine on an Intel P35 >>> >> chipset motherboard, Geforce 8400GS video card connected to a BenQ >>> >> 20" widescreen LCD. >>> >> Any ideas what could cause this behaviour or how to debug further >>> >> (obviously I can't see any error messages as my virtual consoles >>> >> are no loner available)? >>> >> I think I'll try installing via a serial console when I get home >>> >> and see if I have more success. >>> >> Regards, >>> >> Tom >>> >> > >> > Try installing via a text console >> > >> > type linux text at the boot prompt. >> > > I forgot to mention I tried installing via both graphical and text. > Also tried a network-based text install. All presented no video output > whatsoever at the anaconda launch point.I think the correct option is "nofb" for no frame buffer at the original install screen (linux nofb). I ran into this when I first put Linux on my laptop back in the summer of 2005. I originally worked around it by just attaching an external monitor which also works but takes a little more planning and effort. The problem probably has something to do with anaconda shifting into graphics mode when anaconda starts but the mode isn't compatible with the laptop's LCD display. Using nofb tells the kernel not to use frame buffers which keeps the install in a standard (e.g., VGA) mode or the external monitor works with the display mode. Cheers, Dave -- Politics, n. Strife of interests masquerading as a contest of principles. -- Ambrose Bierce
Tom Lanyon
2007-Dec-06 23:57 UTC
[CentOS] 5.x install - loses display when launching, anaconda
On 07/12/2007, at 1:54 AM, David G. Miller wrote:> Tom Lanyon <tom at netspot.com.au> wrote: >> >> >> I forgot to mention I tried installing via both graphical and >> text. Also tried a network-based text install. All presented no >> video output whatsoever at the anaconda launch point. > I think the correct option is "nofb" for no frame buffer at the > original install screen (linux nofb). I ran into this when I first > put Linux on my laptop back in the summer of 2005. I originally > worked around it by just attaching an external monitor which also > works but takes a little more planning and effort. > The problem probably has something to do with anaconda shifting into > graphics mode when anaconda starts but the mode isn't compatible > with the laptop's LCD display. Using nofb tells the kernel not to > use frame buffers which keeps the install in a standard (e.g., VGA) > mode or the external monitor works with the display mode. > > Cheers, > DaveDave, Thanks - can't believe I didn't think of the framebuffer earlier. Using nofb does indeed allow me to progress with the installation. Cheers, Tom