Lenovo duet ct-x636f

[CristianGarcia93]

I'm trying to install cdmium through usb with version 4.0.0 for arm64 and when I choose the Ui, give me error "package ntpdate has not installation candidate".
I tried all, install manually before run the install script or install another ntp but nothing works.
I don't know if I need another version

[AveraheLinuxUser]

Hello. The issue caused by package that was renamed in debian repos.
You can fix it manually:

• nano /CdFiles/fs/debian/info
• Under:
  # packages:
  FS_PKGS_CD_BASE=
  fix ntpdate to ntpsec-ntpdate

[CristianGarcia93]

Thank after your hit I successfully install cdmium but I have another problem.
I install gnome but on screen I see only the cursor

[AveraheLinuxUser]

Thats really weird. Try to disable user session manager (gdm) and start session from tty

[trashbytes]

#183 Same issues here.

[CristianGarcia93]

Nothing changed after I started gdm through terminal

[zachgillette]

It looks like this with any UI installation.

Note: I can hear the volume setting when pressing volume up and down (the little pop noise).

I'm guessing the display driver is borked?

[dengesCU]

I also ran into this issue, and I was under the impression that it arises when updating from Mesa 24 to 25 (This update happened along with many other packages, and I haven't verified that it is (only) Mesa that causes the issue). I switched to Debian Bookworm which runs an older version (of everything), and there everything works just fine.

[zachgillette]

I also ran into this issue, and I was under the impression that it arises when updating from Mesa 24 to 25 (This update happened along with many other packages, and I haven't verified that it is (only) Mesa that causes the issue). I switched to Debian Bookworm which runs an older version (of everything), and there everything works just fine.

Could you elaborate on how you did this?

[dengesCU]

I initially used the image from Github (0.4.0) for Cadmium. This comes with Debian sid. Then I installed Sway (I also tried Gnome after and the same happened) on the usb which worked just fine. After running apt upgrade, I ran into the same issue. On the Discord channel #mt8183 people also ran into this issue and suggested it's due to mesa. Among the updated packages was indeed mesa, and so it seems plausible to me that the Mesa 24->25 update is responsible for the issue.

To avoid the issue, I used the build script in this repo, and built Debian bookworm, installed it, and haven't had the issue anymore. So it definitely has to do with some package update.

[zachgillette]

Drat, I don't have another Linux machine to do a custom build. Is there any way to fix it on the 0.4.0 release?

[dengesCU]

I think it should work if you don't do apt upgrade or hold the right packages. But I wanted to avoid going down that route..

With enough patience you should also be able to build it on the Duet, and then reinstall. Compiling the kernel takes ~1h for me on the Duet vs. 7min on my normal laptop.

PS: I can probably give you the image I used. But frankly, if I were you, I would not trust a stranger's OS image

[zachgillette]

I guess I'll just wait for fixed release. I just wanted to make the Duet usable, since ChromeOS is a joke on it.

[dengesCU]

The same issue seems to happen in PostmarketOS (https://postmarketos.org/edge/2025/05/05/Graphical-issue-with-Mesa-25-on-Mediatek-SoCs/), and was fixed there by adding 'PAN_MESA_DEBUG=noafbc' to the environment
(https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/6470). I haven't tried this (since I am still on Debian Bookworm with mesa 22) but sounds promising. I will test this when I get a chance.
edit: For me the issue was mostly fixed by adding the env variable to /etc/profile: On an existing Bookworm installation I upgraded to Trixie, confirmed that the bug still happened, and then added the env variable to /etc/profile. Gnome and Sway worked without an issue afterwards. However, I wasn't able to get the Login Screen (gdm) to work (I started Gnome and Sway each from tty)

[zachgillette]

The same issue seems to happen in PostmarketOS (https://postmarketos.org/edge/2025/05/05/Graphical-issue-with-Mesa-25-on-Mediatek-SoCs/), and was fixed there by adding 'PAN_MESA_DEBUG=noafbc' to the environment (https://gitlab.postmarketos.org/postmarketOS/pmaports/-/merge_requests/6470). I haven't tried this (since I am still on Debian Bookworm with mesa 22) but sounds promising. I will test this when I get a chance. edit: For me the issue was mostly fixed by adding the env variable to /etc/profile: On an existing Bookworm installation I upgraded to Trixie, confirmed that the bug still happened, and then added the env variable to /etc/profile. Gnome and Sway worked without an issue afterwards. However, I wasn't able to get the Login Screen (gdm) to work (I started Gnome and Sway each from tty)

Unless I did it wrong, this didn't work for me. Tried "export PAN_MESA_DEBUG=noafbc" in both /etc/profile and ~/.profile. I'm booting from USB, so is this the wrong spot? Booting from disk goes straight to the messed up screen.

[dengesCU]

Just to be sure, did you try starting the session from tty or is the flickering the first (and only) thing you see?

In case you are not logged into a tty: You can reach the (non-graphical) with Ctrl+Alt+F2 (that is tty2, for other tty use F1-F7 instead; the (broken) login screen should be on tty1). Then type in your user name and password, and you should see a shell. Assuming you are using Gnome, you could start it with XDG_SESSION_TYPE=wayland dbus-run-session gnome-session

Does this still not work for you?

edit: I don't think this issue is kernel-related but in any case I am running 6.15.6