Welcome!
Important information
-- Information on torrent hosting changes
-- Information on MX15/16 GPG Keys
-- Spectre and Meltdown vulnerabilities

News
-- Introducing our new Website
-- MX Linux on social media: here

Current releases
-- MX-18.1 Point Release release info here
-- Migration Information to MX-18 here
-- antiX-17.4 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

[Resolved] ]missing microcode after Liquorix kernel update

Report Bugs, Issues and non- pacakage Requests
cinclus
Forum Novice
Forum  Novice
Posts: 35
Joined: Sun Mar 13, 2016 5:35 am

Success! Re: missing microcode after Liquorix kernel update

#21

Post by cinclus » Sat Jan 05, 2019 6:28 pm

Only from the rebuilt Liquorix 18.20 kernel I got a working MX-18 booting this kernel: installed und live (after making a MX-Snapshot).

And only old-style rebuilding the Linux 4.18 source patched with Liquorix v4.18.20-lqx2.patch.gz applied and its corresponding config.i386-pae using make, make modules_install and make install commands were successful.

The chaotic debian style instructions I found in the net for doing the same task were of no avail.

User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 18349
Joined: Fri Dec 15, 2006 8:07 pm

Re: [Resolved] ]missing microcode after Liquorix kernel update

#22

Post by Stevo » Sat Jan 05, 2019 11:00 pm

We use the standard Debian packaging tools to rebuild the Liquorix kernel from its sources. That way, the patches in debian/patches are automatically applied.

Quick way: install packaging tools from the Package Installer.

Put the debian folder into the main extracted orig tarball, then open a terminal in that source folder and run

Code: Select all

sudo /usr/lib/pbuilder/pbuilder-satisfydepends && debuild -uc -us -jauto
This will install all the build-depends and then build the kernel packages with all the cores you have available. If your machine runs hot, you can replace "auto" with the lower number of threads you want to use instead. It needs a few GiB of free space for the build. If you make any changes in /debian, you'll probably have to run the build command twice, as the first one regenerates many of the files in /debian from your changes.

The Debian kernel build is similar in broad scope, but is more complicated in detail. For example, it needs over 40 GiB of free space for the build! And it will automatically use all your cores by default; there's a different command to limit those (-J<number of cores desired>) Patches are still in debian/patches, and are still applied as listed in debian/patches/series.

cinclus
Forum Novice
Forum  Novice
Posts: 35
Joined: Sun Mar 13, 2016 5:35 am

Re: [Resolved] ]missing microcode after Liquorix kernel update

#23

Post by cinclus » Fri Jan 11, 2019 11:21 am

@Stevo
If I want to rebuild a Liquorix kernel for say an old Atom netbook only, I can optimize config-arch-32 for this architecture. But how can I then build a kernel suppressing the kernel-building referring to config-arch-32-pae and config-arch-64? Simply removing them in /usr/src/linux-4.18/debian/config/kernelarch-x86/ yields an error.

User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 18349
Joined: Fri Dec 15, 2006 8:07 pm

Re: [Resolved] ]missing microcode after Liquorix kernel update

#24

Post by Stevo » Fri Jan 11, 2019 5:02 pm

I cross-compile the 32-bit versions of Liquorix on 64-bit using pbuilder, but that's a bit harder to set up, or you could try sbuild. You could also have the openSUSE Build Service build your special version; I wrote a guide here on how to start using it.

However, are you going to gain any more than one or two percent speed increase on that netbook?

cinclus
Forum Novice
Forum  Novice
Posts: 35
Joined: Sun Mar 13, 2016 5:35 am

Re: [Resolved] ]missing microcode after Liquorix kernel update

#25

Post by cinclus » Sat Jan 12, 2019 4:16 pm

Now I rebuild 32-Bit Liquorix 4.18-kernels from these kernel-sources, please see

http://download.opensuse.org/repositori ... ebian_9.0/

using unaltered kernel configurations: config-arch-32, config-arch-32-pae respectively and Stevos build-instructions.

