Please confirm there isn't an open report for this issue
Summary
Using Solus since 2020 on my machine, without any heavy issues so far. Since 7.0.X display manager fails at booting but TTY access was working.
After 7.1.3 update the machine doesnt boot at all (No TTY access, no cursor, only black screen). Booting into linux-lts works fine, nothing broken.
Steps to reproduce
- Update an existing solus machine to kernel 7.1.3
- reboot
- notice black screen with no possible interaction (no cursor, no tty, nothing)
- hard power off
Expected result
Boot to GUI and login manager.
Actual result
Black screen with no possible interaction (no cursor, no tty, nothing)
Environment
Repo
Polaris (stable)
Desktop Environment
Xfce
System details
System:
Host: wuerfel-linux Kernel: 6.18.40-299.lts arch: x86_64 bits: 64
Desktop: Xfce v: 4.20.1-UNKNOWN Distro: Solus 4.9 serenity
Machine:
Type: Desktop Mobo: ASRock model: AM1B-ITX serial:
Firmware: BIOS vendor: American Megatrends v: P1.60 date: 04/29/2015
CPU:
Info: quad core AMD Athlon 5350 APU with Radeon R3 [MCP] speed (MHz):
avg: 2050 min/max: 800/2050
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Kabini [Radeon HD 8400 / R3
Series] driver: amdgpu v: kernel
Display: x11 server: X.Org v: 21.1.24 with: Xwayland v: 24.1.13 driver: X:
loaded: amdgpu unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu
resolution: 1920x1200~60Hz
API: OpenGL v: 4.6 vendor: amd mesa v: 26.1.6 renderer: AMD Radeon HD
8400 / R3 Series (radeonsi kabini ACO DRM 3.64 6.18.40-299.lts)
Info: Tools: api: eglinfo, glxinfo, vulkaninfo
de: kscreen-doctor,xfce4-display-settings gpu: radeontop
x11: xdpyinfo, xprop, xrandr
Network:
Device-1: Intel Wireless 7260 driver: iwlwifi
Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
driver: r8169
Drives:
Local Storage: total: 1.01 TiB used: 39.27 GiB (3.8%)
Info:
Memory: total: 8 GiB note: est. available: 7.2 GiB used: 4.43 GiB (61.5%)
Processes: 279 Uptime: 1h 20m Shell: Bash inxi: 3.3.41
Other comments
Booting into linux-lts works fine, nothing broken.
I hoped the update to Kernel com.solus-project.current.7.1.5-349 would fix the issue, but the problem still occurs.
Please confirm there isn't an open report for this issue
Summary
Using Solus since 2020 on my machine, without any heavy issues so far. Since 7.0.X display manager fails at booting but TTY access was working.
After 7.1.3 update the machine doesnt boot at all (No TTY access, no cursor, only black screen). Booting into linux-lts works fine, nothing broken.
Steps to reproduce
Expected result
Boot to GUI and login manager.
Actual result
Black screen with no possible interaction (no cursor, no tty, nothing)
Environment
Repo
Polaris (stable)
Desktop Environment
Xfce
System details
System:
Host: wuerfel-linux Kernel: 6.18.40-299.lts arch: x86_64 bits: 64
Desktop: Xfce v: 4.20.1-UNKNOWN Distro: Solus 4.9 serenity
Machine:
Type: Desktop Mobo: ASRock model: AM1B-ITX serial:
Firmware: BIOS vendor: American Megatrends v: P1.60 date: 04/29/2015
CPU:
Info: quad core AMD Athlon 5350 APU with Radeon R3 [MCP] speed (MHz):
avg: 2050 min/max: 800/2050
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Kabini [Radeon HD 8400 / R3
Series] driver: amdgpu v: kernel
Display: x11 server: X.Org v: 21.1.24 with: Xwayland v: 24.1.13 driver: X:
loaded: amdgpu unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu
resolution: 1920x1200~60Hz
API: OpenGL v: 4.6 vendor: amd mesa v: 26.1.6 renderer: AMD Radeon HD
8400 / R3 Series (radeonsi kabini ACO DRM 3.64 6.18.40-299.lts)
Info: Tools: api: eglinfo, glxinfo, vulkaninfo
de: kscreen-doctor,xfce4-display-settings gpu: radeontop
x11: xdpyinfo, xprop, xrandr
Network:
Device-1: Intel Wireless 7260 driver: iwlwifi
Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
driver: r8169
Drives:
Local Storage: total: 1.01 TiB used: 39.27 GiB (3.8%)
Info:
Memory: total: 8 GiB note: est. available: 7.2 GiB used: 4.43 GiB (61.5%)
Processes: 279 Uptime: 1h 20m Shell: Bash inxi: 3.3.41
Other comments
Booting into linux-lts works fine, nothing broken.
I hoped the update to Kernel com.solus-project.current.7.1.5-349 would fix the issue, but the problem still occurs.