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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
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/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled,
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 800x600x60.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.
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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#484015: xserver-xorg-video-ati: [r128][powerpc] output is limited to 800x600 even with 1024x768 display
Hi, Alex. On Jun 02 2008, Alex Deucher wrote: FWIW, you might also try commenting out the Usefbdev option. IIRC, the driver does work without it. Yes, the driver also works without it, but I have already tried setting the option to use the kernel framebuffer to false in the X.org config file. :-( Thanks for your reply, Rogério Brito. P.S.: I'm more and more convinced that this problem may lay in kernel space instead of user space, even though X blurs the whole thing. :-) -- 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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#484015: xserver-xorg-video-ati: [r128][powerpc] output is limited to 800x600 even with 1024x768 display
Hi, all. On Jun 02 2008, Rogério Brito wrote: P.S.: I'm more and more convinced that this problem may lay in kernel space instead of user space, even though X blurs the whole thing. :-) Well, it seems that something is way wrong here. I just installed gcc-3.4 and compiled a kernel 2.6.9 and the result that I got was exactly the same as before. That is, even jumping way back from kernel 2.6.26-rc4 to kernel 2.6.9, things have not changed, which leads me to think that now that the problem may be connected with Xorg, perhaps... :-( I'm compiling a 2.6.8 kernel just for some safety (since this was the version that shipped with sarge, wasn't it? my memory isn't that good here). Does x.org have something like a git repository? I would be willing to do some git bisect iterations to see if I can find the changeset that modified this behavior. 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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#484015: xserver-xorg-video-ati: [r128][powerpc] output is limited to 800x600 even with 1024x768 display
Rogério Brito wrote: Does x.org have something like a git repository? I would be willing to do some git bisect iterations to see if I can find the changeset that modified this behavior. 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... Good luck, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#484015: xserver-xorg-video-ati: [r128][powerpc] output is limited to 800x600 even with 1024x768 display
Package: xserver-xorg-video-ati Version: 1:6.8.0-1 Severity: important Hi, I am using an iBook G3 600MHz Combo, 12, 1024x768 display, Late 2001 model, with a freeshly installed sid system (I want to get rid of MacOS X, since it is too slow on this machine). Unfortunately, X has some severe problems that were discussed in the debian-powerpc mailing list a short while ago. [1] The distortion that I'm seeing is that the screen is regarded as only 800x600 and the right side is completely black while the bottom area is a mirror of the top area. I have given a lot of details in Ubuntu's lauchpad, including photos that I've taken from this notebook while it was running their latest release. [2] Please, help. I need to use this machine as soon as possible. I have already tried compiling a newer kernel, but it seems that there may be some bad interaction between the kernel and the X server. BTW, I was able to use this machine perfectly in the 2.4 kernel era (I think that it was still with the XFree86 server at the time). 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 (...) If more information is needed, please let me know. Thanks in advance, Rogerio Brito. [1] http://lists.debian.org/debian-powerpc/2008/05/msg00055.html [2] https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/224343 -- Package-specific info: Contents of /var/lib/x11/X.roster: xserver-xorg /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 2008-05-30 14:48 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1948376 2008-05-18 11:27 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: :00:10.0 VGA compatible controller: ATI Technologies Inc Rage Mobility M3 AGP 2x (rev 02) /etc/X11/xorg.conf unchanged from checksum in /var/lib/x11/xorg.conf.md5sum. Xorg X server configuration file status: -rw-r--r-- 1 root root 1175 2008-05-30 15:36 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # 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 EndSection Section Screen Identifier Default Screen Monitor Configured Monitor EndSection Xorg X server log files on system: -rw-r--r-- 1 root root 35186 2008-06-01 17:58 /var/log/Xorg.0.log Contents of most recent Xorg X server log file /var/log/Xorg.0.log: 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: Sun Jun 1 17:58:06 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
