| View previous topic :: View next topic |
| Author |
Message |
Le Barde
n00b
Joined: 13 Jul 2008
Posts: 36
|
 Posted: Fri Jan 16, 2009 2:51 pm Post subject: [emerge Xorg][i810] Support de i810 dans Xorg |
 |
|
Bonjour à tous,
J'essaie de recompiler Xorg pour avoir le support de i810, mais y'a comme qui dirait un truc qui m'embête. Mais voici sans plus attendre la bouzin :
| Quote: | a_po@lat198 ~ $ sudo emerge -pv x11-base/xorg-server
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild R ] x11-base/xorg-server-1.3.0.0-r6 USE="dri ipv6 xorg (-3dfx) -debug -dmx -kdrive -minimal -nptl* -sdl -xprint" INPUT_DEVICES="evdev keyboard mouse -acecad -aiptek -calcomp -citron -digitaledge -dmc -dynapro -elo2300 -elographics -fpit -hyperpen -jamstudio -joystick -magellan -microtouch -mutouch -palmax -penmount -spaceorb -summa -synaptics -tek4957 -ur98 -vmmouse -void -wacom" VIDEO_CARDS="vesa -apm -ark -chips -cirrus -cyrix -dummy -epson -fbdev* -fglrx -glint -i128 (-i740) (-impact) (-imstt) -intel% -mach64 -mga -neomagic (-newport) (-nsc) -nv -nvidia -r128 -radeon -rendition -s3 -s3virge -savage -siliconmotion -sis -sisusb (-sunbw2) (-suncg14) (-suncg3) (-suncg6) (-sunffb) (-sunleo) (-suntcx) -tdfx -tga -trident -tseng -v4l -vga -via -vmware -voodoo (-i810%*)" 0 kB
Total: 1 package (1 reinstall), Size of downloads: 0 kB
a_po@lat198 ~ $ emerge --help
|
Pourquoi (-i810%*) ?
Pourtant dans mon make.conf j'ai bien le tag i810 dans VIDEO_CARDS. ...est-ce que ce ne serait pas un problème de conf' du noyau à vostre avis ?
Merci d'avance.
_________________
War does not decide who's right, but who's left.
Last edited by Le Barde on Fri Jan 16, 2009 3:06 pm; edited 1 time in total |
|
| Back to top |
|
 |
