Video only comes up in 640x480

**sudodus** · October 26th, 2015

Sometimes it helps to uncomment, in other words remove the # character, from the line

Code:

#GRUB_TERMINAL=console

in the /etc/default/grub file.

Code:

sudo nano /etc/default/grub

Change, save, and run the command

Code:

sudo update-grub

See this link for more details

/etc/default/grub

**Icculus** · October 30th, 2015

So I have tried pretty much EVERYTHING at this point. I'd like to confirm my diagnosis.

I have been able to start my machine using Nouveau in full resolution. This is both on 15.04 and now 15.10.
I was having issues with Nouveau when I started this thread. This was due to the bumblebee drivers being installed.
I have tried some drivers that lead to login loops. I have tried some that lead to seemingly dead systems.
I have had Nvidia drivers that allow me to get to the point where I can enter my password via SSH, but then I received no prompt.
I tried to boot into my ancient Windows 7 partition that, last I know, worked fine. I see the opening screen, but then when it should be going to a login, I get "HDMI No Signal" on my monitor.

To me all signs are pointing to hardware. As a software engineer, I feel that is a cop-out, but it really seems to be the case. I haven't looked yet, but if there is a way to explicitly test this I'd appreciate any advice before I go out and spend a couple hundred bucks on a new video card that may or may not solve the problem.

Any thoughts? Is it possible I have a busted video card that still works with the standard drivers but not with the Nvidia ones because the damaged portion of the video card isn't being used? I don't boot into Windows at all anymore, but last I tried (maybe 6 months ago) everything was working fine there.

**sudodus** · October 30th, 2015

It is rather easy to test the RAM (if you can boot into a live drive in BIOS mode: Select memtest.

It is rather easy to check the S.M.A.R.T. status of the internal drive. Use Disks (gnome-disks). Install it if it is not yet installed.

You can check the file system including bad blocks with the following command (when booted from a live drive),

Code:

sudo e2fsck -cf /dev/sdxy

where x is the drive letter and y is the partition number.

If the power supply unit is failing, it might deliver too low voltage, which can cause various problems.

If there is too much dust inside the computer, it might get overheated, which can cause various problems. (Your problems do not look like they are caused by overheating, but who knows.)

But it can be difficult to identify problems with the motherboard.

**Icculus** · October 30th, 2015

Welp... in a last ditch effort I went to the DVI cable instead of HDMI and all seems to be working at this point.

Ugh.... that was two weeks of headache. At least I have basically a speedy and new OS partition. No clue what is going on with Windows 7, but I'm not worrying about it.

Thanks for the help and more importantly, hopefully this can help someone else.