Unix & Linux Stack Exchange
Q&A for users of Linux, FreeBSD and other Unix-like operating systems
Latest Questions
6
votes
1
answers
2901
views
Switchable graphics Intel + AMD Venus Pro
I'm using Manjaro Linux on my laptop with switchable graphic cards: ``` 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b) 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Venus PRO [Radeon HD 8850M / R9 M265X] (rev ff) `...
I'm using Manjaro Linux on my laptop with switchable graphic cards:
The above shows that bumblebee's drivers are installed, but the daemon fails:
[luke@manjaro ~]$ sudo systemctl status bumblebeed
● bumblebeed.service - Bumblebee C Daemon
Loaded: loaded (/usr/lib/systemd/system/bumblebeed.service; enabled; vendor preset: disabled)
Active: activating (auto-restart) (Result: exit-code) since pią 2015-09-18 16:22:55 CEST; 29s ago
Process: 1192 ExecStart=/usr/bin/bumblebeed (code=exited, status=1/FAILURE)
Main PID: 1192 (code=exited, status=1/FAILURE)
wrz 18 16:22:55 manjaro systemd
: bumblebeed.service: Unit entered failed state.
wrz 18 16:22:55 manjaro systemd
: bumblebeed.service: Failed with result 'exit-code'.
During my trial-and-error I also tried to install
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b)
03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Venus PRO [Radeon HD 8850M / R9 M265X] (rev ff)
Here's a screenshot of the drivers section of Manjaro Settings Manager:



video-catalyst
driver (in window shown above). It ended miserably - after the initial startup the screen was full white. I switched to another TTY and deleted video-catalyst using mhwd
.
My goal is to be able to play games on Steam. What can you recommend?
Luke
(151 rep)
Sep 18, 2015, 02:46 PM
• Last activity: Jun 29, 2025, 05:04 PM
2
votes
1
answers
5485
views
Video card driver problem in Debian (AMD Radeon R5 M330)
I am new to Linux. I am using Debian 8. I tried to play some games, but it seems that they are using my integrated Intel video card instead of discrete AMD Radeon: Star Conflict doesn't even show the space - everything is completely black (I can only see ship's interface components). Games with much...
I am new to Linux. I am using Debian 8. I tried to play some games, but it seems that they are using my integrated Intel video card instead of discrete AMD Radeon: Star Conflict doesn't even show the space - everything is completely black (I can only see ship's interface components). Games with much less requirements can produce the image but they are running very slow even on low graphics settings. On the same laptop on Windows side I can play Bioshock Infinite on high settings very well. So, it seems to be linux driver's fault. I have some program called "ATI Catalyst Control Center Linux edition" in my gnome menu and when I try to run it, I get this message:
There was a problem initializing Catalyst Control Center Linux edition. It could be caused by the following.
No AMD graphics driver is installed, or the AMD driver is not functioning properly.
Please install the AMD driver appropriate for you AMD hardware, or configure using aticonfig
I tried installing AMD proprietary driver, but it fails to install.
So, I'd like to use open-source driver, it doesn't really matter, I just want to get my graphics card working.
Output of
lspci | grep 'AMD'
:
0d:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Sun XT [Radeon HD 8670A/8670M/8690M] (rev ff)
I am also curios why it says "Display controller" instead of "VGA compatible controller" like it says about Intel's integrated card.
So, the final question is:
What software/driver should I install or how should I configure my system to get my discrete card working?
I am sorry if I gave not enough info - I just don't know what information is needed here. I would like to provide any info you ask.
Alexandr Gnatyuk
(103 rep)
Oct 10, 2016, 10:09 PM
• Last activity: Jun 25, 2025, 09:05 AM
0
votes
1
answers
4943
views
radeon failed vce resume after upgrade to newest Linux kernel
I have upgraded my Debian to latest version on the kernel version 3.16.0-4-amd64. Update went fine. After that I decided to upgrade linux kernel version to the latest one supported by Debian 10 - 4.19.0-5-amd64. After reboot my X-server didn't get up and in logs when system starting I see an error l...
I have upgraded my Debian to latest version on the kernel version 3.16.0-4-amd64. Update went fine. After that I decided to upgrade linux kernel version to the latest one supported by Debian 10 - 4.19.0-5-amd64. After reboot my X-server didn't get up and in logs when system starting I see an error like that
radeon 0000:01:00.0 failed VCE resume (-110)
Laptom model: Samsung 300E5V/300E4EV/270E5EV/270E4EV/2470EV/2470EE
After sysmtem start I get in command line interface. When try to execute startx
I see then same error about radeon and message from x-server:

$lspci | grep VGA
radeon failed VCE resume (-110)
VGA compatible controller: Intel Corporation 3rd Gen Core processor Graphics Controller(rev 09)
Here is ls -pci
[log](https://pastebin.com/3SUh0zXM) and [log](https://pastebin.com/jS66q0GC) from Xorg.0.log file.
Could you help me please fix an issue and get my desktop up again?
slesh
(121 rep)
Aug 4, 2019, 05:34 PM
• Last activity: May 30, 2025, 06:10 AM
3
votes
1
answers
1962
views
Old ATI Video Card on Debian 8 - Xpress 200 - model: 1150
Well, my problem is very complicated, I've an old machine (Dell Vostro 1000) where I'm using Debian 8 with XFCE. This machine have an integrated video card (ATI MOBILITY RADEON XPRESS 200 - Model: 1150), and it doesn't work with Debian default configuration. Let's see what I already have tried: - To...
Well, my problem is very complicated, I've an old machine (Dell Vostro 1000) where I'm using Debian 8 with XFCE. This machine have an integrated video card (ATI MOBILITY RADEON XPRESS 200 - Model: 1150), and it doesn't work with Debian default configuration.
Let's see what I already have tried:
- To turn on my laptop without it shows the notorious colored stripes I need use the "nomodeset" code on grub.cfg.
- The Debian 8 appears don't have the xorg.conf (???), I made a Xorg.conf following the instructions at https://wiki.debian.org/AtiHowTo , without success.
- I tried already tried follow the procedures in the page above, cause the current proprietary driver is not compatible with my old video card. and the older version (legacy) can't be installed and shows some conflicts with "X". This way I have to use the generic linux driver.
- I tried set the display resolution using XRANDR, but it fails and when I made the insertion of another resolution, I just can't select this.
- Thinking about modules, maybe I can see a little ligth in the end of tunnel. I find a blacklist file into "/etc/modprobe.d" and removed the module "radeonfb" of blacklist, but when I tried to restart, the machine only shows a black screen with the mouse pointer only. to fix this I changed the "quiet" entry of boot line and changed it with "single" to show the command line and I can see that when the module "radeonfb" is loaded, the letters of command line become small (like it have made a resolution adjustment) but I need understand why only a black screen and the mouse pointer is showed.
**NOTE:** The xorgs and firmware-linux are installed but doesn't work. I really don't need 3d acceleration, but I need to resize my screen. Actually it's 1024x768 but the hardware can show 1280x800.
Diego
(31 rep)
May 27, 2015, 06:36 PM
• Last activity: May 24, 2025, 02:04 AM
0
votes
0
answers
417
views
Radeon -> VESA fallback since Bookworm update: "open /dev/dri/card0: No such file or directory"
I just updated my desktop to Bookworm. Now every time I launch a game, the colours are messed up and the screen goes like this: ![1] It stays like this even after closing the game. The only solution is to close and reopen the session. The only use case reproducing this is games because of the specif...
I just updated my desktop to Bookworm. Now every time I launch a game, the colours are messed up and the screen goes like this: !
It stays like this even after closing the game. The only solution is to close and reopen the session.
The only use case reproducing this is games because of the specific display mode they typically use. It doesn't happen when opening a GTK or Qt window. Only with those game windows that are either fixed resolution or full-screen (e.g.: wesnoth, SuperTux 2, emulated games in Mednaffe). How is this display mode called ?
Here's the graphic card:
Advanced Micro Devices, Inc. [AMD/ATI] Oland PRO [Radeon R7 240/340 / Radeon 520]
I do have the following packages installed:
firmware-amd-graphics
xserver-xorg-video-all
libdrm-radeon1
Can't post full Xorg log file here. Here's the part that seems relevant:
[ 27.453] (II) LoadModule: "ati"
[ 27.489] (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so
[ 27.501] (II) Module ati: vendor="X.Org Foundation"
[ 27.501] compiled for 1.21.1.3, module version = 19.1.0
[ 27.501] Module class: X.Org Video Driver
[ 27.501] ABI class: X.Org Video Driver, version 25.2
[ 30.701] (II) LoadModule: "radeon"
[ 30.701] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so
[ 31.113] (II) Module radeon: vendor="X.Org Foundation"
[ 31.117] compiled for 1.21.1.3, module version = 19.1.0
[ 31.117] Module class: X.Org Video Driver
[ 31.117] ABI class: X.Org Video Driver, version 25.2
[ 31.117] (II) LoadModule: "modesetting"
[ 31.117] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 31.229] (II) Module modesetting: vendor="X.Org Foundation"
[ 31.229] compiled for 1.21.1.7, module version = 1.21.1
[ 31.229] Module class: X.Org Video Driver
[ 31.229] ABI class: X.Org Video Driver, version 25.2
[ 31.229] (II) LoadModule: "fbdev"
[ 31.229] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[ 31.337] (II) Module fbdev: vendor="X.Org Foundation"
[ 31.337] compiled for 1.21.1.3, module version = 0.5.0
[ 31.337] Module class: X.Org Video Driver
[ 31.337] ABI class: X.Org Video Driver, version 25.2
[ 31.337] (II) LoadModule: "vesa"
[ 31.337] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 31.373] (II) Module vesa: vendor="X.Org Foundation"
[ 31.377] compiled for 1.21.1.3, module version = 2.5.0
[ 31.377] Module class: X.Org Video Driver
[ 31.377] ABI class: X.Org Video Driver, version 25.2
[ 31.377] (II) RADEON: Driver for ATI/AMD Radeon chipsets:
[... Long list of chipsets ...]
[ 2509.619] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 2509.619] (II) FBDEV: driver for framebuffer: fbdev
[ 2509.619] (II) VESA: driver for VESA chipsets: vesa
[ 2509.623] (II) [KMS] drm report modesetting isn't supported.
[ 2509.623] (EE) open /dev/dri/card0: No such file or directory
[ 2509.623] (WW) Falling back to old probe method for modesetting
[ 2509.623] (EE) open /dev/dri/card0: No such file or directory
[ 2509.623] (II) Loading sub module "fbdevhw"
[ 2509.623] (II) LoadModule: "fbdevhw"
[ 2509.623] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 2509.623] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 2509.623] compiled for 1.21.1.7, module version = 0.0.2
[ 2509.623] ABI class: X.Org Video Driver, version 25.2
[ 2509.623] (EE) Unable to find a valid framebuffer device
[ 2509.623] (WW) Falling back to old probe method for fbdev
[ 2509.623] (II) Loading sub module "fbdevhw"
[ 2509.623] (II) LoadModule: "fbdevhw"
[ 2509.623] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 2509.623] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 2509.623] compiled for 1.21.1.7, module version = 0.0.2
[ 2509.623] ABI class: X.Org Video Driver, version 25.2
[ 2509.623] (EE) open /dev/fb0: No such file or directory
[ 2509.623] (EE) Screen 0 deleted because of no matching config section.
[ 2509.623] (II) UnloadModule: "radeon"
[ 2509.623] (EE) Screen 0 deleted because of no matching config section.
[ 2509.623] (II) UnloadModule: "modesetting"
[ 2509.623] (EE) Screen 0 deleted because of no matching config section.
[ 2509.623] (II) UnloadModule: "fbdev"
[ 2509.623] (II) UnloadSubModule: "fbdevhw"
[ 2509.623] (II) Loading sub module "vbe"
[ 2509.623] (II) LoadModule: "vbe"
[ 2509.623] (II) Loading /usr/lib/xorg/modules/libint10.so
[ 2509.623] (II) Module int10: vendor="X.Org Foundation"
[ 2509.623] compiled for 1.21.1.7, module version = 1.0.0
[ 2509.623] ABI class: X.Org Video Driver, version 25.2
[ 2509.623] (II) Loading sub module "int10"
[ 2509.623] (II) LoadModule: "int10"
[ 2509.623] (II) Loading /usr/lib/xorg/modules/libint10.so
[ 2509.623] (II) Module int10: vendor="X.Org Foundation"
[ 2509.623] compiled for 1.21.1.7, module version = 1.0.0
[ 2509.623] ABI class: X.Org Video Driver, version 25.2
[ 2509.623] (II) VESA(0): initializing int10
[ 2509.623] (II) VESA(0): Primary V_BIOS segment is: 0xc000
[ 2509.623] (II) VESA(0): VESA BIOS detected
[ 2509.623] (II) VESA(0): VESA VBE Version 3.0
[ 2509.623] (II) VESA(0): VESA VBE Total Mem: 16384 kB
[ 2509.623] (II) VESA(0): VESA VBE OEM: AMD ATOMBIOS
[ 2509.623] (II) VESA(0): VESA VBE OEM Software Rev: 15.42
[ 2509.623] (II) VESA(0): VESA VBE OEM Vendor: (C) 1988-2010, Advanced Micro Devices, Inc.
[ 2509.623] (II) VESA(0): VESA VBE OEM Product: OLAND
[ 2509.623] (II) VESA(0): VESA VBE OEM Product Rev: 01.00
[ 2509.643] (II) VESA(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 2509.643] (==) VESA(0): Depth 24, (--) framebuffer bpp 32
[ 2509.643] (==) VESA(0): RGB weight 888
[ 2509.643] (==) VESA(0): Default visual is TrueColor
[ 2509.643] (==) VESA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 2509.643] (II) Loading sub module "ddc"
[ 2509.643] (II) LoadModule: "ddc"
[ 2509.643] (II) Module "ddc" already built-in
Looks like radeon driver fails at some point and the system falls back on a default driver.
Is this correct and what can I do to fix this?
I don't see anything more in

