Liquorix 5.18 build into MX Stable?

Forum rules
Post Reply
Message
Author
User avatar
AVLinux
Posts: 3189
Joined: Wed Jul 15, 2020 1:15 am

Liquorix 5.18 build into MX Stable?

#1 Post by AVLinux »

Hi,

No rush, just wondering if a newer than 5.16 Liquorix build could get into MX Stable sometime?

5.16 seemed to have some issues and for ISO builds I reverted to 5.15 but now that 5.18 has been out and MX has a vanilla 5.18 with AHS updates I'm wondering if it's a good time to move from Liquorix 5.15..? I only ask if a newer Liquorix build was in the pipeline anyway, for ISO building and general MX Users who need the lower latency performance for Audio work it is a wonderful thing to have the Liquorix builds in MX Stable with all the accompanying AHS bells and whistles so in any case... Thanks!!
Top
User avatar
Stevo
Developer
Posts: 14878
Joined: Fri Dec 15, 2006 7:07 pm

Re: Liquorix 5.18 build into MX Stable?

#2 Post by Stevo »

It seems like a good idea, now that we've got working DKMS drivers building for the 5.18 kernels. I sent up the last 5.18-21 Liquorix kernel version yesterday, along with the new 5.19-2 kernel. 5.19's staying in testing until we can confirm the same drivers can build on it.
Top
User avatar
AVLinux
Posts: 3189
Joined: Wed Jul 15, 2020 1:15 am

Re: Liquorix 5.18 build into MX Stable?

#3 Post by AVLinux »

Stevo wrote: Mon Aug 22, 2022 4:33 pm It seems like a good idea, now that we've got working DKMS drivers building for the 5.18 kernels. I sent up the last 5.18-21 Liquorix kernel version yesterday, along with the new 5.19-2 kernel. 5.19's staying in testing until we can confirm the same drivers can build on it.
That's great, thanks @Stevo !!
Top
User avatar
wdscharff
Posts: 1147
Joined: Mon Feb 24, 2020 1:07 am

Re: Liquorix 5.18 build into MX Stable?

#4 Post by wdscharff »

Just FYI, USB driver: rtl8821au which was kindly tinkered to my TP-Link Archer T2U PLUS [RTL8821AU] for Liquorix 5.19.0-1.1 and which is now in the AHS repo, does NOT work with the Liquorix 5.19.0-2.1

if it helps you, this is the log for it

Code: Select all

DKMS make.log for 8821au-5.12.5.2 for kernel 5.19.0-2.1-liquorix-amd64 (x86_64)
Di 23. Aug 10:29:18 CEST 2022
make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/5.19.0-2.1-liquorix-amd64/build M=/var/lib/dkms/8821au/5.12.5.2/build  modules
make[1]: Verzeichnis „/usr/src/linux-headers-5.19.0-2.1-liquorix-amd64“ wird betreten
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/rtw_cmd.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/rtw_security.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/rtw_debug.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/rtw_io.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/rtw_ioctl_query.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/rtw_ioctl_set.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/rtw_ieee80211.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/rtw_mlme.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/rtw_mlme_ext.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/rtw_mi.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/rtw_wlan_util.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/rtw_vht.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/rtw_pwrctrl.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/rtw_rf.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/rtw_chplan.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/monitor/rtw_radiotap.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/rtw_recv.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/rtw_sta_mgt.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/rtw_ap.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/wds/rtw_wds.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/mesh/rtw_mesh.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/mesh/rtw_mesh_pathtbl.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/mesh/rtw_mesh_hwmp.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/rtw_xmit.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/rtw_p2p.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/rtw_rson.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/rtw_tdls.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/rtw_br_ext.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/rtw_iol.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/rtw_sreset.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/rtw_btcoex_wifionly.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/rtw_btcoex.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/rtw_beamforming.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/rtw_odm.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/rtw_rm.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/rtw_rm_fsm.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/rtw_ft.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/rtw_wnm.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/rtw_mbo.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/rtw_rm_util.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/efuse/rtw_efuse.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/rtw_roch.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/crypto/aes-internal.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/crypto/aes-internal-enc.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/crypto/aes-gcm.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/crypto/aes-ccm.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/crypto/aes-omac1.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/crypto/ccmp.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/crypto/gcmp.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/crypto/aes-siv.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/crypto/aes-ctr.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/crypto/sha256-internal.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/crypto/sha256.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/crypto/sha256-prf.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/crypto/rtw_crypto_wrap.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/core/rtw_swcrypto.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/os_dep/osdep_service.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/os_dep/linux/os_intfs.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/os_dep/linux/usb_intf.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/os_dep/linux/usb_ops_linux.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/os_dep/linux/ioctl_linux.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/os_dep/linux/xmit_linux.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/os_dep/linux/mlme_linux.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/os_dep/linux/recv_linux.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/os_dep/linux/ioctl_cfg80211.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/os_dep/linux/rtw_cfgvendor.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/os_dep/linux/wifi_regd.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/os_dep/linux/rtw_android.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/os_dep/linux/rtw_proc.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/os_dep/linux/nlrtw.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/os_dep/linux/rtw_rhashtable.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/hal/hal_intf.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/hal/hal_com.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/hal/hal_com_phycfg.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/hal/hal_phy.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/hal/hal_dm.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/hal/hal_dm_acs.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/hal/hal_btcoex_wifionly.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/hal/hal_btcoex.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/hal/hal_mp.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/hal/hal_mcc.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/hal/hal_hci/hal_usb.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/hal/led/hal_led.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/hal/led/hal_usb_led.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/hal/HalPwrSeqCmd.o
/var/lib/dkms/8821au/5.12.5.2/build/os_dep/linux/ioctl_cfg80211.c: In function ‘rtw_cfg80211_ch_switch_notify’:
/var/lib/dkms/8821au/5.12.5.2/build/os_dep/linux/ioctl_cfg80211.c:478:2: error: too few arguments to function ‘cfg80211_ch_switch_notify’
  478 |  cfg80211_ch_switch_notify(adapter->pnetdev, &chdef);
      |  ^~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /var/lib/dkms/8821au/5.12.5.2/build/include/osdep_service_linux.h:98,
                 from /var/lib/dkms/8821au/5.12.5.2/build/include/osdep_service.h:57,
                 from /var/lib/dkms/8821au/5.12.5.2/build/include/drv_types.h:27,
                 from /var/lib/dkms/8821au/5.12.5.2/build/os_dep/linux/ioctl_cfg80211.c:17:
