You are not logged in.
I updated mesa from 17.2.6-1 to 17.3.0-2 and the firefox upon starting was unresponsive. so i tried starting it on terminal and no errors were returned and the firefox did not start either. Tried firefox -safe-mode with the same results.. so i rolled back mesa to the previous version and bang firefox is working again.. reason anybody???
Last edited by frk (2017-12-18 09:33:10)
Offline
Everything is running perfectly here (mesa 17.3.0-2 && firefox-57.0.2-1).
Try to check mesa changelog: if there's anything new that may affect the behavior of your graphic card, probably that's the reason.
Offline
I updated mesa from 17.2.6-1 to 17.3.0-2
Does that mean you performed a partial update?
Offline
I updated mesa from 17.2.6-1 to 17.3.0-2
Does that mean you performed a partial update?
no.. pacman -Syu...
Everything is running perfectly here (mesa 17.3.0-2 && firefox-57.0.2-1).
Try to check mesa changelog: if there's anything new that may affect the behavior of your graphic card, probably that's the reason.
can't find any in the change log..
VGA controller info
[name@sys ~]$ lspci -v| grep VGA
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R6/R7 Graphics] (prog-if 00 [VGA controller])
[name@sys ~]$ sudo lspci -v -s 00:01.0
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Kaveri [Radeon R6/R7 Graphics] (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company Kaveri [Radeon R6/R7 Graphics]
Flags: bus master, fast devsel, latency 0, IRQ 47
Memory at c0000000 (64-bit, prefetchable) [size=256M]
Memory at d0000000 (64-bit, prefetchable) [size=8M]
I/O ports at 5000 [size=256]
Memory at d6800000 (32-bit, non-prefetchable) [size=256K]
Expansion ROM at 000c0000 [disabled] [size=128K]
Capabilities: [48] Vendor Specific Information: Len=08 <?>
Capabilities: [50] Power Management version 3
Capabilities: [58] Express Root Complex Integrated Endpoint, MSI 00
Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?>
Capabilities: [270] #19
Capabilities: [2b0] Address Translation Service (ATS)
Capabilities: [2c0] Page Request Interface (PRI)
Capabilities: [2d0] Process Address Space ID (PASID)
Kernel driver in use: radeon
Kernel modules: radeon, amdgpu
happy with the downgraded mesa but just wanted figure out what the problem is..
Thanks..
Last edited by frk (2017-12-17 19:07:59)
Offline
Thanks for this! I was having problems since the update too and couldn't figure out what broke it.
a) Firefox would fail to start. It was creating two processes with the same command line and I had to kill the 2nd one manually before the window appeared.
b) Chromium would just open an empty window (no content - just black) and hang.
Downgrading to 17.2.6-1 fixed both issues.
Offline
What if you use the amdgpu driver?
does glxinfo work (resp. are you on wayland)?
Offline
What if you use the amdgpu driver?
does glxinfo work (resp. are you on wayland)?
using X.. no output glxinfo..
edit: installed mesa-demos... output to glxinfo(mesa 17.2.6-1).. https://pastebin.com/dD9WWWyr ... glxinfo unresponsive(mesa 17.3.0-2)
Thanks for this! I was having problems since the update too and couldn't figure out what broke it.
a) Firefox would fail to start. It was creating two processes with the same command line and I had to kill the 2nd one manually before the window appeared.
b) Chromium would just open an empty window (no content - just black) and hang.
Downgrading to 17.2.6-1 fixed both issues.
same here..
process upon starting firefox with mesa 17.3.0-2
[name@sys ~]$ ps aux | grep firefox
name 1281 1.9 1.3 1594804 93232 tty2 Sl+ 07:39 0:00 /usr/lib/firefox/firefox --new-window
name 1284 0.4 0.6 487772 45404 tty2 Sl+ 07:39 0:00 /usr/lib/firefox/firefox --new-window
name 1346 0.0 0.0 10888 2308 pts/0 S+ 07:40 0:00 grep firefox[name@sys ~]$ kill 1284
[name@sys ~]$ ps aux | grep firefox
name 1281 6.7 2.9 1998880 211684 tty2 Dl+ 07:39 0:04 /usr/lib/firefox/firefox --new-window
name 1378 68.0 1.4 1917980 103036 tty2 Sl+ 07:40 0:00 /usr/lib/firefox/firefox -contentproc -childID 1 -isForBrowser -intPrefs (...... ......)-greomni /usr/lib/firefox/omni.ja -appomni /usr/lib/firefox/browser/omni.ja -appdir /usr/lib/firefox/browser 1281 true tab
name 1429 0.0 0.0 10888 2308 pts/0 R+ 07:40 0:00 grep firefox
killing one of the processes opened the window.....
edit: killing the 2nd process opens the window.. killing the 1st does nothing..
Last edited by frk (2017-12-18 09:24:14)
Offline
glxinfo unresponsive(mesa 17.3.0-2)
So it's less of a firefox and more of a GLX issue.
Run "dmesg -w" in one terminal and "glxinfo" in another. Any dmesg output for this?
Also check your Xorg log. If you're using the modesetting driver, glamor might clash with glx.
Does the desktop environment matter (ie. can you run glxinfo on a naked X server with only an xterm running - and i mean "xterm", not konsole or termite or whatever)?
Offline
blacklisting Radeon and adding amdgpu to modules worked.. did not see that the it was using radeon even after installing amdgpu.. thanks the assist..
...
Offline