.xsession-errors
or syslog
when the graphical mayhem actually happens.
Edit:
$ inxi -G
Graphics:
Device-1: AMD Oland PRO [Radeon R7 240/340 / Radeon 520] driver: N/A
Display: x11 server: X.Org v: 1.21.1.7 driver: X: loaded: vesa
unloaded: fbdev,modesetting,radeon dri: swrast gpu: N/A
resolution: 1920x1080
API: OpenGL v: 4.5 Mesa 22.3.6 renderer: llvmpipe (LLVM 15.0.6 128 bits)
**Edit:** Bug reported on [Debian BTS](https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040144) .
**Edit:** Got a new computer, so I won't be following this anymore. I'll update here if the bug report thread is updated.
Jérôme
(2023 rep)
Jun 28, 2023, 09:24 AM
• Last activity: Apr 8, 2024, 08:29 PM
2
votes
2
answers
448
views
Xorg problem with Radeon Mobility X1600 on a 20" iMac LCD from 2006
My attempt to give a meaningful purpose to a 20-inch 2006 iMac 4.1 choked on an odd Xorg problem. Tried **FreeBSD 13.0 Release/amd64** and **elementaryOS 6.0 Odin** as up-to-date systems with their respective **Xorg** packages. Using the **radeon** driver *(only under Linux, as this driver was not p...
My attempt to give a meaningful purpose to a 20-inch 2006 iMac 4.1 choked on an odd Xorg problem. Tried **FreeBSD 13.0 Release/amd64** and **elementaryOS 6.0 Odin** as up-to-date systems with their respective **Xorg** packages. Using the **radeon** driver *(only under Linux, as this driver was not present under FreeBSD, nor was it available as a separate package or in ports)* seems to provide the correct graphics mode with the native resolution of the built-in LCD screen. Windows, icons, panels look all fine, but the background picture *(or the desktop background in general, even as a solid colour)* shows broken artifacts.

Its peculiarity is that ONLY the background is drawn flawed, and any GUI object over that looks perfectly fine, including translucent windows, menubars, icons, etc.

Using the **modesetting** driver seems to be unable to render the graphics screen properly, with the entire display drawn with off-shifted lines.

As the **modesetting** driver exists *(and behaves exactly the same way)* on both FreeBSD and Linux *(talking about recent releases as in late 2021)*, and also being the obvious way forward, I would prefer to get this working instead of relying on **radeon**.
So, I started by extracting the native resolution details from the EDID data of this 2006 iMac's built-in LCD.
Identifier "Color LCD"
ModelName "Color LCD"
VendorName "APP"
# Monitor Manufactured week 0 of 2005
# EDID version 1.3
# Digital Display
DisplaySize 430 270
Gamma 2.20
Modeline "Mode 0" 119.00 1680 1728 1760 1840 1050 1053 1059 1080 -hsync -vsync
The suggested **modeline** matches what **xorg** auto-detects when started without an **xorg.conf** file. As the graphics screen works well under this computer's intended *(and outdated, no longer supported)* operating system **Mac OS X 10.6** Snow Leopard, and looks fine under **Windows 10** too, I used a program named [PowerStrip](http://www.fredshack.com/docs/x.html) to collect whatever screen details I could under Windows. This allowed me to fabricate some promising custom modelines.
Section "Modes"
Identifier "LTM201M1-MODELINES"
###ModeLine "1680x1050" 147.136 1680 1784 1968 2256 1050 1051 1054 1087 +hsync +vsync
ModeLine "1600x1000" 133.142 1600 1704 1872 2144 1000 1001 1004 1035 +hsync +vsync
###ModeLine "1400x1050" 122.614 1400 1488 1640 1880 1050 1051 1054 1087 +hsync +vsync
ModeLine "1664x936" 128.373 1664 1760 1936 2208 936 937 940 969 +hsync +vsync
Modeline "1664x1040" 143.715 1664 1768 1944 2224 1040 1041 1044 1077 +hsync +vsync
ModeLine "1696x1060" 149.543 1696 1800 1984 2272 1060 1061 1064 1097 +hsync +vsync
###ModeLine "1678x1050" 146.745 1678 1784 1964 2250 1050 1051 1054 1087 +hsync +vsync
###ModeLine "1678x1048" 146.475 1678 1784 1964 2250 1048 1049 1052 1085 +hsync +vsync
###ModeLine "1680x1048" 146.866 1680 1784 1968 2256 1048 1049 1052 1085 +hsync +vsync
###ModeLine "k1" 119.000 1680 1728 1760 1840 1050 1053 1059 1080 +hsync +vsync
###ModeLine "k2" 149.543 1680 1800 1984 2272 1050 1061 1064 1097 +hsync +vsync
EndSection
Those with the triple hashtag comments, do not work well with the modesetting driver. They switch the display into an unreadable line-shifted mode as shown on the 3rd picture above. The last two lines were not produced by PowerStrip data, those were assembled by me manually, using one of the above lines but altering one detail or two in the hope that I can get the native resolution working.
Interestingly, the native resolution of 1680x1050 never seems to work using the **modesetting** driver. Not even the **modeline** that is read from EDID, which is what Windows 10, Mac OS X, and the **radeon** Xorg driver under Linux use successfully.
Also interesting that **the "1664x1040" and "1696x1060" modes work perfectly**, giving a nice, flicker free, solid display. These are one smaller, and larger resolutions than the native 1680x1050 while keeping the 16:10 aspect ratio. I am surprised that the 1696x1060 works fine too (obviously, the last few pixels are off screen, hence not visible, but the display is solid without any shifted/running lines).
Here is what the PCI details show.
vgapci0@pci0:1:0:0: class=0x030000 rev=0x00 hdr=0x00 vendor=0x1002 device=0x71c5 subvendor=0x106b subdevice=0x0080
vendor = 'Advanced Micro Devices, Inc. [AMD/ATI]'
device = 'RV530/M56-P [Mobility Radeon X1600]'
class = display
subclass = VGA
The Xorg.0.log from both FreeBSD and Linux, using either the radeon or the modesetting driver, shows nothing wrong. As far as Xorg is concerned, everything runs fine. The problem is that my human eyes see something I am not able to process (shown on the 3rd picture above).
[xrandr --verbose (radeon/Linux)](http://keve.maclab.org/pub/xrandr--verbose.imac41.radeon.linux.txt)
[xrandr --verbose (modesetting/FreeBSD)](http://keve.maclab.org/pub/xrandr--verbose.imac41.modesetting.fbsd.txt)
[Xorg.0.log (radeon/Linux)](http://keve.maclab.org/pub/xorg.0.log.iMac41.radeon.linux.txt)
[Xorg.0.log (modesetting/Linux)](http://keve.maclab.org/pub/xorg.0.log.iMac41.modesetting.linux.txt)
As I am unable to get the native 1680x1050 working with modesetting (failing the same way under FreeBSD and Linux), while the same settings are known to work with the proprietary ATI driver under Windows 10 and Mac OS X, plus the open source radeon driver under Linux, my conclusion is that something may be wrong with the modesetting driver (or the radeonkms module).
**Do you have any suggestion on what to try in order to get the native resolution working with the modesetting driver?**
Alternatively, **what would be the proper channel to report this issue to the developers of the modesetting driver** (or the radeonkms module)**?**
Keve
(123 rep)
Nov 22, 2021, 09:23 PM
• Last activity: Mar 26, 2024, 12:39 PM
4
votes
1
answers
2976
views
Arch linux: AMD ryzen + AMD radeon experiencing freezes and crashes of browsers
I moved my install from intel i7 + intel iris to AMD ryzen 5 + AMD radeon, by swaping SSDs. I experience these issues: --- ### Symptoms - Everything works fine except randomly load of CPU explodes to 30+ and system freezes for few minutes. - All firefox, brave and electron apps crash randomly. I hig...
I moved my install from intel i7 + intel iris to AMD ryzen 5 + AMD radeon, by swaping SSDs. I experience these issues:
---
### Symptoms
- Everything works fine except randomly load of CPU explodes to 30+ and system freezes for few minutes.
- All firefox, brave and electron apps crash randomly. I highly suspect it will be something wit HW acceleration.
- When booting I see
AMDGPU securedisplay: generic failrure
in log and this is in journalctl:
Dec 18 02:26:00 archlinux kernel: amdgpu 0000:04:00.0: amdgpu: Secure display: Generic Failure.
Dec 18 02:26:00 archlinux kernel: amdgpu 0000:04:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
- Sway randomly crashed
- Discord is crashing with message:
[109734:1216/144012.453719:ERROR:shared_image_factory.cc(575)] Could not find SharedImageBackingFactory with params: usage: Gles2|Raster|DisplayRead|Scanout, format: BGRA_8888, share_between_threads: 0, gmb_type: shared_memory
[109734:1216/144018.594445:ERROR:shared_image_factory.cc(575)] Could not find SharedImageBackingFactory with params: usage: Gles2|Raster|DisplayRead|Scanout, format: BGRA_8888, share_between_threads: 0, gmb_type: shared_memory
[109734:1216/144025.341187:ERROR:shared_image_factory.cc(575)] Could not find SharedImageBackingFactory with params: usage: Gles2|Raster|DisplayRead|Scanout, format: BGRA_8888, share_between_threads: 0, gmb_type: shared_memory
[109688:1216/144035.692207:ERROR:gpu_process_host.cc(991)] GPU process exited unexpectedly: exit_code=9
(electron) 'gpu-process-crashed event' is deprecated and will be removed. Please use 'child-process-gone event' instead.
notificationScreen.webContentsSend: win is invalid undefined.
child-process-gone! child: GPU (undefined) exitCode: 9
blackbox: 2023-12-16T13:40:35.738Z 59 before-quit
blackbox: 2023-12-16T13:40:35.763Z 60 window.close win8
blackbox: 2023-12-16T13:40:35.772Z 61 ❌ child-process-gone { type: 'GPU', reason: 'killed', exitCode: 9, serviceName: 'GPU' }
blackbox: 2023-12-16T13:40:36.319Z 62 webContents.destroyed web8
- this is Brave browser log:
[158080:158080:1218/173945.959830:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!
[158080:158080:1218/173945.966721:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times!
[158080:158080:1218/173950.934755:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times!
Warning: terminator_CreateInstance: Failed to CreateInstance in ICD 0. Skipping ICD.
Warning: terminator_CreateInstance: Found no drivers!
Warning: vkCreateInstance failed with VK_ERROR_INCOMPATIBLE_DRIVER
at CheckVkSuccessImpl (../../third_party/dawn/src/dawn/native/vulkan/VulkanError.cpp:101)
at CreateVkInstance (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:493)
at Initialize (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:379)
at Create (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:301)
at operator() (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:556)
- After one strong freeze I found this in the journalctl
:
Dec 23 22:19:05 arch-thinkpad kernel: Out of memory: Killed process 2068 (electron) total-vm:1190296860kB, anon-rss:175928kB, file-rss:256kB, shmem-rss:600kB, UID:1000 pgtables:1752kB oom_score_adj:300
Dec 23 22:21:22 arch-thinkpad kernel: Out of memory: Killed process 10923 (brave) total-vm:1186204220kB, anon-rss:51484kB, file-rss:512kB, shmem-rss:3648kB, UID:1000 pgtables:928kB oom_score_adj:300
Dec 23 22:21:33 arch-thinkpad kernel: Out of memory: Killed process 8797 (brave) total-vm:1186202212kB, anon-rss:51528kB, file-rss:256kB, shmem-rss:1084kB, UID:1000 pgtables:1008kB oom_score_adj:300
Dec 23 22:21:34 arch-thinkpad kernel: Out of memory: Killed process 8753 (brave) total-vm:1186222336kB, anon-rss:50016kB, file-rss:384kB, shmem-rss:1252kB, UID:1000 pgtables:1016kB oom_score_adj:300
- Firefox very often crashes with this log:
[Parent 2974, IPC I/O Parent] WARNING: process 3081 exited on signal 11: file /build/firefox/src/firefox-121.0/ipc/chromium/src/base/process_util_posix.cc:265
[Parent 2974, IPC I/O Parent] WARNING: process 3917 exited on signal 11: file /build/firefox/src/firefox-121.0/ipc/chromium/src/base/process_util_posix.cc:265
[Parent 2974, IPC I/O Parent] WARNING: process 3958 exited on signal 11: file /build/firefox/src/firefox-121.0/ipc/chromium/src/base/process_util_posix.cc:265
[Parent 2974, IPC I/O Parent] WARNING: process 3633 exited on signal 11: file /build/firefox/src/firefox-121.0/ipc/chromium/src/base/process_util_posix.cc:265
ExceptionHandler::GenerateDump cloned child 7802
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Failed to open curl lib from binary, use libcurl.so instead
ExceptionHandler::GenerateDump cloned child 10410
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Failed to open curl lib from binary, use libcurl.so instead
Chromium browser straight up crashes immidietly on lauch:
[32424:32424:0109/161137.203058:ERROR:policy_logger.cc(156)] :components/enterprise/browser/controller/chrome_browser_cloud_management_controller.cc(161) Cloud management controller initialization aborted as CBCM is not enabled. Please use the --enable-chrome-browser-cloud-management
command line flag to enable it if you are not using the official Google Chrome build.
[32500:1:0109/161137.867689:ERROR:command_buffer_proxy_impl.cc(127)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
[32424:32424:0109/161137.868183:ERROR:gpu_process_host.cc(992)] GPU process exited unexpectedly: exit_code=139
[32500:1:0109/161138.480418:ERROR:command_buffer_proxy_impl.cc(127)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
[32573:1:0109/161138.480549:ERROR:command_buffer_proxy_impl.cc(319)] GPU state invalid after WaitForGetOffsetInRange.
[32583:1:0109/161138.481906:ERROR:command_buffer_proxy_impl.cc(127)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
[32424:32452:0109/161138.483240:ERROR:shared_image_interface_proxy.cc(136)] Buffer handle is null. Not creating a mailbox from it.
[32424:32452:0109/161138.483260:ERROR:one_copy_raster_buffer_provider.cc(365)] Creation of MappableSharedImage failed.
[32424:32452:0109/161138.483313:ERROR:shared_image_interface_proxy.cc(136)] Buffer handle is null. Not creating a mailbox from it.
[32424:32424:0109/161138.484013:ERROR:gpu_process_host.cc(992)] GPU process exited unexpectedly: exit_code=139
[32543:1:0109/161139.231084:ERROR:command_buffer_proxy_impl.cc(319)] GPU state invalid after WaitForGetOffsetInRange.
[32573:1:0109/161139.231223:ERROR:command_buffer_proxy_impl.cc(319)] GPU state invalid after WaitForGetOffsetInRange.
[32424:32452:0109/161139.232795:ERROR:shared_image_interface_proxy.cc(136)] Buffer handle is null. Not creating a mailbox from it.
[32424:32452:0109/161139.232810:ERROR:one_copy_raster_buffer_provider.cc(365)] Creation of MappableSharedImage failed.
[32424:32424:0109/161139.232827:ERROR:gpu_process_host.cc(992)] GPU process exited unexpectedly: exit_code=139
[32714:32714:0109/161139.240747:ERROR:angle_platform_impl.cc(44)] Display.cpp:1052 (initialize): ANGLE Display::initialize error 0: Internal Vulkan error (-3): Initialization of an object could not be completed for implementation-specific reasons, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, initialize:1711.
ERR: Display.cpp:1052 (initialize): ANGLE Display::initialize error 0: Internal Vulkan error (-3): Initialization of an object could not be completed for implementation-specific reasons, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, initialize:1711.
[32714:32714:0109/161139.240832:ERROR:gl_display.cc(515)] EGL Driver message (Critical) eglInitialize: Internal Vulkan error (-3): Initialization of an object could not be completed for implementation-specific reasons, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, initialize:1711.
[32714:32714:0109/161139.240859:ERROR:gl_display.cc(786)] eglInitialize SwANGLE failed with error EGL_NOT_INITIALIZED
[32714:32714:0109/161139.240894:ERROR:gl_display.cc(820)] Initialization of all EGL display types failed.
[32714:32714:0109/161139.240917:ERROR:gl_ozone_egl.cc(26)] GLDisplayEGL::Initialize failed.
[32714:32714:0109/161139.241169:ERROR:angle_platform_impl.cc(44)] Display.cpp:1052 (initialize): ANGLE Display::initialize error 0: Internal Vulkan error (-3): Initialization of an object could not be completed for implementation-specific reasons, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, initialize:1711.
ERR: Display.cpp:1052 (initialize): ANGLE Display::initialize error 0: Internal Vulkan error (-3): Initialization of an object could not be completed for implementation-specific reasons, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, initialize:1711.
[32714:32714:0109/161139.241204:ERROR:gl_display.cc(515)] EGL Driver message (Critical) eglInitialize: Internal Vulkan error (-3): Initialization of an object could not be completed for implementation-specific reasons, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, initialize:1711.
[32714:32714:0109/161139.241228:ERROR:gl_display.cc(786)] eglInitialize SwANGLE failed with error EGL_NOT_INITIALIZED
[32714:32714:0109/161139.241250:ERROR:gl_display.cc(820)] Initialization of all EGL display types failed.
[32714:32714:0109/161139.241277:ERROR:gl_ozone_egl.cc(26)] GLDisplayEGL::Initialize failed.
[32714:32714:0109/161139.242947:ERROR:viz_main_impl.cc(196)] Exiting GPU process due to errors during initialization
[32424:32424:0109/161139.654097:ERROR:gpu_process_host.cc(992)] GPU process exited unexpectedly: exit_code=139
[32424:32424:0109/161140.509961:FATAL:gpu_data_manager_impl_private.cc(448)] GPU process isn't usable. Goodbye.
fish: Job 1, 'chromium 2> chromium-log' terminated by signal SIGTRAP (Trace or breakpoint trap)
---
## More information
**Specs:**
- I use HP laptop with arch linux + wayland + sway
- CPU: AMD Ryzen 5 4500U with Radeon Graphics (6) @ 2.375GHz
- GPU: AMD ATI Radeon RX Vega 6
- I have 8Gb or RAM and ~~no SWAP~~ with 8gb swap file on SSD
This is list of installed packages containing amd
:
local/amd-ucode 20231211.f2e52a1c-1
Microcode update image for AMD CPUs
local/amf-headers 1.4.32-1
Header files for AMD Advanced Media Framework
local/libteam 1.32-1
Library for controlling team network device
local/nvtop 3.0.2-1
GPUs process monitoring for AMD, Intel and NVIDIA
local/rocm-dbgapi 5.7.1-1
Support library necessary for a debugger of AMD's GPUs
This is list of packages containing radeon
:
local/hsakmt-roct 5.7.1-1
Radeon Open Compute Thunk Interface
local/lib32-vulkan-radeon 1:23.3.1-1
Radeon's Vulkan mesa driver (32-bit)
local/vulkan-radeon 1:23.3.1-1
Radeon's Vulkan mesa driver
This is output of lspci -nn
:
00:00.0 Host bridge : Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne Root Complex [1022:1630]
00:00.2 IOMMU : Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne IOMMU [1022:1631]
00:01.0 Host bridge : Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge [1022:1632]
00:01.3 PCI bridge : Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge [1022:1634]
00:02.0 Host bridge : Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge [1022:1632]
00:02.1 PCI bridge : Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge [1022:1634]
00:02.3 PCI bridge : Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne PCIe GPP Bridge [1022:1634]
00:08.0 Host bridge : Advanced Micro Devices, Inc. [AMD] Renoir PCIe Dummy Host Bridge [1022:1632]
00:08.1 PCI bridge : Advanced Micro Devices, Inc. [AMD] Renoir Internal PCIe GPP Bridge to Bus [1022:1635]
00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 51)
00:14.3 ISA bridge : Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge [1022:790e] (rev 51)
00:18.0 Host bridge : Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 0 [1022:1448]
00:18.1 Host bridge : Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 1 [1022:1449]
00:18.2 Host bridge : Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 2 [1022:144a]
00:18.3 Host bridge : Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 3 [1022:144b]
00:18.4 Host bridge : Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 4 [1022:144c]
00:18.5 Host bridge : Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 5 [1022:144d]
00:18.6 Host bridge : Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 6 [1022:144e]
00:18.7 Host bridge : Advanced Micro Devices, Inc. [AMD] Renoir Device 24: Function 7 [1022:144f]
01:00.0 Network controller : Realtek Semiconductor Co., Ltd. RTL8822CE 802.11ac PCIe Wireless Network Adapter [10ec:c822]
02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS522A PCI Express Card Reader [10ec:522a] (rev 01)
03:00.0 Non-Volatile memory controller : Samsung Electronics Co Ltd NVMe SSD Controller PM9A1/PM9A3/980PRO [144d:a80a]
04:00.0 VGA compatible controller : Advanced Micro Devices, Inc. [AMD/ATI] Renoir [Radeon RX Vega 6 (Ryzen 4000/5000 Mobile Series)] [1002:1636] (rev c3)
04:00.1 Audio device : Advanced Micro Devices, Inc. [AMD/ATI] Renoir Radeon High Definition Audio Controller [1002:1637]
04:00.2 Encryption controller : Advanced Micro Devices, Inc. [AMD] Family 17h (Models 10h-1fh) Platform Security Processor [1022:15df]
04:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB 3.1 [1022:1639]
04:00.4 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Renoir/Cezanne USB 3.1 [1022:1639]
04:00.5 Multimedia controller : Advanced Micro Devices, Inc. [AMD] ACP/ACP3X/ACP6x Audio Coprocessor [1022:15e2] (rev 01)
04:00.6 Audio device : Advanced Micro Devices, Inc. [AMD] Family 17h/19h HD Audio Controller [1022:15e3]
04:00.7 Signal processing controller : Advanced Micro Devices, Inc. [AMD] Sensor Fusion Hub [1022:15e4]
Output of lspci -k | grep -A 3 -E "(VGA|3D)"
:
04:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [Radeon RX Vega 6 (Ryzen 4000/5000 Mobile Series)] (rev c3)
DeviceName: AMD Radeon(TM) Graphics
Subsystem: Hewlett-Packard Company Renoir [Radeon RX Vega 6 (Ryzen 4000/5000 Mobile Series)]
Kernel driver in use: amdgpu
I have found this in dmesg
log:
[ 2.906817] [drm] amdgpu kernel modesetting enabled.
[ 2.907464] amdgpu: Virtual CRAT table created for CPU
[ 2.907479] amdgpu: Topology: Add CPU node
[ 2.907685] amdgpu 0000:04:00.0: enabling device (0006 -> 0007)
[ 2.907739] [drm] initializing kernel modesetting (RENOIR 0x1002:0x1636 0x103C:0x876E 0xC3).
[ 2.934103] [drm] register mmio base: 0xD0400000
[ 2.934114] [drm] register mmio size: 524288
[ 2.937640] [drm] add ip block number 0
[ 2.937644] [drm] add ip block number 1
[ 2.937646] [drm] add ip block number 2
[ 2.937647] [drm] add ip block number 3
[ 2.937649] [drm] add ip block number 4
[ 2.937651] [drm] add ip block number 5
[ 2.937652] [drm] add ip block number 6
[ 2.937654] [drm] add ip block number 7
[ 2.937655] [drm] add ip block number 8
[ 2.937656] [drm] add ip block number 9
[ 2.937681] amdgpu 0000:04:00.0: amdgpu: Fetched VBIOS from VFCT
[ 2.937684] amdgpu: ATOM BIOS: 113-RENOIR-026
[ 2.939454] [drm] VCN decode is enabled in VM mode
[ 2.939456] [drm] VCN encode is enabled in VM mode
[ 2.940642] [drm] JPEG decode is enabled in VM mode
[ 2.954319] Console: switching to colour dummy device 80x25
[ 2.988195] amdgpu 0000:04:00.0: vgaarb: deactivate vga console
[ 2.988210] amdgpu 0000:04:00.0: amdgpu: Trusted Memory Zone (TMZ) feature enabled
[ 2.988218] amdgpu 0000:04:00.0: amdgpu: MODE2 reset
[ 2.988323] [drm] vm size is 262144 GB, 4 levels, block size is 9-bit, fragment size is 9-bit
[ 2.988337] amdgpu 0000:04:00.0: amdgpu: VRAM: 512M 0x000000F400000000 - 0x000000F41FFFFFFF (512M used)
[ 2.988342] amdgpu 0000:04:00.0: amdgpu: GART: 1024M 0x0000000000000000 - 0x000000003FFFFFFF
[ 2.988345] amdgpu 0000:04:00.0: amdgpu: AGP: 267419648M 0x000000F800000000 - 0x0000FFFFFFFFFFFF
[ 2.988357] [drm] Detected VRAM RAM=512M, BAR=512M
[ 2.988360] [drm] RAM width 128bits DDR4
[ 2.988686] [drm] amdgpu: 512M of VRAM memory ready
[ 2.988692] [drm] amdgpu: 3661M of GTT memory ready.
[ 2.988726] [drm] GART: num cpu pages 262144, num gpu pages 262144
[ 2.988934] [drm] PCIE GART of 1024M enabled.
[ 2.988936] [drm] PTB located at 0x000000F41FC00000
[ 2.989313] [drm] Loading DMUB firmware via PSP: version=0x01010028
[ 2.989963] [drm] Found VCN firmware Version ENC: 1.21 DEC: 6 VEP: 0 Revision: 0
[ 2.989970] amdgpu 0000:04:00.0: amdgpu: Will use PSP to load VCN firmware
[ 3.649478] [drm] reserve 0x400000 from 0xf41f800000 for PSP TMR
[ 3.744619] amdgpu 0000:04:00.0: amdgpu: RAS: optional ras ta ucode is not available
[ 3.754153] amdgpu 0000:04:00.0: amdgpu: RAP: optional rap ta ucode is not available
[ 3.759165] [drm] psp gfx command LOAD_TA(0x1) failed and response status is (0x7)
[ 3.759289] [drm] psp gfx command INVOKE_CMD(0x3) failed and response status is (0x4)
[ 3.759293] amdgpu 0000:04:00.0: amdgpu: Secure display: Generic Failure.
[ 3.759305] amdgpu 0000:04:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
[ 3.759720] amdgpu 0000:04:00.0: amdgpu: SMU is initialized successfully!
[ 3.760994] [drm] Display Core v3.2.247 initialized on DCN 2.1
[ 3.760998] [drm] DP-HDMI FRL PCON supported
[ 3.761775] [drm] DMUB hardware initialized: version=0x01010028
[ 4.104152] [drm] Alt mode has timed out after 202 ms
[ 4.106330] [drm] kiq ring mec 2 pipe 1 q 0
[ 4.109571] [drm] VCN decode and encode initialized successfully(under DPG Mode).
[ 4.109599] [drm] JPEG decode initialized successfully.
[ 4.136633] amdgpu: HMM registered 512MB device memory
[ 4.138946] kfd kfd: amdgpu: Allocated 3969056 bytes on gart
[ 4.138968] kfd kfd: amdgpu: Total number of KFD nodes to be created: 1
[ 4.139127] amdgpu: Virtual CRAT table created for GPU
[ 4.139236] amdgpu: Topology: Add dGPU node [0x1636:0x1002]
[ 4.139239] kfd kfd: amdgpu: added device 1002:1636
[ 4.139253] amdgpu 0000:04:00.0: amdgpu: SE 1, SH per SE 1, CU per SH 8, active_cu_number 6
[ 4.139421] amdgpu 0000:04:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0
[ 4.139424] amdgpu 0000:04:00.0: amdgpu: ring gfx_low uses VM inv eng 1 on hub 0
[ 4.139425] amdgpu 0000:04:00.0: amdgpu: ring gfx_high uses VM inv eng 4 on hub 0
[ 4.139427] amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 5 on hub 0
[ 4.139428] amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 6 on hub 0
[ 4.139430] amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 7 on hub 0
[ 4.139431] amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 8 on hub 0
[ 4.139432] amdgpu 0000:04:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 9 on hub 0
[ 4.139434] amdgpu 0000:04:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 10 on hub 0
[ 4.139435] amdgpu 0000:04:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 11 on hub 0
[ 4.139437] amdgpu 0000:04:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 12 on hub 0
[ 4.139438] amdgpu 0000:04:00.0: amdgpu: ring kiq_0.2.1.0 uses VM inv eng 13 on hub 0
[ 4.139439] amdgpu 0000:04:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 8
[ 4.139441] amdgpu 0000:04:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 8
[ 4.139443] amdgpu 0000:04:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 8
[ 4.139444] amdgpu 0000:04:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 8
[ 4.139445] amdgpu 0000:04:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 8
[ 4.141078] [drm] Initialized amdgpu 3.54.0 20150101 for 0000:04:00.0 on minor 1
[ 4.147509] fbcon: amdgpudrmfb (fb0) is primary device
[ 4.147823] [drm] DSC precompute is not needed.
[ 4.854418] Console: switching to colour frame buffer device 240x67
[ 4.874494] amdgpu 0000:04:00.0: [drm] fb0: amdgpudrmfb frame buffer device
[ 11.871434] Key type trusted registered
[ 11.886779] Key type encrypted registered
...
[ 3001.667474] ThreadPoolForeg: segfault at 3fe173700008 ip 00005632b4aca97b sp 00007f667e7efdc0 error 4 in electron[5632b332f000+7732000] likely on CPU 0 (core 0, socket 0)
[ 3001.667500] Code: 06 48 03 08 5d e9 25 0c 00 00 cc cc cc cc cc 55 48 89 e5 41 57 41 56 41 55 41 54 53 48 83 ec 18 49 89 cd 49 81 e5 00 00 fc ff f6 45 08 40 0f 85 a1 00 00 00 49 89 cf 49 89 f6 80 7f 3a 00 75
[ 4538.486544] electron: segfault at 80000000008 ip 00005578c8450e12 sp 00007fff90612410 error 4 in electron[5578c26d9000+7aaf000] likely on CPU 4 (core 5, socket 0)
[ 4538.486557] Code: f0 0f b1 0f 75 f2 eb 06 67 e8 7a 7d dc fe 48 8b bb b0 01 00 00 48 85 ff 0f 85 8e 01 00 00 48 8b bb a8 01 00 00 48 85 ff 74 24 47 08 a8 02 75 1d 8b 07 0f 1f 44 00 00 83 f8 01 74 0b 8d 48 ff
[ 4595.501146] Isolated Web Co: segfault at 7702dd668c80 ip 00007f02e972e336 sp 00007ffc2f669840 error 4 in libxul.so[7f02e8f3a000+5f91000] likely on CPU 4 (core 5, socket 0)
[ 4595.501158] Code: 24 20 48 8b b4 24 a0 00 00 00 48 85 f6 0f 84 2c 01 00 00 8b 84 24 a8 00 00 00 48 3d ff ff ff 7f 0f 83 4e 0b 00 00 48 8b 4d 00 11 0f ba e2 1e 0f 83 67 01 00 00 8b 79 08 48 29 f9 4c 89 4c 24
this is output of eglinfo -B
:
GBM platform:
eglinfo: eglInitialize failed
Wayland platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES
OpenGL core profile vendor: AMD
OpenGL core profile renderer: AMD Radeon Graphics (radeonsi, renoir, LLVM 16.0.6, DRM 3.54, 6.6.9-arch1-1)
OpenGL core profile version: 4.6 (Core Profile) Mesa 23.3.2-arch1.2
OpenGL core profile shading language version: 4.60
OpenGL compatibility profile vendor: AMD
OpenGL compatibility profile renderer: AMD Radeon Graphics (radeonsi, renoir, LLVM 16.0.6, DRM 3.54, 6.6.9-arch1-1)
OpenGL compatibility profile version: 4.6 (Compatibility Profile) Mesa 23.3.2-arch1.2
OpenGL compatibility profile shading language version: 4.60
OpenGL ES profile vendor: AMD
OpenGL ES profile renderer: AMD Radeon Graphics (radeonsi, renoir, LLVM 16.0.6, DRM 3.54, 6.6.9-arch1-1)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 23.3.2-arch1.2
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20
X11 platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES
OpenGL core profile vendor: AMD
OpenGL core profile renderer: AMD Radeon Graphics (radeonsi, renoir, LLVM 16.0.6, DRM 3.54, 6.6.9-arch1-1)
OpenGL core profile version: 4.6 (Core Profile) Mesa 23.3.2-arch1.2
OpenGL core profile shading language version: 4.60
OpenGL compatibility profile vendor: AMD
OpenGL compatibility profile renderer: AMD Radeon Graphics (radeonsi, renoir, LLVM 16.0.6, DRM 3.54, 6.6.9-arch1-1)
OpenGL compatibility profile version: 4.6 (Compatibility Profile) Mesa 23.3.2-arch1.2
OpenGL compatibility profile shading language version: 4.60
OpenGL ES profile vendor: AMD
OpenGL ES profile renderer: AMD Radeon Graphics (radeonsi, renoir, LLVM 16.0.6, DRM 3.54, 6.6.9-arch1-1)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 23.3.2-arch1.2
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20
Surfaceless platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES
OpenGL core profile vendor: AMD
OpenGL core profile renderer: AMD Radeon Graphics (radeonsi, renoir, LLVM 16.0.6, DRM 3.54, 6.6.9-arch1-1)
OpenGL core profile version: 4.6 (Core Profile) Mesa 23.3.2-arch1.2
OpenGL core profile shading language version: 4.60
OpenGL compatibility profile vendor: AMD
OpenGL compatibility profile renderer: AMD Radeon Graphics (radeonsi, renoir, LLVM 16.0.6, DRM 3.54, 6.6.9-arch1-1)
OpenGL compatibility profile version: 4.6 (Compatibility Profile) Mesa 23.3.2-arch1.2
OpenGL compatibility profile shading language version: 4.60
OpenGL ES profile vendor: AMD
OpenGL ES profile renderer: AMD Radeon Graphics (radeonsi, renoir, LLVM 16.0.6, DRM 3.54, 6.6.9-arch1-1)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 23.3.2-arch1.2
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20
Device platform:
Device #0:
Platform Device platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES
OpenGL core profile vendor: AMD
OpenGL core profile renderer: AMD Radeon Graphics (radeonsi, renoir, LLVM 16.0.6, DRM 3.54, 6.6.9-arch1-1)
OpenGL core profile version: 4.6 (Core Profile) Mesa 23.3.2-arch1.2
OpenGL core profile shading language version: 4.60
OpenGL compatibility profile vendor: AMD
OpenGL compatibility profile renderer: AMD Radeon Graphics (radeonsi, renoir, LLVM 16.0.6, DRM 3.54, 6.6.9-arch1-1)
OpenGL compatibility profile version: 4.6 (Compatibility Profile) Mesa 23.3.2-arch1.2
OpenGL compatibility profile shading language version: 4.60
OpenGL ES profile vendor: AMD
OpenGL ES profile renderer: AMD Radeon Graphics (radeonsi, renoir, LLVM 16.0.6, DRM 3.54, 6.6.9-arch1-1)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 23.3.2-arch1.2
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20
Device #1:
Platform Device platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES
OpenGL core profile vendor: Mesa
OpenGL core profile renderer: llvmpipe (LLVM 16.0.6, 256 bits)
OpenGL core profile version: 4.5 (Core Profile) Mesa 23.3.2-arch1.2
OpenGL core profile shading language version: 4.50
OpenGL compatibility profile vendor: Mesa
OpenGL compatibility profile renderer: llvmpipe (LLVM 16.0.6, 256 bits)
OpenGL compatibility profile version: 4.5 (Compatibility Profile) Mesa 23.3.2-arch1.2
OpenGL compatibility profile shading language version: 4.50
OpenGL ES profile vendor: Mesa
OpenGL ES profile renderer: llvmpipe (LLVM 16.0.6, 256 bits)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 23.3.2-arch1.2
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20
These are my kernel parameters:
Kernel command line: initrd=\amd-ucode.img initrd=\initramfs-linux.img root="LABEL=arch_os" rw i915.enable_psr=0 rd.luks.name=02e...eee=root CONFIG_DRM_AMDGPU_CIK=Y
---
## What I tried:
- I installed AMD microcode and set it up in loader options in systemdboot
- I updated kernel to newest one
- I installed xf86-video-amdgpu
- I updated all firmware using fwupdmgr
- I uninstalled X.org drivers (xf86-video-amdgpu
)
- I uninstalled all amdvlk
drivers and installed radeon drivers
- I installed desktop portals
- I added CONFIG_DRM_AMDGPU_CIK=Y
to kernel parameters. This results in Unknown kernel command line parameters "CONFIG_DRM_AMDGPU_CIK=Y", will be passed to user space.
in dmesg.
- I tried to addd radeon.dpm=0
and radeon.dpm=1
with no effect
- I tried to log debug log of sway and found nothing interesting
- I deleted ~/.cache/mesa
directory
- Adding 8gb swap helps a bit with freezing but does not resolve crashes. Programs just crash faster.
Nothing seems to resolve this issue.
---
## Question
What should I do to get rid of this freezes and crashes ? Do you have any tips how to diagnose these kind of issues ?
Thank you for help
Jan Černý
(1723 rep)
Dec 15, 2023, 06:42 PM
• Last activity: Feb 13, 2024, 11:06 PM
4
votes
1
answers
542
views
Lm_sensors not reading gfx card temperature right
I have ran sensors-detect and lm_sensors still returns the following. radeon-pci-0100 Adapter: PCI adapter temp1: +511.0°C (crit = +120.0°C, hyst = +90.0°C) coretemp-isa-0000 Adapter: ISA adapter Physical id 0: +47.0°C (high = +87.0°C, crit = +105.0°C) Core 0: +46.0...
I have ran sensors-detect and lm_sensors still returns the following.
radeon-pci-0100
Adapter: PCI adapter
temp1: +511.0°C (crit = +120.0°C, hyst = +90.0°C)
coretemp-isa-0000
Adapter: ISA adapter
Physical id 0: +47.0°C (high = +87.0°C, crit = +105.0°C)
Core 0: +46.0°C (high = +87.0°C, crit = +105.0°C)
Core 1: +47.0°C (high = +87.0°C, crit = +105.0°C)
guesy66213
(51 rep)
May 2, 2014, 08:50 PM
• Last activity: Jan 29, 2024, 01:20 AM
0
votes
0
answers
39
views
Radeon card on computer may is defect after current problems. How to check? sddm not start, card detected but no vram
Radeon card on computer may is defect after current problems. How to check? sddm not start, card detected but no vram My raddeon sapphire has 3 fans. These fans were only turning when had gpu loads to do. Otherwise, in reboot they were still. However, now all three fans working continously. Display...
Radeon card on computer may is defect after current problems. How to check? sddm not start, card detected but no vram
My raddeon sapphire has 3 fans. These fans were only turning when had gpu loads to do. Otherwise, in reboot they were still. However, now all three fans working continously.
Display says null display. Sddm is stuch on logind message. My terminal "font" is the basic (large letters) and not the "high-end" font of a graphic card (small letters), as previously.
By the local current problems in Greece (due to fires and heat), i dont know if my graphic card has problem or not. I cant find any util to test its "integrity".
I have gpu utils. It is detected by system as radeon but what else i can do to see if it can work or it is for trash?
- Sddm says is starting but no display in tty7.
- gpu-chk utils says all green and some oranges
- most test utils must open a display to test graphic card

UPDATE 1: I changed from sddm to lightdm display manager. However monitor started to low resolution (1080x -75hz). It appears that i cannot change it
UPDATE 2: radeonontop when using glmark2 and glxgear is all values "0".
It appears that GPU is off. VRAM is not detected by radeonontop
it appears that only some very basic display things is working from radeon card :(
See my whole dmesg (nothing of value)
here
my /etc/modules contains only
AMDPowerProfiler
SOLUTION led by Artem S. Tashkinov
running


sudo modprobe amdgpu
but it was not permanent
i found out that for some reason, amdgpu was blacklisted in my system
at etc/modprobe.d/blacklist-amdgpu.conf
.
I dont know neither the reason nor the process that led to that.
However, after commenting the line, it was fixed. Thanks.
Estatistics
(350 rep)
Jul 24, 2023, 02:54 PM
• Last activity: Jul 24, 2023, 08:09 PM
0
votes
1
answers
308
views
Blender not detecting Radeon graphics card on OpenSuse
I freshly installed OpenSuse on my Laptop, but blender does not seam to detect my Graphics card. I come from Nobrara(Fedora) where everything worked fine as long as I staid on the blender lts 3.3 so I know my card supports hip. I also installed vkbench, which was able detect my card and use it.\ Ble...
I freshly installed OpenSuse on my Laptop, but blender does not seam to detect my Graphics card. I come from Nobrara(Fedora) where everything worked fine as long as I staid on the blender lts 3.3 so I know my card supports hip. I also installed vkbench, which was able detect my card and use it.\
Blender Error Edit → Preferences → System → HIP →
> No compatible GPUs found for Cycles Requires AMD GPU with Vega or RDNA
> architecture and AMD driver version 22.10 or newer
These are the infos I got with zypper info
> libdrm_amdgpu1:\
> 2.4.115-2.2
> kernel-firmware-amdgpu: \
> 20230320-1.1
Neither of them seam to resemble the version number 22.10, but amd does only offer pro driver for Windows on my card.
System:\
OS: OpenSuse Tumbleweed Wayland\
GPU: RX 5600M
Heimchen Heimelig
(1 rep)
Apr 8, 2023, 05:42 PM
• Last activity: Jun 20, 2023, 02:00 PM
8
votes
2
answers
18795
views
Freeze at startup with error “fb: switching to radeondrmfb from EFI VGA”
I'll preface this by saying I've been searching high and low for a solution, and the closest thing I found was [this][1] thread over at [Ask Different][2]. *Background*: I have an ailing MacBook Pro 1,1 that I am trying to breathe a second life into using Linux to do some C++ development work. Eclip...
I'll preface this by saying I've been searching high and low for a solution, and the closest thing I found was this thread over at Ask Different .
*Background*: I have an ailing MacBook Pro 1,1 that I am trying to breathe a second life into using Linux to do some C++ development work. Eclipse is my IDE of choice (mainly so I can be consistent with other computers I have around the house), so I kind of need X/a-GUI-of-some-sort. I've completed a plain Jane install of Debian (Jessie) using the i686 build, and the system is pretty damn solid. However, the system freezes with this error message on boot:
fb: switching to radeondrmfb from EFI VGA
The fix found at Think Different was to add
nomodeset
as a boot option. This gets me into the system, and it is passably usable, but can be better, I'm sure. Some information on the setup:
- Debian (Jessie) build
- I have tried recompiling a 3.x kernel to see if it was something in the newer 4.x kernel, but the problem persists
- Using the latest rEFInd to boot into the system
- lspci -nnk
reports VGA compatible controller : Advanced Micro Devices, Inc. [AMD/ATI] RV530/M56-P [Mobility Radeon X1600] [1002:71c5]
for my graphics card
The issue sounds similar to this one, which also does not have an answer. It has been almost a full decade (if not more) since I've played with Linux (think 2.2.x series kernels when PowerPC was cutting edge), so some of this stuff is very very new to me. So some high level questions.
- What the heck is nomodeset, and what does it do? The closest answer I've found is that nomodeset tells the (newer) Linux kernels not to do any of the heavy lifting with the video card -- presumably this is because video drivers were moved into the kernel? I'm not sure how accurate that is.
- Are there other kernel options I may be able to try? I could not find an exhaustive list of options - some are specific to distros, some to boot loaders, etc.
- If I can boot into the system using nomodeset as a kernel prompt, is there a way to load the Radeon driver after the fact?
- Barring that, can I not configure X in some way to use hardware video rendering vs. software video rendering? I envision booting into text-only mode, and then updating some config option in X, then launching X.
tendim
(181 rep)
Jun 13, 2017, 09:41 PM
• Last activity: Jun 17, 2023, 09:22 PM
47
votes
2
answers
71627
views
xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
I get this error in Xorg.0.log > xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted) Googling quickly reveals that this error is caused by starting Xorg as non root user. Problem is that I'm running this as root. Next possible cause SELinux, that is diabled too. Any other possibl...
I get this error in Xorg.0.log
> xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted)
Googling quickly reveals that this error is caused by starting Xorg as non root user. Problem is that I'm running this as root.
Next possible cause SELinux, that is diabled too.
Any other possible causes of this error?
My graphicscard is
> 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] (prog-if 00 [VGA controller])
But I have severe problems with the drivers, so I'm trying to run as Vesa, using this xorg.conf
> Section "Device"
> Identifier "Videocard0"
> Driver "vesa"
> EndSection
Kjeld Flarup
(628 rep)
Oct 3, 2014, 05:41 PM
• Last activity: Feb 22, 2023, 08:36 AM
8
votes
6
answers
26712
views
How to enable 2560x1440 option for display in Linux Mint?
I just got a new display (Samsung LC27JG50QQU, 1440p, 144hz) which is plugged into my AMD Radeon HD 6950 (DVI-D, DVI-I, HDMI 1.4, 2x Mini DisplayPort) graphics card using HDMI. However, it only lets me set 1080p max in my display settings. Cable and monitor were fine on 1440p with my MacBook Pro. I...
I just got a new display (Samsung LC27JG50QQU, 1440p, 144hz) which is plugged into my AMD Radeon HD 6950 (DVI-D, DVI-I, HDMI 1.4, 2x Mini DisplayPort) graphics card using HDMI. However, it only lets me set 1080p max in my display settings. Cable and monitor were fine on 1440p with my MacBook Pro.
I am running Linux Mint 19.1 Tessa
This is the output
xrandr
gives:
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 16384 x 16384
DisplayPort-3 disconnected (normal left inverted right x axis y axis)
DisplayPort-4 disconnected (normal left inverted right x axis y axis)
HDMI-3 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 597mm x 336mm
1920x1080 60.00* 50.00 59.94
1680x1050 59.88
1600x900 60.00
1280x1024 75.02 60.02
1440x900 59.90
1280x800 59.91
1152x864 75.00
1280x720 60.00 50.00 59.94
1024x768 75.03 70.07 60.00
832x624 74.55
800x600 72.19 75.00 60.32 56.25
720x576 50.00
720x480 60.00 59.94
640x480 75.00 72.81 66.67 60.00 59.94
720x400 70.08
DVI-0 disconnected (normal left inverted right x axis y axis)
DVI-1 disconnected (normal left inverted right x axis y axis)
VGA-1-1 disconnected (normal left inverted right x axis y axis)
HDMI-1-1 disconnected (normal left inverted right x axis y axis)
DP-1-1 disconnected (normal left inverted right x axis y axis)
HDMI-1-2 disconnected (normal left inverted right x axis y axis)
HDMI-1-3 disconnected (normal left inverted right x axis y axis)
DP-1-2 disconnected (normal left inverted right x axis y axis)
DP-1-3 disconnected (normal left inverted right x axis y axis)
lspci -k | grep -EA3 'VGA|3D|Display'
:
00:02.0 Display controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
Subsystem: Gigabyte Technology Co., Ltd 2nd Generation Core Processor Family Integrated Graphics Controller
Kernel driver in use: i915
Kernel modules: i915
--
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cayman PRO [Radeon HD 6950]
Subsystem: Hightech Information System Ltd. Cayman PRO [Radeon HD 6950]
Kernel driver in use: radeon
Kernel modules: radeon
glxinfo | grep -i vendor
:
server glx vendor string: SGI
client glx vendor string: Mesa Project and SGI
Vendor: X.Org (0x1002)
OpenGL vendor string: X.Org
EDID:
00ffffffffffff004c2d560f4d325530
071d0103803c22782a1375a757529b25
105054bfef80b300810081c081809500
a9c0714f0101565e00a0a0a029503020
350055502100001a000000fd00324b1b
5919000a202020202020000000fc0043
32374a4735780a2020202020000000ff
0048544f4d3230303034340a2020014d
02031bf146901f041303122309070783
01000067030c0010008032023a801871
Bart
(97 rep)
Oct 20, 2019, 11:06 PM
• Last activity: Nov 22, 2022, 12:47 PM
0
votes
0
answers
207
views
Enable ATI GPU work on debian 11
I'm on an old laptop with AMD ATI Radeon 6490 M. With default kernel parameters any Linux [freezes](https://unix.stackexchange.com/questions/716790/debian-opensuse-freeze-dead-on-boot-with-an-ati-gpu) on booting, which I fixed by disabling the discrete AMD gpu completely: ``` radeon.modeset=0 amdgpu...
I'm on an old laptop with AMD ATI Radeon 6490 M. With default kernel parameters any Linux [freezes](https://unix.stackexchange.com/questions/716790/debian-opensuse-freeze-dead-on-boot-with-an-ati-gpu) on booting, which I fixed by disabling the discrete AMD gpu completely:
radeon.modeset=0 amdgpu.runpm=0 acpi_backlight=intel_blacklight
It makes it boot, but I want the GPU to work (mainly because I want to unload the CPU and perhaps the battery will last longer?).
This
radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 amdgpu.dc=1
doesn't help either: it still freezes exactly the same way.
[This](https://wiki.archlinux.org/title/ATI#Installation) arch wiki suggestion to install mesa
didn't change anything either, still freezes.
I also tried pulling the driver from [my exact GPU official webpage](https://www.amd.com/en/support/graphics/amd-radeon-hd/amd-radeon-hd-6000m-series/amd-radeon-hd-6490m) , but it gives error something like "the driver only supports X server versions 6.9 to 1.10, yours is 1.20".
Any idea how to make it actually work?
WhiteBlackGoose
(13 rep)
Oct 18, 2022, 04:14 PM
• Last activity: Oct 18, 2022, 04:43 PM
1
votes
1
answers
1474
views
How can I get a two-display Radeon HD 3470 graphics setup working with Scientific Linux 6.5?
I have Scientific Linux 6.5 (2.6.32-431.11.2.el6.x86_64) installed on a Dell OptiPlex 760 with a Radeon HD 3470 graphics card and two displays hooked up to it. I'm having difficulties setting resolutions appropriate for the displays and having the two displays not show the same screen. I am not an e...
I have Scientific Linux 6.5 (2.6.32-431.11.2.el6.x86_64) installed on a Dell OptiPlex 760 with a Radeon HD 3470 graphics card and two displays hooked up to it. I'm having difficulties setting resolutions appropriate for the displays and having the two displays not show the same screen. I am not an expert in Xorg configuration and I would appreciate some assistance in getting things working.
The PCI device listing (
| grep VGA
) for the graphics card is as follows:
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV620 PRO [Radeon HD 3470]
A more detailed listing (-v -s $(lspci | awk '/VGA/{print $1}')
) is as follows:
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV620 PRO [Radeon HD 3470] (prog-if 00 [VGA controller])
Subsystem: Dell Device 3243
Flags: bus master, fast devsel, latency 0, IRQ 16
Memory at d0000000 (64-bit, prefetchable) [size=256M]
Memory at fe9f0000 (64-bit, non-prefetchable) [size=64K]
I/O ports at dc00 [size=256]
Expansion ROM at fea00000 [disabled] [size=128K]
Capabilities: Power Management version 3
Capabilities: Express Legacy Endpoint, MSI 00
Capabilities: [a0] MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities: Vendor Specific Information: ID=0001 Rev=1 Len=010
Kernel modules: radeon
The result of an
query (-q
) is as follows:
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 640 x 400, current 1280 x 1024, maximum 1280 x 1024
default connected 1280x1024+0+0 0mm x 0mm
1280x1024 0.0*
1152x864 0.0
1024x768 0.0
800x600 0.0
640x480 0.0
720x400 0.0
The modeline returned by the coordinated video timing utility
for the highest resolution capable by the main display (1680 x 1050) is as follows:
cvt 1680 1050
# 1680x1050 59.95 Hz (CVT 1.76MA) hsync: 65.29 kHz; pclk: 146.25 MHz
Modeline "1680x1050_60.00" 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync
If I try to use this with xrandr
, I get the following:
xrandr --newmode "1680x1050_60.00" 146.25 1680 1784 1960 2240 1050 1053 1059 1089 -hsync +vsync
xrandr: Failed to get size of gamma for output default
The entire contents of the /etc/X11/xorg.conf
file is as follows:
Section "Device"
Identifier "Videocard0"
Driver "vesa"
EndSection
I am not sure what to do next in order to get the appropriate resolutions set and to get the two displays working as two separate displays (as opposed to having the mirror behaviour).
---
UPDATE: I have attempted to install a driver for this graphics setup (-8.97.100.7-1.x86_64.rpm
), but have run into difficulties regarding undefined symbol
. The ending contents of the file .0.log
are as follows:
[ 39.312] Initializing built-in extension XVideo
[ 39.312] Initializing built-in extension XVideo-MotionCompensation
[ 39.312] Initializing built-in extension SELinux
[ 39.312] Initializing built-in extension XFree86-VidModeExtension
[ 39.312] Initializing built-in extension XFree86-DGA
[ 39.312] Initializing built-in extension XFree86-DRI
[ 39.312] Initializing built-in extension DRI2
[ 39.312] (II) "glx" will be loaded by default.
[ 39.312] (II) LoadModule: "glx"
[ 39.338] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
[ 39.358] (II) Module glx: vendor="Advanced Micro Devices, Inc."
[ 39.358] compiled for 6.9.0, module version = 1.0.0
[ 39.365] Loading extension GLX
[ 39.366] (II) LoadModule: "fglrx"
[ 39.366] (II) Loading /usr/lib64/xorg/modules/drivers/fglrx_drv.so
[ 39.520] (EE) Failed to load /usr/lib64/xorg/modules/drivers/fglrx_drv.so: /usr/lib64/xorg/modules/drivers/fglrx_drv.so: undefined symbol: noXFree86DRIExtension
[ 39.520] (II) UnloadModule: "fglrx"
[ 39.520] (II) Unloading fglrx
[ 39.520] (EE) Failed to load module "fglrx" (loader failed, 7)
[ 39.520] (EE) No drivers available.
[ 39.520]
Fatal server error:
[ 39.520] no screens found
[ 39.520] (EE)
Please consult the Red Hat, Inc. support
at https://www.redhat.com/apps/support/
for help.
[ 39.520] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 39.520] (EE)
d3pd
(131 rep)
Mar 31, 2014, 11:22 AM
• Last activity: Jun 14, 2022, 01:03 PM
1
votes
0
answers
328
views
debian : disable discrete gpu
I searched and only found an article written by 2012 which is too old. I have HD 5450 and GT610 and Ryzen 5700G on msi b550 (I study KVM),and I want to disable HD 5450 and GT610 on normal time. Is there any solution or another plan such as switch ,except BIOS modify?
I searched and only found an article written by 2012 which is too old.
I have HD 5450 and GT610 and Ryzen 5700G on msi b550 (I study KVM),and I want to disable HD 5450 and GT610 on normal time.
Is there any solution or another plan such as switch ,except BIOS modify?
张绍峰
(135 rep)
May 28, 2022, 10:09 PM
• Last activity: May 29, 2022, 12:28 AM
1
votes
3
answers
8382
views
How well will the AMD Radeon HD 7950 gpu perform on Linux?
The time has come for me to upgrade my aging gpu (9800 gt). The AMD 7950 has caught my attention because of the attractive price with pleasing benchmarks. But it is common knowledge that AMD GPUs have poor support on Linux. What sort of performance can I expect, with say, the latest version of Ubunt...
The time has come for me to upgrade my aging gpu (9800 gt). The AMD 7950 has caught my attention because of the attractive price with pleasing benchmarks. But it is common knowledge that AMD GPUs have poor support on Linux.
What sort of performance can I expect, with say, the latest version of Ubuntu? Will I have issues starting X. Will I have issues with a dual monitor setup? Will basic games such as minecraft or neverball play as expected without problems? Will there be any issues with video playback or flash?
I tried doing some research with how this card performs on Linux, but google lacks any usable resources.
If the 7950 is completely useless when paired with a Linux system, can someone suggest a comparable nvidia gpu for the same price range with similar performance?
TheOne
(113 rep)
Mar 18, 2013, 02:37 PM
• Last activity: Feb 7, 2022, 11:07 AM
0
votes
0
answers
241
views
Why do I have libdrm-amdgpu1 and libdrm-radeon1 folders?
Why do I have libdrm-amdgpu1 and libdrm-radeon1 folders? My HP Envy has an integrated Intel gpu and an NVidia MX 250 dedicated gpu. These folders are located in some snap applications ( Pinta and pyqt5-runtime ) as well as in usr/share. Is that because the kernel has so many drivers build in? Can I...
Why do I have libdrm-amdgpu1 and libdrm-radeon1 folders? My HP Envy has an integrated Intel gpu and an NVidia MX 250 dedicated gpu. These folders are located in some snap applications ( Pinta and pyqt5-runtime ) as well as in usr/share. Is that because the kernel has so many drivers build in? Can I delete those folders? They are only small, but since they have have no use is it possible to get rid of them for good?And if yes, how? ( The snaps are mounted as loops and I don't seem to be able to unmount them.)
I run:
Operating System: Kubuntu 20.04
KDE Plasma Version: 5.18.7
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8
Kernel Version: 5.15.5-051505-generic
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz
Memory: 15,3 GiB
in triple boot with Mint 20.2 Uma and Windows 10
Joepie Es
(111 rep)
Dec 10, 2021, 06:45 PM
• Last activity: Jan 23, 2022, 07:10 AM
4
votes
1
answers
1024
views
radeon power management
Checking upon `/sys/kernel/debug/dri/0/radeon_pm_info`, puzzled me. It seems that there are only one power level and some are disabled. It shows : uvd disabled vce disabled power level 0 sclk: 30000 vddc: 3800 Why are they disabled and there are only one power level? **Background** I'm using a lapto...
Checking upon
/sys/kernel/debug/dri/0/radeon_pm_info
, puzzled me. It seems that there are only one power level and some are disabled.
It shows :
uvd disabled
vce disabled
power level 0 sclk: 30000 vddc: 3800
Why are they disabled and there are only one power level?
**Background**
I'm using a laptop with AMD A6-6310 APU with AMD Radeon R4 Graphics with the default open source radeon
kernel module. Compared to the fglrx
module, the battery usage is about 6 mW, as reported by powertop, but when the radeon
kernel module was used in the same scenario, the battery usage is 11mW. I tried setting these and it did not change much :
echo low > /sys/class/drm/card0/device/power_dpm_force_performance_level
echo battery > /sys/class/drm/card0/device/power_dpm_state.
user128712
(141 rep)
Jul 6, 2015, 12:30 PM
• Last activity: Jan 15, 2022, 03:15 AM
0
votes
1
answers
1016
views
Running AMD Radeon HD 7870 XT Tahiti on Ubuntu 20.04 LTS
First of all, I'm new to the Linux world with graphical UIs and I only have some experience in using "headless" terminal only unix varieties. I'm unsuccessfully trying to run an older intel i5-750 computer with an AMD Radeon HD 7870 XT Tahiti PCIE graphics card. I installed a fresh copy of Ubuntu 20...
First of all, I'm new to the Linux world with graphical UIs and I only have some experience in using "headless" terminal only unix varieties.
I'm unsuccessfully trying to run an older intel i5-750 computer with an AMD Radeon HD 7870 XT Tahiti PCIE graphics card.
I installed a fresh copy of Ubuntu 20.04 LTS with kernel
I tested all of the video cards outputs, HDMI, DVI, DisplayPort 1, DisplayPort 2 with the same results.
I'm currently running ubuntu in recovery mode without any loaded video drivers without any other problems. The output of
anni@APOLLON:~$ uname -a
Linux APOLLON 5.8.0-53-generic #60~20.04.1-Ubuntu SMP Thu May 6 09:52:46 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
and on bootup of the computer, after seeing the ubuntu boot logo the screen just shows this weird pattern as shown in the photo below

lspci
is
anni@APOLLON:~$ lspci
...
07:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti LE [Radeon HD 7870 XT]
...
The hardware is OK as it is running perfectly fine under Windows 10 so it must be a driver/configuration issue I cannot fathom.
Does anybody have any clues on what to do to get opengl/mesa grahpics acceleration working? I want to use the computer for some custom accelerated 3D visualization work.
Marcus
(101 rep)
May 16, 2021, 11:57 AM
• Last activity: Nov 18, 2021, 04:57 PM
Showing page 1 of 20 total questions