| View previous topic :: View next topic |
| Author |
Message |
onevision
n00b
Joined: 06 Sep 2011
Posts: 32
Location: Draper, Utah
|
 Posted: Thu Jul 26, 2012 11:53 pm Post subject: X segmentation fault - ATI Turks Radeon HD 7500 Series |
 |
|
So I've got my brand new Dell XPS 8500 computer that I'm setting up for work. I've installed Gentoo countless times, and if trouble came up been able to work through it, including finding some pretty tricky drivers to get odd hardware working. This problem however is a bit beyond me. Everything installed fine, but I can't seem to get my X running. At first it didn't like that the KMS modesetting wasn't enabled, so after some reading in
http://www.gentoo.org/doc/en/xorg-config.xml?style=printable
and
http://en.gentoo-wiki.com/wiki/Radeon
and
http://wiki.gentoo.org/wiki/Radeon
I tried a number of thing, all of which left me in different places, but failing. Not quite sure why, but the ati-drivers was installed (probably because I had fglrx as a second entry in VIDEO_CARDS), but I unmerged that. Found the correct firmware drivers (at least I believe they are correct), which wasn't included in either the linux-firmware or radeon-ucode packages. Just to make sure everything was clean I did a make clean and make mrproper before compiling the kernel. Here are the relevant settings:
Device Drivers --->
Generic Driver Options --->
[*] Include in-kernel firmware blobs in kernel binary
(radeon/BARTS_mc.bin radeon/BARTS_me.bin radeon/BARTS_pfp.bin radeon/BTC_rlc.bin radeon/CAICOS_mc.bin radeon/CAICOS_me.bin radeon/CAICOS_pfp.bin radeon/CAICOS_rlc.bin radeon/TURKS_mc.bin radeon/TURKS_me.bin radeon/TURKS_pfp.bin)
(firmware) Firmware blobs root directory
Graphics support --->
<M> Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) --->
<M> ATI Radeon
[*] Enable modesetting on radeon by default - NEW DRIVER
and my make.conf settings are:
INPUT_DEVICES="evdev mouse keyboard"
VIDEO_CARDS="radeon"
It all compiled fine, but when I try to start xdm I get the following error in the Xorg.0.log:
[ 58.455] (II) RADEON: Driver for ATI Radeon chipsets:
ATI Radeon Mobility X600 (M24) 3150 (PCIE), ATI FireMV 2400 (PCI),
...
[ 58.581] (II) RADEON(0): Output DVI-0 connected
[ 58.581] (II) RADEON(0): Using exact sizes for initial modes
[ 58.581] (II) RADEON(0): Output DVI-0 using initial mode 1920x1080
[ 58.581] (II) RADEON(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 58.581] (II) RADEON(0): mem size init: gart size :1fdff000 vram size: s:40000000 visible:f7d7000
[ 58.581] (II) RADEON(0): EXA: Driver will allow EXA pixmaps in VRAM
[ 58.581] (==) RADEON(0): DPI set to (96, 96)
[ 58.581] (II) Loading sub module "fb"
[ 58.581] (II) LoadModule: "fb"
[ 58.581] (II) Loading /usr/lib64/xorg/modules/libfb.so
[ 58.581] (II) Module fb: vendor="X.Org Foundation"
[ 58.581] compiled for 1.12.2, module version = 1.0.0
[ 58.581] ABI class: X.Org ANSI C Emulation, version 0.4
[ 58.581] (II) Loading sub module "ramdac"
[ 58.581] (II) LoadModule: "ramdac"
[ 58.581] (II) Module "ramdac" already built-in
[ 58.581] (--) Depth 24 pixmap format is 32 bpp
[ 58.581] (II) RADEON(0): [DRI2] Setup complete
[ 58.581] (II) RADEON(0): [DRI2] DRI driver: r600
[ 58.581] (II) RADEON(0): [DRI2] VDPAU driver: r600
[ 58.581]
[ 58.582] Backtrace:
[ 58.582] 0: /usr/bin/X (xorg_backtrace+0x36) [0x56dbb6]
[ 58.582] 1: /usr/bin/X (0x400000+0x1716a9) [0x5716a9]
[ 58.582] 2: /lib64/libpthread.so.0 (0x7ff08b6f7000+0x10420) [0x7ff08b707420]
[ 58.582] 3: /usr/lib64/xorg/modules/drivers/radeon_drv.so (0x7ff088549000+0xe229b) [0x7ff08862b29b]
[ 58.582] 4: /usr/bin/X (AddScreen+0x1a8) [0x436508]
[ 58.582] 5: /usr/bin/X (InitOutput+0x294) [0x475f94]
[ 58.582] 6: /usr/bin/X (0x400000+0x24d03) [0x424d03]
[ 58.582] 7: /lib64/libc.so.6 (__libc_start_main+0xfd) [0x7ff08a62b2ad]
[ 58.582] 8: /usr/bin/X (0x400000+0x24a69) [0x424a69]
[ 58.582]
[ 58.582] Segmentation fault at address (nil)
[ 58.582]
Fatal server error:
[ 58.582] Caught signal 11 (Segmentation fault). Server aborting
[ 58.582]
I'm just not clear on exactly what or where it's failing exactly. The graphics card appears to have loaded correctly and completed, but then X chokes and does the fault. I've tried re-installing xorg-server xorg-drivers xf86-video-ati to see if that would help, but it had no effect. Running revdep-rebuild finds no problems and nothing shows up missing or needing changes with emerge -uDvp --newuse world
Am I just missing the forest through the trees here? This is my first graphics card that uses an HDMI output, which better be the output for the second monitor, but other than that I don't see what is wrong. I suppose I could try the closed source drivers, but it doesn't seem like the drivers are what's failing. Any ideas? Any help would be greatly appreciated, thanks.
-Davey |
|
| Back to top |
|
 |
