3

I work with Ubuntu now for over 2 years, but now I have a problem that the automatic installer installed kernel 4.13.0-37 and after that the boot procedures were not completed.

I can see the normal boot output messages, but then it switches to a black blank screen with a mouse cursor (which cannot move).

So maybe there is a problem in starting the desktop manager?

I tried also to install 4.13.0-38, same problems.

4.13.0.-36 works fine.

As I do not know which further information (e.g. from syslog) is needed, please ask.

My setup: X86 with i5-3570 cpu and Ubuntu version 17.04 with Mate desktop

Update:

Now I removed the microcode to go back to:

[    1.835022] microcode: sig=0x306a9, pf=0x2, revision=0x15
[    1.851062] microcode: Microcode Update Driver: v2.2.

Then reboot to 4.13.0-38 was successful!

After switching back to new microcode it fails again:

[    0.000000] microcode: microcode updated early to revision 0x1c, date = 2015-02-26
[    0.752400] microcode: sig=0x306a9, pf=0x2, revision=0x1c
[    0.752550] microcode: Microcode Update Driver: v2.2.

Btw, 0x1c seems to be the newest kernel driver offered by Ubuntu appgrid. According to the list from Intel it should be 0x1f. Strange..

Improve this question
10
  • Perhaps this is a far fetched explanation but I strongly advise you to re-download the the 3 deb files responsible for 4.13.0-38 - the two deb packages containing the headers + the image file and do this twice in two different directories. Then when done, run crc32 against each file including the one that gives you issues. Are you getting the same hash values? The aim is to check if the downloaded files are downloaded correctly.
    – marko
    Apr 4, 2018 at 9:24
  • I can do this, but I do not think that both versions -37 and -38 were corrupt. I always do an upgrade from official (Ubuntu) sources.
    – Pete 77877
    Apr 4, 2018 at 9:46
  • Yeah I agree, I realized that after I posted my response and the other thing I failed to consider before I typed was whether you are using the Software Updater or installing deb files manually. Sorry.
    – marko
    Apr 4, 2018 at 9:49
  • No problem, any hints are welcome ;-)
    – Pete 77877
    Apr 4, 2018 at 9:52
  • 1
    This problem is probably related to the following bugs: bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920 bugs.launchpad.net/ubuntu/+source/xorg/+bug/1761121
    – maiseb
    Apr 4, 2018 at 19:05

0

Reset to default

You must log in to answer this question.

Browse other questions tagged .