Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in

  FAQ | Search | Memberlist | Usergroups | Statistics | Profile | Log in to check your private messages | Log in | Register

[ATI,AIGLX,DRI] Screen 0 is not DRI capable
 View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2  
Reply to topic    Gentoo Forums Forum Index French
View previous topic :: View next topic  
Author Message
_droop_
l33t
l33t


Joined: 30 May 2004
Posts: 957
PostPosted: Tue Nov 21, 2006 12:48 pm    Post subject: Reply with quote
J'avais pas vu ton dmesg. Effectivement, le drm de ton noyau a l'air vieux.

Si tu n'as pas envie de changer de versions noyau :
- décharges les modules radeon et drm
- désactive le dri du noyau.
- recompiles et réinstalles les modules
- installe x11-drm.
Sinon tu peux installer un noyau récent (2.6.17; 2.6.18 ) et utiliser les drm du noyau.

Si tu utilises ceux du noyau, c'est un peu plus simples pour les mises à jour (pas besoin de faire un 'emerge --oneshot x11-drm' à chaque mise à jour). Par contre tu dois choisir des versions de noyau 'compatible' avec Xorg (pas trop vieux).

Personnellement, j'utilise x11-drm. Au final ca change pas grand chose.

Last edited by _droop_ on Tue Nov 21, 2006 12:54 pm; edited 1 time in total
Back to top
View user's profile Send private message
pathfinder
l33t
l33t


Joined: 19 Jan 2006
Posts: 731
Location: Barcelona, Spain
PostPosted: Tue Nov 21, 2006 12:53 pm    Post subject: Reply with quote
_droop_ wrote:
Je te le fais de mémoire, j'éspère ne pas être trop loin sur les noms de variables

1/ dans /etc/make.conf, tu mets VIDEO_CARDS="radeon". Ce que tu sembles avoir fait vu qu'il t as installe xf86-video-ati (qui contient les driver radeon r200 et r300).

2/ Dans le noyau, il faut ajouter Device Driver -> Direct Rendering Interface -> radeon. Si tu as un noyau ancien (<2.6.16), il faut installer x11-drm.

3/ Dans le xorg.conf, tu met driver "radeon" à la section device. Dans la section module, il faut "load dri" et "load glx". Il faut ajouter une section pour DRI.

edit : Un peu plus de détail sur le how to dri gentoo



le noayu 2.6.18: tu parles bien de ceci?
Quote:
Symbol: DRM_RADEON [=m] x
x Prompt: ATI Radeon x
x Defined at drivers/char/drm/Kconfig:34 x
x Depends on: DRM && PCI x
x Location: x
x -> Device Drivers x
x -> Character devices x
x -> Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) (DRM [=m])


je l ai deja en module de cette meme facon sur mon 2.6.15

c est autre chose?
Back to top
View user's profile Send private message
_droop_
l33t
l33t


Joined: 30 May 2004
Posts: 957
PostPosted: Tue Nov 21, 2006 12:58 pm    Post subject: Reply with quote
pathfinder wrote:
le noayu 2.6.18: tu parles bien de ceci?
Quote:
Symbol: DRM_RADEON [=m] x
x Prompt: ATI Radeon x
x Defined at drivers/char/drm/Kconfig:34 x
x Depends on: DRM && PCI x
x Location: x
x -> Device Drivers x
x -> Character devices x
x -> Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) (DRM [=m])


Oui,

Il faudrait que je vérifie mais il me semble que pour Xorg 7.1, il faut avoir au moins le noyau 2.6.17 pour avoir la bonne version de DRM. Ce qui expliquerait que ca ne fonctionne pas avec ton 2.6.15.
Back to top
View user's profile Send private message
pathfinder
l33t
l33t


Joined: 19 Jan 2006
Posts: 731
Location: Barcelona, Spain
PostPosted: Tue Nov 28, 2006 5:22 pm    Post subject: Reply with quote
bon je suis passé au 2.6.18-r3 sans trop de mal
emerge les x11-drm et ati:
Quote:
atlantis # emerge -1 xf86-video-ati x11-drm

et au passage je charge les modules
Quote:
drm
intel-agp
i915
agpgart
radeon


i915 pourqoi pas....
reboote (pour voir un peu si le nouveau kernel est mieux)


Et en effet il y a un mieux:
beryl en .xinitrc ne plante plus (ECRAN BLANC TOUBLAN)
beryl depuis gnome crashe toujours (meme si ecran blanc tout de meme)

voila quelques outputs:
Quote:
Linux agpgart interface v0.101 (c) Dave Jones
agpgart: Detected an Intel 915G Chipset. (je savais pas que j avais de l agp)
agpgart: AGP aperture is 256M @ 0x0
ACPI: PCI Interrupt 0000:00:1f.3[B] -> GSI 19 (level, low) -> IRQ 19
[drm] Initialized drm 1.0.1 20051102
ACPI: PCI Interrupt 0000:04:00.0[A] -> GSI 16 (level, low) -> IRQ 16
[drm] Initialized radeon 1.25.0 20060524 on minor 0
kjournald starting. Commit interval 5 seconds
EXT3 FS on sda5, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
Adding 1959920k swap on /dev/sda3. Priority:-1 extents:1 across:1959920k
sky2 eth0: enabling interface
sky2 eth0: Link is up at 100 Mbps, full duplex, flow control both
mtrr: 0xd8000000,0x8000000 overlaps existing 0xd8000000,0x1000000
mtrr: 0xd8000000,0x8000000 overlaps existing 0xd8000000,0x1000000 EST CE UN MESSAGE D ERREUR???
[drm] Setting GART location based on new memory map
[drm:radeon_do_init_cp] *ERROR* Cannot use PCI Express without GART in FB memory ET DONC?
[drm] Setting GART location based on new memory map
[drm:radeon_do_init_cp] *ERROR* Cannot use PCI Express without GART in FB memory
[drm] Setting GART location based on new memory map
[drm:radeon_do_init_cp] *ERROR* Cannot use PCI Express without GART in FB memory
[drm] Setting GART location based on new memory map
[drm:radeon_do_init_cp] *ERROR* Cannot use PCI Express without GART in FB memory
[drm] Setting GART location based on new memory map
[drm:radeon_do_init_cp] *ERROR* Cannot use PCI Express without GART in FB memory
[drm] Setting GART location based on new memory map
[drm:radeon_do_init_cp] *ERROR* Cannot use PCI Express without GART in FB memory
[drm] Setting GART location based on new memory map
[drm:radeon_do_init_cp] *ERROR* Cannot use PCI Express without GART in FB memory
[drm] Setting GART location based on new memory map
[drm:radeon_do_init_cp] *ERROR* Cannot use PCI Express without GART in FB memory



