Re: [Xpert]XFree86 CVS and 1600x1024 (DVI) / Radeon
Wonderful. The reason I never saw the post was that my delivery was disabled for the list. I was wondering why my XFree86 mail folder was rather light lately. :-/ This must automatically happen when my mail server starts bouncing messages when the quota gets exceeded. Anyway, here's answers to the replies I found on the web archives: Keith Packard wrote: Hmm. The Radeon driver mode selection code was restructured during the RandR integration, it's quite possible that some mode lines aren't getting properly added. But, your log file seems to list 1600x1024 as a valid mode, so I'm a bit confused. What does 'xrandr' list as valid sizes? The log you enclosed showed the screen running at 16bpp; I assume setting the depth to 24 switches that to 32bpp? Yes, lately I've been running at 16bpp due to the lack of benefit in the higher bit plane modes. I've attached a 24 bit log file. During this session, I verified that pixmaps do have quite a bit of color banding, more so than other 24bit displays. It did push the fbbpp up to 32bpp. Note that this is DVI-DFP. It could be hardware limited, but I can't verify this (there's nothing but Linux on this machine). I've also attached output of some xrandr commands. This required rebuilding xrandr without any opt flags. The executable built with standard opt flags (none specified by myself, I only specified ProjectRoot) refused to interpret any arguments. This is likely due to using gcc 3.2 (RH8). Also note that it lists 1600x1024 as the active mode. The root window is indeed 1600x1024, but the image my SGI is getting is definately 1280x1024. Dr Andrew C Aitchison wrote: When I was looking for a dvi card for my SGI 1600SW, I thought I read that the Radeon didn't official support that resolution; maybe the driver now supports the resolution limit on the card :-( It seems to work quite well here. As distributed with RH8, XFree86 came up at 1600x1024 without needing a modeline. Previously, I used the following: Modeline sgi1600x1024 106.9 1600 1632 1656 1672 1024 1027 1030 1067 That log file says that the config file requested 16bpp :-) Yes, I've been running 16bpp due to the fact that it looks exactly the same as 24bpp. :-) 24bit log file attached. It also says that it is using the DAC in 6bit mode, which would not help. Hrm.. here's the 24bit log. It's listed as 8bit here, but there's still considerable color banding. Jeff This is a pre-release version of XFree86, and is not supported in any way. Bugs may be reported to [EMAIL PROTECTED] and patches submitted to [EMAIL PROTECTED] Before reporting bugs in pre-release versions, please check the latest version in the XFree86 CVS repository (http://www.XFree86.Org/cvs) XFree86 Version 4.2.99.1 / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 15 October 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: Linux 2.4.19-xfs i686 [ELF] 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/XFree86.0.log, Time: Mon Oct 21 22:23:40 2002 (==) Using config file: /etc/X11/XF86Config (==) ServerLayout Anaconda Configured (**) |--Screen Screen0 (0) (**) | |--Monitor Monitor0 (**) | |--Device ATI Radeon VE (**) |--Input Device Mouse0 (**) |--Input Device Keyboard0 (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc105 (**) XKB: model: pc105 (**) Option XkbLayout us (**) XKB: layout: us (==) Keyboard: CustomKeycode disabled (**) FontPath set to unix/:7100 (**) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6-CVS/lib/modules (--) using VT number 7 (II) Open APM successful (II) Module ABI versions: XFree86 ANSI C Emulation: 0.1 XFree86 Video Driver: 0.6 XFree86 XInput driver : 0.3 XFree86 Server Extension : 0.1 XFree86 Font Renderer : 0.3 (II) Loader running on linux (II) LoadModule: bitmap (II) Loading /usr/X11R6-CVS/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor=The XFree86 Project compiled for 4.2.99.1, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.3 (II) Loading font Bitmap (II) LoadModule: pcidata (II) Loading /usr/X11R6-CVS/lib/modules/libpcidata.a (II) Module pcidata: vendor=The XFree86 Project compiled for 4.2.99.1, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI:
Re: [Xpert]XFree86 CVS and 1600x1024 (DVI) / Radeon
On Mon, 21 Oct 2002, Jeff Brubaker wrote: Unfortunately, X comes up with a root window size of 1600x1024 (reported by xdpyinfo) but is really only outputting 1280x1024 (reported by my SGI MultiLink adapter). All of this flows through a Radeon VE to my SGI 1600SW flat panel (DVI). When I was looking for a dvi card for my SGI 1600SW, I thought I read that the Radeon didn't official support that resolution; maybe the driver now supports the resolution limit on the card :-( Oh, and just to put every question in a single e-mail, thus making it difficult to find in mailing list archives, even in 24bpp, pixmaps appear to be 16bpp. My web page, for example, looks substantially different between my S3 based notebook in 24bpp and my Radeon VE based desktop in 24bpp. Is there a pixmap depth limitation in the radeon driver? That log file says that the config file requested 16bpp :-) It also says that it is using the DAC in 6bit mode, which would not help. -- Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge [EMAIL PROTECTED] http://www.dpmms.cam.ac.uk/~werdna ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]XFree86 CVS and 1600x1024 (DVI) / Radeon
I tried to send this a few days ago but it looks like it may not have made it (never saw it come back across the list), so I'll try again. Apologies if it actually made it. With the flurry of commits over the last few weeks, I figured it would be worth installing XFree86 CVS and check out RandR, Xcursor and the new ATI acceleration. Unfortunately, X comes up with a root window size of 1600x1024 (reported by xdpyinfo) but is really only outputting 1280x1024 (reported by my SGI MultiLink adapter). All of this flows through a Radeon VE to my SGI 1600SW flat panel (DVI). Any ideas? Oh, and just to put every question in a single e-mail, thus making it difficult to find in mailing list archives, even in 24bpp, pixmaps appear to be 16bpp. My web page, for example, looks substantially different between my S3 based notebook in 24bpp and my Radeon VE based desktop in 24bpp. Is there a pixmap depth limitation in the radeon driver? I've attached the usual XFree86 logs for completeness. Jeff This is a pre-release version of XFree86, and is not supported in any way. Bugs may be reported to [EMAIL PROTECTED] and patches submitted to [EMAIL PROTECTED] Before reporting bugs in pre-release versions, please check the latest version in the XFree86 CVS repository (http://www.XFree86.Org/cvs) XFree86 Version 4.2.99.1 / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 15 October 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: Linux 2.4.19-xfs i686 [ELF] 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/XFree86.0.log, Time: Thu Oct 17 23:48:57 2002 (==) Using config file: /etc/X11/XF86Config (==) ServerLayout Anaconda Configured (**) |--Screen Screen0 (0) (**) | |--Monitor Monitor0 (**) | |--Device ATI Radeon VE (**) |--Input Device Mouse0 (**) |--Input Device Keyboard0 (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc105 (**) XKB: model: pc105 (**) Option XkbLayout us (**) XKB: layout: us (==) Keyboard: CustomKeycode disabled (**) FontPath set to unix/:7100 (**) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6-CVS/lib/modules (--) using VT number 7 (II) Open APM successful (II) Module ABI versions: XFree86 ANSI C Emulation: 0.1 XFree86 Video Driver: 0.6 XFree86 XInput driver : 0.3 XFree86 Server Extension : 0.1 XFree86 Font Renderer : 0.3 (II) Loader running on linux (II) LoadModule: bitmap (II) Loading /usr/X11R6-CVS/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor=The XFree86 Project compiled for 4.2.99.1, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.3 (II) Loading font Bitmap (II) LoadModule: pcidata (II) Loading /usr/X11R6-CVS/lib/modules/libpcidata.a (II) Module pcidata: vendor=The XFree86 Project compiled for 4.2.99.1, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,1130 card 1043,8027 rev 02 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,1131 card , rev 02 class 06,04,00 hdr 01 (II) PCI: 00:1e:0: chip 8086,244e card , rev 01 class 06,04,00 hdr 01 (II) PCI: 00:1f:0: chip 8086,2440 card , rev 01 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,244b card 1043,8027 rev 01 class 01,01,80 hdr 00 (II) PCI: 00:1f:2: chip 8086,2442 card 1043,8027 rev 01 class 0c,03,00 hdr 00 (II) PCI: 00:1f:3: chip 8086,2443 card 1043,8027 rev 01 class 0c,05,00 hdr 00 (II) PCI: 00:1f:4: chip 8086,2444 card 1043,8027 rev 01 class 0c,03,00 hdr 00 (II) PCI: 01:00:0: chip 1002,5159 card 1002,013a rev 00 class 03,00,00 hdr 00 (II) PCI: 02:0a:0: chip 11ad,0002 card 1385,f004 rev 20 class 02,00,00 hdr 00 (II) PCI: 02:0c:0: chip 1274,5000 card 4942,4c4c rev 01 class 04,01,00 hdr 00 (II) PCI: End of PCI scan (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,2), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) PCI-to-PCI bridge: (II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 1 I/O range: [0] -1 0 0xd000 - 0xdfff (0x1000) IX[B] (II) Bus 1
[Xpert]XFree86 CVS and 1600x1024 (DVI) / Radeon
With the flurry of commits over the last few weeks, I figured it would be worth installing XFree86 CVS and check out RandR, Xcursor and the new ATI acceleration. Unfortunately, X comes up with a root window size of 1600x1024 (reported by xdpyinfo) but is really only outputting 1280x1024 (reported by my SGI MultiLink adapter). All of this flows through a Radeon VE to my SGI 1600SW flat panel. You can physically move windows off the visible screen, so the allocated root window is probably actually 1600x1024. I also manually defined the 1600x1024 modeline, which I grabbed from an old Mark V post in the archives, and XFree86 SEGV'd. Any ideas? I also noticed that xrandr died with BadParameter errors for anything other than changing the screen resolution. I'm guessing the ATI driver needs updating to handle the new extension. Oh, and just to put every question in a single e-mail, even in 24bpp, pixmaps appear to be 16bpp. My web page (in Mozilla), for example, looks substantially different between my S3 based notebook in 24bpp and my Radeon VE based desktop in 24bpp. Is there a pixmap depth limitation in the radeon driver? I've attached the usual XFree86 logs for completeness. Note that this is on RH8, gcc 3.2. Jeff This is a pre-release version of XFree86, and is not supported in any way. Bugs may be reported to [EMAIL PROTECTED] and patches submitted to [EMAIL PROTECTED] Before reporting bugs in pre-release versions, please check the latest version in the XFree86 CVS repository (http://www.XFree86.Org/cvs) XFree86 Version 4.2.99.1 / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 15 October 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: Linux 2.4.19-xfs i686 [ELF] 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/XFree86.0.log, Time: Thu Oct 17 23:48:57 2002 (==) Using config file: /etc/X11/XF86Config (==) ServerLayout Anaconda Configured (**) |--Screen Screen0 (0) (**) | |--Monitor Monitor0 (**) | |--Device ATI Radeon VE (**) |--Input Device Mouse0 (**) |--Input Device Keyboard0 (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc105 (**) XKB: model: pc105 (**) Option XkbLayout us (**) XKB: layout: us (==) Keyboard: CustomKeycode disabled (**) FontPath set to unix/:7100 (**) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6-CVS/lib/modules (--) using VT number 7 (II) Open APM successful (II) Module ABI versions: XFree86 ANSI C Emulation: 0.1 XFree86 Video Driver: 0.6 XFree86 XInput driver : 0.3 XFree86 Server Extension : 0.1 XFree86 Font Renderer : 0.3 (II) Loader running on linux (II) LoadModule: bitmap (II) Loading /usr/X11R6-CVS/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor=The XFree86 Project compiled for 4.2.99.1, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.3 (II) Loading font Bitmap (II) LoadModule: pcidata (II) Loading /usr/X11R6-CVS/lib/modules/libpcidata.a (II) Module pcidata: vendor=The XFree86 Project compiled for 4.2.99.1, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,1130 card 1043,8027 rev 02 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,1131 card , rev 02 class 06,04,00 hdr 01 (II) PCI: 00:1e:0: chip 8086,244e card , rev 01 class 06,04,00 hdr 01 (II) PCI: 00:1f:0: chip 8086,2440 card , rev 01 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,244b card 1043,8027 rev 01 class 01,01,80 hdr 00 (II) PCI: 00:1f:2: chip 8086,2442 card 1043,8027 rev 01 class 0c,03,00 hdr 00 (II) PCI: 00:1f:3: chip 8086,2443 card 1043,8027 rev 01 class 0c,05,00 hdr 00 (II) PCI: 00:1f:4: chip 8086,2444 card 1043,8027 rev 01 class 0c,03,00 hdr 00 (II) PCI: 01:00:0: chip 1002,5159 card 1002,013a rev 00 class 03,00,00 hdr 00 (II) PCI: 02:0a:0: chip 11ad,0002 card 1385,f004 rev 20 class 02,00,00 hdr 00 (II) PCI: 02:0c:0: chip 1274,5000 card 4942,4c4c rev 01 class 04,01,00 hdr 00 (II) PCI: End of PCI scan (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,2), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0
Re: [Xpert]XFree86 CVS and 1600x1024 (DVI) / Radeon
Around 10 o'clock on Oct 18, Jeff Brubaker wrote: Unfortunately, X comes up with a root window size of 1600x1024 (reported by xdpyinfo) but is really only outputting 1280x1024 (reported by my SGI MultiLink adapter). Hmm. The Radeon driver mode selection code was restructured during the RandR integration, it's quite possible that some mode lines aren't getting properly added. But, your log file seems to list 1600x1024 as a valid mode, so I'm a bit confused. What does 'xrandr' list as valid sizes? Any ideas? I also noticed that xrandr died with BadParameter errors for anything other than changing the screen resolution. I'm guessing the ATI driver needs updating to handle the new extension. The current RandR support in the core server is limited to size changes; rotation and reflection would have entailed some more invasive changes to the acceleration code that seemed inappropriate at this point in the release cycle. Oh, and just to put every question in a single e-mail, even in 24bpp, pixmaps appear to be 16bpp. The log you enclosed showed the screen running at 16bpp; I assume setting the depth to 24 switches that to 32bpp? Keith PackardXFree86 Core TeamHP Cambridge Research Lab ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
