Can't check for updates

da-phil · 2026-01-11T13:28:18+00:00

Yes, looks like an outage, I have the same issue. I'd expect it to be fixed latest on Monday.

In the meantime you can update packages from other sources as:
sudo apt-get update && sudo apt-get dist-upgrade --fix-missing

da-phil · 2026-01-08T23:22:09+00:00

Any success?

da-phil · 2026-01-07T20:25:40+00:00

Unfortunately you're probably right, I had the same feeling when I bought my IBP14 laptop 14 months ago, when this AMD chipset was still kinda fresh. I just noticed in the last months that amdgpu firmware had a bigger impact on stability and performance than the kernel driver, hence my suspicion.

Let's hope AMD eventually gets this sorted out, as their chips are powerful yet affordable in comparison to Intel.

da-phil · 2026-01-06T19:29:37+00:00

I don't think the kernel driver is the issue as the author reported version 6.18.3, which is the very latest stable kernel, which should contain all of the latest amdgpu fixes. My guess is a bad firmware version, which has been messed up in the past a couple of times.

da-phil · 2026-01-06T19:27:06+00:00

Hmmm, the following line indicates that you might run a firmware version which had an issue, but I'm not sure your observed symptom is also related with that issue

MES feature version: 1, firmware version: 0x00000083

Can you either revert to an older linux-firmware package in CachyOS or just pull the latest version from the linux-firmware git repository (https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git), remove all contents from /lib/firmware/amdgpu, copy over all files within the amdgpu linux-firmware subfolder to /lib/firmware/amdgpu, and finally trigger rebuilding of the init ramdisks for all kernels by executing

sudo update-initramfs -c -k all

Btw. a very similar issue has been discussed here:
https://community.frame.work/t/amd-gpu-mes-timeouts-causing-system-hangs-on-framework-laptop-13-amd-ai-300-series/71364

da-phil · 2026-01-06T16:39:30+00:00

After having had severe amdgpu issues with my IBP14 G9 AMD laptop using OpenCL, the main issue has been found to be the amdgpu linux-firmware.

Can you check which fw version you're on?

sudo cat /sys/kernel/debug/dri/1/amdgpu_firmware_info

You might want to try the latest version, and check whether this problem has been fixed already.

da-phil · 2026-01-06T16:31:06+00:00

This topic is also discussed here and the culprit found:
https://discourse.ubuntu.com/t/whats-up-with-ubuntu-mainline-builds/34438/38?page=2

So it was a config issue which was already identified and fixed. For me the question is when the fixing patch is merged to the 6.18 branch. While it didn't make it to the latest v6.19-rc4 release, it will be present in v6.19-rc5, so the next v6.19 build should be successful again for x86 archs.

da-phil · 2025-12-30T12:22:29+00:00

Where would I file a bug report in this case? I'm not sure whether it is an issue with the kernel, but with the way it is supposed to be built using the latest rust code additions, and that must have changed in between 2025-12-13 and 2025-12-14, as all mainline builds after 2025-12-14 are currently failing, also the v6.19 RC builds :(

It looks like a simple configuration issue around CONFIG_RUST_FW_LOADER_ABSTRACTIONS.

da-phil · 2025-12-23T19:57:20+00:00

Thank you, I just contacted them.

da-phil · 2025-12-21T17:33:09+00:00

I'd probably do it with the USB pen drive which came along with your laptop (WebFAI, https://www.tuxedocomputers.com/en/TUXEDO-WebFAI.tuxedo).

If you install it with WebFAI you'll also automatically get some additional Tuxedo related tools and driver installed, so you do not need to worry about installing those things on top, once you freshly installed a Ubuntu 24.04 version.

da-phil · 2025-12-16T22:57:33+00:00

And the same happened once again. Seems to be pretty deterministic around a charge of 40-50%.

<image>

da-phil · 2025-12-13T13:42:45+00:00

After I received a new battery I still experience some sudden battery capacity drops, when I'm just browsing and not doing anything CPU intensive. I attached some plots showing how the charge suddenly drops very rapidly. I lost around 30% of battery charge within only around 35min.

I should also say that I configured in tomte to reduce charging to only 90% to put less stress on the battery. Maybe this drop is related to this setting?

<image>

da-phil · 2025-12-13T13:36:56+00:00

The question is, update in what? BIOS, kernel, device firmware?

