Problems with No Video
Posted: Tue May 07, 2013 2:27 am
I have experimented with installing various versions of Linux on the Fit-PC 2i and keep having the same problem; which is I end up with no video moments after proceeding from GRUB, before anything is displayed. This includes Linux Mint 13, which this site has install instructions for.
This is more basic than an issue with X-Windows. The same thing happens with a console-only installation. The one tweak I’ve found that allows for working video is to prevent the gma500_gfx driver from loading by adding a “gma500_gfx.dummy=1” parameter to the kernel boot line. I’d rather be able to use the proper driver than fall back on the generic VESA driver though.
My monitor’s native resolution is 1920x1200 and this is my only guess as to what could be different from other people’s cases. I’ve tried many forms of forcing a conservative resolution at boot time to no avail (e.g., using GRUB_GFXMODE and GRUB_GFXPAYLOAD_LINUX=1024x768, etc.). Also, I can’t tell for sure from reading other people’s experiences, but it seems they end up with a non-native resolution in cases their display isn’t in the built-in resolution table rather than getting no video signal.
Note: my machine has the latest 9/24/10 BIOS, 1G of RAM; and the machine isn’t crashing completely, I can SSH to it when it’s finished booting.
Any idea what is going on here?
This is more basic than an issue with X-Windows. The same thing happens with a console-only installation. The one tweak I’ve found that allows for working video is to prevent the gma500_gfx driver from loading by adding a “gma500_gfx.dummy=1” parameter to the kernel boot line. I’d rather be able to use the proper driver than fall back on the generic VESA driver though.
My monitor’s native resolution is 1920x1200 and this is my only guess as to what could be different from other people’s cases. I’ve tried many forms of forcing a conservative resolution at boot time to no avail (e.g., using GRUB_GFXMODE and GRUB_GFXPAYLOAD_LINUX=1024x768, etc.). Also, I can’t tell for sure from reading other people’s experiences, but it seems they end up with a non-native resolution in cases their display isn’t in the built-in resolution table rather than getting no video signal.
Note: my machine has the latest 9/24/10 BIOS, 1G of RAM; and the machine isn’t crashing completely, I can SSH to it when it’s finished booting.
Any idea what is going on here?