Soo… attempting to show off the laptop to my co-workers resulted a strange sequence of events.
All was going great until, I connected it to one of those curved high resolution screens with build-in ethernet/camera/speakers.
- Plugging it into usb-c top left it switched to using the external monitor only at a very low resolution (charging started, I did not check to see if any of the peripherals were recognized)
- At this time I believe the framework keyboard and track-pad stopped responding. so I connected an apple keyboard using a usb-c (lower-right) to lightning cable. and a mouse on usb-a (lower-left) and could continue using the system.
- Then plugged it into the usb-c top-right and the screen used full resolution.
- At full resolution I thought it be sweet to show off some Minecraft graphics and speed. The game loaded perfectly and started generating terrain of a new off-line world.
- As soon as I started flying around the epileptic white bars started to interfere with the graphics.
- Using F3 Minecraft showed me it was running low on memory, so I assigned more and restarted to no avail.
- At this point the laptop decided to go into sleep mode every couple of seconds (now the fingerprint module really helped to get back into the system quickly). changing the power-saving mode made no difference.
- As the systems behaviour (also white bars outside of Minecraft and non-responsive keyboard/track-pad and the going to sleep) I decided to reboot the system.
- After rebooting the keyboard/track-pad was still not responding.
- Now I decided the demo was over and I just completely shut it down and put it away.
Back at home I booted up and all appears to be fine again (keyboard/trackpad are functional again… no more sudden sleeping)
As far as I can find… most of the above is already known by the community/framework and is being worked on to resolve in various other threads.
- Keyboard stopped working - #11 by SilverSasquatch
- [TRACKING] Graphical corruption in Fedora 39 (AMD 3.03 BIOS) - #112 by framy
Only the falling asleep after a couple of seconds I have not found a precedent for.