Whitehara/kernel-tkg

Description

Description not filled in by author. Very likely personal repository for testing purpose, which you should not use.

Installation Instructions

Instructions not filled in by author. Author knows what to do. Everybody else should avoid this repo.

Active Releases

The following unofficial repositories are provided as-is by owner of this project. Contact the owner directly for bugs or issues (IE: not bugzilla).

Release Architectures Repo Download Fedora 37 x86_64 (0)* Fedora 37 (0 downloads)

* Total number of packages downloaded in the last seven days.


This is a companion discussion topic for the original entry at https://copr.fedorainfracloud.org/coprs/whitehara/kernel-tkg/

Thank you for this repository!
How can I install this kernel in Silverblue?

Unfortunately, I don’t know the detail of Silverblue. Maybe you can download rpms manually, then use the rpm-ostree command like this:

rpm-ostree override replace --remove=kernel-core --remove=kernel-modules --install=kernel-core-*.rpm --install=kernel-modules-*.rpm

Please test it on the test environment before you try it on the production environment, or it will break your environment.

I think I’ve found the way to do it without manual download. Here is the command I use:

rpm-ostree override replace --experimental --from repo='copr:copr.fedorainfracloud.org:whitehara:kernel-tkg' kernel kernel-core kernel-modules kernel-modules-core kernel-modules-extra

Thanks for sharing such useful information.

Hello, thanks for this repo!
Can i kindly ask you a preemptive kernel copr for generic cpus?

I made a new project.

https://copr.fedorainfracloud.org/coprs/whitehara/kernel-tkg-preempt/

Please test it.

Works great on my custom-made Kinoite with nvidia, thank you so much!

This repo is amazing! I’ve been happily using your tkg-zen2-preempt for months now with no issues.

However, would it be possible for you to add the ‘amdgpu.ignore_min_pcap=1’ patch that’s found in the Zen kernel?

Without it I’m only able to reduce my GPUs power limit from 203W to 190W since the changes in kernel 6.7, which really isn’t much of a reduction.

I applied the patch to 6.10.5.
Please test it.

Works perfectly. Thanks so much!

I am using 6.10.11-200_tkg_zen2_preempt.fc40, bluetooth doesnt work.

When I check systemctl bluetooth status it shows this:

○ bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: enabled)
Drop-In: /usr/lib/systemd/system/service.d
└─10-timeout-abort.conf
Active: inactive (dead)
Docs: man:bluetoothd(8)

Sep 28 12:59:56 fedora systemd[1]: bluetooth.service - Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
Sep 28 13:00:01 fedora systemd[1]: bluetooth.service - Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth).

when I restart and enable the service manually, it shows that it runs, but I cant turn it on, cant scan.

here is the output:

● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: enabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: active (running) since Sat 2024-09-28 13:01:15 +07; 24min ago
       Docs: man:bluetoothd(8)
   Main PID: 6171 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 76250)
     Memory: 1.9M (peak: 5.3M)
        CPU: 53ms
     CGroup: /system.slice/bluetooth.service
             └─6171 /usr/libexec/bluetooth/bluetoothd

Sep 28 13:01:15 fedora bluetoothd[6171]: src/plugin.c:init_plugin() System does not support bap plugin
Sep 28 13:01:15 fedora bluetoothd[6171]: src/plugin.c:init_plugin() System does not support bass plugin
Sep 28 13:01:15 fedora bluetoothd[6171]: src/plugin.c:init_plugin() System does not support mcp plugin
Sep 28 13:01:15 fedora bluetoothd[6171]: src/plugin.c:init_plugin() System does not support vcp plugin
Sep 28 13:01:15 fedora bluetoothd[6171]: profiles/audio/micp.c:micp_init() D-Bus experimental not enabled
Sep 28 13:01:15 fedora bluetoothd[6171]: src/plugin.c:init_plugin() System does not support micp plugin
Sep 28 13:01:15 fedora bluetoothd[6171]: src/plugin.c:init_plugin() System does not support ccp plugin
Sep 28 13:01:15 fedora bluetoothd[6171]: src/plugin.c:init_plugin() System does not support csip plugin
Sep 28 13:01:15 fedora bluetoothd[6171]: src/plugin.c:init_plugin() System does not support asha plugin
Sep 28 13:01:15 fedora bluetoothd[6171]: Bluetooth management interface 1.22 initialized

Not listed in rfkill:

❯ rfkill list all
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

# lspci -nnk | grep -iA3 net; lsusb; dmesg | grep -Ei 'blue|firm'

01:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6 AX200 [8086:2723] (rev 1a)
	Subsystem: Intel Corporation Wi-Fi 6 AX200NGW [8086:0084]
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 04f2:b6bf Chicony Electronics Co., Ltd HP HD Camera
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
[    0.314186] Spectre V2 : Enabling Speculation Barrier for firmware calls
[    0.509497] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[    0.532037] acpi PNP0A08:00: [Firmware Info]: ECAM [mem 0xf8000000-0xfbffffff] for domain 0000 [bus 00-3f] only partially covers this bridge
[    2.405609] wmi_bus wmi_bus-PNP0C14:00: [Firmware Info]: DF4E63B6-3BBC-4858-9737-C74F82F821F3 has zero instances
[    2.405856] wmi_bus wmi_bus-PNP0C14:00: [Firmware Info]: 8F1F6436-9F42-42C8-BADC-0E9424F20C9A has zero instances
[    5.145124] [drm] Loading DMUB firmware via PSP: version=0x0101002B
[    5.145878] [drm] Found VCN firmware Version ENC: 1.22 DEC: 7 VEP: 0 Revision: 1
[    5.145887] amdgpu 0000:03:00.0: amdgpu: Will use PSP to load VCN firmware
[    8.070769] iwlwifi 0000:01:00.0: loaded firmware version 77.85be44d3.0 cc-a0-77.ucode op_mode iwlmvm
[   67.465489] Bluetooth: Core ver 2.22
[   67.465561] NET: Registered PF_BLUETOOTH protocol family
[   67.465565] Bluetooth: HCI device and connection manager initialized
[   67.465573] Bluetooth: HCI socket layer initialized
[   67.465578] Bluetooth: L2CAP socket layer initialized
[   67.465590] Bluetooth: SCO socket layer initialized
[  111.635928] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[  111.635934] Bluetooth: BNEP filters: protocol multicast
[  111.635940] Bluetooth: BNEP socket layer initialized

When I switch to latest fedora kernel bluetooth works, here is the output:

● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: enabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: active (running) since Sat 2024-09-28 14:11:27 +07; 1min 14s ago
       Docs: man:bluetoothd(8)
   Main PID: 1143 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 76267)
     Memory: 2.7M (peak: 6.2M)
        CPU: 100ms
     CGroup: /system.slice/bluetooth.service
             └─1143 /usr/libexec/bluetooth/bluetoothd

Sep 28 14:11:48 fedora bluetoothd[1143]: profiles/audio/media.c:app_register_endpoint() Unable to register endpoint :1.116:/MediaEndpoint/A2DPSink/opus_05: Success
Sep 28 14:11:48 fedora bluetoothd[1143]: profiles/audio/media.c:media_endpoint_create() Unable initialize endpoint for UUID 0000110a-0000-1000-8000-00805f9b34fb
Sep 28 14:11:48 fedora bluetoothd[1143]: profiles/audio/media.c:app_register_endpoint() Unable to register endpoint :1.116:/MediaEndpoint/A2DPSource/opus_05: Success
Sep 28 14:11:48 fedora bluetoothd[1143]: profiles/audio/media.c:media_endpoint_create() Unable initialize endpoint for UUID 0000110b-0000-1000-8000-00805f9b34fb
Sep 28 14:11:48 fedora bluetoothd[1143]: profiles/audio/media.c:app_register_endpoint() Unable to register endpoint :1.116:/MediaEndpoint/A2DPSink/opus_05_duplex: Success
Sep 28 14:11:48 fedora bluetoothd[1143]: profiles/audio/media.c:media_endpoint_create() Unable initialize endpoint for UUID 0000110a-0000-1000-8000-00805f9b34fb
Sep 28 14:11:48 fedora bluetoothd[1143]: profiles/audio/media.c:app_register_endpoint() Unable to register endpoint :1.116:/MediaEndpoint/A2DPSource/opus_05_duplex: Success
Sep 28 14:11:48 fedora bluetoothd[1143]: profiles/audio/media.c:client_ready_cb() No valid external Media objects found
Sep 28 14:11:48 fedora bluetoothd[1143]: profiles/audio/media.c:media_endpoint_create() Unable initialize endpoint for UUID 0000110a-0000-1000-8000-00805f9b34fb
Sep 28 14:11:48 fedora bluetoothd[1143]: profiles/audio/media.c:media_endpoint_create() Unable initialize endpoint for UUID 0000110b-0000-1000-8000-00805f9b34fb

Please check it also occurs on the original Fedora kernel, 6.10.11-200.fc40.

