Re: KMS
On Tue, Aug 25, 2009 at 9:31 AM, James Cloos wrote: >> can you post the output of dmesg after loading the radeon drm? > > There is no printk() output when X starts. I used to get: > > Aug 19 05:21:55 [kernel] agpgart-intel :00:00.0: AGP 2.0 bridge > Aug 19 05:21:55 [kernel] agpgart-intel :00:00.0: putting AGP V2 device > into 4x mode > Aug 19 05:21:55 [kernel] radeonfb :01:00.0: putting AGP V2 device into 4x > mode > Aug 19 05:21:55 [kernel] [drm] Setting GART location based on new memory map > Aug 19 05:21:55 [kernel] [drm] Loading R100 Microcode > Aug 19 05:21:55 [kernel] [drm] writeback test succeeded in 1 usecs > > but now get nothing since I turned on CONFIG_DRM_RADEON_KMS and > recompiled ati with enable-kms (and recompiled everything else, too). > sounds like you are missing fbcon support maybe. CONFIG_FRAMEBUFFER_CONSOLE. Dave. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: KMS
On Mon, Aug 24, 2009 at 7:31 PM, James Cloos wrote: >> can you post the output of dmesg after loading the radeon drm? > > There is no printk() output when X starts. I used to get: > > Aug 19 05:21:55 [kernel] agpgart-intel :00:00.0: AGP 2.0 bridge > Aug 19 05:21:55 [kernel] agpgart-intel :00:00.0: putting AGP V2 device > into 4x mode > Aug 19 05:21:55 [kernel] radeonfb :01:00.0: putting AGP V2 device into 4x > mode > Aug 19 05:21:55 [kernel] [drm] Setting GART location based on new memory map > Aug 19 05:21:55 [kernel] [drm] Loading R100 Microcode > Aug 19 05:21:55 [kernel] [drm] writeback test succeeded in 1 usecs Remove radeonfb; it's taking the device. The radeon kms drm provides an fb device. Alex ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: KMS
> can you post the output of dmesg after loading the radeon drm? There is no printk() output when X starts. I used to get: Aug 19 05:21:55 [kernel] agpgart-intel :00:00.0: AGP 2.0 bridge Aug 19 05:21:55 [kernel] agpgart-intel :00:00.0: putting AGP V2 device into 4x mode Aug 19 05:21:55 [kernel] radeonfb :01:00.0: putting AGP V2 device into 4x mode Aug 19 05:21:55 [kernel] [drm] Setting GART location based on new memory map Aug 19 05:21:55 [kernel] [drm] Loading R100 Microcode Aug 19 05:21:55 [kernel] [drm] writeback test succeeded in 1 usecs but now get nothing since I turned on CONFIG_DRM_RADEON_KMS and recompiled ati with enable-kms (and recompiled everything else, too). -JimC ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: KMS
On Mon, Aug 24, 2009 at 6:54 PM, James Cloos wrote: > :; zgrep KMS /proc/config.gz > CONFIG_DRM_RADEON_KMS=y > > The Xorg.0.log (from the still-running instance) and xorg.conf are: can you post the output of dmesg after loading the radeon drm? ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: KMS
:; zgrep KMS /proc/config.gz CONFIG_DRM_RADEON_KMS=y The Xorg.0.log (from the still-running instance) and xorg.conf are: This is a pre-release version of the X server from The X.Org Foundation. It is not supported in any way. Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/. Select the "xorg" product for bugs you find in this release. Before reporting bugs in pre-release versions please check the latest version in the X.Org Foundation git repository. See http://wiki.x.org/wiki/GitPage for git access instructions. X.Org X Server 1.6.99.1 Release Date: (unreleased) X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.31-rc7-lug1 i686 Current Operating System: Linux lugabout 2.6.31-rc7-lug1 #24 PREEMPT Sat Aug 22 21:49:03 EDT 2009 i686 Kernel command line: ro root=/dev/sda4 default_utf8=1 Build Date: 24 August 2009 10:06:40AM Current version of pixman: 0.15.21 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Mon Aug 24 09:24:30 2009 (==) Using config file: "/etc/X11/xorg.conf" (==) ServerLayout "Layout[all]" (**) |-->Screen "LCD" (0) (**) | |-->Monitor "ITUX" (**) | |-->Device "RadeonM7" (**) |-->Input Device "evKeyboard" (**) |-->Input Device "evRelMouse" (**) Option "DontZap" "false" (**) Option "AllowMouseOpenFail" (**) Option "Xinerama" "off" (**) Option "AIGLX" "true" (==) Not automatically adding devices (==) Not automatically enabling devices (**) FontPath set to: /usr/share/fonts/misc, /usr/share/fonts/100dpi, /usr/share/fonts/75dpi, /usr/share/fonts/cyrillic, /usr/share/fonts/efont-unicode, /usr/share/fonts/intlfonts, /usr/share/fonts/jmk, /usr/share/fonts/lfpfonts-fix, /usr/share/fonts/lfpfonts-var, /usr/share/fonts/monafont, /usr/share/fonts/mplus, /usr/share/fonts/sgi-fonts, /usr/share/fonts/shinonome, /usr/share/fonts/terminus, /usr/share/fonts/unifont, /usr/share/fonts/vc, /usr/share/fonts/misc/, /usr/share/fonts/TTF/, /usr/share/fonts/OTF, /usr/share/fonts/Type1/, /usr/share/fonts/100dpi/, /usr/share/fonts/75dpi/, built-ins (==) ModulePath set to "/usr/lib/xorg/modules" (**) Extension "Composite" is disabled (II) Loader magic: 0x8260460 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 6.0 X.Org XInput driver : 7.0 X.Org Server Extension : 2.0 (--) using VT number 7 (--) PCI:*(0:1:0:0) 1002:4c57:1028:00e6 ATI Technologies Inc Radeon Mobility M7 LW [Radeon Mobility 7500] rev 0, Mem @ 0xe000/134217728, 0xfcff/65536, I/O @ 0xcc00/256, BIOS @ 0x/131072 (II) Open ACPI successful (/var/run/acpid.socket) (II) "extmod" will be loaded. This was enabled by default and also specified in the config file. (II) "dbe" will be loaded. This was enabled by default and also specified in the config file. (II) "glx" will be loaded. This was enabled by default and also specified in the config file. (II) "record" will be loaded by default. (II) "dri" will be loaded by default. (II) "dri2" will be loaded by default. (II) LoadModule: "extmod" (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so (II) Module extmod: vendor="X.Org Foundation" compiled for 1.6.99.1, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension MIT-SCREEN-SAVER (II) Loading extension XFree86-VidModeExtension (II) Loading extension XFree86-DGA (II) Loading extension DPMS (II) Loading extension XVideo (II) Loading extension XVideo-MotionCompensation (II) Loading extension X-Resource (II) LoadModule: "ddc" (II) Module "ddc" already built-in (II) LoadModule: "dbe" (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so (II) Module dbe: vendor="X.Org Foundation" compiled for 1.6.99.1, module version = 1.0.0 Module class: X.Org Server Extension ABI class: X.Org Server Extension, version 2.0 (II) Loading extension DOUBLE-BUFFER (II) LoadModule: "glx" (II) Loading /usr/lib/xorg/modules/extensions/libglx.so (II) Module glx: vendor="X.Org Foundation" compiled for 1.6.99.1, module version = 1.0.0 ABI class: X.Org Server Extension, version 2.0 (**) AIGLX enabled (II) Loading extension GLX (II) LoadModule: "vbe" (II) Loading /usr/lib/xorg/modules/libvbe.so (II) Module vbe: vendor="X.Org Foundation" compiled for 1.6.99.1, module version = 1.1.0 ABI class: X.Org Video Driver, version 6.0 (II) LoadModule: "record" (II) Loading /usr/lib/xorg/modules/extensions/librecord.so (II) Module record: ve
Re: KMS
On Mon, Aug 24, 2009 at 6:21 PM, James Cloos wrote: > Alex Deucher > writes: > >> On Mon, Aug 24, 2009 at 5:42 PM, James >> Cloos wrote: >>> I'm at current master for everything: kernel, libsrm, mesa, xserver, >>> ati, x protos, x libs, etc. > >> What kernel are you using? You'll need 2.6.31 and for KMS you'll need >> to enable staging drivers and set the radeon kms config option to y. > > Linus' tree; as of last night that puts me two commits more recent than > the 31-rc7 tag. And KMS is indeed configured there: > > [ 2.771810] [drm] radeon default to kernel modesetting. > [ 2.771886] [drm] radeon kernel modesetting enabled. > > I forgot to mention: the laptop is archaic; it is an r100-class 7500 M7 LW. make sure: CONFIG_DRM_RADEON_KMS=y is set in your .config. Can you post your xorg log? Sounds like maybe you didn't configure the ddx with kms support. Alex ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: KMS
Alex Deucher writes: > On Mon, Aug 24, 2009 at 5:42 PM, James > Cloos wrote: >> I'm at current master for everything: kernel, libsrm, mesa, xserver, >> ati, x protos, x libs, etc. > What kernel are you using? You'll need 2.6.31 and for KMS you'll need > to enable staging drivers and set the radeon kms config option to y. Linus' tree; as of last night that puts me two commits more recent than the 31-rc7 tag. And KMS is indeed configured there: [2.771810] [drm] radeon default to kernel modesetting. [2.771886] [drm] radeon kernel modesetting enabled. I forgot to mention: the laptop is archaic; it is an r100-class 7500 M7 LW. -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: KMS
On Mon, Aug 24, 2009 at 5:42 PM, James Cloos wrote: > I'm at current master for everything: kernel, libsrm, mesa, xserver, > ati, x protos, x libs, etc. > > Kernel looks good. > > libdrm is configured with --enable-radeon-experimental-api. > xf86-video-ati is configured with --enable-dri --enable-kms. > > But I still get this in the Xorg.0.log: > > (II) [KMS] drm report modesetting isn't supported. > ... > drmOpenDevice: node name is /dev/dri/card0 > [drm] failed to load kernel module "radeon" > (EE) RADEON(0): [dri] RADEONDRIGetVersion failed to open the DRM > [dri] Disabling DRI. > ... > (II) AIGLX: Screen 0 is not DRI2 capable > (II) AIGLX: Screen 0 is not DRI capable > (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so > (II) GLX: Initialized DRISWRAST GL provider for screen 0 > > What am I missing? What kernel are you using? You'll need 2.6.31 and for KMS you'll need to enable staging drivers and set the radeon kms config option to y. Alex ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
KMS
I'm at current master for everything: kernel, libsrm, mesa, xserver, ati, x protos, x libs, etc. Kernel looks good. libdrm is configured with --enable-radeon-experimental-api. xf86-video-ati is configured with --enable-dri --enable-kms. But I still get this in the Xorg.0.log: (II) [KMS] drm report modesetting isn't supported. ... drmOpenDevice: node name is /dev/dri/card0 [drm] failed to load kernel module "radeon" (EE) RADEON(0): [dri] RADEONDRIGetVersion failed to open the DRM [dri] Disabling DRI. ... (II) AIGLX: Screen 0 is not DRI2 capable (II) AIGLX: Screen 0 is not DRI capable (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so (II) GLX: Initialized DRISWRAST GL provider for screen 0 What am I missing? -JimC -- James Cloos OpenPGP: 1024D/ED7DAEA6 ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 21374] [Mobility FireGL 9000] cs_gem_write_reloc: Assertion `bo->space_accounted` failed.
http://bugs.freedesktop.org/show_bug.cgi?id=21374 ajax at nwnk dot net changed: What|Removed |Added Version|CVS |git --- Comment #9 from ajax at nwnk dot net 2009-08-24 12:32:06 PST --- Mass version move, cvs -> git -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 16198] Random hard lockups on R500 and RS690 with 3D enabled
http://bugs.freedesktop.org/show_bug.cgi?id=16198 ajax at nwnk dot net changed: What|Removed |Added Version|CVS |git --- Comment #29 from ajax at nwnk dot net 2009-08-24 12:30:17 PST --- Mass version move, cvs -> git -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 23386] Artifacts with cairo dock 2.0 [openGL]
http://bugs.freedesktop.org/show_bug.cgi?id=23386 --- Comment #12 from mac_v 2009-08-24 10:27:41 PST --- (In reply to comment #11) > (In reply to comment #10) > > Even so, i tried cairo-dock but it *would not start* . > > I ran cairo-dock in debug mode and it had only one line: > > > > drmRadeonCmdBuffer: -22 > > Check the dmesg output. > I checked , but nothing gets logged in /var/log/dmesg for this problem. [and nothing else was logged in the dmesg while i was testing this with KMS] -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Re: unknown chip id 0x9610, can't guess
On Mon, Aug 24, 2009 at 10:38 AM, Levent Aksu wrote: > Hello there, > I have submitted this on the Bugzilla 2 weeks ago but no progress yet. I > would not like to sound like pushing but am I on the right track? > > Bugzilla page: > https://bugs.freedesktop.org/show_bug.cgi?id=23216 You need to file the component to something radeon related otherwise it's likely to get lost as it did in this case. 3D accel is still experimental on your chip. You need the xf86-video-ati driver from git master or the 6.12-branch. Then follow the instruction at the end of this page to install the 3D side: http://jbridgman.livejournal.com/945.html Alex ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
unknown chip id 0x9610, can't guess
Hello there, I have submitted this on the Bugzilla 2 weeks ago but no progress yet. I would not like to sound like pushing but am I on the right track? Bugzilla page: https://bugs.freedesktop.org/show_bug.cgi?id=23216 My problem: I cannot have compiz and 3d games are way too slow: glxinfo | grep -i render unknown chip id 0x9610, can't guess. direct rendering: Yes OpenGL renderer string: Software Rasterizer I have these in Xorg log (II) AIGLX: Screen 0 is not DRI2 capable drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 11, (OK) drmOpenByBusid: Searching for BusID pci::01:05.0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: open result is 11, (OK) drmOpenByBusid: drmOpenMinor returns 11 drmOpenByBusid: drmGetBusid reports pci::01:05.0 (EE) AIGLX error: Calling driver entry point failed(EE) AIGLX: reverting to software rendering (II) AIGLX: Loaded and initialized /usr/lib/dri/swrast_dri.so I suspect the "unknown chip" error hints about the culprit. I have the following: * Gigabyte GA-MA78GM-UD2H motherboard which has HD 3200 integrated graphics adapter. * Jaunty 9.04. * 64 bits. Best regards. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 23290] Resume broken with new ATI stack
http://bugs.freedesktop.org/show_bug.cgi?id=23290 Jörg Mayer changed: What|Removed |Added CC||jmx...@loplof.de --- Comment #6 from Jörg Mayer 2009-08-24 08:01:32 PST --- I probably should have mentioned that I opened bug 23479 about that. That bug also contains the logs that come up during resume. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 23290] Resume broken with new ATI stack
http://bugs.freedesktop.org/show_bug.cgi?id=23290 --- Comment #5 from Jörg Mayer 2009-08-24 07:56:38 PST --- Yes, the pictures look very familiar :-) Note that I do not see the bars before suspend - but as my system currently doesn't support suspend-to-disk, I can't verify whether that's a suspend-to-disk vs. suspend-to-ram thing. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 23479] KMS: output broken after resume from RAM
http://bugs.freedesktop.org/show_bug.cgi?id=23479 --- Comment #11 from Yang Zhao 2009-08-24 07:41:02 PST --- Duplicate of bug 23290 -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 23386] Artifacts with cairo dock 2.0 [openGL]
http://bugs.freedesktop.org/show_bug.cgi?id=23386 --- Comment #11 from Michel Dänzer 2009-08-24 06:37:55 PST --- (In reply to comment #10) > Even so, i tried cairo-dock but it *would not start* . > I ran cairo-dock in debug mode and it had only one line: > > drmRadeonCmdBuffer: -22 Check the dmesg output. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 23387] [R300] Screen artifacts on X [KMS]
http://bugs.freedesktop.org/show_bug.cgi?id=23387 --- Comment #8 from Michel Dänzer 2009-08-24 06:35:20 PST --- (In reply to comment #7) > EXANoDownloadFromScreen only helped when no OpenGL app was runnning at least > for the time I tested. Once I started Auteria (http://www.auteria.com)game in > the window, the font tearing and artifacts started appearing again. A similar mechanism as for DownloadFromScreen is used for evicting buffer objects from VRAM, so this indicates that VRAM -> AGP transfers are generally unreliable on your system. One thing I notice in your dmesg is [35162.662996] [drm] AGP mode requested: 4 Maybe you can try different values for the radeon.agpmode parameter, including 1, 2, not specifying any explicitly or -1 to disable AGP. If none of that helps, maybe you can try booting the kernel or loading the radeon kernel module with radeon.test=1 and see if that gives any interesting results. > Also the text inside the game is flickering. That could be a separate issue. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 23386] Artifacts with cairo dock 2.0 [openGL]
http://bugs.freedesktop.org/show_bug.cgi?id=23386 --- Comment #10 from mac_v 2009-08-24 06:35:10 PST --- (In reply to comment #9) > > xorg-edgers ppa (https://launchpad.net/~xorg-edgers/+archive/ppa) has the > latest 3D drivers for Ubuntu. > > Kernel parameter can be set in grub when you boot. You can just append it to > current kernel boot options. Another option is to set it in /etc/modprobe.d/ > but that would require grub command line modifications in case something goes > wrong. > I installed the ppa and tried with kernel mode setting. But my system became very sluggish, i mean really very very sluggish. Even so, i tried cairo-dock but it *would not start* . I ran cairo-dock in debug mode and it had only one line: drmRadeonCmdBuffer: -22 I'm still running the ppa but without KMS , if i run cairo-dock using openGL it has the same artifacts as before.[i understand this problem would only improve with KMS but just mentioning]. So now , 1 . does the above error i got for cairo-dock with KMS , have to be dealt with by cairo-dock or by the graphics driver? 2. Could i have a link to the bug for the radeon KMS slow behavior, i wouldnt mind testing any unstable drivers which fix this. Thanx for the help :) -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 23479] KMS: output broken after resume from RAM
http://bugs.freedesktop.org/show_bug.cgi?id=23479 --- Comment #10 from Jörg Mayer 2009-08-24 05:31:02 PST --- Created an attachment (id=28880) --> (http://bugs.freedesktop.org/attachment.cgi?id=28880) dmesg after saving/resuming via powersave -u -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 23479] KMS: output broken after resume from RAM
http://bugs.freedesktop.org/show_bug.cgi?id=23479 --- Comment #9 from Jörg Mayer 2009-08-24 05:20:22 PST --- Created an attachment (id=28879) --> (http://bugs.freedesktop.org/attachment.cgi?id=28879) result of dmesg after broken resume from echo on x OK, some more experimenting results in: - echo and s2ram do not always break when run from X, just often (2 out of ~10 were not broken) - once it is broken, it is possible to reliably revive the vt by loggin in remotely, chvt 1, running s2ram again and then resuming. I did not manage to revive X that way (even restarting X after such a procedure didn't work). -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 23334] 2D Acceleration not working on RV620/HD3470
http://bugs.freedesktop.org/show_bug.cgi?id=23334 --- Comment #8 from Maximilian Engelhardt 2009-08-24 05:00:30 PST --- I tried with a Ubuntu 9.10 (Karmic Koala) Alpha 4 live CD and it's the same problem there. I guess this should be a recent enough X server. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 23387] [R300] Screen artifacts on X [KMS]
http://bugs.freedesktop.org/show_bug.cgi?id=23387 --- Comment #7 from Gytis Raciukaitis 2009-08-24 04:47:07 PST --- EXANoDownloadFromScreen only helped when no OpenGL app was runnning at least for the time I tested. Once I started Auteria (http://www.auteria.com)game in the window, the font tearing and artifacts started appearing again. Also the text inside the game is flickering. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 23479] KMS: output broken after resume from RAM
http://bugs.freedesktop.org/show_bug.cgi?id=23479 --- Comment #8 from Jörg Mayer 2009-08-24 03:54:27 PST --- Just as an addition to #6: X is fine after the resume as long as echo or s2ram were run from a vt and not from X. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 23479] KMS: output broken after resume from RAM
http://bugs.freedesktop.org/show_bug.cgi?id=23479 --- Comment #7 from Jörg Mayer 2009-08-24 03:37:28 PST --- Created an attachment (id=28876) --> (http://bugs.freedesktop.org/attachment.cgi?id=28876) output of dmesg of resume -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 23479] KMS: output broken after resume from RAM
http://bugs.freedesktop.org/show_bug.cgi?id=23479 --- Comment #6 from Jörg Mayer 2009-08-24 03:36:37 PST --- Made some tests with powersaving: echo mem >/sys/power/state s2ram powersave -u Results: echo and s2ram work, when run from a vt, they don't when run from X; powersave never works I'll attach the output of dmesg from the resume of echo. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 23479] KMS: output broken after resume from RAM
http://bugs.freedesktop.org/show_bug.cgi?id=23479 --- Comment #5 from Jörg Mayer 2009-08-24 02:52:39 PST --- Created an attachment (id=28875) --> (http://bugs.freedesktop.org/attachment.cgi?id=28875) log of resume -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 23479] KMS: output broken after resume from RAM
http://bugs.freedesktop.org/show_bug.cgi?id=23479 --- Comment #4 from Jörg Mayer 2009-08-24 02:47:09 PST --- The system is opensuse 11.1 with all the necessary components updated to be able to run kms (kernel, X, libdrm, radeon driver, mesa). The suspend is done via "powersave -u". vbetool is not installed. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 23479] KMS: output broken after resume from RAM
http://bugs.freedesktop.org/show_bug.cgi?id=23479 --- Comment #3 from Jörg Mayer 2009-08-24 02:46:37 PST --- Created an attachment (id=28874) --> (http://bugs.freedesktop.org/attachment.cgi?id=28874) r100_rbbm_info -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 23479] KMS: output broken after resume from RAM
http://bugs.freedesktop.org/show_bug.cgi?id=23479 --- Comment #2 from Jörg Mayer 2009-08-24 02:46:02 PST --- Created an attachment (id=28873) --> (http://bugs.freedesktop.org/attachment.cgi?id=28873) lspci -v -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 23479] KMS: output broken after resume from RAM
http://bugs.freedesktop.org/show_bug.cgi?id=23479 --- Comment #1 from Jörg Mayer 2009-08-24 02:24:47 PST --- Created an attachment (id=28872) --> (http://bugs.freedesktop.org/attachment.cgi?id=28872) The archive mentioned -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 23479] New: KMS: output broken after resume from RAM
http://bugs.freedesktop.org/show_bug.cgi?id=23479 Summary: KMS: output broken after resume from RAM Product: xorg Version: 7.4 Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/Radeon AssignedTo: xorg-driver-ati@lists.x.org ReportedBy: jmx...@loplof.de QAContact: xorg-t...@lists.x.org I'm using a Radeon Mobility X1400 with KMS (kernel: rc6). After I do a suspend to ram + resume the output consists of vertical bars that often - but not always change colors. There is no way to identify anything of the desktop's contents. I'll attach an archive to the bug containing: resume.log: contents of /var/log/messages with everything before and after the resume removed - the log itself is complete. script.log: lspci, git commands showing which exact version of libdrm, xf86-video-ati and mesa I'm using, glxinfo, uname Xorg.0.log, Xorg.0.log.old, kdm.log, xorg.conf: Just to be complete. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
