2009-03-09 17:48:40

by Kiko Piris

[permalink] [raw]
Subject: pcnet32 not working under 2.6.27.19

Hi,

I have a netfinity 5100 server with the following ethernet nic:

| # lspci -v -s 00:02.0
| 00:02.0 Ethernet controller: Advanced Micro Devices [AMD] 79c970 [PCnet32 LANCE] (rev 44)
| Subsystem: IBM NetFinity 10/100 Fast Ethernet
| Flags: bus master, medium devsel, latency 48, IRQ 15
| I/O ports at 2000 [size=32]
| Memory at feb7fc00 (32-bit, non-prefetchable) [size=32]
| [virtual] Expansion ROM at 20000000 [disabled] [size=1M]
| Capabilities: [40] Power Management version 2
| Kernel driver in use: pcnet32

I’ve compiled 2.6.27.19 and I cannot get the interface to go up (pcnet32
is compiled into the kernel, not as a module, in fact this kernel does
not have module support). 2.6.27.19 config is attached.

“ifconfig eth0 up” returns this error: «SIOCSIFFLAGS: Resource
temporarily unavailable» (whether I give it an address or not).

I can’t tell for sure if it’s all my mistake or what. The funny thing is
that with 2.6.28.7 it works perfectly.

An excerpt from dmesg gives me exactly the same with both kernels:

| # dmesg | egrep -i "pcnet|eth0"
| [ 0.280481] pcnet32.c:v1.35 21.Apr.2008 [email protected]
| [ 0.286687] pcnet32: PCnet/FAST III 79C975 at 0x2000, 00:02:55:7c:fe:90 assigned IRQ 15.
| [ 0.295970] pcnet32: Found PHY 0000:6b60 at address 30.
| [ 0.301501] eth0: registered as PCnet/FAST III 79C975
| [ 0.306670] pcnet32: 1 cards_found.

Well, 2.6.28.7 notifies me about “link up” (2.6.27.19, obviously, does
not):

| [ 45.453962] eth0: link up, 100Mbps, full-duplex

As 2.6.27 will be long term supported and this is a production server
(debian stable), I would like very much to be able to use it on this
server.

Could someone help me and tell me I’m doing something wrong of if
something is missing on 2.6.27 ?

I also don’t know which additional information I could provide, please
ask.

Many tanks in advance!

--
Kiko


Attachments:
(No filename) (1.91 kB)
config-2.6.27.19 (12.98 kB)
Download all attachments