LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Slackware 13.37 problems with Ati 11.4 drivers (https://www.linuxquestions.org/questions/slackware-14/slackware-13-37-problems-with-ati-11-4-drivers-877711/)

adamk75 08-31-2011 06:19 AM

Run it from a terminal with the "--buildpkg Slackware/Slackware" option. It will create a package that can then be installed with "installpkg". Then run 'aticonfig --initial' and reboot.

Adam

thelastblack 09-01-2011 10:52 AM

i found a better way: use "--install" option. it will install it automatically without needing installpkg.
but thank you 4 reply.

adamk75 09-01-2011 10:56 AM

The advantage to building a package is that you now have a record of it the driver with the Slackware package management programs, and can uninstall or upgrade the driver with those same utilities.

Adam

bgeddy 09-01-2011 11:51 AM

Quote:

i found a better way: use "--install" option. it will install it automatically without needing installpkg.
but thank you 4 reply.
As adamk75 has already said it's always better to make a package then install that rather than straight install an application. It's for this reason SlackBuilds are used to create additional packages and Slackware itself. If you don't follow this advice your system will soon become very messy and unmanageable with Slackware's record of installed applications, stored in /var/log/packages, being wrong and updating or removing applications is very difficult.

Kohrnbread 04-30-2013 04:07 AM

Slackware 14.0 x86 Black Screen after startx
 
Quote:

Originally Posted by Pixxt (Post 4350389)
I always before I build the fglrx packages, I run "xorgsetup" to have a nice sane default /etc/X11/xorg.conf . After i install the fglrx package then i ati-config --initial this seems to work for me. YMMV

First off, apologies for posting in a very old thread. However, I encountered a very similar problem on a fresh install of Slackware 14.0 x86. I had so much difficulty in finding a solution for my problem, that when I tried this method, it finally fixed it and I am now comfortably enjoying my new install of Slackware. My hope is to potentially save any future hardship on someone should they encounter the same issues I did.

My interests lies only in that I appreciate the community for its help, and for that I wish to give back my experience with an issue that took a substantial amount of time to solve. Why it took so long is because I've been using linux for about 6 days, so I am needless to say, very much a "newbie" to the Linux experience. However, I aim to show that even if you are a complete and total newbie to Linux/Slackware/Anything_Other_Than_Windows that if you put in the time and have just enough patience, the rewards are well worth it.

What my issue/s were...
After Completing an installation of Slackware 14.0 x86 when the prompt for 'startx' would be issued, I would load a screen showing the HDD/Utils/etc. loading, then the screen goes black. Once this occurs, no commands can be given. The keyboard is completely non-functional. Ctrl+Alt+Del does nothing. Alt+T does nothing. No commands can be issued, a forced shutdown/reboot IS required.

How I solved this...
A Google.com search revealed an issue with drivers relating to ATi onboard graphics & dedicated cards. My issue was not with ATi drivers because I have Intel onboard graphics. However, I came across this thread and saw the post (at the top of page) saying to run xorgsetup. I ran this command and followed every available option with default. After it ran an autoconfigure for screen resolution the system did appear to freeze. DO NOT worry, it will come back in a moment. After this was complete I ran 'startx' and everything booted just fine.

Some details that might help someone in the future...

Laptop: Dell 13X series Inspirion
Slackware Ver.: 14.0
CPU: Intel Core i3
Every setup or option in the install I did as Default/Auto/(NA) etc.
I had internet issues at start of install, this fixed that issue. (Possibly related?)



All in all I hope this helps anyone out in the future, and again, sorry for posting in such an old thread. I just felt that I had info and knowledge that could help benefit the community. Afterall, it's the community that helped solve my issue, so it's only appropriate to pay it forward. :-)


All times are GMT -5. The time now is 11:29 PM.