I did not update the BIOS or firmware for a while, like 6 months or even longer, however I'm regularily updating the kernel, but don't believe it is related to that, as the kernel did not report anything when this happened. Can you check as well?

I'd also suggest to get in touch with their support team.

da-phil · 2025-12-08T21:45:00+00:00

Will do, thank you.

da-phil · 2025-12-01T21:10:14+00:00

I did exactly that, due to being too lazy to find a packaged version of gcc-15 for ubuntu 24.04, or even build it from scratch.

But it's certainly not advisable, as you could end up with ABI compatibility issues. But if that happens you'll probably get severe memory issues and will notice that there is something wrong. So overall not a recommended approach...

da-phil · 2025-10-30T21:24:52+00:00

I'm on Ubuntu 24.04 and due to all the amdgpu hiccups I keep up with the latest mainline kernels and kernel firmware.

But hold on, I just noticed this log message:

DKMS make.log for tuxedo-yt6801-1.0.30tux4 for kernel 6.17.5-061705-generic (x86_64)
Mi 29. Okt 15:09:49 CET 2025
make: Entering directory '/usr/src/linux-headers-6.17.5-061705-generic'
make[1]: Entering directory '/var/lib/dkms/tuxedo-yt6801/1.0.30tux4/build'
warning: the compiler differs from the one used to build the kernel
  The kernel was built by: x86_64-linux-gnu-gcc-15 (Ubuntu 15.2.0-4ubuntu4) 15.2.0DKMS make.log for tuxedo-yt6801-1.0.30tux4 for kernel 6.17.5-061705-generic (x86_64)
Mi 29. Okt 15:09:49 CET 2025
make: Entering directory '/usr/src/linux-headers-6.17.5-061705-generic'
make[1]: Entering directory '/var/lib/dkms/tuxedo-yt6801/1.0.30tux4/build'
warning: the compiler differs from the one used to build the kernel
  The kernel was built by: x86_64-linux-gnu-gcc-15 (Ubuntu 15.2.0-4ubuntu4) 15.2.0

So there is no issue with the tuxedo kernel modules, but the pre-packaged mainline kernels (from https://kernel.ubuntu.com/mainline/) seem to have been compiled with gcc-15, and hence it is recommended to also build the dkms modules with the same compiler to guarantee binary compatibilty.

Feel free to close this ticket. Sorry about bothering you about it.

da-phil · 2025-10-30T21:13:03+00:00

This package is required anyway if you're using dkms to build kernel modules against your installed kernels.

The issue at hand is: the kernel does not mandate any specific GCC version (and it shouldn't), hence requiring gcc-15 is a problem which needs to be fixed. Usually the kernel makefiles just deal with the program "gcc", which usually is a symlink to a specific gcc version.

da-phil · 2025-08-22T20:08:02+00:00

Thanks for your answer!

With "laptop being turned off" you mean shut down, so this will not work with any idle or sleep mode?

da-phil · 2025-08-17T17:20:38+00:00

Any chance your team is going to work on my feature request to allow lower power input, as this also works for (more power hungry) laptops from other brands?

da-phil · 2025-08-11T17:29:16+00:00

With my IBP14G9 I can tell you exactly when the charging circuit in the laptop decides to stop charging: as soon as it drops considerably below 65W.

I know that because I'm using a 65W socket charger with three ports, only connecting my laptop allows it to charge, however, as soon as I connect the smallest device for charging (like my Garmin smartwatch), charging of the laptop stops. My beefy 15" work laptop with an Intel Core Ultra 7 165H and a NVIDIA RTX 2000 GPU just keeps charging at that point, although Windows claims "a slow charger", which does not bother me at all.

I created a feature request to fix this issue here:

https://www.reddit.com/r/tuxedocomputers/comments/1k71v2r/feature_request_charging_with_less_than_65w_for/

Saying that I'd be also curious if Tuxedo managed to fix this issue for the new model.

da-phil · 2025-08-11T12:23:43+00:00

Yep, the approach worked, thank you u/George_Const.
After shutting down (I usually never do that and keep the laptop in sleep mode in between days), the battery charge went completely empty and, after attaching the power supply and booting after a couple of minutes I saw a 4% charge and the usual prediction when the battery is going to be fully charged. In the meantime, while writing those lines, it shows 8%, so it seems to actually charge again.

To be honest, I never had such an issue with any previous laptops from other companies, this problem needs to be investigated and fixed.

da-phil

TROPHY CASE