Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

D9 Cinnamon Hardware rendering gives a black screen

Need help with peripherals or devices?
Post Reply
Message
Author
larienna
Posts: 106
Joined: 2014-09-27 20:54

D9 Cinnamon Hardware rendering gives a black screen

#1 Post by larienna »

The only modifications I made to my system lately is building and installing Python 3.9 in order to make Meson work. Now I cannot boot in Cinnamon using Hardware accelerated rendering. It will only display a black screen with a mouse pointer. I can use Software rendering, but that put my fan at full spin as 50%+ of the CPU is used by Cinnamon. So I reverted to using Mate.

I have an HP Pavillion G6 with Debian 9 installed. I tried reinstalling the graphic drivers using:

Code: Select all

sudo apt-get install --reinstall firmware-amd-graphics
and it does not work (the non-free repo are setup in sources.list). I tried to search for a solution, the problem is reported in other threads, but I cannot find any solution. Here are a few diagnostic commands:

Code: Select all

sudo lshw -c video
  *-display                 
       description: VGA compatible controller
       product: Trinity [Radeon HD 7520G]
       vendor: Advanced Micro Devices, Inc. [AMD/ATI]
       physical id: 1
       bus info: pci@0000:00:01.0
       version: 00
       width: 32 bits
       clock: 33MHz
       capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
       configuration: driver=radeon latency=0
       resources: irq:34 memory:e0000000-efffffff ioport:3000(size=256) memory:f0300000-f033ffff memory:c0000-dffff

Code: Select all

$ sudo dmesg | grep -i radeon
[sudo] password for ericp: 
[    0.186811] smpboot: CPU0: AMD A6-4400M APU with Radeon(tm) HD Graphics (family: 0x15, model: 0x10, stepping: 0x1)
[   18.389145] [drm] radeon kernel modesetting enabled.
[   19.120490] radeon 0000:00:01.0: VRAM: 512M 0x0000000000000000 - 0x000000001FFFFFFF (512M used)
[   19.120494] radeon 0000:00:01.0: GTT: 1024M 0x0000000020000000 - 0x000000005FFFFFFF
[   19.120696] [drm] radeon: 512M of VRAM memory ready
[   19.120698] [drm] radeon: 1024M of GTT memory ready.
[   19.320603] radeon 0000:00:01.0: firmware: direct-loading firmware radeon/ARUBA_pfp.bin
[   19.343435] radeon 0000:00:01.0: firmware: direct-loading firmware radeon/ARUBA_me.bin
[   19.365020] radeon 0000:00:01.0: firmware: direct-loading firmware radeon/ARUBA_rlc.bin
[   19.365419] [drm] radeon: dpm initialized
[   19.453508] radeon 0000:00:01.0: firmware: direct-loading firmware radeon/TAHITI_uvd.bin
[   19.503735] radeon 0000:00:01.0: firmware: direct-loading firmware radeon/TAHITI_vce.bin
[   19.539866] radeon 0000:00:01.0: WB enabled
[   19.539871] radeon 0000:00:01.0: fence driver on ring 0 use gpu addr 0x0000000020000c00 and cpu addr 0xffff9bc4525dcc00
[   19.540252] radeon 0000:00:01.0: fence driver on ring 5 use gpu addr 0x0000000000075a18 and cpu addr 0xffffbea9c1c35a18
[   19.560291] radeon 0000:00:01.0: fence driver on ring 6 use gpu addr 0x0000000020000c18 and cpu addr 0xffff9bc4525dcc18
[   19.560296] radeon 0000:00:01.0: fence driver on ring 7 use gpu addr 0x0000000020000c1c and cpu addr 0xffff9bc4525dcc1c
[   19.560299] radeon 0000:00:01.0: fence driver on ring 1 use gpu addr 0x0000000020000c04 and cpu addr 0xffff9bc4525dcc04
[   19.560302] radeon 0000:00:01.0: fence driver on ring 2 use gpu addr 0x0000000020000c08 and cpu addr 0xffff9bc4525dcc08
[   19.560305] radeon 0000:00:01.0: fence driver on ring 3 use gpu addr 0x0000000020000c0c and cpu addr 0xffff9bc4525dcc0c
[   19.560308] radeon 0000:00:01.0: fence driver on ring 4 use gpu addr 0x0000000020000c10 and cpu addr 0xffff9bc4525dcc10
[   19.560366] radeon 0000:00:01.0: radeon: MSI limited to 32-bit
[   19.560429] radeon 0000:00:01.0: radeon: using MSI.
[   19.560455] [drm] radeon: irq initialized.
[   21.334517] [drm] radeon atom DIG backlight initialized
[   21.334520] [drm] Radeon Display Connectors
[   21.833527] fbcon: radeondrmfb (fb0) is primary device
[   22.824162] radeon 0000:00:01.0: fb0: radeondrmfb frame buffer device
[   22.898982] [drm] Initialized radeon 2.48.0 20080528 for 0000:00:01.0 on minor 0

