Black screen after update

**2CV67** · June 12th, 2019

Thanks cruzer001, but I can only run the "ubuntu-bug linux" code in kernel .142 as there is no screen in the problem kernels .145 & .150.
So Apport never sees anything about the problem!

The procedure for reporting a bug directly on Launchpad is way beyond me...

**cruzer001** · June 12th, 2019

The procedure for reporting a bug directly on Launchpad is way beyond me...

I always thought of it as simple when using terminal. Needed information will be bundled and auto sent to launchpad and you have a few questions to answer. Thats it, you do need a launchpad account.

I would of thought you could of gone to console (ctrl+alt+f1) with the troubled kernel, but your choice.

Later

**2CV67** · June 14th, 2019

Originally Posted by cruzer001

I would of thought you could of gone to console (ctrl+alt+f1) with the troubled kernel, but your choice.

Thanks, but it was not my choice!
As I said in post #7 - Ctrl+Alt+F1=black screen so can't do anything.
Same for Ctrl+Alt+F2-12...

**Rubi1200** · June 14th, 2019

You can also report bugs directly online (you may need to create an account):
https://bugs.launchpad.net/ubuntu/

**2CV67** · June 14th, 2019

Yes, I already have an account, but I usually found the process too complicated.

I will try again...

**Rubi1200** · June 14th, 2019

I must admit I have never reported a bug on Launchpad. However, it might be worthwhile doing so in this case if you have the time and inclination to do so.

**2CV67** · June 14th, 2019

Reported bug:
https://bugs.launchpad.net/ubuntu/+bug/1832863

While there, I saw a recommendation to update BIOS before reporting kernel bugs, but I don't dare to try that yet...

**topoignaz** · October 27th, 2019

After updating from kernel 4.4.0.142 to 4.4.0.148, I experience exactly the same issue described by the OP on my EeePC 1005HA.

Please do not deprecate netbook hardware: after their big outcome between 2008 and 2013, their production was discontinued without any real replacement, many people are still using them.

**2CV67** · November 22nd, 2019

I wiped my Ubuntu partition & installed Lubuntu 18.04.3 instead.
It is working perfectly with latest kernels.

Call this SOLVED, though without finding the reason...