Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux? |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
09-16-2023, 06:46 PM
|
#1
|
Member
Registered: Dec 2018
Posts: 39
Rep: 
|
amd hardware graphics acceleration quit working with no clear cause
today i had problems with my keyboard/usb ports, which was quickly resolved, but when i logged back onto the system i got a message (image i linked in the attachments), but i havent changed anything besides resetting my user password (thru root terminal in safemode) and changing out my keyboard.
my system was running fine for months since i installed linux mint 20.3, ive had no problems with graphics until today, but now the hardware acceleration is gone and my framerate is crap.
why would my gpu just stop working like that? i suspect there may be something wrong with my motherboard now.
i have had minor usb problems previously but if it has spread to the gpu i dont understand how.
gpu: Radeon R7 260X/360
os: linux mint 20.3 cinnamon
cinnamon version: 5.2.7
motherboard info: gigabyte GA-78LMT-S2 64bit
cpu: amd fx4300
|
|
|
09-16-2023, 07:27 PM
|
#2
|
LQ Guru
Registered: Aug 2016
Location: SE USA
Distribution: openSUSE 24/7; Debian, Knoppix, Mageia, Fedora, OS/2, others
Posts: 6,355
|
For serious help, consider providing actual diagnostic information, such as pasting inxi -GSaz input/output here using code tags, and pastebinning Xorg.0.log, whether you find it in /var/log/ or in ~/.local/share/xorg/. Note: 20.3 provides an antique inxi of little value for graphics troubleshooting. Latest inxi can be had from here.
|
|
|
09-16-2023, 07:47 PM
|
#3
|
Member
Registered: Dec 2018
Posts: 39
Original Poster
Rep: 
|
System:
Kernel: 5.4.0-91-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
parameters: BOOT_IMAGE=/boot/vmlinuz-5.4.0-91-generic
root=UUID=e70eda8e-9544-4de8-b5a8-d0b9da860bff ro recovery nomodeset
dis_ucode_ldr
Desktop: Cinnamon 5.2.7 wm: muffin 5.2.1 dm: LightDM 1.30.0
Distro: Linux Mint 20.3 Una base: Ubuntu 20.04 focal
Graphics:
Device-1: AMD Bonaire XTX [Radeon R7 260X/360] vendor: XFX Pine
driver: N/A bus ID: 01:00.0 chip ID: 1002:6658
Display: x11 server: X.Org 1.20.13 driver: ati,vesa
unloaded: fbdev,modesetting,radeon resolution: 1920x1080~N/A
OpenGL: renderer: llvmpipe (LLVM 12.0.0 256 bits) v: 4.5 Mesa 21.2.6
compat-v: 3.1 direct render: Yes
|
|
|
09-16-2023, 07:51 PM
|
#4
|
Member
Registered: Dec 2018
Posts: 39
Original Poster
Rep: 
|
|
|
|
09-17-2023, 02:10 AM
|
#5
|
LQ Guru
Registered: Aug 2016
Location: SE USA
Distribution: openSUSE 24/7; Debian, Knoppix, Mageia, Fedora, OS/2, others
Posts: 6,355
|
All my 20.x installations have been upgraded to now 21.2, so I can't reproduce the software versions your replies show.
Your "pastebin" job is useless here. I have no access rights on that site, apparently required to access others' pastes, and have no intention of getting any. You should have a pastebinit command on your system to pastebin to a more accessible location. If not, install it. If you use Nemo, you can use its built-in paste extension for pastebinning.
Your Bonaire and my Kaveri are both GCN2 generation, so very similar. This is what your inxi output should resemble if you followed my instruction:
Code:
$ inxi -GSaz --vs --zl --hostname
inxi 3.3.29-00 (2023-08-15)
System:
Host: ara88 Kernel: 6.2.0-32-generic arch: x86_64 bits: 64 compiler: N/A
clocksource: tsc available: hpet,acpi_pm parameters: BOOT_IMAGE=/vmlinuz
root=LABEL=<filter> noresume ipv6.disable=1 plymouth.enable=0
net.ifnames=0 radeon.cik_support=0 amdgpu.cik_support=1 consoleblank=0
preempt=full mitigations=off
Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.33 info: xfce4-panel wm: xfwm
v: 4.18.0 vt: 7 dm: LightDM v: 1.30.0 Distro: Linux Mint 21.2 Victoria
base: Ubuntu 22.04 LTS Jammy
Graphics:
Device-1: AMD Kaveri [Radeon R7 Graphics] vendor: ASRock driver: amdgpu
v: kernel alternate: radeon arch: GCN-2 code: Sea Islands
process: GF/TSMC 16-28nm built: 2013-17 ports: active: DP-1,DVI-D-1
empty: HDMI-A-1,VGA-1 bus-ID: 00:01.0 chip-ID: 1002:130f class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.4 compositor: xfwm v: 4.18.0 driver:
X: loaded: amdgpu unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu
display-ID: :0 screens: 1
Screen-1: 0 s-res: 3600x1440 s-dpi: 96 s-size: 953x381mm (37.52x15.00")
s-diag: 1026mm (40.41")
Monitor-1: DVI-D-1 mapped: DVI-D-0 pos: right model: Dell P2213
serial: <filter> built: 2012 res: 1680x1050 hz: 60 dpi: 90 gamma: 1.2
size: 473x296mm (18.62x11.65") diag: 558mm (22") ratio: 16:10 modes:
max: 1680x1050 min: 720x400
Monitor-2: DP-1 mapped: DisplayPort-0 pos: primary,left
model: Acer K272HUL serial: <filter> built: 2018 res: 2560x1440 hz: 60
dpi: 109 gamma: 1.2 size: 598x336mm (23.54x13.23") diag: 686mm (27")
ratio: 16:9 modes: max: 2560x1440 min: 720x400
API: OpenGL v: 4.6 Mesa 23.0.4-0ubuntu1~22.04.1 renderer: KAVERI (kaveri
LLVM 15.0.7 DRM 3.49 6.2.0-32-generic) direct-render: Yes
$
Your kernel parameters include recovery and nomodeset. Nomodeset in particular is bad news for graphics performance, essentially killing it. It's designed mainly to assist in troubleshooting. Your "driver: N/A" and "driver: ati,vesa" are negative consequences of nomodeset. Instead of "N/A" you should see "amdgpu", and instead of "ati,vesa" you should see either "amdgpu" or "modesetting", with amdgpu usually preferred.
Recovery among kernel parameters usually means you booted using a non-default recovery mode Grub selection. Why did you do that?
|
|
|
09-17-2023, 05:05 AM
|
#6
|
Member
Registered: Jan 2022
Location: Hanover, Germany
Distribution: Slackware
Posts: 307
Rep: 
|
Kernel 5.4.0 is very old and possibly too old for use with newer AMD GPUs like yours. amdgpu driver got some improvements in Kernel 5.10, but this kernel is quite old too. Use latest stable kernel 6.5.3 or latest longterm kernel 6.1.53 instead of an antique 5.x kernel.
If graphics problems persist after kernel upgrade it's time to check your hardware.
|
|
|
09-17-2023, 05:16 AM
|
#7
|
Member
Registered: Dec 2018
Posts: 39
Original Poster
Rep: 
|
the default grub recover thing i have no clue, i just looked up how to get to safemode and did it.
|
|
|
09-17-2023, 05:16 AM
|
#8
|
Member
Registered: Dec 2018
Posts: 39
Original Poster
Rep: 
|
|
|
|
09-17-2023, 06:07 AM
|
#9
|
Member
Registered: Dec 2018
Posts: 39
Original Poster
Rep: 
|
updating the kernel APPEARS TO have fixed the lack of hardware acceleration (i think it was the kernel that did that?), but that doesnt explain y it happened in the first place, again i will say that i changed nothing, it just happened.
|
|
|
09-17-2023, 07:53 AM
|
#10
|
Member
Registered: Jan 2022
Location: Hanover, Germany
Distribution: Slackware
Posts: 307
Rep: 
|
Quote:
Originally Posted by bobIsHere244
i will say that i changed nothing, it just happened.
|
Quote:
Originally Posted by bobIsHere244
besides resetting my user password (thru root terminal in safemode) and changing out my keyboard.
|
This is more than "nothing"!
Your system uses with kernel 5.4.0 only this awful VESA driver:
[ 84.956] (II) VESA(0): initializing int10 driver:
radeon driver isn't used due to used nomodeset kernel parameter:
[ 84.817] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-91-generic root=UUID=e70eda8e-9544-4de8-b5a8-d0b9da860bff ro recovery nomodeset dis_ucode_ldr
[ 84.952] (II) [KMS] drm report modesetting isn't supported.
[ 84.952] (EE) open /dev/dri/card0: No such file or directory
amdgpu driver seems to be unavailable.
To use amdgpu driver with a newer kernel you may have to update firmware package. These files are commonly located at /lib/firmware and there must exist a subdirectory /amdgpu filled with firmware files to use amdgpu driver.
Last edited by Arnulf; 09-17-2023 at 07:54 AM.
|
|
|
09-17-2023, 09:10 AM
|
#11
|
Member
Registered: Dec 2018
Posts: 39
Original Poster
Rep: 
|
Quote:
Originally Posted by Arnulf
This is more than "nothing"!
Your system uses with kernel 5.4.0 only this awful VESA driver:
[ 84.956] (II) VESA(0): initializing int10 driver:
radeon driver isn't used due to used nomodeset kernel parameter:
[ 84.817] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-91-generic root=UUID=e70eda8e-9544-4de8-b5a8-d0b9da860bff ro recovery nomodeset dis_ucode_ldr
[ 84.952] (II) [KMS] drm report modesetting isn't supported.
[ 84.952] (EE) open /dev/dri/card0: No such file or directory
amdgpu driver seems to be unavailable.
To use amdgpu driver with a newer kernel you may have to update firmware package. These files are commonly located at /lib/firmware and there must exist a subdirectory /amdgpu filled with firmware files to use amdgpu driver.
|
again, nothing changed, and i dont believe i have automatic updates enables, there was a bunch of stuff in the update cache waiting for me to activate it, whatever config my system was in regardless of how bad or good it was, it WORKED until 1 day it simply didnt, so yes it was nothing.
|
|
|
09-17-2023, 03:46 PM
|
#12
|
LQ Guru
Registered: Aug 2016
Location: SE USA
Distribution: openSUSE 24/7; Debian, Knoppix, Mageia, Fedora, OS/2, others
Posts: 6,355
|
Quote:
Originally Posted by bobIsHere244
the default grub recover thing i have no clue, i just looked up how to get to safemode and did it.
|
Why??? You cannot have nomodeset on the kernel cmdline with an AMD GPU and have competent graphics output. Recovery and safe Grub modes that include nomodeset are there to enable repairs to be made to a broken configuration.
|
|
|
09-17-2023, 04:39 PM
|
#13
|
LQ Guru
Registered: Aug 2016
Location: SE USA
Distribution: openSUSE 24/7; Debian, Knoppix, Mageia, Fedora, OS/2, others
Posts: 6,355
|
Quote:
Originally Posted by bobIsHere244
|
From that file:
Code:
# grep EE Xorg.0.log
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 84.952] (EE) open /dev/dri/card0: No such file or directory
[ 84.952] (EE) open /dev/dri/card0: No such file or directory
[ 84.953] (EE) open /dev/fb0: No such file or directory
[ 84.953] (EE) open /dev/fb0: No such file or directory
[ 84.953] (EE) Screen 0 deleted because of no matching config section.
[ 84.953] (EE) Screen 0 deleted because of no matching config section.
[ 84.953] (EE) Screen 0 deleted because of no matching config section.
#
Those (EE) lines (very bad errors) are a consequence of nomodeset:
Code:
[ 84.817] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-91-generic root=... ro recovery nomodeset dis_ucode_ldr
The amdgpu kernel and display drivers that competent graphics depend on cannot load when nomodeset is employed. We need to see Xorg.0.log from attemping to boot any Grub menu selection that omits nomodeset. You can do that by attempting such boot, then if you get only a black screen and Crtl-Alt-F3 fails to provide a login prompt, rebooting using nomodeset, then uploading Xorg.0.log.old instead of Xorg.0.log.
|
|
|
09-17-2023, 08:23 PM
|
#14
|
Member
Registered: Dec 2018
Posts: 39
Original Poster
Rep: 
|
maybe this was a consequence of entering recovery mode? but i dont know y that would persist like that.
|
|
|
09-17-2023, 10:09 PM
|
#15
|
LQ Guru
Registered: Aug 2016
Location: SE USA
Distribution: openSUSE 24/7; Debian, Knoppix, Mageia, Fedora, OS/2, others
Posts: 6,355
|
Show us what's in your Grub menu. When it appears, instead of booting right away, take a picture and show us what you see. Copy and paste here using code tags /etc/default/grub too. Also helpful could possibly be pastebinning /boot/grub/grub.cfg so we can maybe see what's gone wrong.
|
|
|
All times are GMT -5. The time now is 02:21 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|