SlackwareThis 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.
I have done it, as soon as I have installed new kernel 2.6.24.7 - everything works, I think there were problems with drm module. But I would like to know: how can I check a using of shared memory?
I am posting to this thread rather than starting a new one in hopes that someone will see it. I know there are instructions for getting direct rendering working, but rather than go through the long process (looks like a long process, anyway), I want to ask if I really need it. Video seems to run OK, flash works OK, and I don't use compiz or other desktop candy. I do get very low frame rates in glxgears and the KDE apps open a little slower than I think they should with a dual core processor and scrolling is a little choppy. I do have the ATI proprietary drivers installed and have the ATI Catalyst control center. But, I haven't got direct rendering. fglrxinfo gives me this:
Quote:
bob@bob-laptop:~$ fglrxinfo
libGL error: open DRM failed (Operation not permitted)
libGL error: reverting to (slow) indirect rendering
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Radeon X1200 Series
OpenGL version string: 1.4 (2.1.7415 Release)
Probably just a permissions problem, but I don't think solving that alone would give direct rendering. If there is not going to be significant improvement in graphical performance, I won't bother going through the hassle of getting it working. The machine is a Toshiba laptop with an AMD64 X2 1900Ghz with an ATI X1200 card with (I think 360MB).
And if you are happy with the performance right now, you can leave it be, and work on it later if you wish.
I try to keep post #1 updated as things happen, so going through th entire post is kept to a mininum. But I will wager the answer is in there somewhere.
When you have the time and the desire, take a look. Until then, as long as you are happy, it doesn't HAVE to be enabled.
Thank you for your response. One question though...Is it possible to actually have Rendering working and received a false report that it isn't? Look at this:
Quote:
(II) fglrx(0): Acceleration enabled
(WW) fglrx(0): Option "VendorName" is not used
(WW) fglrx(0): Option "ModelName" is not used
(II) fglrx(0): [DRI] installation complete
(II) fglrx(0): Direct rendering enabled
[atiddx] ASYNCIO init succeed!
(==) fglrx(0): Silken mouse enabled
(==) fglrx(0): Using hardware cursor
(==) RandR enabled
This is a snippit from /var/log/Xorg.0.log. It indicates that DRI is enable, but then I also get this:
Quote:
bob@bob-laptop:~$ glxinfo | grep rendering
libGL error: open DRM failed (Operation not permitted)
libGL error: reverting to (slow) indirect rendering
direct rendering: No (If you want to find out why, try setting LIBGL_DEBUG=verbose)
Kind of confusing. Is it enabled or isn't it. Slow framerate suggests it isn't, but X works well and the ATI driver set itself up nicely. I also get this:
Quote:
bob@bob-laptop:~$ aticonfig --initial --input=/etc/X11/xorg.conf
Found fglrx primary device section
Nothing to do, terminating.
I posted else where but it seems that I am asking the wrong questions or something. So I decided to post here to see if my problem is related to 3d acceleration it is strange because I didn't have this problem when I ran Ubuntu Hardy all I had to do was turn on the accelerated driver which is why I am thinking it is 3d related and I am really hoping that you can help me
I am using 64bit Arch Linux
my glxgears is fine;
Code:
glxgears
41493 frames in 5.0 seconds = 8298.517 FPS
42490 frames in 5.0 seconds = 8497.949 FPS
42529 frames in 5.0 seconds = 8505.635 FPS
44079 frames in 5.0 seconds = 8815.686 FPS
46324 frames in 5.0 seconds = 9264.788 FPS
46482 frames in 5.0 seconds = 9296.372 FPS
46216 frames in 5.0 seconds = 9243.059 FPS
46413 frames in 5.0 seconds = 9282.436 FPS
46467 frames in 5.0 seconds = 9293.307 FPS
46305 frames in 5.0 seconds = 9260.933 FPS
46541 frames in 5.0 seconds = 9308.062 FPS
but when I try a simple game like Enemy territory my fps averages 15-25 when it should be around 144 fps
this is my fglrx
Code:
fglrxinfo
display: :0.0 screen: 0
OpenGL vendor string: ATI Technologies Inc.
OpenGL renderer string: ATI Radeon HD 3870
OpenGL version string: 2.1.7537 Release
and this is my glxinfo | grep direct
Code:
glxinfo | grep direct
direct rendering: Yes
this one has me a little confused because it is so large
glxinfo
Hello, if any beginner like me is having problems founding info about installing ATI drivers, just check this page out:
[...]
It really helped me who didn't know where to start... very easy and everything works fine...
Skuzye
Loooks like the LQ system strips off the final ')' from the uri when used with 'Quote:'. Try:
I am not sure how many other penguins are involved. At least my penguin suffered.
This post is for:
ATI user with tcsh.
For the reason I previously posted (7/Dec/2006), my .tcshrc was modified so that /usr/lib/fglrx is included in LD_LIBRARY_PATH. Now, it look like libraries sit /usr/lib/dri.
Without uninstalling previous drivers (not recommended by ATI), I installed new one and did not modify my .tcshrc (there is no way to know new location). All 3D died.
As for i810, here's my take on some of the info in this thread (this applies to Intel D855GM card, 2004-ish). I use Slackware 12.2 and kernel 2.6.28.
- I've seen no xf86-video-(intel|i810) issues. On my machine, both are installed, and I specify "intel" without problems: this driver detects my card and loads i810 or so the logs say.
- As for the kernel driver, i915 is the new one. You can include both as modules, and yes, DRI will load the right one (per the kernel help), but I would say that for most newer ones, i915 is the one you want. No sense in compiling two unless you're not sure.
- As for kernel config for this card, the Slackware generic kernel includes vesafb as[*] in kernel config, and for intel cards using the intelfb, this is not good. You want the Intel Framebuffer because then you can switch to virtual terminals without crashing Xorg half the time like with vesafb. The crash is caused by the i915 DRI driver trying to tell the Intel framebuffer driver to switch video resolution when you try to switch to a virtual terminal. You must recompile your kernel. See below for my options. You must also disable vesafb because it will grab the framebuffer device before intelfb can, so it basically prevents you from loading intelfb and must be removed. You can try append statements in LILO all day long and it won't change the fact that vesafb loads before intelfb in the kernel. As for DRI, however, and the Intel DRI modules (i915 mainly), you will want to make these modules in your kernel config because they prefer to load themselves. (see below for more kernel compile advice)
- You can run the Intel DRI without the Intel Framebuffer, but (other than above framebuffer resolution switching issue) you will get about 100fps less in glxgears in non-maximized modes.
- As for xorg.conf, mine is http://www.puresimplicity.net/~twinreverb/xorg.conf, but specifying video memory is not appreciated
by intel's drivers. You'll only generate log entries that tell you not to do that, and the driver will ignore it.
- To recompile your kernel the "safest way" (for those who are new to this or are a bit paranoid): first you should be using generic-smp kernel for day to day use (per Slackware's documentation), but still, either use this config (should be in /boot/config-generic-smp-2.6.27.7-smp if i remember correctly) or go download it (on most Slackware mirrors it's in source/k/kernel/ i think). Download the latest kernel image from http://www.kernel.org (when I wrote this, it was 2.6.28). Unpack this in /usr/src/. Remove the kernel-source package that came with Slackware if you want (since you now have updated source). Copy the generic-smp config to /usr/src/linux-2.6.28/.config. Go into your favorite config (make menuconfig is mine), and change the following things:
- In Device Drivers > Graphics Support > make AGP Support <*> and then in this menu make "Intel 440LX/BX/GX, I8xx, and E7x05 chipset support" <*>. This is done using the "y" key on the keyboard for "yes" or "static". If this is the only AGP card you have in this machine (example: a laptop with onboard Intel AGP), you can probably safely remove all others (this is optional). No sense compiling what you are sure you don't have or will never need.
- Make sure Device Drivers > Graphics Support > Direct Rendering Manager is <M> and in this menu area, the appropriate Intel graphics drivers are <M> (as discussed above, "Intel 830M, 845G, 852GM, 855GM, 865G" set to <M> and then i830 and i915 below it are set to <M> unless you know that yours only uses i915, see above). If you don't have any other chipsets (for example, on a laptop with only the Intel onboard graphics) you can probably safely remove all other DRI modules (this is optional).
- In Device Drivers > Graphics Support make "Support for frame buffer devices" <*>, then in this menu, make sure that "VESA VGA graphics support" is [ ] (i.e. press "n" key for "no"). This it the "evil" vesafb that I spoke of above. Then go find "Intel 830M/845G/852GM/855GM/865G/915G/945G/945GM/965G/965G" and make it <*>. DDC/I2C support is optional if you want to go to the I2C section in Device Drivers and enable it. On mine, with the Toshiba ACPI driver, it lets me set the screen brightness, but I haven't noticed much else it gives me.
Then, because this is the generic-smp config, you will want to make sure that you go to File Systems and that your filesystem is selected as <M> (almost all of them are already this way) if you prefer to use an initrd. If you're like me and you hate initrd, and since you're already compiling a kernel, go ahead and make at minimum the filesystem module for your root partition <*>. If you're not sure, the easy thing would be to make ext2, ext3, reiserfs, jfs, and xfs all as <*>. This should boot 99% of all Slackware systems out there.
From here, compile, install, etc. There are handy dandy guides on the internet for this stuff. Enjoy!
Just make sure that you do not merely change the LILO kernel config to the new kernel: make the old kernel (generic-smp or huge-smp, either one) your "failsafe" kernel config, and add a totally new kernel config line for the new one. Also, check out /usr/src/linux-2.6.28/Documentation/fb/intelfb.txt for the LILO append line.
If you experience no blinking cursor when your system starts up (this can be annoying), change "hwcursor" in your LILO append statement to "nohwcursor" and see if that fixes it. On my system, I have to do this.
I finally moved to a install on a AMD64 for 'Slackware64 -rc1'. Looks great so far on real hardware. I like 'KDE 4.2' so far. I'm not a heavy 'GUI' user but this environment does feel clean and crisp. Most of my 'GUI' is browsing so the new 'FF' seems great.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
