F5F Stay Refreshed Software Operating Systems Issue with AMD GPU driver on Ubuntu 18.04

Issue with AMD GPU driver on Ubuntu 18.04

Issue with AMD GPU driver on Ubuntu 18.04

Pages (3): Previous 1 2 3 Next
B
Bobby_Tables
Junior Member
44
02-14-2019, 02:24 PM
#11
I moved to Manjaro but problems persist... YouTube frequently stops on Brave with the SIGSEGV error. I'm using kernel 5.9.3-1.
B
Bobby_Tables
02-14-2019, 02:24 PM #11

I moved to Manjaro but problems persist... YouTube frequently stops on Brave with the SIGSEGV error. I'm using kernel 5.9.3-1.

G
GG_on_the_STC
Junior Member
8
02-14-2019, 11:59 PM
#12
Use Chromium or Firefox for better performance. Brave isn't recommended.
G
GG_on_the_STC
02-14-2019, 11:59 PM #12

Use Chromium or Firefox for better performance. Brave isn't recommended.

L
Lord_Enrico
Junior Member
2
02-15-2019, 12:05 AM
#13
When it crashes, relevant entries show up in `journalctl --catalog --boot`. If you're new to this, the interface works identically to Vim. To dive deeper, press Shift+G. Use arrow keys or PgUp/Down to navigate lines. For searching, type "/" and enter your query like "sigsev" or "brave". Move through results with N and Shift+N. If possible, check the logs after a full crash by running `journalctl --catalog --boot=-1`. Avoid AMDGPU-Pro drivers—they're only needed for OpenCL. Consider adopting markdown in forums.
L
Lord_Enrico
02-15-2019, 12:05 AM #13

When it crashes, relevant entries show up in `journalctl --catalog --boot`. If you're new to this, the interface works identically to Vim. To dive deeper, press Shift+G. Use arrow keys or PgUp/Down to navigate lines. For searching, type "/" and enter your query like "sigsev" or "brave". Move through results with N and Shift+N. If possible, check the logs after a full crash by running `journalctl --catalog --boot=-1`. Avoid AMDGPU-Pro drivers—they're only needed for OpenCL. Consider adopting markdown in forums.

X
76
02-15-2019, 03:49 PM
#14
I moved to Firefox now... The site runs smoothly except occasionally the OS does. I checked `journalctl --catalog --boot` but can't pinpoint the issue. I spotted some red warnings: kernel sp5100-tco disabled, kvm turned off by BIOS, SD 10:0:0:0 not found, and a strange pulseaudio error. The ALSA driver seems faulty, possibly a bug. Consider reporting it to the developers.
X
xXMLGSwag360Xx
02-15-2019, 03:49 PM #14

I moved to Firefox now... The site runs smoothly except occasionally the OS does. I checked `journalctl --catalog --boot` but can't pinpoint the issue. I spotted some red warnings: kernel sp5100-tco disabled, kvm turned off by BIOS, SD 10:0:0:0 not found, and a strange pulseaudio error. The ALSA driver seems faulty, possibly a bug. Consider reporting it to the developers.

R
Raqet
Member
222
02-15-2019, 10:39 PM
#15
The command displays the version information related to AMD GPU and GLX details from the kernel logs.
R
Raqet
02-15-2019, 10:39 PM #15

The command displays the version information related to AMD GPU and GLX details from the kernel logs.

X
Xarlahk
Junior Member
19
02-15-2019, 10:54 PM
#16
dmesg | grep error displays no output
dmesg | grep amdgpu shows server GLX version string: 1.4
dmesg | grep amdgpu reveals client GLX version string: 1.4
dmesg | grep GLX lists version: 1.4
dmesg | grep GLES shows profile versions: 1.4, 1.1, 3.2
OpenGL core profile version: 4.6
Compatibility profile version: 4.6
GLES1 profile version: 1.1
GLES version: 3.2
OpenGL core profile: Mesa 20.2.1
OpenGL ES version: 4.60 (Mesa 20.2.1)
X
Xarlahk
02-15-2019, 10:54 PM #16

dmesg | grep error displays no output
dmesg | grep amdgpu shows server GLX version string: 1.4
dmesg | grep amdgpu reveals client GLX version string: 1.4
dmesg | grep GLX lists version: 1.4
dmesg | grep GLES shows profile versions: 1.4, 1.1, 3.2
OpenGL core profile version: 4.6
Compatibility profile version: 4.6
GLES1 profile version: 1.1
GLES version: 3.2
OpenGL core profile: Mesa 20.2.1
OpenGL ES version: 4.60 (Mesa 20.2.1)

