[Resolved] ]missing microcode after Liquorix kernel update

Report Bugs, Issues and non- package Requests
Message
Author
cinclus
Posts: 103
Joined: Sun Mar 13, 2016 5:35 am

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

#31 Post by cinclus »

cinclus wrote: Sat Jan 19, 2019 9:58 pm 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.
I could not confirm this by rebuilding the 32-Bit kernels from the sources from http://download.opensuse.org/repositori ... ebian_9.0/, viz without using the added patches in debian/patches/:

Code: Select all

debian/version.patch
debian/uname-version-timestamp.patch
debian/kernelvariables.patch
The resulting kernels hang as well on booting.

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

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

#32 Post by cinclus »

Now I liked to know the outcome of an old-style rebuilding of the Liquorix 4.18 kernel patched with patches all contained in the file linux-liquorix_4.18-28~obs.debian.tar.xz and mentioned there in the file debian/patches/series:

v4.18.20-lqx2.patch
version.patch
uname-version-timestamp.patch
kernelvariables.patch

The resulting kernel works perfectly well in an MX-18 installation and in a live-remastered MX-18-live-system (32-Bit non-pae version).

System info from the live-system:
> inxi -bx

Code: Select all

]System:    Host: mx1 Kernel: 4.18.20-lqx2 i686 bits: 32 compiler: gcc v: 6.3.0 
           Desktop: Xfce 4.12.3 Distro: MX-18_386 Continuum Dec 20  2018 
           base: Debian GNU/Linux 9 (stretch) 
Machine:   Type: Desktop System: ASUS product: All Series v: N/A serial: <root required> 
           Mobo: ASUSTeK model: H97M-PLUS v: Rev X.0x serial: <root required> 
           UEFI [Legacy]: American Megatrends v: 2603 date: 02/22/2016 
CPU:       Quad Core: Intel Core i5-4590S type: MCP arch: Haswell speed: 944 MHz 
           min/max: 800/3001 MHz 
Graphics:  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
           vendor: ASUSTeK driver: i915 v: kernel bus ID: 00:02.0 
           Display: x11 server: X.Org 1.19.2 driver: modesetting unloaded: fbdev,vesa 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: Mesa DRI Intel Haswell Desktop x86/MMX/SSE2 v: 4.5 Mesa 18.2.6 
           direct render: Yes 
Network:   Device-1: Intel Ethernet I218-V vendor: ASUSTeK driver: e1000e v: 3.2.6-k port: f080 
           bus ID: 00:19.0 
Drives:    Local Storage: total: 1.95 TiB used: 620.59 GiB (31.1%) 
Info:      Processes: 215 Uptime: 1m Memory: 3.33 GiB used: 302.5 MiB (8.9%) Init: SysVinit 
           runlevel: 5 Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12 inxi: 3.0.29 [/code

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

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

#33 Post by cinclus »

Summary: How I got finally working Debian 32-Bit-kernel-packages for my Intel-hardware platforms: H97 and G45 w/ nvidia graphics card.

I used these source files from:

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

linux-liquorix_4.18.orig.tar.xz
linux-liquorix_4.18-28~obs.debian.tar.xz

From the latter I used

1. for kernel configuration (.config):

debian/config/kernelarch-x86/config-arch-32-pae
(or debian/config/kernelarch-x86/config-arch-32)

2. the kernel-patches:

debian/patches/zen/v4.18.20-lqx2.patch

debian/patches/debian/version.patch

debian/patches/debian/uname-version-timestamp.patch

debian/patches/debian/kernelvariables.patch

3. build command:

Code: Select all

root@mx1:/usr/src/linux-4.18# make deb-pkg
[...]
root@mx1:/usr/src/linux-4.18# ls ../*.deb
 ../linux-headers-4.18.20-lqx2_4.18.20-lqx2-1_i386.deb
 ../linux-libc-dev_4.18.20-lqx2-1_i386.deb
 ../linux-image-4.18.20-lqx2_4.18.20-lqx2-1_i386.deb
For detailed steps to setup the patched kernel source I refer to Raphaël Hertzog/Roland Mas,chapter 8.10.

The kernel works on my hardware in a local MX18 installation and as a usb-live system.

Reference: Raphaël Hertzog and Roland Mas: The Debian Administrator’s Handbook 2015, online:
http://debian-handbook.info

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

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

#34 Post by cinclus »

My method to build a Liquorix-kernel working in my hardware environment (H97 mainboard) seems so far to generally work with any of the available Liquorix-source-packages on https://github.com/damentz/liquorix-package/releases

My instructions above to build special-purpose Debian liquorix-kernel-packages started with a kernel-source and a liquorix-package from Stevos OpenSuse-site
http://download.opensuse.org/repositori ... ebian_9.0/

Now there is another method to get kernel-packages based on Damentz' Liquorix-patches. The essential difference to my previous instructions is to use the quilt command for patching the kernel.

1) download a liquorix-package of your choice “liquorix-package-(4|5).x-y[z].tar.gz” from

