-
Notifications
You must be signed in to change notification settings - Fork 38
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
Black screen before SDDM session restarts #34
Comments
You can try running the commands from Also, you can try moving the command to unload kernel module below and comment the line to unbind the framebuffer as suggested in #9. |
I moved the line in the start hook and nothing changed. Error log gave the same issue, "shutting down, reason=failed" |
Turns out I was being a big goober and forgot the enable the default network. This is the new log, it black screened and hung until I did a hard shutdown. |
I guess the VM is working (seeing at the log, it didn't terminate) but you aren't getting any display. Can you provide the log after removing Display Spice?
Those permissions are fine. You don't have to worry about permissions on |
Here is the new log with Display Spice gone
Gotcha, I was worried since the efi-framebuffer command kept giving permission errors |
Not really sure what's the issue. |
❯ systemctl status libvirtd Nov 13 20:55:32 serpentbox libvirtd[6473]: this function is not supported by the connection driver: virConnectGetAllDomainStats |
Not sure why it's failing.. I tried to reproduce Try simplifying the start script to: #!/bin/sh
set -x
systemctl stop display-manager
systemctl --user -M lucian@ stop plasma*
modprobe -r amdgpu |
Result is a black screen which hangs until I reboot. |
No idea what might be the issue as log has no error.. exec 19>/home/YOUR_USERNAME/startlog
BASH_XTRACEFD=19
set -x This should create startlog file incl. the status of each command.. |
startlog.txt |
The commands seem to be working as expected. Not sure what's causing the issue.. |
I might reinstall a fresh linux soon, Wayland Plasma has been occasionally hard crashing when I play games recently. There could be something wrong with my install and I'm not tech savvy enough to diagnose it. I'll update this issue if/when I'm on a new install. |
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
I'm currently busy, if I have to time to try this again I can reopen the issue or open another one. Thank you for your help. |
I've have a new install on EndeavorOS with Plasma Wayland, and I still cannot get the vm to work. I wonder if having a DP monitor is part of it? I also have a second HDMI screen, both are plugged into my GPU. |
Using the simplified start script I get a new issue. It just hangs on this now |
I've following the instructions, only skipping the vBIOS stuff and audio.
When I start the VM the screen goes black, I hear my GPU fans turn on for a second, then they turn off before I am returned to my SDDM login screen. I'm not too technical and the error message is unclear so I don't know what's going wrong.
XML: https://pastebin.com/YMiRmxLS
LOG: GPU_Passthrough.log
Hooks:
qemu.txt
start.txt
stop.txt
The text was updated successfully, but these errors were encountered: