Hi,
Since yesterday, OpenSuse Leap 15.5 shows a black screen with a white dash at the top left of the screen after waking the system from standby and I’ve to hit the reset button to restart.
I install updates everyday. KDE is the desktop environment. Grateful for your guidance and support.
Did you try any of Ctrl-Alt-F[1,2,3,4,5,6,7,8] to find a shell prompt or a running KDE session? Do you have another computer to try remote login?
Hi, I tried and it didn’t work. It’s frozen and I’ve to hit the reset button to start.
Perhaps this information is useful:
mamunson@dynamic-pd01:~> sudo hwinfo --gfxcard
[sudo] password for root:
10: PCI 01.0: 0300 VGA compatible controller (VGA)
[Created at pci.386]
Unique ID: vSkL.n5cd_q2Xik2
SysFS ID: /devices/pci0000:00/0000:00:01.0
SysFS BusID: 0000:00:01.0
Hardware Class: graphics card
Model: "ATI Trinity 2 [Radeon HD 7540D]"
Vendor: pci 0x1002 "ATI Technologies Inc"
Device: pci 0x9991 "Trinity 2 [Radeon HD 7540D]"
SubVendor: pci 0x1462 "Micro-Star International Co., Ltd. [MSI]"
SubDevice: pci 0x7721
Driver: "radeon"
Driver Modules: "radeon"
Memory Range: 0xd0000000-0xdfffffff (ro,non-prefetchable)
I/O Ports: 0xf000-0xf0ff (rw)
Memory Range: 0xfeb00000-0xfeb3ffff (rw,non-prefetchable)
Memory Range: 0x000c0000-0x000dffff (rw,non-prefetchable,disabled)
IRQ: 34 (12564 events)
Module Alias: "pci:v00001002d00009991sv00001462sd00007721bc03sc00i00"
Driver Info #0:
Driver Status: radeon is active
Driver Activation Cmd: "modprobe radeon"
Driver Info #1:
Driver Status: amdgpu is active
Driver Activation Cmd: "modprobe amdgpu"
Config Status: cfg=new, avail=yes, need=no, active=unknown
Primary display adapter: #10
mamunson@dynamic-pd01:~> ^C
mamunson@dynamic-pd01:~>
Try booting to multi-user.target immediately after a normal boot attempted. I often find here what you see and experience, but I can login via remote to access logs. You should be able to append 3 to the linu line after entering edit mode by striking the E key at the Grub menu before proceeding with boot, then scan sudo journalctl -b -e for clues, and or save the journal to disk to pastebin via susepaste command, or pastebin directly via:
sudo journalctl -b | susepaste -e 40320
Instead of appending 3 you should be able to append nomodeset instead and get the journal from previous boot to attach or pastebin.
I too have a Trinity, an HD7480D that works fine, but I normally never let it into standby or sleep, and do not have Plasma installed on 15.5 there:
# inxi -GSaz --vs --za --hostname
inxi 3.3.36-00 (2024-09-04)
System:
Host: ga88x Kernel: 5.14.21-150500.55.80-default arch: x86_64 bits: 64
compiler: gcc v: 7.5.0 clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/boot/vmlinuz root=LABEL=<filter> noresume
ipv6.disable=1 net.ifnames=0 mitigations=auto consoleblank=0
Desktop: TDE (Trinity) v: R14.1.2 tk: Qt v: 3.5.0 wm: Twin v: 3.0
with: kicker vt: 7 dm: 1: TDM 2: XDM Distro: openSUSE Leap 15.5
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Trinity 2 [Radeon HD 7480D]
vendor: Gigabyte driver: radeon v: kernel alternate: amdgpu
arch: TeraScale-3 code: Northern Islands process: TSMC 32nm built: 2010-13
ports: active: DVI-D-1,HDMI-A-1 empty: VGA-1 bus-ID: 00:01.0
chip-ID: 1002:9993 class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.4 compositor: Twin v: 3.0 driver: X:
loaded: modesetting dri: r600 gpu: radeon display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x2400 s-dpi: 120 s-size: 406x508mm (15.98x20.00")
s-diag: 650mm (25.6")
Monitor-1: DVI-D-1 pos: top model: Dell P2213 serial: <filter> built: 2012
res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2 size: 473x296mm (18.62x11.65")
diag: 558mm (22") ratio: 16:10 modes: max: 1680x1050 min: 720x400
Monitor-2: HDMI-A-1 mapped: HDMI-1 pos: primary,bottom model: NEC EA243WM
serial: <filter> built: 2011 res: 1920x1200 hz: 60 dpi: 94 gamma: 1.2
size: 519x324mm (20.43x12.76") diag: 612mm (24.1") ratio: 16:10 modes:
max: 1920x1200 min: 640x480
API: EGL v: 1.5 hw: drv: amd r600 platforms: device: 0 drv: r600 device: 1
drv: swrast gbm: drv: r600 surfaceless: drv: r600 x11: drv: r600
inactive: wayland
API: OpenGL v: 4.5 vendor: x.org mesa v: 22.3.5 glx-v: 1.4
direct-render: yes renderer: AMD ARUBA (DRM 2.50.0 /
5.14.21-150500.55.80-default LLVM 15.0.7) device-ID: 1002:9993
memory: 750 MiB unified: no
API: Vulkan v: 1.2.133 layers: 1 device: 0 type: cpu name: llvmpipe (LLVM
15.0.7 256 bits) driver: mesa llvmpipe v: 22.3.5 (LLVM 15.0.7)
device-ID: 10005:0000 surfaces: xcb,xlib
#
If /var/log/journal/ directory does not exist, you’ll need to sudo mkdir /var/log/journal and reboot before trying to collect journal from a prior boot as above instructed.
I’ll check. In the meantime, I’m getting: [667.431455] Freezing of tasks failed after 20.008 seconds (0 tasks refusing to freeze, wq_busy=1): when I try to put it to sleep.
I only have OpenSuse Leap 15.5 so I don’t have a multi boot option.
I tried accessing it by hitting the esc or shift key with no success
This is very generic error. Showing the full dmesg output may provide some clues (upload to https://paste.opensuse.org/).
But with some luck simply increasing timeout may work:
echo 30000 > /sys/power/pm_freeze_timeout
makes it 30 seconds.
I don’t know how multi-boot would apply here. Multi-user.target means boot system only to text mode (don’t start X), so that a broken X won’t prevent running the computer at all.
Hi, You mean like this ?
According to ChatGPT:
Option 2: Using a Boot Script
Alternatively, you can add the command to a boot script such as /etc/rc.local or create your own script in /etc/init.d.
Create a new script:
Open a terminal and create the script file:
bash
sudo nano /etc/init.d/set_freeze_timeout
Add the following content to the script:
bash
#!/bin/sh
echo 30000 > /sys/power/pm_freeze_timeout
Make the script executable:
bash
sudo chmod +x /etc/init.d/set_freeze_timeout
Register the script to run at boot:
bash
sudo ln -s /etc/init.d/set_freeze_timeout /etc/rc5.d/S99set_freeze_timeout
This will apply the setting every time the system boots into runlevel 5 (graphical mode).
Before making anything permanent it makes sense to test whether it helps at all.
I just made an update via Discover and the problem seems to have been resolved.
I did the following with no success:
I did the following:
sudo nano /etc/systemd/system/set_pm_freeze_timeout.service
[Unit]
Description=Set pm_freeze_timeout
[Service]
Type=oneshot
ExecStart=/bin/sh -c 'echo 30000 > /sys/power/pm_freeze_timeout'
[Install]
WantedBy=multi-user.target
sudo systemctl enable set_pm_freeze_timeout.service
I ran sudo smartctl -a /dev/sda and everything looks good.
Hi, I tried striking the E key at the Grub menu before proceeding with boot with no success.
Unless you add, remove or edit something before proceeding with boot, no difference can be expected.
I see nothing to suggest you followed the key part of the comment #4 instruction. You strike the E key so that you can change something before proceeding. I don’t see a standalone 3 anywhere in that first image. I recommend you remove quiet, and put 3 in its place before proceeding.
