On Monday 16 October 2006 18:15, Andriy Gapon wrote: > In STABLE and upcoming 6.2 (and in CURRENT, of course) there is a new > SMB driver for NForce2/3/4 chipsets, nfsmb, developed by Ruslan Ermilov. > However, the driver doesn't currently work on all hardware that it is to > support. The problem is with choosing proper BAR registers, which, as it > seems, might be different for different chipsets/SMB controllers. > > If you have a system based on NForce2/3/4, could you please share the > following information: > > 1. find out pci handle of your SMB controller: > $ pciconf -l | fgrep 0x0c0500 > and also note chip field value, it should match 00(64|84|d4|e4|52)10de. > E.g.: > [EMAIL PROTECTED]:1:1: class=0x0c0500 card=0x1c02147b chip=0x006410de > rev=0xa2 hdr=0x00 > > 2. read values in BARs 4 and 5 and also registers 0x50 and 0x54 like > follows: > $ pciconf -r pci0:1:1 0x20 > $ pciconf -r pci0:1:1 0x24 > $ pciconf -r pci0:1:1 0x50 > $ pciconf -r pci0:1:1 0x54 > using your pci handle instead of pci0:1:1, e.g.: > $ pciconf -r pci0:1:1 0x20 > 00000000 > $ pciconf -r pci0:1:1 0x24 > 00000000 > $ pciconf -r pci0:1:1 0x50 > 00001001 > $ pciconf -r pci0:1:1 0x54 > 00001041 > > 3. send chip id and register values here. > > Thank you very much in advance.
Tyan Thunder K8WE (S2895) data# pciconf -lv | fgrep 0x0c0500 [EMAIL PROTECTED]:1:1: class=0x0c0500 card=0x289510f1 chip=0x005210de rev=0xa2 hdr=0x00 data# pciconf -r pci0:1:1 0x20 0000a001 data# pciconf -r pci0:1:1 0x24 0000a041 data# pciconf -r pci0:1:1 0x50 0000a001 data# pciconf -r pci0:1:1 0x54 0000a041 -- ian j hart _______________________________________________ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"