Bug#484015: xserver-xorg-video-ati: [r128][powerpc] output is limited to 800x600 even with 1024x768 display
Hi there. I finally made X work with full 1024x768 resolution on this iBook. (hooray!). I'm sending a copy of this to -powerpc for reference and future googlers. First I downgraded the whole Xorg and its components to the stable version (etch?). Then, I was conservative and used dpkg-reconfigure to configure the monitor. It worked *fine*. On the other hand, using a configuration file (xorg.conf) from sid on the etch branch gave me the same results as if I were using sid. But keeping the etch-generated file with sid xorg.conf worked fine. I think (I'm investigating this right now) that the issue here is that the modern Xorg configuration tools don't write the monitor frequencies (if I ask X to configure itself with "X -configure"), while they seem crucial on this machine for it to work. (Just tested it) Yep! That's it: the lines with the monitor frequencies are *needed* for X to work with the correct resolution. Even though I made this work, I think that this bug is quite not done yet, but I can lower its severity to normal. On Jun 03 2008, Brice Goglin wrote: > There are many different components in Xorg. The one you should look at are: > * the r128 driver is at > git://anongit.freedesktop.org/git/xorg/driver/xf86-video-r128 > * the Xservet at git://anongit.freedesktop.org/git/xorg/xserver > > Bisecting the former should be easy. Bisecting the latter may be much > more a pain due to ABI changes or so... Nice. I can bisect it now to see the culprit changeset. Thanks, Rogério Brito. -- Rogério Brito : [EMAIL PROTECTED],ime.usp}.br : GPG key 1024D/7C2CAEB8 http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 15846] display horribly rendered with radeon 7200 card on ubuntu 8.04 (Hardy)
http://bugs.freedesktop.org/show_bug.cgi?id=15846 --- Comment #4 from Tom Horsley <[EMAIL PROTECTED]> 2008-06-02 13:54:38 PST --- Nope, same ridiculous colors with or without DefaultTMDSPLL. -- 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#457612: xserver-xorg-video-ati: x fails after update on testing. ppc ati 7500 graphics card
On Sat, May 31, 2008 at 8:43 AM, LeeE <[EMAIL PROTECTED]> wrote: > On Friday 30 May 2008 19:06, you wrote: >> On Fri, May 30, 2008 at 10:15 AM, LeeE <[EMAIL PROTECTED]> > wrote: >> > I'd like to add that I'm getting the same problem as >> > oswaldkelso except that I'm on i386 and not ppc and the card is >> > an ATI 9200 (RV280). I can boot the system in to a back up >> > 'etch' install where it works ok. >> > >> > To summarise: >> > >> > Xorg appears to load and run ok but the screen remains blank. >> > If I leave the system alone i.e. not touching the mouse or >> > keyboard I can see the monitor switch into standby and then if >> > I hit a key or move the mouse the monitor comes back out of >> > standby but the screen remains blank. >> > >> > When booting the system from an Ubuntu 8 cd for a live session >> > I can hear the session start-up sounds, indicating that xorg >> > thinks it's working ok. If I then Ctrl+Alt+Backspace to kill X >> > I hear the session startup sounds again, as x reloads. >> > >> > A curious thing I've noticed is that when X thinks it's running >> > ok it's not possible to use the screen (A Philips 109s CRT >> > monitor) OSD controls to change brightness, contrast etc. - the >> > OSD controls do not appear on the screen, but they do appear ok >> > when back in the console or when etch is running. >> > >> > Running with DPMS disabled made no difference - it does not >> > seem to be possible to disable EDID with the xorg ati driver. >> > >> > I've also tried several different kernel versions, with no >> > change. >> > >> > Please let me know if you want the xorg conf & log, but they >> > don't seem to show anything relevent - as I say, xorg seems to >> > think that it's running ok. >> >> Please provide your xorg log and config. >> >> Alex > > Hello Alex, > > I've attached these. xserver strikes again! the xserver is picking a mode that your monitor doesn't like: (II) RADEON(0): Output VGA-0 using initial mode 1600x1024 while the mode is within sync ranges of your config and the ones in your edid, this mode obviously isn't workable. We really need to patch the randr core to limit itself to edid or driver provided modes for the initial mode. Ajax did some recent work in this regard. this might be the cause of or solution to the problem. you can override this by adding a PreferredMode option to the monitor section linked to the output in question. See this page for more: http://wiki.debian.org/XStrikeForce/HowToRandR12 Alex ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 15846] display horribly rendered with radeon 7200 card on ubuntu 8.04 (Hardy)
http://bugs.freedesktop.org/show_bug.cgi?id=15846 --- Comment #3 from Alex Deucher <[EMAIL PROTECTED]> 2008-06-02 07:31:10 PST --- does this option help? Option "DefaultTMDSPLL" "TRUE" -- 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 15846] display horribly rendered with radeon 7200 card on ubuntu 8.04 (Hardy)
http://bugs.freedesktop.org/show_bug.cgi?id=15846 --- Comment #2 from Tom Horsley <[EMAIL PROTECTED]> 2008-06-02 07:25:24 PST --- After looking at this for a while, I'm wondering if the driver is somehow enabling the color mapping hardware on the 7200 instead of a truecolor mode? That would certainly wind up with random data being used for the colormap and produce silly looking output like I see (just a random thought, I have no idea if it is really the problem). -- 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#484015: xserver-xorg-video-ati: [r128][powerpc] output is limited to 800x600 even with 1024x768 display
On Mon, Jun 2, 2008 at 9:24 AM, Rogério Brito <[EMAIL PROTECTED]> wrote: > Hi, Michel. Long time no see/talk. :-) > > On Jun 02 2008, Michel Dänzer wrote: >> On Sun, 2008-06-01 at 18:29 -0300, Rogerio Brito wrote: >> > Oh, BTW, one error/warning that I see reported on the machine's >> > console (and that apparently doesn't get included in the X logs) is >> > the following: >> > >> > (many times the following error---at least 20 times in a row) >> > (EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument >> > (...) >> >> But they are included in the log file: >> >> > (II) R128(0): Not using default mode "1024x768" (unknown reason) >> > (EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument > (...) > > Sorry. Missed them while perusing the file. > >> So, for some reason the kernel's aty128fb is rejecting the X server's >> 1024x768 modes. > > Indeed. That's one of the reasons why I tried downloading an older 2.6 > kernel, but the dependencies of modern udev have stopped me from > compiling it (I would try with the kernel released with sarge, i.e., > 2.6.8). > >> Have you tried putting an X mode definition (e.g. obtained by fbset >> -x) of the console 1024x768 mode into the xorg.conf monitor section? > > Yes, I did that when I first reported this bug to Ubuntu, but apparently > the bug went unnoticed for a long time and sorted as "unimportant" (!) > or something like that. > > Anyway, I just tried it again and I'm including here attached both the > xorg.conf and the X log. FWIW, you might also try commenting out the "Usefbdev" option. IIRC, the driver does work without it. Alex ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 16200] New: Xorg server busy-loops at start when DRI is true
http://bugs.freedesktop.org/show_bug.cgi?id=16200 Summary: Xorg server busy-loops at start when DRI is true Product: xorg Version: git Platform: x86-64 (AMD64) OS/Version: FreeBSD Status: NEW Severity: major Priority: medium Component: Driver/Radeon AssignedTo: xorg-driver-ati@lists.x.org ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] I am using the latest xorg-server from git, built against the following packages: * dri2proto from git * drm from git * glproto from git * inputproto from git * kbproto from git * libX11 from git * libxcb from git * mesa from git I've pulled down the latest DRM from git and build/installed the kernel modules against the latest FreeBSD 8.0-CURRENT (June 1st, 2008). I cannot start the Xserver using the latest radeon driver (commit 8504c6b0e40477ee544ad7f5366d569bdc53d6f0) from xf86-video-ati, when I have DRI enabled. The symptom is that the Xserver starts up and clears the screen (sets up the video mode I guess), but stops in a loop (100% CPU, nearly all of it system time) before it begins rendering to the screen. I used dcons to connect to another box and get a message dump, and the result is that the drm driver is running a loop printing the following to the screen (endlessly, but pausing between each print): [drm:pid1385:radeon_cp_idle] [drm:pid1385:radeon_do_cp_idle] [drm:pid1385:drm_ioctl] returning 16 [drm:pid1385:drm_ioctl] pid=1385, cmd=0x20006444, nr=0x44, dev 0xff000129d600, auth=1 [drm:pid1385:radeon_cp_idle] [drm:pid1385:radeon_do_cp_idle] [drm:pid1385:drm_ioctl] returning 16 [drm:pid1385:drm_ioctl] pid=1385, cmd=0x20006444, nr=0x44, dev 0xff000129d600, auth=1 [drm:pid1385:radeon_cp_idle] [drm:pid1385:radeon_do_cp_idle] [drm:pid1385:drm_ioctl] returning 16 [drm:pid1385:drm_ioctl] pid=1385, cmd=0x20006444, nr=0x44, dev 0xff000129d600, auth=1 I can access the box via SSH, and it looks like Xorg just hoses my display until I reboot the thing. This is an RS690T on an HP Compaq 6715b notebook with a 1680x1050 flat panel. The following is the drm probe output: drm0: on vgapci0 info: [drm] Initialized radeon 1.29.0 20080528 Output of "lspci -nn -s 01:05 -v": 01:05.0 VGA compatible controller [0300]: ATI Technologies Inc RS690M [Radeon X1200 Series] [1002:791f] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Unknown device [103c:30c2] Flags: bus master, fast devsel, latency 64, IRQ 19 Memory at c000 (64-bit, prefetchable) Memory at d040 (64-bit, non-prefetchable) I/O ports at 4000 Memory at d050 (32-bit, non-prefetchable) Capabilities: [50] Power Management version 2 Capabilities: [80] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable- Perhaps interesting to note is that this is an IGP chip, the drm kmod probes it as a PCI device (specifically neither PCIY_EXPRESS or PCIY_AGP). I am not sure if this is helpful. Using the radeonhd driver, I can get the Xserver to come up with DRI enabled, but I get a blank (black space) where rendering should be for glxgears, etc... The output of glxinfo using the radeonhd driver seems to be okay. -- 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 with R500 with 3D enabled
http://bugs.freedesktop.org/show_bug.cgi?id=16198 --- Comment #3 from Alex Deucher <[EMAIL PROTECTED]> 2008-06-02 07:08:38 PST --- I suppose it's technically r300, since that driver supports r3xx-r5xx. -- 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 with R500 with 3D enabled
http://bugs.freedesktop.org/show_bug.cgi?id=16198 Alex Deucher <[EMAIL PROTECTED]> changed: What|Removed |Added Component|Driver/Radeon |Drivers/DRI/r300 Product|xorg|Mesa Version|git |CVS -- 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#484015: xserver-xorg-video-ati: [r128][powerpc] output is limited to 800x600 even with 1024x768 display
Hi again. On Jun 02 2008, Rogério Brito wrote: > Anyway, I just tried it again and I'm including here attached both the > xorg.conf and the X log. Just to make things easier to spot, here is the diff of the log without the modeline and with the modeline provided by fbset. Thanks again, Rogério. -- Rogério Brito : [EMAIL PROTECTED],ime.usp}.br : GPG key 1024D/7C2CAEB8 http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org --- old.Xorg.0.log 2008-06-02 10:28:00.0 -0300 +++ Xorg.0.log 2008-06-02 10:16:00.0 -0300 @@ -1,3 +1,4 @@ + X.Org X Server 1.4.0.90 Release Date: 5 September 2007 X Protocol Version 11, Revision 0 @@ -11,7 +12,7 @@ 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: Sun Jun 1 17:58:06 2008 +(==) Log file: "/var/log/Xorg.0.log", Time: Mon Jun 2 10:00:41 2008 (==) Using config file: "/etc/X11/xorg.conf" (==) No Layout section. Using the first Screen section. (**) |-->Screen "Default Screen" (0) @@ -338,6 +339,7 @@ (II) R128(0): Configured Monitor: Using default vrefresh range of 50.00-70.00 Hz (WW) R128(0): Unable to estimate virtual size (II) R128(0): Clock range: 12.50 to 250.00 MHz +(II) R128(0): Not using mode "1024x768" (unknown reason) (II) R128(0): Not using default mode "640x350" (vrefresh out of range) (EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument (II) R128(0): Not using default mode "320x175" (unknown reason) @@ -373,19 +375,13 @@ (EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument (II) R128(0): Not using default mode "400x300" (unknown reason) (EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument -(II) R128(0): Not using default mode "1024x768" (unknown reason) -(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument (II) R128(0): Not using default mode "512x384" (unknown reason) -(II) R128(0): Not using default mode "1024x768" (hsync out of range) (EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument (II) R128(0): Not using default mode "512x384" (unknown reason) -(II) R128(0): Not using default mode "1024x768" (hsync out of range) (EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument (II) R128(0): Not using default mode "512x384" (unknown reason) -(II) R128(0): Not using default mode "1024x768" (hsync out of range) (EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument (II) R128(0): Not using default mode "512x384" (unknown reason) -(II) R128(0): Not using default mode "1024x768" (hsync out of range) (EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument (II) R128(0): Not using default mode "512x384" (unknown reason) (II) R128(0): Not using default mode "1152x864" (hsync out of range) @@ -485,14 +481,8 @@ (EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument (II) R128(0): Not using default mode "960x720" (unknown reason) (II) R128(0): Not using default mode "2048x1536" (insufficient memory for mode) -(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument -(II) R128(0): Not using default mode "1024x768" (unknown reason) (II) R128(0): Not using default mode "2048x1536" (insufficient memory for mode) -(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument -(II) R128(0): Not using default mode "1024x768" (unknown reason) (II) R128(0): Not using default mode "2048x1536" (insufficient memory for mode) -(EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument -(II) R128(0): Not using default mode "1024x768" (unknown reason) (--) R128(0): Virtual size is 800x600 (pitch 800) (**) R128(0): *Default mode "800x600": 40.0 MHz, 37.9 kHz, 60.3 Hz (II) R128(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz) @@ -681,6 +671,6 @@ (--) Configured Mouse: PnP-detected protocol: "ExplorerPS/2" (II) Configured Mouse: ps2EnableDataReporting: succeeded (II) R128(0): [drm] removed 1 reserved context for kernel -(II) R128(0): [drm] unmapping 8192 bytes of SAREA 0xe905e000 at 0x48022000 +(II) R128(0): [drm] unmapping 8192 bytes of SAREA 0xe9898000 at 0x48022000 (II) R128(0): [drm] Closed DRM master. FreeFontPath: FPE "/usr/share/fonts/X11/misc" refcount is 2, should be 1; fixing. ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
Bug#484015: xserver-xorg-video-ati: [r128][powerpc] output is limited to 800x600 even with 1024x768 display
Hi, Michel. Long time no see/talk. :-) On Jun 02 2008, Michel Dänzer wrote: > On Sun, 2008-06-01 at 18:29 -0300, Rogerio Brito wrote: > > Oh, BTW, one error/warning that I see reported on the machine's > > console (and that apparently doesn't get included in the X logs) is > > the following: > > > > (many times the following error---at least 20 times in a row) > > (EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument > > (...) > > But they are included in the log file: > > > (II) R128(0): Not using default mode "1024x768" (unknown reason) > > (EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument (...) Sorry. Missed them while perusing the file. > So, for some reason the kernel's aty128fb is rejecting the X server's > 1024x768 modes. Indeed. That's one of the reasons why I tried downloading an older 2.6 kernel, but the dependencies of modern udev have stopped me from compiling it (I would try with the kernel released with sarge, i.e., 2.6.8). > Have you tried putting an X mode definition (e.g. obtained by fbset > -x) of the console 1024x768 mode into the xorg.conf monitor section? Yes, I did that when I first reported this bug to Ubuntu, but apparently the bug went unnoticed for a long time and sorted as "unimportant" (!) or something like that. Anyway, I just tried it again and I'm including here attached both the xorg.conf and the X log. Thanks, Rogério Brito. -- Rogério Brito : [EMAIL PROTECTED],ime.usp}.br : GPG key 1024D/7C2CAEB8 http://www.ime.usp.br/~rbrito : http://meusite.mackenzie.com.br/rbrito Projects: algorithms.berlios.de : lame.sf.net : vrms.alioth.debian.org # xorg.conf (X.Org X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type "man xorg.conf" at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section "InputDevice" Identifier "Generic Keyboard" Driver "kbd" Option "XkbRules" "xorg" Option "XkbModel" "pc104" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "Emulate3Buttons" "true" EndSection Section "Device" Identifier "Configured Video Device" Driver "ati" BusID "PCI:0:16:0" Option "UseFBDev" "true" EndSection Section "Monitor" Identifier "Configured Monitor" Mode "1024x768" # D: 64.994 MHz, H: 48.359 kHz, V: 59.998 Hz DotClock 64.995 HTimings 1024 1064 1200 1344 VTimings 768 771 777 806 Flags"-HSync" "-VSync" EndMode EndSection Section "Screen" Identifier "Default Screen" Monitor "Configured Monitor" EndSection X.Org X Server 1.4.0.90 Release Date: 5 September 2007 X Protocol Version 11, Revision 0 Build Operating System: Linux Debian (xorg-server 2:1.4.1~git20080517-1) Current Operating System: Linux ibook 2.6.26-rc4-3 #1 Sun Jun 1 15:21:45 BRT 2008 ppc Build Date: 18 May 2008 01:16:18PM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present 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 Jun 2 10:00:41 2008 (==) Using config file: "/etc/X11/xorg.conf" (==) No Layout section. Using the first Screen section. (**) |-->Screen "Default Screen" (0) (**) | |-->Monitor "Configured Monitor" (==) No device specified for screen "Default Screen". Using the first device section listed. (**) | |-->Device "Configured Video Device" (==) |-->Input Device "Configured Mouse" (==) |-->Input Device "Generic Keyboard" (==) The core pointer device wasn't specified explicitly in the layout. Using the first mouse device. (==) The core keyboard device wasn't specified explicitly in the layout. Using the first keyboard device. (==) Automatically adding devices (==) Automatically enabling devices (==) No FontPath specified. Using compiled-in default. (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. Entry deleted from font path. (WW) The directory "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType" does not exist. Entry deleted from font path. (==) FontPath set to: /usr/shar
[Bug 16198] Random hard lockups with R500 with 3D enabled
http://bugs.freedesktop.org/show_bug.cgi?id=16198 Julien Cristau <[EMAIL PROTECTED]> changed: What|Removed |Added AssignedTo|[EMAIL PROTECTED] |xorg-driver-ati@lists.x.org Component|* Other |Driver/Radeon --- Comment #2 from Julien Cristau <[EMAIL PROTECTED]> 2008-06-02 06:14:49 PST --- reassigning to Driver/Radeon for now (it seems there's no r500 component for mesa yet) -- 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 16193] r500 screen corruption ( unable to reserve offscreen area for back buffer)
http://bugs.freedesktop.org/show_bug.cgi?id=16193 --- Comment #1 from Allart Kooiman <[EMAIL PROTECTED]> 2008-06-02 04:37:28 PST --- Sorry, I just realised I used the normal X server last week instead of git. But that doesn't change the issue. Setting XaanOffSceenpixmaps to true solves it. -- 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#484015: xserver-xorg-video-ati: [r128][powerpc] output is limited to 800x600 even with 1024x768 display
On Sun, 2008-06-01 at 18:29 -0300, Rogerio Brito wrote: > > Oh, BTW, one error/warning that I see reported on the machine's console (and > that > apparently doesn't get included in the X logs) is the following: > > (many times the following error---at least 20 times in a row) > (EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument > (...) But they are included in the log file: > (II) R128(0): Not using default mode "1024x768" (unknown reason) > (EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument > (II) R128(0): Not using default mode "512x384" (unknown reason) > (II) R128(0): Not using default mode "1024x768" (hsync out of range) > (EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument > (II) R128(0): Not using default mode "512x384" (unknown reason) > (II) R128(0): Not using default mode "1024x768" (hsync out of range) > (EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument > (II) R128(0): Not using default mode "512x384" (unknown reason) > (II) R128(0): Not using default mode "1024x768" (hsync out of range) > (EE) R128(0): FBIOPUT_VSCREENINFO: Invalid argument > (II) R128(0): Not using default mode "512x384" (unknown reason) > (II) R128(0): Not using default mode "1024x768" (hsync out of range) So, for some reason the kernel's aty128fb is rejecting the X server's 1024x768 modes. Have you tried putting an X mode definition (e.g. obtained by fbset -x) of the console 1024x768 mode into the xorg.conf monitor section? -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer ___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org http://lists.x.org/mailman/listinfo/xorg-driver-ati
[Bug 16193] New: r500 screen corruption ( unable to reserve offscreen area for back buffer)
http://bugs.freedesktop.org/show_bug.cgi?id=16193 Summary: r500 screen corruption (unable to reserve offscreen area for back buffer) Product: xorg Version: git Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: minor Priority: medium Component: Driver/Radeon AssignedTo: xorg-driver-ati@lists.x.org ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] Created an attachment (id=16864) --> (http://bugs.freedesktop.org/attachment.cgi?id=16864) Xorg log Xorg log reports: "(EE) RADEON(0): Unable to reserve offscreen area for back buffer, you might experience screen corruption". I notice indeed some screen corruption in the right area of my screen. One week ago I saw them only with exa enabled in my xorg.conf. I'm using the xorg edgers packages of 06-01-2008 on ubuntu hardy. -- 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 16185] Changing outputs on RS690 turns screen green
http://bugs.freedesktop.org/show_bug.cgi?id=16185 Kevin Read <[EMAIL PROTECTED]> changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Comment #2 from Kevin Read <[EMAIL PROTECTED]> 2008-06-02 00:52:59 PST --- As Roland pointed out in the other report, the board is actually a ASUS M2A-VM, my bad, sorry about that. -- 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 16186] TV-Out doesn't work on RS690
http://bugs.freedesktop.org/show_bug.cgi?id=16186 Kevin Read <[EMAIL PROTECTED]> changed: What|Removed |Added CC||[EMAIL PROTECTED] --- Comment #2 from Kevin Read <[EMAIL PROTECTED]> 2008-06-02 00:51:45 PST --- Oops, of course. This should read ASUS M2A-VM, thanks for pointing that out. -- 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
