Booting normally results in black screen, even after upgrading kernel

[cjames]

Specs:
Kernel: 6.5.0-25-generic x86_64
Desktop: Xfce 4.18.1
Distro: Linux Mint 21.3
Mobo: X470 GAMING PLUS MAX
CPU: AMD Ryzen 5 1600
GPU: AMD Radeon R9 390


I recently installed LM-XFCE alongside Windows 10. However, when I boot up, if I try to boot LM in anything other than recovery mode, the LM logo displays for 15-30 seconds, and then the screen goes blank and my mouse and keyboard turn off.

I have already tried upgrading the kernel (per this thread: viewtopic.php?t=410244), but this makes no difference. I have checked for driver updates and I have updated all of my software. This smells like a driver issue, but I am lost for next steps.

Edit: I'm not sure if this is relevant, but I can't login to my Windows dual-boot without prioritizing the Windows Boot Manager. If I try to use GRUB to boot into Windows, Windows acts like it needs to check corrupted data. I haven't tested this very thoroughly, though.

[gomerpile]

nano /etc/xorg.conf, delete every in there. Do this in recovery

[cjames]

I booted using recovery, and there is no /etc/xorg.conf, nor does that file exist anywhere in /etc or any of its subdirectories. /etc/X11/xorg.conf.d/ is also empty.

In the logs, I see this line:

Using system config directory "/usr/share/X11/xorg.conf.d

However, when I look there, all I see is a bunch of fairly generic configuration for dealing with special hardware, none of which seems relevant to me. I've also looked in all the destinations described in the Xorg documentation, and can't find anything there, either.

Perhaps this is my problem? No xorg.conf at all?

[SMG]

I booted using recovery, and there is no /etc/xorg.conf, nor does that file exist anywhere in /etc or any of its subdirectories. /etc/X11/xorg.conf.d/ is also empty.

In the logs, I see this line:

Using system config directory "/usr/share/X11/xorg.conf.d

However, when I look there, all I see is a bunch of fairly generic configuration for dealing with special hardware, none of which seems relevant to me. I've also looked in all the destinations described in the Xorg documentation, and can't find anything there, either.

Perhaps this is my problem? No xorg.conf at all?

No, it is not a problem. There is not supposed to be an xorg.conf file.

Please boot into your system (even if it is only recovery mode) and provide your system information. Open the System Reports app and click the System Information tab on the left. Your computer's information should come up in the right pane. Then click the Copy button in the lower right and paste the results into a reply window here so we can see how Linux Mint views your hardware.

[Gcandy77]

I suspect that its your graphics drivers .. I suspect this cos I own a 290 that shares the same GCN 1.1 and has been a massive pita to use if your trying to get AMDGPU running on your system .. Ive also had instances after kernel updates that totally knacker the drivers that I have installed as they are often "not recognised" or "supported" by the latest kernel and I only find out when I reboot (Im still a linux newbie)

I have had so many black screens due to this .. that I suspect you should be able just to edit the boot command with nomodeset in order to gain access to your desktop again.

When ure at the boot menu for LM/Windows ... highlight LM and push "E" .. This should take u into something like this

Code: Select all

......
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
#GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset"
GRUB_CMDLINE_LINUX=""
......

The nomodeset is what you want to insert ... Hit save/enter n it should boot.

If it does .. I guarantee you the the gpu drivers are probably knackered again n Id recommend a purge and re-install.

Hope it helps

[SMG]

I suspect that its your graphics drivers .. I suspect this cos I own a 290 that shares the same GCN 1.1 and has been a massive pita to use if your trying to get AMDGPU running on your system

The original poster in this topic says they have R9 390 which is GCN 2.x. That still means it is experimental support for amdgpu, but it is not the same generation as yours.

I have had so many black screens due to this .. that I suspect you should be able just to edit the boot command with nomodeset in order to gain access to your desktop again.

Or you just boot in Recovery mode which automatically adds nomodeset. You can get to recovery mode by selecting the Advanced Options in grub and then selecting a kernel with (recovery mode) in its name.

If it does .. I guarantee you the the gpu drivers are probably knackered again n Id recommend a purge and re-install.

One does not "purge and re-install" drivers that come from the Linux kernel.

[cjames]

