Re: Problems with Nvidia nvsound module

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



when i installed the nforce2 drivers, i had a few problems also.  i don't
know if sharing my experience will help, but here goes.

the installer kept erroring too fast for me to read what was going on.  but
before i figured out it made a log in /var/log/, i got the installer to
work by logging outta X.  in fact, i ran the installer after a fresh boot
and it seemed to work.

next i remember editing modules.conf:
alias eth0 nvnet
alias snd-card-0 nvsound

then i rebooted.  lsmod still showed forcedeth as my eth0 driver.  now here
is where it gets hazy.  i can't remember if i opened up modules.conf again
or modprobe.conf.  well whatever i opened had the old aliases for eth0 and
snd-card-0, so i changed them again to nvnet and nvsound.  rebooted, and
this time nvnet came up in lsmod.  started X, but no sound!  then i opened
kmix and all the volumes were set to zero.  i raised some of the volumes
and started Juk...it played beautifully.

a bit of a side note, its worth every ounce of effort to get nvsound
working.  the difference between nvsound and the default driver for FC2 is
like night and day.  its so drastic infact that i thought my speakers were
broken (or just shitty) before i got nvsound working.

i also have a bunch of install/remove lines in either modules.conf or
modprobe.conf...its cool to just delete them?


Nick Pierpoint wrote:

> On Tue, 2004-08-24 at 13:04, Michael Schwendt wrote:
>> On Tue, 24 Aug 2004 12:31:19 +0100, Nick Pierpoint wrote:
>> > 
>> > Is this what you mean by "clean up all sound/mixer related stuff"?
>> 
>> Yes, except that you should delete the nvsound entry, too. First
>> objective should be to get the intel8x0 driver working as reference.
>> After that you can try installing the external nvsound driver.
>> 
>> > I tried also deleting the "alias snd-card-0" line but this stopped
>> > system-config-soundcard from starting at all.
>> 
>> Weird. If you have sound driver kernel modules loaded before starting
>> s-c-s, that likely causes problems or confuses it.
> 
> modprobe.conf is now:
> 
> # Note: for use under 2.4, changes must also be made to modules.conf!
> alias usb-controller ohci-hcd
> alias ieee1394-controller ohci1394
> options ne irq=10
> alias eth0 nvnet
> alias usb-interface usb-ohci
> alias snd-card-0 snd-intel8x0
> 
> After booting I get no sound.
> 
> If I run system-config-soundcard I then get sound (although no changes
> to /etc/modprobe.conf).
> 
> If I then reboot, I get no sound again.
> 
> I'm losing the configuration somewhere.
> 
> I've removed the nvsound module (modinfo nvsound now says no such module
> or somesuch) but notice that the system-config-soundcard still remembers
> that nvsound was there at some point - oddly when I play the test sound
> button on the tab for this module it still works!!!
> 
> --
> nick
> 
> 




[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux