TTY Screen
FiReLScar opened this issue · 7 comments
When I start the VM I get sent to a TTY and my system is halted, I renamed the VM so I could use it without passthrough to install the nvidia drivers on the guest assuming that was the issue, and windows said that it started up incorrectly and then I would try again and same result. I reinstalled windows again and it popped up a blue screen saying that some files were missing. I've seen a similar issue but the person said that they didn't dump their GPU, I did, I went to windows and tried GPU-Z but it said it didn't support dumping and then I used a different thing and got the same result the risingprismtv dude got pretty much except I didn't have to remove the beginning bytes.
I'll do an update once I've reinstalled it again and installed the drivers...
Windows is working fine now, I'm going to reboot with the passthrough and see what happens. If it doesn't work my best guess is NIC because the guide says that it can happen with the NIC card
I couldn't install the nvidia drivers due to it being an outdated version of windows (10 not 11). So I just tried to boot the vm with the passthrough and it sent me to the tty login again, I tried it without mic and it happened even faster...
Did you ever solve this issue? The same thing is happening to me.
I tried a different script and got a different result, the vm just never starts. You could try it and have better luck maybe, it's called sGPUpt its here on github. Also I have a gigabyte b450m. To get past the tty problem you just need to do sudo systemctl set-default graphical.target I believe.
I'm having the same problem. Anyone know how to fix it?
I'm having the same problem. Anyone know how to fix it?
The tty screen issue? You have to run a few commands, one to set the graphical interface (KDE, gnome, xcfe etc.. Basically the home screen) as the default instead of tty and then another to switch to it. Unsure about the whole thing tbh I reinstalled manjaro to try with a different set up (sGPUpt on github). I solved my issues with sGPUpt, it was something to do with my main xml and I still had a setting enabled in my bios. The issue I made should be there detailing what worked for my system (not guaranteed to work for yours as each pc build is different).