B
BritishPing
Member
105
02-20-2019, 02:26 AM
#17
Reattempt this now. It shouldn't trigger glxinfo. Everything else appears okay though. I'm also curious if you have a card that experiences similar problems like my MSI 5700XT. I own a MSI card that handles memory very closely. On Windows it runs smoothly, but on Linux it causes random freezes and restarts. Perhaps the Windows driver accounts for this since AMDGPU doesn't, no idea. For my card, changing the memory clock from 875 to 850 might help. Consider setting "amdgpu.ppfeaturemask=0xffffffff" in the kernel command line—either at grub during boot or in /boot/grub/grub.cfg permanently. You can add it alongside "quite splash." After that, try installing corectrl and see if crashes persist.
B
BritishPing
02-20-2019, 02:26 AM #17

Reattempt this now. It shouldn't trigger glxinfo. Everything else appears okay though. I'm also curious if you have a card that experiences similar problems like my MSI 5700XT. I own a MSI card that handles memory very closely. On Windows it runs smoothly, but on Linux it causes random freezes and restarts. Perhaps the Windows driver accounts for this since AMDGPU doesn't, no idea. For my card, changing the memory clock from 875 to 850 might help. Consider setting "amdgpu.ppfeaturemask=0xffffffff" in the kernel command line—either at grub during boot or in /boot/grub/grub.cfg permanently. You can add it alongside "quite splash." After that, try installing corectrl and see if crashes persist.

M
MaddiBlake
Member
241
02-21-2019, 12:29 AM
#18
The BIOS/UEFI disabling KVM likely indicates the virtualization extensions are turned off. The sdd and lightdm alerts aren't concerning either. The color-safe notification doesn't matter here either. The watchdog alert appears unrelated to the problem. PulseAudio activity seems normal, as the bug reports don't match the situation. After your crash and restart, you ran `journalctl --catalog --boot=-1`? Typically, GPU issues leave a crash dump in journalctl, especially with Intel GPUs. I haven't experienced GPU crashes on my previous AMD machine, so I can't confirm. Edited November 17, 2020 by elsandosgrande “[…] reports I could find […]” → “[…] reports that I could find […]”.
M
MaddiBlake
02-21-2019, 12:29 AM #18

The BIOS/UEFI disabling KVM likely indicates the virtualization extensions are turned off. The sdd and lightdm alerts aren't concerning either. The color-safe notification doesn't matter here either. The watchdog alert appears unrelated to the problem. PulseAudio activity seems normal, as the bug reports don't match the situation. After your crash and restart, you ran `journalctl --catalog --boot=-1`? Typically, GPU issues leave a crash dump in journalctl, especially with Intel GPUs. I haven't experienced GPU crashes on my previous AMD machine, so I can't confirm. Edited November 17, 2020 by elsandosgrande “[…] reports I could find […]” → “[…] reports that I could find […]”.

H
hadesboy12
Junior Member
2
02-21-2019, 01:57 AM
#19
The system detected changes in kernel settings and topology. It enabled GPU mode and adjusted device configurations. VRAM usage was reported at 8176M, with GART and TMZ features noted as disabled. Memory initialization succeeded, and audio components bound properly. A memory clock adjustment of 850 MHz was attempted following the crash.
H
hadesboy12
02-21-2019, 01:57 AM #19

The system detected changes in kernel settings and topology. It enabled GPU mode and adjusted device configurations. VRAM usage was reported at 8176M, with GART and TMZ features noted as disabled. Memory initialization succeeded, and audio components bound properly. A memory clock adjustment of 850 MHz was attempted following the crash.

K
kcaz56
Senior Member
664
03-01-2019, 06:55 PM
#20
Not always. It applies only when helpful data is created before the system crashes or gets stuck, unless you have a tool like kdump ready—something I believe works only on Fedora, though I’m not sure about that.
K
kcaz56
03-01-2019, 06:55 PM #20

Not always. It applies only when helpful data is created before the system crashes or gets stuck, unless you have a tool like kdump ready—something I believe works only on Fedora, though I’m not sure about that.

Pages (3): Previous 1 2 3 Next