Re: AMD SUMO vs Xorg 7.7
В Mon, 5 Dec 2016 16:39:31 +0900 Michel Dänzer <mic...@daenzer.net> пишет: > On 03/12/16 12:24 AM, Alexander Konotop wrote: > > Here it is. > > I think it might be xserver-xorg-video-radeon:amd64 (at line 360). > > In the November 25-27 window you mentioned, xserver-xorg-video-radeon > was upgraded from 1:7.8.0-1 to 1:7.8.0-1+b1. That's a binary-only NMU, > i.e. the same package version was just recompiled against the newer > version of xserver-xorg-core, which was upgraded from 2:1.18.4-2 to > 2:1.19.0-2. The problem is more likely due to the latter than the former. > > Can you try confirming this using http://snapshot.debian.org/ ? > > Yes, it looks like +b1 is the only upgrade since mid november. I run dist-upgrade quite often, so the same version but without +b1 most likely was installed before. The same should be actual for xserver-xorg-core, 2:1.19.0-2 is currently installed. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org https://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: AMD SUMO vs Xorg 7.7
I've attached the log. I tried looking at the Xorg.0.log using "tail -f" while starting a browser and waiting for it to freeze. Nothing happened, no new messages in Xorg.0.log. As well as in syslog and dmesg. В Fri, 2 Dec 2016 10:35:15 +0900 Michel Dänzer <mic...@daenzer.net> пишет: > On 02/12/16 05:18 AM, Alexander Konotop wrote: > > Hello! It looks like I've found a radeon driver bug. > > > > Distro: > > Debian Sid(Unstable). > > > > Hardware: > > * SUMO (integrated in AMD A4 APU) > > * CAICOS (external) > > > > Problem: > > All webkit browsers freeze in few moments after startup while > > loading/opening or closing tabs. > > It happens only whith an integrated card (SUMO). > > Either propagating --disable-gpu to a browser or running on CAICOS using > > DRI_PRIME=1 eliminates > > freezing. > > Also running sauerbraten on SUMO causes freezing in few seconds after game > > starts, in menu. > > Switching to a terminal and back (ctrl+alt+f1 and then ctrl+alt+f7) > > unfreezes the game for few > > seconds and then it freezes again. > > Please provide the corresponding Xorg log file. > > [ 9.429] X.Org X Server 1.19.0 Release Date: 2016-11-15 [ 9.429] X Protocol Version 11, Revision 0 [ 9.429] Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian [ 9.429] Current Operating System: Linux jager 4.8.11-towo.3-siduction-amd64 #1 SMP PREEMPT siduction 4.8-20 (2016-11-28) x86_64 [ 9.429] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.8.11-towo.3-siduction-amd64 root=UUID=5b027533-c09b-4df9-873c-a2fa2bb2b1d1 ro quiet resume=UUID=edc157fa-fd31-4e8a-98c8-80c795887235 [ 9.429] Build Date: 23 November 2016 07:20:23PM [ 9.429] xorg-server 2:1.19.0-2 (https://www.debian.org/support) [ 9.429] Current version of pixman: 0.34.0 [ 9.429] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 9.429] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 9.429] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Dec 2 08:43:27 2016 [ 9.432] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 9.435] (==) No Layout section. Using the first Screen section. [ 9.435] (==) No screen section available. Using defaults. [ 9.435] (**) |-->Screen "Default Screen Section" (0) [ 9.435] (**) | |-->Monitor "" [ 9.438] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 9.438] (==) Automatically adding devices [ 9.438] (==) Automatically enabling devices [ 9.438] (==) Automatically adding GPU devices [ 9.438] (==) Max clients allowed: 256, resource mask: 0x1f [ 9.446] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 9.446] Entry deleted from font path. [ 9.450] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [ 9.450] (==) ModulePath set to "/usr/lib/xorg/modules" [ 9.450] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 9.450] (II) Loader magic: 0x56036f77fe00 [ 9.450] (II) Module ABI versions: [ 9.450] X.Org ANSI C Emulation: 0.4 [ 9.450] X.Org Video Driver: 23.0 [ 9.450] X.Org XInput driver : 24.1 [ 9.450] X.Org Server Extension : 10.0 [ 9.451] (++) using VT number 7 [ 9.451] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration [ 9.452] (II) xfree86: Adding drm device (/dev/dri/card0) [ 9.472] (II) xfree86: Adding drm device (/dev/dri/card1) [ 9.477] (--) PCI:*(0:0:1:0) 1002:9648:103c:168c rev 0, Mem @ 0xb000/268435456, 0xd810/262144, I/O @ 0x7000/256, BIOS @ 0x/131072 [ 9.477] (--) PCI: (0:1:0:0) 1002:6760:103c:168c rev 0, Mem @ 0xc000/268435456, 0xd800/131072, I/O @ 0x6000/256, BIOS @ 0x/131072 [ 9.477] (II) LoadModule: "glx" [ 9.483] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [ 9.514] (II) Module glx: vendor="X.Org Foundation" [ 9.514] compiled for 1.19.0, module version = 1.0.0 [ 9.514] ABI class: X.Org Server Extension, version 10.0 [ 9.514] (==) Matched ati as autoconfigured driver 0 [ 9.514] (==) Matched ati as autoconfigured driver 1 [ 9.514] (==) Matched ati as autoconfigured driver 2 [ 9.514] (==) Matched
AMD SUMO vs Xorg 7.7
Hello! It looks like I've found a radeon driver bug. Distro: Debian Sid(Unstable). Hardware: * SUMO (integrated in AMD A4 APU) * CAICOS (external) Problem: All webkit browsers freeze in few moments after startup while loading/opening or closing tabs. It happens only whith an integrated card (SUMO). Either propagating --disable-gpu to a browser or running on CAICOS using DRI_PRIME=1 eliminates freezing. Also running sauerbraten on SUMO causes freezing in few seconds after game starts, in menu. Switching to a terminal and back (ctrl+alt+f1 and then ctrl+alt+f7) unfreezes the game for few seconds and then it freezes again. No problems for sauerbraten with DRI_PRIME=1 on CAICOS. Here's a forum topic which I started before I determined that the browsers problem is caused by videocard: https://forum.siduction.org/index.php?topic=6469 But there's not much useful debug info actually. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org https://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: Muxless Dual AMD + Xorg 1.14 = blank screen
Thank You very much! I've enabled compositing and now I'm able to run a game in a window mode. It gives almost twice better fps in sauerbraten and xonotic. Fullscreen gives blank screen. Maybe xfce's window manager detects start of fullscreen applications and disables compositing or smth else happens. It's interesting that glxgears now shows ~1100 fps with internal card and compositing enabled, but shows ~970 fps with external card (DRI_PRIME=1). В Thu, 26 Sep 2013 16:56:14 -0400 Alex Deucher alexdeuc...@gmail.com пишет: On Thu, Sep 26, 2013 at 3:13 PM, Alexander Konotop alexander.kono...@gmail.com wrote: Hello, guys :-) Couldn't someone tell me if it's an issue or it really won't work as still unimplemented, or maybe I'm doing smth wrong: I have an AMD APU + External AMD card (Muxless). here's lspci --vv output for them: 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6480G] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device 168c Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 48 Region 0: Memory at b000 (32-bit, prefetchable) [size=256M] Region 1: I/O ports at 7000 [size=256] Region 2: Memory at d810 (32-bit, non-prefetchable) [size=256K] Expansion ROM at unassigned [disabled] Capabilities: access denied Kernel driver in use: radeon 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M Series] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Radeon HD 6470M Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 50 Region 0: Memory at c000 (64-bit, prefetchable) [size=256M] Region 2: Memory at d800 (64-bit, non-prefetchable) [size=128K] Region 4: I/O ports at 6000 [size=256] Expansion ROM at d802 [disabled] [size=128K] Capabilities: access denied Kernel driver in use: radeon I've at first read this page: http://xorg.freedesktop.org/wiki/RadeonFeature/ especially the phrase X Server 1.14 is required to support rendering and display from different cards and MOSTLY at the Hybrid Graphics/PowerXpress/Enduro row for my cards. and subscribed to this mail list to see any news on Dual Graphics support or bugs. At second I'we waited for xorg 1.14 to appear in my distro. At third I've tried to setup my two cards using this post: http://forums.linuxmint.com/viewtopic.php?f=49t=139413 So I'm using xrandr to switch the PRIME card and it looks like workng at first: $ glxinfo | egrep (OpenGL vendor|OpenGL renderer|OpenGL version) OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD SUMO OpenGL version string: 3.0 Mesa 9.1.6 $ DRI_PRIME=1 glxinfo | egrep (OpenGL vendor|OpenGL renderer|OpenGL version) OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD CAICOS OpenGL version string: 3.0 Mesa 9.1.6 But if I try to run a fullscreen game specifying DRI_PRIME=1 - it shows blank screen. I can write /quit in the game's console (being blind) and it really quits - so it's not a hang. Sometimes xserver restarts while trying to run a game this way. Syslog and Xorg.0.log are empty. After that I tried to run non-fullscreen (I've run glxgears). glxgears shows twice more fps but it's window is just black. So it seems like xrandr asks the xserver to render on a second GPU but it doesn't ask it to use the first GPU to output video. So maybe I need to configure xorg.conf somehow? I've read somewhere that there's no need to do it if I use xrandr to switch and no need to restart Xserver for muxless systems. On a muxless system, there are often no displays connected to one of the GPUs so it can only be used for rendering. You can't force X to start on that GPU because there are no displays. You don't need an xorg config. Btw if I restart xserver my xrandr settings will fall back to using APU's GPU as primary. To start an Xserver I'm using lightdm. You need to be using a compositing window manager to start with. See this page for more info: http://nouveau.freedesktop.org/wiki/Optimus/ You can probably resize the window to make the display appear. I think there may be some damage tracking issues that need to be sorted out in the xserver, but no one has had a chance to look into them yet. Alex ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg
