LinuxQuestions.org - LCD off: during boot/after waking up from inactivity/after suspension

- Linux - Laptop and Netbook (https://www.linuxquestions.org/questions/linux-laptop-and-netbook-25/)

- - LCD off: during boot/after waking up from inactivity/after suspension (https://www.linuxquestions.org/questions/linux-laptop-and-netbook-25/lcd-off-during-boot-after-waking-up-from-inactivity-after-suspension-4175644010/)

LCD off: during boot/after waking up from inactivity/after suspension

This is my first time asking something here, so please be as tolerant as possible with any mistake that I make.

The problem:

I have installed ubuntu 18.10 and (sometimes ~70% chance) when I boot up the laptop I see a purple screen and then the lcd turns off (just black, without light).
The same happens 99% of the times, if i leave the laptop for some minutes in inactivity. When I come back, I press buttons or move the mouse and the lcd remains dead.
The same happens 99% of the times, if I wake the laptop from suspension.

While the screen is turned off, I can hear sounds if I hit the volume up/down buttons. Furthermore, I can blindly log in, then press Ctrl+Alt+T, write reboot and press enter (all these blindly), and the laptop reboots, prossibly to the same situation.

I tried the "nomodeset" trick and it worked, but I get a wrong resolution and extremely bad graphics performance, rendering the laptop unusable. The same goes for "radeon.modeset=0".

The same thing happend with Lubuntu 18.04.

Is there any possible solution to this problem? Thanks in advance for any suggestions.

Laptop model: HP pavilion dv6 1120ev
Graphics: ATI Mobility Radeon HD 4530

Code:

01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] RV710/M92 [Mobility Radeon HD 4530/4570/545v] [1002:9553]

    Subsystem: Hewlett-Packard Company Mobility Radeon HD 4530 [103c:3628]

    Kernel driver in use: radeon

    Kernel modules: radeon

Code:

dmesg | grep -i radeon



[    7.175636] [drm] radeon kernel modesetting enabled.

[    7.175725] fb: switching to radeondrmfb from VESA VGA

[    7.176813] radeon 0000:01:00.0: VRAM: 512M 0x0000000000000000 - 0x000000001FFFFFFF (512M used)

[    7.176816] radeon 0000:01:00.0: GTT: 1024M 0x0000000020000000 - 0x000000005FFFFFFF

[    7.181149] [drm] radeon: 512M of VRAM memory ready

[    7.181151] [drm] radeon: 1024M of GTT memory ready.

[    7.187901] [drm] radeon: dpm initialized

[    7.215648] radeon 0000:01:00.0: WB enabled

[    7.215652] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000020000c00 and cpu addr 0x(____ptrval____)

[    7.215655] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000020000c0c and cpu addr 0x(____ptrval____)

[    7.216130] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x000000000005c598 and cpu addr 0x(____ptrval____)

[    7.220259] radeon 0000:01:00.0: radeon: MSI limited to 32-bit

[    7.220355] radeon 0000:01:00.0: radeon: using MSI.

[    7.220386] [drm] radeon: irq initialized.

[    8.125000] [drm] radeon atom DIG backlight initialized

[    8.125001] [drm] Radeon Display Connectors

[    9.092657] fbcon: radeondrmfb (fb0) is primary device

[    9.092834] radeon 0000:01:00.0: fb0: radeondrmfb frame buffer device

[    9.105851] [drm] Initialized radeon 2.50.0 20080528 for 0000:01:00.0 on minor 0

FWIW this is an equally old Dell that has a RV730/M96-XT and works fine at 1920x1080 - but no 3D eye candy as I have no use for it. There have been regressions in the past that have caused issues with the radeon driver, but not for a couple of years. I would expect recent Ubuntu to use reasonably recent kernels (I use Fedora).
I see the following in a commented line in my grub defaults - but I don't recall the specific reasons, and as I say, it was a while ago.

Code:

radeon.dpm=0 radeon.aspm=0 radeon.runpm=0

Quote:

Originally Posted by syg00 (Post 5936073)

Code:

radeon.dpm=0 radeon.aspm=0 radeon.runpm=0

Hey, thanks for your reply. I tried what you suggested but it didn't work.

There is something new, though. I found a key combination (fn + f5 if I remember correctly) which triggers sleep mode. If I press it several times, one of them manages to wake up the screen properly.

The weird part is that it is happening randomly, in most but not all "wake up" attempts of the laptop.