I believe this is occurring before the nvidia driver gets involved. Have you tried downgrading nvidia? On Oct 27, 2010 11:15 PM, "Heiko Baums" <lists@xxxxxxxxxxxxxxx> wrote: > Am Wed, 27 Oct 2010 21:36:52 -0500 > schrieb "David C. Rankin" <drankinatty@xxxxxxxxxxxxxxxxxx>: > >> Guys, >> >> To add to the nvidia issues, after update to the latest >> driver (nvidia 260.19.12-1) the machine stops during boot due to >> (Invalid video mode, press enter to see list....) >> >> Pressing enter then lists the available modes. However, when >> I enter one of the listed modes, it is rejected and I get prompted >> again with the (Invalid video mode, press enter to see list....). >> >> I don't know whether this is a bug, a KMS thing, or what, but >> I have never had any problems passing vga=0x31a on the kernel line >> with the nvidia driver before. (I know with ATI, KMS early is >> recommended, and no vga= on the kernel line) >> >> Is anybody else seeing this? Should I just remove the vga= >> line? >> >> After letting the (Invalid video mode, press enter to see >> list....) prompt time-out, it all continues fine and the nvidia >> driver loads without issue. What say the experts? > > There's an option to scanning your video card for valid values. If I > recall correctly you just can enter "scan" at that prompt. Then you can > set vga= to one of the possible values. > > But if you're using KMS you need to remove the vga kernel parameter. If > you don't want to use KMS, add the kernel parameters vga and nomodeset. > > Heiko
