Re: nfsmb survey

2006-10-24 Thread Conrad J. Sabatier
On Mon, 16 Oct 2006 21:31:28 +0300, Cheffo [EMAIL PROTECTED] wrote: 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

Re: nfsmb survey

2006-10-18 Thread Nikolay Pavlov
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.

Re: nfsmb survey

2006-10-18 Thread ian j hart
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

Re: nfsmb survey

2006-10-18 Thread Miroslav Lachman
1. find out pci handle of your SMB controller: # pciconf -lv | fgrep 0x0c0500 -A 4 [EMAIL PROTECTED]:1:1: class=0x0c0500 card=0x5348108e chip=0x005210de rev=0xa2 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'nForce4 SMBus' class= serial bus subclass = SMBus 2.

Re: nfsmb survey

2006-10-17 Thread Andriy Gapon
Big thanks to everybody who responded! It would be great to get more information about the following chip ids for which we haven't got any reports yet: 00d410denVidia Corporation nForce3 Pro150 SMBus (MCP) 003410denVidia Corporation nForce4 SMBus (MCP-04) 036810denVidia

Re: nfsmb survey

2006-10-17 Thread Karol Kwiatkowski
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.:

Re: nfsmb survey

2006-10-16 Thread Jeremy Chadwick
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

Re: nfsmb survey

2006-10-16 Thread Torfinn Ingolfsen
On Mon, 16 Oct 2006 20:15:26 +0300 Andriy Gapon [EMAIL PROTECTED] wrote: System 1 is a MSI MS-7093 mainboard (aka RS480M2-IL) running [EMAIL PROTECTED] uname -a FreeBSD kg-fil.kg4.no 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #9: Tue Oct 3 23:08:46 CEST 2006 [EMAIL

Re: nfsmb survey

2006-10-16 Thread Andrew Degtiariov
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.: [EMAIL PROTECTED]:1:1:class=0x0c0500 card=0x1c02147b chip=0x006410de rev=0xa2 hdr=0x00 2. read values in BARs 4

nfsmb survey

2006-10-16 Thread Andriy Gapon
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,

Re: nfsmb survey

2006-10-16 Thread Art Mason
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

Re: nfsmb survey

2006-10-16 Thread Zakharov Vladimir
On Mon, Oct 16, 2006, Andriy Gapon wrote: 1. find out pci handle of your SMB controller: # pciconf -lv | fgrep 0x0c0500 -A 4 [EMAIL PROTECTED]:1:1:class=0x0c0500 card=0x0c111043 chip=0x006410de rev=0xa2 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'nForce MCP-T? SMBus

Re: nfsmb survey

2006-10-16 Thread Cheffo
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,

Re: nfsmb survey

2006-10-16 Thread Boris Samorodov
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

Re: nfsmb survey

2006-10-16 Thread Andrew Reilly
$ sudo pciconf -l | fgrep 0x0c0500 [EMAIL PROTECTED]:1:1: class=0x0c0500 card=0x0c111458 chip=0x005210de rev=0xa2 hdr=0x00 $ sudo pciconf -r pci0:1:1 0x20 1c01 $ sudo pciconf -r pci0:1:1 0x24 1c41 $ sudo pciconf -r pci0:1:1 0x50 1c01 $ sudo pciconf -r pci0:1:1 0x54 1c41 This

Re: nfsmb survey

2006-10-16 Thread Dan
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