Booting (initvsys or systemd) any of the resulting two kernels hang with a blank screen.

Whereas, please see above, booting into the kernels, built directly from the original patched Liquorix 4.18 source, using the patch
https://liquorix.net/sources/v4.18.20-lqx2.patch.gz

and the kernel configurations
https://liquorix.net/sources/4.18/config.i386
https://liquorix.net/sources/4.18/config.i386-pae
respectively, works as expected.

User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 18349
Joined: Fri Dec 15, 2006 8:07 pm

Re: [Resolved] ]missing microcode after Liquorix kernel update

#26

Post by Stevo » Sat Jan 12, 2019 4:35 pm

Hmmm, the kernel and header debs you are building are exactly the same as the ones in my original OBS repository?

I'm not sure exactly what's going on now--are both the original packages and your cloned rebuilds booting to blank screens? That is what I would expect if they are exactly the same.

cinclus
Forum Novice
Forum  Novice
Posts: 35
Joined: Sun Mar 13, 2016 5:35 am

Re: [Resolved] ]missing microcode after Liquorix kernel update

#27

Post by cinclus » Sat Jan 12, 2019 5:50 pm

My cloned (rebuilt, non-working) kernel-debs:

linux-image-4.18.0-20.3-liquorix-686-pae_4.18-28~obs_i386.deb
linux-image-4.18.0-20.3-liquorix-686_4.18-28~obs_i386.deb

linux-headers-4.18.0-20.3-liquorix-686-pae_4.18-28~obs_i386.deb
linux-headers-4.18.0-20.3-liquorix-686_4.18-28~obs_i386.deb

I have now removed the above debs and replaced by these equivalent(?) debs from testrepo:

http://ftp.halifax.rwth-aachen.de/mxlin ... -liquorix/

linux-image-4.18.0-20.3-liquorix-686_4.18-28~mx17+1_i386.deb
linux-image-4.18.0-20.3-liquorix-686-pae_4.18-28~mx17+1_i386.deb

linux-headers-4.18.0-20.3-liquorix-686_4.18-28~mx17+1_i386.deb
linux-headers-4.18.0-20.3-liquorix-686-pae_4.18-28~mx17+1_i386.deb

with same results: nothing boots.

cinclus
Forum Novice
Forum  Novice
Posts: 35
Joined: Sun Mar 13, 2016 5:35 am

Re: [Resolved] ]missing microcode after Liquorix kernel update

#28

Post by cinclus » Sat Jan 19, 2019 10:57 am

These failing kernels all hang showing at first only a blinking cursor but after about 60s this message appears:

Code: Select all

Failed to execute /init (error -8)
Starting init: /sbin/init exists but couldn't execute it (error -8)
Starting init: /bin/sh exists but couldn't execute it (error -8)
Kernel panic - not syncing: No working init found.  Try passing init= option to
kernel. See Linux Docunentation/adnin-guide/init.rst for guidance.
CPU: 0 PID: l Comm: MuQSS/0 Not tainted 4.18.0-20.3-liquorix-686-pae #l liquorix
 4.18-28˜mxl7+l
Hardware name: ASUS All Series/H97M-PLUS, BIOS 2603 02/22/2016
Call Trace:
 dump_stack+0x63/0x8d
 panic+0xd0/0x229
 ? printk+0x3e/0x46
 kernel_init+0x1e0/0x250
 ? rest_init+0xd0/0xd0
 ret_from_fork+0x35/0x40
Kernel Offset: disabled
---[ end Kernel panic - not syncing: No working init found.  Try passing init= o
ption to kernel. See Linux Documentation/admin-guide/init.rst for guidance. ]---

User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 18349
Joined: Fri Dec 15, 2006 8:07 pm

Re: [Resolved] ]missing microcode after Liquorix kernel update

#29

Post by Stevo » Sat Jan 19, 2019 3:50 pm