Code: Select all

$ inxi -b
System:    Host: sypha Kernel: 4.9.0-3-amd64 x86_64 (64 bit) Desktop: MATE 1.16.2
           Distro: Debian GNU/Linux 9 (stretch)
Machine:   Device: laptop System: Hewlett-Packard product: HP Pavilion g6 Notebook PC v: 088B110000305910000620100
           Mobo: Hewlett-Packard model: 1849 v: 57.35
           UEFI [Legacy]: Insyde v: F.26 date: 02/21/2013
Battery    BAT0: charge: 19.8 Wh 100.0% condition: 19.8/19.8 Wh (100%)
CPU:       Dual core AMD A6-4400M APU with Radeon HD Graphics (-MCP-) speed/max: 1700/2700 MHz
Graphics:  Card: Advanced Micro Devices [AMD/ATI] Trinity [Radeon HD 7520G]
           Display Server: X.Org 1.19.2 drivers: ati,radeon (unloaded: modesetting,fbdev,vesa)
           Resolution: 1366x768@60.07hz
           GLX Renderer: Gallium 0.4 on AMD ARUBA (DRM 2.48.0 / 4.9.0-3-amd64, LLVM 3.9.1)
           GLX Version: 3.0 Mesa 13.0.6
Network:   Card-1: Ralink RT3290 Wireless 802.11n 1T/1R PCIe driver: rt2800pci
           Card-2: Realtek RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller
           driver: r8169
Drives:    HDD Total Size: 500.1GB (74.7% used)
Info:      Processes: 164 Uptime: 38 min Memory: 2156.1/5444.6MB Client: Shell (bash) inxi: 2.3.5 

larienna
Posts: 106
Joined: 2014-09-27 20:54

Re: D9 Cinnamon Hardware rendering gives a black screen

#2 Post by larienna »

I even tried installing a newer version of the proprietary driver and it complains that my Xserver version is too recent:

Code: Select all

=====================================================================
 AMD Catalyst(TM) Proprietary Driver Installer/Packager 
=====================================================================

error: Detected X Server version 'XServer 1.19.2_64a' is not supported. Supported versions are X.Org 6.9 or later, up to XServer 1.10 (default:v2:x86_64:lib32:XServer 1.19.2_64a:none:4.9.0-3-amd64:)
Installation will not proceed.
Here is the apt-cache output.

Code: Select all

$ sudo apt-cache show xserver-xorg
Package: xserver-xorg
Source: xorg
Version: 1:7.7+19
Installed-Size: 238
Maintainer: Debian X Strike Force <debian-x@lists.debian.org>
Architecture: amd64
Provides: xserver
Depends: xserver-xorg-core (>= 2:1.17.2-2), xserver-xorg-video-all | xorg-driver-video, xserver-xorg-input-all | xorg-driver-input, xkb-data (>= 1.4), x11-xkb-utils
Recommends: libgl1-mesa-dri, xserver-xorg-legacy
Description-en: X.Org X server
 This package depends on the full suite of the server and drivers for the
 X.Org X server.  It does not provide the actual server itself.
Description-md5: 3d8c1d268e8af6b69f54d86fbd5a3939
Homepage: http://www.x.org/
Tag: hardware::input, hardware::video, interface::daemon, network::server,
 role::metapackage, use::driver, x11::xserver
Section: x11
Priority: optional
Filename: pool/main/x/xorg/xserver-xorg_7.7+19_amd64.deb
Size: 93702
MD5sum: 8ea835a713c7d3203e211edc80f16e71
SHA256: e9f6520d747cb5080ed9839ab2ea5f73f47627087bb3490425e0416a74dcb7cb

LE_746F6D617A7A69
Posts: 932
Joined: 2020-05-03 14:16
Has thanked: 7 times
Been thanked: 65 times

Re: D9 Cinnamon Hardware rendering gives a black screen

#3 Post by LE_746F6D617A7A69 »

larienna wrote: 2022-10-01 15:16 The only modifications I made to my system lately is building and installing Python 3.9 in order to make Meson work.
If You're absolutely convinced that this is the cause, then the question is: how/where did You installed the compiled/downloaded binaries (libs/executables) in Your system? Normally, custom programs/libs should be installed in /usr/local/* or in /opt/* or in Your home directory.

If You did this right, (so we can assume that it was just a coincidence), then the missing part of the picture is the content of xserver log: /var/log/Xorg.0.log

You may also use the debsums command to verify the integrity of Your OS.
Bill Gates: "(...) In my case, I went to the garbage cans at the Computer Science Center and I fished out listings of their operating system."
The_full_story and Nothing_have_changed

User avatar
stevepusser
Posts: 12930
Joined: 2009-10-06 05:53
Has thanked: 41 times
Been thanked: 71 times

Re: D9 Cinnamon Hardware rendering gives a black screen

#4 Post by stevepusser »

Ummm...you are aware that Debian 9 is past end-of-life?

And those proprietary AMD Linux drivers were obsolete way way even before Debian 9, and Debian had them in the non-free section for the old releases where they were supported?

Is it impossible for you to upgrade to a supported Debian version?

There's a Yiddish word for your system's status: farpotshket.

Which means to fix something that was slightly broken until it's now completely broken.

The solution is to restore from your system backup.

I'm also curious as to what version of meson you needed--it may have been available in stretch-backports or another compatible repo (MX 17) without any Python shenanigans. https://repology.org/project/meson/versions
MX Linux packager and developer

larienna
Posts: 106
Joined: 2014-09-27 20:54

Re: D9 Cinnamon Hardware rendering gives a black screen

#5 Post by larienna »

If You're absolutely convinced that this is the cause, then the question is: how/where did You installed the compiled/downloaded binaries (libs/executables) in Your system?
I am not exactly sure what is the cause, it's just the most recent major changes I made to my system. Python3 seems installed to to a local directory

$ which python3
/usr/local/bin/python3

$ which python
/usr/bin/python


then the missing part of the picture is the content of xserver log: /var/log/Xorg.0.log
I imagine, I need to boot the defective cinnamon, switch terminal and make a copy of this log, if there is an error with my GFXcard, it should be there?

You may also use the debsums command to verify the integrity of Your OS
It seems I don't have debsums installed

I'm also curious as to what version of meson you needed--it may have been available in stretch-backports or another compatible repo (MX 17) without any Python shenanigans. https://repology.org/project/meson/versions
I wanted to try out meson from another thread's suggestion. I followed instructions on their website, it required Python 3.7 and above, I had python 3.5. So I decided to build python 3.9, now meson seems to work. But everything else seems to have failed. I wonder if I can revert back to python 3.5 which should still be on the system. I think there is a command to change priority. There is probably a config file that I modified somewhere, can't remember which one.

Somewhat related to python, I am now using Mate temporarily, but I cannot start the Ibus preference panel to configure available keyboard layout. ibus-setup gives me an error which after some search, seems also related to python.

Ummm...you are aware that Debian 9 is past end-of-life?
So what! I cannot reinstall linux every 6 months to follow the development cycle of debian, as it takes me at least 1 month to install and configure my system and restore it to the state where it was. And even with all my documented configuration, I end up losing some configuration because of undocumented changes I could have made later to the system.

In general, I never update my system to avoid situations like this. Because updating can break the system, while I still desperately need the computer. I never thought upgrading python would have broken my system. This is why, I reinstall in the summer, or another period of time where I can be without a computer for at least a month. So that if my computer catch fire or has other hasards, it does not matter, I'll have the time to fix it. Still with the pandemic and remote work, that period where I don't need my computer seems to be smaller than before.

Is it impossible for you to upgrade to a supported Debian version?
Well currently no, as I need my computer every week for my job (remote work) and for school. I could give it a try during Christmas vacations, else it will have to be next summer. Like I said, it takes me at least a month to install and configure.

And those proprietary AMD Linux drivers were obsolete way way even before Debian 9, and Debian had them in the non-free section for the old releases where they were supported?
That is what I though. On the last reinstall, the "firmware-amd-graphics" package seemed to have done the job. This is why I don't think it's a driver problem.

LE_746F6D617A7A69
Posts: 932
Joined: 2020-05-03 14:16
Has thanked: 7 times
Been thanked: 65 times

