Differences between version 32 and previous revision of NForce2Notes.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 32 | Last edited on Sunday, May 9, 2004 2:17:54 pm | by CraigBox | Revert |
| Older page: | version 31 | Last edited on Thursday, April 29, 2004 9:58:39 am | by JoshBassett | Revert |
@@ -9,17 +9,15 @@
To get an nvidia card working, see their http://www.nvidia.com/ site for their latest graphics driver (currently [1.0-5336|http://www.nvidia.com/object/linux_display_ia32_1.0-5336.html] as of March 6, 2004).
!! Network
-The network controller on nForce2 based boards only works with a binary driver called nvnet that is supplied by nvidia in the package above. This seems to work fine and gives reasonable performance.
-If you're using kernel 2.6, you will have to
[patch the NVidia source
|http://penna
.dyn.dhs
.org/nvnet
.2.5-1
.diff] to make nvnet run
.
+The
[ForcedEth
|http://www
.hailfinger
.org/carldani/linux/patches/forcedeth/], driver is a reverse engineered, open source ethernet driver for the onboard NVIDIA lan
. It's very stable and comes with
2.4
.24+ and 2.6.3+ kernels
.
-See also [ForcedEth|http://www
.hailfinger
.org/carldani/linux/patches/forcedeth/]
, a reverse engineered open source ethernet
driver for
the onboard NVIDIA lan.
+If you want to use nvidia's binary driver, it's called nvnet and is supplied by nvidia in the package above
. This seems to work fine and gives reasonable performance
.
+Sometimes you'll notice
, when doing large transfers over your LAN, that your CPU usage goes through the roof and eth0 generates up to 500,000 interrupts
a second. The nvnet
driver is to blame; you can either load
the module with 'optimizations=1' to optimize for CPU usage instead of throughput (interestingly, this doesn't seem to affect throughput at all)
-!Note with regard to network performance
-
-Sometimes
you'll notice
, when doing large transfers over your LAN, that your CPU usage goes through the roof and eth0 generates up
to 500,000 interrupts a second. The nvnet driver is to blame; you can either load
the module with 'optimizations=1' to optimize for CPU usage instead of throughput (interestingly, this doesn't seem to affect throughput at all), or you can load forcedeth, which makes it all go away
. forcedeth should be included in 2
.4
.24+ and is within
2.6
.3+
.
+If
you're using kernel 2.6
, you will have
to [patch
the NVidia source|http://penna
.dyn
.dhs.org/nvnet
.2.5-1
.diff] to make nvnet run
.
!! Sound
Provided you have your motherboard correctly setup (see below) you should be able to use the kernel supplied OSS i810_audio module to get sound using the nvidia chipset. You can get better facility out of the nvaudio module but it's hard to get going.
@@ -41,8 +39,10 @@
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss
options snd-intel8x0 mpu_port=0x330
</verbatim>
+
+!!Digital speaker setup
You can either be using an analog speaker setup, or a digital speaker setup. While the above configuration is sufficient for analog speakers, the following additional notes are applicable to a digital speaker setup.
The digital setup will be using the motherboard's S/PDIF output. The ALSA card 0, device 0 (playback) provides the analog outputs. However, the ALSA card 0, device 2 (playback) provides the S/PDIF (i.e. IEC958) output.
@@ -50,11 +50,39 @@
You will want to direct ALSA's OSS emulation device 0 (/dev/dsp0, /dev/adsp0, etal) to ALSA device 2, so that applications using the OSS API will send their sounds to your nifty digital speaker system. To accomplish this mapping of OSS device 0 to ALSA device 2, add the following to your modules.conf file:
<verbatim>
options snd-pcm-oss dsp_map=2 adsp_map=2
</verbatim>
+
+!!Software mixing
+
In addition, you might want to configure alsa-lib to provide software mixing and rate conversion, with the following /etc/asound.conf file:
+
+!Analog output
+<verbatim>
+### /etc/asound.conf for nforce2 apu (analog out, from http://www.wlug.org.nz/NForce2Notes)
+
+pcm.!default {
+ type plug
+ slave.pcm "nforce"
+}
+
+pcm.nforce {
+ type dmix
+ ipc_key 1024
+ slave {
+ pcm "hw:0,0"
+ period_time 0
+ period_size 1024
+ buffer_size 4096
+ rate 48000
+ }
+}
+</verbatim>
+
+!Digital output
+
<verbatim>
-### /etc/asound.conf for nforce2 apu
+### /etc/asound.conf for nforce2 apu (digital out, from http://www.wlug.org.nz/NForce2Notes)
pcm.nforce-hw {
type hw
card 0
}
