Differences between current version and predecessor to the previous major change of NForce2Notes.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 38 | Last edited on Friday, June 17, 2005 11:47:12 am | by CraigBox | |
| Older page: | version 33 | Last edited on Thursday, May 13, 2004 6:29:15 pm | by WilliamBlew | Revert |
@@ -1,8 +1,7 @@
The three components of the motherboard that you are likely to need special (usually binary) drivers from outside the kernel for are graphics, network and sound. These are described in more detail below. MattBrown has a Gigabyte GA-7N400Pro motherboard and CraigBox has a Soltek 75-FRN-RL and this page is based mostly on experiences with those.
-First of all download the nvidia driver package from the following URL (You may want to check for a more recent version)
-
http://www.nvidia.com/view.asp?IO=
linux_nforce_1
.-0261
+First of all download the most recent
nvidia driver package from [NVIDIA's NForce driver archive|
http://www.nvidia.com/object/
linux_nforce_archive.html]
.
!! Graphics
You need NVIDIA AGPGART support, and you get this by using 2.4.22+ or 2.6.3+ Some people have experienced performance issues with 8x AGP using kernels before 2.6.3. See RadeonNotes for more on getting an ATI card to work.
@@ -10,14 +9,18 @@
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 [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.
+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. This means you do not need to patch your kernel if you are running one of these kernels!
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)
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.
+
+! Wake On LAN
+
+The nvnet driver claims to support [WOL], but doesn't. The forcedeth driver supports [WOL], but seems to disable it by default. You need a program called ethtool to set the WOL status each time you boot. See WakeOnLanNotes for more details.
!! 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.
@@ -46,9 +49,9 @@
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.
-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:
+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 (modprobe.conf in Linux 2.6)
file:
<verbatim>
options snd-pcm-oss dsp_map=2 adsp_map=2
</verbatim>
@@ -57,9 +60,10 @@
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)
+### /etc/asound.conf for nforce2 apu
+###
(analog out, from http://www.wlug.org.nz/NForce2Notes)
pcm.!default {
type plug
slave.pcm "nforce"
@@ -80,9 +84,11 @@
!Digital output
<verbatim>
-### /etc/asound.conf for nforce2 apu (digital out, from http://www.wlug.org.nz/NForce2Notes)
+### /etc/asound.conf for nforce2 apu
+###
(digital out, from http://www.wlug.org.nz/NForce2Notes)
+
pcm.nforce-hw {
type hw
card 0
}