./include/net/cfg80211.h:7967:6: note: declared here
 7967 | void cfg80211_ch_switch_notify(struct net_device *dev,
      |      ^~~~~~~~~~~~~~~~~~~~~~~~~
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/hal/rtl8812a/Hal8812PwrSeq.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/hal/rtl8812a/Hal8821APwrSeq.o
/var/lib/dkms/8821au/5.12.5.2/build/os_dep/linux/ioctl_cfg80211.c: At top level:
/var/lib/dkms/8821au/5.12.5.2/build/os_dep/linux/ioctl_cfg80211.c:10415:13: error: initialization of ‘int (*)(struct wiphy *, struct net_device *, unsigned int)’ from incompatible pointer type ‘int (*)(struct wiphy *, struct net_device *)’ [-Werror=incompatible-pointer-types]
10415 |  .stop_ap = cfg80211_rtw_stop_ap,
      |             ^~~~~~~~~~~~~~~~~~~~
/var/lib/dkms/8821au/5.12.5.2/build/os_dep/linux/ioctl_cfg80211.c:10415:13: note: (near initialization for ‘rtw_cfg80211_ops.stop_ap’)
/var/lib/dkms/8821au/5.12.5.2/build/os_dep/linux/ioctl_cfg80211.c:10459:17: error: initialization of ‘int (*)(struct wiphy *, struct wireless_dev *, unsigned int,  struct cfg80211_chan_def *)’ from incompatible pointer type ‘int (*)(struct wiphy *, struct wireless_dev *, struct cfg80211_chan_def *)’ [-Werror=incompatible-pointer-types]
10459 |  .get_channel = cfg80211_rtw_get_channel,
      |                 ^~~~~~~~~~~~~~~~~~~~~~~~
/var/lib/dkms/8821au/5.12.5.2/build/os_dep/linux/ioctl_cfg80211.c:10459:17: note: (near initialization for ‘rtw_cfg80211_ops.get_channel’)
/var/lib/dkms/8821au/5.12.5.2/build/os_dep/linux/ioctl_cfg80211.c: In function ‘rtw_wdev_unregister’:
/var/lib/dkms/8821au/5.12.5.2/build/os_dep/linux/ioctl_cfg80211.c:10695:10: error: ‘struct wireless_dev’ has no member named ‘current_bss’
10695 |  if (wdev->current_bss) {
      |          ^~
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/hal/rtl8812a/rtl8812a_xmit.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/hal/rtl8812a/rtl8812a_sreset.o
  CC [M]  /var/lib/dkms/8821au/5.12.5.2/build/hal/rtl8812a/rtl8812a_hal_init.o
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:249: /var/lib/dkms/8821au/5.12.5.2/build/os_dep/linux/ioctl_cfg80211.o] Fehler 1
make[2]: *** Es wird auf noch nicht beendete Prozesse gewartet....
make[1]: *** [Makefile:1856: /var/lib/dkms/8821au/5.12.5.2/build] Fehler 2
make[1]: Verzeichnis „/usr/src/linux-headers-5.19.0-2.1-liquorix-amd64“ wird verlassen
make: *** [Makefile:2511: modules] Fehler 2
says nothing to me now, but made sure that I could no longer see a WLAN stick in QSI.
(fortunately I don't do that on my work system ;-} )
my working horse Desktop AMD Ryzen 9 3900x, 32GB Ram // SSD ... enough
mx-fluxbox, what else?

In nature there are neither rewards nor punishments.
There are consequences.

my wallpaper gallery
Top
User avatar
siamhie
Global Moderator
Posts: 3785
Joined: Fri Aug 20, 2021 5:45 pm

Re: Liquorix 5.18 build into MX Stable?

#5 Post by siamhie »

Stevo wrote: Mon Aug 22, 2022 4:33 pm It seems like a good idea, now that we've got working DKMS drivers building for the 5.18 kernels. I sent up the last 5.18-21 Liquorix kernel version yesterday, along with the new 5.19-2 kernel. 5.19's staying in testing until we can confirm the same drivers can build on it.
I couldn't get rtl8814au driver to build on either 5.19 kernel.


5.19.0-2.1-liquorix-amd64

Code: Select all

Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
  rtl8814au-dkms
Preconfiguring packages ...
rtl8814au-dkms failed to preconfigure, with exit status 1
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/1,603 kB of archives.
After this operation, 13.5 MB of additional disk space will be used.
Selecting previously unselected package rtl8814au-dkms.
(Reading database ... 330675 files and directories currently installed.)
Preparing to unpack .../rtl8814au-dkms_5.8.5.1-1~mx21+1_all.deb ...
Unpacking rtl8814au-dkms (5.8.5.1-1~mx21+1) ...
Setting up rtl8814au-dkms (5.8.5.1-1~mx21+1) ...
Loading new rtl8814au-5.8.5.1 DKMS files...
Building for 5.19.0-2.1-liquorix-amd64 6.0.0-rc1
Building initial module for 5.19.0-2.1-liquorix-amd64
Error!  Build of 8814au.ko failed for: 5.19.0-2.1-liquorix-amd64 (x86_64)
Make sure the name of the generated module is correct and at the root of the
build directory, or consult make.log in the build directory
/var/lib/dkms/rtl8814au/5.8.5.1/build/ for more information.
dpkg: error processing package rtl8814au-dkms (--configure):
 installed rtl8814au-dkms package post-installation script subprocess returned error exit status 7
Errors were encountered while processing:
 rtl8814au-dkms
Please wait, creating menu file - stored in /home/siamhie/.fluxbox/submenus/full_menu ...
Menu file created and ready to be used
E: Sub-process /usr/bin/dpkg returned an error code (1)

5.19.0-3.1-liquorix-amd64

Code: Select all

Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
  rtl8814au-dkms
Preconfiguring packages ...
rtl8814au-dkms failed to preconfigure, with exit status 1
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/1,603 kB of archives.
After this operation, 13.5 MB of additional disk space will be used.
Selecting previously unselected package rtl8814au-dkms.
(Reading database ... 330675 files and directories currently installed.)
Preparing to unpack .../rtl8814au-dkms_5.8.5.1-1~mx21+1_all.deb ...
Unpacking rtl8814au-dkms (5.8.5.1-1~mx21+1) ...
Setting up rtl8814au-dkms (5.8.5.1-1~mx21+1) ...
Loading new rtl8814au-5.8.5.1 DKMS files...
Building for 5.19.0-3.1-liquorix-amd64 6.0.0-rc1
Building initial module for 5.19.0-3.1-liquorix-amd64
Error!  Build of 8814au.ko failed for: 5.19.0-3.1-liquorix-amd64 (x86_64)
Make sure the name of the generated module is correct and at the root of the
build directory, or consult make.log in the build directory
/var/lib/dkms/rtl8814au/5.8.5.1/build/ for more information.
dpkg: error processing package rtl8814au-dkms (--configure):
 installed rtl8814au-dkms package post-installation script subprocess returned error exit status 7
Errors were encountered while processing:
 rtl8814au-dkms
Please wait, creating menu file - stored in /home/siamhie/.fluxbox/submenus/full_menu ...
Menu file created and ready to be used
E: Sub-process /usr/bin/dpkg returned an error code (1)
Identical error message from the log.

Code: Select all

DKMS make.log for rtl8814au-5.8.5.1 for kernel 5.19.0-2.1-liquorix-amd64 (x86_64)
Tue 23 Aug 2022 09:18:46 AM PDT
#make -C /lib/modules/5.19.0-2.1-liquorix-amd64/build M=/var/lib/dkms/rtl8814au/5.8.5.1/build clean
cd hal ; rm -fr */*/*/*.mod.c */*/*/*.mod */*/*/*.o */*/*/.*.cmd */*/*/*.ko
cd hal ; rm -fr */*/*.mod.c */*/*.mod */*/*.o */*/.*.cmd */*/*.ko
cd hal ; rm -fr */*.mod.c */*.mod */*.o */.*.cmd */*.ko
cd hal ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
cd core ; rm -fr */*.mod.c */*.mod */*.o */.*.cmd */*.ko
cd core ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
cd os_dep/linux ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
cd os_dep ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
cd platform ; rm -fr *.mod.c *.mod *.o .*.cmd *.ko
rm -fr Module.symvers ; rm -fr Module.markers ; rm -fr modules.order
rm -fr *.mod.c *.mod *.o .*.cmd *.ko *~
rm -fr .tmp_versions
make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/5.19.0-2.1-liquorix-amd64/build M=/var/lib/dkms/rtl8814au/5.8.5.1/build  modules
make[1]: Entering directory '/usr/src/linux-headers-5.19.0-2.1-liquorix-amd64'
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_cmd.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_security.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_debug.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_io.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_ioctl_query.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_ioctl_set.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_ieee80211.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_mlme.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_mlme_ext.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_mi.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_wlan_util.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_vht.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_pwrctrl.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_rf.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_chplan.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_recv.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_sta_mgt.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_ap.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/mesh/rtw_mesh.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/mesh/rtw_mesh_pathtbl.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/mesh/rtw_mesh_hwmp.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_xmit.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_p2p.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_rson.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_tdls.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_br_ext.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_iol.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_sreset.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_btcoex_wifionly.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_btcoex.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_beamforming.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_odm.o
  CC [M]  /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_rm.o
/var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_br_ext.c:20:11: fatal error: net/ipx.h: No such file or directory
   20 |  #include <net/ipx.h>
      |           ^~~~~~~~~~~
compilation terminated.
make[2]: *** [scripts/Makefile.build:249: /var/lib/dkms/rtl8814au/5.8.5.1/build/core/rtw_br_ext.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [Makefile:1856: /var/lib/dkms/rtl8814au/5.8.5.1/build] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-5.19.0-2.1-liquorix-amd64'
make: *** [Makefile:2353: modules] Error 2
This is my Fluxbox . There are many others like it, but this one is mine. My Fluxbox is my best friend. It is my life.
I must master it as I must master my life. Without me, my Fluxbox is useless. Without my Fluxbox, I am useless.
Top
User avatar
herbie
Posts: 33
Joined: Tue Mar 27, 2018 3:13 pm

Re: Liquorix 5.18 build into MX Stable?

#6 Post by herbie »

Maybe I'm not totally with it today, but after seeing all the talk about liquorix kernels I checked on how I implemented the kernel.

curl 'https://liquorix.net/add-liquorix-repo.sh' | sudo bash

was all I did. Got that info from the lIquorix website. Now all I have to do in do updates and get the new kernel when they have it ready.

Did I miss something?
Top
User avatar
AVLinux
Posts: 3189
Joined: Wed Jul 15, 2020 1:15 am

Re: Liquorix 5.18 build into MX Stable?

#7 Post by AVLinux »

herbie wrote: Tue Aug 23, 2022 2:46 pm Maybe I'm not totally with it today, but after seeing all the talk about liquorix kernels I checked on how I implemented the kernel.

curl 'https://liquorix.net/add-liquorix-repo.sh' | sudo bash

was all I did. Got that info from the lIquorix website. Now all I have to do in do updates and get the new kernel when they have it ready.

Did I miss something?
That is adding the separate Liquorix Repository which isn't wrong per se but it is an outside Repo that may occasionally give you such a fresh Liquorix version that Video and Firmware Drivers from MX haven't caught up yet..

The Liquorix builds discussed here are specially re-compiled for the MX Linux native Repos and have some versioning control to ensure they are nicely matched with the 'AHS' firmware and drivers..
Top
Post Reply

Return to “Package Requests - MX-21”