Bruce-b Posted May 24, 2007 Share Posted May 24, 2007 Bonjour a tous, lorsque je démarre une nouvelle session après avoir choisit le bureau metisse dans Drak3d, metisse ne se lance pas, je ne vois a l'écran que le fond d'écran et le pointeur de la souris qui "tournicote" sans fin pour finalement finir par un retour au gestionnaire de connexion et choisir un autre bureau Je précise que mes drivers ati proprio fonctionnent bien car compiz et beryl fonctionnent (via XGL donc). Quelqu'un a t'il un début de piste a me donner svp Question Link to comment Share on other sites More sharing options...
Bruce-b Posted May 25, 2007 Author Share Posted May 25, 2007 siouplait, une petite piste pour m'aider Link to comment Share on other sites More sharing options...
lorinc Posted May 25, 2007 Share Posted May 25, 2007 et si tu essayes de le lancer via startx (faut te faire un xinitrc quivabien), quels seraient alors les messages d'erreurs ? Link to comment Share on other sites More sharing options...
Scaramouche Posted May 28, 2007 Share Posted May 28, 2007 alors, il me faudrait : la réponse à lorinc, le modèle de la carte et les perfs de ta machine (proc, ram, etc) , la version de mandriva (Spring je suppose ?) et miroirs installés (backports ou pas ? plf ou pas ?), tu as installé le drivers ati de qui ? mandriva, plf ? un ati ou un dkms-ati ? compilé à partir des sources ? la réponse de "rpm -q ati" ou "rpm -q dkms-ati" à faire dans une console en root s'il te plait après on va voir si on peut réflechir Link to comment Share on other sites More sharing options...
Bruce-b Posted May 30, 2007 Author Share Posted May 30, 2007 alors, il me faudrait : la réponse à lorinc, le modèle de la carte et les perfs de ta machine (proc, ram, etc) , la version de mandriva (Spring je suppose ?) et miroirs installés (backports ou pas ? plf ou pas ?), tu as installé le drivers ati de qui ? mandriva, plf ? un ati ou un dkms-ati ? compilé à partir des sources ? la réponse de "rpm -q ati" ou "rpm -q dkms-ati" à faire dans une console en root s'il te plait après on va voir si on peut réflechir Bon, j'ai pas mon PC sous la main, je complèterai plus tard, mais je peux déjà dire ceci: - Mandriva 2007.1 Spring version 32 bit - CG ATI X800 GTO 16 256 Mo de powercolor en PCI-e - Derniers drivers fglrx de chez ati (8.35.6) - Proc AMD 64X2 4200+ - 1.5 Go de RAM (RAM 2*512 + 2*256 DDR400 Kingston en dual channel) - CM Gigabyte GA-K8NF9 ultra (nForce4) En fait, je pense avoir le bug n° 29864 Link to comment Share on other sites More sharing options...
Scaramouche Posted May 31, 2007 Share Posted May 31, 2007 tu as testé ce que préconise fcrozat ? try using fglrx driver with metisse, r300 drivers are known to have problems. Link to comment Share on other sites More sharing options...
Bruce-b Posted May 31, 2007 Author Share Posted May 31, 2007 tu as testé ce que préconise fcrozat ?try using fglrx driver with metisse, r300 drivers are known to have problems. pas la peine, car comme je l'ai dis, j'utilise deja les dernier driver fglrx d'ati 8.35.6 sinon, voici la suite des infos demandées: [root@localhost pascal]# rpm -q ati le paquetage ati n'est pas installé [root@localhost pascal]# uname -a Linux localhost 2.6.17-14mdv #1 SMP Wed May 9 21:11:43 MDT 2007 i686 AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ GNU/Linux [root@localhost pascal]# rpm -q dkms-ati le paquetage dkms-ati n'est pas installé et la liste des mirroirs installés: [root@localhost pascal]# more /etc/urpmi/urpmi.cfg { } "Mandriva\ Linux\ -\ 2007.1\ (Free)\ -\ Installer" removable://media/cdrom/i586/media/main { ignore key-ids: 70771ff3 media_info_dir: media_info removable: /dev/hdb static } "Mandriva\ Linux\ -\ 2007.1\ (Free)\ -\ Installer"\ (contrib) removable://media/cdrom/i586/media/contrib { ignore key-ids: 78d019f5 media_info_dir: media_info removable: /dev/hdb static } main ftp://ftp.proxad.net/pub/Distributions_Linux/MandrivaLinux/official/2007.1/i586/media/main/release { hdlist key-ids: 70771ff3 media_info_dir: media_info } main_updates ftp://ftp.proxad.net/pub/Distributions_Linux/MandrivaLinux/official/2007.1/i586/media/main/updates { hdlist key-ids: 22458a98 media_info_dir: media_info update } main_backports ftp://ftp.proxad.net/pub/Distributions_Linux/MandrivaLinux/official/2007.1/i586/media/main/backports { hdlist media_info_dir: media_info } contrib ftp://ftp.proxad.net/pub/Distributions_Linux/MandrivaLinux/official/2007.1/i586/media/contrib/release { hdlist key-ids: 78d019f5 media_info_dir: media_info } contrib_updates ftp://ftp.proxad.net/pub/Distributions_Linux/MandrivaLinux/official/2007.1/i586/media/contrib/updates { hdlist key-ids: 26752624 media_info_dir: media_info update } contrib_backports ftp://ftp.proxad.net/pub/Distributions_Linux/MandrivaLinux/official/2007.1/i586/media/contrib/backports { hdlist media_info_dir: media_info } non-free ftp://ftp.proxad.net/pub/Distributions_Linux/MandrivaLinux/official/2007.1/i586/media/non-free/release { hdlist key-ids: 70771ff3 media_info_dir: media_info } non-free_updates ftp://ftp.proxad.net/pub/Distributions_Linux/MandrivaLinux/official/2007.1/i586/media/non-free/updates { hdlist media_info_dir: media_info update } plf-free ftp://ftp.free.fr/pub/Distributions_Linux/plf/mandriva/2007.1/free/release/binary/i586 { hdlist key-ids: caba22ae media_info_dir: . update } plf-nonfree ftp://ftp.free.fr/pub/Distributions_Linux/plf/mandriva/2007.1/non-free/release/binary/i586 { hdlist key-ids: caba22ae media_info_dir: . update } voila, si tu as besoin d'autres chose, hesite pas Link to comment Share on other sites More sharing options...
Scaramouche Posted June 1, 2007 Share Posted June 1, 2007 si je comprend bien tu as pas installé les rpm ati de mandriva ou plf ? et tu as essayé avec ? P.S. : en plf aussi y'a des backport il me semble Link to comment Share on other sites More sharing options...
Bruce-b Posted June 10, 2007 Author Share Posted June 10, 2007 non, j'ai pas essayé avec les rpm, seulement le .run de ati. D'ailleurs, cela ne fonctionne pas non plus avec les drivers de juin 8.37.6, voici mon .xsession-errors lorsque metisse tente de démarrer: [pascal@localhost ~]$ cat xsession.save /etc/X11/gdm/PreSession/Default: Registering your session with wtmp and utmp /etc/X11/gdm/PreSession/Default: running: /usr/bin/sessreg -a -w /var/log/wtmp -u /var/run/utmp -x "/var/lib/gdm/:0.Xservers" -h "" -l ":0" "pascal" /etc/X11/gdm/Xsession: Beginning session setup... /etc/X11/gdm/Xsession: Setup done, will execute: /etc/X11/xdm/Xsession KDE /etc/X11/Xsession: line 135: 7243 Erreur de segmentation $COMPOSITING_SERVER $COMPOSITING_SERVER_DISPLAY $COMPOSITING_SERVER_ARGS INFO: imwheel started (pid=7262) Could not open display, check shell DISPLAY variable, and export or setenv it! Error opening display xset: unable to open display ":1" xsetroot: unable to open display ':1' xmodmap: unable to open display ':1' xmodmap: unable to open display ':1' startkde: Starting up... ksplash: cannot connect to X server :1 xprop: unable to open display ':1' usage: xprop [-options ...] [[format [dformat]] atom] ... where options include: -grammar print out full grammar for command line -display host:dpy the X server to contact -id id resource id of window to examine -name name name of window to examine -font name name of font to examine -remove propname remove a property -set propname value set a property to a given value -root examine the root window -len n display at most n bytes of any property -notype do not display the type field -fs filename where to look for formats for properties -frame don't ignore window manager frames -f propname format [dformat] formats to use for property of given name -spy examine window properties forever kdeinit: Can't connect to the X Server. kdeinit: Might not terminate at end of session. kded: cannot connect to X server :1 DCOP aborting call from 'anonymous-7375' to 'kded' kded: ERROR: Communication problem with kded, it probably crashed. kcminit_startup: cannot connect to X server :1 ksmserver: cannot connect to X server :1 startkde: Shutting down... klauncher: Exiting on signal 1 startkde: Running shutdown scripts... xprop: unable to open display ':1' usage: xprop [-options ...] [[format [dformat]] atom] ... where options include: -grammar print out full grammar for command line -display host:dpy the X server to contact -id id resource id of window to examine -name name name of window to examine -font name name of font to examine -remove propname remove a property -set propname value set a property to a given value -root examine the root window -len n display at most n bytes of any property -notype do not display the type field -fs filename where to look for formats for properties -frame don't ignore window manager frames -f propname format [dformat] formats to use for property of given name -spy examine window properties forever startkde: Done. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.