SUSE / openSUSEThis Forum is for the discussion of Suse 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.
Does anyone have a link to a step-by-step how-to install the nforce2 drivers on suse9.3? I want to use the sound drivers to enable multiple simultaneous sound streams.
Oh I did just that... well I downloaded the driver + kernel source and ran the installer. I'm not sure why you want me to make cloneconfig etc. but I know so little...
Anyway, the nvidia network driver included in the nforce package installs just fine and is in use as we speak, but my sound card still uses the snd-intel8x0 driver. My problem is that I have no Idea of what to do to tell suse to use the nvidia driver instead.
Yeah I did hat once and was not sure how to get the system to use the nvaudio instead. When I checked the SuSE plugger it had three drivers listed snd-intel8x0 was running. I modprobed the others fine. I actually had them all modprobed. gee no crash, but hell still no sound.
I'm trying to get sound through the spidf port. I'm not sure if the analog ports works since I only have a digital speaker system.
No I didn't solve it. I followed the instructions in /usr/share/nforce/... But I've come to the conclusion that suse does not really cares abt what is in /etc/modprobe.conf, /etc/modprobe.cond.local and /etc/modprobe.d/sound
I tried this Nvidia rigamarole, again. This time I actually took the time to read the documents (shame on me from the first time)
There was mention that SuSE does in fact ignore a lot of config stuff. In this case it uses the modprobe.d directory for local configs, in this case a sound file.
This document also tells you what to do to in both this file and the modprobe.conf file.
I'm going to start my machine up later today to see if it all worked. For the record, your are correct the snd-intel8x0 device is damn persistent.
This can all be found by following the applicable links from www.nvidia.com
Last edited by SCOSWriter; 06-03-2005 at 07:19 AM.
Neither do I since you said you had an nforce chipset. Nforce chipsets typically use nvidia's audio- not intel's
this is crap because the driver (snd-intel8x0) is for AC on intel and nforce mobos, check first details for God's sake before assuming anything based on the driver's name.
Originally posted by SCOSWriter I tried this Nvidia rigamarole, again. This time I actually took the time to read the documents (shame on me from the first time)
There was mention that SuSE does in fact ignore a lot of config stuff. In this case it uses the modprobe.d directory for local configs, in this case a sound file.
This document also tells you what to do to in both this file and the modprobe.conf file.
I'm going to start my machine up later today to see if it all worked. For the record, your are correct the snd-intel8x0 device is damn persistent.
This can all be found by following the applicable links from www.nvidia.com
I followed the instructions in the nvidia readme at the best of my knowlege. And edited the, presumably, correct /etc/*.conf -files. But it didn't work out. If you give it a go and actually make it work please take notes on what files you edit and post back here.
Sorry... I just had to let that out. This is my first experience with linux and I can tell already that this is going to be a huge learning curve. Anyway, I am just curious as to why the sound driver inside YaST labled nForce doesn't work in the first place. Why can't everything work the first time, why?!
I ignored the forcedeth comment. I don't use this card, and don't want anything to affect the other.
At this point I never ran alsaconf at all and this might be important since It creates some entries in the modprobe.conf, etc.
From there onI followed the instructions to the key.
When it was all done, I never thought it would work. The snd-intel8x0 module was still there and the nvmixer application never brought up my sound card, but of course after reboot, I was pleasantly suprised to hear the KDE welcome chime.
I then ran the nvmixer and it recognized everything.
I did run the nvmixer before I rebooted, this may or may not have had an effect.
Give it a try. For all of those, who have tried and tried with alsa, I say give up and use the nvidia driver. Its now mature enough that it, does hardware mixing, outputs to my spid/f connector, and man it sounds great. I really did not have to do anything, but run the installer and reboot. That kinda made me ill since I spend weeks off and on, trying to get this to work.
Now I just have to get my mouse buttons to work.
A word of warning, if you have configured a fglrx driver with xorg, the settings in your xorg.conf file will get messed up if you use yast to change your mouse hardware settings.
Originally posted by antiNeo THIS DRIVER BUISINESS IS DRIVING ME CRAZY!!!!!!
Sorry... I just had to let that out. This is my first experience with linux and I can tell already that this is going to be a huge learning curve. Anyway, I am just curious as to why the sound driver inside YaST labled nForce doesn't work in the first place. Why can't everything work the first time, why?!
In response to this, I'm going to provide some info that might help you with this learning curve. I have installed SuSE 9.1 and 9.2 on serveral machines whether a home or at work and I have found that sound in particular is trickiest thing to get working.
Most often its related to on-board sound ware. For example on an out of the box HP Compaq, the sound works, but the obvious driver to use does not work (the current intel driver). After all this is a i915 intel board, and everything on it is intel but the damn intel driver just does not work.
I experimentated with, different card drivers by manually selecting a sound card, through yast. Every freaking intel board driver I tried to add just did not work. Then on a whim I went to the nvidia selections and chose nvidia2, I actually heard sound... not great but ok we've got sound. Then I chose nvidia3, it was better and as good as this in pc mono speaker was going to get.
Maybe nvidia knows something about sound architectures that intel is just not doing?
Who knows? All I know is that so far the Nvidia drivers are winning 4 to 1. There are people out there that have used the snd-intel8x0, and got it to work just fine, so my questions is, what are they doing thats different from the alsa web posts, if anything different at all. Maybe, but unlikly, is it a software combination. Could i even be different generations of this mobo (Asus A7N8X-E deluxe) Mine is rev. 2.X, and has the latest 1013. bios release. It came with 1008 or 9 when I bought it.
Last edited by SCOSWriter; 06-06-2005 at 08:05 AM.
I ignored the forcedeth comment. I don't use this card, and don't want anything to affect the other.
At this point I never ran alsaconf at all and this might be important since It creates some entries in the modprobe.conf, etc.
From there onI followed the instructions to the key.
When it was all done, I never thought it would work. The snd-intel8x0 module was still there and the nvmixer application never brought up my sound card, but of course after reboot, I was pleasantly suprised to hear the KDE welcome chime.
I then ran the nvmixer and it recognized everything.
I did run the nvmixer before I rebooted, this may or may not have had an effect.
Give it a try. For all of those, who have tried and tried with alsa, I say give up and use the nvidia driver. Its now mature enough that it, does hardware mixing, outputs to my spid/f connector, and man it sounds great. I really did not have to do anything, but run the installer and reboot. That kinda made me ill since I spend weeks off and on, trying to get this to work.
Now I just have to get my mouse buttons to work.
A word of warning, if you have configured a fglrx driver with xorg, the settings in your xorg.conf file will get messed up if you use yast to change your mouse hardware settings.
This is odd, I thought I'd tried everything... Exactly what files did you have to edit? And how? I'm asking because I have installed the nforce driver on this computer before (using Mandrake) without trouble. It puzzles me that I fail now.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.