E420R and -CURRENT

Jason Fortezzo fortezza at mechanicalism.net
Sun Jul 13 16:00:57 PDT 2003


I running -CURRENT on a E420R, everything works great except for gem(4) 
support.  I get the following error: 

gem0: phy probe failed: 6
gem0: could not be configured
device_probe_and_attach: gem0 attach returned 6

I have some SysKonnect and Intel gigabit cards on hand, should I try
them instead?


stray vector interrupt 2029
Copyright (c) 1992-2003 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
         The Regents of the University of California. All rights reserved.
FreeBSD 5.1-CURRENT #0: Sat Jun  7 16:02:01 CDT 2003
     root at randon:/usr/obj/usr/src/sys/RANDON
Preloaded elf kernel "/boot/kernel/kernel" at 0xc04b2000.
Timecounter "tick"  frequency 450032765 Hz
real memory  = 4294967296 (4096 MB)
avail memory = 4161511424 (3968 MB)
cpu0: Sun Microsystems UltraSparc-II Processor (450.03 MHz CPU)
cpu1: Sun Microsystems UltraSparc-II Processor (450.03 MHz CPU)
cpu2: Sun Microsystems UltraSparc-II Processor (450.03 MHz CPU)
cpu3: Sun Microsystems UltraSparc-II Processor (450.03 MHz CPU)
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
nexus0: <OpenFirmware Nexus device>
pcib0: <U2P UPA-PCI bridge> on nexus0
pcib0: Psycho, impl 0, version 4, ign 0x7c0, bus B
initialializing counter-timer
Timecounter "counter-timer"  frequency 1000000 Hz
DVMA map: 0xfc000000 to 0xffffffff
pci0: <PCI bus> on pcib0
pci0: <bridge, HOST-PCI> at device 0.0 (no driver attached)
ebus0: revision 0x01
ebus0: <PCI-EBus2 bridge> mem 
0x71000000-0x717fffff,0x70000000-0x70ffffff at device 1.0 on pci0
ebus0: <auxio> addr 
0x140072f000-0x140072f003,0x140072c000-0x140072c003,0x140072a000-0x140072a003,0x1400728000-0x1400728003,0x1400726000-0x1400726003

(no driver attached)
ebus0: <power> addr 0x1400724000-0x1400724003 irq 37 (no driver attached)
ebus0: <SUNW,pll> addr 0x1400504000-0x1400504002 (no driver attached)
ebus0: <sc> addr 0x1400500000-0x1400500007 (no driver attached)
sab0: <Siemens SAB 82532 v3.2> addr 0x1400400000-0x140040007f irq 43 on 
ebus0
sabtty0: <ttya> on sab0
sabtty0: console 9600,8,n,1,-
sabtty1: <ttyb> on sab0
ebus0: <su> addr 0x14003083f8-0x14003083ff irq 41 (no driver attached)
ebus0: <su> addr 0x14003062f8-0x14003062ff irq 42 (no driver attached)
ebus0: <ecpp> addr 
0x1400700000-0x140070000f,0x1400300398-0x1400300399,0x14003043bc-0x14003043cb

irq 34 (no driver attached)
ebus0: <fdthree> addr 
0x1400720000-0x1400720003,0x1400706000-0x140070600f,0x14003023f0-0x14003023f7

irq 39 (no driver attached)
eeprom0: <EBus EEPROM/clock> addr 0x1400000000-0x1400001fff on ebus0
eeprom0: model mk48t59
eeprom0: hostid 80e91621
ebus0: <flashprom> addr 0x1000000000-0x10000fffff (no driver attached)
hme0: <Sun HME 10/100 Ethernet> mem 0x10100000-0x10107fff irq 33 at 
device 1.1 on pci0
hme0: Ethernet address: 08:00:20:e9:16:21
miibus0: <MII bus> on hme0
ukphy0: <Generic IEEE 802.3u media interface> on miibus0
ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
gem0: <Sun GEM Gigabit Ethernet Adaptor> mem 0x10200000-0x103fffff irq 
16 at device 2.0 on pci0
gem0: phy probe failed: 6
gem0: could not be configured
device_probe_and_attach: gem0 attach returned 6
sym0: <875> port 0x1000-0x10ff mem 
0x1010a000-0x1010afff,0x10108000-0x101080ff irq 32 at device 3.0 on pci0
sym0: No NVRAM, ID 7, Fast-20, SE, parity checking
sym1: <875> port 0x1400-0x14ff mem 
0x1010e000-0x1010efff,0x1010c000-0x1010c0ff irq 38 at device 3.1 on pci0
sym1: No NVRAM, ID 7, Fast-20, SE, parity checking
pcib1: <PCI-PCI bridge> at device 4.0 on pci0
pci1: <PCI bus> on pcib1
pci1: <bridge, PCI-unknown> at device 0.0 (no driver attached)
hme1: <Sun HME 10/100 Ethernet> mem 0x4000000-0x4007fff irq 25 at device 
0.1 on pci1
hme1: Ethernet address: 08:00:20:e9:16:21
miibus1: <MII bus> on hme1
ukphy1: <Generic IEEE 802.3u media interface> on miibus1
ukphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
pci1: <bridge, PCI-unknown> at device 1.0 (no driver attached)
hme2: <Sun HME 10/100 Ethernet> mem 0x8000000-0x8007fff irq 26 at device 
1.1 on pci1
hme2: Ethernet address: 08:00:20:e9:16:21
miibus2: <MII bus> on hme2
ukphy2: <Generic IEEE 802.3u media interface> on miibus2
ukphy2:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
pci1: <bridge, PCI-unknown> at device 2.0 (no driver attached)
hme3: <Sun HME 10/100 Ethernet> mem 0xc000000-0xc007fff irq 27 at device 
2.1 on pci1
hme3: Ethernet address: 08:00:20:e9:16:21
miibus3: <MII bus> on hme3
ukphy3: <Generic IEEE 802.3u media interface> on miibus3
ukphy3:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
pci1: <bridge, PCI-unknown> at device 3.0 (no driver attached)
hme4: <Sun HME 10/100 Ethernet> mem 0x10000000-0x10007fff irq 24 at 
device 3.1 on pci1
hme4: Ethernet address: 08:00:20:e9:16:21
miibus4: <MII bus> on hme4
ukphy4: <Generic IEEE 802.3u media interface> on miibus4
ukphy4:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
pci0: <serial bus, Fibre Channel> at device 5.0 (no driver attached)
pcib2: <U2P UPA-PCI bridge> on nexus0
pcib2: Psycho, impl 0, version 4, ign 0x7c0, bus A
pci2: <PCI bus> on pcib2
pci2: <bridge, HOST-PCI> at device 0.0 (no driver attached)
pcib3: <PCI-PCI bridge> at device 1.0 on pci2
pci3: <PCI bus> on pcib3
pci3: <bridge, PCI-unknown> at device 0.0 (no driver attached)
hme5: <Sun HME 10/100 Ethernet> mem 0x4000000-0x4007fff irq 1 at device 
0.1 on pci3
hme5: Ethernet address: 08:00:20:e9:16:21
miibus5: <MII bus> on hme5
ukphy5: <Generic IEEE 802.3u media interface> on miibus5
ukphy5:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
pci3: <bridge, PCI-unknown> at device 1.0 (no driver attached)
hme6: <Sun HME 10/100 Ethernet> mem 0x8000000-0x8007fff irq 2 at device 
1.1 on pci3
hme6: Ethernet address: 08:00:20:e9:16:21
miibus6: <MII bus> on hme6
ukphy6: <Generic IEEE 802.3u media interface> on miibus6
ukphy6:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
pci3: <bridge, PCI-unknown> at device 2.0 (no driver attached)
hme7: <Sun HME 10/100 Ethernet> mem 0xc000000-0xc007fff irq 3 at device 
2.1 on pci3
hme7: Ethernet address: 08:00:20:e9:16:21
miibus7: <MII bus> on hme7
ukphy7: <Generic IEEE 802.3u media interface> on miibus7
ukphy7:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
pci3: <bridge, PCI-unknown> at device 3.0 (no driver attached)
hme8: <Sun HME 10/100 Ethernet> mem 0x10000000-0x10007fff irq 0 at 
device 3.1 on pci3
hme8: Ethernet address: 08:00:20:e9:16:21
miibus8: <MII bus> on hme8
ukphy8: <Generic IEEE 802.3u media interface> on miibus8
ukphy8:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
Timecounters tick every 10.000 msec
Waiting 15 seconds for SCSI devices to settle
cd0 at sym0 bus 0 target 6 lun 0
cd0: <TOSHIBA DVD-ROM SD-M1401 1007> Removable CD-ROM SCSI-2 device
cd0: 20.000MB/s transfers (20.000MHz, offset 16)
cd0: cd present [690420 x 512 byte records]
da0 at sym0 bus 0 target 0 lun 0
da0: <FUJITSU MAJ3182M SUN18G 0804> Fixed Direct Access SCSI-2 device
da0: 40.000MB/s transfers (20.000MHz, offset 16, 16bit), Tagged Queueing 
Enabled
da0: 17274MB (35378533 512 byte sectors: 255H 63S/T 2202C)
da1 at sym0 bus 0 target 1 lun 0
da1: <IBM DDYST1835SUN18G S96H> Fixed Direct Access SCSI-3 device
da1: 40.000MB/s transfers (20.000MHz, offset 16, 16bit), Tagged Queueing 
Enabled
da1: 17274MB (35378533 512 byte sectors: 255H 63S/T 2202C)
SMP: AP CPU #3 Launched!
SMP: AP CPU #2 Launched!
SMP: AP CPU #1 Launched!
Mounting root from ufs:/dev/da1a
Invalid time in real time clock.
Check and reset the date immediately!


-- 
Jason Fortezzo
fortezza at mechanicalism.net


More information about the freebsd-sparc64 mailing list