Okay, if this won’t even get to BIOS with the dGPU installed, something isn’t correct and you will want to open a support ticket.
You will want to get this into a support ticket as that is where I review stuff like this due to staffing and available cycles.
Hello,
Just want to share my experience with F16 batch 15 after 1 week of using it…
Ubuntu 24.04 has introduced a bug in latest kernel update 6.8.35 basically machine
will fail to properly wake up from suspend mode (encrypted drive) it can’t be shutdown/restarted quickly as it complains of being unable to access disk trying to write a log file with “filesystem read only” messages flash this goes on for 20 mins until it eventually turns off.
Initially, I didn’t want to use Ubuntu as my dislike for Ubuntu way of doing things so Mint was my first choice but installer froze at partitioning so I did install Ubuntu in the end.
Updating bios was another SNAFU, instruction to use USB boot disk ended up with ruined USB drive, however Ubuntu’s own firmware installer did precisely just that (so please update your instruction as in version 24.04 one can just use firmware updater to update bios) It set up everything properly and bios update went in smoothly after reboot…
Tracking down issue with waking up from suspend read only file system confirmed that no problem existed in 6.8.31 kernel but I had enough of Ubuntu by then…
So totally unsupported Mabox Linux 24.05 is now running like a charm with both Manjaro kernels 6.6.x and 6.9.2-1 with the latter running most of the time!
No issues with touch pad, no issues with anything really, it just works!
Arch wiki about Framework laptop puts official instructions/guides to shame which is disappointing ideed should be he first port of call for anyone setting up Framework laptop with Linux OS.
B/R
I tried installing on my new FW16 but had some problems with some program windows flashing and doing strange things sometimes (did a fresh install, no upgrade)
Went back to 22.04 and no problems with this version.
Just gonna wait until 24.04.01 point release.
Just installed Ubuntu 24.04 on my Batch 19 Framework16 and everything seems to be working perfectly with one exception: the open file dialog does not work correctly in either Firefox or Brave, but does work in Chrome. Is anyone else seeing this?
The open file dialog comes up with no problem when needed (e.g. you are trying to import a certificate), but if you double click on a file or click the open button, the dialog disappears but the file is not uploaded. I am currently forced to use Chrome because of this, which is not my preferred choice.
Possibly this is an Ubuntu bug, but I couldn’t find anything on the Ubuntu forums about it, which I would expect to if it was impacting everyone because Firefox is the default browser.
I would be curious to know if any other Framework16 users have seen this problem. If you are running Ubuntu 24.04 on a Framework16, are you able to open files in Firefox?
In case it is relevant, I’m using internal graphics, no GPU, and I did a fresh install of Ubuntu 24.04 from a live USB.
EDIT: As suggested by Paul Kelly, I removed snap following the instructions at https://linuxconfig.org/uninstalling-snapd-on-ubuntu and reinstalled Firefox and Brave and this completely solved the problem.
Sounds like a snap problem. I went with Ubuntu 24.04 too, but found that life was better after I nuked snapd from the system. I reinstalled Firefox & Brave using traditional packages from Mozilla and Brave repositories. My particular problem was KeePassXC integration doesn’t work through the isolation that the snap package imposes on Firefox.
Ubuntu really doesn’t make it easy to switch away from snap, I probably would have been better off changing to a snap-free distribution like mint or Pop!_OS.
Thank you so much, removing snap completely solved my problem!
As a longtime Pop/OS user I had no idea Canonical had done this. I wanted to try out Ubuntu 24.04 because of all the good things I had heard about it’s performance on the Framework16, but I will be switching back to Pop/OS as soon as they release their version 24.04 (looking foward to Cosmic but even without it I find Pop/OS to be a huge improvement over Ubuntu, and not just for System76 machines).
I had the issue of the touch-pad not working as well. The way I fixed the issue was to power off the framework 16, connect to Ethernet through the Ethernet module I purchased through framework, boot up, and then sudo apt update. I am still unsure as to why this worked for me, but this was my solution.
I’m also running into issues with the touchpad not being recognized. It’s probably that kernel issue, but what’s interesting is that it seems to consistently never work if I boot the laptop while connected to the power adapter.
Framework 16, Ubuntu 24.04 - Bluetooth not working on boot.
I am not finding this issue reported here by anyone else.
On cold boot, bluetooth is not detected. I don’t mean that devices are not detected. The system does not identify that it has bluetooth. Everything else works fine. Touchpad works, keyboard works, all ports working as expected, WiFi is working without issue.
If I reboot, everything works perfectly. So if I shut my computer down, after booting it up, I reboot, and everything is good.
But if I go from shutdown to booted, the system does not detect that it has bluetooth (cannot turn it on in the settings).
Plugged in, unplugged, doesn’t matter.
As far as I have seen up to this point, this problem only exists on a cold boot.
I’m also having intermittent issues with the touchpad.
Ubuntu 24.04, Linux 6.8.0-39, Ryzen 7040 series.
Of course, now that I’m actively trying to reproduce it to get a dmesg trace, it doesn’t happen anymore, but such is life.
What is the experience with duel booting between ubuntu and windows 10 22.H2. I want to have windows 10 on my laptop because of compatibility with solid works, auto cad, and the Microsoft office sweat.
Did this issue ever get resolved? I’m having the same issue now too on Ubuntu 24.04.
Not here, in any case.
I tried a mainline kernel hoping this would fix things (currently on Linux 6.10.2-061002-generic), and it seems to have fixed issues like crashes-to-poweroff, but as of today Aug 11 2024 I still get a dying trackpad/cursor.
I did manage to get some dmesg traces, which show… nothing.
The USB hub and USB devices are still there, there doesn’t seem to be any new error when booting with a dead trackpad (diffed to a trace with a working one), and there are no new logs in dmesg when the trackpad dies.
How does it happen for you? For me, it only happens on boot. If the trackpad isn’t working on boot, it won’t work. If it’s working, it keeps working. So my current solution is to keep rebooting until it works…
Also haven’t found anything in the logs. I looked at /proc/bus/input and when it doesn’t work it’s not there, and when it works it is. No other clues.
Also, BIOS is detecting it, because if it it’s not there BIOS will throw a warning…
For me it also happens sometimes on boot, but can also happen during run.
I haven’t had it happen when my device was on battery and not plugged in to power, but my device is plugged in most of the time so I can’t infer much from this.
When it happens during run, the cursor just snaps to its stuck position on the lower right, and stay there until I force it to reboot (either via power button or via opening a terminal with the keyboard).
I managed to reproduce the issue on boot just now, by hot-rebooting 6 times (plugged in).
It it ever matters, my ports are DisplayPort (left back), USB-A (left middle), MicroSD (left front), USB-C (right back, charging port), USB-A (right middle), Ethernet (right front), and I am using the keyboard and the numpad.
I haven’t been able to consistently reproduce it. It seems random. Recently I’ve been doing some data transfers between external drives which crashes often (frustrating… but unrelated) and noticed it more. I’m not sure if it’s related to these crashes, or if I’m just noticing it because I rarely reboot my computer otherwise. I have a USB mouse but it happens whether or not it’s plugged in at boot.
My ports are:
left back USB-C
left mid HDMI
left front: USB-A
right back USB-C
right mid: audio
right front: USB-A
I’m on Framework 16 Ryzen 7040 series, Ubuntu 24.04, kernel linux 6.8.0-39-generic x86_64
I also uploaded my journalctl contents here:
not working: current_boot_logs.tar.gz - Google Drive
working: previous_boot_logs.tar.gz - Google Drive
Only thing I can observe (search “touchpad” in the logs) is it’s just not being detected when it doesn’t work. I don’t see any errors or anything but not well-versed.
In current_boot (not working):
Aug 07 15:25:37 papakwaqa kernel: hid-generic 0018:32AC:001B.0001: hidraw0: I2C HID v1.00 Device [FRMW0003:00 32AC:001B] on i2c-FRMW0003:00
Aug 07 15:25:37 papakwaqa kernel: nvme nvme0: pci function 0000:02:00.0
Aug 07 15:25:37 papakwaqa kernel: nvme nvme0: allocated 32 MiB host memory buffer.
Aug 07 15:25:37 papakwaqa kernel: nvme nvme0: 16/0/0 default/read/poll queues
Aug 07 15:25:37 papakwaqa kernel: nvme0n1: p1 p2
Aug 07 15:25:37 papakwaqa kernel: hid-sensor-hub 0018:32AC:001B.0001: hidraw0: I2C HID v1.00 Device [FRMW0003:00 32AC:001B] on i2c-FRMW0003:00
In works_boot:
Aug 07 22:20:50 papakwaqa kernel: hid-generic 0018:32AC:001B.0001: hidraw0: I2C HID v1.00 Device [FRMW0003:00 32AC:001B] on i2c-FRMW0003:00
Aug 07 22:20:50 papakwaqa kernel: input: PIXA3854:00 093A:0274 Mouse as /devices/platform/AMDI0010:03/i2c-1/i2c-PIXA3854:00/0018:093A:0274.0002/input/input3
Aug 07 22:20:50 papakwaqa kernel: input: PIXA3854:00 093A:0274 Touchpad as /devices/platform/AMDI0010:03/i2c-1/i2c-PIXA3854:00/0018:093A:0274.0002/input/input4
Aug 07 22:20:50 papakwaqa kernel: hid-generic 0018:093A:0274.0002: input,hidraw1: I2C HID v1.00 Mouse [PIXA3854:00 093A:0274] on i2c-PIXA3854:00
Aug 07 22:20:50 papakwaqa kernel: xhci_hcd 0000:c1:00.3: xHCI Host Controller
Aug 07 22:20:50 papakwaqa kernel: xhci_hcd 0000:c1:00.3: new USB bus registered, assigned bus number 1
Aug 07 22:20:50 papakwaqa kernel: hid-sensor-hub 0018:32AC:001B.0001: hidraw0: I2C HID v1.00 Device [FRMW0003:00 32AC:001B] on i2c-FRMW0003:00
Aug 07 22:20:50 papakwaqa kernel: xhci_hcd 0000:c1:00.3: hcc params 0x0128ffc5 hci version 0x120 quirks 0x0000000200000410
Aug 07 22:20:50 papakwaqa kernel: xhci_hcd 0000:c1:00.3: xHCI Host Controller
Aug 07 22:20:50 papakwaqa kernel: xhci_hcd 0000:c1:00.3: new USB bus registered, assigned bus number 2
Aug 07 22:20:50 papakwaqa kernel: xhci_hcd 0000:c1:00.3: Host supports USB 3.1 Enhanced SuperSpeed
In previous_boot (works):
Aug 05 13:57:06 papakwaqa kernel: hid-generic 0018:32AC:001B.0001: hidraw0: I2C HID v1.00 Device [FRMW0003:00 32AC:001B] on i2c-FRMW0003:00
Aug 05 13:57:06 papakwaqa kernel: input: PIXA3854:00 093A:0274 Mouse as /devices/platform/AMDI0010:03/i2c-1/i2c-PIXA3854:00/0018:093A:0274.0002/input/input3
Aug 05 13:57:06 papakwaqa kernel: input: PIXA3854:00 093A:0274 Touchpad as /devices/platform/AMDI0010:03/i2c-1/i2c-PIXA3854:00/0018:093A:0274.0002/input/input4
Aug 05 13:57:06 papakwaqa kernel: hid-generic 0018:093A:0274.0002: input,hidraw1: I2C HID v1.00 Mouse [PIXA3854:00 093A:0274] on i2c-PIXA3854:00
Aug 05 13:57:06 papakwaqa kernel: nvme 0000:02:00.0: platform quirk: setting simple suspend
Aug 05 13:57:06 papakwaqa kernel: nvme nvme0: pci function 0000:02:00.0
Aug 05 13:57:06 papakwaqa kernel: hid-sensor-hub 0018:32AC:001B.0001: hidraw0: I2C HID v1.00 Device [FRMW0003:00 32AC:001B] on i2c-FRMW0003:00
Aug 05 13:57:06 papakwaqa kernel: nvme nvme0: allocated 32 MiB host memory buffer.
Aug 05 13:57:06 papakwaqa kernel: nvme nvme0: 16/0/0 default/read/poll queues
Aug 05 13:57:06 papakwaqa kernel: nvme0n1: p1 p2
Aug 05 13:57:06 papakwaqa kernel: input: PIXA3854:00 093A:0274 Mouse as /devices/platform/AMDI0010:03/i2c-1/i2c-PIXA3854:00/0018:093A:0274.0002/input/input5
Aug 05 13:57:06 papakwaqa kernel: input: PIXA3854:00 093A:0274 Touchpad as /devices/platform/AMDI0010:03/i2c-1/i2c-PIXA3854:00/0018:093A:0274.0002/input/input6
Aug 05 13:57:06 papakwaqa kernel: hid-multitouch 0018:093A:0274.0002: input,hidraw1: I2C HID v1.00 Mouse [PIXA3854:00 093A:0274] on i2c-PIXA3854:00
(Also not working: works_boot_logs.tar.gz - Google Drive – separate post because “new users can only put two links in a post”)
Yeah - contrary to my initial probe, the dmesg is different during boot.
A working boot has the lines
input: PIXA3854:00 093A:0274 Mouse as /devices/platform/AMDI0010:03/i2c-1/i2c-PIXA3854:00/0018:093A:0274.0002/input/input3
input: PIXA3854:00 093A:0274 Touchpad as /devices/platform/AMDI0010:03/i2c-1/i2c-PIXA3854:00/0018:093A:0274.0002/input/input4
hid-generic 0018:093A:0274.0002: input,hidraw1: I2C HID v1.00 Mouse [PIXA3854:00 093A:0274] on i2c-PIXA3854:00
hid-sensor-hub 0018:32AC:001B.0001: hidraw0: I2C HID v1.00 Device [FRMW0003:00 32AC:001B] on i2c-FRMW0003:00
after:
Run /init as init process
with arguments:
/init
splash
with environment:
HOME=/
TERM=linux
BOOT_IMAGE=/boot/vmlinuz-6.10.2-061002-generic
hid: raw HID events driver (C) Jiri Kosina
ACPI: video: Video Device [VGA] (multi-head: yes rom: no post: no)
input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:1b/LNXVIDEO:00/input/input2
ACPI: bus type thunderbolt registered
And a non-working boot does not.
A non-working boot does not have 093A:0274 at all.
I do manage to reproduce the issue within 10 hot reboots while plugged in.
Looks like the issue got to Reddit as well.
Just dropped a CS ticket, feel free to drop one with working and non-working logs for CS to get more data points.
I’ve been contacting support for a similar issue Frequent keyboard/trackpad freeze as well. They sent me a new mid-plate and the problem is still happening.