I can not get external displays to work. I have tried Fedora 39 and Arch. I have tried both displayport and hdmi to different monitors from the back ports. Has anyone had any luck with external displays?
I have been able to get the HDMI port to work without any issue. Also tried a couple of different docks with mixed results.
On one HP dock, I could extend to one display and only mirror to the second (total of three displays counting the laptop). Did not spend much time troubleshooting yet before moving on to the next hub.
On a random amazon hub I was able to extend my display across all three screens without an issue.
1 Like
This is with Framework HDMI and/or DP expansion cards? And if so, tested on multiple expansion bays? If it’s a dock/adapter of some sort, that’s another thing altogether.
I was using a USB C to HDMI connector and a USB-C to Displayport cable, via a dock and directly connected to the laptop.
I then tried the Framework HDMI card, v1, and it seems to work. Going to keep digging.
Has anyone tried OpenSuse Tumbleweed on the AMD laptop?
1 Like
I’m putzing on fedora 39. So far the problems seem to be suspend not coming back. fwupdmgr and tools locks up with no apparent warning or error. If you immediately reboot, it hangs on fwupd service for 6 minutes. When resuming from suspend, the monitor doesn’t come back sometimes, other times the keyboard doesn’t come back. The whole X is your only choice on initial boot is annoying, though the workaround of logging out and back in gets you wayland works for me.
New thing after writing this, firefox youtube experience is bad. Tried with hardware decoding enabled/disabled. Just glitchy and lots of amdgpu errors in journal.
Do we have a list of bugs for Fedora that we can track/contribute to?
This is the “head” tracker bug, so new ones should probably be also added as a dependency to it:
I’m in batch 2 and plan on trying it. Probably with Gnome as the default, if that doesn’t work well I’ll try KDE.
exact problems i had with fwupd. impossible to use the command at all, yet the guides have no mention of this. had to install windows just to update the trackpad
Is it possible to distribute the firmware another way than fwupd? I cannot get the fwupd service to start on my system. It just hangs.
Not in today, however, I need to address some stuff before this becomes a huge thread. Only reason I’m touching this today is I rather not see this blow up over the weekend.
Outside of the fingerprint reader and the linked doc how to update it in the guide, firmware updates should be held off on.
Meaning at this time, I’m unaware of anything outside of drivers (Linux or Windows) being updated.
Monday I’ll look into fwupd on F39. If it can be duplicated, I’ll file the bug report personally.
Regarding suspend, on both of my AMD laptops, suspend resumes flawlessly. Mind you, this is only connected to ac power.
Which BIOS is installed (even though it should be what I have, I must ask) and what is attached when you’re resuming? This is fully updated (dnf) F39?
Thanks and I’ll be by Monday to go over this.
7 Likes
In Fedora fwupd was stuck in waiting and dmesg was showing some amdgup timeout errors.
I managed to run fwupd using another distro using X11 to avoid the amdgpu errors and it worked like a charm. After the update I moved back to fedora and the fingerprint reader worked.
1 Like
It does seem like fwupd hanging is related to the amdgpu errors.
Hoping my experience can provide useful data. On Arch, with sway:
- The first time I start sway after booting, it crashes with:
-
amdgpu: The CS has been rejected (-125). Recreate the context.- This log entry is also in 2244221 – Framework 13 AMD Defaults to X11 on boot, hopefully this is the issue fixed by 3.03.
- Subsequent launches work.
-
- Starting a Wayland session triggers the amdgpu error reliably for me. I have not used Fedora, but I suspect Fedora could be falling back to X11 after Wayland fails.
- Regarding
fwupd,- Running
fwupdmgrbefore launching sway (and causing the amdgpu error) works. - Running
fwupdmgranytime after attempting to launch sway will hang.
- Running
- I suspect that the two issues are related, which would explain why using X11 works for
fwupd.
If anyone is having issues with fwupd while attempting to update the fingerprint reader, I suggest either trying X11 or booting into a console instead of Wayland.
Have yet to test suspend, but I think I will wait until after 3.03 to do so.
4 Likes
@Gabriel_Esposito what you have written up exactly matches my experience using sway, including the initial crash when starting sway.
In my testing suspend also crashes with the same amdgpu error output as sway. Hibernate works though.
3 Likes
All,
Running an update with fwupd and making sure all your packages are updated (for that day, meaning dnf update every day until the release settles down a bit). There should be no hang, Workstation/GNOME.
3 Likes
@Matt_Hartley I’ve been running ArcoLinux since my AMD framework came in. Aside from the FW upgrade on the fingerprint reader, everything worked out of the box. I’ve used both the stock kernel and xanmod (both 6.5.7-1).
Used Arcolinux L - Downloads | ArcoLinux
Hrm. Just got mine, and I don’t see anyone else having so many issues on the Fedora 39 Beta. It installed fine for me, but…
- The GPU seems to not work at all. I just get llvmpipe/lavapipe and most GPU accelerated stuff just fails to start. This is kind of a dealbreaker as I can’t run any of my tools.
- BIOS doesn’t seem to have a setting for making F-keys the default. This is a mild dealbreaker as I use a ton of tools that use F-keys constantly.
- Doesn’t go to sleep when I close the lid.
- Sleeps from the Gnome menu, but I can’t get it to wake back up.
- Can’t adjust screen brightness with the keys (fn or not), and the default is really dim.
- Fingerprint reader didn’t work out of the box. I updated firmware and now recognizes it, but it failed to add a single print after 5 minutes of trying. Dunno… never had one of those before, and honestly not sure I care?
Is it just working fine for everybode else?
edit: Ooooh. I think I know what happened. I couldn’t get the F39 installer to start GDM, it would just hang on a blinking cursor. So I used safe graphics mode… and apparently that installs the GRUB bootloader set up that way. I tried booting the installer again and it works now for some reason. Surely I could have fixed the bootloader config… but it was easier to just reinstall. I didn’t really have anything set up anyway.
edit 2: Yup, Reinstalling sans the “safe graphics” mode in the installer has fixed the GPU and sleep issues. Derp. I also tried the fingerprint reader again, and apparently you just need to stick your finger on the sensor like 20 times to train it? I guess it’s a Gnome issue, but that was really non-obvious. Still not quite perfect, but it mostly works now.
1 Like
- You may need to log out then back in. Make sure you are updated completely after install, there are a number of packages that are updated since initial install.
- FN+Esc will allow you to toggle FnLock.
- There is a bunch of suspend issues being looked at with newer firmware that hasn’t been released to the public yet.
- For the screen brightness, check to make sure you are updated to the latest, fiddle with the FnLock settings before using. Make sure you are on the latest kernel.
- The main thing is making sure you are updated and running linux kernel 6.5.7. You may need to update the default kernel to run.
It’s still a bit buggy, if you look at all the different threads out there, it seems we are waiting on a newer firmware version that’s not publicly available that will fix our woes.
Nah, I’ve triple checked for updates, rebooted many times at this point, etc. Kernel is indeed 6.5.7-300.fc39.x86_64. GPU just isn’t having it. Same for the screen brightness.
fn-lock: Oooooh. I guess I’ve seen that on other people’s laptops and always wondered what it was. Apple has a OS setting and my last laptop had a BIOS setting for it. Well, that’s one issue solved. I don’t suppose there is a way to make that permanent?
1 Like