Quote:
Originally Posted by Gregg Bell
Thanks rjb. I am going to let this sort of roll for a while. I don't have a way of testing the RAM, and I don't have the Smart control to test the hard drive. The way I see it now, it's possible but very unlikely that the RAM or the hard drive are the issues.
|
(Traveling since last Wednesday, and playing catchup...)
I don't think this is a hardware problem. You report that when you boot the system, you do see the BIOS stuff, so the monitor works and the PC is talking to it.
You see a blank screen when Ubuntu is coming up, but that simply means nothing is being sent to the monitor. It doesn't mean nothing is happening at all.
You report that if you wait long enough, Ubuntu
does come up and appears to operate normally. This is another indicator against a hardware problem.
The question is precisely what is going on in the period between when you boot the system and when Ubuntu is ready for use.
The place to check that sort of thing is in /var/log/syslog. Ubuntu records its status, and that's where the records are kept. It sounds a lot to me like there's a problem in the video configuration, Ubuntu is trying to use it the way it had been configured, failing, and eventually giving up and using a generic default. The question is what the configuration had been, why it fails after a 15.10->16.04 upgrade, and the best fix to apply. If what Ubuntu comes up with when it
does[ display suits you, the fix might be "Use the generic default".
I
don't think the bug report you referenced has anything to do with this. That report concerns a confusing error message about weak cryptographic signing, but if you read the thread, it appears that updates
are in fact downloaded and applied. The error message is a warning, not an indication of failure.
______
Dennis