https://github.com/damentz/liquorix-package/releases

and a kernel-source “linux-(4|5).x.tar.xz“ from

kernel.org

N.B.: digits 4|5.x in the name of the chosen liquorix-package must match the ones of in the name of the kernel source!.

2) copy the subdirectory-tree “patches” contained in the (unpacked) liquorix-package to
the top-level-directory of the kernel source-tree.

3) install the quilt-package,

4) cd to the top level of the kernel-source-tree,

5) for kernel configuration rename debian/config/kernelarch-x86/config-arch-32-pae
(or debian/config/kernelarch-x86/config-arch-32) to .config and copy it to the top level directory of the kernel-source tree

6) patch the kernel source simply by

Code: Select all

root@mx1:/usr/src/linux-5.0# quilt push –a
7) and built again the kernel-packages by

Code: Select all

root@mx1:/usr/src/linux-5.0# make [-j x] deb-pkg
–j x switch is for using x cpu-kernels for parallel make.
Last edited by cinclus on Tue Mar 10, 2020 5:11 am, edited 1 time in total.

User avatar
Stevo
Developer
Posts: 12776
Joined: Fri Dec 15, 2006 8:07 pm

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

#35 Post by Stevo »

That seems to be exactly the same thing that building it the Debian way with the packaging toolset does, except a lot more work.

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

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

#36 Post by cinclus »

Stevo wrote: Fri Jul 19, 2019 9:57 pm That seems to be exactly the same thing that building it the Debian way with the packaging toolset does, except a lot more work.
Not at all as I have shown, please look again into the discussion following #22. The results were negative with your method.
The essential difference is that I only use the patch-subtree of the liquorix-packages.

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

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

#37 Post by cinclus »

... continuing #34.

Required packages: flex, bison, libssl-dev, quilt.

Example: MX 18.3:
linux-5.1.tar.xz
liquorix-package-5.1-24.zip

Works!

Example: MX 19.1:
same sources, same packages, same configuration.

Fails with following error:

Code: Select all

alt_user@mxalt:~/kernel/linux-5.1 time make oldconfig -j 4 deb-pkg LOCALVERSION=-mx19
...
LD [M]  sound/usb/usx2y/snd-usb-usx2y.ko
  LD [M]  sound/x86/snd-hdmi-lpe-audio.ko
  LD [M]  sound/xen/snd_xen_front.ko
  LD [M]  virt/lib/irqbypass.ko
make[3]: *** [debian/rules:6: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
make[2]: *** [scripts/package/Makefile:74: deb-pkg] Error 2
make[1]: *** [Makefile:1417: deb-pkg] Error 2
make: *** [Makefile:312: __build_one_by_one] Error 2

real	35m5.078s
user	120m24.513s
sys	9m56.167s

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

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

#38 Post by cinclus »

I have repeated the results from above (MX 18.3 32-Bit, MX 19.1 32-Bit) but this time with different versions of gcc.

I built the same the same kernel as above on MX 18.3 - before with gcc-6 (default) - now with gcc-7 (from testing-repo)
and on MX 19.1 - before with gcc-8 (default) - now with gcc-7 (from main repo).

So I have factored out the role of different gcc versions.

But it comes as a surprise that:

The liquorix 5.1 32-Bit kernel again builds successful with gcc-7 under MX 18.3.
but fails again under MX 19.1 with the same error under gcc-7 as before with gcc-8.

Question: are there other hidden factors in the build environment on the different MX platforms?

Post Reply

Return to “Bugs and Non-Package Requests Forum”