-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't get GPU to work with hyprland #136
Comments
Just saw that it seems like I'm not using asahi edge kernel also, but I don't have any idea on how to switch to edge actually |
I'm using hyprland with GPU so it's definitely possible. I have this as my
|
Tried with your config, it cause Hyprland to crash at startup with the following logs:
This shouldn't happen tho as the normal workaround for this is normally to set May I see your full nixOS config file so I can compare to mine @rowanG077 ? I've kinda tried everything possible around the GPU options so I'm really stuck actually :( |
That's the exact error I got when my GPU wasn't functioning due to #126 Are you sure you are uptodate? What platform are you on? Can you attach your kernel log? |
I just checked and yeah I'm up to date with apple-silicon-support, I'm using the unstable nix channel also and I'm up to date with it.
|
kernel logs look clean to me. If you boot into plasma does the GPU work? The only real difference between your config and mine is that I don't use flakes and thus I use the nixpkgs hyprland. If plasma has GPU accel. Try the nixpkgs hyprland. If that works as well then it's probably mesa mismatch. I'm not super familiar with flakes, maybe it's not properly replacing/overlaying the mesa asahi over the default mesa. |
Okay so it appear that having only (not using the flakes hyprland anymore, using the nixpkgs like you) Also, I only got Plasma X11 to work through SDDM (with the GPU enabled), but I didn't managed to get plasma Wayland to work in any case, giving me this error:
How are you managing your hyprland config actually then ? |
I think you can use |
I don't use home manager so I can't really comment what goes wrong here. I just have config files. |
I'm not sure how home manager works with flakes. Does it use the nixpkgs you choose or does it use the one it specifies itself? If it's the later then you need to somehow tell home manager to not use it's own nixpkgs for the hyprland package. Which is probably what @teevik suggestion does. An easy way to tell if home manager brings it's own nixpkgs + hyprland is to check if the standard hyprland derivation differs from the one provided by home manager. |
We can't use Derivation path are differents, but the same version of Hyprland is used tho. Anyway we can confirm that the problem is inside home-manager module |
Are you sure that home-manager is using the same If you have used that, then maybe |
Personally, I have Hyprland running on a M1 Air, but it barely works. Very laggy, and screenshots are broken. No clue what causes the issues. I've noticed that when the lag spikes happen, CPU usage of Hyprland rises to around 8%, and so does usage of the asahi_sched process, when they both sit at 0.1% when it's not lagging. |
Writing this comment reminded me I have the experimental tearing enabled in Hyprland. Turning |
Okay, so Hyprland does not work for me if and only if I have Hyprland works and seems to be GPU-accelerated when I don't manage it through home-manager. |
Okay, I've had issues with Hyprland again, and came to this conclusion: When using hyprland from nixpkgs, it worked fine. When it was from their flake, it was broken. The solution? Use an overlay.
Then, just use |
I'm also seeing hyprland crashing on launch (from I'm confused as to your update -- you report that It works for me when run from a Plasma session, but crashes on launch from sddm. |
Some new finding I made |
This guy found a solution:
Source: https://github.com/mario-iml/nixos/tree/33ffeddf172d4f3ffd277f055c36dbb1ccd85179/hosts/m1 With this configuration I am able to run Hyprland with GPU on M1. |
I think this should be closed, it was figured out in a different issue |
Until now I haven't been able to start Hyprland on my M1, haven't tried any other graphical shells yet. Anyhow it strikes me as odd that in the above proposal @n3oney If you're referring to #159, I've also included that in my tests, but it doesn't seem to have me brought much closer... Possibly part of the issue may be with the fact that Hyprland has just made a transition (though I covered both env vars from #159 in my env). Or am I missing something in how (presumably the |
What I think is important is using Hyprland's overlay, otherwise it doesn't get applied |
@ppenguin In my post above I messed up the link somehow. Please have a look here https://github.com/mario-iml/nixos/tree/33ffeddf172d4f3ffd277f055c36dbb1ccd85179/hosts/m1/ I have it running for couple of days now and I am daily driving my M1 with Hyprland at work. |
Thanks, will try more as soon as I get the chance (might be only in a few days though)... Will report back. |
Using hyprland, I can't get things work with the GPU, so it is using the CPU instead and it's not really usable then.
I installed NixOS with the last released ISO found on this repo (24-12-2023)
hardware.asahi.useExperimentalGPUDriver
is on, using the overlay mode.Output of
glxinfo
:$ glxinfo | grep 'OpenGL renderer string' OpenGL renderer string: llvmpipe (LLVM 16.0.6, 128 bits)
Here is my actual config:
https://github.com/SailorSnoW/snOwOS/
Is there a conflict with something already installed on my config or maybe I did the hyprland setup in a wrong way, or missing env variables ?
The text was updated successfully, but these errors were encountered: