Skip to contentSkip to conversation

How's the nforce4 support in Linux?

DISCUSSION Asfand Yar Qazi 8 participants 8 messages Mar 24, 2005 – Mar 25, 2005 3 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#3 lore raw
Quoted 9 lines · Arjan van de Ven
Quoted 3 lines

* "hardware firewall" -- sounds silly. Pretty sure Linux doesn't support it in any case.

probably just one of those things implemented in the binary drivers in software, just like the "hardware" IDE raid is most of the time (3ware being the positive exception there)

http://www.neoseeker.com/Articles/Hardware/Previews/nvnforce4/3.html

You're right there - some semi-hardware support combined with drivers apparently result in lower CPU usage that software firewalls. Apparently.

Actually, these people like it:
http://www.bjorn3d.com/read.php?cID=712&pageID=1096

However one feature that you can't laugh at is the fact that it can be made to block packets in the span of time between the OS being loaded up, and the "real" firewall coming up. This small time span theoretically leaves the PC vulnerable, so I think this is the only use for "ActiveAmor Firewall".

However, this doesn't answer my original question (which I suppose I should have made clearer): can I get SATA II NCQ support in Linux with an nForce 4 chipset?

#5 lore raw
In reply to Asfand Yar Qazi
Quoted 11 lines · Asfand Yar Qazi
Quoted 9 lines · Arjan van de Ven
Quoted 3 lines

* "hardware firewall" -- sounds silly. Pretty sure Linux doesn't support it in any case.

probably just one of those things implemented in the binary drivers in software, just like the "hardware" IDE raid is most of the time (3ware being the positive exception there)

Quoted 4 lines

http://www.neoseeker.com/Articles/Hardware/Previews/nvnforce4/3.html

You're right there - some semi-hardware support combined with drivers apparently result in lower CPU usage that software firewalls. Apparently.

lower CPU usage than the *windows* firewall.
While there is a potential gain from a firewall function on the other side of the PCI bus, this gain is when you reject most packets. Eg you save "bad" packets from going over the bus. Now the question is how many bad packets do you get per second...

Quoted 5 lines

However one feature that you can't laugh at is the fact that it can be made to block packets in the span of time between the OS being loaded up, and the "real" firewall coming up. This small time span theoretically leaves the PC vulnerable, so I think this is the only use for "ActiveAmor Firewall".

This is a joke right? In linux at least, the OS doesn't get packets unless it asks for it; I can't imagine any other OS doing that differently (since most are somewhat based on the same model). And all linux distros I know of first install the firewall rules and then tell the NIC to start receiving packets. In that order. I don't know how windows does it (and I don't care), but if it gets this wrong it would be a really bad bug in windows. But I guess it'd give the chipset marketing people something to boast about ;)

#6 lore raw
In reply to Asfand Yar Qazi
Quoted 5 lines · Asfand Yar Qazi

http://www.neoseeker.com/Articles/Hardware/Previews/nvnforce4/3.html

You're right there - some semi-hardware support combined with drivers apparently result in lower CPU usage that software firewalls. Apparently.

Quoted 8 lines

Actually, these people like it:
http://www.bjorn3d.com/read.php?cID=712&pageID=1096

However one feature that you can't laugh at is the fact that it can be made to block packets in the span of time between the OS being loaded up, and the "real" firewall coming up. This small time span theoretically leaves the PC vulnerable, so I think this is the only use for "ActiveAmor Firewall".

Until the OS loads network drivers AND configures IP support AND starts accepting packets in, there is nothing for the firewall to do. Certainly on Linux I can make sure iptables is populated (or least has a sane policy set) before I bring up networking. In other words: "Who cares".

Quoted 3 lines

However, this doesn't answer my original question (which I suppose I should have made clearer): can I get SATA II NCQ support in Linux with an nForce 4 chipset?

Don't know. I think 3ware's controllers do their own NCQ, which is pretty neat.

Len Sorensen

#7 lore raw
Quoted 5 lines · Lennart Sorensen

Until the OS loads network drivers AND configures IP support AND starts accepting packets in, there is nothing for the firewall to do. Certainly on Linux I can make sure iptables is populated (or least has a sane policy set) before I bring up networking. In other words: "Who cares".

guess that's a windows thing...

#8 lore raw
In reply to Asfand Yar Qazi
Quoted 1 line · Asfand Yar Qazi

However, this doesn't answer my original question (which I suppose I should have made clearer): can I get SATA II NCQ support in Linux with an nForce 4 chipset?

I answered this question already. The answer is no.

Jeff

#9 lore raw
In reply to a message not in the archive
Quoted 8 lines · Asfand Yar Qazi

NForce4 Ultra is brilliant - in many ways. Except it requires binary drivers, which I really don't want to use. And apparently, the hardware firewall seems to restrict bandwidth a bit. And even when its off, external chips that end up being faster (http://tinyurl.com/4zssp)

So, I'm wondering, are my assumptions correct? Do I have to use binary drivers to make absolutely full use of the Nforce4 chipset? Or is there sufficient support for me to make use of the features on it without using binary drivers?

Sorry for asking something that may have been asked before, but I've tried searching several times through the mailing list and on a search engine, but have had little luck.

Thanks,
Asfand Yar

There is no need to use any binary drivers on the nForce4 - the only ones even available are for the network and audio. The network works fine with the forcedeth driver included in the kernel - I don't know about the audio, I'm not using the onboard sound.

Some wrinkles with Linux support are that you may need to update the X server (ex: X.org) as there are some bugs with PCI Express video on x86_64 that were fixed somewhat recently - as well there was a bug with USB port detection that cropped up in kernel 2.6.10 and I believe is fixed in 2.6.11.

The nForce4 chipset supports NCQ on the SATA interface, however this is not supported in Linux yet. It seems like the SATA controller has some similarity or is based on the ADMA architecture (the Windows driver is called "NVIDIA nForce4 ADMA Controller", so using it with the ADMA driver might be doable at some point, though I haven't heard of any hardware specs being released..

Signature · 3 lines
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from [email protected]
Home Page: http://www.roberthancock.com/
#10 lore raw
Quoted 4 lines · Robert Hancock

There is no need to use any binary drivers on the nForce4 - the only ones even available are for the network and audio. The network works fine with the forcedeth driver included in the kernel - I don't know about the audio, I'm not using the onboard sound.

Your statement is self contradictory. How can you say there's no need to use binary drivers if you don't know anything about the audio support? Many users consider sound a critical feature.

As a matter of fact there are a few quirks with the audio on Nvidia chipsets, due to (surprise) lack of documentation.

Lee