Here are the results of my System Information query:

Code: Select all

System:
  Kernel: 6.5.0-25-generic x86_64 bits: 64 compiler: N/A Desktop: Xfce 4.18.1 tk: Gtk 3.24.33
    info: xfce4-panel wm: xfwm 4.18.0 vt: 7 dm: LightDM 1.30.0 Distro: Linux Mint 21.3 Virginia
    base: Ubuntu 22.04 jammy
Machine:
  Type: Desktop Mobo: Micro-Star model: X470 GAMING PLUS MAX (MS-7B79) v: 3.0
    serial: <superuser required> UEFI: American Megatrends v: H.60 date: 06/11/2020
CPU:
  Info: 6-core model: AMD Ryzen 5 1600 bits: 64 type: MT MCP smt: enabled arch: Zen+ rev: 2 cache:
    L1: 576 KiB L2: 3 MiB L3: 16 MiB
  Speed (MHz): avg: 2075 high: 3699 min/max: 1550/3200 boost: enabled cores: 1: 1550 2: 1550
    3: 1550 4: 1480 5: 1550 6: 3694 7: 1550 8: 3699 9: 1550 10: 1550 11: 1480 12: 3698
    bogomips: 76787
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: AMD Hawaii PRO [Radeon R9 290/390] vendor: Micro-Star MSI driver: N/A pcie:
    speed: 8 GT/s lanes: 16 bus-ID: 27:00.0 chip-ID: 1002:67b1 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.4 compositor: xfwm v: 4.18.0 driver: X: loaded: ati,vesa
    unloaded: fbdev,modesetting,radeon gpu: N/A display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x286mm (20.0x11.3") s-diag: 583mm (23")
  Monitor-1: default res: 1920x1080 hz: 77 size: N/A
  OpenGL: renderer: llvmpipe (LLVM 15.0.7 256 bits) v: 4.5 Mesa 23.2.1-1ubuntu3.1~22.04.2
    direct render: Yes
