IT geek 31 | 11 Jan 2011 13:34

Fwd: Gigabit PCI network card for Qube2

Hi Mark,

Did you have to configure a special kernel for the Intel Pro/1000 GT
card to be seen?

I have bought one and put it in, but it doesn't show up either at boot
or in dmesg :-(

Any ideas?

Cobalt Microserver Diagnostics - 'We serve it, you surf it'
Built Tue May 25 15:58:41 PDT 1999

 1.LCD Test................................PASS
 2.Controller Test.........................PASS
 5.Bank 0:.................................64M
 6.Bank 1:.................................64M
 7.Bank 2:.................................64M
 8.Bank 3:.................................64M
 9.Serial Test.............................PASS
10.PCI Expansion Slot....................**Unknown Card**
12.IDE Test................................PASS
13.Ethernet Test...........................PASS
16.RTC Test................................PASS
BOOTLOADER ramcode: selected partition /dev/hda1
Decompressing done
Executing bootloader kernel...
Decompressing -- done.

>> NetBSD/cobalt 5.1 Bootloader, Revision 0.9 [ <at> 0x80f00000]
(Continue reading)

IT geek 31 | 11 Jan 2011 13:39

Re: Gigabit PCI network card for Qube2

Actually, my mistake - I get the following in dmesg:

Intel i82541PI Gigabit Ethernet (ethernet network, revision 0x05) at
pci0 dev 10 function 0 not configured

On 31 December 2010 06:22, Mark Smith <markinnz <at> gmail.com> wrote:
> Hi there,
>
> Well I've put the Intel Pro/1000 GT into the Qube2 and it does indeed work :-)
> This is the output of ifconfg:
>
> qube2# ifconfig -a
> tlp0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
>        address: 00:10:e0:00:47:ff
>        media: Ethernet autoselect (none)
>        status: no carrier
> wm0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>        capabilities=2bf80<TSO4,IP4CSUM_Rx,IP4CSUM_Tx,TCP4CSUM_Rx,TCP4CSUM_Tx,UDP4CSUM_Rx,UDP4CSUM_Tx,TCP6CSUM_Tx,UDP6CSUM_Tx>
>        enabled=0
>        address: 00:15:17:0e:b8:e2
>        media: Ethernet autoselect (1000baseT full-duplex,flowcontrol,rxpause,txpause)
>        status: active
>        inet 192.168.0.5 netmask 0xffffff00 broadcast 192.168.0.255
>        inet6 fe80::215:17ff:fe0e:b8e2%wm0 prefixlen 64 scopeid 0x2
> tlp1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
>        address: 00:10:e0:00:48:0f
>        media: Ethernet autoselect (none)
>        status: no carrier
>
>
(Continue reading)

IT geek 31 | 12 Jan 2011 14:11

Re: Gigabit PCI network card for Qube2

Hi Mark,

Yes that would be great!  Please add some numpty instructions on how
to boot to it too (Linux is my thing, NetBSD kernels I have never
touched).

Many thanks,

-Mark

On 12 January 2011 05:01, Mark Smith <markinnz <at> gmail.com> wrote:
>
> On 12/01/2011, at 1:32 AM, IT geek 31 wrote:
>
>> Hi Mark,
>>
>> Did you have to configure a special kernel for the Intel Pro/1000 GT
>> card to be seen?
>>
>> I have bought one and put it in, but it doesn't show up either at boot
>> or in dmesg :-(
>>
>> Any ideas?
>>
>>
> Hi there,
>
> Yes I compiled a new kernel with the Intel drivers in it.  Just did it on the Qube2 itself, set it to compile
and went to bed :-)  Was all done by morning.
>
(Continue reading)

IT geek 31 | 18 Jan 2011 22:52

Re: Gigabit PCI network card for Qube2

Hi Mark,

Yes that would be great!  Please add some numpty instructions on how
to boot to it too (Linux is my thing, NetBSD kernels I have never
touched).

Many thanks,

-Mark

On 12 January 2011 05:01, Mark Smith <markinnz <at> gmail.com> wrote:
>
> On 12/01/2011, at 1:32 AM, IT geek 31 wrote:
>
>> Hi Mark,
>>
>> Did you have to configure a special kernel for the Intel Pro/1000 GT
>> card to be seen?
>>
>> I have bought one and put it in, but it doesn't show up either at boot
>> or in dmesg :-(
>>
>> Any ideas?
>>
>>
> Hi there,
>
> Yes I compiled a new kernel with the Intel drivers in it.  Just did it on the Qube2 itself, set it to compile
and went to bed :-)  Was all done by morning.
>
(Continue reading)

Martin Mersberger | 19 Jan 2011 21:10
Picon
Favicon

Re: port-cobalt/44331 (current hangs before/in init(8))

Hi...

>> I there anything, I can help your with?
> 
> Try this patch.
> http://mail-index.netbsd.org/netbsd-bugs/2011/01/19/msg020843.html
looks good:

Copyright (c) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005,
    2006, 2007, 2008, 2009, 2010, 2011
    The NetBSD Foundation, Inc.  All rights reserved.
Copyright (c) 1982, 1986, 1989, 1991, 1993
    The Regents of the University of California.  All rights reserved.

NetBSD 5.99.44 (GENERIC-PF) #2: Wed Jan 19 16:24:11 CET 2011
	root <at> builder:/usr/obj/sys/arch/cobalt/compile/GENERIC-PF
Cobalt RaQ
total memory = 128 MB
avail memory = 120 MB
timecounter: Timecounters tick every 10.000 msec
mainbus0 (root)
com0 at mainbus0 addr 0x1c800000 level 3: st16650a, working fifo
com0: console
cpu0 at mainbus0: QED RM5200 CPU (0x2810) Rev. 1.0 with built-in FPU
Rev. 1.0
cpu0: 48 TLB entries, 16MB max page size
cpu0: 16KB/32B 2-way set-associative L1 Instruction cache
cpu0: 16KB/32B 2-way set-associative write-back L1 Data cache
mcclock0 at mainbus0 addr 0x10000070: mc146818 compatible time-of-day clock
panel0 at mainbus0 addr 0x1f000000
(Continue reading)

Mark Smith | 29 Jan 2011 08:52
Picon

Intel Pro 1000 in a Qube2 .. unknown PHY ?

Hi there,

The Intel Pro/1000 GT is running in my Qube 2 but there is one last bit that is unhappy :

wm0 at pci0 dev 10 function 0: Intel i82541PI 1000BASE-T Ethernet, rev. 5
wm0: interrupting at irq 9
wm0: 32-bit 33MHz PCI bus
wm0: 64 word (6 address bits) MicroWire EEPROM
wm0: Ethernet address 00:15:17:0e:b8:e2
OUI 0x005500 model 0x0038 rev 0 at wm0 phy 1 not configured
OUI 0x005500 model 0x0038 rev 0 at wm0 phy 1 not configured

I think it's complaining that it doesn't know what PHY to use ?  Anyone with more smarts than me able to tell me
what it means ?

I can dump the config of my kernel if you need.

Thanks!

Mark

Izumi Tsutsui | 29 Jan 2011 09:29
Picon
Gravatar

Re: Intel Pro 1000 in a Qube2 .. unknown PHY ?

> OUI 0x005500 model 0x0038 rev 0 at wm0 phy 1 not configured
> OUI 0x005500 model 0x0038 rev 0 at wm0 phy 1 not configured
> 
> I think it's complaining that it doesn't know what PHY to use ?
> Anyone with more smarts than me able to tell me what it means ?

% grep 0x005500 /usr/src/sys/dev/mii/miidevs
oui yyINTEL			0x005500	Intel
% grep 0x0038 /usr/src/sys/dev/mii/miidevs
model yyINTEL IGP01E1000	0x0038 Intel IGP01E1000 Gigabit PHY
% grep IGP01 /usr/src/sys/arch/i386/conf/ALL
igphy*	at mii? phy ?			# Intel IGP01E1000

---
Izumi Tsutsui

Mark Smith | 29 Jan 2011 10:47
Picon

Re: Intel Pro 1000 in a Qube2 .. unknown PHY ?


On 29/01/2011, at 9:29 PM, Izumi Tsutsui wrote:

>> OUI 0x005500 model 0x0038 rev 0 at wm0 phy 1 not configured
>> OUI 0x005500 model 0x0038 rev 0 at wm0 phy 1 not configured
>> 
>> I think it's complaining that it doesn't know what PHY to use ?
>> Anyone with more smarts than me able to tell me what it means ?
> 
> % grep 0x005500 /usr/src/sys/dev/mii/miidevs
> oui yyINTEL			0x005500	Intel
> % grep 0x0038 /usr/src/sys/dev/mii/miidevs
> model yyINTEL IGP01E1000	0x0038 Intel IGP01E1000 Gigabit PHY
> % grep IGP01 /usr/src/sys/arch/i386/conf/ALL
> igphy*	at mii? phy ?			# Intel IGP01E1000
> 

Ahh thanks! :-)

