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.
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I originally posted a problem I was having in post #105. I did a little work on it just after I posted, but then the laptop went on a few trips & I just got it back yesterday. Today I d/led & installed 2.6.32.3, from current. Then I built & installed all five packages mentioned above, but I still had no joy. The error I was getting was that it couldn't find /usr/lib64/xorg/modules/dri/r300_dri.so. /usr/lib64/xorg/modules/dri/r600_dri.so was there, however. Working a hunch & knowing that I couldn't make it any worse, I went into mesa.SlackBuild & changed both instances of r600 to r300. This time, after rebuilding & reinstalling mesa, all worked well. My xorg.log is clean. I built & installed bloodfrontier again & it runs at a decent rate (I had been getting 1 fps before). One of the things I did early on was to remove Eric's multilib packages. I am very probably wrong, but I had the impression that something there was interfering with the operation of mesa. If I had to use this in a multilib environment, how would I go about that?
Regards,
Bill
At first I also sought that in order to get working solution, Alien's multilib packages has to be of the same versions as 64 bit. I mean if I installed mesa*_x86_64*, I also have to build and upgrade the same version of 32compat package.
But in some other thread I saw that Eric reply to similar question. He was saying if I remember correctly, that 32compat packages live completely independent from 64 bit packages. So there is no need to update those unless you have some special need for it.
I have 32copmat packages of Eric installed on my computer and I do not update those.
I have 32copmat packages of Eric installed on my computer and I do not update those.
Then are you not using dri in a 32 bit environment? My daughter is deeply into World Of Warcraft, which only runs under wine, which means a 32 bit environment. We have currently left a 12.2 partition on the laptop, into which I have installed the ATI binary drivers. I guess I have a bit more work to do to get that scenario to work on 13.0.
Regards,
Bill
We do not need the first one. It is already in the kernel.
3) [CODE]cd /usr/src/linux-2.6.33-rc5
make mrproper
patch -p1 < /home/Soft/agd5f/pm/0002-drm-radeon-kms-add-dynamic-engine-reclocking-V9.patch
patch -p1 < /home/Soft/agd5f/pm/0003-drm-radeon-kms-add-functions-to-get-current-pcie-la.patch
patch -p1 < /home/Soft/agd5f/pm/0004-drm-radeon-kms-pull-power-mode-info-from-bios-table.patch
patch -p1 < /home/Soft/agd5f/pm/0005-drm-radeon-kms-don-t-set-pcie-lanes-for-ignored-pow.patch
patch -p1 < /home/Soft/agd5f/pm/0006-drm-radeon-kms-add-a-power-state-type-based-on-powe.patch
patch -p1 < /home/Soft/agd5f/pm/0007-drm-radeon-kms-add-code-to-select-power-state.patch
patch -p1 < /home/Soft/agd5f/pm/0008-drm-radeon-kms-use-power-states-for-dynamic-reclock.patch
patch -p1 < /home/Soft/agd5f/pm/0009-drm-radeon-kms-get_power_state-early-not-when-proc.patch
patch -p1 < /home/Soft/agd5f/pm/0010-drm-radeon-kms-use-wait-queue-events-for-VBLANK-sync.patch
cp /{path to slackware}/source/k/config-generic-2.6.32.3 .config
make oldconfig
make bzImage modules modules_install
4) do the lilo part and add something like
append="resume=/dev/cryptvg/swap vt.default_utf8=1 radeon.modeset=1 radeon.dynpm=1" for this kernel. Third option switches on kms for radeon and the forth switches on power management.
First and second options has nothing to do with radeon. Just general options for hibernate and utf.
5) copy *.bin from here http://people.freedesktop.org/~agd5f/radeon_ucode/
to /lib/firmware/radeon
First of all thanks a lot for the Slack Team for a huge updates.
Secondly if you wish to run kms for radeon on -current and to be able to use acceleration for X, you still need libdrm, mesa and xf86-video-ati from git. Actually there should be stable releases of this soft later this month. But for now we still need git.
For the kernel part - nothing has to be rebuilt. You only need to add file /etc/modprobe.d/radeon.conf, which will include only one string: "options radeon modeset=1".
Then you need to load radeon module before X starts. it is safe to do this from /etc/rc.d/rc.modules. Add the following line:
/sbin/modprobe radeon
somewhere.
And after reboot proceed with downloading and building libdrm, mesa and xf86-video-ati, using above quoted scripts.
i had a working kms enabled 2.6.32 kernel working perfectly fine with kde 4.4 (with compositing) before by following this guide.
i just updated to current after looking at the huge batch of updates and was eager to try out the kms improvements on the 2.6.33 kernel..X stopped working after the updates and i spent a couple of hours trying to get things running back again with kms + kde 4.4 + compositing. so far i've only managed to get the 2.6.32 kernel working as usual..here are my notes:-
- i had to rebuild libdrm, mesa, xf86-video-ati from git and replace them over the -current packages. (i noticed the -current packages seem to be up to date with the current git versions except for mesa..i'm wondering if only mesa needs to be rebuilt from git)
- then Xorg.0.log reported that it couldn't find the dri drivers and i had to export LIBGL_DRIVERS_PATH=/usr/local/lib/dri/ in /etc/profile. then another library error came up and i had to symlink /usr/local/lib/dri/ to /usr/lib64/xorg/modules/dri.
WARNING: Error inserting i2c_algo_bit (/lib/modules/2.6.33-smp/kernel/drivers/i2c/algos/i2c-algo-bit.ko): Invalid module format
WARNING: Error inserting agpgart (/lib/modules/2.6.33-smp/kernel/drivers/char/agp/agpgart.ko): Invalid module format
WARNING: Error inserting drm (/lib/modules/2.6.33-smp/kernel/drivers/gpu/drm/drm.ko): Invalid module format
WARNING: Error inserting drm_kms_helper (/lib/modules/2.6.33-smp/kernel/drivers/gpu/drm/drm_kms_helper.ko): Invalid module format
WARNING: Error inserting ttm (/lib/modules/2.6.33-smp/kernel/drivers/gpu/drm/ttm/ttm.ko): Invalid module format
FATAL: Error inserting radeon (/lib/modules/2.6.33-smp/kernel/drivers/gpu/drm/radeon/radeon.ko): Invalid module format
i haven't tried the proposed solution of recompiling the kernel with changing the CONFIG_PREEMPT options but i'm assuming it's not actually the CONFIG_PREEMPT options that are solving the problem but rebuilding the modules again. i'll give a try later today to see if works and give an update.
hope this helps.cheers
*edited*
i've just recompiled the 2.6.33 kernel with my old .config and
CONFIG_PREEMPT_NONE is not set
CONFIG_PREEMPT_VOLUNTARY=y
CONFIG_PREEMPT is not set
and kms + DRI is working fine. it looks like problem isn't with the preempt options, but the kernel modules in the -current package. rebuilding them seems to solve the problem.
Secondly if you wish to run kms for radeon on -current and to be able to use acceleration for X, you still need libdrm, mesa and xf86-video-ati from git. Actually there should be stable releases of this soft later this month. But for now we still need git.
Thanks for keeping this thread up-to-date. Great job!
i had a working kms enabled 2.6.32 kernel working perfectly fine with kde 4.4 (with compositing) before by following this guide.
i just updated to current after looking at the huge batch of updates and was eager to try out the kms improvements on the 2.6.33 kernel..X stopped working after the updates and i spent a couple of hours trying to get things running back again with kms + kde 4.4 + compositing. so far i've only managed to get the 2.6.32 kernel working as usual..here are my notes:-
- i had to rebuild libdrm, mesa, xf86-video-ati from git and replace them over the -current packages. (i noticed the -current packages seem to be up to date with the current git versions except for mesa..i'm wondering if only mesa needs to be rebuilt from git)
- then Xorg.0.log reported that it couldn't find the dri drivers and i had to export LIBGL_DRIVERS_PATH=/usr/local/lib/dri/ in /etc/profile. then another library error came up and i had to symlink /usr/local/lib/dri/ to /usr/lib64/xorg/modules/dri.
WARNING: Error inserting i2c_algo_bit (/lib/modules/2.6.33-smp/kernel/drivers/i2c/algos/i2c-algo-bit.ko): Invalid module format
WARNING: Error inserting agpgart (/lib/modules/2.6.33-smp/kernel/drivers/char/agp/agpgart.ko): Invalid module format
WARNING: Error inserting drm (/lib/modules/2.6.33-smp/kernel/drivers/gpu/drm/drm.ko): Invalid module format
WARNING: Error inserting drm_kms_helper (/lib/modules/2.6.33-smp/kernel/drivers/gpu/drm/drm_kms_helper.ko): Invalid module format
WARNING: Error inserting ttm (/lib/modules/2.6.33-smp/kernel/drivers/gpu/drm/ttm/ttm.ko): Invalid module format
FATAL: Error inserting radeon (/lib/modules/2.6.33-smp/kernel/drivers/gpu/drm/radeon/radeon.ko): Invalid module format
i haven't tried the proposed solution of recompiling the kernel with changing the CONFIG_PREEMPT options but i'm assuming it's not actually the CONFIG_PREEMPT options that are solving the problem but rebuilding the modules again. i'll give a try later today to see if works and give an update.
hope this helps.cheers
Rebulding the kernel with CONFIG_PREEMPT_NONE=y does work. I had problems with mesa, drm and radeon from the latest update until I rec ompiled the kernel.
i've just recompiled the 2.6.33 kernel with my old .config and
CONFIG_PREEMPT_NONE is not set
CONFIG_PREEMPT_VOLUNTARY=y
CONFIG_PREEMPT is not set
and kms + DRI is working fine. it looks like problem isn't with the preempt options, but the kernel modules in the -current package. rebuilding them seems to solve the problem.
You only need to add file /etc/modprobe.d/radeon.conf, which will include only one string: "options radeon modeset=1"
and then it worked. I was not aware of this KMS stuff. My system feels more responsive.
No need for me to recompile the kernel (I'm using the stock generic smp one) or any other package (mesa, xf86-video-ati). I even didn't need to add anything to /etc/rc.d/rc.modules.
Thank you dolphin77 for your tip.
[EDIT] Sorry KMS is not working with driver xf86-video-ati-6.12.5. I'll try to install driver 6.12.191[/EDIT]
Last edited by gegechris99; 03-09-2010 at 06:40 AM.
Reason: KMS not working on my card with driver version 6.12.5
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.