Patchset for TUXEDO devices

Bug #2098104 reported by Werner Sembach
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Medium
Benjamin Wheeler
Noble
Fix Released
Medium
Unassigned

Bug Description

SRU Justification:

Impact: This is a patchset that we (TUXEDO Computers) currently apply on top of the Ubuntu 6.8 kernel to make it run smoothly on all our devices. All patches apply smoothly to 6.8.
Fix: These are all patches already upstream, just not on the 6.8 branch, because they where upstreamed after that one was already EOL.
Testcase: We run this patchset for all our customers devices (we basically maintain our own OEM branch) so it is quite field testet. Besides that, whenever a new patch was added we did regression testing on a selection of devices.

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-6.9.y&id=7173972a2eb1107ae3dc076f1cd27abce132e027
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-6.9.y&id=97474e5f54243be13d72cbda50624f0114213c7d
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-6.9.y&id=511207452221a94242664be47c4ceb63d5c6b293
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-6.9.y&id=52f8c45fa36df0754b4562b7b535be8475304ebe
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-6.9.y&id=00efe7fcf9ceeff0808bca9460afb49e7ada6068
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-6.9.y&id=f96ba82df505903ead1d28cf5eccc4ee8102a048
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-6.11.y&id=905560781394f91ff09ad71974ecfb78c9d7cc6e
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-6.11.y&id=cc4e80f047b881a7f44c9adb3f2d2ebec18c2823
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b1049f2d68693c80a576c4578d96774a68df2bad
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=dbf2bb1a1319b7c7d8828905378a6696cca6b0f2
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=11cb3529d18514f7d28ad2190533192aedefd761

Revision history for this message
Tim Whisonant (tswhison) wrote :

Hello Werner, thank you for sharing these and for helping to improve Ubuntu. I have sent a note to our extended team to ask about including these. I'll follow up once I have a response.

Best,
Tim

Revision history for this message
Tim Whisonant (tswhison) wrote (last edit ):

Some early feedback I received: we would like to know more of the details of the patches and the hardware they support.

Please refer to our patch submission guidelines found at

https://canonical-kernel-docs.readthedocs-hosted.com/en/latest/reference/stable-patch-format/

description: updated
Revision history for this message
Werner Sembach (wsembach) wrote :

Thanks for the link (I only found a ubuntu wiki entry that probably is a little outdated if that one is the current guidline?).

Should I resend the patch? I saw that I messed up the subject line a bit.

For the explanations (in the same order as the links above):

wifi: ath12k: add fallback board name without variant while searching board-2.bin
wifi: ath12k: remove unused ATH12K_BD_IE_BOARD_EXT
wifi: ath12k: add support to search regdb data in board-2.bin for WCN7850
wifi: ath12k: support default regdb while searching board-2.bin for WCN7850

Are part of a larger patchset to enable support for the ath12k wifi chipset that iirc we currently use in our intel desktop pcs. The rest of that patchset already got included in the Ubuntu 6.8 kernel. TBH I never looked into the patches individually, maybe you can give some insights?

ACPI: resource: Use IRQ override on Maibenben X565

is basically just here so that

ACPI: resource: Do IRQ override on TongFang GXxHRXx and GMxHGxx

doesn't cause a merge conflict. The 2nd patch is for the TUXEDO InfinityBook Pro Gen9 AMD and TUXEDO Stellaris Slim Gen1 AMD keyboard to work. It is a quirk that some AMD notebook need, because of a potential BIOS bug.

ALSA: hda/realtek: Fix headset mic on TUXEDO Gemini 17 Gen3

Qurik for the microphone to work in the built in audio jack

ALSA: hda/realtek: Fix headset mic on TUXEDO Stellaris 16 Gen6 mb1

Qurik for the microphone to work in the built in audio jack

PCI: Avoid putting some root ports into D3 on TUXEDO Sirius Gen1

Fixes a no resume bug on unupdated BIOS on the TUXEDO Sirius Gen1

nvme-pci: Add TUXEDO InfinityFlex to Samsung sleep quirk

Quirk to make the device sleep better

nvme-pci: Add TUXEDO IBP Gen9 to Samsung sleep quirk

Quirk to make the device sleep better

To summarise: ath12k wifi chip support and a lot of single device quirks with the respective device in the patches subject line

Revision history for this message
Werner Sembach (wsembach) wrote (last edit ):

I just saw, I also sent the patches to the mailing list, but the don't seem to have reched it: https://lists.ubuntu.com/archives/kernel-team/2025-February/thread.html

Did I run in some spam filter? Or do i need to subscribe first before I can post to it?

