LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 09-28-2022, 04:11 PM   #1
gauchao
Member
 
Registered: Dec 2009
Location: Veneto
Distribution: Slackware64
Posts: 364

Rep: Reputation: 138Reputation: 138
Firefox 105.0.1 error messages after Sep 28th upgrade - Slack64-Current


After today's upgrades (Slackware64-current), Firefox 105.0.1 refused to start. I killed the process that remained running in background, lauched FF again from a console and it started but with error messages (FF is running now, but with these errors in the console). I have an AMD GPU card running stock drivers (see inxi -G output below). Things were running nicely yesterday. Kernel 5.19.12, display server X.org.

Any ideas?

Console errors:

Quote:
bash-5.2$ firefox
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: VA-API test failed: no supported VAAPI profile found. (t=0.537699) [GFX1-]: glxtest: VA-API test failed: no supported VAAPI profile found.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
ATTENTION: default value of option mesa_glthread overridden by environment.
Missing chrome or resource URL: resource://gre/modules/UpdateListener.sys.mjs
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Couldn't sanitize RENDERER device: TAHITI (t=136.039) [GFX1-]: Couldn't sanitize RENDERER device: TAHITI
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Couldn't sanitize RENDERER device: TAHITI (t=136.039) |[C1][GFX1-]: Couldn't sanitize RENDERER device: TAHITI (t=138.517) [GFX1-]: Couldn't sanitize RENDERER device: TAHITI
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Couldn't sanitize RENDERER device: TAHITI (t=136.039) |[C1][GFX1-]: Couldn't sanitize RENDERER device: TAHITI (t=138.517) |[C2][GFX1-]: Couldn't sanitize RENDERER device: TAHITI (t=144.868) [GFX1-]: Couldn't sanitize RENDERER device: TAHITI
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Couldn't sanitize RENDERER device: TAHITI (t=136.039) |[C1][GFX1-]: Couldn't sanitize RENDERER device: TAHITI (t=138.517) |[C2][GFX1-]: Couldn't sanitize RENDERER device: TAHITI (t=144.868) |[C3][GFX1-]: Couldn't sanitize RENDERER device: TAHITI (t=174.15) [GFX1-]: Couldn't sanitize RENDERER device: TAHITI
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Couldn't sanitize RENDERER device: TAHITI (t=136.039) |[C1][GFX1-]: Couldn't sanitize RENDERER device: TAHITI (t=138.517) |[C2][GFX1-]: Couldn't sanitize RENDERER device: TAHITI (t=144.868) |[C3][GFX1-]: Couldn't sanitize RENDERER device: TAHITI (t=174.15) |[C4][GFX1-]: Couldn't sanitize RENDERER device: TAHITI (t=226.068) [GFX1-]: Couldn't sanitize RENDERER device: TAHITI
My inxi -G:

Quote:
bash-5.2$ inxi -G
Graphics:
Device-1: AMD Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X] driver: radeon
v: kernel
Display: server: X.Org v: 21.1.4 with: Xwayland v: 22.1.3 driver: X:
loaded: radeon unloaded: modesetting,vesa gpu: radeon
resolution: 1920x1080~60Hz
OpenGL: renderer: TAHITI ( LLVM 14.0.6 DRM 2.50 5.19.12) v: 4.5 Mesa
22.2.0
Thank you.
 
Old 09-28-2022, 05:02 PM   #2
fourtysixandtwo
Member
 
Registered: Jun 2021
Location: Alberta
Distribution: Slackware...mostly
Posts: 301

Rep: Reputation: 200Reputation: 200Reputation: 200
I'm not running current, but you might want to try switching to the amdgpu driver. I have a Tahiti card as well and if my memory serves me, I used to see those errors with firefox before I switched drivers. The amdgpu driver has better support for hw acceleration.

There's a couple other ways to enable it, but this the method I used.
Code:
# cat /etc/modprobe.d/amdgpu.conf
options amdgpu si_support=1
options amdgpu cik_support=1

