Won't boot on 6.14.1-1-liquorix-amd64 kernel panic [Solved]
Re: Won't boot on 6.14.1-1-liquorix-amd64 kernel panic
The 6.14 Liquorix kernel provides much improved internal drivers for all the Realtek chipsets except 8814AU, which will be added in 6.15. So those DKMS packages are being updated to not build on 6.14. There's a pretty easy way to get the 6.15 drivers on pretty much any older kernel by downloading. making, and installing rtw88-dkms and rtw89-dkms from morrownd's Github. The drivers built in just a few seconds on my machine, which is much faster than the set of old rtl DKMS drivers we ship.
MXPI = MX Package Installer
QSI = Quick System Info from menu
The MX Test repository is mostly backports; not the same as Debian testing
QSI = Quick System Info from menu
The MX Test repository is mostly backports; not the same as Debian testing
Re: Won't boot on 6.14.1-1-liquorix-amd64 kernel panic
I'd like to give a try to those files you mention, sadly can't find those on github... can you link those or giving a url to them? 

Re: Won't boot on 6.14.1-1-liquorix-amd64 kernel panic
Hi @Stevo ,
"Again, a dkms build failure of a deprecrated DKMS package, that you don't even use, is not a kernel panic. A kernel panic is something you see in the dmesg output, and it provides a memory trace for debugging."
"A kernel panic is something you see in the dmesg output, and it provides a memory trace for debugging."
OK. Better phrasing: The failed boot had something about "kernel panic" as screen output.
I was claiming nothing. I know nothing.
"...deprecated DKMS package that you don't even use,"
Even? I didn't officially ask for them to be in there.
... Anyway, I could remove the offending packages and try out 6.14.1-1, if I knew how, or not.
My habit is to let the MX provided kernels install, and not complain.
Thanks tonnes!
Jim
"Again, a dkms build failure of a deprecrated DKMS package, that you don't even use, is not a kernel panic. A kernel panic is something you see in the dmesg output, and it provides a memory trace for debugging."
"A kernel panic is something you see in the dmesg output, and it provides a memory trace for debugging."
OK. Better phrasing: The failed boot had something about "kernel panic" as screen output.
I was claiming nothing. I know nothing.
"...deprecated DKMS package that you don't even use,"
Even? I didn't officially ask for them to be in there.
... Anyway, I could remove the offending packages and try out 6.14.1-1, if I knew how, or not.
My habit is to let the MX provided kernels install, and not complain.
Thanks tonnes!
Jim
Thanks for being there!
Re: Won't boot on 6.14.1-1-liquorix-amd64 kernel panic
It's because of all kinds definitions on what certain text mean and or do with all text computer languages is the reason why I struggle learning these languages and that because I have been incapable learning these text computer languages I actually despise them because of the many times I have bricked my computer that required a full reformat and full re-installation due to my lack of knowledge that I could never understand these text languages. I find it great for those that understand all these text and look up to these people who have become successfully knowledgeable on them. Anyone who is a knowledgeable expert on working with computers should be able to understand my feelings are about working with text on computers because it can really mess things up by entering the wrong commands due to my lack of knowledge in those areas. I don't want this to make it look as criticism from me on these text methods of operating computers. This is one of the many reasons why I back up my data on my computers which these backups saved me countless times.DukeComposed wrote: Thu Apr 10, 2025 5:07 pmStephen Bourne wrote the shell for 7th Edition Unix, called the Bourne Shell. When Bash was developed ten years later as an improvement on the Bourne shell, the pun was too good to pass up.
I will take your word for it. Thank you for the clarification on what bash means.

I am command line illiterate.
I copy & paste to the terminal. Liars, Wiseguys, Trolls, and those without manners will be added to my ignore list. 


Re: Won't boot on 6.14.1-1-liquorix-amd64 kernel panic
While I no longer have any issues I am curious about your post and respect your great knowledge.Stevo wrote: Thu Apr 10, 2025 6:32 pmSorry...but how can we blame the kernel for not being compatible with a 550 Nvidia driver that's not in our repositories? That's not a kernel panic, just a build failure, but I know cutting and pasting real kernel "oopsies" can be a problem.Code: Select all
Error! Bad return status for module build on kernel: 6.14.1-1-liquorix-amd64 (x86_64) Consult /var/lib/dkms/nvidia-current/550.144.03/build/make.log for more information.
I think everyone should remove unused wi-fi DKMS drivers. They really slow down any kernel update, for no reason. The 6.14 Liquorix kernel seems have much improved internal Realtek drivers, for those that are wondering what good it is.
For those that don't want to provide any QSI or system information--using a third-party driver that won't build on a new kernel is something we wasted time discovering.
Are you referring to my computer or someone else's?
There issues come down to: 1) In my case I don't use Nvidia since I built my computer with AMD hardware to try to ovoid any Nvidia issues that are reported all over the Internet. I have no knowledge of Nvidia issues since I don't use Nvidia hardware. 2) My computer has never lied to me before and I have no reason to believe that is wrong when my monitor said kernel panic.
You recommend that "I think everyone should remove unused wi-fi DKMS drivers". How would this be accomplished?
Thank you very much for sharing your knowledge Stevo.

