Slackware This Forum is for the discussion of Slackware Linux.
|
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
11-18-2013, 09:08 AM
|
#1
|
Member
Registered: Jun 2010
Location: Ukraine, Vinnitsa
Distribution: Slackware
Posts: 351
Rep:
|
AMD APU + Catalyst + Xorg = failed, and I hate to raise this question again!
I hate to raise this question again!
I cannot force to work Xorg on my hardware.
AMD APU A4-3400 (include Radeon 6410D graphics)
Slackware 14.1
Installing Catalyst 11.4 ends with kernel module build error. Skipped it.
1. Installing 11.6 beta - builds. Slackware specific package(fglrx-*.t?z) installed
2. aticonfig --initail --resolution=0,1024x768 - DONE. /etc/X11/xorg.conf.d/ati.conf generated
3. in /etc/modprobe.d/ blacklisted radeon and radeonhd
4. reboot
5. login, startx - FAILED. Black screen. Text cursor at top left corner blinks. Alt+F# and Alt+Ctrl+F#, Alt+Ctrl+Backspace, Alt+Ctrl+Delete - no reaction.
6. Cold reset(and damned fsck consumes another 15minutes of time and portion of nerves).
7. Boot kernel with additional parameter nomodeset
8. login, startx - see step 5.
Any suggestions, working solution?
PS: Shall provide xorg.0.log latter if required.
PPS:
ati.conf attached.
Xorg.0.log - as it appeared, there is no any Xorg.0.log. Really I see empty Xorg.0.log. It seems it fails to save it into disk at all.
Last what I saw on screen after running starx - List of extensions to be loaded.
Last edited by FeyFre; 11-18-2013 at 03:46 PM.
|
|
|
11-18-2013, 10:11 AM
|
#2
|
Member
Registered: Feb 2003
Location: Almere, Netherlands
Distribution: slack 7.1 till latest and -current, LFS
Posts: 368
Rep: 
|
both Xorg.0.log and also your ati.conf might be handy.
|
|
|
11-18-2013, 01:10 PM
|
#3
|
LQ Newbie
Registered: Jan 2009
Location: Italy
Distribution: Slackware
Posts: 15
Rep:
|
Quote:
Originally Posted by FeyFre
1. Installing 11.6 beta - builds. Slackware specific package(fglrx-*.t?z) installed
|
Try to install the driver without creating the package; with the recent driver (or kernel I don't know exactly where the problem is)
the internal slackbuild puts some files in the wrong path.
The autoinstaller works fine and doesn't left garbage around when you uninstall the driver.
|
|
|
11-18-2013, 03:46 PM
|
#4
|
Member
Registered: Jun 2010
Location: Ukraine, Vinnitsa
Distribution: Slackware
Posts: 351
Original Poster
Rep:
|
ati.conf attached
Xorg.0.log - failed. it is really empty
|
|
|
11-18-2013, 04:00 PM
|
#5
|
Member
Registered: Feb 2003
Location: Almere, Netherlands
Distribution: slack 7.1 till latest and -current, LFS
Posts: 368
Rep: 
|
I am not sure where the problem is.
If Xorg.0.log is empty, you might want to look at Xorg.0.log.1
sometimes it spawns a second log file and the new one is empty
|
|
|
11-18-2013, 06:54 PM
|
#6
|
Member
Registered: Jun 2010
Location: Ukraine, Vinnitsa
Distribution: Slackware
Posts: 351
Original Poster
Rep:
|
I am not so dumb  There is no more any Xorg logs.
Well, I shall try to do clean install and report result, BUT I very dislike recent trend of Slackware releases to unable to work w/o clean install.
|
|
|
11-18-2013, 07:50 PM
|
#7
|
Member
Registered: Jan 2006
Location: Command Line
Distribution: Slackware
Posts: 75
Rep: 
|
My home laptop with an A8 APU is working just fine with 14.1 and the latest beta driver. Whenever Xorg is updated the ATI drivers most likely will not work unless they release a new beta, they are always one step behind. This is an ATI issue not a Slackware issue.
|
|
|
11-18-2013, 09:18 PM
|
#8
|
LQ Guru
Registered: Jul 2011
Location: California
Distribution: Slackware64-15.0 Multilib
Posts: 6,564
|
Can you get it to work with the default Mesa driver at least?
If you can get it to work with the open source "xf86-video-ati" driver for Radeons, you shouldn't need the FGLRX driver at all unless you are absolutely certain it's necessary.
Radeons like yours with the Northern Islands chipset should work with the Gallium radeon driver using the Glamor EGL driver. All you then need to do is set up your xorg.conf file in /etc/X11 as such:
Section "Module"
Load "dri2"
Load "glamoregl"
EndSection
Section "Device"
Identifier "radeon"
Driver "radeon"
Option "AccelMethod" "glamor"
EndSection
|
|
|
11-18-2013, 09:49 PM
|
#9
|
Moderator
Registered: Dec 2009
Location: Germany
Distribution: Whatever fits the task best
Posts: 17,148
|
To get an APU of that series working properly on Slackware 14.1 using the Mesa drivers you need at least kernel 3.11 (for dynamic power-management, otherwise the video-part of the APU will most likely run on its lowest frequency all the time), but better 3.12 (fixes a serious bug in the ondemand cpufreq governor, which improves performance dependent on the use case up to 90%) and Mesa 9.2 (not really necessary, but allows hardware video decoding using VDPAU and gives better 3D performance).
Glamor is for the HD6000 series not necessary, but should work (I still have not tried that, will do that soon).
|
|
|
11-18-2013, 09:52 PM
|
#10
|
LQ Guru
Registered: Jul 2011
Location: California
Distribution: Slackware64-15.0 Multilib
Posts: 6,564
|
I'd say just get kernel 3.12 as recommended. I think Slackware already has libmesa 9.2 or later.
|
|
|
11-18-2013, 10:39 PM
|
#11
|
Moderator
Registered: Dec 2009
Location: Germany
Distribution: Whatever fits the task best
Posts: 17,148
|
Quote:
Originally Posted by ReaperX7
I'd say just get kernel 3.12 as recommended. I think Slackware already has libmesa 9.2 or later.
|
Slackware 14.1 (and at this point -current) come with Mesa 9.1.7.
|
|
|
11-18-2013, 11:08 PM
|
#12
|
LQ Guru
Registered: Jul 2011
Location: California
Distribution: Slackware64-15.0 Multilib
Posts: 6,564
|
Well, then you'll need libmesa 9.2.3 also.
If Slackware doesn't come with a copy of EGL, you can safely import the LFS build into Slackware:
http://www.linuxfromscratch.org/blfs...tml#glamor-egl
Just replace $XORG_CONFIG with the correct pathway "--prefix=/usr", and simply build as the instructions say to, and install.
Last edited by ReaperX7; 11-18-2013 at 11:15 PM.
|
|
|
All times are GMT -5. The time now is 02:11 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|