Welcome!
Important information
-- Spectre and Meltdown vulnerabilities

News
-- MX Linux on social media: here
-- Mepis support still here

Current releases
-- MX-18 Final release info here
-- Migration Information to MX-18 here
-- antiX-17.3 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: 27
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: 17556
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: 27
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: 17556
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: 27
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: 17556
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: 27
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.

Post Reply

Return to “Bugs and Non-Package Requests Forum”