SlackwareThis Forum is for the discussion of Slackware Linux.
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.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
After a clean install of Slackware 12.0 X won't start and locks the whole computer.
When I change the Driver line from the default 'vesa' to 'radeon' in the xorg.conf file everything works fine.
When I then try to install the proprietary drivers from ATi the installation finishes without errors, but starting X still doesn't work and locks up the whole system. Again changing the Driver line from 'fglrx' to 'radeon' makes it work.
I installed the the new ATI drivers (8.39.4) last night on Slackware 12, and used the generic-smp 2.6.21 kernel which is shipped with Slackware (avoided a recompile, luckily :-). I used the installer to make the Slackware packages and then installed them, and it all appears to be working just fine (playing 3d games works, and glxgears(not a benchmark, I know :-) runs at about 3500+ fps.)
try grep 'EE' /var/log/Xorg.0.log
Also, make sure the fglrx module is loaded properly in the kernel (lsmod | grep 'fglrx')
All else failing, try the newest drivers, as they were released about 4 days ago (on July 23, 2007)
Thanks for the tip, but I don't think that's the solution. You see I've been using ATi's proprietary drivers back since Slackware 10.1 without having to compile my own kernel to get it working.
Did you read the description for Slack 12:
There are two kinds of kernels in Slackware -- the huge kernels, which
contain support for just about every driver in the Linux kernel. These are
primarily intended to be used for installation, but there's no real reason
that you couldn't continue to run them after you have installed. The
other type of kernel is the generic kernel, in which nearly every driver
is built as a module. To use a generic kernel you'll need to build an
initrd to load your filesystem module and possibly your drive controller
or other drivers needed at boot time, configure LILO to load the initrd at
boot, and reinstall LILO. See the docs in /boot after installing for more
information. Slackware's Linux kernels come in both SMP and non-SMP types
now. The SMP kernel supports multiple processors, multi-core CPUs,
HyperThreading, and about every other optimization available. In our own
testing this kernel has proven to be fast, stable, and reliable. We
recommend using the SMP kernel even on single processor machines if it
will run on them.
Ran into the same problem just doing the first boot up after install. Compiling the kernel is no big deal, just requires your attention and you need to know what type of processor and motherboard your using. Doesn't hurt to know the rest of your hardware either.
be sure to setup your test kernel under a separate line option in lilo.conf so that you have a fall back position
I always had problems with my ATI and the only way to solve was to recompile the kernel so it could work with ATI's driver.
Just out of curiosity what model is you card?
I have Radeon 9600 Pro.
BTW: the only way I know to check out if ATI's driver is working is fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI RADEON 9600 Series
OpenGL version string: 2.0.6474 (8.38.6)
bash-3.1$ glxinfo |grep direct
direct rendering: Yes
I'm some kind of being afraid of n proprietary driver by ati. I do have ati radeon mobility 9600 and if this is possible i'll be glad to seen step-by-step description of setup of the proprietary driver.
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
I've just upgraded to Slackware 12.0 and, after fooling around with the supplied ATI driver and the optional one (neither did the job), I installed the ATI proprietary drivers and all works as expected (that is, it works). My test is Google Earth; if that starts up and zooms smoothly, all is well with the world (so to speak).
I should note that I start with a generated xorg.conf file in place using xorgsetup to do so. That reads the graphics card and display and builds an xorg.conf file that, frankly, is just fine for most every purpose. In my case, xortsetup accurately determines the horizontal and vertical frequency ranges, size of the bulb and all that and creates a useful xorg.conf.
What I do is compile the kernel using the config file from the disk 1 kernel directory. I know there is an argument back and forth about whether to do so or not, but I have found that not doing so results in an error message trying to install other things (including ATI drivers), so, what the heck. I do make and make modules, doesn't hurt, seems to help.
I execute ati-driver-installer-8.39.4-x86.x86_64.run, choose the defaults (automatic installation), let it finish, execute aticonfig --initial (on a new installation; an upgrade doesn't need that), then reboot (per the ATI instructions). aticonfig modifies the xorg.conf file that was created with xorgsetup earlier.
Things seem to work just fine if I just leave it alone...
That seems to be the case with the out-of-the-box generic kernel however I'd like a couple customizations like the processor family changed from 386 to K8. No dice, for some obscure reason any attempt to compile the kernel results in lots of trouble for me. Guess I'll just have to slow and find out just what the precise problem is.
Hi again, I'm back from vacation and ready to start struggling with the ATi drivers again.
Thanks for all the tips.
I compiled my kernel with the settings that Hyakutake suggested, still no success, but I got some interesting error messages that we should be able to work something out with.
First from /var/log/messages:
Aug 8 13:26:14 testslack kernel: [fglrx] module loaded - fglrx 8.39.4 [Jul 20 2007] on minor 0
Aug 8 13:26:14 testslack kernel: [fglrx] module unloaded - fglrx 8.39.4 [Jul 20 2007] on minor 0
Loading, then directly unloading, :S.
Then from /var/log/Xorg.0.log:
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: open result is -1, (No such device or address)
drmOpenDevice: Open failed
[drm] failed to load kernel module "radeon"
(EE) RADEON(0): [dri] RADEONDRIGetVersion failed to open the DRM
[dri] Disabling DRI.
Hmmm, whadday think?
Last edited by Sn!per[SWE]; 08-08-2007 at 01:11 PM.
The radeon driver has problems with the ati driver. This is what I hear all the time. post your xorg.conf. most likely you need to remove radeon from the xorg.conf and rmmod radeon(possibly blacklist it). I've never had this problem but it is what i hear often.