Graphic Card Issue

[dms05]

I've just installed v13.37 (KDE) to sda1 from the LiveCD. With the LiveCD my nVidia graphics card was recognised and the correct 1920*1080 screen size set. However after full installation the graphics card isn't recognised and the screen remains blank (after showing a few seconds of the initial text during booting). If I then leave the computer for 15 minutes and I let the screen auto shuts down the correct resolution is chosen when I reactivate the screen and all is well. As I can't see anything before auto shut down is their anyway I can force the correct selection of the screen resolution?

[thom1]

Did you specify "vga=normal" to your lilo.conf ? Because you have to.

[dms05]

No, I just used the fully auto install routine. So even after a fully auto install I still need to modify Lilo?

Later.......

I entered exactly the command as recommended and all is now working. Many thanks.

[thom1]

I don't know, I never use salix livecd and never run auto-install.

[gapan]

Weird, I don't think there's anything different in the live CD. You shouldn't need to add anything to lilo.conf. Try installing the binary driver from nvidia.

[Shador]

Weird, I don't think there's anything different in the live CD.

Yes, there's a small difference. The LiveCD does not use lilo but grub2 instead. And grub2 is configured to initialize the frame buffer and pass some data to the kernel during booting, which allows it to use that same framebuffer without reinitializing it. That has some advantages regarding aesthetics, flexibility and a little performance.
With lilo the kernel is setting up the framebuffer separately by itself. But actually I would have more expected occasional problems with the LiveCD than the other way round.

This seems like modesetting issue as you mention that you get some very early kernel messages until the native resolution kicks in. This change of resolution happens after the early boot stage regardless of lilo or grub2 since KMS has been integrated into the kernel and if the driver supports it of course. You could try passing 'nomodeset' to the kernel.

[JRD]

Totally agree with Shador analisys.

Add "nomodeset" to the kernel parameter on boot.