Original kernel systemctl bluetooth status output:

● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: enabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: active (running) since Sat 2024-09-28 14:24:55 +07; 2min 49s ago
       Docs: man:bluetoothd(8)
   Main PID: 12485 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 76267)
     Memory: 1.1M (peak: 5.0M)
        CPU: 256ms
     CGroup: /system.slice/bluetooth.service
             └─12485 /usr/libexec/bluetooth/bluetoothd

Sep 28 14:24:55 fedora bluetoothd[12485]: Endpoint registered: sender=:1.116 path=/MediaEndpoint/A2DPSource/faststream_duplex
Sep 28 14:24:55 fedora bluetoothd[12485]: Endpoint registered: sender=:1.116 path=/MediaEndpoint/A2DPSink/opus_05
Sep 28 14:24:55 fedora bluetoothd[12485]: Endpoint registered: sender=:1.116 path=/MediaEndpoint/A2DPSource/opus_05
Sep 28 14:24:55 fedora bluetoothd[12485]: Endpoint registered: sender=:1.116 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Sep 28 14:24:55 fedora bluetoothd[12485]: Endpoint registered: sender=:1.116 path=/MediaEndpoint/A2DPSource/opus_05_duplex
Sep 28 14:24:59 fedora bluetoothd[12485]: Failed to set mode: Failed (0x03)
Sep 28 14:25:07 fedora bluetoothd[12485]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Sep 28 14:25:33 fedora bluetoothd[12485]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Sep 28 14:26:23 fedora bluetoothd[12485]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down
Sep 28 14:27:10 fedora bluetoothd[12485]: Failed to set mode: Failed (0x03)
~ 

I can select, and pair devices

Thank you for your report.
Was it also working on the previous version, 6.10.10-200_tkg_zen2_preempt.fc40?

Weird, I restarted the bluetooth demon, let the system run for a while, close the lid of my laptop, which put it into sleep mode, Once I opened it, bluetooth started to work. It looks like it doesnt start the daemon on startup, or it has some issues doing so.

This is replicable btw, after every laptop restart, I need to do these steps.

Never tried older kernel before, first time I try tkg - custom kernel.

Here is the output of the daemon after wake up. Dont know if its helpfull at all :slight_smile:

● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: enabled)
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: active (running) since Sat 2024-09-28 15:22:10 +07; 9min ago
       Docs: man:bluetoothd(8)
   Main PID: 4763 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 76250)
     Memory: 2.4M (peak: 5.2M)
        CPU: 118ms
     CGroup: /system.slice/bluetooth.service
             └─4763 /usr/libexec/bluetooth/bluetoothd

Sep 28 15:25:18 fedora bluetoothd[4763]: Endpoint registered: sender=:1.108 path=/MediaEndpoint/A2DPSource/aptx_ll_1
Sep 28 15:25:18 fedora bluetoothd[4763]: Endpoint registered: sender=:1.108 path=/MediaEndpoint/A2DPSource/aptx_ll_0
Sep 28 15:25:18 fedora bluetoothd[4763]: Endpoint registered: sender=:1.108 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
Sep 28 15:25:18 fedora bluetoothd[4763]: Endpoint registered: sender=:1.108 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
Sep 28 15:25:18 fedora bluetoothd[4763]: Endpoint registered: sender=:1.108 path=/MediaEndpoint/A2DPSource/faststream
Sep 28 15:25:18 fedora bluetoothd[4763]: Endpoint registered: sender=:1.108 path=/MediaEndpoint/A2DPSource/faststream_duplex
Sep 28 15:25:18 fedora bluetoothd[4763]: Endpoint registered: sender=:1.108 path=/MediaEndpoint/A2DPSink/opus_05
Sep 28 15:25:18 fedora bluetoothd[4763]: Endpoint registered: sender=:1.108 path=/MediaEndpoint/A2DPSource/opus_05
Sep 28 15:25:18 fedora bluetoothd[4763]: Endpoint registered: sender=:1.108 path=/MediaEndpoint/A2DPSink/opus_05_duplex
Sep 28 15:25:18 fedora bluetoothd[4763]: Endpoint registered: sender=:1.108 path=/MediaEndpoint/A2DPSource/opus_05_duplex

Unfortunately, this is just a normal log about bluetoothd and no hints…

I suppose there are some problems about hardware initialization.
Since some of the parameters are changed in the custom kernel, it may not initialize the bluetooth device correctly. However, I don’t know which parameters affect that…

How about do this command when you see the problem?

sudo modprobe -r btusb
sudo modprobe btusb