RE: [Xpert]ATI Radeon 9000 Pro
Title: Message (just got the mail, XF86 server seems catching up some old stacks) the original ATI boards might be supported by the closed source DRI-drivers from ATI itselves. -Original Message-From: Craig Gallek [mailto:[EMAIL PROTECTED]]Sent: Thursday, October 03, 2002 07:58To: [EMAIL PROTECTED]Subject: [Xpert]ATI Radeon 9000 Pro Hello, I was thinking about scrapping Windows and converting to Linux. I found a thread on your web site that says you do not yet support the ATI Radeon 9000 Pro (which my computer uses). It also says that support will be added in the near future. I was just wondering how near the future is. Thanks, Craig Gallek
Re: [Xpert]ATI Radeon 9000
hy0 [EMAIL PROTECTED] writes: The patch for Radoen 9000, M9 and Radeon 9700 2D support has been submitted and will be in XFree CVS tree in the near future. Ok, waiting to see it (if this isn't a big problem for you please forward it to me, thanks). Meanwhile specifying ChipID in the config file with a 8500 or 7500 ID is a correct solution for getting 9000 or M9 to work with the existing X4.2xx Radoen dirver (2D part only, note this won't work with 9700). Finally got it working with cvs xfree after removing my ModeLine 1600x1024 (used on Rage128). :-))) Hope this helps Thanks! There is one funny thing. Modes 1600x1200 startx, and I'm getting 1600x1200 running fine. Now I'm adding Virtual 1600 1024 startx and... getting 1280x1024 :-) Anyway that's not important for me right now. -- Arkadiusz Mikiewicz niestety kloczek lubi by dyktatorem [EMAIL PROTECTED]AM2-6BONE, 1024/3DB19BBD, arekm(at)ircnet, PWr ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]ATI Radeon 9000
Vladimir Dergachev [EMAIL PROTECTED] writes: Try adding Option ChipId 0x4243 Hm, I don't see 0x4243 in xf86PciInfo.h but I've tried all these: #define PCI_CHIP_R200_BB0x4242 #define PCI_CHIP_R200_QL0x514C #define PCI_CHIP_R200_QN0x514E #define PCI_CHIP_R200_QO0x514F #define PCI_CHIP_R200_Ql0x516C Unfortunately I get only to (==) RADEON(0): Write-combining range (0xe400,0x400) Fatal server error: Caught signal 8. Server aborting Log from console: XFree86 Version 4.2.0 / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 11 March 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.2.20 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: Wed Sep 11 12:00:54 2002 (==) Using config file: /etc/X11/XF86Config (WW) RADEON: No matching Device section for instance (BusID PCI:1:0:1) found Fatal server error: Caught signal 8. Server aborting When reporting a problem related to a server crash, please send the full server output, not just the last messages. This can be found in the log file /var/log/XFree86.0.log. Please report problems to [EMAIL PROTECTED] Aborted (core dumped) --- And /var/log/XFree86.0.log XFree86 Version 4.2.0 / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 11 March 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.2.20 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: Wed Sep 11 12:01:47 2002 (==) Using config file: /etc/X11/XF86Config (==) ServerLayout XFree86 Configured (**) |--Screen Screen0 (0) (**) | |--Monitor Monitor0 (**) | |--Device Card0 (**) |--Input Device Mouse0 (**) |--Input Device Mouse1 (**) |--Input Device Keyboard0 (**) Option AutoRepeat 500 30 (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc104 (**) XKB: model: pc104 (**) Option XkbLayout pl (**) XKB: layout: pl (**) Option XkbOptions altwin:left_meta_win (**) XKB: options: altwin:left_meta_win (==) Keyboard: CustomKeycode disabled (**) FontPath set to unix/:7100 (==) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules (--) using VT number 11 (WW) Open APM failed (/dev/apm_bios) (No such file or directory) (II) Module ABI versions: XFree86 ANSI C Emulation: 0.1 XFree86 Video Driver: 0.5 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/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor=The XFree86 Project compiled for 4.2.0, 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/lib/modules/libpcidata.a (II) Module pcidata: vendor=The XFree86 Project compiled for 4.2.0, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.5 (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 1106,0305 card 147b,a401 rev 02 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 1106,8305 card , rev 00 class 06,04,00 hdr 01 (II) PCI: 00:07:0: chip 1106,0686 card 147b, rev 22 class 06,01,00 hdr 80 (II) PCI: 00:07:1: chip 1106,0571 card 1106,0571 rev 10 class 01,01,8a hdr 00 (II) PCI: 00:07:2: chip 1106,3038 card 0925,1234 rev 10 class 0c,03,00 hdr 00 (II) PCI: 00:07:3: chip 1106,3038 card 0925,1234 rev 10 class 0c,03,00 hdr 00 (II) PCI: 00:07:4: chip 1106,3057 card 1106,3057 rev 30 class 06,80,00 hdr 00 (II) PCI: 00:09:0: chip 109e,036e card , rev 11 class 04,00,00 hdr 80 (II) PCI: 00:09:1: chip 109e,0878 card , rev 11 class 04,80,00 hdr 80 (II) PCI: 00:0b:0: chip 105a,4d68 card 105a,4d68 rev 01 class 01,80,85 hdr 00 (II) PCI: 00:0d:0: chip 10b7,9200 card 10b7,1000 rev 6c class 02,00,00 hdr 00 (II) PCI: 00:0f:0: chip 104c,ac50 card
Re: [Xpert]ATI Radeon 9000
Charl P. Botha [EMAIL PROTECTED] writes: That's probably the reason WHY you should try ChipId 0x4243. Weird. I thought that by using ChipID someid (like 0x4242) I'm telling XFree: hey, this device is XYZ (Radeon 8500 BB for 0x4242), belive me and don't autodetect. What 0x4243 is supposed to mean? pci bus 0x0001 cardnum 0x00 function 0x00: vendor 0x1002 device 0x4966 ATI Device unknown pci bus 0x0001 cardnum 0x00 function 0x01: vendor 0x1002 device 0x496e ATI Device unknown Anyway here it is: Section Device Identifier Card0 Driver radeon VendorName ATI BoardName Radeon 9000 Option ChipID 0x4243 # ChipID 0x4242 EndSection and [...] (II) Primary Device is: PCI 01:00:0 (--) Assigning device section with no busID to primary device (WW) RADEON: No matching Device section for instance (BusID PCI:1:0:1) found (EE) No devices detected. Fatal server error: no screens found charl p. botha http://cpbotha.net/ http://visualisation.tudelft.nl/ -- Arkadiusz Mikiewicz niestety kloczek lubi by dyktatorem [EMAIL PROTECTED]AM2-6BONE, 1024/3DB19BBD, arekm(at)ircnet, PWr ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]ATI Radeon 9000
On 11 Sep 2002, Arkadiusz Miskiewicz wrote: Charl P. Botha [EMAIL PROTECTED] writes: That's probably the reason WHY you should try ChipId 0x4243. Weird. I thought that by using ChipID someid (like 0x4242) I'm telling XFree: hey, this device is XYZ (Radeon 8500 BB for 0x4242), belive me and don't autodetect. What 0x4243 is supposed to mean? It's a pci id of AIW Radeon 8500 DV. Perhaps it has not made into linux kernel yet. Also try this: Option ChipId 0x4243 If still does not work try ati.2 drivers from http://gatos.sf.net/ Vladimir Dergachev pci bus 0x0001 cardnum 0x00 function 0x00: vendor 0x1002 device 0x4966 ATI Device unknown pci bus 0x0001 cardnum 0x00 function 0x01: vendor 0x1002 device 0x496e ATI Device unknown Anyway here it is: Section Device Identifier Card0 Driver radeon VendorName ATI BoardName Radeon 9000 Option ChipID 0x4243 # ChipID 0x4242 EndSection and [...] (II) Primary Device is: PCI 01:00:0 (--) Assigning device section with no busID to primary device (WW) RADEON: No matching Device section for instance (BusID PCI:1:0:1) found (EE) No devices detected. Fatal server error: no screens found charl p. botha http://cpbotha.net/ http://visualisation.tudelft.nl/ -- Arkadiusz Mi¶kiewicz niestety kloczek lubi byæ dyktatorem [EMAIL PROTECTED]AM2-6BONE, 1024/3DB19BBD, arekm(at)ircnet, PWr ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]ATI Radeon 9000
On Wed, Sep 11, 2002 at 02:19:01PM +0200, Arkadiusz Miskiewicz wrote: Charl P. Botha [EMAIL PROTECTED] writes: That's probably the reason WHY you should try ChipId 0x4243. Weird. I thought that by using ChipID someid (like 0x4242) I'm telling XFree: hey, this device is XYZ (Radeon 8500 BB for 0x4242), belive me and don't autodetect. What 0x4243 is supposed to mean? pci bus 0x0001 cardnum 0x00 function 0x00: vendor 0x1002 device 0x4966 ATI Device unknown pci bus 0x0001 cardnum 0x00 function 0x01: vendor 0x1002 device 0x496e ATI Device unknown Aaah, I didn't read your first email. Have you tried: ChipId 0x4966 in the Device section? It will connect that device section to the unknown ATI device, which is of course your ATI video card, which should at least eliminate the RADEON: No matching device section for ... -- charl p. botha http://cpbotha.net/ http://visualisation.tudelft.nl/ ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]ATI Radeon 9000
On Wed, Sep 11, 2002 at 02:19:01PM +0200, Arkadiusz Miskiewicz wrote: Charl P. Botha [EMAIL PROTECTED] writes: That's probably the reason WHY you should try ChipId 0x4243. Weird. I thought that by using ChipID someid (like 0x4242) I'm telling XFree: hey, this device is XYZ (Radeon 8500 BB for 0x4242), belive me and don't autodetect. Ugh, my apologies. You are completely correct... I misunderstood the ChipId documentation. -- charl p. botha http://cpbotha.net/ http://visualisation.tudelft.nl/ ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]ATI Radeon 9000
Vladimir Dergachev [EMAIL PROTECTED] writes: What 0x4243 is supposed to mean? It's a pci id of AIW Radeon 8500 DV. So another unsupported one. Perhaps it has not made into linux kernel yet. kernel? support in kernel is required for DRI. I'm trying to get XFree working even without DRI. Also try this: Option ChipId 0x4243 XFree drivers do not support 0x4243. It will not work. If still does not work try ati.2 drivers from http://gatos.sf.net/ gatos drivers also don't support 0x4243 (don't support my radeon, too) Vladimir Dergachev btw. how PCI IDs are managed? Vendor (like ATI) gets some ID space (as in with MAC on network cards) and does whathever it wants in that assigned space? Or maybe vendor is required to register each product in some global database? ps. response from ati support sucks, automated message ;/ -- Arkadiusz Mikiewicz niestety kloczek lubi by dyktatorem [EMAIL PROTECTED]AM2-6BONE, 1024/3DB19BBD, arekm(at)ircnet, PWr ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]ATI Radeon 9000
Arkadiusz Miskiewicz [EMAIL PROTECTED] writes: Unfortunately current radeon drivers does not have PCI ID of this card (afaik even in xfree cvs). Just tried today cvs version of xfree from HEAD. With overriding ChipID 0x4242 got X running but there is one problem reading/localizing BIOS (II) RADEON(0): initializing int10 (WW) RADEON(0): Bad V_BIOS checksum (II) RADEON(0): Primary V_BIOS segment is: 0xc000 and second problem with ,,out of scan range'' problaby due to BIOS problem (my monitor turned screen off). 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: 7 June 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 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: Wed Sep 11 19:44:14 2002 (==) Using config file: /etc/X11/XF86Config (==) ServerLayout XFree86 Configured (**) |--Screen Screen0 (0) (**) | |--Monitor Monitor0 (**) | |--Device Card0 (**) |--Input Device Mouse0 (**) |--Input Device Mouse1 (**) |--Input Device Keyboard0 (**) Option AutoRepeat 500 30 (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc104 (**) XKB: model: pc104 (**) Option XkbLayout pl (**) XKB: layout: pl (**) Option XkbOptions altwin:left_meta_win (**) XKB: options: altwin:left_meta_win (==) Keyboard: CustomKeycode disabled (**) FontPath set to unix/:7100 (==) RgbPath set to /mnt/storage1/misiek/xfree/lib/X11/rgb (==) ModulePath set to /mnt/storage1/misiek/xfree/lib/modules (--) using VT number 11 (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 /mnt/storage1/misiek/xfree/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 /mnt/storage1/misiek/xfree/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 1106,0305 card 147b,a401 rev 02 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 1106,8305 card , rev 00 class 06,04,00 hdr 01 (II) PCI: 00:07:0: chip 1106,0686 card 147b, rev 22 class 06,01,00 hdr 80 (II) PCI: 00:07:1: chip 1106,0571 card 1106,0571 rev 10 class 01,01,8a hdr 00 (II) PCI: 00:07:2: chip 1106,3038 card 0925,1234 rev 10 class 0c,03,00 hdr 00 (II) PCI: 00:07:3: chip 1106,3038 card 0925,1234 rev 10 class 0c,03,00 hdr 00 (II) PCI: 00:07:4: chip 1106,3057 card 1106,3057 rev 30 class 06,80,00 hdr 00 (II) PCI: 00:09:0: chip 109e,036e card , rev 11 class 04,00,00 hdr 80 (II) PCI: 00:09:1: chip 109e,0878 card , rev 11 class 04,80,00 hdr 80 (II) PCI: 00:0b:0: chip 105a,4d68 card 105a,4d68 rev 01 class 01,80,85 hdr 00 (II) PCI: 00:0d:0: chip 10b7,9200 card 10b7,1000 rev 6c class 02,00,00 hdr 00 (II) PCI: 00:0f:0: chip 104c,ac50 card d400, rev 01 class 06,07,00 hdr 02 (II) PCI: 00:11:0: chip 1102,0002 card 1102,8064 rev 07 class 04,01,00 hdr 80 (II) PCI: 00:11:1: chip 1102,7002 card 1102,0020 rev 07 class 09,80,00 hdr 80 (II) PCI: 01:00:0: chip 1002,4966 card 174b,7197 rev 01 class 03,00,00 hdr 80 (II) PCI: 01:00:1: chip 1002,496e card 174b,7196 rev 01 class 03,80,00 hdr 00 (II) PCI: End of PCI scan (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (-1,0,0), BCTRL: 0x08 (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: 0x0c (VGA_EN is set) (II) Bus 1 I/O
RE: [Xpert]ATI Radeon 9000
Title: RE: [Xpert]ATI Radeon 9000 Hello, What 0x4243 is supposed to mean? It's a pci id of AIW Radeon 8500 DV. So another unsupported one. No, according to the PCI ID database on www.yourvote.com 0x4243 the piggy back firewire port of the 8500 DV. This is indeed not a grafics chip at all. Who the heck has come up with that bogus ID? In the PCI device listing you will clearly find the correct ID of this ATI Radeon 9000 card: 0x4966 Charl is finally most right with his proposal: ChipId 0x4966 (i dont use that because when i am developing i am always having a full X11 tree handy and then i just add the IDs directly into my code, a few seconds recompile of the ddx driver module and its done...) you had two IDs in your specific case, thats why: only primary function 0 does identify the chip, any further device functions only do have different IDs if they do provide something different with the same silicon, a thing that is often seen on intel's bus bridges. Perhaps it has not made into linux kernel yet. kernel? support in kernel is required for DRI. I'm trying to get XFree working even without DRI. The write meant something different - the coding of DRI partially is kernel based and uses the constant defines from linux kernel header files (which do originate from the yourvote.com site). As the Radeon 9000 is a pretty new board the Linux kernel is possibly just updating this, but the DRI project hasnt identified this addition. Thats a development thing users should not care to much. For users there is just the method of browsing their pci configuration and add the yet not known compatible devices to their config file by the ChipID statement. Also try this: Option ChipId 0x4243 XFree drivers do not support 0x4243. It will not work. that boy was hoaxing with his suggestion or using the FAQ template? If still does not work try ati.2 drivers from http://gatos.sf.net/ gatos drivers also don't support 0x4243 (don't support my radeon, too) must be the same boy as above btw. how PCI IDs are managed? Vendor (like ATI) gets some ID space (as in with MAC on network cards) and does whathever it wants in that assigned space? Or maybe vendor is required to register each product in some global database? There is an organsiation called PCI Special Interests Group (www.pcisig.com) that does work on specs. Its a big business club. And it registers the misc companys with a vendor ID. The device IDs are in the duty of the respective vendors. Each of these IDs is 16 bits wide. If you use up 50 device IDs a year, you will have mor than 1000 years of time until you have to register for a secondary vendor ID. ps. response from ati support sucks, automated message ;/ hmm. that means customer support got your mail. ;-) anyways X11-DRI drivers are supported by their respective vendors. -Alex.
Re: [Xpert]ATI Radeon 9000
Hi, The patch for Radoen 9000, M9 and Radeon 9700 2D support has been submitted and will be in XFree CVS tree in the near future. 9000 and 8500 don't share the same IDs, that's for sure. Meanwhile specifying ChipID in the config file with a 8500 or 7500 ID is a correct solution for getting 9000 or M9 to work with the existing X4.2xx Radoen dirver (2D part only, note this won't work with 9700). If you specify ChipID with a 8500 ID (0x4242 for example), it will only work with the single head config. If you want both heads to work correctly with a dual-head/Xinerama setup, use a 7500 (0x5157) or a VE ID (0x5159 for example). Although 9000 uses the same 3D core as used in 8500, its 2D features (dual-head, tvout, etc) actually follow 7500. When you use a 7500 or VE ID, make sure to disable DRI. Although the 2D part of radeon DRI support is likely to work fine with radeon.o kernel driver on a 9000 (this is because the 2D DRI support only uses DMA to send 2D commands, doesn't even use the microcode for 2D commands), any ogl app (like ogl screen savers) will lock whole thing up if DRI is enabled. The failure experienced by Arkadiusz in http://www.xfree86.org/pipermail/xpert/2002-September/020561.html is probably caused by the bug with DDA rountines in the old X4.20 driver, this has been discussed before and has been fixed in XFree CVS tree. Hope this helps Hui I recently recieved a Radeon 9000pro mac edition and hacked it to work by just adding the PCI id as stated in other posts (but in the driver this time), this cards ID is 0x4966. Is it true that there are 9000's with 8500 ID's? ani On Wed, 11 Sep 2002, Alexander Stohr wrote: Hello, What 0x4243 is supposed to mean? It's a pci id of AIW Radeon 8500 DV. So another unsupported one. No, according to the PCI ID database on www.yourvote.com 0x4243 the piggy back firewire port of the 8500 DV. This is indeed not a grafics chip at all. Who the heck has come up with that bogus ID? In the PCI device listing you will clearly find the correct ID of this ATI Radeon 9000 card: 0x4966 Charl is finally most right with his proposal: ChipId 0x4966 (i dont use that because when i am developing i am always having a full X11 tree handy and then i just add the IDs directly into my code, a few seconds recompile of the ddx driver module and its done...) you had two IDs in your specific case, thats why: only primary function 0 does identify the chip, any further device functions only do have different IDs if they do provide something different with the same silicon, a thing that is often seen on intel's bus bridges. Perhaps it has not made into linux kernel yet. kernel? support in kernel is required for DRI. I'm trying to get XFree working even without DRI. The write meant something different - the coding of DRI partially is kernel based and uses the constant defines from linux kernel header files (which do originate from the yourvote.com site). As the Radeon 9000 is a pretty new board the Linux kernel is possibly just updating this, but the DRI project hasnt identified this addition. Thats a development thing users should not care to much. For users there is just the method of browsing their pci configuration and add the yet not known compatible devices to their config file by the ChipID statement. Also try this: Option ChipId 0x4243 XFree drivers do not support 0x4243. It will not work. that boy was hoaxing with his suggestion or using the FAQ template? If still does not work try ati.2 drivers from http://gatos.sf.net/ gatos drivers also don't support 0x4243 (don't support my radeon, too) must be the same boy as above btw. how PCI IDs are managed? Vendor (like ATI) gets some ID space (as in with MAC on network cards) and does whathever it wants in that assigned space? Or maybe vendor is required to register each product in some global database? There is an organsiation called PCI Special Interests Group (www.pcisig.com) that does work on specs. Its a big business club. And it registers the misc companys with a vendor ID. The device IDs are in the duty of the respective vendors. Each of these IDs is 16 bits wide. If you use up 50 device IDs a year, you will have mor than 1000 years of time until you have to register for a secondary vendor ID. ps. response from ati support sucks, automated message ;/ hmm. that means customer support got your mail. ;-) anyways X11-DRI drivers are supported by their respective vendors. -Alex. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]ATI Radeon 9000
Try adding Option ChipId 0x4243 To the device section of /etc/XF86Config Vladimir Dergachev On 10 Sep 2002, Arkadiusz Miskiewicz wrote: Hi, I have ATI Radeon 9000 Powered by ATI (made by Sapphire). It has only analog (monitor) and s-video output, no dvi, 64M of RAM. Unfortunately current radeon drivers does not have PCI ID of this card (afaik even in xfree cvs). How can I force radeon driver to service this card (hope it will work)? Here is lspci output: 01:00.0 VGA compatible controller: ATI Technologies Inc: Unknown device 4966 (rev 01) (prog-if 00 [VGA]) Subsystem: Unknown device 174b:7197 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 32 (2000ns min), cache line size 08 Interrupt: pin A routed to IRQ 9 Region 0: Memory at e400 (32-bit, prefetchable) [size=64M] Region 1: I/O ports at a000 [size=256] Region 2: Memory at ed00 (32-bit, non-prefetchable) [size=64K] Expansion ROM at unassigned [disabled] [size=128K] Capabilities: [58] AGP version 2.0 Status: RQ=47 SBA+ 64bit- FW+ Rate=x1,x2 Command: RQ=0 SBA+ AGP- 64bit- FW- Rate=none Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 01:00.1 Display controller: ATI Technologies Inc: Unknown device 496e (rev 01) Subsystem: Unknown device 174b:7196 Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 32 (2000ns min), cache line size 08 Region 0: Memory at e800 (32-bit, prefetchable) [disabled] [size=64M] Region 1: Memory at ed01 (32-bit, non-prefetchable) [disabled] [size=64K] Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Here is full scanpci output: pci bus 0x cardnum 0x00 function 0x00: vendor 0x1106 device 0x0305 VIA Technologies, Inc. VT8363/8365 [KT133/KM133] CardVendor 0x147b card 0xa401 (ABIT Computer Corp. KT7/KT7-RAID/KT7A/KT7A-RAID Mainboard) STATUS0x2210 COMMAND 0x0006 CLASS 0x06 0x00 0x00 REVISION 0x02 BIST 0x00 HEADER 0x00 LATENCY 0x08 CACHE 0x00 BASE0 0xe008 addr 0xe000 MEM PREFETCHABLE pci bus 0x cardnum 0x01 function 0x00: vendor 0x1106 device 0x8305 VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP] STATUS0x2230 COMMAND 0x0007 CLASS 0x06 0x04 0x00 REVISION 0x00 HEADER0x01 LATENCY 0x00 PRIBUS0x00 SECBUS 0x01 SUBBUS 0x01 SECLT 0x00 IOBASE0xa000 IOLIM 0xafff SECSTATUS 0x NOPREFETCH_MEMBASE 0xec00 MEMLIM 0xedff PREFETCH_MEMBASE 0xe400 MEMLIM 0xebff NO_FAST_B2B NO_SEC_BUS_RST NO_M_ABRT VGA_EN ISA_EN NO_SERR_EN NO_PERR_EN pci bus 0x cardnum 0x07 function 0x00: vendor 0x1106 device 0x0686 VIA Technologies, Inc. VT82C686 [Apollo Super South] CardVendor 0x147b card 0x (ABIT Computer Corp., Card unknown) STATUS0x0210 COMMAND 0x0087 CLASS 0x06 0x01 0x00 REVISION 0x22 BIST 0x00 HEADER 0x80 LATENCY 0x00 CACHE 0x00 BYTE_00x108 BYTE_1 0x00 BYTE_2 0x00 BYTE_3 0x00 pci bus 0x cardnum 0x07 function 0x01: vendor 0x1106 device 0x0571 VIA Technologies, Inc. Bus Master IDE CardVendor 0x1106 card 0x0571 (VIA Technologies, Inc., Card unknown) STATUS0x0290 COMMAND 0x0007 CLASS 0x01 0x01 0x8a REVISION 0x10 BIST 0x00 HEADER 0x00 LATENCY 0x20 CACHE 0x00 BASE4 0xb001 addr 0xb000 I/O MAX_LAT 0x00 MIN_GNT 0x00 INT_PIN 0x00 INT_LINE 0xff BYTE_00x3a08e203 BYTE_1 0x00 BYTE_2 0x8099858 BYTE_3 0x pci bus 0x cardnum 0x07 function 0x02: vendor 0x1106 device 0x3038 VIA Technologies, Inc. USB CardVendor 0x0925 card 0x1234 (VIA Technologies, Inc. (Wrong ID) USB Controller) STATUS0x0210 COMMAND 0x0007 CLASS 0x0c 0x03 0x00 REVISION 0x10 BIST 0x00 HEADER 0x00 LATENCY 0x20 CACHE 0x08 BASE4 0xb401 addr 0xb400 I/O MAX_LAT 0x00 MIN_GNT 0x00 INT_PIN 0x04 INT_LINE 0x0b BYTE_00x31000 BYTE_1 0x00 BYTE_2 0x8099bd0 BYTE_3 0x pci bus 0x cardnum 0x07 function 0x03: vendor 0x1106 device 0x3038 VIA Technologies, Inc. USB CardVendor 0x0925 card 0x1234 (VIA Technologies, Inc. (Wrong ID) USB Controller) STATUS0x0210 COMMAND 0x0007 CLASS 0x0c 0x03 0x00 REVISION 0x10 BIST
