Arch won't start , probably due to Catalyst

Question

Hello,
I have a small (Big) problem on my computer , that probleme made me whype my HDD thrice for now , because like said in the title my ARCH setup won't start , so here is the problem : The loading is stuck after those few lines :
//Talking about the number of blocks in /dev/sda3
[ OK ]Reached dhcpcd on eno1
[ OK ]Reached target Multi-user system
[ OK ]Reached target Graphical Interface
[ OK ]Reached target Network
The things I know about this problem :
-First happened when installing Catalyst
-I did a very small install with the base / base-devel / skype / gnome / gnome-extra / xorg and the Unoficial catalyst repo (I think I forget nothing ...)
-It happened with or without xf86-video-ati
-It is stuck there. It won't let me do anything
-Due to the xorg116 bug with catalyst I used the unofficial xorg115 repo each time
Unfortunately each time I did a
systemctl enable gdm
so I can't do any test.
Anyone has a clue of what is happening ? I tried using lxdm for example , but since it did not work very fast , I did not use it , and I had forgoten to add Catalyst that time.
So should I stick with the xf86-video-ati , use lxdm (or an other display manager) or do another thing ?
Last edited by traxys (2014-08-25 16:43:54)

Answer 1

So know , with tying to use the startx command I think I can say that the problem is not GNOME but the drivers ....
Because startx crashed , and the log (http://pastebin.com/tTndn5ep) complains about a "dri3" module that is not found (look at about line 610)
This is a more problematic thing I think
And by the way I don't have the package xorg-twm
EDIT : just saw this :
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x56) [0x58f186]
(EE) 1: /usr/bin/X (0x400000+0x192fc9) [0x592fc9]
(EE) 2: /usr/lib/libpthread.so.0 (0x7f7ef5074000+0xf4b0) [0x7f7ef50834b0]
(EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f7ef08b1000+0x155b5) [0x7f7ef08c65b5]
(EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7f7ef08b1000+0x127dcf) [0x7f7ef09d8dcf]
(EE) 5: /usr/lib/xorg/modules/drivers/fglrx_drv.so (xdl_xs115_atiddxPxFreeScreen+0x2e) [0x7f7ef13990ee]
(EE) 6: /usr/lib/xorg/modules/drivers/fglrx_drv.so (xdl_xs115_atiddxFreeScreen+0x64) [0x7f7ef13777d4]
(EE) 7: /usr/bin/X (xf86DeleteScreen+0x5a) [0x47fe8a]
(EE) 8: /usr/bin/X (InitOutput+0xacf) [0x47950f]
(EE) 9: /usr/bin/X (0x400000+0x3ab2a) [0x43ab2a]
(EE) 10: /usr/lib/libc.so.6 (__libc_start_main+0xf0) [0x7f7ef3cde000]
(EE) 11: /usr/bin/X (0x400000+0x250fe) [0x4250fe]
(EE)
(EE) Segmentation fault at address 0x14
(EE)
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
Saw ther is an interaction between intel and ati that goes nuts ?
Last edited by traxys (2014-08-25 19:31:59)