|
6.5.15-2 Fails to boot.
I think the issue is something simple, but I am really lazy. I just loaded up Synaptic and removed the packages.
First off is the mandatory $ inxi -bGxxz :: Code :: System:
Kernel: 6.4.15-2-liquorix-amd64 arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 wm: xfwm dm: LightDM Distro: MX-23_ahs_x64 Libretto July 31 2023 base: Debian GNU/Linux 12 (bookworm) Machine: Type: Desktop System: Gigabyte product: B450 AORUS PRO WIFI v: N/A serial: <superuser required> Mobo: Gigabyte model: B450 AORUS PRO WIFI-CF v: x.x serial: <superuser required> BIOS: American Megatrends LLC. v: F61 date: 07/13/2021 CPU: Info: 8-core AMD Ryzen 7 3700X [MT MCP] arch: Zen 2 speed (MHz): avg: 2278 min/max: 2200/4426 Graphics: Device-1: NVIDIA GP106 [GeForce GTX 1060 6GB] vendor: eVga.com. driver: nvidia v: 525.125.06 arch: Pascal pcie: speed: 8 GT/s lanes: 16 bus-ID: 07:00.0 chip-ID: 10de:1c03 Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.18.0 driver: X: loaded: nvidia gpu: nvidia display-ID: :0.0 screens: 1 Screen-1: 0 s-res: 3840x2160 s-dpi: 96 Monitor-1: HDMI-0 res: 3840x2160 dpi: 140 diag: 801mm (31.54") API: OpenGL v: 4.6.0 NVIDIA 525.125.06 renderer: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 direct-render: Yes Network: Device-1: Intel I211 Gigabit Network vendor: Gigabyte driver: igb v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 04:00.0 chip-ID: 8086:1539 Device-2: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi v: kernel pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 05:00.0 chip-ID: 8086:24fb Drives: Local Storage: total: 931.51 GiB used: 719.41 GiB (77.2%) Info: Processes: 368 Uptime: 38m Memory: 31.29 GiB used: 3.03 GiB (9.7%) Init: SysVinit v: 3.06 runlevel: 5 default: graphical Compilers: gcc: 12.2.0 alt: 12 Packages: 2514 pm: dpkg pkgs: 2504 pm: flatpak pkgs: 10 Shell: Bash v: 5.2.15 running-in: xfce4-terminal inxi: 3.3.26 Upon following the install script, it generates a bunch of errors. Most are unimportant things about unsigned packages. I for one do not care about that at all. The following is the output if I run the install script as it is. :: Code :: $ curl -s 'https://liquorix.net/install-liquorix.sh' | sudo bash
[INFO ] Possible distributions: debian Hit:1 http://deb.debian.org/debian bookworm-updates InRelease Hit:2 http://deb.debian.org/debian bookworm InRelease Hit:3 http://deb.debian.org/debian bookworm-backports InRelease Hit:7 http://security.debian.org/debian-security bookworm-security InRelease Hit:8 http://eddie.website/repository/apt stable InRelease Hit:5 https://cdn.liquorix.net/debian bookworm InRelease Get:4 https://mxrepo.com/mx/repo bookworm InRelease [19.8 kB] Hit:6 https://mxrepo.com/mx/testrepo bookworm InRelease Get:9 https://mxrepo.com/mx/repo bookworm/main i386 Packages [146 kB] Get:10 https://mxrepo.com/mx/repo bookworm/main amd64 Packages [148 kB] Fetched 314 kB in 1s (254 kB/s) Reading package lists... Done Reading package lists... Done Building dependency tree... Done Reading state information... Done curl is already the newest version (7.88.1-10+deb12u1). gpg is already the newest version (2.2.40-1.1). ca-certificates is already the newest version (20230311). 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 3441 100 3441 0 0 17995 0 --:--:-- --:--:-- --:--:-- 18015 [INFO ] Liquorix keyring added to /etc/apt/keyrings/liquorix-keyring.gpg Reading package lists... Done Building dependency tree... Done Reading state information... Done apt-transport-https is already the newest version (2.6.1). lsb-release is already the newest version (12.0-1). 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. Hit:1 http://deb.debian.org/debian bookworm-updates InRelease Hit:2 http://deb.debian.org/debian bookworm InRelease Hit:5 http://deb.debian.org/debian bookworm-backports InRelease Hit:7 http://security.debian.org/debian-security bookworm-security InRelease Hit:8 http://eddie.website/repository/apt stable InRelease Hit:3 https://cdn.liquorix.net/debian bookworm InRelease Hit:4 https://mxrepo.com/mx/repo bookworm InRelease Hit:6 https://mxrepo.com/mx/testrepo bookworm InRelease Reading package lists... Done [INFO ] Liquorix repository added successfully to /etc/apt/sources.list.d/liquorix.list Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: linux-headers-6.5.15-2-liquorix-amd64 linux-image-6.5.15-2-liquorix-amd64 Suggested packages: linux-doc-6.5 crda The following NEW packages will be installed: linux-headers-6.5.15-2-liquorix-amd64 linux-headers-liquorix-amd64 linux-image-6.5.15-2-liquorix-amd64 linux-image-liquorix-amd64 0 upgraded, 4 newly installed, 0 to remove and 1 not upgraded. Need to get 0 B/90.1 MB of archives. After this operation, 563 MB of additional disk space will be used. Selecting previously unselected package linux-headers-6.5.15-2-liquorix-amd64. (Reading database ... 329221 files and directories currently installed.) Preparing to unpack .../linux-headers-6.5.15-2-liquorix-amd64_6.5-1.1~bookworm_amd64.deb ... Unpacking linux-headers-6.5.15-2-liquorix-amd64 (6.5-1.1~bookworm) ... Selecting previously unselected package linux-image-6.5.15-2-liquorix-amd64. Preparing to unpack .../linux-image-6.5.15-2-liquorix-amd64_6.5-1.1~bookworm_amd64.deb ... Unpacking linux-image-6.5.15-2-liquorix-amd64 (6.5-1.1~bookworm) ... Selecting previously unselected package linux-headers-liquorix-amd64. Preparing to unpack .../linux-headers-liquorix-amd64_6.5-1.1~bookworm_amd64.deb ... Unpacking linux-headers-liquorix-amd64 (6.5-1.1~bookworm) ... Selecting previously unselected package linux-image-liquorix-amd64. Preparing to unpack .../linux-image-liquorix-amd64_6.5-1.1~bookworm_amd64.deb ... Unpacking linux-image-liquorix-amd64 (6.5-1.1~bookworm) ... Setting up linux-image-6.5.15-2-liquorix-amd64 (6.5-1.1~bookworm) ... I: /vmlinuz.old is now a symlink to boot/vmlinuz-6.4.15-2-liquorix-amd64 I: /initrd.img.old is now a symlink to boot/initrd.img-6.4.15-2-liquorix-amd64 I: /vmlinuz is now a symlink to boot/vmlinuz-6.5.15-2-liquorix-amd64 I: /initrd.img is now a symlink to boot/initrd.img-6.5.15-2-liquorix-amd64 /etc/kernel/postinst.d/dkms: dkms: running auto installation service for kernel 6.5.15-2-liquorix-amd64. /usr/sbin/dkms.mx autoinstall --kernelver 6.5.15-2-liquorix-amd64 Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20230504/source/dkms.conf) Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20230504/source/dkms.conf) Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20230504/source/dkms.conf) Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20230504/source/dkms.conf) Sign command: /lib/modules/6.5.15-2-liquorix-amd64/build/scripts/sign-file Binary /lib/modules/6.5.15-2-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed Building module: Cleaning build area... ./dkms-make.sh..... Cleaning build area... 8812au.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.5.15-2-liquorix-amd64/updates/dkms/ depmod... Sign command: /lib/modules/6.5.15-2-liquorix-amd64/build/scripts/sign-file Binary /lib/modules/6.5.15-2-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed Building module: Cleaning build area... make -j16 KERNELRELEASE=6.5.15-2-liquorix-amd64 KVER=6.5.15-2-liquorix-amd64... Cleaning build area... wl.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.5.15-2-liquorix-amd64/updates/dkms/ depmod... Sign command: /lib/modules/6.5.15-2-liquorix-amd64/build/scripts/sign-file Binary /lib/modules/6.5.15-2-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed Building module: Cleaning build area... env NV_VERBOSE=1 make -j16 modules KERNEL_UNAME=6.5.15-2-liquorix-amd64.......(bad exit status: 2) Error! Bad return status for module build on kernel: 6.5.15-2-liquorix-amd64 (x86_64) Consult /var/lib/dkms/nvidia-current/525.125.06/build/make.log for more information. Sign command: /lib/modules/6.5.15-2-liquorix-amd64/build/scripts/sign-file Binary /lib/modules/6.5.15-2-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20230504/source/dkms.conf) Building module: Cleaning build area... 'make' -j16 KVER=6.5.15-2-liquorix-amd64 USER_MODULE_NAME=rtl8821ce CONFIG_RTW_DEBUG=n...... Cleaning build area... rtl8821ce.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.5.15-2-liquorix-amd64/updates/dkms/ depmod... Sign command: /lib/modules/6.5.15-2-liquorix-amd64/build/scripts/sign-file Binary /lib/modules/6.5.15-2-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed Warning: The /var/lib/dkms/rtl8821cu/5.12.0/6.5.15-2-liquorix-amd64/x86_64/dkms.conf for module rtl8821cu includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch/config. This indicates that it should not be built. Skipping... Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. dkms: autoinstall for kernel: 6.5.15-2-liquorix-amd64 failed! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: error processing package linux-image-6.5.15-2-liquorix-amd64 (--configure): installed linux-image-6.5.15-2-liquorix-amd64 package post-installation script subprocess returned error exit status 1 Setting up linux-headers-6.5.15-2-liquorix-amd64 (6.5-1.1~bookworm) ... /etc/kernel/header_postinst.d/dkms: dkms: running auto installation service for kernel 6.5.15-2-liquorix-amd64. /usr/sbin/dkms.mx autoinstall --kernelver 6.5.15-2-liquorix-amd64 Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20230504/source/dkms.conf) Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20230504/source/dkms.conf) Deprecated feature: MODULES_CONF (/var/lib/dkms/rtl8821ce/5.5.2.1+git20230504/source/dkms.conf) Sign command: /lib/modules/6.5.15-2-liquorix-amd64/build/scripts/sign-file Binary /lib/modules/6.5.15-2-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed Building module: Cleaning build area... env NV_VERBOSE=1 make -j16 modules KERNEL_UNAME=6.5.15-2-liquorix-amd64.......(bad exit status: 2) Error! Bad return status for module build on kernel: 6.5.15-2-liquorix-amd64 (x86_64) Consult /var/lib/dkms/nvidia-current/525.125.06/build/make.log for more information. Sign command: /lib/modules/6.5.15-2-liquorix-amd64/build/scripts/sign-file Binary /lib/modules/6.5.15-2-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed Warning: The /var/lib/dkms/rtl8821cu/5.12.0/6.5.15-2-liquorix-amd64/x86_64/dkms.conf for module rtl8821cu includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch/config. This indicates that it should not be built. Skipping... Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. dkms: autoinstall for kernel: 6.5.15-2-liquorix-amd64 failed! run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11 Failed to process /etc/kernel/header_postinst.d at /var/lib/dpkg/info/linux-headers-6.5.15-2-liquorix-amd64.postinst line 11. dpkg: error processing package linux-headers-6.5.15-2-liquorix-amd64 (--configure): installed linux-headers-6.5.15-2-liquorix-amd64 package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of linux-headers-liquorix-amd64: linux-headers-liquorix-amd64 depends on linux-headers-6.5.15-2-liquorix-amd64 (= 6.5-1.1~bookworm); however: Package linux-headers-6.5.15-2-liquorix-amd64 is not configured yet. dpkg: error processing package linux-headers-liquorix-amd64 (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of linux-image-liquorix-amd64: linux-image-liquorix-amd64 depends on linux-image-6.5.15-2-liquorix-amd64 (= 6.5-1.1~bookworm); however: Package linux-image-6.5.15-2-liquorix-amd64 is not configured yet. dpkg: error processing package linux-image-liquorix-amd64 (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: linux-image-6.5.15-2-liquorix-amd64 linux-headers-6.5.15-2-liquorix-amd64 linux-headers-liquorix-amd64 linux-image-liquorix-amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) Finally that is all done. I am not even going to try fixing this. But I bet this will be easy as pie for most of the regulars, and perhaps the install script can be edited to help lazy people like myself? If not, I will just be happy in 6.4.15-2. Thanks in advance. Have a nice day everyone. Back to top |
|||||
|
I looked up the package rtl8821cu and found this.
https://www.realtek.com/en/products/communications-network-ics/item/rtl8821cu It is a Wifi driver. I finally fired up Synaptic and looked for the rtl8821cu package. It showed me this. "rtl8821cu driver in DKMS format, builds up to 5.17 kernels." So I completely removed it. I have had 6.2 upon install of this OS, so it was never able to use this old garbage. And I use Ethernet anyway. However, it still fails. I have no idea how I am intended to configure "linux-image-6.5.15-2-liquorix-amd64". Back to top |
|||||
|
:: Code :: 525.125.06that driver doesn't support 6.5 kernel as far as I know, you can't run current kernels with old nvidia non free drivers. Sometimes you can't run new kernels with new nvidia drivers, but that's not as common as it used to be. So despite your laziness, you will have to either give up on running current kernels, or learn how to install current nvidia drivers, and run non in tree kernel modules. They are well into the 535 series by now on the current branch for nvidia. And only the latest ones support 6.4 and 6.5 kernels as far as I know, but I don't pretend to follow this stuff closely anymore. However, you were energetic enough to read the how to post issues, which saves some steps. The rt build failure may actually be a resolvable issue, unless the module was not building on 6.5 kernel. Really, if you want to run non in tree modules, you're better off sticking to the distro packaged kernel and calling it a day. That's the lazy way to do it, it works well. Or use Liquorix AND use in tree kernel modules, that works very well too. Or stay about 1 major version behind with liquorix, that doesn't work as well, but tends to give you a little buffer space for various drivers to catch up. But you can't run older nvidia drivers with liquorix, period, you have to run the current ones to have any hope of it working over time. Back to top |
|||||
|
Thank you for the quick reply. I am thinking of switching to another distro for the future anyway. (Artix XFCE with OpenRC.) So I may get around most of these issues in favor of a better possible future install state. The issues with MX tying DKMS that should be a post install thing, directly to the Kernel itself is a big problem, and I see no evidence they are going to fix that.
In addition, the install script was just updated for Artix. So now would be a good time to switch over and get used to Pacman. For the moment, I will look into doing a manual install of the newer Nvidia drivers. Thank you again for pointing me in the right direction. Back to top |
|||||
|
Yep, this is a bug with MX Linux. Here's another thread where a foreign script part of MX interferes with the installation of Liquorix by bundling the result of a DKMS install with the package: techpatterns.com/forums/about3033.html
That's completely wrong, a DKMS module failing to build doesn't mean the kernel itself failed to install. :: Quote :: Thank you for the quick reply. I am thinking of switching to another distro for the future anyway. (Artix XFCE with OpenRC.) So I may get around most of these issues in favor of a better possible future install state. The issues with MX tying DKMS that should be a post install thing, directly to the Kernel itself is a big problem, and I see no evidence they are going to fix that.
In addition, the install script was just updated for Artix. So now would be a good time to switch over and get used to Pacman. I agree, if you like running enthusiast kernels, or at least the latest greatest, an Arch based distro is the right way to go. I personally run Arch on all my systems and never have issues with DKMS. Broken DKMS packages are usually fixed in 24-48 hours in the rare case they aren't updated before a major kernel update. Back to top |
|||||
|
Thank you each for the replies.
And since the issue is not actually anything with Liquorix, it is fair to mark this as resolved. One thing I would ask of the Arch users, is there a cheat sheet of some sort? I installed Artix last night. But then I am left with a very lean build and no idea how to use it. I could not find a list of commands for Pacman, and even as I bumbled around attempting the basic functions it offers, I could not find the name of any package I would have installed/updated. I can only theorize that Artix is meant to be used by a person with multiple computers working concurrently, and a few resources I could not find. So as sad as I am to admit it, I reinstalled MX 23. At least I know how to find and install the packages I use daily. The first step to getting Artix usable would be getting the Nvidia driver installed. But doing that was made all but impossible without secret magic phrases to kill off the X server in a hundred different ways, while leaving the terminal working. What a train wreck. So I am back on MX running an older Kernel than the newest, because MX is slow to change and my old hardware would not benefit as much from a newer Kernel. Back to top |
|||||
|
:: Quote :: One thing I would ask of the Arch users, is there a cheat sheet of some sort? I installed Artix last night. But then I am left with a very lean build and no idea how to use it. I could not find a list of commands for Pacman, and even as I bumbled around attempting the basic functions it offers, I could not find the name of any package I would have installed/updated.
I can only theorize that Artix is meant to be used by a person with multiple computers working concurrently, and a few resources I could not find. So as sad as I am to admit it, I reinstalled MX 23. At least I know how to find and install the packages I use daily. As far as I can tell, Artix is just an anti-systemd variation of Arch with choices of preconfigured desktop environments. Now whether the experience is superior to Endeavour or RebornOS, no idea. I'm personally a fan of EndeavourOS as it filled in the void of Antergos rather well, but YMMV. But for cheat sheets, you should probably try installing Arch and configuring it yourself with the installation guide: wiki.archlinux.org/title/Installation_guide. This will properly familiarize yourself with the distribution and all the common activities you'll perform on CLI. Once you're comfortable, jumping to a distro based on Arch will just be a point of convenience with tasteful defaults. Skipping this step will leave you without experience with the basics of operating an Arch system, which is probably what happened to you. EDIT: If you like Debian, Siduction is a great choice based off of testing: siduction.org. That's the last Debian based distribution I seriously used and I currently mirror their repos and ISOs as part of my appreciation of their efforts and community: liquorix.net/siduction Back to top |
|||||
|
Awesome. I will probably give Siduction a try.
Also, if anyone thinks he linked in a page that does not exist, remove the period from the end of the Installation Guide link. It is a simple and understandable error. One day, I will probably try moving to Arch, and I will do as you suggest. I am trying to switch off of systemd as the init system, not because I dislike it, but because I have never tried anything that does not have the monolithic init system that half of the Internet hates beyond words. Moving on. I am currently back on MX, polishing this distro and getting things as I like. Mostly wasted effort, but it is based upon Debian 12, and I use the XFCE version. And when I move to Siduction, much of what I am teaching myself will be almost identical. So I am thinking of this as practice. Artix is still in the future for me. But I may try to put it off until I can afford the currently $260 USD I will need to buy a Radeon RX 7600. Then I can finally forget all the Nvidia driver nightmares that seem to be a daily occurrence. As always, thanks for the reply. And I do appreciate the links. Have a nice day everyone. Back to top |
|||||
|
Not sure if it's related or not, but was 6.5.15 built and released by mistake? 6.5.3 is currently the latest 6.5 kernel.
Back to top |
|||||
|
:: Bopp wrote :: Not sure if it's related or not, but was 6.5.15 built and released by mistake? 6.5.3 is currently the latest 6.5 kernel.Yes, that was my mistake. The latest package is the correct version. You'll need to manually remove the previous package to the correct version ordered in GRUB. Updates will still proceed like normal since the package version (not the kernel version), always starts with -1 and increments once per update, rather than following the version of the software. Back to top |
|||||
|
All times are GMT - 8 Hours
|
|||||