| 29 Jan 2025 |
 skttlock | Hey Matt! Thanks for your work. Wanted to add that I personally had no issues with Wi-Fi and Bluetooth- no need for a workaround (GNOME). I believe the same goes for the finger print reader. FW 13inch Intel i7 11th gen. DIY Edition.
Thanks again! | 22:16:50 |
 Matt H. - on PTO | Okay, so we feel like I can change these to working across the board? AMD offerings and Intel 13th through 11th? | 22:22:09 |
| Matt H. - on PTO | Nothing has changed yet, it's still pending, so I can pound out the changes today before the web team even sees my work order. | 22:22:44 |
| Matt H. - on PTO | * Okay, so we feel like I can change these to working across the board? AMD offerings and Intel 13th through 11th? Wifi/bluetooth, FPReader. | 22:23:21 |
| Matt H. - on PTO | AMD is Mediatek wifi, Intel is Intel wifi just for situational awarenes. | 22:24:23 |
| Matt H. - on PTO | * AMD is Mediatek wifi, Intel is Intel wifi just for situational awareness. | 22:24:30 |
| 30 Jan 2025 |
|  laurynasp joined the room. | 08:56:07 |
| 31 Jan 2025 |
|  quin joined the room. | 13:27:37 |
|  Jonas Chevalier changed their display name from Jonas Chevalier to Jonas Chevalier (FOSDEM). | 19:12:09 |
| quin changed their display name from worm_with_boots to quin. | 23:00:09 |
| 1 Feb 2025 |
| skttlock | Whoops! Just checked for fingerprint under user settings in GNOME 40-something. Not there. Sounds like it's a simple enabling of fprintd service to get it working though. | 00:28:00 |
 Daniel Schaefer (Framework) | Try fprintd-enroll.
If that works it's a gnome problem | 00:36:07 |
 Infinidoge 🏳️⚧️ | If you used a different distro or OS before, you may need to reset the finger print sensor | 00:36:40 |
| Daniel Schaefer (Framework) | Fingerprint reader should not have any problems working.
We added our USB PID three years ago, so any recent software should have support.
But a windows-only firmware shipped during a few weeks last year. Check if fwupd says you're on the latest firmware | 00:38:01 |
| Infinidoge 🏳️⚧️ | (It's... weird. There is a script floating around from when I ran into the reset issue. Might no longer be relevant, but I keep a copy of the script just in case) | 00:39:02 |
 @ahoneybun:matrix.org | Wait is that nix-minecraft @[Infinidoge 🏳️⚧️] ? | 00:40:23 |
| Infinidoge 🏳️⚧️ | Perhaps :) | 00:40:51 |
| @ahoneybun:matrix.org | Coolio! | 00:41:08 |
| @ahoneybun:matrix.org | Redacted or Malformed Event | 00:45:09 |
| @ahoneybun:matrix.org | 
Download tenor_gif3434478361256336962.gif | 00:45:15 |
| @ahoneybun:matrix.org | In reply to @ctsdownloads:fedora.im
screencapture-staging-frame-work-linux-2025-01-29-13_21_01.png It's... beautiful | 00:45:29 |
|  myhlamaeus joined the room. | 18:34:10 |
| 3 Feb 2025 |
| Jonas Chevalier changed their display name from Jonas Chevalier (FOSDEM) to Jonas Chevalier. | 08:23:41 |
| 5 Feb 2025 |
|  hexadecimal_dinosaur joined the room. | 02:51:55 |
| 7 Feb 2025 |
|  sleepymonad left the room. | 08:45:02 |
 damccull | Recently I've been having dgpu crashes that take out the whole computer, and then I get behavior where the dgpu doesn't show up or load properly when rebooting or coming back online. The support folks at framework don't seem to know what's going on. They say it's an OS config error. It happens on both ubuntu and fedora live disks though, as well as my main nixos install. It started happening about 2-3 weeks after I made my latest config change and I hadn't changed or updated anything since then. Here's the only related dmesg stuff I can find on it.
[ 3.828129] amdgpu 0000:03:00.0: amdgpu: get invalid ip discovery binary signature
[ 3.828166] [drm:amdgpu_discovery_set_ip_blocks [amdgpu]] *ERROR* amdgpu_discovery_init failed
[ 3.828419] amdgpu 0000:03:00.0: amdgpu: Fatal error during GPU init
[ 3.828477] amdgpu 0000:03:00.0: amdgpu: amdgpu: finishing device.
[ 3.828621] amdgpu 0000:03:00.0: probe with driver amdgpu failed with error -22
Anyone seen this or know what's going on? Happy to provide further logs too.
| 11:49:39 |
| damccull | nvtop doesn't show the dgpu at all after this. Even after a reboot. It was gone for about a week and then came back by itself two days ago, and now I just had it crash on me again and I can't get the GPU to show up again. | 11:51:24 |
| 8 Feb 2025 |
 legacyPiegames | And once again I open my laptop to find out that the battery died overnight | 11:41:03 |
| legacyPiegames | * And once again I open my Framework 16 to find out that the battery died overnight | 11:41:18 |
| legacyPiegames | Is there a way to get it to resume from suspend only if I press the power button? These spurious wakeups are really annoying but even more annoying to me is that disabling all wakeup sources in /proc/acpi/wakeup has no effect | 11:42:11 |
