linux-vfio And linux-vfio-lts Go To Black Screen On Boot

Mirad · 2019-05-29 02:18:53

Hey all, thanks for the help. I'm trying to do VFIO GPU Passthrough on my system and I need to use linux-vfio for the ACS Override patch. After installing the headers and kernel, respectively, they only take me to a black screen. I decided to try linux-vfio-lts and that produced the same result. I'm not sure what I can do to fix this. Any ideas?

Here is the output of inxi -Fxz:

System:    Host: arch-desk Kernel: 5.1.4-arch1-1-ARCH x86_64 bits: 64 compiler: gcc v: 8.3.0 Desktop: KDE Plasma 5.15.5 
           Distro: Arch Linux 
Machine:   Type: Desktop Mobo: ASRock model: Z370 Killer SLI/ac serial: <filter> UEFI: American Megatrends v: P1.20 
           date: 11/27/2017 
CPU:       Topology: 6-Core model: Intel Core i7-8700K bits: 64 type: MT MCP arch: Kaby Lake rev: A L2 cache: 12.0 MiB 
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 88728 
           Speed: 800 MHz min/max: 800/4700 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 802 5: 801 6: 800 7: 800 8: 800 
           9: 800 10: 800 11: 800 12: 800 
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Vega 10 XL/XT [Radeon RX Vega 56/64] vendor: ASUSTeK driver: amdgpu 
           v: kernel bus ID: 03:00.0 
           Device-2: NVIDIA GP104 [GeForce GTX 1070] vendor: ZOTAC driver: nouveau v: kernel bus ID: 04:00.0 
           Display: x11 server: X.org 1.20.4 driver: amdgpu,modesetting resolution: <xdpyinfo missing> 
           OpenGL: renderer: Radeon RX Vega (VEGA10 DRM 3.30.0 5.1.4-arch1-1-ARCH LLVM 8.0.0) v: 4.5 Mesa 19.0.5 
           direct render: Yes 
Audio:     Device-1: Intel 200 Series PCH HD Audio vendor: ASRock driver: snd_hda_intel v: kernel bus ID: 00:1f.3 
           Device-2: Advanced Micro Devices [AMD/ATI] Vega 10 HDMI Audio [Radeon Vega 56/64] driver: snd_hda_intel v: kernel 
           bus ID: 03:00.1 
           Device-3: NVIDIA GP104 High Definition Audio vendor: ZOTAC driver: snd_hda_intel v: kernel bus ID: 04:00.1 
           Device-4: Kingston type: USB driver: hid-generic,snd-usb-audio,usbhid bus ID: 3-3:2 
           Sound Server: ALSA v: k5.1.4-arch1-1-ARCH 
Network:   Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 3.2.6-k port: f000 bus ID: 00:1f.6 
           IF: enp0s31f6 state: down mac: <filter> 
           Device-2: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi v: kernel port: d000 bus ID: 0a:00.0 
           IF: wlp10s0 state: up mac: <filter> 
Drives:    Local Storage: total: 6.60 TiB used: 331.29 GiB (4.9%) 
           ID-1: /dev/nvme0n1 vendor: Crucial model: CT1000P1SSD8 size: 931.51 GiB 
           ID-2: /dev/sda vendor: Western Digital model: WD10EZEX-00BN5A0 size: 931.51 GiB 
           ID-3: /dev/sdb vendor: Crucial model: CT250MX500SSD1 size: 232.89 GiB 
           ID-4: /dev/sdc type: USB vendor: Seagate model: BUP BK size: 4.55 TiB 
Partition: ID-1: / size: 227.49 GiB used: 160.84 GiB (70.7%) fs: ext4 dev: /dev/sdb3 
Sensors:   System Temperatures: cpu: 34.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
           GPU: device: nouveau temp: 50 C fan: 0 device: amdgpu temp: 52 C fan: 1616 
Info:      Processes: 285 Uptime: 42m Memory: 15.60 GiB used: 2.51 GiB (16.1%) Init: systemd Compilers: gcc: 8.3.0 Shell: bash 
           v: 5.0.7 inxi: 3.0.34

Last edited by Mirad (2019-05-29 02:26:57)

jasonwryan · 2019-05-29 02:21:55

Please use code tags when pasting to the boards: https://wiki.archlinux.org/index.php/Co … s_and_code

Moving to NC...

Mirad · 2019-05-29 02:29:54

My bad, I'm used to other ways of formatting code used on other forums so I couldn't figure it out. Thank you for posting the link showing how to do it on this forum!

jasonwryan · 2019-05-29 02:39:16

From that output, you are booting into the vanilla kernel, so the modules won't load.

Mirad · 2019-05-29 03:00:26

Yes, I am indeed booting into the vanilla kernel. The reason for this is because if I boot into either linux-vfio or linux-vfio-lts I am presented with a blank screen. I can't go into a tty from the screen (I tried) so I couldn't run any commands or do anything unless I booted back into the vanilla kernel.

Lone_Wolf · 2019-05-29 09:00:04

You can use journalctl -b -some_number to retrieve logs from previous boots.

see https://wiki.archlinux.org/index.php/Systemd/Journal for additional options.

Last edited by Lone_Wolf (2019-05-29 09:00:22)

Mirad · 2019-05-30 18:43:49

Here is the log from trying to boot from linux-vfio-lts: https://paste.ubuntu.com/p/4B4rm5sH6P/

The only thing I can notice thats wrong is the ACPI errors, but I've had those in the past with other distros and they haven't really affected my boot sequence in a noticeable way to my knowledge.

