LinuxQuestions.org
Did you know LQ has a Linux Hardware Compatibility List?
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 01-16-2010, 06:30 PM   #121
TSquaredF
Member
 
Registered: Dec 2005
Location: "The South Coast of Texas"
Distribution: Slackware64-current
Posts: 490
Blog Entries: 1

Rep: Reputation: 55

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
 
Old 01-17-2010, 02:37 AM   #122
dolphin77
Member
 
Registered: May 2009
Posts: 200

Original Poster
Rep: Reputation: 54
Please correct me if I am wrong.

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.
Code:
ls -l /var/adm/packages/ |grep mesa
-rw-r--r-- 1 root root    1688 2010-01-16 21:06 mesa-20100116_git-x86_64-1_vt
-rw-r--r-- 1 root root    1949 2009-12-11 00:29 mesa-compat32-7.5-x86_64-1
 
Old 01-17-2010, 09:13 AM   #123
TSquaredF
Member
 
Registered: Dec 2005
Location: "The South Coast of Texas"
Distribution: Slackware64-current
Posts: 490
Blog Entries: 1

Rep: Reputation: 55
dolphin77:
Quote:
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
 
Old 01-24-2010, 10:53 AM   #124
dolphin77
Member
 
Registered: May 2009
Posts: 200

Original Poster
Rep: Reputation: 54
Power management for radeon? It is there for testing.

1) get the linux-2.6.33-rc5

2) get this patches:
http://people.freedesktop.org/~agd5f/pm/

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

this should be it.

Last edited by dolphin77; 01-24-2010 at 10:54 AM.
 
Old 01-25-2010, 03:26 AM   #125
overvolting
LQ Newbie
 
Registered: Jan 2010
Posts: 3

Rep: Reputation: 0
looking forward to seeing the power management changes in the kernel asap.
 
Old 03-02-2010, 02:54 PM   #126
dolphin77
Member
 
Registered: May 2009
Posts: 200

Original Poster
Rep: Reputation: 54
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.

Good luck there.
 
Old 03-03-2010, 01:57 PM   #127
zvzi
Member
 
Registered: Aug 2003
Location: Malaysia
Distribution: slackware
Posts: 71

Rep: Reputation: 17
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.

now kms and compositing was working fine again but only with the 2.6.32 kernel. with the 2.6.33 kernel i'm getting these errors (as posted here http://www.linuxquestions.org/questi...pgrade-792578/):-

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.

Last edited by zvzi; 03-03-2010 at 08:51 PM.
 
Old 03-03-2010, 02:57 PM   #128
BroX
Member
 
Registered: Oct 2003
Location: Sweden
Distribution: Slackware64-current
Posts: 746

Rep: Reputation: 64
Thumbs up

Quote:
Originally Posted by dolphin77 View Post
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!
 
Old 03-03-2010, 03:18 PM   #129
LordAnta
Member
 
Registered: Apr 2008
Location: Bucharest, Romania
Distribution: Slackware current
Posts: 126

Rep: Reputation: 17
Quote:
Originally Posted by zvzi View Post
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.

now kms and compositing was working fine again but only with the 2.6.32 kernel. with the 2.6.33 kernel i'm getting these errors (as posted here http://www.linuxquestions.org/questi...pgrade-792578/):-

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.
 
Old 03-03-2010, 08:50 PM   #130
zvzi
Member
 
Registered: Aug 2003
Location: Malaysia
Distribution: slackware
Posts: 71

Rep: Reputation: 17
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.
 
Old 03-04-2010, 03:50 PM   #131
gegechris99
Member
 
Registered: Oct 2005
Location: France
Distribution: Slackware 14.1 64bit
Posts: 728
Blog Entries: 3

Rep: Reputation: 77
Hello,

I just want to share my own experience with my ATI card after I upgraded to latest -current (dated Tue Mar 2 23:31:51 UTC 2010) for Slackware 32-bits.

My card is:
Code:
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV100 QY [Radeon 7000/VE]
When I first ran "startx" after the upgrade, I had a black screen with no response from keyboard and mouse (I'm using the radeon driver).

I've taken advice from dolphin77's post #126

Quote:
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
 
Old 03-05-2010, 07:27 PM   #132
octoberblu3
Member
 
Registered: Oct 2005
Distribution: Slackware64-current
Posts: 67

Rep: Reputation: 22
I was able to get KMS and DRI2 working by just using xf86-video-ati from git. The kernel is now new enough and so is mesa 7.7

Now we just need xf86-video-ati version 6.13, which is currently in release candidate stage (6.12.9x)
 
Old 03-06-2010, 01:55 AM   #133
dolphin77
Member
 
Registered: May 2009
Posts: 200

Original Poster
Rep: Reputation: 54
Quote:
Originally Posted by octoberblu3 View Post
I was able to get KMS and DRI2 working by just using xf86-video-ati from git. The kernel is now new enough and so is mesa 7.7

Now we just need xf86-video-ati version 6.13, which is currently in release candidate stage (6.12.9x)
Yes, you right. For pre r600 chips. I meant r600 and further.
 
Old 03-09-2010, 02:21 AM   #134
dolphin77
Member
 
Registered: May 2009
Posts: 200

Original Poster
Rep: Reputation: 54
Hooray!!!

This thread should be dead for now. Slack Team introduced in -current completely working solution (at least for my Radeon HD3400).

Thank you Slackware Developers!!!

brgrds,
Vladimir

Last edited by dolphin77; 03-09-2010 at 03:39 AM.
 
Old 03-09-2010, 11:09 AM   #135
octoberblu3
Member
 
Registered: Oct 2005
Distribution: Slackware64-current
Posts: 67

Rep: Reputation: 22
Quote:
Originally Posted by dolphin77 View Post
Hooray!!!

This thread should be dead for now. Slack Team introduced in -current completely working solution (at least for my Radeon HD3400).

Thank you Slackware Developers!!!

brgrds,
Vladimir
Well, almost. All we need now is xf86-video-ati-6.13.

6.12.5 doesn't have the KMS code in it, so we have to wait for the next major release (or keep compiling from git master or 6.12.191).
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Linux KMS Intel 865G: Hacking KMS to use vesa... or disable hardware acceleration eantoranz Linux - Hardware 1 08-01-2009 12:58 PM
KMS with radeon gives garbled screen with x onlyolli Linux - Software 0 06-29-2009 04:14 PM
LXer: TTM, Radeon KMS Support Goes Into Linux 2.6.31 LXer Syndicated Linux News 0 06-17-2009 06:11 PM
LXer: The KMS, Plymouth Experience In Fedora 10 LXer Syndicated Linux News 0 11-28-2008 02:40 AM
Radeon 9600 Pro 2.6.6 Works, 2.6.7 doesn't AlgebraicSpore Linux - Hardware 4 07-14-2004 05:36 PM


All times are GMT -5. The time now is 02:08 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration