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.
with kernel 18.104.22.168 (in extra, modules installed and lilo
Moreover, scrolling in xterm is slowly than that of my slack
10.2, even if I try with a copy of the old xorg.conf file
(so, without dri), and of my last suse.
I have also tried with an ubuntu 6.10, that says
that dri is enabled with xdriinfo and glxinfo (ok),
but hangs my computer with glxgears with a warning about
the support of visual 0x42.
What could I do to get a performance like the previous
slack version and (better) get also my dri works?
Or get better diagnosis..
Hmmm.. May I suggest, a good place to start might be to load Ubuntu, and copy what's in the xorg.conf file and save it somewhere, like on a floppy or something, or somewhere safe on the hard disk.
Then reload Slackware, and open up the saved file from Ubuntu and compare it to the one you have in Slackware.
This may give you a good headstart as to what is missing for the DRI.
It may NOT help you with the Visual 0x42 error, but it is a start. There may be a module or option missing or some such thing, which is preventing full performance.
After you have done this, assuming X works, examine the logs (xorg.log) and see what is there if anything, about anything missing or other error messages.
No, xorg.conf file is ok, I am (almost) sure..
These days I try with different distributions: last fedora live cd, damn small linux, foresight,
and all gives me differents output, xdriinfo and x log file gives me that dri working, but
in some distro glxinfo gives me : "direct rendering: No", even if xdriinfo gives me an output
that is not "not direct rendering capable", but "Screen 0: savage".. However, in these distros,
when I launch xdriinfo options savage it complains.. In ubuntu and fedora it lists all xml
output, glxinfo output is "direct rendering: Yes", but hangs with glxgears..
So I would like to know:
* Does anyone really can make direct rendering, 3d acceleration, tuxracer *ran* with a
S3 Savage4 card (16M video memory) ? Is this really possible ?
* Can anyone explain me all the components of x drivers (what to recompile savage.ko driver, drm
and dri drivers - if to download the binary snapshots from dri.freedesktop.org, libdrm or
whatever else) - Docs and references are really too confusing about these things - I found a
lot of posts in various forums and one says a different way to do this (wrongly).