loqs · 2019-05-30 19:44:23

Can you post a boot log from a working boot for comparison. Also what GPU should be providing the frambuffer for the console?

Mirad · 2019-05-30 19:56:42

Yeah sure! Here's a log from a working boot (The vanilla kernel): https://paste.ubuntu.com/p/pNCjGjcm6B/

The GPU that should be providing the framebuffer is the Vega56, since nothing is plugged into the 1070 right now.

03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XL/XT [Radeon RX Vega 56/64] (rev c3)
        Subsystem: ASUSTeK Computer Inc. Vega 10 XL/XT [Radeon RX Vega 56/64]
        Kernel driver in use: amdgpu
        Kernel modules: amdgpu

loqs · 2019-05-30 20:37:51

The kernel output from vfio does not contain any entries for the admgpu module while the linux output has 30+.
Can you ssh into the system to execute commands while the system is presenting a blank screen?

Mirad · 2019-05-30 22:00:25

Yes, I have a laptop I can SSH into the system from

loqs · 2019-05-30 22:09:10

Please post the output of the following after connecting in using ssh

lspci -nnk

If the entry for the vega56 does not include "Kernel driver in use: amdgpu" but does include "Kernel modules: X" then also the output from modprobe X.

Mirad · 2019-05-31 02:46:30

Okay I just tried to ssh into the system while it was booting into linux-vfio-lts. It seems like the computer doesn't actually get to the point where it is assigned an IP address by the router, so I cannot actually ssh into it like I thought I could. I checked and if I boot into the vanilla kernel I can indeed ssh into it using that kernel. I also looked at my router's built in tool to see what devices are connected to it and my computer isn't there if it's in a vfio kernel. I also decided to check if this is just a vfio and vfio-lts problem and I don't think it is because I tried installing and booting into the linux-lts kernel and I got the same blank screen.

Last edited by Mirad (2019-05-31 02:47:33)

Mirad · 2019-05-31 20:54:58

I just checked to see if I could SSH into any of the other kernels that aren't working (linux-vfio and linux-lts), and I can't. It seems like the computer just doesn't want to work with any kernel except for the vanilla kernel which was installed when I installed Arch.

loqs · 2019-05-31 21:08:43

What about older version of linux package 5.0.Y or 4.20.Y?
If they are not in the package cache you can obtain them from Arch_Linux_Archive#/packages

Salastil · 2019-06-02 02:55:01

Have you changed the primary GPU for the computer in the BIOS? This sounds exactly like that issue. Switch it from the dedicated GPU to the onboard or whatever you intend to use as the Host GPU.

Mirad · 2019-06-02 05:33:13

Salastil wrote:

Have you changed the primary GPU for the computer in the BIOS? This sounds exactly like that issue. Switch it from the dedicated GPU to the onboard or whatever you intend to use as the Host GPU.

Yes, I already did this when I first got into linux. On my motherboard I can only choose between PCI Express and Onboard as the primary adapter (It doesn't allow me to specify which card specifically).

loqs wrote:

What about older version of linux package 5.0.Y or 4.20.Y?
If they are not in the package cache you can obtain them from Arch_Linux_Archive#/packages

I'm working on downgrading the vanilla kernel to 4.20.8, I just need to backup my system so that if the downgrade bricks my system I can get it back to a usable state easily. I'll get to you shortly on whether or not the downgrade works.

Arch Linux

#1 2019-05-29 02:18:53

linux-vfio And linux-vfio-lts Go To Black Screen On Boot

#2 2019-05-29 02:21:55

Re: linux-vfio And linux-vfio-lts Go To Black Screen On Boot

#3 2019-05-29 02:29:54

Re: linux-vfio And linux-vfio-lts Go To Black Screen On Boot

#4 2019-05-29 02:39:16

Re: linux-vfio And linux-vfio-lts Go To Black Screen On Boot

#5 2019-05-29 03:00:26

Re: linux-vfio And linux-vfio-lts Go To Black Screen On Boot

#6 2019-05-29 09:00:04

Re: linux-vfio And linux-vfio-lts Go To Black Screen On Boot

#7 2019-05-30 18:43:49

Re: linux-vfio And linux-vfio-lts Go To Black Screen On Boot

#8 2019-05-30 19:44:23

Re: linux-vfio And linux-vfio-lts Go To Black Screen On Boot

#9 2019-05-30 19:56:42

Re: linux-vfio And linux-vfio-lts Go To Black Screen On Boot

#10 2019-05-30 20:37:51

Re: linux-vfio And linux-vfio-lts Go To Black Screen On Boot

#11 2019-05-30 22:00:25

Re: linux-vfio And linux-vfio-lts Go To Black Screen On Boot

#12 2019-05-30 22:09:10

Re: linux-vfio And linux-vfio-lts Go To Black Screen On Boot

#13 2019-05-31 02:46:30

Re: linux-vfio And linux-vfio-lts Go To Black Screen On Boot

#14 2019-05-31 20:54:58

Re: linux-vfio And linux-vfio-lts Go To Black Screen On Boot

#15 2019-05-31 21:08:43

Re: linux-vfio And linux-vfio-lts Go To Black Screen On Boot

#16 2019-06-02 02:55:01

Re: linux-vfio And linux-vfio-lts Go To Black Screen On Boot

#17 2019-06-02 05:33:13

Re: linux-vfio And linux-vfio-lts Go To Black Screen On Boot

Board footer