View Single Post
Old 05-14-2016, 02:38 PM   #669
Gregg Bell
Gregg Bell
Gregg Bell ought to be getting tired of karma fortunes by now.Gregg Bell ought to be getting tired of karma fortunes by now.Gregg Bell ought to be getting tired of karma fortunes by now.Gregg Bell ought to be getting tired of karma fortunes by now.Gregg Bell ought to be getting tired of karma fortunes by now.Gregg Bell ought to be getting tired of karma fortunes by now.Gregg Bell ought to be getting tired of karma fortunes by now.Gregg Bell ought to be getting tired of karma fortunes by now.Gregg Bell ought to be getting tired of karma fortunes by now.Gregg Bell ought to be getting tired of karma fortunes by now.Gregg Bell ought to be getting tired of karma fortunes by now.
 
Gregg Bell's Avatar
 
Posts: 2,266
Karma: 3917598
Join Date: Jan 2013
Location: Itasca, Illinois
Device: Kindle Touch 7, Sony PRS300, Fire HD8 Tablet
Quote:
Originally Posted by DMcCunney View Post
(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
Thanks Dennis. I don't think it's a hardware or a bug issue either. I've tried (with help) a million things. (Fixing packages, blah blah blah) And we only made it worse. Now I can only boot through the GRUB and only to the 15.10 kernel. And even that is screwed up--it will only boot when GRUB is set at:

GRUB_DEFAULT=4

even though the 4 does not correspond to the 15.10 kernel

I gave up. Now the plan (granted, it's not much of a plan) is to just wait for October to roll around and upgrade to 16.10 and hope that fixes it somehow. (Like I said it's not much of a plan.)

I've been in the Ubuntu forum and a lot of people are having delayed booting issues with the upgrade from 15.10 to 16.04LTS.

Right now the computer works great using the 15.10 kernel. So I'm leaving well enough alone. (This is my work computer and it would be a major hassle to lose it.)
Gregg Bell is offline   Reply With Quote