!JQvnJacrwKgtkGHYHO:matrix.org

NixOS + Framework

139 Members
Discussing NixOS in the context of the Framework laptop40 Servers

Load older messages


SenderMessageTime
3 Feb 2025
@zimbatm:numtide.comJonas Chevalier changed their display name from Jonas Chevalier (FOSDEM) to Jonas Chevalier.08:23:41
5 Feb 2025
@userblackbox:matrix.orghexadecimal_dinosaur joined the room.02:51:55
7 Feb 2025
@sleepymonad:matrix.org@sleepymonad:matrix.org left the room.08:45:02
@damccull:matrix.orgdamccull

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:matrix.orgdamccullnvtop 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
@piegames:matrix.org@piegames:matrix.orgAnd once again I open my laptop to find out that the battery died overnight11:41:03
@piegames:matrix.org@piegames:matrix.org* And once again I open my Framework 16 to find out that the battery died overnight11:41:18
@piegames:matrix.org@piegames:matrix.org 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
@piegames:matrix.org@piegames:matrix.orgFor example, when I suspend the laptop with open screen, I can still resume it by touching keys or the touchpad. This should absolutely not happen11:42:54
@aktaboot:tchncs.deaktaboot @legacyPiegames I do get the behaviour you're looking for on the 13 11:45:47
@piegames:matrix.org@piegames:matrix.orgI know of several other people with spurious wakeup issues, not sure what exactly the cause is though11:46:41
@aktaboot:tchncs.deaktaboot I don't remember exactly from where i got that but:
  services.udev = {
    enable = true;
    extraRules = ''
      ACTION=="add", SUBSYSTEM=="acpi", DRIVERS=="button", ATTRS{hid}=="PNP0C0D", ATTR{power/wakeup}="disabled"
      ACTION=="add", SUBSYSTEM=="serio", DRIVERS=="atkbd", ATTR{power/wakeup}="disabled"
    '';
this is the thing that fixed it for me
11:46:54
@aktaboot:tchncs.deaktaboot(I used to have the same issue as you do)11:47:09
@aktaboot:tchncs.deaktabootnow laptop only wakes up on power button, after sleep11:47:36
@piegames:matrix.org@piegames:matrix.org
  systemd.tmpfiles.rules =
    builtins.map (dev: "w+ /sys/bus/pci/devices/${dev}/power/wakeup - - - - disabled")
      [
        "0000:00:02.2" # GPP6
        "0000:00:03.1" # GP11
        "0000:00:04.1" # GP12
        "0000:c1:00.3" # XHC0
        "0000:c1:00.4" # XHC1
        "0000:c3:00.3" # XHC3
        "0000:c3:00.4" # XHC4
        "0000:c3:00.5" # NHI0
        "0000:c3:00.6" # NHI1
      ];

This is my current, non-working attempt FWIW

11:49:38
@piegames:matrix.org@piegames:matrix.orgThanks, I'll try out yours11:49:44
@aktaboot:tchncs.deaktabootif this also works for you, we could put some info in the wiki or somewhere :)11:51:09
@piegames:matrix.org@piegames:matrix.orgOr put it into nixos-hardware11:51:20
@piegames:matrix.org@piegames:matrix.org Did not work, at least not without reboot (I think it shouldn't be required?) 11:55:33
@aktaboot:tchncs.deaktabootI'm not sure if it's required ^^12:01:35
@aktaboot:tchncs.deaktaboothttps://community.frame.work/t/tracking-framework-amd-ryzen-7040-series-lid-wakeup-behavior-feedback/12:05:47
@piegames:matrix.org@piegames:matrix.orgit seems to be12:21:05
@piegames:matrix.org@piegames:matrix.orgAlso, it seems to indeed have fixed my issue with wakeup devices, many thanks12:21:38
@piegames:matrix.org@piegames:matrix.orgLet's hope that I'll encounter much less dead laptops in the morning now12:21:59
@aktaboot:tchncs.deaktaboot oh, it's also already in the wiki, although, the title is kinda weird 12:26:10
@aktaboot:tchncs.deaktabootwell it's not really the same rules at all12:26:55
@piegames:matrix.org@piegames:matrix.org"Putting your Framework in a backpack can cause it to wake up due to the screen flexing onto the keyboard" though that's exactly what's happening to me. Sometime I open the laptop and there are even a couple of characters typed into the login screen12:27:29
@aktaboot:tchncs.deaktabootokay that's fair :)12:28:21
@amy:catgirl.cloudAmy joined the room.17:30:57
@amy:catgirl.cloudAmySince it seems to be such a widespread issue, I was hoping to land something like that in nixos-hardware, but I kind of fell off the internet for a while. The beginning of my effort was https://community.frame.work/t/responded-waking-from-suspend-w-lid-closed/47497/7117:46:35

Show newer messages


Back to Room ListRoom Version: 10