Audio:
  Device-1: AMD Hawaii HDMI Audio [Radeon R9 290/290X / 390/390X] vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s lanes: 16 bus-ID: 27:00.1 chip-ID: 1002:aac8
    class-ID: 0403
  Device-2: AMD Family 17h HD Audio vendor: Micro-Star MSI driver: snd_hda_intel v: kernel pcie:
    speed: 8 GT/s lanes: 16 bus-ID: 29:00.3 chip-ID: 1022:1457 class-ID: 0403
  Sound Server-1: ALSA v: k6.5.0-25-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Micro-Star MSI
    driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 22:00.0
    chip-ID: 10ec:8168 class-ID: 0200
  IF: enp34s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 1.36 TiB used: 20.31 GiB (1.5%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 970 EVO 500GB size: 465.76 GiB speed: 31.6 Gb/s
    lanes: 4 type: SSD serial: <filter> rev: 2B2QEXE7 temp: 33.9 C scheme: GPT
  ID-2: /dev/sda vendor: Western Digital model: WD1003FZEX-00MK2A0 size: 931.51 GiB
    speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: 1A01 scheme: GPT
Partition:
  ID-1: / size: 108.72 GiB used: 10.14 GiB (9.3%) fs: ext4 dev: /dev/nvme0n1p6
  ID-2: /boot/efi size: 95 MiB used: 26.7 MiB (28.1%) fs: vfat dev: /dev/sda2
Swap:
  ID-1: swap-1 type: partition size: 31.25 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sda7
USB:
  Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 14 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Hub-2: 2-0:1 info: Super-speed hub ports: 8 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-3: 3-0:1 info: Hi-speed hub with single TT ports: 2 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Hub-4: 4-0:1 info: Super-speed hub ports: 2 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-5: 5-0:1 info: Hi-speed hub with single TT ports: 4 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002 class-ID: 0900
  Device-1: 5-1:2 info: Input Club ErgoDox Infinity
    type: Keyboard,HID,Abstract (modem),CDC-Data,Mouse driver: cdc_acm,hid-generic,usbhid
    interfaces: 7 rev: 2.0 speed: 12 Mb/s power: 500mA chip-ID: 1c11:b04d class-ID: 0300
    serial: <filter>
  Device-2: 5-2:3 info: Logitech G502 SE HERO Gaming Mouse type: Mouse,HID
    driver: hid-generic,usbhid interfaces: 2 rev: 2.0 speed: 12 Mb/s power: 300mA chip-ID: 046d:c08b
    class-ID: 0300 serial: <filter>
  Hub-6: 6-0:1 info: Super-speed hub ports: 4 rev: 3.0 speed: 5 Gb/s chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  Message: No sensor data found. Is lm-sensors configured?
Repos:
  Packages: apt: 2142
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    1: deb http: //packages.linuxmint.com virginia main upstream import backport
    2: deb http: //mirror.math.ucdavis.edu/ubuntu jammy main restricted universe multiverse
    3: deb http: //mirror.math.ucdavis.edu/ubuntu jammy-updates main restricted universe multiverse
    4: deb http: //mirror.math.ucdavis.edu/ubuntu jammy-backports main restricted universe multiverse
    5: deb http: //security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
Info:
  Processes: 360 Uptime: 1m wakeups: 0 Memory: 31.28 GiB used: 1.75 GiB (5.6%) Init: systemd
  v: 249 runlevel: 5 Compilers: gcc: 11.4.0 alt: 11/12 Client: Unknown python3.10 client
  inxi: 3.3.13

[cjames]

I edited my grub file to include nomodeset, but the same problem still occurred. I've also looked through my kernel.log, syslog, and mintsystem.log files and have not found any error reports. I have found in my syslog where I turn off the system, and even there the system doesn't seemed alarmed. One moment, stuff is successfully starting. The next, it's successfully terminating.

gpumanager.log reports this:

Vendor/Device Id: 1002:67b1
BusID "PCI:39@0:0:0"

There are some error messages in that file, but I think they are related to starting in recovery mode and not being able to access stuff that would be there in a normal mode boot.

Just to recap: I boot up, choose LM21.3 XFCE from menu, the LM logo displays while the system is loaded, and then one of a couple things happens. Most commonly, the mouse cursor appears for a second, then the screen goes totally black and reports "no signal." Sometimes, it just goes black the displays "no signal." Sometimes the login screen displays, then it starts rendering improperly, and then the screen goes black and displays "no signal."

[SMG]

Here are the results of my System Information query:

There is no graphics driver loaded because you told it not to load.

Graphics:
Device-1: AMD Hawaii PRO [Radeon R9 290/390] vendor: Micro-Star MSI driver: N/A pcie:
speed: 8 GT/s lanes: 16 bus-ID: 27:00.0 chip-ID: 1002:67b1 class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.4 compositor: xfwm v: 4.18.0 driver: X: loaded: ati,vesa
unloaded: fbdev,modesetting,radeon gpu: N/A display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x286mm (20.0x11.3") s-diag: 583mm (23")
Monitor-1: default res: 1920x1080 hz: 77 size: N/A
OpenGL: renderer: llvmpipe (LLVM 15.0.7 256 bits) v: 4.5 Mesa 23.2.1-1ubuntu3.1~22.04.2
direct render: Yes

Your system does not need a newer kernel although it should not be a problem.

Just to recap: I boot up, choose LM21.3 XFCE from menu, the LM logo displays while the system is loaded, and then one of a couple things happens. Most commonly, the mouse cursor appears for a second, then the screen goes totally black and reports "no signal." Sometimes, it just goes black the displays "no signal." Sometimes the login screen displays, then it starts rendering improperly, and then the screen goes black and displays "no signal."

You said in your first post you were getting a black screen. "No signal" is not a black screen; it is a sign of a hardware problem.

The first thing you should try is removing both ends of your monitor cable and reattaching both ends securely. Then try booting normally making sure you are NOT using nomodeset.

[cjames]

Yeah, I've already read through your Tips for Troubleshooting Graphics Issues, and I have already tried the disconnection option, but the same pattern of behavior exists.

Sorry about the black screen confusion. My screen does go black, and then a few seconds later says, "No signal" and goes into sleep mode. I figured this was the same thing as the other black screen posts here.

Do you need me to try to post what gets loaded if I don't boot in recovery mode? I'm not sure how I would do that, considering it goes black as soon as the login page pops up. Could this be an XFCE thing?

[SMG]

Sorry about the black screen confusion. My screen does go black, and then a few seconds later says, "No signal" and goes into sleep mode. I figured this was the same thing as the other black screen posts here.

The other ones just stay black usually with a blinking cursor. That is a different situation.

If you've read the Tips topic then you've seen the suggestions about trying a different cable or trying a different port on the GPU (or on the monitor if more than one is available).

Do you need me to try to post what gets loaded if I don't boot in recovery mode? I'm not sure how I would do that, considering it goes black as soon as the login page pops up.

So if you boot normally (do not use nomodeset) and get the black screen then no signal and then you boot again in recovery mode there is a way to get the data from the boot cycle that had the problem. On the second boot cycle (the one in recovery mode) run the following:

Code: Select all

journalctl -b -1 | grep -i "drm\|radeon\|amdgpu\|27:00.0\|39:00.0"

The Hawaii GPU is GCN2.x which can use amdgpu with the proper kernel parameters, but the default is to load radeon so we'll check for both. We'll also check two busIDs just in case something odd is happening.

Could this be an XFCE thing?

I wouldn't think so. Sounds more like just a graphics-related issue.

[cjames]

Alright, here is the output of the journalctl grep

Code: Select all

Mar 24 19:07:10 caleb-mint kernel: pci 0000:27:00.0: [1002:67b1] type 00 class 0x030000
Mar 24 19:07:10 caleb-mint kernel: pci 0000:27:00.0: reg 0x10: [mem 0xe0000000-0xefffffff 64bit pref]
Mar 24 19:07:10 caleb-mint kernel: pci 0000:27:00.0: reg 0x18: [mem 0xf0000000-0xf07fffff 64bit pref]
Mar 24 19:07:10 caleb-mint kernel: pci 0000:27:00.0: reg 0x20: [io  0xe000-0xe0ff]
Mar 24 19:07:10 caleb-mint kernel: pci 0000:27:00.0: reg 0x24: [mem 0xfce00000-0xfce3ffff]
Mar 24 19:07:10 caleb-mint kernel: pci 0000:27:00.0: reg 0x30: [mem 0xfce40000-0xfce5ffff pref]
Mar 24 19:07:10 caleb-mint kernel: pci 0000:27:00.0: BAR 0: assigned to efifb
Mar 24 19:07:10 caleb-mint kernel: pci 0000:27:00.0: Video device with shadowed ROM at [mem 0x000c0000-0x000dffff]
Mar 24 19:07:10 caleb-mint kernel: pci 0000:27:00.0: supports D1 D2
Mar 24 19:07:10 caleb-mint kernel: pci 0000:27:00.0: PME# supported from D1 D2 D3hot
Mar 24 19:07:10 caleb-mint kernel: pci 0000:27:00.0: vgaarb: setting as boot VGA device
Mar 24 19:07:10 caleb-mint kernel: pci 0000:27:00.0: vgaarb: bridge control possible
Mar 24 19:07:10 caleb-mint kernel: pci 0000:27:00.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none
Mar 24 19:07:10 caleb-mint kernel: pci 0000:27:00.1: D0 power state depends on 0000:27:00.0
Mar 24 19:07:10 caleb-mint kernel: pci 0000:27:00.0: Adding to iommu group 15
Mar 24 19:07:10 caleb-mint kernel: ACPI: bus type drm_connector registered
Mar 24 19:07:10 caleb-mint kernel: [drm] radeon kernel modesetting enabled.
Mar 24 19:07:10 caleb-mint kernel: radeon 0000:27:00.0: vgaarb: deactivate vga console
Mar 24 19:07:10 caleb-mint kernel: [drm] initializing kernel modesetting (HAWAII 0x1002:0x67B1 0x1462:0x2015 0x80).
Mar 24 19:07:10 caleb-mint kernel: [drm] doorbell mmio base: 0xF0000000
Mar 24 19:07:10 caleb-mint kernel: [drm] doorbell mmio size: 8388608
Mar 24 19:07:10 caleb-mint kernel: radeon 0000:27:00.0: No more image in the PCI ROM
Mar 24 19:07:10 caleb-mint kernel: radeon 0000:27:00.0: VRAM: 8192M 0x0000000000000000 - 0x00000001FFFFFFFF (8192M used)
Mar 24 19:07:10 caleb-mint kernel: radeon 0000:27:00.0: GTT: 2048M 0x0000000200000000 - 0x000000027FFFFFFF
Mar 24 19:07:10 caleb-mint kernel: [drm] Detected VRAM RAM=8192M, BAR=256M
Mar 24 19:07:10 caleb-mint kernel: [drm] RAM width 512bits DDR
Mar 24 19:07:10 caleb-mint kernel: [drm] radeon: 8192M of VRAM memory ready
Mar 24 19:07:10 caleb-mint kernel: [drm] radeon: 2048M of GTT memory ready.
Mar 24 19:07:10 caleb-mint kernel: [drm] Loading hawaii Microcode
Mar 24 19:07:10 caleb-mint kernel: [drm] Internal thermal controller with fan control
Mar 24 19:07:10 caleb-mint kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-v5pKK4/linux-hwe-6.5-6.5.0/drivers/gpu/drm/radeon/radeon_atombios.c:2717:34
Mar 24 19:07:10 caleb-mint kernel:  radeon_atombios_parse_power_table_6+0x39c/0x3d0 [radeon]
Mar 24 19:07:10 caleb-mint kernel:  radeon_atombios_get_power_modes+0x1e9/0x210 [radeon]
Mar 24 19:07:10 caleb-mint kernel:  radeon_pm_init_dpm+0x8e/0x2f0 [radeon]
Mar 24 19:07:10 caleb-mint kernel:  radeon_pm_init+0xdf/0x120 [radeon]
Mar 24 19:07:10 caleb-mint kernel:  cik_init+0x26e/0x650 [radeon]
Mar 24 19:07:10 caleb-mint kernel:  radeon_device_init+0x57e/0xaf0 [radeon]
Mar 24 19:07:10 caleb-mint kernel:  radeon_driver_load_kms+0xcc/0x300 [radeon]
Mar 24 19:07:10 caleb-mint kernel:  drm_dev_register+0x10e/0x240 [drm]
Mar 24 19:07:10 caleb-mint kernel:  radeon_pci_probe+0xec/0x180 [radeon]
Mar 24 19:07:10 caleb-mint kernel:  ? __pfx_radeon_module_init+0x10/0x10 [radeon]
Mar 24 19:07:10 caleb-mint kernel:  radeon_module_init+0x4c/0xff0 [radeon]
Mar 24 19:07:10 caleb-mint kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-v5pKK4/linux-hwe-6.5-6.5.0/drivers/gpu/drm/radeon/radeon_atombios.c:2715:55
Mar 24 19:07:10 caleb-mint kernel:  radeon_atombios_parse_power_table_6+0x384/0x3d0 [radeon]
Mar 24 19:07:10 caleb-mint kernel:  radeon_atombios_get_power_modes+0x1e9/0x210 [radeon]
Mar 24 19:07:10 caleb-mint kernel:  radeon_pm_init_dpm+0x8e/0x2f0 [radeon]
Mar 24 19:07:10 caleb-mint kernel:  radeon_pm_init+0xdf/0x120 [radeon]
Mar 24 19:07:10 caleb-mint kernel:  cik_init+0x26e/0x650 [radeon]
Mar 24 19:07:10 caleb-mint kernel:  radeon_device_init+0x57e/0xaf0 [radeon]
Mar 24 19:07:10 caleb-mint kernel:  radeon_driver_load_kms+0xcc/0x300 [radeon]
Mar 24 19:07:10 caleb-mint kernel:  drm_dev_register+0x10e/0x240 [drm]
Mar 24 19:07:10 caleb-mint kernel:  radeon_pci_probe+0xec/0x180 [radeon]
Mar 24 19:07:10 caleb-mint kernel:  ? __pfx_radeon_module_init+0x10/0x10 [radeon]
Mar 24 19:07:10 caleb-mint kernel:  radeon_module_init+0x4c/0xff0 [radeon]
Mar 24 19:07:10 caleb-mint kernel: UBSAN: array-index-out-of-bounds in /build/linux-hwe-6.5-v5pKK4/linux-hwe-6.5-6.5.0/drivers/gpu/drm/radeon/ci_dpm.c:5588:32
Mar 24 19:07:10 caleb-mint kernel:  ci_parse_power_table+0x3a2/0x3e0 [radeon]
Mar 24 19:07:10 caleb-mint kernel:  ci_dpm_init+0x1ef/0x9e0 [radeon]
Mar 24 19:07:10 caleb-mint kernel:  radeon_pm_init_dpm+0x10c/0x2f0 [radeon]
Mar 24 19:07:10 caleb-mint kernel:  radeon_pm_init+0xdf/0x120 [radeon]
Mar 24 19:07:10 caleb-mint kernel:  cik_init+0x26e/0x650 [radeon]
Mar 24 19:07:10 caleb-mint kernel:  radeon_device_init+0x57e/0xaf0 [radeon]
Mar 24 19:07:10 caleb-mint kernel:  radeon_driver_load_kms+0xcc/0x300 [radeon]
Mar 24 19:07:10 caleb-mint kernel:  drm_dev_register+0x10e/0x240 [drm]
Mar 24 19:07:10 caleb-mint kernel:  radeon_pci_probe+0xec/0x180 [radeon]
Mar 24 19:07:10 caleb-mint kernel:  ? __pfx_radeon_module_init+0x10/0x10 [radeon]
Mar 24 19:07:10 caleb-mint kernel:  radeon_module_init+0x4c/0xff0 [radeon]
Mar 24 19:07:10 caleb-mint kernel: [drm] radeon: dpm initialized
Mar 24 19:07:10 caleb-mint kernel: [drm] Found UVD firmware Version: 1.64 Family ID: 9
Mar 24 19:07:10 caleb-mint kernel: [drm] Found VCE firmware/feedback version 40.2.2 / 15!
Mar 24 19:07:10 caleb-mint kernel: [drm] GART: num cpu pages 524288, num gpu pages 524288
Mar 24 19:07:10 caleb-mint kernel: [drm] PCIE gen 3 link speeds already enabled
Mar 24 19:07:10 caleb-mint kernel: [drm] PCIE GART of 2048M enabled (table at 0x000000000030E000).
Mar 24 19:07:10 caleb-mint kernel: radeon 0000:27:00.0: WB enabled
Mar 24 19:07:10 caleb-mint kernel: radeon 0000:27:00.0: fence driver on ring 0 use gpu addr 0x0000000200000c00
Mar 24 19:07:10 caleb-mint kernel: radeon 0000:27:00.0: fence driver on ring 1 use gpu addr 0x0000000200000c04
Mar 24 19:07:10 caleb-mint kernel: radeon 0000:27:00.0: fence driver on ring 2 use gpu addr 0x0000000200000c08
Mar 24 19:07:10 caleb-mint kernel: radeon 0000:27:00.0: fence driver on ring 3 use gpu addr 0x0000000200000c0c
Mar 24 19:07:10 caleb-mint kernel: radeon 0000:27:00.0: fence driver on ring 4 use gpu addr 0x0000000200000c10
Mar 24 19:07:10 caleb-mint kernel: radeon 0000:27:00.0: fence driver on ring 5 use gpu addr 0x0000000000078d30
Mar 24 19:07:10 caleb-mint kernel: radeon 0000:27:00.0: fence driver on ring 6 use gpu addr 0x0000000200000c18
Mar 24 19:07:10 caleb-mint kernel: radeon 0000:27:00.0: fence driver on ring 7 use gpu addr 0x0000000200000c1c
Mar 24 19:07:10 caleb-mint kernel: radeon 0000:27:00.0: radeon: using MSI.
Mar 24 19:07:10 caleb-mint kernel: [drm] radeon: irq initialized.
Mar 24 19:07:10 caleb-mint kernel: [drm] ring test on 0 succeeded in 3 usecs
Mar 24 19:07:10 caleb-mint kernel: [drm] ring test on 1 succeeded in 2 usecs
Mar 24 19:07:10 caleb-mint kernel: [drm] ring test on 2 succeeded in 2 usecs
Mar 24 19:07:10 caleb-mint kernel: [drm] ring test on 3 succeeded in 3 usecs
Mar 24 19:07:10 caleb-mint kernel: [drm] ring test on 4 succeeded in 3 usecs
Mar 24 19:07:10 caleb-mint kernel: [drm] ring test on 5 succeeded in 2 usecs
Mar 24 19:07:10 caleb-mint kernel: [drm] UVD initialized successfully.
Mar 24 19:07:10 caleb-mint kernel: [drm] ring test on 6 succeeded in 17 usecs
Mar 24 19:07:10 caleb-mint kernel: [drm] ring test on 7 succeeded in 2 usecs
Mar 24 19:07:10 caleb-mint kernel: [drm] VCE initialized successfully.
Mar 24 19:07:10 caleb-mint kernel: [drm] ib test on ring 0 succeeded in 0 usecs
Mar 24 19:07:10 caleb-mint kernel: [drm] ib test on ring 1 succeeded in 0 usecs
Mar 24 19:07:10 caleb-mint kernel: [drm] ib test on ring 2 succeeded in 0 usecs
Mar 24 19:07:10 caleb-mint kernel: [drm] ib test on ring 3 succeeded in 0 usecs
Mar 24 19:07:10 caleb-mint kernel: [drm] ib test on ring 4 succeeded in 0 usecs
Mar 24 19:07:10 caleb-mint kernel: [drm] ib test on ring 5 succeeded
Mar 24 19:07:10 caleb-mint kernel: [drm] ib test on ring 6 succeeded
Mar 24 19:07:10 caleb-mint kernel: [drm] ib test on ring 7 succeeded
Mar 24 19:07:10 caleb-mint kernel: [drm] Radeon Display Connectors
Mar 24 19:07:10 caleb-mint kernel: [drm] Connector 0:
Mar 24 19:07:10 caleb-mint kernel: [drm]   DP-1
Mar 24 19:07:10 caleb-mint kernel: [drm]   HPD2
Mar 24 19:07:10 caleb-mint kernel: [drm]   DDC: 0x6530 0x6530 0x6534 0x6534 0x6538 0x6538 0x653c 0x653c
Mar 24 19:07:10 caleb-mint kernel: [drm]   Encoders:
Mar 24 19:07:10 caleb-mint kernel: [drm]     DFP1: INTERNAL_UNIPHY2
Mar 24 19:07:10 caleb-mint kernel: [drm] Connector 1:
Mar 24 19:07:10 caleb-mint kernel: [drm]   HDMI-A-1
Mar 24 19:07:10 caleb-mint kernel: [drm]   HPD3
Mar 24 19:07:10 caleb-mint kernel: [drm]   DDC: 0x6550 0x6550 0x6554 0x6554 0x6558 0x6558 0x655c 0x655c
Mar 24 19:07:10 caleb-mint kernel: [drm]   Encoders:
Mar 24 19:07:10 caleb-mint kernel: [drm]     DFP2: INTERNAL_UNIPHY2
Mar 24 19:07:10 caleb-mint kernel: [drm] Connector 2:
Mar 24 19:07:10 caleb-mint kernel: [drm]   DVI-D-1
Mar 24 19:07:10 caleb-mint kernel: [drm]   HPD1
Mar 24 19:07:10 caleb-mint kernel: [drm]   DDC: 0x6560 0x6560 0x6564 0x6564 0x6568 0x6568 0x656c 0x656c
Mar 24 19:07:10 caleb-mint kernel: [drm]   Encoders:
Mar 24 19:07:10 caleb-mint kernel: [drm]     DFP3: INTERNAL_UNIPHY1
Mar 24 19:07:10 caleb-mint kernel: [drm] Connector 3:
Mar 24 19:07:10 caleb-mint kernel: [drm]   DVI-D-2
Mar 24 19:07:10 caleb-mint kernel: [drm]   HPD6
Mar 24 19:07:10 caleb-mint kernel: [drm]   DDC: 0x6580 0x6580 0x6584 0x6584 0x6588 0x6588 0x658c 0x658c
Mar 24 19:07:10 caleb-mint kernel: [drm]   Encoders:
Mar 24 19:07:10 caleb-mint kernel: [drm]     DFP4: INTERNAL_UNIPHY
Mar 24 19:07:10 caleb-mint kernel: [drm] Initialized radeon 2.50.0 20080528 for 0000:27:00.0 on minor 0
Mar 24 19:07:10 caleb-mint kernel: [drm] fb mappable at 0xE0731000
Mar 24 19:07:10 caleb-mint kernel: [drm] vram apper at 0xE0000000
Mar 24 19:07:10 caleb-mint kernel: [drm] size 8294400
Mar 24 19:07:10 caleb-mint kernel: [drm] fb depth is 24
Mar 24 19:07:10 caleb-mint kernel: [drm]    pitch is 7680
Mar 24 19:07:10 caleb-mint kernel: fbcon: radeondrmfb (fb0) is primary device
Mar 24 19:07:10 caleb-mint kernel: radeon 0000:27:00.0: [drm] fb0: radeondrmfb frame buffer device
Mar 24 19:07:10 caleb-mint kernel: [drm] amdgpu kernel modesetting enabled.
Mar 24 19:07:10 caleb-mint kernel: amdgpu: CRAT table disabled by module option
Mar 24 19:07:10 caleb-mint kernel: amdgpu: Virtual CRAT table created for CPU
Mar 24 19:07:10 caleb-mint kernel: amdgpu: Topology: Add CPU node
Mar 24 19:07:10 caleb-mint systemd[1]: Starting Load Kernel Module drm...
Mar 24 19:07:10 caleb-mint systemd[1]: modprobe@drm.service: Deactivated successfully.
Mar 24 19:07:10 caleb-mint systemd[1]: Finished Load Kernel Module drm.

[SMG]

Alright, here is the output of the journalctl grep

There are no problems in that output.

Let's get some more details about your setup and I'll see if I have other ideas or can think of something else to check.

• To what port on the GPU are you connecting, DP-1, HDMI-A-1, or DVI-D1 or DVI-D2?
• What type of cable are you using? (example DP to DP)
• What is the make and model of the monitor?

[cjames]

I'm using HDMI-A-1, and it's HDMI to HDMI.

It's an HP 22xw (https://support.hp.com/us-en/document/c04708730).

[SMG]

... and then the screen goes blank and my mouse and keyboard turn off.

Are the mouse and keyboard still going off too?

[SMG]

Machine:
Type: Desktop Mobo: Micro-Star model: X470 GAMING PLUS MAX (MS-7B79) v: 3.0
serial: <superuser required> UEFI: American Megatrends v: H.60 date: 06/11/2020

If this is the correct link, there are quite a few BIOS/UEFI updates and one mentions, "Improved USB device compatibility" and many others have "AMD ComboAm4v2PI" updates. Sometimes updates help with Linux Mint even if they do not make a difference in Windows. Maybe it will help with the keyboard /mouse issue?

Also, maybe we can get the Xorg log from the prior boot (although it may be too late). Run

Code: Select all

cat /var/log/Xorg.0.log.old | nc termbin.com 9999

It will return with a url address that you can post in your next reply.

[cjames]

I'll update the BIOS, then.

The mouse and keyboard turn off at the exact same time that the screen shifts from "black" to "also black, but clearly doesn't have a signal now, even though the dialog box hasn't shown up."

Here's the termbin from Xorg.1.log.old: https://termbin.com/yhvu

Interestingly, I've got two xorg log files, so two xorg servers get started. Xorg.0.log.old is empty.

[SMG]

Here's the termbin from Xorg.1.log.old: https://termbin.com/yhvu

That is from a recovery mode boot cycle and is not a "fresh" Xorg start because the time is already over 1500 seconds. Hmm.

It is showing the 39

Code: Select all

[  1541.968] (--) PCI:*(39@0:0:0) 1002:67b1:1462:2015 rev 128, Mem @ 0xe0000000/268435456, 0xf0000000/8388608, 0xfce00000/262144, I/O @ 0x0000e000/256, BIOS @ 0x????????/131072

Interestingly, I've got two xorg log files, so two xorg servers get started. Xorg.0.log.old is empty.

I don't recall off-hand why that might happen. I'm pretty sure I've seen that in the past, but it's been long enough ago I don't recall why that happens.

[SMG]

Interestingly, I've got two xorg log files, so two xorg servers get started. Xorg.0.log.old is empty.

Does /var/log/Xorg.0.log also show recovery mode at the top (on the Kernel command line:)?

[cjames]

Yes. I'm going to force it to break again and post the results.