You are not logged in.

#1 2011-12-30 04:19:06

Zarcjap
Member
Registered: 2011-06-28
Posts: 29

[SOLVED] AMD/ATI Drivers crashing on startx

I ordered parts to build a new HTPC that just arrived today. I built it and got arch up and running without much trouble but I hit a snag when I started trying to get X up and running (isn't this always when things seems to go wrong? lol) The board has an AMD E350 with Radeon HD 6310 graphics and from things I've read around the web, I'm going to need proprietary drivers to get good smooth HD playback. I followed instructions on the ATI Catalyst page of the Arch Wiki and added

[catalyst]
Server = http://catalyst.apocalypsus.net/repo/catalyst/$arch

to my /etc/pacman.conf file then installed all the drivers through pacman. Now when I run startx i get

(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:1:1) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:17:0) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:18:0) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:18:2) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:19:0) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:19:2) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:0) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:1) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:2) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:3) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:4) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:5) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:21:0) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:21:1) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:21:2) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:21:3) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:22:0) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:22:2) found
(EE) fglrx(0): atiddxDriScreenInit failed, GPS not been initialized.
(EE) fglrx(0): XMM failed to open CMMQS connection.(EE) fglrx(0):
(EE) fglrx(0): XMM failed to initialize
[glesx] __glESXExtensionInit: No GL ES2.0 capable screen found!

but as long as my .xinitrc file has something like

exec xterm

it will still run. However when i try running xbmc by changing .xinitrc to

exec xbmc

it crashes with all the same error message above with the addition of

X Error of failed request:  BadRequest (invalid request code or no such operation)
  Major opcode of failed request:  139 (ATIFGLEXTENSION)
  Minor opcode of failed request:  66 ()
  Serial number of failed request:  13
  Current serial number in output stream:  13
XBMC needs hardware accelerated OpenGL rendering.
Install an appropriate graphics driver.

Please consult XBMC Wiki for supported hardware
http://xbmc.org/wiki/?title=Supported_hardware

I did a quick Google and also searched on the forum but didn't see anything relevant to my card so I was wondering if anyone else could point me in the right direction.
Thanks

Last edited by Zarcjap (2011-12-30 11:21:24)

Offline

#2 2011-12-30 10:40:39

ChemBro
Member
Registered: 2008-10-22
Posts: 679

Re: [SOLVED] AMD/ATI Drivers crashing on startx

Well, I don't have a solution, but did you forget to put "nomodeset" in grub or "fglrx" in the modules section in /etc/rc.conf? These are two common mistakes, so I want to be sure, that at least these two have nothing to do with your problem.

Last edited by ChemBro (2011-12-30 10:40:51)

Offline

#3 2011-12-30 10:54:42

Zarcjap
Member
Registered: 2011-06-28
Posts: 29

Re: [SOLVED] AMD/ATI Drivers crashing on startx

I actually hadn't done either. I just did both and rebooted and xbmc opened no problem! thanks. I didn't know I needed to manually add flgrx to the rc.conf file.
Also what exactly does adding "nomodset" to grub do?

Also running startx still gives me this:

(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:1:1) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:17:0) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:18:0) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:18:2) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:19:0) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:19:2) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:0) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:1) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:2) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:3) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:4) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:20:5) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:21:0) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:21:1) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:21:2) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:21:3) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:22:0) found
(WW) fglrx: No matching Device section for instance (BusID PCI:0@0:22:2) found
[-     XMM_GLX] [I ]glesxXvInit Configureable RGBOutputColorRange

It is working but all those warnings make me nervous like somethings gunna break lol.

Last edited by Zarcjap (2011-12-30 10:57:01)

Offline

#4 2011-12-30 22:01:06

ChemBro
Member
Registered: 2008-10-22
Posts: 679

Re: [SOLVED] AMD/ATI Drivers crashing on startx

Zarcjap wrote:

Also what exactly does adding "nomodset" to grub do?

Says to the kernel to not start in KMS (kernel mode setting)? Or to not start the open source driver radeon? One of them (maybe both).

And I would ignore the warning. I have them, too, though not that much. It's just for checking something (it finds the correct BusID, as you can see [aka working xserver]).

Offline

Board footer

Powered by FluxBB