Black Screen, No input signal Liquorix 6.12 and 6.13 - AMD6700XT
gingerbatman
Status: New User - Welcome
Joined: 15 Mar 2025
Posts: 3
Reply Quote
Hey All,

I was using Liquorix kernals for ages until 6.12 came out and now I cant see anything on the screen once it boots.
Kernal 6.11 works fine, I also tested XanMod works fine on 6.12 and 6.13 along with Stock 6.8 I have no issues.

Useing anything Liquorix 6.12 and above it boots as normal and shows the "splash" screen text and when it would typically show the Mint logo the screen goes dark and I get a no input signal on my monitor and never shows my desktop.

Tried simplifying my monitor setup and directly connected 1 monitor using a known good cable and same issue.

Any help or obvious errors in the logs I missed would be greatly appreciated as I would prefer to use the Liquorix kernal

Heres the inxi from Xanmod kernal as I dont have Liquorix 6.11 anymore

Along with the journalctl -b -l -k output : https://pastebin.com/kUU7kkZ3


:: Code ::

System:
  Kernel: 6.13.4-x64v3-xanmod1 arch: x86_64 bits: 64 compiler: gcc v: 14.2.0
  Desktop: Cinnamon v: 6.4.8 tk: GTK v: 3.24.41 wm: Muffin dm: LightDM
    Distro: Linux Mint 22.1 Xia base: Ubuntu 24.04 noble
Machine:
  Type: Desktop Mobo: Micro-Star model: MAG X570S TOMAHAWK MAX WIFI (MS-7D54)
    v: 1.0 serial: <superuser required> UEFI: American Megatrends LLC. v: 1.A0
    date: 07/16/2024
CPU:
  Info: 6-core AMD Ryzen 5 5600X [MT MCP] arch: Zen 3+ speed (MHz): avg: 3164
    min/max: 550/4651