BillWho
Veteran
Joined: 03 Mar 2012
Posts: 1600
Location: US
|
| Posted: Fri Jul 27, 2012 2:49 am Post subject: |
|
|
onevision,
Try
-*- Userspace firmware loading support │ │
│ │ [*] Include in-kernel firmware blobs in kernel binary │ │
│ │ () External firmware blobs to build into the kernel binary │ │
You should only need evdev for INPUT_DEVICES in make.conf, but the addition of mouse and keyboard won't really hurt anything.
One last thing is did you emerge sys-kernel/linux-firmware  The compile probably would have failed without it, but just to cover all the bases 
_________________
Good luck 
Since installing gentoo, my life has become one long emerge  |
|
| Back to top |
|
|
onevision
n00b
Joined: 06 Sep 2011
Posts: 32
Location: Draper, Utah
|
| Posted: Fri Jul 27, 2012 3:24 pm Post subject: |
|
|
Yeah, I actually copied certain elements from other installs, so the 'mouse' and 'keyboard' were from pre-evdev installs, but I figured it wouldn't hurt and might be handy to have as a backup method. Sort of had the same idea with VIDEO_DEVICES in that I originally had 'radeon fglrx ati', but after starting to have problems, I removed the last two and recompiled with --newuse to world, as well as manually forced xorg-server xorg-drivers and couple other to reinstall.
I originally emerged radeon-ucode, but then unmerged it and emerged linux-firmware - neither of which actually contained the drivers I needed, which I find funny, since if you click on the homepage link for that package it takes you to the FTP directory where all the driver files are found. So I just grabbed the files from there and placed them into the firmware directory.
I'm just not sure if the problem lies with the video driver or with the X install. It's unclear to me which is the problem, but if it's X, then that would suck spending all day dicking around with the radeon drivers from the closed source method. Thanks for the feedback and let me know if anything else jumps out at you as wrong. 
-Davey |
|
| Back to top |
|
|
Ant P.
Watchman
Joined: 18 Apr 2009
Posts: 6920
|
| Posted: Fri Jul 27, 2012 7:35 pm Post subject: |
|
|
You should leave radeon-ucode installed. It does have the correct files:
| Code: | ~ $ cave contents radeon-ucode | egrep 'BARTS|BTC|CAICOS|TURKS'
/lib64/firmware/radeon/BARTS_me.bin
/lib64/firmware/radeon/BTC_rlc.bin
/lib64/firmware/radeon/CAICOS_me.bin
/lib64/firmware/radeon/TURKS_me.bin
/lib64/firmware/radeon/BARTS_mc.bin
/lib64/firmware/radeon/BARTS_pfp.bin
/lib64/firmware/radeon/CAICOS_mc.bin
/lib64/firmware/radeon/CAICOS_pfp.bin
/lib64/firmware/radeon/TURKS_mc.bin
/lib64/firmware/radeon/TURKS_pfp.bin |
|
|
| Back to top |
|
|
onevision
n00b
Joined: 06 Sep 2011
Posts: 32
Location: Draper, Utah
|
| Posted: Fri Jul 27, 2012 8:48 pm Post subject: Good Advice |
|
|
That sounds reasonable, and also led me to find out why I thought the drivers weren't there. I thought the the drivers would install the files into the 'firmware' directory located in '/usr/src/linux/', but it doesn't, it installs them into '/lib/firmware'. At any rate, I switch from using linux-firmware (which had a lot of additional drivers for various things, including radeon) back to just using radeon-ucode. I also adjusted the kernel configuration to use absolute path call and to point to that correct directory. I recompiled (after a make clean and make mrproper), but the results are still the same.
-Davey |
|
| Back to top |
|
|
BillWho
Veteran
Joined: 03 Mar 2012
Posts: 1600
Location: US
|
| Posted: Fri Jul 27, 2012 9:19 pm Post subject: |
|
|
onevision,
Just for the he#! of it try make firmware_install
_________________
Good luck
Since installing gentoo, my life has become one long emerge |
|
| Back to top |
|
|
onevision
n00b
Joined: 06 Sep 2011
Posts: 32
Location: Draper, Utah
|
| Posted: Fri Jul 27, 2012 9:27 pm Post subject: |
|
|
Sure thing. Can't say that I've ever used that option before, but couldn't hurt. The output was interesting.
linux # make firmware_install
IHEX firmware/3com/3C359.bin
MKDIR /lib/firmware/3com/
INSTALL /lib/firmware/3com/3C359.bin
IHEX firmware/acenic/tg1.bin
MKDIR /lib/firmware/acenic/
INSTALL /lib/firmware/acenic/tg1.bin
IHEX firmware/acenic/tg2.bin
INSTALL /lib/firmware/acenic/tg2.bin
IHEX firmware/adaptec/starfire_rx.bin
MKDIR /lib/firmware/adaptec/
INSTALL /lib/firmware/adaptec/starfire_rx.bin
IHEX firmware/adaptec/starfire_tx.bin
INSTALL /lib/firmware/adaptec/starfire_tx.bin
IHEX firmware/dsp56k/bootstrap.bin
MKDIR /lib/firmware/dsp56k/
INSTALL /lib/firmware/dsp56k/bootstrap.bin
HOSTCC firmware/ihex2fw
IHEX2FW firmware/atmsar11.fw
INSTALL /lib/firmware/atmsar11.fw
IHEX firmware/bnx2x/bnx2x-e1-6.2.9.0.fw
MKDIR /lib/firmware/bnx2x/
INSTALL /lib/firmware/bnx2x/bnx2x-e1-6.2.9.0.fw
IHEX firmware/bnx2x/bnx2x-e1h-6.2.9.0.fw
INSTALL /lib/firmware/bnx2x/bnx2x-e1h-6.2.9.0.fw
IHEX firmware/bnx2x/bnx2x-e2-6.2.9.0.fw
INSTALL /lib/firmware/bnx2x/bnx2x-e2-6.2.9.0.fw
IHEX firmware/bnx2/bnx2-mips-09-6.2.1a.fw
MKDIR /lib/firmware/bnx2/
INSTALL /lib/firmware/bnx2/bnx2-mips-09-6.2.1a.fw
IHEX firmware/bnx2/bnx2-rv2p-09-6.0.17.fw
INSTALL /lib/firmware/bnx2/bnx2-rv2p-09-6.0.17.fw
IHEX firmware/bnx2/bnx2-rv2p-09ax-6.0.17.fw
INSTALL /lib/firmware/bnx2/bnx2-rv2p-09ax-6.0.17.fw
IHEX firmware/bnx2/bnx2-mips-06-6.2.1.fw
INSTALL /lib/firmware/bnx2/bnx2-mips-06-6.2.1.fw
IHEX firmware/bnx2/bnx2-rv2p-06-6.0.15.fw
INSTALL /lib/firmware/bnx2/bnx2-rv2p-06-6.0.15.fw
IHEX firmware/sun/cassini.bin
MKDIR /lib/firmware/sun/
INSTALL /lib/firmware/sun/cassini.bin
IHEX firmware/intelliport2.bin
INSTALL /lib/firmware/intelliport2.bin
IHEX firmware/cxgb3/t3b_psram-1.1.0.bin
MKDIR /lib/firmware/cxgb3/
INSTALL /lib/firmware/cxgb3/t3b_psram-1.1.0.bin
IHEX firmware/cxgb3/t3c_psram-1.1.0.bin
INSTALL /lib/firmware/cxgb3/t3c_psram-1.1.0.bin
IHEX firmware/cxgb3/t3fw-7.10.0.bin
INSTALL /lib/firmware/cxgb3/t3fw-7.10.0.bin
IHEX firmware/cxgb3/ael2005_opt_edc.bin
INSTALL /lib/firmware/cxgb3/ael2005_opt_edc.bin
IHEX firmware/cxgb3/ael2005_twx_edc.bin
INSTALL /lib/firmware/cxgb3/ael2005_twx_edc.bin
IHEX firmware/cxgb3/ael2020_twx_edc.bin
INSTALL /lib/firmware/cxgb3/ael2020_twx_edc.bin
H16TOFW firmware/matrox/g200_warp.fw
MKDIR /lib/firmware/matrox/
INSTALL /lib/firmware/matrox/g200_warp.fw
H16TOFW firmware/matrox/g400_warp.fw
INSTALL /lib/firmware/matrox/g400_warp.fw
IHEX firmware/r128/r128_cce.bin
MKDIR /lib/firmware/r128/
INSTALL /lib/firmware/r128/r128_cce.bin
IHEX firmware/av7110/bootcode.bin
MKDIR /lib/firmware/av7110/
INSTALL /lib/firmware/av7110/bootcode.bin
IHEX firmware/ttusb-budget/dspbootcode.bin
MKDIR /lib/firmware/ttusb-budget/
INSTALL /lib/firmware/ttusb-budget/dspbootcode.bin
IHEX firmware/e100/d101m_ucode.bin
MKDIR /lib/firmware/e100/
INSTALL /lib/firmware/e100/d101m_ucode.bin
IHEX firmware/e100/d101s_ucode.bin
INSTALL /lib/firmware/e100/d101s_ucode.bin
IHEX firmware/e100/d102e_ucode.bin
INSTALL /lib/firmware/e100/d102e_ucode.bin
IHEX firmware/myricom/lanai.bin
MKDIR /lib/firmware/myricom/
INSTALL /lib/firmware/myricom/lanai.bin
IHEX firmware/cis/LA-PCM.cis
MKDIR /lib/firmware/cis/
INSTALL /lib/firmware/cis/LA-PCM.cis
IHEX firmware/cis/PCMLM28.cis
INSTALL /lib/firmware/cis/PCMLM28.cis
IHEX firmware/cis/DP83903.cis
INSTALL /lib/firmware/cis/DP83903.cis
IHEX firmware/cis/NE2K.cis
INSTALL /lib/firmware/cis/NE2K.cis
IHEX firmware/cis/tamarack.cis
INSTALL /lib/firmware/cis/tamarack.cis
IHEX firmware/cis/PE-200.cis
INSTALL /lib/firmware/cis/PE-200.cis
IHEX firmware/cis/PE520.cis
INSTALL /lib/firmware/cis/PE520.cis
IHEX firmware/cis/3CXEM556.cis
INSTALL /lib/firmware/cis/3CXEM556.cis
IHEX firmware/cis/3CCFEM556.cis
INSTALL /lib/firmware/cis/3CCFEM556.cis
IHEX firmware/cis/MT5634ZLX.cis
INSTALL /lib/firmware/cis/MT5634ZLX.cis
IHEX firmware/cis/RS-COM-2P.cis
INSTALL /lib/firmware/cis/RS-COM-2P.cis
IHEX firmware/cis/COMpad2.cis
INSTALL /lib/firmware/cis/COMpad2.cis
IHEX firmware/cis/COMpad4.cis
INSTALL /lib/firmware/cis/COMpad4.cis
IHEX firmware/cis/SW_555_SER.cis
INSTALL /lib/firmware/cis/SW_555_SER.cis
IHEX firmware/cis/SW_7xx_SER.cis
INSTALL /lib/firmware/cis/SW_7xx_SER.cis
IHEX firmware/cis/SW_8xx_SER.cis
INSTALL /lib/firmware/cis/SW_8xx_SER.cis
IHEX firmware/ositech/Xilinx7OD.bin
MKDIR /lib/firmware/ositech/
INSTALL /lib/firmware/ositech/Xilinx7OD.bin
IHEX firmware/advansys/mcode.bin
MKDIR /lib/firmware/advansys/
INSTALL /lib/firmware/advansys/mcode.bin
IHEX firmware/advansys/38C1600.bin
INSTALL /lib/firmware/advansys/38C1600.bin
IHEX firmware/advansys/3550.bin
INSTALL /lib/firmware/advansys/3550.bin
IHEX firmware/advansys/38C0800.bin
INSTALL /lib/firmware/advansys/38C0800.bin
IHEX firmware/qlogic/1040.bin
MKDIR /lib/firmware/qlogic/
INSTALL /lib/firmware/qlogic/1040.bin
IHEX firmware/qlogic/1280.bin
INSTALL /lib/firmware/qlogic/1280.bin
IHEX firmware/qlogic/12160.bin
INSTALL /lib/firmware/qlogic/12160.bin
IHEX firmware/qlogic/isp1000.bin
INSTALL /lib/firmware/qlogic/isp1000.bin
IHEX firmware/qlogic/sd7220.fw
INSTALL /lib/firmware/qlogic/sd7220.fw
IHEX firmware/tr_smctr.bin
INSTALL /lib/firmware/tr_smctr.bin
IHEX firmware/korg/k1212.dsp
MKDIR /lib/firmware/korg/
INSTALL /lib/firmware/korg/k1212.dsp
IHEX firmware/ess/maestro3_assp_kernel.fw
MKDIR /lib/firmware/ess/
INSTALL /lib/firmware/ess/maestro3_assp_kernel.fw
IHEX firmware/ess/maestro3_assp_minisrc.fw
INSTALL /lib/firmware/ess/maestro3_assp_minisrc.fw
IHEX firmware/sb16/mulaw_main.csp
MKDIR /lib/firmware/sb16/
INSTALL /lib/firmware/sb16/mulaw_main.csp
IHEX firmware/sb16/alaw_main.csp
INSTALL /lib/firmware/sb16/alaw_main.csp
IHEX firmware/sb16/ima_adpcm_init.csp
INSTALL /lib/firmware/sb16/ima_adpcm_init.csp
IHEX firmware/sb16/ima_adpcm_playback.csp
INSTALL /lib/firmware/sb16/ima_adpcm_playback.csp
IHEX firmware/sb16/ima_adpcm_capture.csp
INSTALL /lib/firmware/sb16/ima_adpcm_capture.csp
IHEX firmware/yamaha/ds1_ctrl.fw
MKDIR /lib/firmware/yamaha/
INSTALL /lib/firmware/yamaha/ds1_ctrl.fw
IHEX firmware/yamaha/ds1_dsp.fw
INSTALL /lib/firmware/yamaha/ds1_dsp.fw
IHEX firmware/yamaha/ds1e_ctrl.fw
INSTALL /lib/firmware/yamaha/ds1e_ctrl.fw
IHEX firmware/yamaha/yss225_registers.bin
INSTALL /lib/firmware/yamaha/yss225_registers.bin
IHEX firmware/tehuti/bdx.bin
MKDIR /lib/firmware/tehuti/
INSTALL /lib/firmware/tehuti/bdx.bin
IHEX firmware/tigon/tg3.bin
MKDIR /lib/firmware/tigon/
INSTALL /lib/firmware/tigon/tg3.bin
IHEX firmware/tigon/tg3_tso.bin
INSTALL /lib/firmware/tigon/tg3_tso.bin
IHEX firmware/tigon/tg3_tso5.bin
INSTALL /lib/firmware/tigon/tg3_tso5.bin
IHEX firmware/3com/typhoon.bin
INSTALL /lib/firmware/3com/typhoon.bin
IHEX2FW firmware/dabusb/firmware.fw
MKDIR /lib/firmware/dabusb/
INSTALL /lib/firmware/dabusb/firmware.fw
IHEX firmware/dabusb/bitstream.bin
INSTALL /lib/firmware/dabusb/bitstream.bin
IHEX2FW firmware/emi26/loader.fw
MKDIR /lib/firmware/emi26/
INSTALL /lib/firmware/emi26/loader.fw
IHEX2FW firmware/emi26/firmware.fw
INSTALL /lib/firmware/emi26/firmware.fw
IHEX2FW firmware/emi26/bitstream.fw
INSTALL /lib/firmware/emi26/bitstream.fw
IHEX2FW firmware/emi62/loader.fw
MKDIR /lib/firmware/emi62/
INSTALL /lib/firmware/emi62/loader.fw
IHEX2FW firmware/emi62/bitstream.fw
INSTALL /lib/firmware/emi62/bitstream.fw
IHEX2FW firmware/emi62/spdif.fw
INSTALL /lib/firmware/emi62/spdif.fw
IHEX2FW firmware/emi62/midi.fw
INSTALL /lib/firmware/emi62/midi.fw
IHEX firmware/kaweth/new_code.bin
MKDIR /lib/firmware/kaweth/
INSTALL /lib/firmware/kaweth/new_code.bin
IHEX firmware/kaweth/trigger_code.bin
INSTALL /lib/firmware/kaweth/trigger_code.bin
IHEX firmware/kaweth/new_code_fix.bin
INSTALL /lib/firmware/kaweth/new_code_fix.bin
IHEX firmware/kaweth/trigger_code_fix.bin
INSTALL /lib/firmware/kaweth/trigger_code_fix.bin
IHEX2FW firmware/keyspan/mpr.fw
MKDIR /lib/firmware/keyspan/
INSTALL /lib/firmware/keyspan/mpr.fw
IHEX2FW firmware/keyspan/usa18x.fw
INSTALL /lib/firmware/keyspan/usa18x.fw
IHEX2FW firmware/keyspan/usa19.fw
INSTALL /lib/firmware/keyspan/usa19.fw
IHEX2FW firmware/keyspan/usa19qi.fw
INSTALL /lib/firmware/keyspan/usa19qi.fw
IHEX2FW firmware/keyspan/usa19qw.fw
INSTALL /lib/firmware/keyspan/usa19qw.fw
IHEX2FW firmware/keyspan/usa19w.fw
INSTALL /lib/firmware/keyspan/usa19w.fw
IHEX2FW firmware/keyspan/usa28.fw
INSTALL /lib/firmware/keyspan/usa28.fw
IHEX2FW firmware/keyspan/usa28xa.fw
INSTALL /lib/firmware/keyspan/usa28xa.fw
IHEX2FW firmware/keyspan/usa28xb.fw
INSTALL /lib/firmware/keyspan/usa28xb.fw
IHEX2FW firmware/keyspan/usa28x.fw
INSTALL /lib/firmware/keyspan/usa28x.fw
IHEX2FW firmware/keyspan/usa49w.fw
INSTALL /lib/firmware/keyspan/usa49w.fw
IHEX2FW firmware/keyspan/usa49wlc.fw
INSTALL /lib/firmware/keyspan/usa49wlc.fw
IHEX firmware/ti_3410.fw
INSTALL /lib/firmware/ti_3410.fw
IHEX firmware/ti_5052.fw
INSTALL /lib/firmware/ti_5052.fw
IHEX firmware/mts_cdma.fw
INSTALL /lib/firmware/mts_cdma.fw
IHEX firmware/mts_gsm.fw
INSTALL /lib/firmware/mts_gsm.fw
IHEX firmware/mts_edge.fw
INSTALL /lib/firmware/mts_edge.fw
H16TOFW firmware/edgeport/boot.fw
MKDIR /lib/firmware/edgeport/
INSTALL /lib/firmware/edgeport/boot.fw
H16TOFW firmware/edgeport/boot2.fw
INSTALL /lib/firmware/edgeport/boot2.fw
H16TOFW firmware/edgeport/down.fw
INSTALL /lib/firmware/edgeport/down.fw
H16TOFW firmware/edgeport/down2.fw
INSTALL /lib/firmware/edgeport/down2.fw
IHEX firmware/edgeport/down3.bin
INSTALL /lib/firmware/edgeport/down3.bin
IHEX2FW firmware/whiteheat_loader.fw
INSTALL /lib/firmware/whiteheat_loader.fw
IHEX2FW firmware/whiteheat.fw
INSTALL /lib/firmware/whiteheat.fw
IHEX2FW firmware/keyspan_pda/keyspan_pda.fw
MKDIR /lib/firmware/keyspan_pda/
INSTALL /lib/firmware/keyspan_pda/keyspan_pda.fw
IHEX2FW firmware/keyspan_pda/xircom_pgs.fw
INSTALL /lib/firmware/keyspan_pda/xircom_pgs.fw
H16TOFW firmware/vicam/firmware.fw
MKDIR /lib/firmware/vicam/
INSTALL /lib/firmware/vicam/firmware.fw
IHEX firmware/cpia2/stv0672_vp4.bin
MKDIR /lib/firmware/cpia2/
INSTALL /lib/firmware/cpia2/stv0672_vp4.bin
IHEX firmware/yam/1200.bin
MKDIR /lib/firmware/yam/
INSTALL /lib/firmware/yam/1200.bin
IHEX firmware/yam/9600.bin
INSTALL /lib/firmware/yam/9600.bin
A lot of drivers, none of which I believe I have set or need. Like I see several network card drivers, only I'm using r8169, which is set as a module and loads and connects fine. At any rate, I ran a make install after and rebooted the system (I'm assuming it would need that), but alas the end result is still the same. |
|
| Back to top |
|
|
BillWho
Veteran
Joined: 03 Mar 2012
Posts: 1600
Location: US
|
| Posted: Fri Jul 27, 2012 9:42 pm Post subject: |
|
|
onevision,
That's really odd - I only get the firmware for the video and wireless. I'll have to take a look at a couple of more things, but I'm getting low on ideas 
Maybe you have all those devices enabled that require firmware I stripped-out everything except for the specific devices in the machine.
_________________
Good luck
Since installing gentoo, my life has become one long emerge |
|
| Back to top |
|
|
onevision
n00b
Joined: 06 Sep 2011
Posts: 32
Location: Draper, Utah
|
| Posted: Fri Jul 27, 2012 10:36 pm Post subject: |
|
|
Yeah, by default when you open menuconfig, the kernel runs something like anaconda to scan your hardware and tries to pick the required options for you - which they have gotten that working very well. I does however auto-select a good number of unneeded modules and elements. Being that I was just trying to get up and running as quickly as possible (being a computer for work and all), I only quickly ran through the kernel config, cleaning up the obvious entries - like especially network adapters and SATA bus options. Some sections I just let be as is, thinking I could always come back later and make it lean then. Priority was just getting operational first, as I'm working on another computer right now that I brought in from home. It definitely has some extra elements to the kernel config though right now, but nothing that should be harmful, and it's all boot just fine - and working fine, other than choking on X
Yeah, I ran through a slew of possible causes to the problem before I posted here, and I too am getting near the end of things to try. I'm about ready to just pop the crappy Radeon X700 out of the my computer I brought in from home and plug that into this new machine, as that should just pop right up. Makes it nice that they are both ATI radeon cards, so changing the kernel config would be almost no change, and everything else would pretty much be the same as well. This is why I don't buy ATI cards anymore. |
|
| Back to top |
|
|
BillWho
Veteran
Joined: 03 Mar 2012
Posts: 1600
Location: US
|
| Posted: Fri Jul 27, 2012 11:05 pm Post subject: |
|
|
onevision,
What does lsmod|grep radeon show Mine is
| Code: | root@gentoo-gateway etc # lsmod|grep radeon
radeon 714053 2
drm_kms_helper 20972 1 radeon
ttm 51155 1 radeon
drm 182213 4 ttm,drm_kms_helper,radeon
cfbfillrect 2917 1 radeon
cfbimgblt 1849 1 radeon
cfbcopyarea 2921 1 radeon
i2c_algo_bit 4401 1 radeon
fb 46504 6 fbcon,drm_kms_helper,radeon,softcursor,tileblit,bitblit
|
_________________
Good luck
Since installing gentoo, my life has become one long emerge |
|
| Back to top |
|
|
jasn
Guru
Joined: 05 May 2005
Posts: 439
Location: Maryland, US
|
| Posted: Sat Jul 28, 2012 12:39 am Post subject: Re: X segmentation fault - ATI Turks Radeon HD 7500 Series |
|
|
| onevision wrote: | Device Drivers --->
Generic Driver Options --->
[*] Include in-kernel firmware blobs in kernel binary
(radeon/BARTS_mc.bin radeon/BARTS_me.bin radeon/BARTS_pfp.bin radeon/BTC_rlc.bin radeon/CAICOS_mc.bin radeon/CAICOS_me.bin radeon/CAICOS_pfp.bin radeon/CAICOS_rlc.bin radeon/TURKS_mc.bin radeon/TURKS_me.bin radeon/TURKS_pfp.bin)
(firmware) Firmware blobs root directory |
I don't build the firmware blobs into the kernel as described. I just install them by emerging sys-kernel/linux-firmware, and then when the system boots, it will load the appropriate blob from the firmware directory. If you're going to build the blobs into the kernel, I think that you're supposed to build the radeon modules in as well.
Good Luck.. |
|
| Back to top |
|
|
onevision
n00b
Joined: 06 Sep 2011
Posts: 32
Location: Draper, Utah
|
| Posted: Sat Jul 28, 2012 12:49 am Post subject: Good Call |
|
|
Now that is very interesting in a couple of different ways. Firstly, I'm not getting near the options loaded as you do.
# lsmod | grep radeon
radeon 783964 1
ttm 61686 1 radeon
drm_kms_helper 25498 1 radeon
drm 198441 3 radeon,ttm,drm_kms_helper
i2c_algo_bit 5120 1 radeon
And in addition to that, with doing a full lsmod I can see that for whatever reason it's still loading the fglrx module as well. That shouldn't even be installed, as I don't have the ati-drivers installed. I did however do a make clean, make mrproper, make clean and then copy the config file over before building the kernel. The fglrx module is the one from the closed source drivers isn't it?
# lsmod
Module Size Used by
fglrx 2588260 0
snd_hda_codec_hdmi 23249 2
ath9k 89524 0
snd_hda_codec_realtek 109331 1
ath9k_common 1834 1 ath9k
ath9k_hw 360425 2 ath9k,ath9k_common
r8169 48468 0
radeon 783964 1
ttm 61686 1 radeon
drm_kms_helper 25498 1 radeon
snd_hda_intel 22591 0
snd_hda_codec 79988 3 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel
drm 198441 3 radeon,ttm,drm_kms_helper
btusb 11320 0
mii 3843 1 r8169
i2c_algo_bit 5120 1 radeon
ath 14653 3 ath9k,ath9k_common,ath9k_hw
snd_hwdep 5830 1 snd_hda_codec
bluetooth 160958 1 btusb
Wonder why it is loading that up - even if it were installed, since it's not in my /etc/conf.d/modules. It does sort of auto load that though. Removing that module however doesn't change anything though, and even if I keep it active, I can't unload the radeon module as it's in use - at least the frame buffer part of it. When I do an eselect opengl list, all I see available is the xorg-x11 driver. Odd. The Xorg.0.log does show that the radeon driver successfully loaded though. Hummm, something definitely isn't right though.
- Davey |
|
| Back to top |
|
|
BillWho
Veteran
Joined: 03 Mar 2012
Posts: 1600
Location: US
|
| Posted: Sat Jul 28, 2012 1:04 am Post subject: |
|
|
onevision,
Eliminate anything to do with this -> fglrx 2588260 0
Its in your lsmod dump 
_________________
Good luck
Since installing gentoo, my life has become one long emerge |
|
| Back to top |
|
|
jasn
Guru
Joined: 05 May 2005
Posts: 439
Location: Maryland, US
|
| Posted: Sun Jul 29, 2012 5:13 pm Post subject: |
|
|
FWIW, this is what I learned when building ATI GPU driver support for the older generation Radeon 6970M hardware. Current config is;
| Code: | sys-kernel/gentoo-sources-3.5.0
x11-drivers/xf86-video-ati-6.14.6-r1
media-libs/mesa-8.1_rc1_pre20120724
x11-libs/libdrm-2.4.37 |
If your hardware is the newer Fusion hardware there's a possibility that the open source radeon driver doesn't correctly support the hardware yet, but I think it now does.
If you have previously installed the AMD proprietary drivers, there's a chance the fglrx module is still in your /lib/modules/ tree. If it's there, and the open source radeon driver is there as well, they'll both load, as they are on your system, and you won't be able to get working graphics going.
There are two ways of configuring the open source Radeon driver. One is to do it by configuring kernel drivers as <M> modules. In that case the system will autoload everything, including the firmware blob. So when you configure your kernel for radeon drivers as modules, you can't configure in-kernel firmware blobs. The second way of configuring the radeon drivers is with everything built-in. Firmware blobs and drivers.
I would suggest it's easier to configure things for auto-loading in case you don't know which firmware blob is the correct one for your GPU. For example, you state in your OP that you built in the firmware for the Southern Islands Radeon GPU into your kernel, however when you look at the Gentoo Wiki, you see that it states that your Radeon HD 7500/7600 APU series is the Fusion series which requires the ARUBA firmware.
That's why I recommend an autoload configuration. In order to accomplish that here's what I would suggest trying;
| Code: | 1) Make sure you have removed the proprietary driver from your system by doing an `emerge -C ati-drivers`
2) Make sure your /etc/make.conf VIDEO_CARDS="radeon" (and not fglrx)
3) If you changed your /etc/make.conf make sure you resync portage and do an update of your world
4) Delete your /lib/modules/[version]-gentoo directory completely |
This is to ensure you have removed all traces of the fglrx driver from your system.
Configure your kernel with;
| Code: | 1) Device Drivers -> Graphics Support -> <M> /dev/agpgart (AGP Support) --->
1a) and under /dev/agpgart (AGP Support) ---> <M> AMD Opteron/Athlon64 on-CPU GART support
2) Device Drivers -> Graphics Support -> <M> Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) --->
2a) and under Direct Rendering Manager (XFree86 4.1.0 and higher DRI support) ---> <M> ATI Radeon
[*] Enable modesetting on radeon by default - NEW DRIVER |
UPDATE: My previous configuration of using the ATI framebuffer driver gave me a blank console screen, on my recent system installation. In order to get my framebuffer working correctly I configured my kernel with these settings;
| Code: | 3) Device Drivers -> Graphics Support -> {*} Support for frame buffer devices --->
3a) and under Support for frame buffer devices ---> [*] Enable firmware EDID
[ ] Framebuffer foreign endianness support --->
[*] Enable Video Mode Handling Helpers
[*] Enable Tile Blitting Support
and do not select any framebuffer drivers. |
Then continue configuring your kernel and do not include the radeon device firmware blob;
| Code: | 4) Device Drivers -> Generic Driver Options ---> -*- Userspace firmware loading support
[] Include in-kernel firmware blobs in kernel binary
() External firmware blobs to build into the kernel binary |
Then build and install your kernel and modules. You then need to emerge either;
| Code: | | x11-drivers/radeon-ucode-20120320 |
for installing only the Radeon firmware blobs, or;
| Code: | | sys-kernel/linux-firmware-20120816 |
for installing the Radeon firmware blobs along with a bunch of other device firmware, like the Intel WiFi firmware, etc.
Then you don't need to do any additional system configuration, and you don't need an xorg.conf. When you reboot you should not see fglrx loaded as a module, and you should see similar modules autoloaded as BillWho pointed out. As a matter of fact you should see dmesg output similar to the following;
| Code: | [ 2.803769] [drm] radeon defaulting to kernel modesetting.
[ 2.803774] [drm] radeon kernel modesetting enabled.
[ 2.803966] [drm] initializing kernel modesetting (BARTS 0x1002:0x6720 0x1558:0x5102).
[ 2.804047] [drm] register mmio base: 0xF7E20000
[ 2.804048] [drm] register mmio size: 131072
[ 2.804193] radeon 0000:01:00.0: VRAM: 2048M 0x0000000000000000 - 0x000000007FFFFFFF (2048M used)
[ 2.804196] radeon 0000:01:00.0: GTT: 512M 0x0000000080000000 - 0x000000009FFFFFFF
[ 2.804201] [drm] Detected VRAM RAM=2048M, BAR=256M
[ 2.804202] [drm] RAM width 256bits DDR
[ 2.804242] [TTM] Zone kernel: Available graphics memory: 16441362 kiB
[ 2.804243] [TTM] Zone dma32: Available graphics memory: 2097152 kiB
[ 2.804244] [TTM] Initializing pool allocator
[ 2.804247] [TTM] Initializing DMA pool allocator
[ 2.804269] [drm] radeon: 2048M of VRAM memory ready
[ 2.804273] [drm] radeon: 512M of GTT memory ready.
[ 2.804284] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[ 2.804285] [drm] Driver supports precise vblank timestamp query.
[ 2.804341] radeon 0000:01:00.0: irq 52 for MSI/MSI-X
[ 2.804349] radeon 0000:01:00.0: radeon: using MSI.
[ 2.804394] [drm] radeon: irq initialized.
[ 2.804399] [drm] GART: num cpu pages 131072, num gpu pages 131072
[ 2.804784] [drm] Loading BARTS Microcode
[ 2.826206] [drm] PCIE GART of 512M enabled (table at 0x0000000000040000).
[ 2.826329] radeon 0000:01:00.0: WB enabled
[ 2.826332] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000080000c00 and cpu addr 0xffff880802203c00
[ 2.843325] [drm] ring test on 0 succeeded in 3 usecs
[ 2.843528] [drm] ib test on ring 0 succeeded in 0 usecs
[ 2.843787] [drm] Radeon Display Connectors
[ 2.843788] [drm] Connector 0:
[ 2.843789] [drm] LVDS-1
[ 2.843791] [drm] DDC: 0x6470 0x6470 0x6474 0x6474 0x6478 0x6478 0x647c 0x647c
[ 2.843792] [drm] Encoders:
[ 2.843793] [drm] LCD1: INTERNAL_UNIPHY
[ 2.843794] [drm] Connector 1:
[ 2.843795] [drm] HDMI-A-1
[ 2.843795] [drm] HPD3
[ 2.843797] [drm] DDC: 0x6450 0x6450 0x6454 0x6454 0x6458 0x6458 0x645c 0x645c
[ 2.843798] [drm] Encoders:
[ 2.843798] [drm] DFP1: INTERNAL_UNIPHY2
[ 2.843799] [drm] Connector 2:
[ 2.843800] [drm] DVI-I-1
[ 2.843801] [drm] HPD1
[ 2.843802] [drm] DDC: 0x6430 0x6430 0x6434 0x6434 0x6438 0x6438 0x643c 0x643c
[ 2.843803] [drm] Encoders:
[ 2.843804] [drm] DFP2: INTERNAL_UNIPHY1
[ 2.843805] [drm] CRT1: INTERNAL_KLDSCP_DAC1
[ 2.843899] [drm] Internal thermal controller with fan control
[ 2.845084] [drm] radeon: power management initialized
[ 3.351874] [drm] fb mappable at 0xE0142000
[ 3.351876] [drm] vram apper at 0xE0000000
[ 3.351877] [drm] size 9216000
[ 3.351878] [drm] fb depth is 24
[ 3.351879] [drm] pitch is 7680
[ 3.351909] fb0: radeondrmfb frame buffer device
[ 3.351910] drm: registered panic notifier |
I edited the dmesg output to only include the radeon related messages. Notice the message regarding loading of the BARTS microcode, which is done automatically on my system.
Good Luck..
UPDATE: I recently performed a clean install of the latest Gentoo ~amd64, (gentoo-sources-3.5.4), on my Clevo P150HM/ATI 6970M laptop and found out that I could not now get the framebubuffer console display to work correctly with the instructions I had previously used above. I'm updating my post with what did work.
Last edited by jasn on Sun Dec 02, 2012 5:26 pm; edited 2 times in total |
|
| Back to top |
|
|
Ant P.
Watchman
Joined: 18 Apr 2009
Posts: 6920
|
| Posted: Sun Jul 29, 2012 6:29 pm Post subject: |
|
|
| rm -r /lib/modules/$kernel_you're_building and run make modules_install again. That should get rid of fglrx. |
|
| Back to top |
|
|
onevision
n00b
Joined: 06 Sep 2011
Posts: 32
Location: Draper, Utah
|
| Posted: Mon Jul 30, 2012 8:05 pm Post subject: Good Plan |
|
|
Great feedback and information. Before your posting I decided to just try the closed sourced drivers, since it was loading it anyway, so I removed the kernel configuration for DRM and tried to just run off of the ati-drivers package. That didn't work out too well - about the same results.
So your posting sounded like a very good course of action and the next logical step to take. I removed the dependent package or two on the ati-drivers, and copied the output from equery files ati-drivers before uninstalling that package. You were correct, in that it was not removing the file /lib/modules/3.3.8-gentoo/video/fglrx.so, which I manually removed. I went through the make clean, make mrproper, and reconfigured the kernel config to use the DRM ATI module. I did already have those previously as a module, but in addition changed the AGP settings to also be a module, which previously were *. I dropped the selection on:
[] Include in-kernel firmware blobs in kernel binary
() External firmware blobs to build into the kernel binary
It does still currently have the radeon-ucode installed, although nothing really directing to those drivers (as the kernel config option "Firmware blobs root directory" disappears with the other two above blanked out. Also made sure that the make.conf had only 'radeon' entered as the VIDEO_CARDS, then I recompiled the kernel. It did finally remove the fglrx module from being compiled and auto-loaded, which is a step in the right direction, but ultimately had the same failure.
I previously I actually had the northern island radeon modules set in the kernel because one of the many pages I viewed stated that it was for 6000 series up to 7800. This conficts with to following choice, which states exactly for the 7500. I'm still not sure exactly which drivers should be loaded as the output from lspci state the card as 'turk', which would be the northern island I believe. Here's what lspci outputs:
01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Turks [Radeon HD 7500 Series]
which my first mistake was getting that confused with the audio card, which is:
01:00.1 Audio device: Advanced Micro Devices [AMD] nee ATI Turks HDMI Audio [Radeon HD 6000 Series]
At any rate, the modules look like they are loading correctly for the main ATI drivers, and the fglrx is now removed:
Module Size Used by
snd_hda_codec_hdmi 23249 2
snd_hda_codec_realtek 109331 1
ath9k 89524 0
radeon 783964 1
ttm 61686 1 radeon
drm_kms_helper 25498 1 radeon
ath9k_common 1834 1 ath9k
snd_hda_intel 22591 0
drm 198441 3 radeon,ttm,drm_kms_helper
intel_agp 10560 0
ath9k_hw 360425 2 ath9k,ath9k_common
intel_gtt 14327 1 intel_agp
btusb 11320 0
snd_hda_codec 79988 3 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel
agpgart 26103 4 ttm,drm,intel_agp,intel_gtt
ath 14653 3 ath9k,ath9k_common,ath9k_hw
r8169 48468 0
snd_hwdep 5830 1 snd_hda_codec
i2c_algo_bit 5120 1 radeon
mii 3843 1 r8169
bluetooth 160958 1 btusb
Dmesg output seems to be alright, although I'm not getting any output of it auto-loading northern, southern, or any of the drivers from the radeon-ucode package. Here's the relevant output from dmesg:
[ 4.144501] [drm] PCIE GART of 512M enabled (table at 0x0000000000040000).
[ 4.144611] radeon 0000:01:00.0: WB enabled
[ 4.144613] [drm] fence driver on ring 0 use gpu addr 0x40000c00 and cpu addr 0xffff880213fccc00
[ 4.161036] [drm] ring test on 0 succeeded in 3 usecs
[ 4.161251] [drm] ib test on ring 0 succeeded in 0 usecs
[ 4.161374] [drm] Radeon Display Connectors
[ 4.161375] [drm] Connector 0:
[ 4.161376] [drm] HDMI-A
[ 4.161376] [drm] HPD4
[ 4.161378] [drm] DDC: 0x6450 0x6450 0x6454 0x6454 0x6458 0x6458 0x645c 0x645c
[ 4.161378] [drm] Encoders:
[ 4.161379] [drm] DFP1: INTERNAL_UNIPHY2
[ 4.161380] [drm] Connector 1:
[ 4.161381] [drm] DVI-I
[ 4.161381] [drm] HPD1
[ 4.161382] [drm] DDC: 0x6460 0x6460 0x6464 0x6464 0x6468 0x6468 0x646c 0x646c
[ 4.161383] [drm] Encoders:
[ 4.161384] [drm] DFP2: INTERNAL_UNIPHY
[ 4.161385] [drm] CRT1: INTERNAL_KLDSCP_DAC1
[ 4.161449] [drm] Internal thermal controller with fan control
[ 4.162530] [drm] radeon: power management initialized
[ 4.256183] [drm] fb mappable at 0xE0142000
[ 4.256184] [drm] vram apper at 0xE0000000
[ 4.256185] [drm] size 8294400
[ 4.256186] [drm] fb depth is 24
[ 4.256186] [drm] pitch is 7680
[ 4.256207] fbcon: radeondrmfb (fb0) is primary device
[ 4.467312] drm: registered panic notifier
[ 4.467316] [drm] Initialized radeon 2.13.0 20080528 for 0000:01:00.0 on minor 0
[ 4.467418] snd_hda_intel 0000:01:00.1: irq 46 for MSI/MSI-X
[ 4.467438] modprobe used greatest stack depth: 3104 bytes left
[ 4.471004] HDMI status: Codec=0 Pin=3 Presence_Detect=0 ELD_Valid=0
[ 4.471038] input: HD-Audio Generic HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input14
[ 5.465743] EXT4-fs (sda3): re-mounted. Opts: (null)
The Xorg.0.log still looks the same, which is to say it looks like the video driver loaded fine and then something is amiss with X:
[ 390.021] (II) RADEON(0): Output HDMI-0 disconnected
[ 390.021] (II) RADEON(0): Output DVI-0 connected
[ 390.021] (II) RADEON(0): Using exact sizes for initial modes
[ 390.021] (II) RADEON(0): Output DVI-0 using initial mode 1920x1080
[ 390.021] (II) RADEON(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 390.021] (II) RADEON(0): mem size init: gart size :1fdff000 vram size: s:40000000 visible:f7d7000
[ 390.021] (II) RADEON(0): EXA: Driver will allow EXA pixmaps in VRAM
[ 390.021] (==) RADEON(0): DPI set to (96, 96)
[ 390.021] (II) Loading sub module "fb"
[ 390.021] (II) LoadModule: "fb"
[ 390.021] (II) Loading /usr/lib64/xorg/modules/libfb.so
[ 390.031] (II) Module fb: vendor="X.Org Foundation"
[ 390.031] compiled for 1.12.2, module version = 1.0.0
[ 390.031] ABI class: X.Org ANSI C Emulation, version 0.4
[ 390.031] (II) Loading sub module "ramdac"
[ 390.031] (II) LoadModule: "ramdac"
[ 390.031] (II) Module "ramdac" already built-in
[ 390.031] (--) Depth 24 pixmap format is 32 bpp
[ 390.034] (II) RADEON(0): [DRI2] Setup complete
[ 390.034] (II) RADEON(0): [DRI2] DRI driver: r600
[ 390.034] (II) RADEON(0): [DRI2] VDPAU driver: r600
[ 390.034]
[ 390.034] Backtrace:
[ 390.035] 0: /usr/bin/X (xorg_backtrace+0x36) [0x56dbb6]
[ 390.035] 1: /usr/bin/X (0x400000+0x1716a9) [0x5716a9]
[ 390.035] 2: /lib64/libpthread.so.0 (0x7f28e00a7000+0x10420) [0x7f28e00b7420]
[ 390.035] 3: /usr/lib64/xorg/modules/drivers/radeon_drv.so (0x7f28dcef9000+0xe229b) [0x7f28dcfdb29b]
[ 390.035] 4: /usr/bin/X (AddScreen+0x1a8) [0x436508]
[ 390.035] 5: /usr/bin/X (InitOutput+0x294) [0x475f94]
[ 390.035] 6: /usr/bin/X (0x400000+0x24d03) [0x424d03]
[ 390.035] 7: /lib64/libc.so.6 (__libc_start_main+0xfd) [0x7f28defdb2ad]
[ 390.035] 8: /usr/bin/X (0x400000+0x24a69) [0x424a69]
[ 390.035]
[ 390.035] Segmentation fault at address (nil)
[ 390.035]
Fatal server error:
[ 390.035] Caught signal 11 (Segmentation fault). Server aborting
The frame buffer is definitely loading and working right, as I can tell when that switches on. I'm thinking maybe adding back in the southern drivers?
emerge -Dv xorg-server xorg-drivers xf86-video-ati xorg-x11 |
|
| Back to top |
|
|
Gusar
Advocate
Joined: 09 Apr 2005
Posts: 2665
Location: Slovenia
|
| Posted: Mon Jul 30, 2012 8:08 pm Post subject: |
|
|
| The stable libdrm in portage (2.4.33) is too old. You need 2.4.34 or later. And while you're at it, going with a xf86-video-ati newer than what's in stable would probably be good too. |
|
| Back to top |
|
|
jasn
Guru
Joined: 05 May 2005
Posts: 439
Location: Maryland, US
|
| Posted: Mon Jul 30, 2012 9:52 pm Post subject: |
|
|
Before you reconfigure anything I would suggest doing what Gusar pointed out. Make sure you're running the latest version xf86-video-ati, mesa and libdrm. They should be at least at;
| Code: | x11-drivers/xf86-video-ati-6.14.6-r1
media-libs/mesa-8.1_rc1_pre20120724
x11-libs/libdrm-2.4.37 |
You'll have to unmask libdrm to install the latest version. Also what do you get when you do the following;
| Code: | dmesg |grep -i microcode
dmesg |grep -i drm |
If that doesn't work and you want to try building everything into the kernel, then you can reconfigure your kernel, specifically going to the options mentioned previously, and change them to built in (*), instead of modules (M). Then go to the firmware blob section and configure it the way you had originally, using the appropriate firmware. I would try ARUBA first, but feel free to try TURKS if you like. I would also suggest trying only 1 set at a time.
If all else fails, in order to run the proprietary driver, fglrx, you need to remove everything regarding the open source driver from your kernel config. (Again you need to make sure the system isn't autoloading both modules which it will do if it can) Then you need to add an xorg.conf file, which you can generate using the ati driver utility. This wiki covers the process pretty well.
Good Luck.. |
|
| Back to top |
|
|
onevision
n00b
Joined: 06 Sep 2011
Posts: 32
Location: Draper, Utah
|
| Posted: Mon Jul 30, 2012 10:03 pm Post subject: Good point |
|
|
Both excellent suggestions. I have upgraded and am running on the following versions:
x11-libs/libdrm-2.4.37
x11-drivers/xf86-video-ati-6.14.6-r1
That change significantly changed the outcome. While it is still sort of crashing, it doesn't look like a graphics card or X server crash now, or at the very least is a much different failure. Here's the output when trying to start an X session.
X.Org X Server 1.12.2
Release Date: 2012-05-29
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.3.8-gentoo x86_64 Gentoo
Current Operating System: Linux bacon 3.3.8-gentoo #1 SMP Mon Jul 30 07:30:46 MDT 2012 x86_64
Kernel command line: root=/dev/sda3
Build Date: 30 July 2012 07:43:54AM
Current version of pixman: 0.26.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Jul 30 09:39:01 2012
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(II) [KMS] Kernel modesetting enabled.
which: no keychain in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin:/usr/x86_64-pc-linux-gnu/gcc-bin/4.5.3)
/etc/X11/xinit/xinitrc: line 59: twm: command not found
/etc/X11/xinit/xinitrc: line 60: xclock: command not found
/etc/X11/xinit/xinitrc: line 63: exec: xterm: not found
/etc/X11/xinit/xinitrc: line 61: xterm: command not found
/etc/X11/xinit/xinitrc: line 62: xterm: command not found
xinit: connection to X server lost
waiting for X server to shut down Server terminated successfully (0). Closing log file.
From the Xorg.0.log file it almost looks like evdev isn't loading:
[ 385.592] (**) Dell Dell KM632 Wireless Keyboard and Mouse: always reports core events
[ 385.592] (**) evdev: Dell Dell KM632 Wireless Keyboard and Mouse: Device: "/dev/input/event2"
[ 385.592] (--) evdev: Dell Dell KM632 Wireless Keyboard and Mouse: Vendor 0x413c Product 0x2501
[ 385.592] (--) evdev: Dell Dell KM632 Wireless Keyboard and Mouse: Found keys
[ 385.592] (II) evdev: Dell Dell KM632 Wireless Keyboard and Mouse: Configuring as keyboard
[ 385.592] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/input/input2/event2"
[ 385.592] (II) XINPUT: Adding extended input device "Dell Dell KM632 Wireless Keyboard and Mouse" (type: KEYBOARD, id
[ 385.592] (**) Option "xkb_rules" "evdev"
[ 385.592] (**) Option "xkb_model" "evdev"
[ 385.592] (**) Option "xkb_layout" "us"
[ 385.592] (II) config/udev: Adding input device Dell Dell KM632 Wireless Keyboard and Mouse (/dev/input/event3)
[ 385.592] (**) Dell Dell KM632 Wireless Keyboard and Mouse: Applying InputClass "evdev keyboard catchall"
[ 385.592] (II) Using input driver 'evdev' for 'Dell Dell KM632 Wireless Keyboard and Mouse'
[ 385.592] (**) Dell Dell KM632 Wireless Keyboard and Mouse: always reports core events
[ 385.592] (**) evdev: Dell Dell KM632 Wireless Keyboard and Mouse: Device: "/dev/input/event3"
[ 385.592] (--) evdev: Dell Dell KM632 Wireless Keyboard and Mouse: Vendor 0x413c Product 0x2501
[ 385.592] (--) evdev: Dell Dell KM632 Wireless Keyboard and Mouse: Found 1 mouse buttons
[ 385.592] (--) evdev: Dell Dell KM632 Wireless Keyboard and Mouse: Found scroll wheel(s)
[ 385.592] (--) evdev: Dell Dell KM632 Wireless Keyboard and Mouse: Found relative axes
[ 385.592] (II) evdev: Dell Dell KM632 Wireless Keyboard and Mouse: Forcing relative x/y axes to exist.
[ 385.592] (--) evdev: Dell Dell KM632 Wireless Keyboard and Mouse: Found absolute axes
[ 385.592] (II) evdev: Dell Dell KM632 Wireless Keyboard and Mouse: Forcing absolute x/y axes to exist.
[ 385.592] (--) evdev: Dell Dell KM632 Wireless Keyboard and Mouse: Found keys
[ 385.592] (II) evdev: Dell Dell KM632 Wireless Keyboard and Mouse: Configuring as mouse
[ 385.592] (II) evdev: Dell Dell KM632 Wireless Keyboard and Mouse: Configuring as keyboard
[ 385.593] (II) evdev: Dell Dell KM632 Wireless Keyboard and Mouse: Adding scrollwheel support
[ 385.593] (**) evdev: Dell Dell KM632 Wireless Keyboard and Mouse: YAxisMapping: buttons 4 and 5
[ 385.593] (**) evdev: Dell Dell KM632 Wireless Keyboard and Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 385.593] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.1/input/input3/event3"
[ 385.593] (II) XINPUT: Adding extended input device "Dell Dell KM632 Wireless Keyboard and Mouse" (type: KEYBOARD, id 9)
[ 385.593] (**) Option "xkb_rules" "evdev"
[ 385.593] (**) Option "xkb_model" "evdev"
[ 385.593] (**) Option "xkb_layout" "us"
[ 385.593] (II) evdev: Dell Dell KM632 Wireless Keyboard and Mouse: initialized for relative axes.
[ 385.593] (WW) evdev: Dell Dell KM632 Wireless Keyboard and Mouse: ignoring absolute axes.
[ 385.593] (**) Dell Dell KM632 Wireless Keyboard and Mouse: (accel) keeping acceleration scheme 1
[ 385.593] (**) Dell Dell KM632 Wireless Keyboard and Mouse: (accel) acceleration profile 0
[ 385.593] (**) Dell Dell KM632 Wireless Keyboard and Mouse: (accel) acceleration factor: 2.000
[ 385.593] (**) Dell Dell KM632 Wireless Keyboard and Mouse: (accel) acceleration threshold: 4
[ 385.593] (II) config/udev: Adding input device Dell Dell KM632 Wireless Keyboard and Mouse (/dev/input/event4)
[ 385.593] (**) Dell Dell KM632 Wireless Keyboard and Mouse: Applying InputClass "evdev pointer catchall"
[ 385.593] (II) Using input driver 'evdev' for 'Dell Dell KM632 Wireless Keyboard and Mouse'
[ 385.593] (**) Dell Dell KM632 Wireless Keyboard and Mouse: always reports core events
[ 385.593] (**) evdev: Dell Dell KM632 Wireless Keyboard and Mouse: Device: "/dev/input/event4"
[ 385.593] (--) evdev: Dell Dell KM632 Wireless Keyboard and Mouse: Vendor 0x413c Product 0x2501
[ 385.593] (--) evdev: Dell Dell KM632 Wireless Keyboard and Mouse: Found 3 mouse buttons
[ 385.593] (--) evdev: Dell Dell KM632 Wireless Keyboard and Mouse: Found scroll wheel(s)
[ 385.593] (--) evdev: Dell Dell KM632 Wireless Keyboard and Mouse: Found relative axes
[ 385.593] (--) evdev: Dell Dell KM632 Wireless Keyboard and Mouse: Found x and y relative axes
[ 385.593] (II) evdev: Dell Dell KM632 Wireless Keyboard and Mouse: Configuring as mouse
[ 385.593] (II) evdev: Dell Dell KM632 Wireless Keyboard and Mouse: Adding scrollwheel support
[ 385.593] (**) evdev: Dell Dell KM632 Wireless Keyboard and Mouse: YAxisMapping: buttons 4 and 5
[ 385.593] (**) evdev: Dell Dell KM632 Wireless Keyboard and Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 385.593] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.2/input/input4/event4"
[ 385.593] (II) XINPUT: Adding extended input device "Dell Dell KM632 Wireless Keyboard and Mouse" (type: MOUSE, id 10)
[ 385.593] (II) evdev: Dell Dell KM632 Wireless Keyboard and Mouse: initialized for relative axes.
[ 385.593] (**) Dell Dell KM632 Wireless Keyboard and Mouse: (accel) keeping acceleration scheme 1
[ 385.593] (**) Dell Dell KM632 Wireless Keyboard and Mouse: (accel) acceleration profile 0
[ 385.593] (**) Dell Dell KM632 Wireless Keyboard and Mouse: (accel) acceleration factor: 2.000
[ 385.593] (**) Dell Dell KM632 Wireless Keyboard and Mouse: (accel) acceleration threshold: 4
[ 385.593] (II) config/udev: Adding input device Dell Dell KM632 Wireless Keyboard and Mouse (/dev/input/mouse0)
[ 385.593] (II) No input driver specified, ignoring this device.
[ 385.593] (II) This device may have been added with another device file.
[ 385.593] (II) config/udev: Adding input device HDA Intel PCH Line Out Side (/dev/input/event10)
[ 385.593] (II) No input driver specified, ignoring this device.
[ 385.593] (II) This device may have been added with another device file.
[ 385.593] (II) config/udev: Adding input device HDA Intel PCH Line Out CLFE (/dev/input/event11)
[ 385.593] (II) No input driver specified, ignoring this device.
[ 385.593] (II) This device may have been added with another device file.
[ 385.594] (II) config/udev: Adding input device HDA Intel PCH Line Out Surround (/dev/input/event12)
[ 385.594] (II) No input driver specified, ignoring this device.
[ 385.594] (II) This device may have been added with another device file.
[ 385.594] (II) config/udev: Adding input device HDA Intel PCH Line Out Front (/dev/input/event13)
[ 385.594] (II) No input driver specified, ignoring this device.
[ 385.594] (II) This device may have been added with another device file.
[ 385.594] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=3 (/dev/input/event5)
[ 385.594] (II) No input driver specified, ignoring this device.
[ 385.594] (II) This device may have been added with another device file.
[ 385.594] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event6)
[ 385.594] (II) No input driver specified, ignoring this device.
[ 385.594] (II) This device may have been added with another device file.
[ 385.594] (II) config/udev: Adding input device HDA Intel PCH Front Mic (/dev/input/event7)
[ 385.594] (II) No input driver specified, ignoring this device.
[ 385.594] (II) This device may have been added with another device file.
[ 385.594] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event8)
[ 385.594] (II) No input driver specified, ignoring this device.
[ 385.594] (II) This device may have been added with another device file.
[ 385.594] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event9)
[ 385.594] (II) No input driver specified, ignoring this device.
[ 385.594] (II) This device may have been added with another device file.
[ 385.624] (II) evdev: Power Button: Close
[ 385.624] (II) UnloadModule: "evdev"
[ 385.639] (II) evdev: Power Button: Close
[ 385.639] (II) UnloadModule: "evdev"
[ 385.655] (II) evdev: Dell Dell KM632 Wireless Keyboard and Mouse: Close
[ 385.655] (II) UnloadModule: "evdev"
[ 385.671] (II) evdev: Dell Dell KM632 Wireless Keyboard and Mouse: Close
[ 385.671] (II) UnloadModule: "evdev"
[ 385.687] (II) evdev: Dell Dell KM632 Wireless Keyboard and Mouse: Close
[ 385.687] (II) UnloadModule: "evdev"
[ 385.694] Server terminated successfully (0). Closing log file.
the modules loading are looking great.
Module Size Used by
snd_hda_codec_hdmi 23249 2
snd_hda_codec_realtek 109331 1
ath9k 89524 0
radeon 783964 1
snd_hda_intel 22591 0
snd_hda_codec 79988 3 snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel
btusb 11320 0
ath9k_common 1834 1 ath9k
ath9k_hw 360425 2 ath9k,ath9k_common
ttm 61686 1 radeon
drm_kms_helper 25498 1 radeon
drm 198441 3 radeon,ttm,drm_kms_helper
intel_agp 10560 0
intel_gtt 14327 1 intel_agp
agpgart 26103 4 ttm,drm,intel_agp,intel_gtt
snd_hwdep 5830 1 snd_hda_codec
i2c_algo_bit 5120 1 radeon
ath 14653 3 ath9k,ath9k_common,ath9k_hw
r8169 48468 0
mii 3843 1 r8169
bluetooth 160958 1 btusb
All of the commands in the error message I thought were part of the core xorg-X11 (i.e. twm, xclock, exec, xterm), but apparently twm, xclock and xterm are all there own packages, none of which were installed. Odd that it would be dependent on those programs and not install automatically as a dependent. At any rate I manually installed those three programs - not sure what 'exec' is tied to or why it's needed, as the computer I'm working from now doesn't have it either, and works just fine. I did however do a emerge -uDvp --newuse world, which came up as not needing anything.
After installing those however, I was able to start the cheesy X with startx... which I couldn't stop, even after killing the process. But after a quick reboot, I fired up xdm and everything worked like a champ. You are a scholar and a gentleman, and I thank you all for your very helpful and great ideas and input. Looks like I'm ready to load that puppy up with a couple more tools and get to work, thanks to all the help.
BTW, sort of a random question. This is actually the first computer I've personally seen with a... rats, not VGA, but the popular type video output and the second output an HDMI. I'm guessing the HDMI will support the second monitor? Just haven't seen a dual with those outputs, although it would be silly to not support dual monitors on a newer box. Just curious if anyone knew for sure if that HDMI supports a second monitor?
Thanks again all, your help is greatly appreciated.
-Davey |
|
| Back to top |
|
|
Gusar
Advocate
Joined: 09 Apr 2005
Posts: 2665
Location: Slovenia
|
| Posted: Mon Jul 30, 2012 10:09 pm Post subject: Re: Good point |
|
|
| onevision wrote: | | Odd that it would be dependent on those programs |
It's not. X tries to load those if you haven't installed anything else it should run. A lot of people make this mistake - they install X and only X and then wonder why it doesn't start. It does start, but then shuts down because it has nothing do to.
| onevision wrote: | | BTW, sort of a random question. This is actually the first computer I've personally seen with a... rats, not VGA, but the popular type video output and the second output an HDMI. I'm guessing the HDMI will support the second monitor? Just haven't seen a dual with those outputs, although it would be silly to not support dual monitors on a newer box. Just curious if anyone knew for sure if that HDMI supports a second monitor? |
I don't know what you mean here. DisplayPort? It looks similar to HDMI. Then there's DVI, which is three rows of small square holes.
Radeon cards since Evergreen (HD5xxx) support 4-6 displays, depending on card. |
|
| Back to top |
|
|
onevision
n00b
Joined: 06 Sep 2011
Posts: 32
Location: Draper, Utah
|
| Posted: Tue Jul 31, 2012 12:06 am Post subject: Ah |
|
|
And that is exactly what happened. X started up and then immediately shut down. Everything is running like a champ now though.
Oh, and the type I couldn't think of the name was DVI for the monitor I had plugged in and was using, and it did end up just being a HDMI (or display port, as stated by the monitor manual). It also picked up the second monitor (once I ran and got an HDMI cable), and everything popped up just as expected. 4-6 display you say *drool* I've always wanted to setup a desktop workstation that uses 4 monitors, 6 would be that much sweeter.
Thanks again for all the help, mucho gracias.
-Davey |
|
| Back to top |
|
|
|
|
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
|
|
Desktop Environments
