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 am having problems getting my sound and video drivers to load. I'm convinced this is because the drivers aren't loading because the kernel doesn't detect them, as they are seen as unknown devices. I've tried a few kernel appends with little success, just a little more "verboseness" that led me to this conclusion. Anyone have any idea how to force linux to recognize drivers to busIDs? Or is my conclusion off base?
On the video side, what is listed for Driver in your xorg.conf file (fgrep Driver /etc/X11/xorg.conf)?
On the audio side, try here. Update: This takes you to alsa. I'd suggest posting on the alsa-devel mailing list. It probably won't take much to get it added to the driver. I'm currently working on HD audio issues, otherwise I'd look into it directly.
Last edited by GrueMaster; 02-24-2007 at 02:40 PM.
Hmm, at auzentechs site they say it works with the built-in c-media drivers but don't go much into details. Just said the chip is based on an earlier model, so I would think all the function calls or whatever would still work... I'm not a programmer but I would think adding support for this card would be as easy as typing a busID/chipID/vendor name into the code somewhere, but I'm not a programmer so how should I know? Obviously, this way wouldn't enable all the bells and whistles this card has(I really like it's headphone driver but anyway..), but at least I would think the sound quality would be there.
My xorg.conf does point to fglrx:
Code:
Driver "fglrx"
And yea, this is the last time I'm buying an ATi card
Oh, and I followed THIS guide to install the drivers. Also used the tutorial here at linuxquestions.org and a few others.
Last edited by Furlinastis; 02-24-2007 at 03:10 PM.
I have a C-Media sound card and it works great (even better than my soundblaster which the C-Media card replaced). So, it will work. Now, what kernel are you using ? It works for me with huge26.s
Last edited by H_TeXMeX_H; 02-24-2007 at 04:08 PM.
OH... heh heh... how'd I leave that info out? I'm using 2.6.20.1 and slackware11... but since I upgraded from 2.6.20 X won't boot at all, so I'm going to go back to 2.6.20 cause that worked (well, "worked") with fglrx.
OH... heh heh... how'd I leave that info out? I'm using 2.6.20.1 and slackware11... but since I upgraded from 2.6.20 X won't boot at all, so I'm going to go back to 2.6.20 cause that worked (well, "worked") with fglrx.
You probably forgot to compile the fglrx-kernel module for 2.6.20.1
The 7280 device is your Radeon X1950Pro, at least parts of it.
The 72a0 device is obviously some other part of your Radeon X1950Pro but only ATI knows what.
The kernel doesn't really need to know exactly what the different devices are as long the right kernel or Xorg modules do know, but someone should at least get the correct names added to "/usr/share/misc/pci.ids".
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.