kwenspc
Advocate
Joined: 21 Sep 2003
Posts: 4954
|
| Posted: Fri Jan 16, 2009 3:05 pm Post subject: |
|
|
C'est le flag "intel" je crois qu'il faut dorénavant utiliser.
Sinon tu peux mettre ton titre de topic au normes du forum?
_________________
membre officieux du SAV Ati GEntoo |
|
| Back to top |
|
|
Le Barde
n00b
Joined: 13 Jul 2008
Posts: 36
|
| Posted: Fri Jan 16, 2009 3:12 pm Post subject: |
|
|
Pourtant dans mon équipe (on est 20 développeurs, tous avec Gentoo  ) on a tous quasiment la même machine et en tous cas tous le même chipset graphique. Ils utilisent i810, donc ça devrait fonctionner non ?
Ça veut dire quoi le (-i810%*) ?
_________________
War does not decide who's right, but who's left. |
|
| Back to top |
|
|
kopp
Advocate
Joined: 09 Apr 2004
Posts: 2885
Location: Grenoble, France
|
| Posted: Fri Jan 16, 2009 4:49 pm Post subject: |
|
|
Ça veut dire que le useflag n'existe plus.
man emerge te donne :
| Code: | --verbose (-v)
Tell emerge to run in verbose mode. Currently this flag causes emerge to
print out GNU info errors, if any, and to show the USE flags that will be
used for each package when pretending. The following symbols are affixed to
USE flags in order to indicate their status:
Symbol Location Meaning
──────────────────────────────────────────────────────────────
- prefix not enabled (either disabled or removed)
* suffix transition to or from the enabled state
% suffix newly added or removed
() circumfix forced, masked, or removed |
Comme le dit kwenspc, maintenant, il faut utiliser intel |
|
| Back to top |
|
|
Le Barde
n00b
Joined: 13 Jul 2008
Posts: 36
|
| Posted: Mon Jan 19, 2009 9:18 am Post subject: |
|
|
Merci beaucoup, ça marche mais je n'ai pas encore ma résolution native (1440x900) 
Voici mon xorg.conf :
| Quote: | Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
Option "AIGLX" "true"
Option "Xinerama" "off"
Option "Clone" "off"
EndSection
Section "Files"
FontPath "/usr/share/fonts/misc/"
FontPath "/usr/share/fonts/TTF/"
FontPath "/usr/share/fonts/Type1/"
FontPath "/usr/share/fonts/CID/"
FontPath "/usr/share/fonts/75dpi/"
FontPath "/usr/share/fonts/100dpi/"
FontPath "/usr/share/fonts/corefonts/"
FontPath "/usr/share/fonts/freefont/"
FontPath "/usr/share/fonts/terminus/"
FontPath "/usr/share/fonts/ukr/"
FontPath "/usr/share/fonts/urw-fonts/"
FontPath "/usr/share/fonts/lfpfonts-fix/"
FontPath "/usr/share/fonts/lfpfonts-var/"
EndSection
Section "Module"
Load "record"
Load "extmod"
# Load "GLcore"
Load "dbe"
Load "dri"
Load "drm"
Load "glx"
# Load "vnc"
Load "xtrap"
Load "freetype"
Load "type1"
# Load "i2c"
# Load "dcc"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "logiik"
Option "XkbLayout" "fr"
Option "XkbOptions" "lv3:ralt_switch"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5"
Option "Emulate3Buttons" "no"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "DELL"
ModelName "LCD198WFP"
Option "DPMS"
HorizSync 30-81
VertRefresh 56-76
EndSection
Section "Device"
Identifier "Card0"
Driver "intel"
BusID "PCI:0:2:0"
Option "XAANoOffscreenPixmaps" "true"
Option "DRI" "true"
Option "ModeValidation" "NoMaxPClkCheck"
Option "DynamicClocks" "off"
Option "XAANoOffscreenPixmaps" "true"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Modes "1920x1200" "1680x1050" "1440x900" "1280x1024" "1024x768" "800x600" "640x480"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Modes "1920x1200" "1680x1050" "1440x900" "1280x1024" "1024x768" "800x600" "640x480"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Modes "1920x1200" "1680x1050" "1440x900" "1280x1024" "1024x768" "800x600" "640x480"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Modes "1920x1200" "1680x1050" "1440x900" "1280x1024" "1024x768" "800x600" "640x480"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Modes "1920x1200" "1680x1050" "1440x900" "1280x1024" "1024x768" "800x600" "640x480"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Modes "1920x1200" "1680x1050" "1440x900" "1280x1024" "1024x768" "800x600" "640x480"
Viewport 0 0
Depth 24
EndSubSection
EndSection
Section "DRI"
Group 0
Mode 0666
EndSection
Section "Extensions"
Option "Composite" "Enable"
EndSection
|
J'ai mis les modes avec 1440x900 et pourtant rien...
Auriez-vous une idée ?
_________________
War does not decide who's right, but who's left. |
|
| Back to top |
|
|
bouriquo
Guru
Joined: 29 May 2004
Posts: 304
Location: Collonges (01)
|
| Posted: Mon Jan 19, 2009 9:48 am Post subject: |
|
|
Salut,
Je pense pas que cela est une incidence, mais pourquoi mettre les résolutions 1900x1280 si tu ne peux faire que tu 1440x900 ?.
Ensuite il me semble que c'est soit dri soit glx et pas les deux en même temps, mais je me trompe peut être  .
Ensuite tu as essayé de modifier la résolution sous ton windows manager ?
@++ |
|
| Back to top |
|
|
kopp
Advocate
Joined: 09 Apr 2004
Posts: 2885
Location: Grenoble, France
|
| Posted: Mon Jan 19, 2009 2:18 pm Post subject: |
|
|
| Code: | | grep "(EE)" /var/log/Xorg.0.log |
| Code: | | grep "(WW)" /var/log/Xorg.0.log |
|
|
| Back to top |
|
|
Le Barde
n00b
Joined: 13 Jul 2008
Posts: 36
|
| Posted: Mon Jan 19, 2009 3:31 pm Post subject: |
|
|
Hmmmm...
| Code: | a_po@pc_machin ~/log $ grep "(EE)" /var/log/Xorg.0.log
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): [dri] DRIScreenInit failed. Disabling DRI.
(EE) AIGLX: Screen 0 is not DRI capable
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
(EE) intel(0): Unable to write to SDVOCTRL_E for SDVOB Slave 0x70.
a_po@pc_machin ~/log $
|
et aussi :
| Code: | a_po@pc_machin ~/log $ grep "(WW)" /var/log/Xorg.0.log
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(WW) The directory "/usr/share/fonts/TTF/" does not exist.
(WW) The directory "/usr/share/fonts/CID/" does not exist.
(WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/freefont/".
(WW) The directory "/usr/share/fonts/ukr/" does not exist.
(WW) The directory "/usr/share/fonts/urw-fonts/" does not exist.
(WW) The directory "/usr/share/fonts/lfpfonts-fix/" does not exist.
(WW) The directory "/usr/share/fonts/lfpfonts-var/" does not exist.
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(WW) intel: No matching Device section for instance (BusID PCI:0:2:1) found
(WW) intel(0): Register 0x61114 (PORT_HOTPLUG_STAT) changed from 0x00000000 to 0x00000b00
(WW) intel(0): Failed to set up write-combining range (0xc0000000,0x10000000)
(WW) intel(0): Option "ModeValidation" is not used
(WW) intel(0): Option "DynamicClocks" is not used
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
a_po@pc_machin ~/log $
|
_________________
War does not decide who's right, but who's left. |
|
| Back to top |
|
|
Le Barde
n00b
Joined: 13 Jul 2008
Posts: 36
|
| Posted: Mon Jan 19, 2009 3:34 pm Post subject: |
|
|
| bouriquo wrote: | Salut,
Je pense pas que cela est une incidence, mais pourquoi mettre les résolutions 1900x1280 si tu ne peux faire que tu 1440x900 ?.
Ensuite il me semble que c'est soit dri soit glx et pas les deux en même temps, mais je me trompe peut être .
Ensuite tu as essayé de modifier la résolution sous ton windows manager ?
|
Je vais voir ça de suite. En tous cas, je peux changer de résolution, mais on ne me propose pas 1440x900
_________________
War does not decide who's right, but who's left. |
|
| Back to top |
|
|
bouriquo
Guru
Joined: 29 May 2004
Posts: 304
Location: Collonges (01)
|
| Posted: Mon Jan 19, 2009 3:38 pm Post subject: |
|
|
| On te propose quoi ? |
|
| Back to top |
|
|
Le Barde
n00b
Joined: 13 Jul 2008
Posts: 36
|
| Posted: Mon Jan 19, 2009 3:41 pm Post subject: |
|
|
On me propose :
- 1600x1200
- 1600x1024
- 1400x1050
- 1280x1024
- 1280x960
- 1152x864
- 1024x768
- 832x624
- 800x600
- 640x480
_________________
War does not decide who's right, but who's left. |
|
| Back to top |
|
|
guilc
Bodhisattva
Joined: 15 Nov 2003
Posts: 3326
Location: Paris - France
|
| Posted: Mon Jan 19, 2009 9:17 pm Post subject: |
|
|
Tu as une carte intel avec résolutions figées dans le bios video on dirait. C'est le cas de beaucoup de modèles un peu ancien.
Tu peux contourner ce problème en activant dans le bios video ta résolution via l'outil sys-apps/915resolution.
C'est marrant, il me semblait que cet outil n'était plus nécessaire avec les dernières version du driver intel...
_________________
Merci de respecter les règles du forum.
Mon site perso : https://www.xwing.info
Mon PORTDIR_OVERLAY : https://gentoo.xwing.info ou layman -a xwing |
|
| Back to top |
|
|
kopp
Advocate
Joined: 09 Apr 2004
Posts: 2885
Location: Grenoble, France
|
| Posted: Mon Jan 19, 2009 9:39 pm Post subject: |
|
|
guilc : est ce vraiment le dernier pilote intel ? il n'est pas en ~arch vu la version de xorg (ultra vieille quand même ...)
Peut-être que ça explique le problème...
Aussi y a cette histoire d'adresse PCI pour le DRI : tu utilises quelle sortie ? |
|
| Back to top |
|
|
Mickael
Advocate
Joined: 05 Sep 2005
Posts: 2383
Location: ~Belfort! - France - EU
|
| Posted: Mon Jan 26, 2009 8:50 am Post subject: |
|
|
| guilc wrote: | ....
Tu peux contourner ce problème en activant dans le bios video ta résolution via l'outil sys-apps/915resolution.
C'est marrant, il me semblait que cet outil n'était plus nécessaire avec les dernières version du driver intel... |
Tout à fait, ce dernier peut être utile si lors du boot, uvesafb ne fonctionne pas correctement (la faute à qui  , ==>le truc qui caresse le clavier) sinon une fois X lancé, 915résolution est inutile. /off En même temps les constructeurs et intel pourrait au minimum implémenter la résolution des écrans dans le bios de ces machines! s'pas croyable ce foutage de gueule!
_________________
À LIRE : COMMENT POSTER ET OBTENIR DE L'AIDE ?
Qui suis-je ? Bon j'ai relu, comme d'habitude, je suis bon a rien le vendredi
Qui suis-je ? Je ne serai jamais modo |
|
| Back to top |
|
|
Le Barde
n00b
Joined: 13 Jul 2008
Posts: 36
|
| Posted: Mon Jan 26, 2009 9:51 am Post subject: |
|
|
Merci merci pour vos réponses. Je n'ai pas encore pu tester car il y a le feu au boulot. Mais dès que j'ai un peu plus de temps je me repenche là-dessus.
EDIT : Et je n'ai pas compris cette histoire de DRI... Quelqu'un pourrait m'en dire un peu plus à ce sujet ?
_________________
War does not decide who's right, but who's left. |
|
| Back to top |
|
|
|
French
