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.: nfsmb0@pci0: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. -- Andriy Gapon
On Monday 16 October 2006 12: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.: > nfsmb0@pci0: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.Hope this helps. Motherboard is an Asus A8N (non-SLI) Socket 939 part w/ an nForce 4 chipset: 6.1-RELEASE FreeBSD 6.1-RELEASE #0 (GENERIC) pciconf -l | fgrep 0x0c0500 none1@pci0:1:1: class=0x0c0500 card=0x815a1043 chip=0x005210de rev=0xa2 hdr=0x00 pciconf -r pci0:1:1 0x20 00004c01 pciconf -r pci0:1:1 0x24 00004c41 pciconf -r pci0:1:1 0x50 00004c01 pciconf -r pci0:1:1 0x54 00004c41 Let me know if I can provide any additional information, or correct information if I did this wrong, ha! Cheers, -- Art Mason amason@rackspace.com Intensive Network Security Rackspace Managed Hosting (800) 961-4454 ext. 4290
On Mon, Oct 16, 2006, Andriy Gapon wrote:> 1. find out pci handle of your SMB controller:# pciconf -lv | fgrep 0x0c0500 -A 4 nfsmb0@pci0:1:1: class=0x0c0500 card=0x0c111043 chip=0x006410de rev=0xa2 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'nForce MCP-T? SMBus Controller' class = serial bus subclass = SMBus> 2. read values in BARs 4 and 5 and also registers 0x50 and 0x54# pciconf -r pci0:1:1: 0x20 00000000 # pciconf -r pci0:1:1: 0x24 00000000 # pciconf -r pci0:1:1: 0x50 00005001 # pciconf -r pci0:1:1: 0x54 00005501> 3. send chip id and register values here.# uname -a FreeBSD 6.2-PRERELEASE Mon Oct 16 21:31:17 MSD 2006 i386
On Mon, Oct 16, 2006 at 08:15:26PM +0300, 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.Andriy, Does this issue also cover the situation where if a kernel is built with ichsmb *and* nfsmb, and is run on an NForce2/3/4 board, the ichsmb driver is chosen/bound to one of the two SMBus devices, when in fact nfsmb should bind to both? (Only after removing ichsmb from the kernel configuration did nfsmb bind to both). Just curious -- thanks! -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |
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.: > nfsmb0@pci0: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. > >none1@pci0:1:1: class=0x0c0500 card=0x815a1043 chip=0x005210de rev=0xa2 hdr=0x00 pciconf -r pci0:1:1 0x20 00004c01 pciconf -r pci0:1:1 0x24 00004c41pciconf -r pci0:1:1 0x50 00004c01 pciconf -r pci0:1:1 0x54 00004c41 FreeBSD cheffo.freebsd-bg.org 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #10: Sun Oct 8 20:01:14 EEST 2006
On Mon, 16 Oct 2006 20:15:26 +0300 Andriy Gapon <avg@icyb.net.ua> wrote: System 1 is a MSI MS-7093 mainboard (aka RS480M2-IL) running root@kg-fil# uname -a FreeBSD kg-fil.kg4.no 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #9: Tue Oct 3 23:08:46 CEST 2006 root@kg-fil.kg4.no:/usr/obj/usr/src/sys/FIL60 amd64> 1. find out pci handle of your SMB controller:root@kg-fil# pciconf -lv | fgrep 0x0c0500 -A4 none1@pci0:1:1: class=0x0c0500 card=0x0c111458 chip=0x005210de rev=0xa2 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'nForce4 SMBus' class = serial bus subclass = SMBus> 2. read values in BARs 4 and 5 and also registers 0x50 and 0x54 likeroot@kg-fil# pciconf -r pci0:1:1: 0x20 00001c01 root@kg-fil# pciconf -r pci0:1:1: 0x24 00001c41 root@kg-fil# pciconf -r pci0:1:1: 0x50 00001c01 root@kg-fil# pciconf -r pci0:1:1: 0x54 00001c41 System 2 is a Gigabyte GA-K8-NF-9 mainboard running FreeBSD kg-quiet.kg4.no 6.1-STABLE FreeBSD 6.1-STABLE #10: Wed Oct 11 19:49:47 CEST 2006 root@kg-quiet.kg4.no:/usr/obj/usr/src/sys/QUIET amd64> 1. find out pci handle of your SMB controller:root@kg-quiet# pciconf -lv | fgrep 0x0c0500 -A4 none0@pci0:20:0: class=0x0c0500 card=0x71411462 chip=0x43721002 rev=0x04 hdr=0x00 vendor = 'ATI Technologies Inc' device = 'SMBus' class = serial bus subclass = SMBus So I guess this is a different SMBus controller, and will not be supported by this driver? HTH -- Regards, Torfinn Ingolfsen, Norway
On Mon, Oct 16, 2006 at 08:15:26PM +0300, Andriy Gapon wrote:> $ pciconf -l | fgrep 0x0c0500 > and also note chip field value, it should match 00(64|84|d4|e4|52)10de. > E.g.: > nfsmb0@pci0: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.$ pciconf -l | fgrep 0x0c0500 none1@pci0:1:1: class=0x0c0500 card=0x286510f1 chip=0x005210de rev=0xa2 hdr=0x00 # pciconf -r pci0:1:1 0x20 00001c01 # pciconf -r pci0:1:1 0x24 00001c41 # pciconf -r pci0:1:1 0x50 00001c01 # pciconf -r pci0:1:1 0x54 00001c41 -- Andrew Degtiariov DA-RIPE
On Mon, 16 Oct 2006 20:15:26 +0300 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%pciconf -lv | fgrep 0x0c0500 -A3 none9@pci0:10:1: class=0x0c0500 card=0x1b571019 chip=0x026410de rev=0xa3 hdr=0x00 vendor = 'NVIDIA Corporation' class = serial bus subclass = SMBus> 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# pciconf -r pci0:10:1 0x20 00001c01 # pciconf -r pci0:10:1 0x24 00001c41 # pciconf -r pci0:10:1 0x50 00000000 # pciconf -r pci0:10:1 00000000 WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD committer, http://www.FreeBSD.org The Power To Serve
$ sudo pciconf -l | fgrep 0x0c0500 none1@pci0:1:1: class=0x0c0500 card=0x0c111458 chip=0x005210de rev=0xa2 hdr=0x00 $ sudo pciconf -r pci0:1:1 0x20 00001c01 $ sudo pciconf -r pci0:1:1 0x24 00001c41 $ sudo pciconf -r pci0:1:1 0x50 00001c01 $ sudo pciconf -r pci0:1:1 0x54 00001c41 This is on an nForce 4/AMD64-X2 system. Hope this helps. Cheers, -- Andrew
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.: > nfsmb0@pci0:1:1: class=0x0c0500 card=0x1c02147b chip=0x006410de > rev=0xa2 hdr=0x00(root)# uname -a FreeBSD storm 6.1-STABLE FreeBSD 6.1-STABLE #1: Mon May 22 23:55:36 BST 2006 root@storm:/usr/obj/usr/src/sys/GENERIC i386 (root)# pciconf -lv | fgrep 0x0c0500 -A 4 none1@pci0:1:1: class=0x0c0500 card=0x0c111458 chip=0x005210de rev=0xa2 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'nForce4 SMBus' class = serial bus subclass = SMBus> 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(root)# pciconf -r pci0:1:1 0x20 00001c01 (root)# pciconf -r pci0:1:1 0x24 00001c41 (root)# pciconf -r pci0:1:1 0x50 00001c01 (root)# pciconf -r pci0:1:1 0x54 00001c41
On 16/10/2006 19:15, Andriy Gapon wrote:> 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.: > nfsmb0@pci0:1:1: class=0x0c0500 card=0x1c02147b chip=0x006410de > rev=0xa2 hdr=0x00# uname -srp FreeBSD 6.2-PRERELEASE i386 # pciconf -lv | fgrep 0x0c0500 -A 4 nfsmb0@pci0:1:1: class=0x0c0500 card=0x00841849 chip=0x008410de rev=0xa1 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'nForce MCP2S PCI System Management' class = serial bus subclass = SMBus> 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# pciconf -r pci0:1:1 0x20 00000000 # pciconf -r pci0:1:1 0x24 00000000 # pciconf -r pci0:1:1 0x50 00004301 # pciconf -r pci0:1:1 0x54 00004301 Cheers, Karol -- Karol Kwiatkowski <freebsd at orchid dot homeunix dot org> OpenPGP: http://www.orchid.homeunix.org/carlos/gpg/0x06E09309.asc -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 250 bytes Desc: OpenPGP digital signature Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20061017/578affde/signature.pgp
On Monday, 16 October 2006 at 20:15:26 +0300, 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.: > nfsmb0@pci0: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. > > -- > Andriy Gapon > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"root@viking:~# pciconf -l | fgrep 0x0c0500 none0@pci0:1:1: class=0x0c0500 card=0x813f1043 chip=0x00e410de rev=0xa1 hdr=0x00 root@viking:~# pciconf -r pci0:1:1 0x20 00005001 root@viking:~# pciconf -r pci0:1:1 0x24 00005041 root@viking:~# pciconf -r pci0:1:1 0x50 00005001 root@viking:~# pciconf -r pci0:1:1 0x54 00005041 -- ====================================================================== - Best regards, Nikolay Pavlov. <<<----------------------------------- ======================================================================
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.: > nfsmb0@pci0: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 nfsmb0@pci0: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
> 1. find out pci handle of your SMB controller:# pciconf -lv | fgrep 0x0c0500 -A 4 none1@pci0:1:1: class=0x0c0500 card=0x5348108e chip=0x005210de rev=0xa2 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'nForce4 SMBus' class = serial bus subclass = SMBus> 2. read values in BARs 4 and 5 and also registers 0x50 and 0x54 like > follows:# pciconf -r pci0:1:1 0x20 00001c01 # pciconf -r pci0:1:1 0x24 00001c41 # pciconf -r pci0:1:1 0x50 00001c01 # pciconf -r pci0:1:1 0x54 00001c41 FreeBSD 6.2-BETA2 FreeBSD 6.2-BETA2 #0: Mon Oct 2 03:22:01 UTC 2006 root@opus.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386