# cat /etc/modprobe.d/radeon.conf
options radeon si_support=0
options radeon cik_support=0

#also added the following and rebuilt initrd.gz
echo "MODCONF=\"1\"" >> /etc/mkinitrd.conf
 
2 members found this post helpful.
Old 09-29-2022, 04:58 AM   #3
giomat
Member
 
Registered: Jul 2017
Posts: 335

Rep: Reputation: 237Reputation: 237Reputation: 237
Regarding the first VAAPI error, you probably got bitten by the last mesa update. Starting from 22.2, mesa does not build by default video decode codecs for h264/h265, thus leaving amd gpus without VAAPI support.
 
4 members found this post helpful.
Old 09-29-2022, 06:15 AM   #4
marav
LQ Sage
 
Registered: Sep 2018
Location: Gironde
Distribution: Slackware
Posts: 5,234

Rep: Reputation: 3948Reputation: 3948Reputation: 3948Reputation: 3948Reputation: 3948Reputation: 3948Reputation: 3948Reputation: 3948Reputation: 3948Reputation: 3948Reputation: 3948
Quote:
Originally Posted by giomat View Post
Regarding the first VAAPI error, you probably got bitten by the last mesa update. Starting from 22.2, mesa does not build by default video decode codecs for h264/h265, thus leaving amd gpus without VAAPI support.
Yep
Code:
Support for building Mesa with select video codecs disabled out of software patent concerns.
https://www.phoronix.com/news/Mesa-22.2-Released

Maybe we should add:
Code:
+ -Dvideo-codecs=vc1dec,h264dec,h264enc,h265dec,h265enc \
 
2 members found this post helpful.
Old 09-29-2022, 06:20 AM   #5
elcore
Senior Member
 
Registered: Sep 2014
Distribution: Slackware
Posts: 1,751

Rep: Reputation: Disabled
Quote:
Originally Posted by marav View Post
Maybe we should add:
Code:
+ -Dvideo-codecs=vc1dec,h264dec,h264enc,h265dec,h265enc \
You mean remove? It's not adding anything TBH
And maybe if it goes down that route, then vdpau also should be moved to SBo or something?

Last edited by elcore; 09-29-2022 at 06:23 AM.
 
Old 09-29-2022, 06:32 AM   #6
marav
LQ Sage
 
Registered: Sep 2018
Location: Gironde
Distribution: Slackware
Posts: 5,234

