@eau
I do not have experience with OpenBSD 7.6 on Framework 13 AMD.
The symptoms you see, keys repeated etc. has been seen on Linux, and it has been in relation to some power save settings.
Disabling power save features for the keyboard seems to mitigate the problem on Linux.
Maybe you can try the same on OpenBSD.
Another mitigation is disabling the keyboard auto-repeat.
Something that might help a bit.
Disable key autorepeat:
xset r off
Enable key autorepeat
xset r on
By switching it off, it should stop the repeat aspect, but wonāt help with the missed keys
may I know the firmware version of your fingerprint scanner? I updated the bios and my fingerprint scanner wasnāt updated.
Fingerprint Sensor:
Device ID: 23ec719b6aabc2d2dac5176c232f0da7a21881b0
Summary: Match-On-Chip fingerprint sensor
Current version: 01000334
Vendor: Goodix (USB:0x27C6)
Install Duration: 10 seconds
Serial Number: UIDXXXXXXXX_XXXX_MOC_B0
GUID: 1e8c8470-a49c-571a-82fd-19c9fa32b8c3 ā USB\VID_27C6&PID_609C
Device Flags: ⢠Updatable
⢠Device can recover flash failures
⢠Signed Payload
$ fwupdmgr refresh --force
Updating lvfs
Downloading⦠[************************************** ]
Successfully downloaded new metadata: 2 local devices supported
$ fwupdmgr get-updates
Devices with no available firmware updates:
⢠Fingerprint Sensor
⢠SSD 990 PRO 1TB
Devices with the latest available firmware version:
⢠System Firmware
⢠UEFI dbx
No updates available
so if I set the battery limit to be 80%, will the battery extender be useful?
Are the percentages (above) based on the capacity of the battery or the battery limit?
same, set the limit to 80%, I recall the LED alternating occasionally before the BIOS update, but not changing color constantly. If I put it under load, it might be amber for a while then white, then amber again.
Some additional details: The charging LED was alternating at a rate under <1 second when the battery was already at 80% with the battery extender settings mentioned above. Using a 100W Anker charger.
Updated tonight on Kubuntu Plucky (Debian sid isnāt bleeding-edge enough for me), through KDE Discover. This is the first time Iāve seen a firmware update through Discover and I must say itās pretty cool!
The update went smoothly, though afterwards my particular monitor setup was acting a bit funky. Specifically, an external 4k monitor that was connected via a USB-C to DisplayPort adapter was unstable. Disconnecting and reconnecting resolved that, but it got me rejiggering my monitors to discover that my docking station now works in different configurations. I still canāt reliably get dual 4k outputs from it with Wayland (comment about Linux kernel 6.13-rc1 upcoming though - Iām currently on an Ubuntufied kernel 6.11), but I can now use one output attached to it and the other attached directly, both using the rear ports (which previously was hit or miss, mostly miss).
Hopefully this will resolve my random reboot issues, though Iāll have to do some video calls to know for sure.
We are going to hold this release at BETA and not promote to stable due to an issue we have found related to the battery extender function. The top post has been updated with more details.
If you did install the 3.06 BIOS, you may need to reinstall the AMD drivers. I found that using the AMD online installer got rid of all the weird issues I had in Windows after the update.
Hello,
AMD 7040 ryzen 7 + 64GB RAM BIOS 3.06 BETA Windows 11 23H2
I did not found anything on this topic related to the āissueā I am experiencing, so here goes:
first boot after installation - white screen - no longer occurs after another reboot
I suddenly noticed I have 8GB vRAM (compared to 4GB on 3.05) (GAMING mode)
when I change the vRAM setting in BIOS to āAUTOā, windows 11 does not boot up (white screen) consistently
I guess this means this update has a āhidden featureā of setting vRAM to 8 if >=64GB RAM, but this screws up somehow the 2GB mode
on BIOS releases, would it be possible to release a Changelog to have visibility on changes?
It would be helpful to troubleshoot side effects ( ex: and avoid silent changes on how device are reported back to the OS⦠)
When I ādisconnect batteryā and then re-power it up, most UEFI settings are remembered, but it always goes back to the default UMA setting (512MB out of 32GB), even though I set it to UMA Gaming Optimized (4GB out of 32GB).
This was a problem since the original UEFI, to the current 3.05.
Is this fixed yet? I donāt see it mentioned anywhere.
The new driver for amd is now being auto installed by windows update, so the issue with 96GB framework 13 devices is becoming a problem as windows update is bricking machines.
When is the 3.07 beta due? Itās priority has somewhat increased