| Git Clone URL: | https://aur.archlinux.org/linux-amd.git (read-only, click to copy) |
|---|---|
| Package Base: | linux-amd |
| Description: | The Linux kernel and modules - With some improvement patches |
| Upstream URL: | https://www.kernel.org/ |
| Licenses: | GPL-2.0-only |
| Provides: | KSMBD-MODULE, VIRTUALBOX-GUEST-MODULES, WIREGUARD-MODULE |
| Replaces: | virtualbox-guest-modules-arch, wireguard-arch |
| Submitter: | None |
| Maintainer: | archdevlab |
| Last Packager: | archdevlab |
| Votes: | 33 |
| Popularity: | 1.19 |
| First Submitted: | 2019-11-10 15:20 (UTC) |
| Last Updated: | 2024-08-21 00:22 (UTC) |
Mentioned patches do not guarantee a 100% workaround as far as I could see. This has yet to be researched, concluded and fixed upstream before I think its worth it for me to make any sort of adoption...
As for now, does spamming this make it work after a few tries? I'm just curious..
rmmod btusb
rmmod btintel
modprobe btintel
modprobe btusb
Just as a reference, Bluetooth is working correctly with linux-zen 5.16.12.zen1-1 and WAS working with previous versions of linux-amd. Maybe it's related to these posts "https://bbs.archlinux.org/viewtopic.php?id=271459" and the problem comes from upstairs.
Regards.
I dont have any Intel BT hardware around afaik, I only see this in the config:
CONFIG_BT_INTEL=m
CONFIG_BT_HCIUART_INTEL=y
It's enabled. That's all I know. Sorry... :-(
@eggz Hi, I'm on the latest kernel (-2) and having a problem with Bluetooth "Bluetooth: hci0: Reading Intel version command failed (-110)"
Are you aware of this? Is there something I can do to solve this problem?
Thank you very much for your time and efforts.
Regards.
I have -3 installed, looks like I just missed the update, ill start a recompile.
Here with gcc version 11.2.0-4 and last linux-amd 5.16.v.12-1 dkms modules are not compiling because of gcc incompatible version.
I am using repository linuxkernels linux-amd build
Yeah it should be present on my kernels, I always check for stuff like that after building, installing and running them aswel.
EDIT, should be fine:
(2/2) Install DKMS modules
==> dkms install --no-depmod px4_drv/r384.7fa9f05 -k 5.16.10-SLIM
==> dkms install --no-depmod px4_drv/r384.7fa9f05 -k 5.16.10-arch1-1
==> dkms install --no-depmod px4_drv/r384.7fa9f05 -k 5.16.10-AMD
==> dkms install --no-depmod px4_drv/r384.7fa9f05 -k 5.16.10-AMD-znver2
==> depmod 5.16.10-SLIM
==> depmod 5.16.10-arch1-1
==> depmod 5.16.10-AMD
==> depmod 5.16.10-AMD-znver2
Oops, does that mean I built the kernel before updating gcc?
@eggz I have the following logs (building px4_drv dkms):
make[1]: Entering directory '/usr/lib/modules/5.16.10-AMD/build'
warning: the compiler differs from the one used to build the kernel
The kernel was built by: gcc (GCC) 11.1.0
You are using: gcc (GCC) 11.2.0
CC [M] /var/lib/dkms/px4_drv/r384.7fa9f05/build/driver/driver_module.o
cc1: error: incompatible gcc/plugin versions
cc1: error: failed to initialize plugin ./scripts/gcc-plugins/stackleak_plugin.so
cc1: error: incompatible gcc/plugin versions
cc1: error: failed to initialize plugin ./scripts/gcc-plugins/structleak_plugin.so
make[2]: *** [scripts/Makefile.build:287: /var/lib/dkms/px4_drv/r384.7fa9f05/build/driver/driver_module.o] Error 1
make[1]: *** [Makefile:1846: /var/lib/dkms/px4_drv/r384.7fa9f05/build/driver] Error 2
make[1]: Leaving directory '/usr/lib/modules/5.16.10-AMD/build'
make: *** [Makefile:19: px4_drv.ko] Error 2
@hina yes, these are the changes:
-CONFIG_CC_VERSION_TEXT="gcc (GCC) 11.1.0"
+CONFIG_CC_VERSION_TEXT="gcc (GCC) 11.2.0"
-CONFIG_GCC_VERSION=110100
+CONFIG_GCC_VERSION=110200
-CONFIG_AS_VERSION=23601
+CONFIG_AS_VERSION=23800
-CONFIG_LD_VERSION=23601
+CONFIG_LD_VERSION=23800
But can you elaborate on what the problem is exactly? All I can see it's enabled:
CONFIG_HAVE_ARCH_STACKLEAK=y
CONFIG_GCC_PLUGIN_STACKLEAK=y
CONFIG_STACKLEAK_TRACK_MIN_SIZE=100
Pinned Comments
archdevlab commented on 2024-08-15 03:38 (UTC)
Hi
I have adopted this package and have updated it!
Thanks!
<deleted-account> commented on 2023-05-04 16:38 (UTC)
GCC13.1 is mainlined in arch, so this means znver4 support can kick off on this kernel. The graysky compile patches have been updated too.
This kernel now natively supports the znver4 arch, but this kernel will most likely keep working on all AMD ryzen hardware. It's better to be able to address certain small perks or issues per architecture now and in the future.
<deleted-account> commented on 2020-10-26 18:15 (UTC)
GCC11.1 is mainlined in arch, so this means znver3 support can kick off on this kernel. The graysky compile patches have been updated too.
This kernel now natively supports the znver3 arch, but this kernel will most likely keep working on all AMD ryzen hardware. It's better to be able to address certain small perks or issues per architecture now and in the future.
<deleted-account> commented on 2019-11-10 15:23 (UTC)
Tired of compiling? Use this binary repo instead! Add this at the end of /etc/pacman.conf :