Letoh

Members
  • Posts

    6
  • Joined

  • Last visited

Letoh's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Just tried dumping the 1070 vbios using spaceinvader's script and using it instead of the Techpowerup one. Same result. VM works using standard generic display driver and goes into a boot loop the moment the nvidia driver is loaded. The nvidia installer recognises that the card is valid, but install does not complete successfully. Again Manjaro VM works fine with the dumped vbios file. Also tried running the following lines in a script: echo 0 > /sys/class/vtconsole/vtcon0/bind echo 0 > /sys/class/vtconsole/vtcon1/bind echo efi-framebuffer.0 > /sys/bus/platform/drivers/efi-framebuffer/unbind This did not change the situation and I still cannot pass the video card to the VM and run with the nvidia driver (472.12) without the VM crashing and going into a boot loop. tower-diagnostics-20210924-0857.zip
  2. Last worked in 6.8.3. Have tried lots of options to get a Windows VM to work since 6.8.3 release but after Windows install finishes and after logging in for the first time, at point where it detects the graphics card and updates driver, it black screens and reboots. Does a boot loop from that point onward. If I change VM to VNC graphics and run DDU and remove Nvidia drivers I can get into the VM, but the moment I add a nvidia driver it boot loops again. The video card works perfectly using the same setings when passed to a Manjaro VM. Any suggestions would be awesome! I have attached diagnostics. tower-diagnostics-20210923-1620.zip
  3. I have the same issue. Setting video to VNC works fine. Using DDU and then removing all video drivers and rebooting using MSI Gaming 1070 Ti works up until the OS tries to add the video card. At that point the VM crashes and tries to reboot. Boot loop from that point on. Never gets to login. All suggestions in this thread have not worked. I have been able to load a number of Linux distros using the video card and ROM I am passing without issue. Only Windows VM on 6.9 & 6.9.1 refuse to work.
  4. Upgrade from 6.8.3 to 6.9.0 was quick and all dockers are working properly. Pass though of 2nd Video Card (Nvidea 1070) to Windows 10 VMs after upgrade is broken. Have tried to pass ROM (didn't need to in past) and even tried recreating the VM from scratch. Goes into a boot loop immediately after point where Video card is upgraded to Nvidea specific driver. If VM left as VNC (i.e. no pass through) it works fine.. Changing VM to use VNC after it is broken does not work. Goes into boot loop if VM is restarted. Have noted that in new VM (in VNC), SteelSeries Apex M800 Keyboard does not work. Had to plug in a more basic keyboard to allow setup screen data entry. I pass the USB controller to the VM and SteelSeries Rival 310 eSports Mouse plugged in on controller works fine. tower-diagnostics-20210307-1042.zip
  5. Thanks heaps for you assistance. Go file was missing and there were FSCK*.REC files on the USB flash. I have moved a copy of the go from a backup of the flash drive. Oddly there are duplicates of DISK_ASSIGNMENT.txt & machine-id files: I will remove these duplicates and give the system a reboot.
  6. Had the AMD 580 passed through to a Win 10 VM hang and freeze up my Host so had to reboot. (I am patiently awaiting the fix for this). I however have hit a issue on startup. All apps, dockers and VM did not restart this time and the web interface did not come up. To get the web interface up I had to run: nohup /usr/local/sbin/emhttp -p 80 I was then able to restart but again the emhttp did not start. I have tried updating to 2.8.2 to see if this helped but found the same on reboot and had to manually start emhttp manually. After updating I noted that all my plugins were missing and had to re-add. I was able to enable Docker and found that although my docker configs were there, I had to reload each of them from Apps get them operational. I also had to enable VMs and they seemed fine. I tried another reboot and found that again I had to manually load emhttp to get things to work. I have attached my diagnostics. Any suggesting on how to fix this? tower-diagnostics-20200208-0019.zip