C
C
CityCat42018-10-26 08:19:14
linux
CityCat4, 2018-10-26 08:19:14

What happened to kernel 4.18?

And what is so fatal happened to the 4.18 bucket, why is it stupidly not loaded on a machine on which 4.14.52 is loaded with a bang?
A few days ago I put a bucket of 4.18.14 on a test car, but still have not rebooted. I reboot and ... oops - the wheelbarrow hangs after the inscription Loading initial ramdisk, that is, after the initrd command has worked.

Answer the question

In order to leave comments, you need to log in

3 answer(s)
S
Scan-4, 2018-10-26
@Scan-4

There is such a problem now only on x86, on the x86_64 architecture it is not observed. Roll back to the old. And I note - the trend towards x86 architecture is no longer in vogue. At the dawn of IT, there is a 64 architecture, and support for 32-bit is receding into the summer.

V
Vladimir, 2018-10-26
@MechanID

I have 4.18.14 CHOST="x86_64-pc-linux-gnu" flight is normal, do you have self-collected kernel or genkernnel?

C
CityCat4, 2018-11-01
@CityCat4

I answer myself.
All by itself was solved by installing bucket 4.18.16, despite the fact that it is not marked as stable in portage.

# uname -a
Linux calcds17 4.18.16-calculate #1 SMP PREEMPT Thu Nov 1 11:28:11 +07 2018 x86_64 Intel(R) Xeon(R) CPU E5-2620 v4 @ 2.10GHz GenuineIntel GNU/Linux

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question