Re: D9 Cinnamon Hardware rendering gives a black screen

#6 Post by LE_746F6D617A7A69 »

larienna wrote: 2022-10-09 12:50 I am not exactly sure what is the cause, it's just the most recent major changes I made to my system. Python3 seems installed to to a local directory

$ which python3
/usr/local/bin/python3

$ which python
/usr/bin/python
"seems installed"? - what about the dependencies?
Anyway, for Me it looks like You don't understand the basic rules of developing for Linux systems - sorry.

Linux-based OS are the most powerful environment for developing a code - You have to make a decision, because it's impossible to write a good code for both Winblows and Linux (f.e. because Microshit is unable to settle a viable naming convention for their API :lol: )
Bill Gates: "(...) In my case, I went to the garbage cans at the Computer Science Center and I fished out listings of their operating system."
The_full_story and Nothing_have_changed

larienna
Posts: 106
Joined: 2014-09-27 20:54

Re: D9 Cinnamon Hardware rendering gives a black screen

#7 Post by larienna »

Linux-based OS are the most powerful environment for developing a code - You have to make a decision, because it's impossible to write a good code for both Winblows and Linux
I like Linux, it gives me control on my computer, and has a developper friendly environment. Portability is still important since most people are on windows. Cross compiling seem to makes developing on windows relatively easier than expected.

larienna
Posts: 106
Joined: 2014-09-27 20:54

Re: D9 Cinnamon Hardware rendering gives a black screen

#8 Post by larienna »

I fixed it, it was Evil python 3.9 that broke the system. I did not know cinnamon was using python.

I'll guess I'll either have to wait before using meson, or I'll have to find a version of meson that runs on python 3.5. I'll have to investigate.

Not sure if pip install the latest software version or the latest version compatible with your python version.

LE_746F6D617A7A69
Posts: 932
Joined: 2020-05-03 14:16
Has thanked: 7 times
Been thanked: 65 times

Re: D9 Cinnamon Hardware rendering gives a black screen

#9 Post by LE_746F6D617A7A69 »

larienna wrote: 2022-10-12 02:50 Portability is still important since most people are on windows (...)
I would say that most people are on Android ;) (which is also not good, btw)
larienna wrote: 2022-10-12 11:39 (...) it was Evil python 3.9 that broke the system (...)
Not really - You can have installed as many versions of python as You wish - the problem is, that You shouldn't touch the dependencies of the python version used by Debian.

Alternatively, You can install current stable Debian (which provides python3.9) in a QEMU VM - what will allow to keep your current OS/setup unchanged.
Bill Gates: "(...) In my case, I went to the garbage cans at the Computer Science Center and I fished out listings of their operating system."
The_full_story and Nothing_have_changed

larienna
Posts: 106
Joined: 2014-09-27 20:54

Re: D9 Cinnamon Hardware rendering gives a black screen

#10 Post by larienna »

I would say that most people are on Android ;) (which is also not good, btw)
I tried some Android dev, it looked promising, but it's a nightmare to program (lot of black magic involved, and gradle does not help). We had a combo box that did not behave correctly, and 3 programmers could not figure it out by looking at it for 2 hours. Some people say that Android suffer from over engineering. Personally, it's the lack of control on my program, the distance between the programmer and the machine, and the rapid obsolescence of software that annoys me. Also the fact that loading and running an hello world project in Android Studio takes me 15 minutes. An hello world program in code::blocks takes me 15 seconds.

I managed to install meson through apt. I don't know why I did not use that solution first. I guess I looked at meson's web site install procedure and went the complex and manual way first.

LE_746F6D617A7A69
Posts: 932
Joined: 2020-05-03 14:16
Has thanked: 7 times
Been thanked: 65 times

Re: D9 Cinnamon Hardware rendering gives a black screen

#11 Post by LE_746F6D617A7A69 »

larienna wrote: 2022-10-13 12:44 An hello world program in code::blocks takes me 15 seconds.
It looks like a mistake - are You sure it takes 15s (which C::B version?).
I'm currently working on a relatively small project, which has only about ~150K LOC spread over ~40 files, and the C::B is loading this project in less than a second - did You meant 0.15s?

If it's not a mistake, then apparently there must be something wrong with Your system - or maybe Your SSD is just slowing down? (surprise, surprise ;))
Bill Gates: "(...) In my case, I went to the garbage cans at the Computer Science Center and I fished out listings of their operating system."
The_full_story and Nothing_have_changed


Post Reply