Revision history for this message
Tim Whisonant (tswhison) wrote :

Hi Werner, I think it could be that you need to subscribe first.

Could you try that and then re-submit them to <email address hidden>

Please include the descriptions you added above to the content of your SRU submission to the mailing list.

Thank you!
Tim

Revision history for this message
Werner Sembach (wsembach) wrote :

Done, just messed up the git-sent-email (forgot to disable the tocmd ...).

Revision history for this message
Werner Sembach (wsembach) wrote :

Done² hopefully this time in the correct format: https://lists.ubuntu.com/archives/kernel-team/2025-February/157179.html

Revision history for this message
Werner Sembach (wsembach) wrote :

ps the sru v3 patchset is now directly cherry-picked from the torvalds branch and not anymore from the stable branches

Changed in linux (Ubuntu):
assignee: nobody → Benjamin Wheeler (benjaminwheeler)
importance: Undecided → Medium
status: New → In Progress
Revision history for this message
Benjamin Wheeler (benjaminwheeler) wrote :

Just pasting the link to email re-submission here: https://lists.ubuntu.com/archives/kernel-team/2025-February/157393.html

Changed in linux (Ubuntu):
status: In Progress → Fix Committed
Revision history for this message
Benjamin Wheeler (benjaminwheeler) wrote :

Released in 6.8.0-58.60! Thanks again for your suggestion to improve Ubuntu.

Changed in linux (Ubuntu):
status: Fix Committed → Fix Released
Changed in linux (Ubuntu Noble):
status: New → Fix Released
importance: Undecided → Medium
assignee: nobody → Benjamin Wheeler (benjaminwheeler)
assignee: Benjamin Wheeler (benjaminwheeler) → nobody
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux/6.8.0-58.60 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux' to 'verification-done-noble-linux'. If the problem still exists, change the tag 'verification-needed-noble-linux' to 'verification-failed-noble-linux'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-noble-linux-v2 verification-needed-noble-linux
Revision history for this message
Benjamin Wheeler (benjaminwheeler) wrote :

The patchset is in the debian changelog for 6.8.0-58.60.

tags: added: verification-done-noble-linux
removed: verification-needed-noble-linux
Juerg Haefliger (juergh)
tags: added: kernel-daily-bug
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-raspi/6.8.0-1028.32 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-raspi' to 'verification-done-noble-linux-raspi'. If the problem still exists, change the tag 'verification-needed-noble-linux-raspi' to 'verification-failed-noble-linux-raspi'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-noble-linux-raspi-v2 verification-needed-noble-linux-raspi
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-nvidia-tegra/6.8.0-1007.7 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-nvidia-tegra' to 'verification-done-noble-linux-nvidia-tegra'. If the problem still exists, change the tag 'verification-needed-noble-linux-nvidia-tegra' to 'verification-failed-noble-linux-nvidia-tegra'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-noble-linux-nvidia-tegra-v2 verification-needed-noble-linux-nvidia-tegra
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-fips/6.8.0-72.72+fips1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-fips' to 'verification-done-noble-linux-fips'. If the problem still exists, change the tag 'verification-needed-noble-linux-fips' to 'verification-failed-noble-linux-fips'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-noble-linux-fips-v2 verification-needed-noble-linux-fips
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-aws-fips/6.8.0-1034.36+fips1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-aws-fips' to 'verification-done-noble-linux-aws-fips'. If the problem still exists, change the tag 'verification-needed-noble-linux-aws-fips' to 'verification-failed-noble-linux-aws-fips'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-noble-linux-aws-fips-v2 verification-needed-noble-linux-aws-fips
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-gcp-fips/6.8.0-1035.37+fips1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-gcp-fips' to 'verification-done-noble-linux-gcp-fips'. If the problem still exists, change the tag 'verification-needed-noble-linux-gcp-fips' to 'verification-failed-noble-linux-gcp-fips'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-noble-linux-gcp-fips-v2 verification-needed-noble-linux-gcp-fips
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-xilinx/6.8.0-1017.18 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-xilinx' to 'verification-done-noble-linux-xilinx'. If the problem still exists, change the tag 'verification-needed-noble-linux-xilinx' to 'verification-failed-noble-linux-xilinx'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-noble-linux-xilinx-v2 verification-needed-noble-linux-xilinx
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-azure-fips/6.8.0-1034.39+fips1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-azure-fips' to 'verification-done-noble-linux-azure-fips'. If the problem still exists, change the tag 'verification-needed-noble-linux-azure-fips' to 'verification-failed-noble-linux-azure-fips'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-noble-linux-azure-fips-v2 verification-needed-noble-linux-azure-fips
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.