I am command line illiterate.
I copy & paste to the terminal. Liars, Wiseguys, Trolls, and those without manners will be added to my ignore list. 


Re: Won't boot on 6.14.1-1-liquorix-amd64 kernel panic
Take a look at MX Cleanup in MX Tools. In it's Removal tool section the "Remove unused WiFi drivers" button.Mauser wrote: Fri Apr 11, 2025 12:15 pm ...You recommend that "I think everyone should remove unused wi-fi DKMS drivers". How would this be accomplished? ...
Re: Won't boot on 6.14.1-1-liquorix-amd64 kernel panic
Thank you. This information help me and others.kmathern wrote: Fri Apr 11, 2025 12:48 pmTake a look at MX Cleanup in MX Tools. In it's Removal tool section the "Remove unused WiFi drivers" button.Mauser wrote: Fri Apr 11, 2025 12:15 pm ...You recommend that "I think everyone should remove unused wi-fi DKMS drivers". How would this be accomplished? ...

I am command line illiterate.
I copy & paste to the terminal. Liars, Wiseguys, Trolls, and those without manners will be added to my ignore list. 


- DukeComposed
- Posts: 1396
- Joined: Thu Mar 16, 2023 1:57 pm
Re: Won't boot on 6.14.1-1-liquorix-amd64 kernel panic
Bear in mind that back in the 1970s, text methods were the only methods to operate computers. Even today modern Linuxes like MX are still designed to work like those ancient servers were, with an added graphics layer applied on top. We've come a long way in terms of speed, performance, and user interfaces like the Windows 95 start button or Apple's trash bin that have shaped the way we think about how a modern desktop should look and feel. Performance is important here because drawing graphics is computationally expensive, while text is relatively computationally cheap. Despite these advances, the low-level UNIX-like architecture is still there and shells are not going to go away any time soon.Mauser wrote: Fri Apr 11, 2025 11:56 am I don't want this to make it look as criticism from me on these text methods of operating computers.
"MX Cleanup > Removal Tool > Remove unused WiFi drivers" ought to do it.Mauser wrote: Fri Apr 11, 2025 12:15 pm You recommend that "I think everyone should remove unused wi-fi DKMS drivers". How would this be accomplished?
Re: Won't boot on 6.14.1-1-liquorix-amd64 kernel panic
kmathern in post #36 already stated that.DukeComposed wrote: Fri Apr 11, 2025 12:59 pmBear in mind that back in the 1970s, text methods were the only methods to operate computers. Even today modern Linuxes like MX are still designed to work like those ancient servers were, with an added graphics layer applied on top. We've come a long way in terms of speed, performance, and user interfaces like the Windows 95 start button or Apple's trash bin that have shaped the way we think about how a modern desktop should look and feel. Performance is important here because drawing graphics is computationally expensive, while text is relatively computationally cheap. Despite these advances, the low-level UNIX-like architecture is still there and shells are not going to go away any time soon.Mauser wrote: Fri Apr 11, 2025 11:56 am I don't want this to make it look as criticism from me on these text methods of operating computers.
"MX Cleanup > Removal Tool > Remove unused WiFi drivers" ought to do it.Mauser wrote: Fri Apr 11, 2025 12:15 pm You recommend that "I think everyone should remove unused wi-fi DKMS drivers". How would this be accomplished?
I am command line illiterate.
I copy & paste to the terminal. Liars, Wiseguys, Trolls, and those without manners will be added to my ignore list. 


- DukeComposed
- Posts: 1396
- Joined: Thu Mar 16, 2023 1:57 pm
Re: Won't boot on 6.14.1-1-liquorix-amd64 kernel panic
kmathern wrote: Fri Apr 11, 2025 12:48 pm Take a look at MX Cleanup in MX Tools. In it's Removal tool section the "Remove unused WiFi drivers" button.
1744390753 - 1744390125 = 628DukeComposed wrote: Fri Apr 11, 2025 12:59 pm "MX Cleanup > Removal Tool > Remove unused WiFi drivers" ought to do it.
You don't say.