Rep: Reputation: 3948Reputation: 3948Reputation: 3948Reputation: 3948Reputation: 3948Reputation: 3948Reputation: 3948Reputation: 3948Reputation: 3948Reputation: 3948Reputation: 3948
Quote:
Originally Posted by elcore View Post
You mean remove? It's not adding anything TBH
And maybe if it goes down that route, then vdpau also should be moved to SBo or something?
Nope
Others also do it like that (at least Arch & Gentoo)
Code:
option(
  'video-codecs',
  type : 'array',
  value : [],
  choices: [
    'vc1dec', 'h264dec', 'h264enc', 'h265dec', 'h265enc'
  ],
  description : 'List of patent encumbered codecs to build support for. Distros might want to consult their legal
department before enabling these. This is used for all video APIs (vaapi, vdpau, vulkan). Non-patent encumbered 
codecs will be enabled by default.'
but maybe there will be a veto from Pat's legal department ;-)

Last edited by marav; 09-29-2022 at 06:34 AM.
 
Old 09-29-2022, 06:41 AM   #7
elcore
Senior Member
 
Registered: Sep 2014
Distribution: Slackware
Posts: 1,751

Rep: Reputation: Disabled
Quote:
Originally Posted by marav View Post
Nope
Nope? Can't you be more specific? You mean nope; you're not removing by compiling without, or nope; the vdpau should stay in broken state?
That part of mesa should really go to SBo, but with SBo policy of not replacing distro packages, how?
 
Old 09-29-2022, 06:44 AM   #8
marav
LQ Sage
 
Registered: Sep 2018
Location: Gironde
Distribution: Slackware
Posts: 5,234

Rep: Reputation: 3948Reputation: 3948Reputation: 3948Reputation: 3948Reputation: 3948Reputation: 3948Reputation: 3948Reputation: 3948Reputation: 3948Reputation: 3948Reputation: 3948
Quote:
Originally Posted by elcore View Post
Nope? Can't you be more specific? You mean nope; you're not removing by compiling without, or nope; the vdpau should stay in broken state?
That part of mesa should really go to SBo, but with SBo policy of not replacing distro packages, how?
I'm not removing
The -D means :
Code:
Universal options
All these can be set by passing -Doption=value to meson (aka meson setup)
https://mesonbuild.com/Builtin-options.html

and "+" a the beginning is because I made a diff between my slackbuild and the original one
Code:
--- mesa.SlackBuild.orig  2022-08-09 04:58:15.107303823 +0200
+++ mesa.SlackBuild     2022-09-29 12:33:04.235322375 +0200
@@ -143,6 +143,7 @@
   -Dgles2=enabled \
   -Dopengl=true \
   -Dglx=dri \
+  -Dvideo-codecs=vc1dec,h264dec,h264enc,h265dec,h265enc \
   .. || exit 1
   "${NINJA:=ninja}" $NUMJOBS || exit 1
   DESTDIR=$PKG $NINJA install || exit 1

Last edited by marav; 09-29-2022 at 06:48 AM.
 
1 members found this post helpful.
Old 09-29-2022, 06:58 AM   #9
elcore
Senior Member
 
Registered: Sep 2014
Distribution: Slackware
Posts: 1,751

Rep: Reputation: Disabled
Quote:
Originally Posted by marav View Post
I'm not removing
OK, I'm not removing it either, we may legally keep this enabled because we're in EU.
Still not clear if we're going to have to recompile all of mesa in the future, to get this.
 
Old 09-29-2022, 08:32 AM   #10
ctrlaltca
Member
 
Registered: May 2019
Location: Italy
Distribution: Slackware
Posts: 316

Rep: Reputation: 350Reputation: 350Reputation: 350Reputation: 350
From my understandings this mostly affects GPU-accellerated video decode/encode (VAAPI) on AMD hardware using mesa's va driver.
Intel already needed an external driver for this (https://github.com/intel/media-driver/), while nouveau is probably out of luck anyway on recent cards.

About 5 months ago a change was introduced in mesa to require an explicit list of enabled video codecs at configure time:
https://gitlab.freedesktop.org/mesa/...9bf33337bc2c96
The default list of enabled codecs is empty, but all of them are explicitly enabled in mesa's automatic CI build script, and they are still enabled as of today.

One week ago fedora disabled all codecs in its CI build script, thus the drama:
https://src.fedoraproject.org/rpms/m...branch=rawhide
Looks like Fedora now split the vaapi drivers into a separate package, hoping for them being provided by a separate entity (possibly rpmfusion):
https://src.fedoraproject.org/rpms/m...branch=rawhide

Arch still enables all the video codecs: arch: https://github.com/archlinux/svntogi...5ef0e6d7c57f8a
Gentoo defines a compile time flag "proprietary-codecs": https://gitweb.gentoo.org/repo/gento....0.ebuild#n448
Debian defines a compile time filter "pkg.mesa.nolibva": https://salsa.debian.org/xorg-team/l...e/debian/rules
Ubuntu does the same as Debian: https://git.launchpad.net/ubuntu/+so...u/kinetic#n135
OpenSUSE doesn't explicitly enable any of the video codes (looks like they "forgot" to add the option when updating to mesa 22.2): https://build.opensuse.org/package/v....spec?expand=1
 
4 members found this post helpful.
Old 09-29-2022, 01:29 PM   #11
giomat
Member
 
Registered: Jul 2017
Posts: 335

Rep: Reputation: 237Reputation: 237Reputation: 237
Quote:
Originally Posted by ctrlaltca View Post
Arch still enables all the video codecs: arch: https://github.com/archlinux/svntogi...5ef0e6d7c57f8a
Gentoo defines a compile time flag "proprietary-codecs": https://gitweb.gentoo.org/repo/gento....0.ebuild#n448
Debian defines a compile time filter "pkg.mesa.nolibva": https://salsa.debian.org/xorg-team/l...e/debian/rules
Ubuntu does the same as Debian: https://git.launchpad.net/ubuntu/+so...u/kinetic#n135
OpenSUSE doesn't explicitly enable any of the video codes (looks like they "forgot" to add the option when updating to mesa 22.2): https://build.opensuse.org/package/v....spec?expand=1
And if i understand correcly, slackware won't enable them because it's US based, while debian/arch/gentoo can get away because they are community managed right?
Guess we will have to compile our own mesa package, luckily it's very easy on slack but still an annoyance.
 
Old 09-29-2022, 04:45 PM   #12
jayjwa
Member
 
Registered: Jul 2003
Location: NY
Distribution: Slackware, Termux
Posts: 747

Rep: Reputation: 235Reputation: 235Reputation: 235
Yesterday everything was working, I updated to current just now and Firefox is broken (also Librewolf). There's no error messages, it just hangs. I'm posting this from SeaMonkey.

09:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R5 430 OEM / R7 240/340 / Radeon 520 OEM]

is my card, using "radeon" kmod. Alot of people are going to have non-working browsers. "Just build Mesa yourself" is our current fix?
 
1 members found this post helpful.
Old 09-29-2022, 05:29 PM   #13
jayjwa
Member
 
Registered: Jul 2003
Location: NY
Distribution: Slackware, Termux
Posts: 747

Rep: Reputation: 235Reputation: 235Reputation: 235
Good news: rebuilding Mesa with the patch fixes things. Bad news: Firefox wanted to "refresh" for some reason, which I foolishly allowed, losing all my bookmarks and configuration.
 
2 members found this post helpful.
Old 09-29-2022, 06:00 PM   #14
gauchao
Member
 
Registered: Dec 2009
Location: Veneto
Distribution: Slackware64
Posts: 364

Original Poster
Rep: Reputation: 138Reputation: 138
Thank you for the help.

I turned off Firefox hardware acceleration but still kept radeon driver (I will try to change the radeon driver to amdgpu driver later, as suggested by fourtysixandtwo). This way, the RENDERER DEVICE error went off, but the VA-API / mesa error kept showing up.
 
1 members found this post helpful.
Old 09-30-2022, 09:14 AM   #15
keefaz
LQ Guru
 
Registered: Mar 2004
Distribution: Slackware
Posts: 6,552

Rep: Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872Reputation: 872
Quote:
Originally Posted by jayjwa View Post
Good news: rebuilding Mesa with the patch fixes things. Bad news: Firefox wanted to "refresh" for some reason, which I foolishly allowed, losing all my bookmarks and configuration.
No old profiles in ~/.mozilla/firefox to copy Places.sqlite into the new profile?
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Libreoffice not working after May 11st 2020 Slack64-current upgrade gauchao Slackware 19 05-19-2020 08:17 AM
[SOLVED] sep-26 current upgrade (boost) broke alien's libreoffice fsauer Slackware 7 09-28-2017 10:49 AM
[SOLVED] no sound output after update to current (Sep 12) qunying Slackware 5 09-15-2017 08:00 AM
awk command line: blank line record sep, new line field sep robertmarkbram Programming 4 02-21-2010 05:25 AM
slack-current (25 sep 06) kernel bug? slak05 Slackware 8 09-27-2006 02:10 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 03:29 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration