Opened 16 years ago
Closed 16 years ago
#3192 closed enhancement (fixed)
nForce Driver needs updating
Reported by: | Luposian | Owned by: | axeld |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | Drivers/Network | Version: | R1/pre-alpha1 |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | x86 |
Description
On my Acer micro tower system, there was no functioning networking. Upon discovery that the majority of the mainboard is based on the nForce chipset (which is supported in the Haiku driver set), it was realized that the issue was likely that the nForce driver hadn't been updated recently (there are several, more recent, nForce chipsets that are not in the current driver).
Since then, Tonestone made an updated nForce driver binary available to me (which works fine, so far as I've used it), but it was suggested by Urias, I report a ticket here, to make sure it is properly addressed/handled by the devs.
Change History (5)
comment:1 by , 16 years ago
comment:2 by , 16 years ago
Looks like these two diffs might be the relevant ones (although there are some other changes in the last few months as well - including something related to jumbo frame support)
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/nfe/if_nfe.c.diff?r1=1.28;r2=1.29
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/nfe/if_nfereg.h.diff?r1=1.12;r2=1.13
comment:4 by , 16 years ago
I'm currently replying via Firefox 2.0.0.18, in Haiku R28761, so I think it's safe to call this ticket closed, unless anyone else wants to add something. Thanks to all (or just Korli?) for such a quick turn-around after I posted this ticket. Guess it DOES pay to do things the right way. :-) I'll remember that from now on.
comment:5 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Surely it's updatable. Could you just give details about your chip version (pci id) and confirm it's actually the nfe driver in src/add-ons/kernel/drivers/network/nforce/ ?