See Linux Documentation/admin-guide/init.rst for guidance
That file's in the kernel source, and here's what it says:
Explaining the dreaded "No init found." boot hang message
=========================================================

OK, so you've got this pretty unintuitive message (currently located
in init/main.c) and are wondering what the H*** went wrong.
Some high-level reasons for failure (listed roughly in order of execution)
to load the init binary are:

A) Unable to mount root FS
B) init binary doesn't exist on rootfs
C) broken console device
D) binary exists but dependencies not available
E) binary cannot be loaded

Detailed explanations:

A) Set "debug" kernel parameter (in bootloader config file or CONFIG_CMDLINE)
to get more detailed kernel messages.
B) make sure you have the correct root FS type
(and ``root=`` kernel parameter points to the correct partition),
required drivers such as storage hardware (such as SCSI or USB!)
and filesystem (ext3, jffs2 etc.) are builtin (alternatively as modules,
to be pre-loaded by an initrd)
C) Possibly a conflict in ``console= setup`` --> initial console unavailable.
E.g. some serial consoles are unreliable due to serial IRQ issues (e.g.
missing interrupt-based configuration).
Try using a different ``console= device`` or e.g. ``netconsole=``.
D) e.g. required library dependencies of the init binary such as
``/lib/ld-linux.so.2`` missing or broken. Use
``readelf -d <INIT>|grep NEEDED`` to find out which libraries are required.
E) make sure the binary's architecture matches your hardware.
E.g. i386 vs. x86_64 mismatch, or trying to load x86 on ARM hardware.
In case you tried loading a non-binary file here (shell script?),
you should make sure that the script specifies an interpreter in its shebang
header line (``#!/...``) that is fully working (including its library
dependencies). And before tackling scripts, better first test a simple
non-script binary such as ``/bin/sh`` and confirm its successful execution.
To find out more, add code ``to init/main.c`` to display kernel_execve()s
return values.

Please extend this explanation whenever you find new failure causes
(after all loading the init binary is a CRITICAL and hard transition step
which needs to be made as painless as possible), then submit patch to LKML.
Further TODOs:

- Implement the various ``run_init_process()`` invocations via a struct array
which can then store the ``kernel_execve()`` result value and on failure
log it all by iterating over **all** results (very important usability fix).
- try to make the implementation itself more helpful in general,
e.g. by providing additional error messages at affected places.

Andreas Mohr <andi at lisas period de>
So it's probably because it can't mount the root file system.

As a workaround, have you thought about remastering the ISO with the Liquorix kernel added and using that for your Live USB?

cinclus
Forum Novice
Forum  Novice
Posts: 35
Joined: Sun Mar 13, 2016 5:35 am

Re: [Resolved] ]missing microcode after Liquorix kernel update

#30

Post by cinclus » Sat Jan 19, 2019 9:58 pm

Stevo wrote:
Sat Jan 19, 2019 3:50 pm
See Linux Documentation/admin-guide/init.rst for guidance
So it's probably because it can't mount the root file system.

Code: Select all

Kernel panic - not syncing: No working init found.  Try passing init= option to
kernel.
I found no information where to put an option "init=..." and what value(s) to try.
As a workaround, have you thought about remastering the ISO with the Liquorix kernel added and using that for your Live USB?
In #21 and #25 I was not clear enough about the fact that I had already remastered the ISO with the working Liquorix kernel built with the Liquorix patch https://liquorix.net/sources/v4.18.20-lqx2.patch.gz. And this remastered ISO boots live very well with this kernel.

But - please see above - none of the Liquorix 4.18.20 32-Bit kernels rebuilt from the mentioned sources on http://download.opensuse.org/repositori ... ebian_9.0/ work. And none of the Liquorix 4.18.20 32-Bit kernels from the mx-testrepo work as well.

As I understand the cause of failure of the kernels built from the opensuse sources are the added patches besides the patch https://liquorix.net/sources/v4.18.20-lqx2.patch.gz.

Post Reply

Return to “Bugs and Non-Package Requests Forum”