System76 Serval WS - "Regular" and AHS Versions Major Intallation Problem [Solved]

[lhb1142]

hmmm. I didn't remember setting up auto-kernel updates on 23.4. They might well be, I'm checking. If so that is a mistake on my part.

when you rebooted the last time and lost wifi, did you try booting back into the previous kernel?

I'm afraid I wouldn't know how to do that.

Lawrence

[dolphin_oracle]

Code: Select all

sudo apt remove linux-image-liquorix-amd64 linux-headers-liquorix-amd64

this will not remove the kernel, just stop updates.

alternatively, you can disable kernel updates in mx tweak on the "other" tab.

[Stevo]

You can choose which kernel in the first GRUB menu screen that appears when you boot up, in the Advanced Options, on an installed system. It won't be there on a Live session.

You can also choose a nonsystemd or systemd boot for each kernel there, so that's another option to try if nothing else works.

[lhb1142]

Code: Select all

sudo apt remove linux-image-liquorix-amd64 linux-headers-liquorix-amd64

alternatively, you can disable kernel updates in mx tweak on the "other" tab.

I did this. AFTER I did this, I saw that the MX Updater was "green" and I updated, accepting everything. Unfortunately, when I rebooted, the Wi-Fi was GONE, just like all the other times. (I wonder if the disabling of kernel updates in MX Tweak came too late to prevent a complete updating via the MX Updater.)

But I'm going to try reinstalling (for the fifth or sixth time), disabling kernel updates in MX Tweak (as you instructed), and then updating (using sudo apt update && sudo apt upgrade). I hope this works. I'll let everyone know, probably tomorrow.

I do thank everyone who has tried to help me. I have NEVER had such an installation problem on ANY of the computers on which I have installed MX Linux previously. Installation and updating was always smooth and perfect. This is the first time this has ever happened to any computer on which I have installed MX Linux (and I hope it's the last!).

AND I hope that this can be fixed.

Lawrence

[dolphin_oracle]

Code: Select all

sudo apt remove linux-image-liquorix-amd64 linux-headers-liquorix-amd64

alternatively, you can disable kernel updates in mx tweak on the "other" tab.

I did this. AFTER I did this, I saw that the MX Updater was "green" and I updated, accepting everything. Unfortunately, when I rebooted, the Wi-Fi was GONE, just like all the other times. (I wonder if the disabling of kernel updates in MX Tweak came too late to prevent a complete updating via the MX Updater.)

But I'm going to try reinstalling (for the fifth or sixth time), disabling kernel updates in MX Tweak (as you instructed), and then updating (using sudo apt update && sudo apt upgrade). I hope this works. I'll let everyone know, probably tomorrow.

I do thank everyone who has tried to help me. I have NEVER had such an installation problem on ANY of the computers on which I have installed MX Linux previously. Installation and updating was always smooth and perfect. This is the first time this has ever happened to any computer on which I have installed MX Linux (and I hope it's the last!).

AND I hope that this can be fixed.

Lawrence

looking at the apt history, or uname -a even, will tell you if the kernel updated or not. I suspect not.

and since there was no firmware, its worth checking rfkill output to see how its affected.

Code: Select all

rfkill list all

[Stevo]

Since you can also get a Net connection without wi-fi, it could help to get a QSI of when it's not working, to see if we can spot any difference.

It would help if you made a personal snapshot after the install, but before any updates; that way you can just reinstall from that if need be, instead of from square one every time.

An alternative to that could be to try a Timeshift backup and restore of your system.

[lhb1142]

Code: Select all

sudo apt remove linux-image-liquorix-amd64 linux-headers-liquorix-amd64

this will not remove the kernel, just stop updates.

alternatively, you can disable kernel updates in mx tweak on the "other" tab.

Hooray, Hooray! It's fixed! I did a complete reinstallation of MX Linux 23.4 AHS, I connected to my Wi-Fi (as i had been able to do before) and then, without doing anything else, I just disabled the kernel updates in MX Tweak as you suggested, I then rebooted the computer, and THEN I updated it.

When I restarted the computer (holding my breath), the Wi-Fi was still functioning!

Now the only thing I have to do besides configuring the computer and adding my data from my previous one, is to find out how to add a BIOS password (which is something I like though I suppose it isn't 100% necessary); for that of course I'll have to contact System76.

As I mentioned I have some configuring to do (to get the computer to look the way I like it) but I'll do that this weekend (we're quite busy today).

I want to SINCERELY THANK EVERYONE WHO RESPONDED TO ME and especially to "dolphin-oracle" who gave me the instructions as to how to correct this kernel situation. As I stated above, this is the first time I have ever had a problem insalling MX Linux on ANY computer (and I hope it's the last!).

I am also hoping that, with the release of version 25.x (as always I'll wait until the first updated version is introduced before switching over) that this kernel problem will be eliminated permanently.

THANKS, THANKS AGAIN!

Lawrence

[Kermit the Frog]

The only question is why iwlwifi doesn't get loaded with 6.11 though it's supported by that kernel, too.

In case you install any more recent kernel (for whatever reason) in the future, just remember that you can boot with the 6.10 via "Advanced Options" on Grub (in case of any problems with the new one). In short: 6.10 will stay there unless manually removed by you.

[lhb1142]

Dear "Kermit,"

I am hoping that whatever the problem is, it will be fixed either with either a version 23.5 or the next version 25.x.

I am certain that anyone else buying a System76 computer with specifications similar to mine (see above) will have the same installation problem.

Fortunately, as it turns out, the solution is easy (as is everything in Linux ONCE YOU KNOW HOW TO DO IT!).

Lawrence

[Kermit the Frog]

As you might already know: when everything's fine:

"MX Snapshot" from menu and create your own iso :)