Quote:
$ cat /var/log/Xorg.0.log | grep -i WW
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(WW) RADEON: No matching Device section for instance (BusID PCI:4:0:1) found
(WW) RADEON(0): Failed to detect secondary monitor, MergedFB/Clone mode disabled
(WW) (1152x864,Mitsubishi Diamond Scan) mode clock 108MHz exceeds DDC maximum 100MHz
(WW) (1280x960,Mitsubishi Diamond Scan) mode clock 108MHz exceeds DDC maximum 100MHz
(WW) (1280x960,Mitsubishi Diamond Scan) mode clock 148.5MHz exceeds DDC maximum 100MHz
(WW) (1280x1024,Mitsubishi Diamond Scan) mode clock 108MHz exceeds DDC maximum 100MHz
(WW) (1280x1024,Mitsubishi Diamond Scan) mode clock 135MHz exceeds DDC maximum 100MHz
(WW) (1280x1024,Mitsubishi Diamond Scan) mode clock 157.5MHz exceeds DDC maximum 100MHz
(WW) (1600x1200,Mitsubishi Diamond Scan) mode clock 162MHz exceeds DDC maximum 100MHz
(WW) (1600x1200,Mitsubishi Diamond Scan) mode clock 175.5MHz exceeds DDC maximum 100MHz
(WW) (1600x1200,Mitsubishi Diamond Scan) mode clock 189MHz exceeds DDC maximum 100MHz
(WW) (1600x1200,Mitsubishi Diamond Scan) mode clock 202.5MHz exceeds DDC maximum 100MHz
(WW) (1600x1200,Mitsubishi Diamond Scan) mode clock 229.5MHz exceeds DDC maximum 100MHz
(WW) (1792x1344,Mitsubishi Diamond Scan) mode clock 204.8MHz exceeds DDC maximum 100MHz
(WW) (1792x1344,Mitsubishi Diamond Scan) mode clock 261MHz exceeds DDC maximum 100MHz
(WW) (1856x1392,Mitsubishi Diamond Scan) mode clock 218.3MHz exceeds DDC maximum 100MHz
(WW) (1856x1392,Mitsubishi Diamond Scan) mode clock 288MHz exceeds DDC maximum 100MHz
(WW) (1920x1440,Mitsubishi Diamond Scan) mode clock 234MHz exceeds DDC maximum 100MHz
(WW) (1920x1440,Mitsubishi Diamond Scan) mode clock 297MHz exceeds DDC maximum 100MHz
(WW) (1400x1050,Mitsubishi Diamond Scan) mode clock 122MHz exceeds DDC maximum 100MHz
(WW) (1400x1050,Mitsubishi Diamond Scan) mode clock 155.8MHz exceeds DDC maximum 100MHz
(WW) (1600x1024,Mitsubishi Diamond Scan) mode clock 106.91MHz exceeds DDC maximum 100MHz
(WW) (1920x1440,Mitsubishi Diamond Scan) mode clock 341.35MHz exceeds DDC maximum 100MHz
(WW) (2048x1536,Mitsubishi Diamond Scan) mode clock 266.95MHz exceeds DDC maximum 100MHz
(WW) (2048x1536,Mitsubishi Diamond Scan) mode clock 340.48MHz exceeds DDC maximum 100MHz
(WW) (2048x1536,Mitsubishi Diamond Scan) mode clock 388.04MHz exceeds DDC maximum 100MHz
(WW) RADEON(0): Direct rendering disabled
(WW) RADEON(0): Option "DRI" is not used
(WW) RADEON(0): Option "AllowGLXWithComposite" is not used
(WW) RADEON(0): Option "ExaNoOffscreenPixmaps" is not used


