You are not logged in.
So I have this Radeon RX570, and am using the amdgpu driver. DVI is fine, and HDMI works during UEFI, but once it passes to Arch booting, the HDMI is disconnected, and cannot be enabled through a/xrandr. I've tried re-plugging the device, re-installing the driver, to no avail.
EDIT: Solution
I do not have a Xorg.conf, or any uncommented xrandr lines.
Here is the Xorg.log. Any assistance here would be very much appreciated.
Last edited by jowijo (2019-05-27 00:11:44)
Offline
Are there interesting messages in "journalctl -k" or "journalctl -b"?
In your Xorg log, the driver sees absolutely nothing about the HDMI monitor. It says nothing is connected to that output.
About the text console, you can find what's seen there in /sys/class/drm/. Each output of the card has a folder there, and you can see what's connected like this:
grep . /sys/class/drm/*/status
Offline
Output of grep:
/sys/class/drm/card0-DP-1/status:disconnected
/sys/class/drm/card0-DP-2/status:disconnected
/sys/class/drm/card0-DP-3/status:disconnected
/sys/class/drm/card0-DVI-D-1/status:connected
/sys/class/drm/card0-HDMI-A-1/status:disconnected
As for the journal, nothing seemingly related to the graphics card.
Offline
Please post full lspci -k , dmesg and/or journalctl -b outputs.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Please post full lspci -k , dmesg and/or journalctl -b outputs.
lspci -k
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers (rev 07)
Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers
Kernel driver in use: skl_uncore
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 07)
Kernel driver in use: pcieport
00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller (rev 31)
Subsystem: ASUSTeK Computer Inc. 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
00:16.0 Communication controller: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 (rev 31)
Subsystem: ASUSTeK Computer Inc. 100 Series/C230 Series Chipset Family MEI Controller
Kernel driver in use: mei_me
Kernel modules: mei_me
00:17.0 SATA controller: Intel Corporation Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode] (rev 31)
Subsystem: ASUSTeK Computer Inc. Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode]
Kernel driver in use: ahci
Kernel modules: ahci
00:1c.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #5 (rev f1)
Kernel driver in use: pcieport
00:1d.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #9 (rev f1)
Kernel driver in use: pcieport
00:1d.1 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #10 (rev f1)
Kernel driver in use: pcieport
00:1f.0 ISA bridge: Intel Corporation H110 Chipset LPC/eSPI Controller (rev 31)
Subsystem: ASUSTeK Computer Inc. H110 Chipset LPC/eSPI Controller
00:1f.2 Memory controller: Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller (rev 31)
Subsystem: ASUSTeK Computer Inc. 100 Series/C230 Series Chipset Family Power Management Controller
00:1f.3 Audio device: Intel Corporation 100 Series/C230 Series Chipset Family HD Audio Controller (rev 31)
Subsystem: ASUSTeK Computer Inc. 100 Series/C230 Series Chipset Family HD Audio Controller
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:1f.4 SMBus: Intel Corporation 100 Series/C230 Series Chipset Family SMBus (rev 31)
Subsystem: ASUSTeK Computer Inc. 100 Series/C230 Series Chipset Family SMBus
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] (rev ef)
Subsystem: XFX Pine Group Inc. Radeon RX 570
Kernel driver in use: amdgpu
Kernel modules: amdgpu
01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]
Subsystem: XFX Pine Group Inc. Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
Subsystem: ASUSTeK Computer Inc. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
Kernel driver in use: r8169
Kernel modules: r8169
Offline
[ 0.163641] Kernel command line: initrd=\initramfs-linux.img root=/dev/sda2 rw
Looks like you haven't configured Microcode updating ?
[ 0.236433] smpboot: CPU0: Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz (family: 0x6, model: 0x5e, stepping: 0x3)
The intel core i5-6500 does come with an integrated gpu, but lspci doesn't list one .
Did you disable it in bios / uefi firmware or do you have another processor ?
What is brand and model of your motherboard ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Looks like you haven't configured Microcode updating ?
No, I have not. First I'm learning about this, tbh.
Did you disable it in bios / uefi firmware or do you have another processor ?
Yes, it is set to exclusively use the PCIe GPU (Radeon).
What is brand and model of your motherboard ?
ASRock B85M-ITX
Offline
It's mentioned clearly in installation guide since december 2018. Before that is was not hard to miss it.
While it may not be related to the current issue, all systems should use it now.
Please configure microcode updating.
The latest bios / uefi firmware for that motherboard is 2.50 from jan 20 2016, are you running that ?
Your system should have 2 hdmi connectors : one from the MB and one from the videocard.
please verify you do use the correct one.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
It's mentioned clearly in installation guide since december 2018. Before that is was not hard to miss it.
While it may not be related to the current issue, all systems should use it now.
Please configure microcode updating.The latest bios / uefi firmware for that motherboard is 2.50 from jan 20 2016, are you running that ?
Your system should have 2 hdmi connectors : one from the MB and one from the videocard.
please verify you do use the correct one.
EDIT: Microcode updated and EFISTUB configured.
Also I can assure you the HDMI connection is in the graphics card, and not the motherboard.
EDIT 2: Interesting. When I connected my TV to the HDMI out, it works flawlessly. Then connecting the Cintiq to it, it worked also, though it was rather bright, but arandr couldn't specify a resolution. Dropping out of X and back in once again renders the tablet screen "disconnected".
Last edited by jowijo (2019-05-26 22:30:25)
Offline
I guess this is a bug in the amdgpu kernel module. This wouldn't be unusual. One thing you can try is, boot with a parameter "amdgpu.dc=0" on the kernel command line. The driver will then use different code for the output to the monitors.
The bug tracker for the amdgpu kernel module is here:
https://bugs.freedesktop.org/buglist.cg … ate%20DESC
You might find an interesting bug report when you look around there, for example there's one here about HDMI problems:
Offline
I guess this is a bug in the amdgpu kernel module. This wouldn't be unusual. One thing you can try is, boot with a parameter "amdgpu.dc=0" on the kernel command line. The driver will then use different code for the output to the monitors.
The bug tracker for the amdgpu kernel module is here:
https://bugs.freedesktop.org/buglist.cg … ate%20DESC
You might find an interesting bug report when you look around there, for example there's one here about HDMI problems:
Well, looks like that kernel parameter did the trick, thank you!
Offline