Graphics:
  Device-1: AMD Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT]
    vendor: Gigabyte driver: amdgpu v: kernel arch: RDNA-2 pcie: speed: 16 GT/s
    lanes: 16 ports: active: HDMI-A-1,HDMI-A-2 empty: DP-1,DP-2,Writeback-1
    bus-ID: 2f:00.0 chip-ID: 1002:73df
  Device-2: ARC Camera - 1080p driver: snd-usb-audio,uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 1-1.2.1:8 chip-ID: 05a3:9332
  Display: x11 server: X.Org v: 21.1.11 with: Xwayland v: 23.2.6 driver: X:
    loaded: amdgpu unloaded: fbdev,modesetting,radeon,vesa dri: radeonsi
    gpu: amdgpu display-ID: :0 screens: 1
  Screen-1: 0 s-res: 3640x1920 s-dpi: 96
  Monitor-1: HDMI-A-1 mapped: HDMI-A-0 pos: primary,bottom-r
    model: BenQ EX2780Q res: 2560x1440 dpi: 109 diag: 685mm (27")
  Monitor-2: HDMI-A-2 mapped: HDMI-A-1 pos: top-left model: Samsung S24F350
    res: 1080x1920 dpi: 94 diag: 598mm (23.5")
  API: EGL v: 1.5 platforms: device: 0 drv: radeonsi device: 1 drv: swrast
    gbm: drv: kms_swrast surfaceless: drv: radeonsi x11: drv: radeonsi
    inactive: wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: PPA glx-v: 1.4
    direct-render: yes renderer: AMD Radeon RX 6700 XT (radeonsi navi22 LLVM
    19.1.7 DRM 3.60 6.13.4-x64v3-xanmod1) device-ID: 1002:73df
  API: Vulkan v: 1.3.275 surfaces: xcb,xlib device: 0 type: discrete-gpu
    driver: N/A device-ID: 1002:73df device: 1 type: cpu driver: N/A
    device-ID: 10005:0000
Network:
  Device-1: Realtek RTL8125 2.5GbE vendor: Micro-Star MSI driver: r8169
    v: kernel pcie: speed: 5 GT/s lanes: 1 port: f000 bus-ID: 26:00.0
    chip-ID: 10ec:8125
  Device-2: Intel Wi-Fi 6E AX210/AX1675 2x2 [Typhoon Peak] driver: iwlwifi
    v: kernel pcie: speed: 5 GT/s lanes: 1 bus-ID: 28:00.0 chip-ID: 8086:2725
Drives:
  Local Storage: total: 3.41 TiB used: 2.25 TiB (66.1%)
Info:
  Memory: total: 32 GiB available: 31.27 GiB used: 2.23 GiB (7.1%)
  Processes: 369 Power: uptime: 2m wakeups: 0 Init: systemd v: 255
    target: graphical (5) default: graphical
  Packages: 2526 pm: dpkg pkgs: 2515 pm: flatpak pkgs: 11 Compilers:
    gcc: 13.3.0 Shell: fish v: 3.7.0 running-in: gnome-terminal inxi: 3.3.34


Thank you!!
Back to top
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 4132
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
Good bug report.

Try adding one more thing:

cat /var/log/Xorg.0.log | tail -n 50. Or just the whole file.

For display start failures, generally the actual error is in the last 50 lines of the xorg log.

Double check you don't have a hardcoded monitor location in xorg.conf file, or in sub files.

Since you have amdgpu, that gets rid of the main common cause for desktop failing to start but booting fine.

You should be able to ctrl + alt + f1 or f2 to the console screen, where you can login and grab the data on failure.
Back to top
stevenpusser
Status: Contributor
Joined: 14 Jan 2017
Posts: 94
Reply Quote
It's weird, but when I first ported over the first 6.13-1 for MX Linux, installed, and booted to it, I also got a black screen the first few times, with a little flashing dash cursor in the upper left. After a few hard resets and a boot to the 6.12 kernel, it cleared up and has never recurred on 6.13. This is also on amdgpu with a backported Mesa and firmware on top of Bookworm.

:: Code ::
Graphics:
  Device-1: NVIDIA GA107M [GeForce RTX 3050 Ti Mobile] vendor: Dell
    driver: nvidia v: 535.216.03 arch: Ampere pcie: speed: 2.5 GT/s lanes: 8
    bus-ID: 01:00.0 chip-ID: 10de:25a0
  Device-2: AMD Cezanne [Radeon Vega Series / Radeon Mobile Series]
    vendor: Dell driver: amdgpu v: kernel arch: GCN-5 pcie: speed: 8 GT/s
    lanes: 16 ports: active: DP-1 off: eDP-1 empty: none bus-ID: 05:00.0
    chip-ID: 1002:1638 temp: 67.0 C
  Device-3: Microdia Integrated_Webcam_HD type: USB driver: uvcvideo
    bus-ID: 1-4:4 chip-ID: 0c45:6720
  Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9
    compositor: kwin_x11 driver: X: loaded: amdgpu,nvidia dri: radeonsi
    gpu: amdgpu display-ID: :0 screens: 1
  Screen-1: 0 s-res: 2560x1440 s-dpi: 96
  Monitor-1: DP-1 mapped: DisplayPort-0 pos: primary model: CS27QH
    res: 2560x1440 dpi: 109 diag: 685mm (27")
  Monitor-2: eDP-1 mapped: eDP note: disabled model: ChiMei InnoLux 0x1522
    res: 2560x1440 dpi: 142 diag: 394mm (15.5")
  API: OpenGL v: 4.6 Mesa 24.2.8-1mx23ahs renderer: AMD Radeon Graphics
    (radeonsi renoir LLVM 15.0.6 DRM 3.61 6.13.7-1-liquorix-amd64)
    direct-render: Yes

Back to top
gingerbatman
Status: New User - Welcome
Joined: 15 Mar 2025
Posts: 3
Reply Quote
Thanks guys I appreciate your response!

:: Quote ::
You should be able to ctrl + alt + f1 or f2 to the console screen, where you can login and grab the data on failure.

:: Quote ::
I also got a black screen the first few times, with a little flashing dash cursor in the upper left


I saw this in a few other posts but I dont even get a cursor and I did try to change the TTY to get more info but does nothing like the screen just went into standby.

I was temped to setup an SSH connection to see if it actually boots up and see if I could pull anything.
Looking at the Xorg.0.log.old I think there might be something interesting.
It mentions no screens found and Screen 0 deleted because of no matching config section.

It looks like the Liquoix kernal doesnt find /dev/dri/card0 and then gives up where my current kernal sees my card is at /dev/dri/card1 and continues with that instead, I dont know if that makes sense or not just an observation between the 2 log files.

I put the full file on pastebin again - Xorg.0.Log.old --> https://pastebin.com/9eRFMnkE
The most recent successful boot Xorg.0.log --> https://pastebin.com/xqmXQ3Gu


:: Code ::
[     8.823] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[     8.823] (II) FBDEV: driver for framebuffer: fbdev
[     8.823] (II) VESA: driver for VESA chipsets: vesa
[     8.823] (WW) xf86OpenConsole: setpgid failed: Operation not permitted
[     8.823] (WW) xf86OpenConsole: setsid failed: Operation not permitted
[     8.823] (EE) open /dev/dri/card0: No such file or directory
[     8.823] (WW) Falling back to old probe method for modesetting
[     8.823] (EE) open /dev/dri/card0: No such file or directory
[     8.823] (II) Loading sub module "fbdevhw"
[     8.823] (II) LoadModule: "fbdevhw"
[     8.823] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[     8.823] (II) Module fbdevhw: vendor="X.Org Foundation"
[     8.823]    compiled for 1.21.1.11, module version = 0.0.2
[     8.823]    ABI class: X.Org Video Driver, version 25.2
[     8.823] (EE) Unable to find a valid framebuffer device
[     8.823] (WW) Falling back to old probe method for fbdev
[     8.823] (II) Loading sub module "fbdevhw"
[     8.823] (II) LoadModule: "fbdevhw"
[     8.823] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[     8.823] (II) Module fbdevhw: vendor="X.Org Foundation"
[     8.823]    compiled for 1.21.1.11, module version = 0.0.2
[     8.823]    ABI class: X.Org Video Driver, version 25.2
[     8.823] (EE) open /dev/fb0: No such file or directory
[     8.823] vesa: Ignoring device with a bound kernel driver
[     8.823] (EE) Screen 0 deleted because of no matching config section.
[     8.823] (II) UnloadModule: "modesetting"
[     8.823] (EE) Screen 0 deleted because of no matching config section.
[     8.823] (II) UnloadModule: "fbdev"
[     8.823] (II) UnloadSubModule: "fbdevhw"
[     8.823] (II) UnloadSubModule: "fbdevhw"
[     8.823] (II) UnloadSubModule: "fbdevhw"
[     8.823] (EE) Screen 0 deleted because of no matching config section.
[     8.823] (II) UnloadModule: "vesa"
[     8.823] (EE) Device(s) detected, but none match those in the config file.
[     8.823] (EE)
Fatal server error:
[     8.823] (EE) no screens found(EE)
[     8.823] (EE)
Please consult the The X.Org Foundation support
    at http://wiki.x.org
 for help.
[     8.823] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[     8.823] (EE)
[     8.823] (EE) Server terminated with error (1). Closing log file.

Back to top
damentz
Status: Assistant
Joined: 09 Sep 2008
Posts: 1159
Reply Quote
If your previous boot was on Liquorix and you successfully boot into a different kernel, you can run sudo journalctl -k -b -1 to retrieve all the kernel logs from the previous boot.

Try and that and post it on some type of paste bin service for us to look at.
Back to top
gingerbatman
Status: New User - Welcome
Joined: 15 Mar 2025
Posts: 3
Reply Quote
Hey damentz,

I put one in my original post but I done another one here for you to check - https://pastebin.com/jkhZh8e2

Thanks for your help!
Back to top
Display posts from previous:   

All times are GMT - 8 Hours