Quote:
$ cat /var/log/Xorg.0.log | grep -i EE
Current Operating System: Linux atlantis 2.6.18-gentoo-r3 #1 SMP PREEMPT Tue Nov 28 18:36:54 CET 2006 i686
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(**) |-->Screen "Screen 1" (0)
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-Misc
(II) LoadModule: "freetype"
(II) Loading /usr/lib/xorg/modules/fonts/libfreetype.so
(II) Module freetype: vendor="X.Org Foundation & the After X-TT Project"
(II) Loading font FreeType
(II) Loading extension XFree86-DRI
(II) Setting vga for screen 0.
(==) RADEON(0): X server will not keep DPI constant for all screen sizes
(II) RADEON(0): Year: 1999 Week: 37
(II) RADEON(0): redX: 0.620 redY: 0.334 greenX: 0.289 greenY: 0.595
(WW) (1152x864,Mitsubishi Diamond Scan) mode clock 108MHz exceeds DDC maximum 100MHz
(WW) (1280x960,Mitsubishi Diamond Scan) mode clock 108MHz exceeds DDC maximum 100MHz
(WW) (1280x960,Mitsubishi Diamond Scan) mode clock 148.5MHz exceeds DDC maximum 100MHz
(WW) (1280x1024,Mitsubishi Diamond Scan) mode clock 108MHz exceeds DDC maximum 100MHz
(WW) (1280x1024,Mitsubishi Diamond Scan) mode clock 135MHz exceeds DDC maximum 100MHz
(WW) (1280x1024,Mitsubishi Diamond Scan) mode clock 157.5MHz exceeds DDC maximum 100MHz
(WW) (1600x1200,Mitsubishi Diamond Scan) mode clock 162MHz exceeds DDC maximum 100MHz
(WW) (1600x1200,Mitsubishi Diamond Scan) mode clock 175.5MHz exceeds DDC maximum 100MHz
(WW) (1600x1200,Mitsubishi Diamond Scan) mode clock 189MHz exceeds DDC maximum 100MHz
(WW) (1600x1200,Mitsubishi Diamond Scan) mode clock 202.5MHz exceeds DDC maximum 100MHz
(WW) (1600x1200,Mitsubishi Diamond Scan) mode clock 229.5MHz exceeds DDC maximum 100MHz
(WW) (1792x1344,Mitsubishi Diamond Scan) mode clock 204.8MHz exceeds DDC maximum 100MHz
(WW) (1792x1344,Mitsubishi Diamond Scan) mode clock 261MHz exceeds DDC maximum 100MHz
(WW) (1856x1392,Mitsubishi Diamond Scan) mode clock 218.3MHz exceeds DDC maximum 100MHz
(WW) (1856x1392,Mitsubishi Diamond Scan) mode clock 288MHz exceeds DDC maximum 100MHz
(WW) (1920x1440,Mitsubishi Diamond Scan) mode clock 234MHz exceeds DDC maximum 100MHz
(WW) (1920x1440,Mitsubishi Diamond Scan) mode clock 297MHz exceeds DDC maximum 100MHz
(WW) (1400x1050,Mitsubishi Diamond Scan) mode clock 122MHz exceeds DDC maximum 100MHz
(WW) (1400x1050,Mitsubishi Diamond Scan) mode clock 155.8MHz exceeds DDC maximum 100MHz
(WW) (1600x1024,Mitsubishi Diamond Scan) mode clock 106.91MHz exceeds DDC maximum 100MHz
(WW) (1920x1440,Mitsubishi Diamond Scan) mode clock 341.35MHz exceeds DDC maximum 100MHz
(WW) (2048x1536,Mitsubishi Diamond Scan) mode clock 266.95MHz exceeds DDC maximum 100MHz
(WW) (2048x1536,Mitsubishi Diamond Scan) mode clock 340.48MHz exceeds DDC maximum 100MHz
(WW) (2048x1536,Mitsubishi Diamond Scan) mode clock 388.04MHz exceeds DDC maximum 100MHz
of this adapter, please see http://gatos.sf.net.
(II) do I need RAC? No, I don't.
(**) RADEON(0): RADEONScreenInit d8000000 0
(**) RADEON(0): RADEONSaveScreen(0)
(II) RADEON(0): Largest offscreen area available: 1280 x 7165
(**) RADEON(0): RADEONDRICloseScreen
(**) RADEON(0): Option "XaaNoOffscreenPixmaps" "true"
(II) RADEON(0): Using XFree86 Acceleration Architecture (XAA)
Screen to screen bit blits
Indirect CPU to Screen color expansion
(II) RADEON(0): Largest offscreen area available: 1280 x 7161
(WW) RADEON(0): Option "ExaNoOffscreenPixmaps" is not used
(**) RADEON(0): RADEONScreenInit finished
(II) Initializing built-in extension XFree86-Bigfont
(EE) AIGLX: Screen 0 is not DRI capable
(II) GLX: Initialized MESA-PROXY GL provider for screen 0
xkb_keycodes { include "xfree86+aliases(qwerty)" };
(II) Mouse1: ps2EnableDataReporting: succeeded
(**) RADEON(0): RADEONSaveScreen(2)


je sais plus quoi faire...
Back to top
View user's profile Send private message
_droop_
l33t
l33t


Joined: 30 May 2004
Posts: 957
PostPosted: Wed Nov 29, 2006 9:38 am    Post subject: Reply with quote
Salut,

Effectivement le message dans dmesg m'a l'air d'indiquer une erreur.

Apparement ca peut se produire sur des cartes mal supportées. Dans ce cas, il faut faire une petite modification du noyau. Ce qui semble être le cas pour certaines X300 (remarques que le post sur la lkml est vieu et peut être obsolête, je vais essayer de vérifier).

