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.
I'm stuck here
A. Why would make install works? you didn't make before.
root @ WhiteCastle linux] $ make install
sh /usr/src/linux-220.127.116.11/arch/i386/boot/install.sh 18.104.22.168-smp arch/i386/boot/bzImage System.map "/boot"
*** Missing file: arch/i386/boot/bzImage
*** You need to run "make" before "make install".
make: *** [install] Error 1
make: *** [install] Error 2
Also, I got no /lib/modules/fglrx
Originally Posted by perry
Step 1: Download the driver Step 5: Update the kernel
Finally, should you ever make any changes to your kernel after this, it'll be a good idea to do this after you've done a make install:
(current cd in /usr/src/linux)
This ensures the fglrx driver is still part of your kernel.
If making changes to your kernel is a frequent process, make a change to your /sbin/installkernel file to speed the process up for you!
# The -p is for the few people that know you can set passwords on lilo that
# will then be required if someone wants to be sneaky and root the system
# with "linux single" or similar lameness..
Step 6: Reboot & Test
Hope this helps get you these kind of results:
15743 frames in 5.0 seconds = 3147.260 FPS
19605 frames in 5.0 seconds = 3920.955 FPS
18246 frames in 5.0 seconds = 3649.192 FPS
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI RADEON 9600 Series
OpenGL version string: 2.0.6747 (8.40.4)
Step 7: Enjoy your new 3D hardware accleration
Be sure to undo the changes made for your backup plan (if you did that), change the inittab entry from 3 to 4. Mind you, I'm back to 1280x1024 resolution again (as oppose to 1400x1050). Maybe I'll make another posting on how to switch between these two drivers later!
While not an *absolute* requirement, sometimes ATI requests you have a device called 'shm' supported in your /etc/fstab:
tmpfs /dev/shm tmpfs defaults 0 0
It rarely takes up much memory, it won't hurt to have it included!
root @ WhiteCastle linux] $ xvinfo
X-Video Extension version 2.2
no adaptors present
root @ WhiteCastle linux] $ dmesg | grep -i fglrx
fglrx: module license 'Proprietary. (C) 2002 - ATI Technologies, Starnberg, GERMANY' taints kernel.
[fglrx] Maximum main memory to use for locked dma buffers: 427 MBytes.
[fglrx] USWC is disabled in module parameters
[fglrx] PAT is disabled!
[fglrx] module loaded - fglrx 8.40.4 [Jul 31 2007] on minor 0
[fglrx] Internal AGP support requested, but kernel AGP support active.
[fglrx] Have to use kernel AGP support to avoid conflicts.
[fglrx] AGP detected, AgpState = 0x1f00421b (hardware caps of chipset)
[fglrx] AGP enabled, AgpCommand = 0x1f004312 (selected caps)
[fglrx] total GART = 268435456
[fglrx] free GART = 252440576
[fglrx] max single GART = 252440576
[fglrx] total LFB = 134217728
[fglrx] free LFB = 116387840
[fglrx] max single LFB = 116387840
[fglrx] total Inv = 134217728
[fglrx] free Inv = 134217728
[fglrx] max single Inv = 134217728
[fglrx] total TIM = 0
root @ WhiteCastle linux] $ mount | grep tmpfs
tmpfs on /dev/shm type tmpfs (rw)
(That "make install" was a reference to your kernel, if you were updating your kernel that would be the last instruction before adding your ati driver)
Seems to me that you might be using the *huge* kernel. You might want to do a kernel distribution upgrade from Slackware (see above) and then make use of your generic-smp kernel before trying to install your ATI driver. Thats how I did it.
Also, even after you get it all setup, whenever you make a change to or reinstall your kernel you'll probably need to reinstall your ATI module simply by:
IF that directory isn't there something isn't installed properly.
is it next to impossible to add a boot splash to Slackware, i keep reading these horror stories about it here. or is it just a bad idea all around?
Well, it is a useless piece of eyecandy if you ask me, and other distros use it to hide those "confusing to the average end user" kernel messages that scroll on your screen when Linux boots.
But it is not hard at all to add bootsplash to your Slackware system at all provided you find a bootsplash kernel patch for your exact kernel, are not afraid of a kernel compile, are willing to edit all of your "rc.*" files to add progress bar information, and know how to create an initial ramdisk (initrd) and add the bootsplash program to it, and know how to add it to lilo.conf.
So, yes, doable.
There is also the "splashy" utility from Debian, which does not require a kernel patch. All it does is (again) hide the kernel messages on boot by "splashing" a nice bitmap on your console with a progress bar. Again, you will have to edit all of your rc.* files, know how to create a initrd and use that.
Bootsplash is more powerful than that because it can wrap your consoles in a nice graphical theme as well.
I can't enable direct rendering on toshiba satellite L20 running slack 12.0 with default kernel (22.214.171.124-smp).
I use default i810 driver from the slackware 12.0.
Already put modprobe i810 and modprobe drm in rc.modules
Already edit the xorg.conf , but still:
$glxinfo |grep direct
direct rendering: No
OpenGL renderer string: Mesa GLX Indirect
Anyone can help?
Last edited by hottdogg; 09-19-2007 at 11:30 PM.
Reason: using code for glxinfo
I don't mean to hijack this thread but I followed the instructions (or so I thought) and somehow messed something up. When my computer boots in root boots fine with ATI Radeon drivers. Everything seems fine. But if I logoff and kill X then I lose my drivers and my screen shuts off. Sometimes my PC won't shutdown all the way, it shuts X down, but doesn't seem to shut it down any farther. And to make it worse, it won't boot in X on my other account(the non root account).
Any advice would be nice.