Is there a central bit of documentation that lists all of what you need to add to a kernel config file to get
drivers working ?  (sort of "if you have hardware xxxx then add yyyy to the config file" ?)

I did "man mii" and it didn't list "igphy" only "inphy, oiphy and ikphy" ... guess you either have to be
psychic or been a NetBSD guru since day 1  :-)

I'll go add that to my config and rebuild.

Thanks

Mark
(Continue reading)

Mark Smith | 29 Jan 2011 12:12
Picon

Intel Pro/1000 in a Qube2 observations

Hi there,

Since things appear to be working with this board I've done a few rough tests with some interesting results
(only 100BaseT results at the moment as thats all my current router/hub supports)

1)  By default the hardware checksums are not enabled ... which seems kind of odd you can see the before and
after here :

	Before:
	qube2# ifconfig -v wm0
		wm0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        	capabilities=2bf80<TSO4,IP4CSUM_Rx,IP4CSUM_Tx,TCP4CSUM_Rx,TCP4CSUM_Tx,UDP4CSUM_Rx,UDP4CSUM_Tx,TCP6CSUM_Tx,UDP6CSUM_Tx>
        	enabled=0
        	address: 00:15:17:0e:b8:e2
        	media: Ethernet autoselect (100baseTX full-duplex,flowcontrol,rxpause,txpause)
        	status: active
      	  	input: 556569 packets, 42363982 bytes, 410 multicasts
        	output: 922440 packets, 1358364969 bytes, 7 multicasts
        	inet 192.168.0.7 netmask 0xffffff00 broadcast 192.168.0.255
       	 	inet6 fe80::215:17ff:fe0e:b8e2%wm0 prefixlen 64 scopeid 0x2

	then run :  ifconfig wm0 ip4csum tcp4csum udp4csum

	After:
	qube2# ifconfig -v wm0
		wm0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        	capabilities=2bf80<TSO4,IP4CSUM_Rx,IP4CSUM_Tx,TCP4CSUM_Rx,TCP4CSUM_Tx,UDP4CSUM_Rx,UDP4CSUM_Tx,TCP6CSUM_Tx,UDP6CSUM_Tx>
        	enabled=3f00<IP4CSUM_Rx,IP4CSUM_Tx,TCP4CSUM_Rx,TCP4CSUM_Tx,UDP4CSUM_Rx,UDP4CSUM_Tx>
        	address: 00:15:17:0e:b8:e2
        	media: Ethernet autoselect (100baseTX full-duplex,flowcontrol,rxpause,txpause)
(Continue reading)

Izumi Tsutsui | 29 Jan 2011 13:21
Picon
Gravatar

Re: Intel Pro 1000 in a Qube2 .. unknown PHY ?

> Is there a central bit of documentation that lists all of what
> you need to add to a kernel config file to get drivers working ?

Well we always have less man power for up-to-date docs...
("may the sources be with you" :-)

Of course any documentation patches (via send-pr etc) are appreciated.

> (sort of "if you have hardware xxxx then add yyyy to the config file" ?)

Combinations of MAC controllers/PHY chips are quite independent
so no trivial way to maintain a list of existing boards.

The simplest way is to put all supported mii devices
(probably you can see it in arch/i386/conf/ALL or dev/mii/files.mii)
into a config file and see which one is matched.
(though other unused drivers simply waste RAMs)

ukphy(4) might work as a generic one if there is no chip
specific PHY drivers.

---
Izumi Tsutsui


Gmane