Sinon un cat /proc/mtrr indiquera les régions définies et éventuellement la source du conflit (s'il y en a un).

Le module i915 c'est pas pour la carte graphique intégré au chipset ? Dans ce cas tu devrais essayer de ne pas le charger.

Il faudrait que je vérifie ce qu'indique un dmesg 'normal' et comment on configure le pci express, mais ca risque d'être dur avant ce soir...

Bon courage en tout cas...
Back to top
View user's profile Send private message
pathfinder
l33t
l33t


Joined: 19 Jan 2006
Posts: 731
Location: Barcelona, Spain
PostPosted: Wed Nov 29, 2006 1:17 pm    Post subject: Reply with quote
Quote:
# cat /proc/mtrr
reg00: base=0x00000000 ( 0MB), size=1024MB: write-back, count=1
reg01: base=0xd8000000 (3456MB), size= 128MB: write-combining, count=1


( je pige pas du tout)
[aussi, a la bios, il y a un message d erreur asez bizarre avec le nouveau kernel, comme quoi BIOS-eXXX n est pas utilisable ou un truc comme ca...]

sinon, j unloade i915 pour voir. et je suis le how to:https://forums.gentoo.org/viewtopic-t-374745-highlight-r300.html
Back to top
View user's profile Send private message
pathfinder
l33t
l33t


Joined: 19 Jan 2006
Posts: 731
Location: Barcelona, Spain
PostPosted: Wed Nov 29, 2006 1:57 pm    Post subject: Reply with quote
pour le message de la BIOS, je crois pas que ca ait a voir, mais le voici:
Code:
MCFG area at e0000000 is not E820 reserved
(la quantite de 0 apres le e est incertaine...)

je precise:
mon noyau est desormais un
2.6.18-r3
et j y ai mis en modules le DRI, ATI RADEON, i915, et tout ce qui me passait par la tete...
Quote:
lsmod
Module Size Used by
radeon 113568 0
drm 61588 1 radeon
i2c_i801 8204 0
intel_agp 21404 1
i2c_core 18048 1 i2c_i801
agpgart 27084 2 drm,intel_agp


(j ai pas charge i915)

Quote:
glxinfo
name of display: :0.0
display: :0 screen: 0
direct rendering: No


aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
Back to top
View user's profile Send private message
Magic Banana
Veteran
Veteran


Joined: 13 Dec 2005
Posts: 1912
Location: Belo Horizonte, Minas Gerais, Brasil
PostPosted: Wed Nov 29, 2006 2:37 pm    Post subject: Reply with quote
Comme _droop_, je te conseille de faire comme si tu n'avais QUE ta carte graphique Radeon ou que ta carte graphique intégrée i915...
Back to top
View user's profile Send private message
_droop_
l33t
l33t


Joined: 30 May 2004
Posts: 957
PostPosted: Wed Nov 29, 2006 2:49 pm    Post subject: Reply with quote
Re,

Tu peux indiquer ce que donne lspci -vv pour ta carte ?

il faudrait vérifier que ta carte est bien supporté par drm (ce qui ne semble pas être le cas). Pour cela il faut d'abord choper l'id :

Si par exemple lspci indique
Code:
0000:01:00.0 VGA compatible controller: ATI Technologies Inc RV370 5B60 [Radeon X300 (PCIE)]

l'id c'est 5B60.

Il faut ensuite regarder dans drm_pciids.h si cet id existe (il se trouve dans l'archive x11-drm mais je peux pas te dire où exactement). (A la rigeur dans les source du 2.6.18, ca doit être à peu près la même version de drm).
Back to top
View user's profile Send private message
pathfinder
l33t
l33t


Joined: 19 Jan 2006
Posts: 731
Location: Barcelona, Spain
PostPosted: Wed Nov 29, 2006 4:33 pm    Post subject: Reply with quote
Quote:
04:00.0 VGA compatible controller: ATI Technologies Inc RV370 5B60 [Radeon X300 (PCIE)] (prog-if 00 [VGA])
Subsystem: PC Partner Limited Unknown device 0500
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0, Cache Line Size 04
Interrupt: pin A routed to IRQ 16
Region 0: Memory at d8000000 (32-bit, prefetchable) [size=128M]
Region 1: I/O ports at e000 [size=256]
Region 2: Memory at d7fe0000 (32-bit, non-prefetchable) [size=64K]
Expansion ROM at d7fc0000 [disabled] [size=128K]
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-
Capabilities: [58] Express Endpoint IRQ 0
Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag+
Device: Latency L0s <128ns, L1 <2us
Device: AtnBtn- AtnInd- PwrInd-
Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
Link: Supported Speed 2.5Gb/s, Width x16, ASPM L0s L1, Port 0
Link: Latency L0s <128ns, L1 <1us
Link: ASPM Disabled RCB 64 bytes CommClk- ExtSynch-
Link: Speed 2.5Gb/s, Width x16
Capabilities: [80] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
Address: 0000000000000000 Data: 0000


ok je poursuis donc sur ce topic
merci de vos reponses.

j ai bien tente avec SEUL le module drm et radeon (j oublie i915)
Quote:
$ lsmod
Module Size Used by
radeon 113568 0
drm 61588 1 radeon
i2c_i801 8204 0
intel_agp 21404 1
i2c_core 18048 1 i2c_i801
agpgart 27084 2 drm,intel_agp


pour ce qui est du fichier dont tu parles:
je me l ai pas trouve dans
Quote:
$ sudo find / -name x11-drm
/etc/modules.d/x11-drm
/lib/modules/2.6.15-gentoo-r1/x11-drm
/lib/modules/2.6.18-gentoo-r3/x11-drm
/usr/portage/x11-base/x11-drm


parcontre ton autre piste:
Quote:
atlantis linux # find /usr/src/linux/ -name "*drm_pci*"
/usr/src/linux/drivers/char/drm/drm_pci.c
/usr/src/linux/drivers/char/drm/drm_pci.o
/usr/src/linux/drivers/char/drm/.drm_pci.o.cmd
/usr/src/linux/drivers/char/drm/drm_pciids.h

Bingo...
je dois cherche quoi dans ce fichier?
parce que 5B60 n y est pas...

Quote:
/*
This file is auto-generated from the drm_pciids.txt in the DRM CVS
Please contact dri-devel@lists.sf.net to add new cards to this list
*/
#define radeon_PCI_IDS \
{0x1002, 0x3150, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV380|CHIP_IS_MOBILITY}, \
{0x1002, 0x3152, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV380|CHIP_IS_MOBILITY|CHIP_NEW_MEMMAP}, \
{0x1002, 0x3154, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV380|CHIP_IS_MOBILITY|CHIP_NEW_MEMMAP}, \
{0x1002, 0x3E50, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV380|CHIP_NEW_MEMMAP}, \
{0x1002, 0x3E54, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV380|CHIP_NEW_MEMMAP}, \
{0x1002, 0x4136, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RS100|CHIP_IS_IGP}, \
{0x1002, 0x4137, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RS200|CHIP_IS_IGP}, \
{0x1002, 0x4144, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R300}, \
{0x1002, 0x4145, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R300}, \ on est d accord, c est pas de celui la
{0x1002, 0x4146, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R300}, \ qu il s agit, hein?
{0x1002, 0x4147, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R300}, \
{0x1002, 0x4148, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R350}, \
{0x1002, 0x4149, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R350}, \
{0x1002, 0x414A, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R350}, \
{0x1002, 0x414B, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R350}, \
{0x1002, 0x4150, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV350}, \
{0x1002, 0x4151, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV350}, \
{0x1002, 0x4152, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV350}, \
{0x1002, 0x4153, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV350}, \
{0x1002, 0x4154, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV350}, \
{0x1002, 0x4155, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV350}, \
{0x1002, 0x4156, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV350}, \
{0x1002, 0x4237, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RS200|CHIP_IS_IGP}, \
{0x1002, 0x4242, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R200}, \
{0x1002, 0x4243, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R200}, \
{0x1002, 0x4336, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RS100|CHIP_IS_IGP|CHIP_IS_MOBILITY}, \
{0x1002, 0x4337, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RS200|CHIP_IS_IGP|CHIP_IS_MOBILITY}, \
{0x1002, 0x4437, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RS200|CHIP_IS_IGP|CHIP_IS_MOBILITY}, \
{0x1002, 0x4966, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV250}, \
{0x1002, 0x4967, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV250}, \
{0x1002, 0x4A48, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R420|CHIP_NEW_MEMMAP}, \
{0x1002, 0x4A49, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R420|CHIP_NEW_MEMMAP}, \
{0x1002, 0x4A4A, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R420|CHIP_NEW_MEMMAP}, \
{0x1002, 0x4A4B, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R420|CHIP_NEW_MEMMAP}, \
{0x1002, 0x4A4C, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R420|CHIP_NEW_MEMMAP}, \
{0x1002, 0x4A4D, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R420|CHIP_NEW_MEMMAP}, \
{0x1002, 0x4A4E, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R420|CHIP_IS_MOBILITY|CHIP_NEW_MEMMAP}, \
{0x1002, 0x4A4F, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R420|CHIP_NEW_MEMMAP}, \
{0x1002, 0x4A50, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R420|CHIP_NEW_MEMMAP}, \
{0x1002, 0x4A54, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R420|CHIP_NEW_MEMMAP}, \
{0x1002, 0x4B49, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R420|CHIP_NEW_MEMMAP}, \
{0x1002, 0x4B4A, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R420|CHIP_NEW_MEMMAP}, \
{0x1002, 0x4B4B, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R420|CHIP_NEW_MEMMAP}, \
{0x1002, 0x4B4C, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R420|CHIP_NEW_MEMMAP}, \
{0x1002, 0x4C57, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV200|CHIP_IS_MOBILITY}, \
{0x1002, 0x4C58, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV200|CHIP_IS_MOBILITY}, \
{0x1002, 0x4C59, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV100|CHIP_IS_MOBILITY}, \
{0x1002, 0x4C5A, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV100|CHIP_IS_MOBILITY}, \
{0x1002, 0x4C64, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV250|CHIP_IS_MOBILITY}, \
{0x1002, 0x4C66, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV250|CHIP_IS_MOBILITY}, \
{0x1002, 0x4C67, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV250|CHIP_IS_MOBILITY}, \
{0x1002, 0x4E44, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R300}, \
{0x1002, 0x4E45, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R300}, \
{0x1002, 0x4E46, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R300}, \
{0x1002, 0x4E47, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R300}, \
{0x1002, 0x4E48, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R350}, \
{0x1002, 0x4E49, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R350}, \
{0x1002, 0x4E4A, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R350}, \
{0x1002, 0x4E4B, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R350}, \
{0x1002, 0x4E50, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV350|CHIP_IS_MOBILITY}, \
{0x1002, 0x4E51, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV350|CHIP_IS_MOBILITY}, \
{0x1002, 0x4E52, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV350|CHIP_IS_MOBILITY}, \
{0x1002, 0x4E53, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV350|CHIP_IS_MOBILITY}, \
{0x1002, 0x4E54, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV350|CHIP_IS_MOBILITY}, \
{0x1002, 0x4E56, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV350|CHIP_IS_MOBILITY}, \
{0x1002, 0x5144, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R100|CHIP_SINGLE_CRTC}, \
{0x1002, 0x5145, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R100|CHIP_SINGLE_CRTC}, \
{0x1002, 0x5146, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R100|CHIP_SINGLE_CRTC}, \
{0x1002, 0x5147, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R100|CHIP_SINGLE_CRTC}, \
{0x1002, 0x5148, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R200}, \
{0x1002, 0x514C, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R200}, \
{0x1002, 0x514D, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R200}, \
{0x1002, 0x5157, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV200}, \
{0x1002, 0x5158, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV200}, \
{0x1002, 0x5159, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV100}, \
{0x1002, 0x515A, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV100}, \
{0x1002, 0x515E, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV100}, \
{0x1002, 0x5460, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV380|CHIP_IS_MOBILITY}, \
{0x1002, 0x5462, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV380|CHIP_IS_MOBILITY}, \
{0x1002, 0x5464, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV380|CHIP_IS_MOBILITY}, \
{0x1002, 0x5548, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R420|CHIP_NEW_MEMMAP}, \
{0x1002, 0x5549, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R420|CHIP_NEW_MEMMAP}, \
{0x1002, 0x554A, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R420|CHIP_NEW_MEMMAP}, \
{0x1002, 0x554B, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R420|CHIP_NEW_MEMMAP}, \
{0x1002, 0x554C, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R420|CHIP_NEW_MEMMAP}, \
{0x1002, 0x554D, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R420|CHIP_NEW_MEMMAP}, \
{0x1002, 0x554E, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R420|CHIP_NEW_MEMMAP}, \
{0x1002, 0x554F, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R420|CHIP_NEW_MEMMAP}, \
{0x1002, 0x5550, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R420|CHIP_NEW_MEMMAP}, \
{0x1002, 0x5551, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R420|CHIP_NEW_MEMMAP}, \
{0x1002, 0x5552, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R420|CHIP_NEW_MEMMAP}, \
{0x1002, 0x5554, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R420|CHIP_NEW_MEMMAP}, \
{0x1002, 0x564A, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV410|CHIP_IS_MOBILITY|CHIP_NEW_MEMMAP}, \
{0x1002, 0x564B, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV410|CHIP_IS_MOBILITY|CHIP_NEW_MEMMAP}, \
{0x1002, 0x564F, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV410|CHIP_IS_MOBILITY|CHIP_NEW_MEMMAP}, \
{0x1002, 0x5652, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV410|CHIP_IS_MOBILITY|CHIP_NEW_MEMMAP}, \
{0x1002, 0x5653, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV410|CHIP_IS_MOBILITY|CHIP_NEW_MEMMAP}, \
{0x1002, 0x5834, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RS300|CHIP_IS_IGP}, \
{0x1002, 0x5835, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RS300|CHIP_IS_IGP|CHIP_IS_MOBILITY}, \
{0x1002, 0x5960, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV280}, \
{0x1002, 0x5961, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV280}, \
{0x1002, 0x5962, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV280}, \
{0x1002, 0x5964, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV280}, \
{0x1002, 0x5965, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV280}, \
{0x1002, 0x5969, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV100}, \
{0x1002, 0x5b60, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV380|CHIP_NEW_MEMMAP}, \
{0x1002, 0x5b62, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV380|CHIP_NEW_MEMMAP}, \
{0x1002, 0x5b63, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV380|CHIP_NEW_MEMMAP}, \
{0x1002, 0x5b64, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV380|CHIP_NEW_MEMMAP}, \
{0x1002, 0x5b65, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV380|CHIP_NEW_MEMMAP}, \
{0x1002, 0x5c61, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV280|CHIP_IS_MOBILITY}, \
{0x1002, 0x5c63, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV280|CHIP_IS_MOBILITY}, \
{0x1002, 0x5d48, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R420|CHIP_IS_MOBILITY|CHIP_NEW_MEMMAP}, \
{0x1002, 0x5d49, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R420|CHIP_IS_MOBILITY|CHIP_NEW_MEMMAP}, \
{0x1002, 0x5d4a, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R420|CHIP_IS_MOBILITY|CHIP_NEW_MEMMAP}, \
{0x1002, 0x5d4c, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R420|CHIP_NEW_MEMMAP}, \
{0x1002, 0x5d4d, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R420|CHIP_NEW_MEMMAP}, \
{0x1002, 0x5d4e, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R420|CHIP_NEW_MEMMAP}, \
{0x1002, 0x5d4f, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R420|CHIP_NEW_MEMMAP}, \
{0x1002, 0x5d50, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R420|CHIP_NEW_MEMMAP}, \
{0x1002, 0x5d52, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R420|CHIP_NEW_MEMMAP}, \
{0x1002, 0x5d57, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_R420|CHIP_NEW_MEMMAP}, \
{0x1002, 0x5e48, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV410|CHIP_NEW_MEMMAP}, \
{0x1002, 0x5e4a, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV410|CHIP_NEW_MEMMAP}, \
{0x1002, 0x5e4b, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV410|CHIP_NEW_MEMMAP}, \
{0x1002, 0x5e4c, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV410|CHIP_NEW_MEMMAP}, \
{0x1002, 0x5e4d, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV410|CHIP_NEW_MEMMAP}, \
{0x1002, 0x5e4f, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV410|CHIP_NEW_MEMMAP}, \
{0x1002, 0x7834, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RS300|CHIP_IS_IGP|CHIP_NEW_MEMMAP}, \
{0x1002, 0x7835, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RS300|CHIP_IS_IGP|CHIP_IS_MOBILITY|CHIP_NEW_MEMMAP}, \
{0, 0, 0}

#define r128_PCI_IDS \
{0x1002, 0x4c45, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x4c46, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x4d46, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x4d4c, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x5041, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x5042, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x5043, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x5044, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x5045, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x5046, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x5047, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x5048, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x5049, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x504A, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x504B, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x504C, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x504D, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x504E, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x504F, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x5050, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x5051, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x5052, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x5053, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x5054, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x5055, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x5056, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x5057, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x5058, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x5245, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x5246, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x5247, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x524b, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x524c, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x534d, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x5446, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x544C, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x5452, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0, 0, 0}

#define mga_PCI_IDS \
{0x102b, 0x0520, PCI_ANY_ID, PCI_ANY_ID, 0, 0, MGA_CARD_TYPE_G200}, \
{0x102b, 0x0521, PCI_ANY_ID, PCI_ANY_ID, 0, 0, MGA_CARD_TYPE_G200}, \
{0x102b, 0x0525, PCI_ANY_ID, PCI_ANY_ID, 0, 0, MGA_CARD_TYPE_G400}, \
{0x102b, 0x2527, PCI_ANY_ID, PCI_ANY_ID, 0, 0, MGA_CARD_TYPE_G550}, \
{0, 0, 0}

#define mach64_PCI_IDS \
{0x1002, 0x4749, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x4750, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x4751, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x4742, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x4744, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x4c49, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x4c50, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x4c51, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x4c42, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x4c44, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x474c, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x474f, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x4752, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x4753, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x474d, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x474e, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x4c52, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x4c53, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x4c4d, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1002, 0x4c4e, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0, 0, 0}

#define sisdrv_PCI_IDS \
{0x1039, 0x0300, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1039, 0x5300, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1039, 0x6300, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1039, 0x7300, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0, 0, 0}

#define tdfx_PCI_IDS \
{0x121a, 0x0003, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x121a, 0x0004, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x121a, 0x0005, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x121a, 0x0007, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x121a, 0x0009, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x121a, 0x000b, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0, 0, 0}

#define viadrv_PCI_IDS \
{0x1106, 0x3022, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1106, 0x3118, PCI_ANY_ID, PCI_ANY_ID, 0, 0, VIA_PRO_GROUP_A}, \
{0x1106, 0x3122, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1106, 0x7205, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x1106, 0x3108, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0, 0, 0}

#define i810_PCI_IDS \
{0x8086, 0x7121, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x8086, 0x7123, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x8086, 0x7125, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x8086, 0x1132, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0, 0, 0}

#define i830_PCI_IDS \
{0x8086, 0x3577, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x8086, 0x2562, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x8086, 0x3582, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x8086, 0x2572, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0, 0, 0}

#define gamma_PCI_IDS \
{0x3d3d, 0x0008, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0, 0, 0}

#define savage_PCI_IDS \
{0x5333, 0x8a20, PCI_ANY_ID, PCI_ANY_ID, 0, 0, S3_SAVAGE3D}, \
{0x5333, 0x8a21, PCI_ANY_ID, PCI_ANY_ID, 0, 0, S3_SAVAGE3D}, \
{0x5333, 0x8a22, PCI_ANY_ID, PCI_ANY_ID, 0, 0, S3_SAVAGE4}, \
{0x5333, 0x8a23, PCI_ANY_ID, PCI_ANY_ID, 0, 0, S3_SAVAGE4}, \
{0x5333, 0x8c10, PCI_ANY_ID, PCI_ANY_ID, 0, 0, S3_SAVAGE_MX}, \
{0x5333, 0x8c11, PCI_ANY_ID, PCI_ANY_ID, 0, 0, S3_SAVAGE_MX}, \
{0x5333, 0x8c12, PCI_ANY_ID, PCI_ANY_ID, 0, 0, S3_SAVAGE_MX}, \
{0x5333, 0x8c13, PCI_ANY_ID, PCI_ANY_ID, 0, 0, S3_SAVAGE_MX}, \
{0x5333, 0x8c22, PCI_ANY_ID, PCI_ANY_ID, 0, 0, S3_SUPERSAVAGE}, \
{0x5333, 0x8c24, PCI_ANY_ID, PCI_ANY_ID, 0, 0, S3_SUPERSAVAGE}, \
{0x5333, 0x8c26, PCI_ANY_ID, PCI_ANY_ID, 0, 0, S3_SUPERSAVAGE}, \
{0x5333, 0x8c2a, PCI_ANY_ID, PCI_ANY_ID, 0, 0, S3_SUPERSAVAGE}, \
{0x5333, 0x8c2b, PCI_ANY_ID, PCI_ANY_ID, 0, 0, S3_SUPERSAVAGE}, \
{0x5333, 0x8c2c, PCI_ANY_ID, PCI_ANY_ID, 0, 0, S3_SUPERSAVAGE}, \
{0x5333, 0x8c2d, PCI_ANY_ID, PCI_ANY_ID, 0, 0, S3_SUPERSAVAGE}, \
{0x5333, 0x8c2e, PCI_ANY_ID, PCI_ANY_ID, 0, 0, S3_SUPERSAVAGE}, \
{0x5333, 0x8c2f, PCI_ANY_ID, PCI_ANY_ID, 0, 0, S3_SUPERSAVAGE}, \
{0x5333, 0x8a25, PCI_ANY_ID, PCI_ANY_ID, 0, 0, S3_PROSAVAGE}, \
{0x5333, 0x8a26, PCI_ANY_ID, PCI_ANY_ID, 0, 0, S3_PROSAVAGE}, \
{0x5333, 0x8d01, PCI_ANY_ID, PCI_ANY_ID, 0, 0, S3_TWISTER}, \
{0x5333, 0x8d02, PCI_ANY_ID, PCI_ANY_ID, 0, 0, S3_TWISTER}, \
{0x5333, 0x8d03, PCI_ANY_ID, PCI_ANY_ID, 0, 0, S3_PROSAVAGEDDR}, \
{0x5333, 0x8d04, PCI_ANY_ID, PCI_ANY_ID, 0, 0, S3_PROSAVAGEDDR}, \
{0, 0, 0}

#define ffb_PCI_IDS \
{0, 0, 0}

#define i915_PCI_IDS \
{0x8086, 0x3577, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x8086, 0x2562, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x8086, 0x3582, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x8086, 0x2572, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
{0x8086, 0x2582, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \


et RV370 non plus... (ca ca m ennuie plus...)
Back to top
View user's profile Send private message
_droop_
l33t
l33t


Joined: 30 May 2004
Posts: 957
PostPosted: Wed Nov 29, 2006 6:40 pm    Post subject: Reply with quote
Code:
{0x1002, 0x5b60, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_RV380|CHIP_NEW_MEMMAP}


Il y est, le problème n'est pas là...

Utilises tu un framebuffer ?

Si c'est le cas il faut que tu utilises l'option nomtrr. Exemple de ligne de boot :

Code:
video=vesafb:ywrap,vga=0x31X,nomtrr


Enfin, je te conseille de commencer par faire un test sans framebuffer et sans i915.

note : à un moment tu t'étonnes d'avoir l'agp, il me semble que sous linux agp=pci express (du point de vue du noyau).
Back to top
View user's profile Send private message
pathfinder
l33t
l33t


Joined: 19 Jan 2006
Posts: 731
Location: Barcelona, Spain
PostPosted: Wed Nov 29, 2006 7:15 pm    Post subject: Reply with quote
c est marque RV380 et pas RV370... c est pareil?

j utilise un framebuffer:.... uuuuuuuuuuuuuuuuuuuuuuu
en fait, j avais make.conf avec vesafb active (je recompile world en -uvDN sans cette option) pour avoir un zoli boot au demarrage.
depuis que je suis passe en 2.6.18-r3, il ne marche plus en realite, et c est pas grave.

voile l option de mon /boot/grub..
Quote:
title GNU/Linux Gentoo 2006.0 (i686 kernel 2.6.18-gentoo-r3 Emergence Theme)
root (hd0,0)
kernel /kernel-2.6.18-gentoo-r3-1 root=/dev/sda2 video=vesafb:mtrr:3,ywrap,1024x768-32@65 splash=verbose,theme:emergence quiet CONSOLE=/dev/tty1

tu me conseilles donc quoi pour cette ligne?
(sachant que maintenant, je recompile le systeme sans vesafb en flag dans mon make.conf)

je n ai pas changé la config du noyau (il me semble qu il fallait certains modules pour le framebuffer, mais je n ai rien modifie depuis mon passage au nouveau noyau)

je n utilise plus depuis ce matin le module i915, le probleme n est donc plus la.
pour faire alors le test sans framebuffer, je boote avec l option nomtrr, c est tout?

et l option de xorg.conf,

Option "mtrr" "off", je l utilise?
Back to top
View user's profile Send private message
_droop_
l33t
l33t


Joined: 30 May 2004
Posts: 957
PostPosted: Wed Nov 29, 2006 7:23 pm    Post subject: Reply with quote
On doit plus être très loin là.

Dans le grub, tu met nomtrr à la place de mtrr (le frame buffer sera surement un peu plus lent mais si tu passes pas la journée dessus...) (voir désactiver complètement le framebuffer en recompilant le noyau pour commencer).

Dans le xorg, tu devrais enlever l'option que tu as mise.

Pour le RV380/370, les puces doivent être suffisement proche pour être gérée de la même façon. (par contre elles doivent avoir des diffèrences genre taille bus mémoire ou nombre d'unités de calcul...).
Back to top
View user's profile Send private message
pathfinder
l33t
l33t


Joined: 19 Jan 2006
Posts: 731
Location: Barcelona, Spain
PostPosted: Wed Nov 29, 2006 7:42 pm    Post subject: Reply with quote
Quote:
kernel /kernel-2.6.18-gentoo-r3-1 root=/dev/sda2 video=vesafb:ywrap,1024x768-32@65,nomtrr splash=verbose,theme:emergence quiet CONSOLE=/dev/tty1

ca veut dire que ca va pas utiliser mtrr?
(je sais meme pas ce que c est)
et que ca va utiliser tout de meme le framebuffer meme s il est plus compile systemwide?

qu est ce qui sera plus lent?

je devrais desactiver les options du FB dans le noyau?
l emerge est en cours...
Back to top
View user's profile Send private message
nemo13
Veteran
Veteran


Joined: 08 Oct 2004
Posts: 1016
Location: France/Istres
PostPosted: Wed Nov 29, 2006 9:27 pm    Post subject: Reply with quote
_droop_ wrote:
note : à un moment tu t'étonnes d'avoir l'agp, il me semble que sous linux agp=pci express (du point de vue du noyau).

Bonsoir,
je crois que non ; au cours de l'année j'avais posé la question de mettre agp dans le noyau quand
on avait une pci E , et widdan m'avait répondu que s'était inutile

donc pour ma conf de carte graphique est :
Code:
lspci
00:01.0 PCI bridge: Intel Corporation 82915G/P/GV/GL/PL/910GL PCI Express Root Port (rev 04)
01:00.0 VGA compatible controller: nVidia Corporation NV43 [GeForce 6600] (rev a2)
Code:
zgrep -i agp /proc/config.gz
# CONFIG_AGP is not set

et nvidia ne me fait pas la gueule
Code:
cat  /proc/driver/nvidia/cards/0
Model:           GeForce 6600
IRQ:             16
Video BIOS:      05.43.02.16.27
Card Type:       PCI-E
DMA Size:        39 bits
DMA Mask:        0x7fffffffff

voil-voila si çà peut aider.
edit le noyau tout neuf de ce soir :
Code:
 uname -a
Linux gentoobscur 2.6.18-gentoo-r3 #1 SMP PREEMPT Wed Nov 29 19:58:51 CET 2006 i686
Intel(R) Pentium(R) 4 CPU 3.20GHz GenuineIntel GNU/Linux

gentoobscur nemo13 #
Back to top
View user's profile Send private message
_droop_
l33t
l33t


Joined: 30 May 2004
Posts: 957
PostPosted: Thu Nov 30, 2006 8:21 am    Post subject: Reply with quote
pathfinder wrote:
Quote:
kernel /kernel-2.6.18-gentoo-r3-1 root=/dev/sda2 video=vesafb:ywrap,1024x768-32@65,nomtrr splash=verbose,theme:emergence quiet CONSOLE=/dev/tty1

ca veut dire que ca va pas utiliser mtrr?
(je sais meme pas ce que c est)
et que ca va utiliser tout de meme le framebuffer meme s il est plus compile systemwide?

qu est ce qui sera plus lent?


Le mtrr ca permet d'accèlerer l'accès aux plages mémoire sur les périphériques (comme par exemple la mémoire ram).

Avec l'option nomtrr, le framebuffer devrait être plus lent plus lent. Mais si tu l'utilises qu'au démarrage, c'est pas bien important...

pathfinder wrote:

je devrais desactiver les options du FB dans le noyau?
l emerge est en cours...


Pour commencer, ce serait plus simple en effet d'avoir le noyau sans framebuffer, enfin essaye l'option nomtrr si tu veux garder le fb...

Quel emerge, tu confondrais pas frame buffer et fbsplash ?


@nemo13 : tu as raison, il semble qu'il faille juste activer l'option dans 'Bus options (PCI, PCMCIA, EISA, MCA, ISA)' de menuconfig, merci.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index French All times are GMT
Goto page Previous  1, 2
Page 2 of 2

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum



 Links: forums.gentoo.org | www.gentoo.org | bugs.gentoo.org | wiki.gentoo.org | forum-mods@gentoo.org

Copyright 2001-2025 Gentoo Foundation, Inc. Designed by Kyle Manna © 2003; Style derived from original subSilver theme. | Hosting by Gossamer Threads Inc. © | Powered by phpBB 2.0.23-gentoo-p11 © 2001, 2002 phpBB Group
Privacy Policy