• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Issue with driver on Debian

C

ChrisCanada

n00b
Joined
Sep 23, 2009
Messages
26
So I just put together a "new" computer and added in a few network cards. The network card is native to the linux kernel (It's a 3com 3C996 using the Broadcom 57XX chipset). It should use the tg3 driver according to other places and the manufacturer. It doesn't work. The device is listed in lspci. The module is loaded in lsmod. No mention of it in dmesg. The outputs of such commands are listed below, with the computer info being listed first. I'm a bit stuck here, I'm not used to *nix hardware problems, only windows ones.

router:~# uname -a
Linux router 2.6.26-2-sparc64 #1 Tue Jan 12 22:16:05 UTC 2010 sparc64 GNU/Linux



router:~# lspci
00:03.0 Non-VGA unclassified device: ALi Corporation M7101 Power Management Controller [PMU]
00:05.0 PCI bridge: Intel Corporation 21152 PCI-to-PCI Bridge
00:07.0 ISA bridge: ALi Corporation M1533/M1535/M1543 PCI to ISA Bridge [Aladdin IV/V/V+]
00:08.0 Multimedia audio controller: ALi Corporation M5451 PCI AC-Link Controller Audio Device (rev 01)
00:0c.0 Bridge: Sun Microsystems Computer Corp. RIO EBUS (rev 01)
00:0c.1 Ethernet controller: Sun Microsystems Computer Corp. RIO 10/100 Ethernet [eri] (rev 01)
00:0c.2 FireWire (IEEE 1394): Sun Microsystems Computer Corp. RIO 1394 (rev 01)
00:0c.3 USB Controller: Sun Microsystems Computer Corp. RIO USB (rev 01)
00:0d.0 IDE interface: ALi Corporation M5229 IDE (rev c3)
00:13.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)
01:00.0 Ethernet controller: D-Link System Inc Gigabit Ethernet Adapter (rev 11)
01:01.0 Ethernet controller: Intel Corporation 82557/8/9/0/1 Ethernet Pro 100 (rev 05)
01:02.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5701 Gigabit Ethernet (rev 15)



router:~# lsmod | grep tg3
tg3 107204 0



router:~# dmesg | grep eth
[ 54.043638] eth0: Sun GEM (PCI) 10/100/1000BaseT Ethernet 00:03:ba:a2:72:23
[ 54.043923] eth0: Found BCM5221 PHY
[ 54.522308] skge eth1: addr 00:0f:3d:f4:89:c5
[ 54.584121] e100: eth2: e100_probe: addr 0x1ff03004000, irq 17, MAC addr 00:08:c7:8c:e4:67
[ 56.441899] eth0: Link is up at 100 Mbps, full-duplex.
[ 104.676854] eth0: Link is up at 100 Mbps, full-duplex.
[ 104.687671] eth0: Pause is disabled
[ 115.813668] eth0: no IPv6 routers present
[ 222.585512] skge eth1: enabling interface
[ 222.591519] ADDRCONF(NETDEV_UP): eth1: link is not ready
[ 225.471911] ADDRCONF(NETDEV_UP): eth2: link is not ready
 
Please provide output of 'lspci -k -nn'

Sounds like this might be a PCI ID the driver isn't recognizing, so it's not attaching to the hardware.

SPARC eh? What're you running this on? Why so many random NICs? Curious... :D
 
It's a sunblade 150, TI Ultrasparc IIe 550mhz, 768MB, 80GB (It's one of two, the other is better though (1.5GB, 330GB)). I got two of these brand new a few months ago, and they have decent specs. Eventually this may become my main router (hence pc being named router, tired of smoothwall). I wanted to have one physical mangement interface (onboard), a VLAN'ed main nic for most routing as well as another NIC for quickly connecting another guest network. It's quite possible that I could ditch a NIC if this is a PCI issue. I'm upgrading the kernel now so if it doesn't work after a kernel upgrade I can try pulling a nic out.

router:~# lspci -k -nn
00:03.0 Non-VGA unclassified device [0000]: ALi Corporation M7101 Power Management Controller [PMU] [10b9:7101]
00:05.0 PCI bridge [0604]: Intel Corporation 21152 PCI-to-PCI Bridge [8086:b152]
00:07.0 ISA bridge [0601]: ALi Corporation M1533/M1535/M1543 PCI to ISA Bridge [Aladdin IV/V/V+] [10b9:1533]
00:08.0 Multimedia audio controller [0401]: ALi Corporation M5451 PCI AC-Link Controller Audio Device [10b9:5451] (rev 01)
Kernel driver in use: ALI 5451
Kernel modules: snd-ali5451
00:0c.0 Bridge [0680]: Sun Microsystems Computer Corp. RIO EBUS [108e:1100] (rev 01)
00:0c.1 Ethernet controller [0200]: Sun Microsystems Computer Corp. RIO 10/100 Ethernet [eri] [108e:1101] (rev 01)
Kernel driver in use: gem
Kernel modules: sungem
00:0c.2 FireWire (IEEE 1394) [0c00]: Sun Microsystems Computer Corp. RIO 1394 [108e:1102] (rev 01)
Kernel driver in use: ohci1394
Kernel modules: ohci1394
00:0c.3 USB Controller [0c03]: Sun Microsystems Computer Corp. RIO USB [108e:1103] (rev 01)
Kernel driver in use: ohci_hcd
Kernel modules: ohci-hcd
00:0d.0 IDE interface [0101]: ALi Corporation M5229 IDE [10b9:5229] (rev c3)
Kernel driver in use: ALI15x3_IDE
Kernel modules: alim15x3
00:13.0 VGA compatible controller [0300]: ATI Technologies Inc Rage XL [1002:4752] (rev 27)
Kernel driver in use: atyfb
01:00.0 Ethernet controller [0200]: D-Link System Inc Gigabit Ethernet Adapter [1186:4c00] (rev 11)
Kernel driver in use: skge
Kernel modules: skge
01:01.0 Ethernet controller [0200]: Intel Corporation 82557/8/9/0/1 Ethernet Pro 100 [8086:1229] (rev 05)
Kernel driver in use: e100
Kernel modules: e100
01:02.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme BCM5701 Gigabit Ethernet [14e4:1645] (rev 15)
Kernel modules: tg3
 
Hmm, it appears that the kernel module on your system has mapped that PCI ID, so it should be attaching. There should be something in dmesg about this I would think, it seems like it's failing to init the hardware for some reason. Can you post a full dmesg output?

Always did like the SPARC architecture. I remember lusting over a disused e450 at my college. Was trying to convince the dean to let the comp sci. guys fire it up and use it as a sandbox, but he wasn't biting, even though the poor thing was just sitting there in the corner turned off :(.
 
Well here's the issue:
Code: 
[   54.530481] tg3.c:v3.92.1 (June 9, 2008)
[   54.538626] PCI: Enabling device: (0000:01:02.0), cmd 2
[   54.538655] tg3: Cannot map device registers, aborting.
[   54.547004] tg3: probe of 0000:01:02.0 failed with error -12

Taking a look at the driver source code it looks like the kernel is returning an invalid address (0) for the device's PCI address space, but I've done very, very little kernel development so that's really just a guess. It's possible this is a PCI issue, or possibly a driver bug. I would try a different NIC first.

This register allocation portion of the code seems to have changed a fair bit since .26, so a newer kernel may help as well.
 
You must log in or register to reply here.
Back
Top