Try with linux-lts with its headers
3 core/linux-lts-headers 6.12.12-1 (26.7 MiB 136.1 MiB)
Headers and scripts for building modules for the LTS Linux kernel
2 core/linux-lts-docs 6.12.12-1 (26.0 MiB 216.4 MiB)
Documentation for the LTS Linux kernel
1 core/linux-lts 6.12.12-1 (137.7 MiB 137.9 MiB)
The LTS Linux kernel and modules
==> Packages to install (eg: 1 2 3, 1-3 or ^4)
==> 1 2 3
Sync Explicit (3): linux-lts-6.12.12-1, linux-lts-docs-6.12.12-1, linux-lts-headers-6.12.12-1
Ok got that installed, do I need to somehow tell EOS to boot that instead of what I currently have loaded?
I believe if youāre using grub
in a typical configuration, then yes, you would select the lts (long term stable) kernel shortly upon your machine rebooting.
Iāve had issues with broadcom-wl in the past where Iād have to reinstall with fresh headers each time I update the kernel on a certain machine (iMac 2019). My understanding is that the -dkms version was supposed to help avoid this. (Apparently itās not fully ready for prime time )
Pinned post at top of forum.
broadcom-wl-dkms is also broken it seems.
but should be resolved soon.
There was a report already, but the package is still not working
Everyone having such hardware should be aware of non working wifi
@garrafa
There is an issue with broadcom on the current kernel. It does work on the lts kernel. If you are using grub and you install the lts kernel and run the update grub command it will be listed in advanced when you boot along with the current kernel but it should automatically boot on lts as the first entry.
Edit: Only the broadcom-wl-dkms is available now as broadcom-wl has been removed from the Arch repo. This has been pinned on the top of the topics page. But there is an issue on latest kernel where the module isnāt loading therefore no WiFi.
This is strange, I donāt see it listed post POST. Let me figure out if I need to hit something on that list to see the other kernels installed.
If you click on the hamburger menu and click on topics itās pinned right at the top. This is just referring to the broadcom-wl package being removed from the repo and only the dkms version being available.
Broadcom is working now on the latest kernel with updated broadcom-wl-dkms
package
Version : 6.30.223.271-41
Oh no, I meant the new lts kernel.
The new yay update picked up on broadcom 41, the version available yesterday was 39.
rafa@EndeavourOS ~$ yay -Q | grep broadcom
broadcom-wl-dkms 6.30.223.271-39
rafa@EndeavourOS ~$ yay
[sudo] password for rafa:
:: Synchronizing package databases...
endeavouros is up to date
core is up to date
extra 7.5 MiB 442 KiB/s 00:17 [------------------------------------------------------------] 100%
multilib is up to date
:: Searching AUR for updates...
:: Searching databases for updates...
:: 6 packages to upgrade/install.
6 extra/broadcom-wl-dkms 6.30.223.271-39 -> 6.30.223.271-41
Ok so, the internal broadcom wifi adapter is now working, I am not sure if itās the combination of having the lts kernel installed and the most recent update of the dkms module from -39 to -41.
What do you guys think?
I ended up with this setup after installing and removing:
Name : linux
Version : 6.13.1.arch1-1
Description : The Linux kernel and modules
Architecture : x86_64
URL : https://github.com/archlinux/linux
Licenses : GPL-2.0-only
Groups : None
Provides : KSMBD-MODULE VIRTUALBOX-GUEST-MODULES WIREGUARD-MODULE
Depends On : coreutils initramfs kmod
Optional Deps : linux-firmware: firmware images needed for some devices [installed]
scx-scheds: to use sched-ext schedulers
wireless-regdb: to set the correct wireless channels of your country
Required By : b43-firmware
Name : broadcom-wl-dkms
URL : https://www.broadcom.com/site-search?filters[pages][content_type][values][]=Downloads&q=802.11%20linux%20sta%20wireless%20driver
Conflicts With : broadcom-wl
Required By : broadcom-wl-dkms
Name : b43-firmware
URL : https://wireless.wiki.kernel.org/en/users/Drivers/b43
Conflicts With : b43-firmware-classic
Required By : b43-firmware
No ⦠itās the new updated package why it now works on the current kernel.
Yup, the LTS kernel has nothing to do with the driver working with the default kernel.
Anyway, the LTS kernel is good to keep in the system in case the default kernel gets an update that is problematic to some driver.
How do you trigger this to launch? I installed it but in the grub menu, I don“t see it. It must be added to the grub list or something?
You have to run the grub update command if you are using grub?
sudo grub-mkconfig -o /boot/grub/grub.cfg
Then it will add it to boot but you donāt see it unless you go into advanced in the grub menu. It should automatically boot lts unless you go into advanced and select the current kernel.
If you have grub installed, then you can use the command mentioned by @ricklinux .
By default EndeavourOS will install systemd-boot instead of grub.
First, please show the output of command
pacman -Q grub
No grub installed.
Seems to be systemd:
rafa@EndeavourOS etc$ pacman -Q systemd
systemd 257.2-2
I donāt think that exactly tells you that it is systemd-boot. I use grub and systemd is on every system.
ex:
[ricklinux@rick-ms7c37 ~]$ pacman -Q systemd
systemd 257.2-2
[ricklinux@rick-ms7c37 ~]$
If you do ls / , do you see boot or efi ?