install 3C996B-T NIC under Solaris 10 u9

Post by Andy
Hello everybody
How can we install a recognized nic card without reinstalling the OS? The
driver should be on the Solaris 10 DVD but I do not know where. Thanks in
advance
Andy

--
Bruce Porter
XJR1300SP, XJ900F, Pegaso 650 Trail (x2) one red one grey
POTM#1(KoTL), WUSS#1 , YTC#1(bar), OSOS#2(KoTL) , DS#3 , IbW#18 ,Apostle#8
"The internet is a huge and diverse community but mainly friendly"
http://blog.maui.co.uk/index.php/ytc/
There *is* an alternative! http://www.openoffice.org/

Andy

2011-10-30 18:13:52 UTC

Post by YTC#1

Post by Andy
Hello everybody
How can we install a recognized nic card without reinstalling the OS? The
driver should be on the Solaris 10 DVD but I do not know where. Thanks in
advance
Andy

Assumimng the install was SUNWCXall, then just add the card and reboot.
When it comes use run ifconfig -a plumb, it should come up as a BGE I
think.
bge.conf is part of SUNWcacr, so you should have it on the system
--
Bruce Porter
XJR1300SP, XJ900F, Pegaso 650 Trail (x2) one red one grey
POTM#1(KoTL), WUSS#1 , YTC#1(bar), OSOS#2(KoTL) , DS#3 , IbW#18 ,Apostle#8
"The internet is a huge and diverse community but mainly friendly"http://blog.maui.co.uk/index.php/ytc/
There *is* an alternative!http://www.openoffice.org/

In fact I've replaced another NIC with the bge and I still got the
following at boot time
Failed to plumb elxl0 ....
ifconfig -a plumb does not bring up the bge nic.
Also svcs -xv gives svc:/network/physical:default in maintenance
state.
elxl0 is the nic that I've used when I installed the os.

Chris Ridd

2011-10-30 18:47:33 UTC

Post by Andy
In fact I've replaced another NIC with the bge and I still got the
following at boot time
Failed to plumb elxl0 ....
ifconfig -a plumb does not bring up the bge nic.
Also svcs -xv gives svc:/network/physical:default in maintenance
state.
elxl0 is the nic that I've used when I installed the os.

You've done a reconfiguration boot? (boot with -r, or "touch
/reconfigure" & do a normal reboot)

--
Chris

Andy

2011-10-30 19:30:19 UTC

Post by Chris Ridd

You've done a reconfiguration boot? (boot with -r, or "touch
/reconfigure" & do a normal reboot)
--
Chris

I did it and it does not change anything. I think there should be a
problem with smf. Should I enter in single user mode and do something?

Bruce Esquibel

2011-10-30 20:32:05 UTC

Post by Andy
I did it and it does not change anything. I think there should be a
problem with smf. Should I enter in single user mode and do something?

Are you positive the card is supported?

There were some 3Com's that were only supported under Sparc, not X86.

Probably much older ones than the one you are using but double check.

Like someone else pointed out, "it should just work".

One other thing, and this is vague because I don't remember all the details
but there was an older machine (like v20z or v40z) which didn't work with
the elxl0 when added because of the bge0/bge1 onboards.

Disabling the bge's caused the elxl0 to come up fine by itself. There was a
round-about fix, like not plumbing them in the global zone at boot but
assigning them to a couple zones.

Doesn't make sense typing that out, really don't remember.

Just suggesting if there are other ethernet interfaces, try disabiling them
and see if the 3C996 comes up.

-bruce
***@ripco.com

Andy

2011-10-30 21:34:15 UTC

Post by Andy
I did it and it does not change anything. I think there should be a
problem with smf. Should I enter in single user mode and do something?

Are you positive the card is supported?
There were some 3Com's that were only supported under Sparc, not X86.
Probably much older ones than the one you are using but double check.
Like someone else pointed out, "it should just work".
One other thing, and this is vague because I don't remember all the details
but there was an older machine (like v20z or v40z) which didn't work with
the elxl0 when added because of the bge0/bge1 onboards.
Disabling the bge's caused the elxl0 to come up fine by itself. There was a
round-about fix, like not plumbing them in the global zone at boot but
assigning them to a couple zones.
Doesn't make sense typing that out, really don't remember.
Just suggesting if there are other ethernet interfaces, try disabiling them
and see if the comes up.
-bruce

On the box of the 3C996 nic is written that is supported by Solaris
x86
but that should means Solaris 8 x86 because it is an old card.
I did also sys-unconfig and changed hostname.elxl0 to hostname.bge0
and I still have svcs -xv giving svc:/network/physical:default in
maintenance state.
What is strange is when I replaced the elxl0 card back again I still
have svcs -xv giving svc:/network/physical:default in maintenance
state!
and ifconfig -a does not see the 3com card also.

YTC#1

2011-10-31 11:09:34 UTC

Post by Andy
I did it and it does not change anything. I think there should be a
problem with smf. Should I enter in single user mode and do something?

Are you positive the card is supported?
There were some 3Com's that were only supported under Sparc, not X86.
Probably much older ones than the one you are using but double check.
Like someone else pointed out, "it should just work".
One other thing, and this is vague because I don't remember all the
details but there was an older machine (like v20z or v40z) which didn't
work with the elxl0 when added because of the bge0/bge1 onboards.
Disabling the bge's caused the elxl0 to come up fine by itself. There
was a round-about fix, like not plumbing them in the global zone at boot
but assigning them to a couple zones.
Doesn't make sense typing that out, really don't remember.
Just suggesting if there are other ethernet interfaces, try disabiling
them and see if the comes up.
-bruce

On the box of the 3C996 nic is written that is supported by Solaris x86
but that should means Solaris 8 x86 because it is an old card. I did also

If it used to work on 8, I would expect it to work on S10.

The card you listed is on the HCL, have a look at the prtvtoc example that
goes with that. You may need to tweak driver_aliases

sys-unconfig and

changed hostname.elxl0 to hostname.bge0 and I still

have svcs -xv giving svc:/network/physical:default in maintenance state.
What is strange is when I replaced the elxl0 card back again I still
have svcs -xv giving svc:/network/physical:default in maintenance state!

And the log file shows ?

And the messages file shows ???

and ifconfig -a does not see the 3com card also.

Andy

2011-11-02 04:47:23 UTC

Post by YTC#1

Post by Andy
I did it and it does not change anything. I think there should be a
problem with smf. Should I enter in single user mode and do something?

Are you positive the card is supported?
There were some 3Com's that were only supported under Sparc, not X86.
Probably much older ones than the one you are using but double check.
Like someone else pointed out, "it should just work".
One other thing, and this is vague because I don't remember all the
details but there was an older machine (like v20z or v40z) which didn't
work with the elxl0 when added because of the bge0/bge1 onboards.
Disabling the bge's caused the elxl0 to come up fine by itself. There
was a round-about fix, like not plumbing them in the global zone at boot
but assigning them to a couple zones.
Doesn't make sense typing that out, really don't remember.
Just suggesting if there are other ethernet interfaces, try disabiling
them and see if the comes up.
-bruce

On the box of the 3C996 nic is written that is supported by Solaris x86
but that should means Solaris 8 x86 because it is an old card. I did also

If it used to work on 8, I would expect it to work on S10.
The card you listed is on the HCL, have a look at the prtvtoc example that
goes with that. You may need to tweak driver_aliases

sys-unconfig and

changed hostname.elxl0 to hostname.bge0 and I still

And the log file shows ?
And the messages file shows ???

and ifconfig -a does not see the 3com card also.

--
Bruce Porter
XJR1300SP, XJ900F, Pegaso 650 Trail (x2) one red one grey
POTM#1(KoTL), WUSS#1 , YTC#1(bar), OSOS#2(KoTL) , DS#3 , IbW#18 ,Apostle#8
"The internet is a huge and diverse community but mainly friendly"http://blog.maui.co.uk/index.php/ytc/
There *is* an alternative!http://www.openoffice.org/

Thanks for your messages but I had to give up because I can no more
log into the system.
In fact I have an old ASUS motherboard with an Adaptec 320 controller
and a SCSI HD with no jumper so with scsi id 0
I've tried to replace the 1 g nic with the elxl0 to see if i can go
back, but after the adaptec ctrl see my hd as lun 6!!! so that I can
no more boot!!!!

Andy

2011-11-06 14:31:54 UTC

I've found the driver bge and the file bge.conf under /platform/i86pc/
kernel/drv.
Is there a way to attach it to the 3com nic?

Ian Collins

2011-11-06 18:45:30 UTC

Post by Andy
I've found the driver bge and the file bge.conf under /platform/i86pc/
kernel/drv.
Is there a way to attach it to the 3com nic?

Why would you expect the Broadcom driver work with a 3Com NIC?

Buy an Intel (or Realtek) NIC and save your self the pain.

--
Ian Collins

cjt

2011-11-07 02:05:28 UTC

Post by Ian Collins

Post by Andy
I've found the driver bge and the file bge.conf under /platform/i86pc/
kernel/drv.
Is there a way to attach it to the 3com nic?

Why would you expect the Broadcom driver work with a 3Com NIC?
Buy an Intel (or Realtek) NIC and save your self the pain.

He's already been playing with it for a week. Apparently time has no
value to him.

YTC#1

2011-11-07 18:33:29 UTC

Post by Ian Collins

Post by Andy
I've found the driver bge and the file bge.conf under /platform/i86pc/
kernel/drv.
Is there a way to attach it to the 3com nic?

Why would you expect the Broadcom driver work with a 3Com NIC?

Because it is a Broadcom chipset, and is listed as "reported to work" on
the HCL

Post by Ian Collins
Buy an Intel (or Realtek) NIC and save your self the pain.

True.

But I admire the fact he is trying to use something, that *should* work.

John D Groenveld

2011-11-07 22:51:58 UTC

Post by YTC#1
Because it is a Broadcom chipset, and is listed as "reported to work" on
the HCL

The HCL entry:
<URL:http://www.oracle.com/webfolder/technetwork/hcl/data/components/details/3com/sol_10_01_06/1406.html>
The output of prtconf(1M):
<URL:http://www.oracle.com/webfolder/technetwork/hcl/data/components/prtconf/3com/sol_10_01_06/1406.txt>
The PCI vendor database entry for the 3com NIC device id:
<URL:http://www.pcidatabase.com/search.php?device_search_str=1006&device_search.x=0&device_search.y=0>

# update_drv -a -i "pci10b7,1006" bge
# touch /reconfigure
# sys-unconfig

But the OP should post his output of prtconf(1M) if he hasn't
sent the hardware to salvage and surplus.

John
***@acm.org

Andy

2011-11-08 13:19:08 UTC

Post by YTC#1
Because it is a Broadcom chipset, and is listed as "reported to work" on
the HCL

<URL:http://www.oracle.com/webfolder/technetwork/hcl/data/components/detai...>
<URL:http://www.oracle.com/webfolder/technetwork/hcl/data/components/prtco...>
<URL:http://www.pcidatabase.com/search.php?device_search_str=1006&device_s...>
# update_drv -a -i "pci10b7,1006" bge
# touch /reconfigure
# sys-unconfig
But the OP should post his output of prtconf(1M) if he hasn't
sent the hardware to salvage and surplus.
John

Thanks John ,
I have the following response from the system:
bash-3.00# update_drv -a -i "pci10b7,1006" bge
devfsadm: driver failed to attach: bge
Warning: Driver (bge) successfully added to system but failed to
attach
I must mention a few things:
It is an old machine which has 2 pci 64 buses. One is for the 3com
card (which is also pci64) and on the other one I have an adaptec
ultra 320 controller.
Also I succeeded with a Realtek card:
bash-3.00# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu
8232 index 1
inet 127.0.0.1 netmask ff000000
rtls0: flags=1004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu
1500 index 2
inet 192.168.1.37 netmask ffffff00 broadcast 192.168.1.255
ether 0:40:95:9:6a:db
bash-3.00# psrinfo -pv
The physical processor has 1 virtual processor (0)
x86 (AuthenticAMD family 6 model 6 step 2 clock 1267 MHz)
AMD Athlon(tm) MP 2000+
The physical processor has 1 virtual processor (1)
x86 (AuthenticAMD family 6 model 6 step 2 clock 1267 MHz)
AMD Athlon(tm) MP 2000+

John D Groenveld

2011-11-08 15:00:58 UTC

Post by John D Groenveld
But the OP should post his output of prtconf(1M) if he hasn't
sent the hardware to salvage and surplus.

bash-3.00# update_drv -a -i "pci10b7,1006" bge
devfsadm: driver failed to attach: bge
Warning: Driver (bge) successfully added to system but failed to
attach

prtconf(1M)?
Or have you given up on the NIC and/or the PCI slot?

John
***@acm.org

Andy

2011-11-09 07:41:55 UTC

Post by John D Groenveld

Post by John D Groenveld
But the OP should post his output of prtconf(1M) if he hasn't
sent the hardware to salvage and surplus.

bash-3.00# update_drv -a -i "pci10b7,1006" bge
devfsadm: driver failed to attach: bge
Warning: Driver (bge) successfully added to system but failed to
attach

prtconf(1M)?
Or have you given up on the NIC and/or the PCI slot?
John

bash-3.00$ prtconf -pv
System Configuration: Sun Microsystems i86pc
Memory size: 1024 Megabytes
System Peripherals (PROM Nodes):

Node 0x000001
bios-boot-device: '80'
stdout: 00000000
name: 'i86pc'

Node 0x000002
existing: 01035000.00000000.0794d801.00000000
name: 'ramdisk'

Node 0x000003
bus-type: 'isa'
device_type: 'isa'
name: 'isa'

Node 0x000004
device_type: 'pci'
reg: 00000000.00000000.00000000
#size-cells: 00000002
#address-cells: 00000003
name: 'pci'

Node 0x000005
assigned-addresses:
c2000010.00000000.f0000000.00000000.08000000.c2000014.00000000.ef800000.00000000.00001000.81000018.00000000.0000e800.00000000.00000004
reg:
00000000.00000000.00000000.00000000.00000000.42000010.00000000.00000000.00000000.08000000.42000014.00000000.00000000.00000000.00001000.01000018.00000000.00000000.00000000.00000004
compatible: 'pci1022,700c.11' + 'pci1022,700c' + 'pciclass,
060000' + 'pciclass,0600'
model: 'Host bridge'
power-consumption: 00000001.00000001
66mhz-capable:
devsel-speed: 00000001
max-latency: 00000000
min-grant: 00000000
unit-address: '0'
class-code: 00060000
revision-id: 00000011
vendor-id: 00001022
device-id: 0000700c
name: 'pci1022,700c'

Node 0x000006
reg: 00000800.00000000.00000000.00000000.00000000
compatible: 'pci1022,700d.0' + 'pci1022,700d' + 'pciclass,
060400' + 'pciclass,0604'
model: 'PCI-PCI bridge'
ranges:
81000000.00000000.0000d000.81000000.00000000.0000d000.00000000.00001000.82000000.00000000.ce800000.82000000.00000000.ce800000.00000000.01600000.c2000000.00000000.d0000000.c2000000.00000000.d0000000.00000000.1f800000
bus-range: 00000001.00000001
#size-cells: 00000002
#address-cells: 00000003
device_type: 'pci'
power-consumption: 00000001.00000001
66mhz-capable:
devsel-speed: 00000001
unit-address: '1'
class-code: 00060400
revision-id: 00000000
vendor-id: 00001022
device-id: 0000700d
name: 'pci1022,700d'

Node 0x00000f
display-edif-id: 'SAM011F'
video-adapter-type: 'svga'
display-type: 'color'
display-edif-block: ffffff00.00ffffff.011f2d4c.
4d4a3139.03010f2a.781e266c.a2866f2a.24944d5a.bf544f1a.808180ef.
01014f71.01010101.01010101.2a300101.00519800.7030402a.
2d780013.1e000011.fd000000.1e4b3800.0a000e51.20202020.00002020.5300fc00.4d636e79.65747361.20200a72.ff000000.46564800.37304159.0a303037.20002020
assigned-addresses:
c2012810.00000000.e0000000.00000000.08000000.81012814.00000000.0000d800.00000000.00000100.82012818.00000000.cf000000.00000000.00010000.a1012800.00000000.000003b0.00000000.0000000c.a1012800.00000000.000003c0.00000000.00000020.a2012800.00000000.000a0000.00000000.00020000
reg:
00012800.00000000.00000000.00000000.00000000.42012810.00000000.00000000.00000000.08000000.01012814.00000000.00000000.00000000.00000100.02012818.00000000.00000000.00000000.00010000.a1012800.00000000.000003b0.00000000.0000000c.a1012800.00000000.000003c0.00000000.00000020.a2012800.00000000.000a0000.00000000.00020000
compatible: 'pci1002,5964.1043.c008.1' +
'pci1002,5964.1043.c008' + 'pci1043,c008' + 'pci1002,5964.1' +
'pci1002,5964' + 'pciclass,030000' + 'pciclass,0300'
model: 'VGA compatible controller'
power-consumption: 00000001.00000001
66mhz-capable:
fast-back-to-back:
devsel-speed: 00000001
interrupts: 00000001
max-latency: 00000000
min-grant: 00000008
subsystem-vendor-id: 00001043
subsystem-id: 0000c008
device_type: 'display'
unit-address: '5'
class-code: 00030000
revision-id: 00000001
vendor-id: 00001002
device-id: 00005964
name: 'display'

Node 0x000010
assigned-addresses:
c2012910.00000000.d0000000.00000000.08000000.82012914.00000000.ce800000.00000000.00010000
reg:
00012900.00000000.00000000.00000000.00000000.42012910.00000000.00000000.00000000.08000000.02012914.00000000.00000000.00000000.00010000
compatible: 'pci1002,5d44.1043.c009.1' +
'pci1002,5d44.1043.c009' + 'pci1043,c009' + 'pci1002,5d44.1' +
'pci1002,5d44' + 'pciclass,038000' + 'pciclass,0380'
model: 'Video controller'
power-consumption: 00000001.00000001
66mhz-capable:
fast-back-to-back:
devsel-speed: 00000001
max-latency: 00000000
min-grant: 00000008
subsystem-vendor-id: 00001043
subsystem-id: 0000c009
unit-address: '5,1'
class-code: 00038000
revision-id: 00000001
vendor-id: 00001002
device-id: 00005d44
name: 'pci1043,c009'

Node 0x000007
reg: 00003800.00000000.00000000.00000000.00000000
compatible: 'pci1022,7440.1043.8044.4' +
'pci1022,7440.1043.8044' + 'pci1043,8044' + 'pci1022,7440.4' +
'pci1022,7440' + 'pciclass,060100' + 'pciclass,0601'
model: 'ISA bridge'
power-consumption: 00000001.00000001
66mhz-capable:
devsel-speed: 00000001
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001043
subsystem-id: 00008044
unit-address: '7'
class-code: 00060100
revision-id: 00000004
vendor-id: 00001022
device-id: 00007440
name: 'pci1043,8044'

Node 0x000008
#size-cells: 00000000
#address-cells: 00000001
device_type: 'pci-ide'
assigned-addresses:
81003900.00000000.000001f0.00000000.00000008.81003900.00000000.000003f6.00000000.00000001.81003900.00000000.00000170.00000000.00000008.81003900.00000000.00000376.00000000.00000001.81003920.00000000.0000b800.00000000.00000010
reg:
00003900.00000000.00000000.00000000.00000000.81003900.00000000.000001f0.00000000.00000008.81003900.00000000.000003f6.00000000.00000001.81003900.00000000.00000170.00000000.00000008.81003900.00000000.00000376.00000000.00000001.01003920.00000000.00000000.00000000.00000010
compatible: 'pci1022,7441.1022.7441.4' +
'pci1022,7441.1022.7441' + 'pci1022,7441' + 'pci1022,7441.4' +
'pci1022,7441' + 'pciclass,01018a' + 'pciclass,0101'
model: 'IDE controller'
power-consumption: 00000001.00000001
devsel-speed: 00000001
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001022
subsystem-id: 00007441
unit-address: '7,1'
class-code: 0001018a
revision-id: 00000004
vendor-id: 00001022
device-id: 00007441
name: 'pci-ide'

Node 0x000009
reg: 00000000
name: 'ide'

Node 0x00000a
reg: 00000001
name: 'ide'

Node 0x00000b
reg: 00003b00.00000000.00000000.00000000.00000000
compatible: 'pci1022,7443.1043.8044.3' +
'pci1022,7443.1043.8044' + 'pci1043,8044' + 'pci1022,7443.3' +
'pci1022,7443' + 'pciclass,068000' + 'pciclass,0680'
model: 'Bridge device'
power-consumption: 00000001.00000001
fast-back-to-back:
devsel-speed: 00000001
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001043
subsystem-id: 00008044
unit-address: '7,3'
class-code: 00068000
revision-id: 00000003
vendor-id: 00001022
device-id: 00007443
name: 'pci1043,8044'

Node 0x00000c
assigned-addresses:
81004810.00000000.0000b400.00000000.00000100.83004814.00000000.ce000000.00000000.00002000.8100481c.
00000000.0000b000.00000000.00000100
reg:
00004800.00000000.00000000.00000000.00000000.01004810.00000000.00000000.00000000.00000100.03004814.00000000.00000000.00000000.00002000.0100481c.
00000000.00000000.00000000.00000100
compatible: 'pci9005,8012.9005.42.3' +
'pci9005,8012.9005.42' + 'pci9005,42' + 'pci9005,8012.3' +
'pci9005,8012' + 'pciclass,010000' + 'pciclass,0100'
model: 'SCSI bus controller'
power-consumption: 00000001.00000001
66mhz-capable:
devsel-speed: 00000001
interrupts: 00000001
max-latency: 00000019
min-grant: 00000028
subsystem-vendor-id: 00009005
subsystem-id: 00000042
unit-address: '9'
class-code: 00010000
revision-id: 00000003
vendor-id: 00009005
device-id: 00008012
pci-msi-capid-pointer: 000000a0
name: 'pci9005,42'

Node 0x00000d
assigned-addresses:
81004910.00000000.0000a800.00000000.00000100.83004914.00000000.cd800000.00000000.00002000.8100491c.
00000000.0000a400.00000000.00000100
reg:
00004900.00000000.00000000.00000000.00000000.01004910.00000000.00000000.00000000.00000100.03004914.00000000.00000000.00000000.00002000.0100491c.
00000000.00000000.00000000.00000100
compatible: 'pci9005,8012.9005.42.3' +
'pci9005,8012.9005.42' + 'pci9005,42' + 'pci9005,8012.3' +
'pci9005,8012' + 'pciclass,010000' + 'pciclass,0100'
model: 'SCSI bus controller'
power-consumption: 00000001.00000001
66mhz-capable:
devsel-speed: 00000001
interrupts: 00000002
max-latency: 00000019
min-grant: 00000028
subsystem-vendor-id: 00009005
subsystem-id: 00000042
unit-address: '9,1'
class-code: 00010000
revision-id: 00000003
vendor-id: 00009005
device-id: 00008012
pci-msi-capid-pointer: 000000a0
name: 'pci9005,42'

Node 0x00000e
slot-names: 00000160.746f6c53.6c530034.0033746f.
746f6c53.00000035
reg: 00008000.00000000.00000000.00000000.00000000
compatible: 'pci1022,7448.4' + 'pci1022,7448' + 'pciclass,
060400' + 'pciclass,0604'
model: 'PCI-PCI bridge'
ranges:
81000000.00000000.00009000.81000000.00000000.00009000.00000000.00001000.82000000.00000000.cb000000.82000000.00000000.cb000000.00000000.02800000.c2000000.00000000.cfe00000.c2000000.00000000.cfe00000.00000000.00100000
bus-range: 00000002.00000002
#size-cells: 00000002
#address-cells: 00000003
device_type: 'pci'
power-consumption: 00000001.00000001
66mhz-capable:
devsel-speed: 00000001
unit-address: '10'
class-code: 00060400
revision-id: 00000004
vendor-id: 00001022
device-id: 00007448
name: 'pci1022,7448'

Node 0x000011
assigned-addresses:
81022810.00000000.00009800.00000000.00000020
reg:
00022800.00000000.00000000.00000000.00000000.01022810.00000000.00000000.00000000.00000020
compatible: 'pci1102,2.1102.100a.a' +
'pci1102,2.1102.100a' + 'pci1102,100a' + 'pci1102,2.a' + 'pci1102,2' +
'pciclass,040100' + 'pciclass,0401'
model: 'Audio device'
power-consumption: 00000001.00000001
fast-back-to-back:
devsel-speed: 00000001
interrupts: 00000001
max-latency: 00000014
min-grant: 00000002
subsystem-vendor-id: 00001102
subsystem-id: 0000100a
unit-address: '5'
class-code: 00040100
revision-id: 0000000a
vendor-id: 00001102
device-id: 00000002
name: 'pci1102,100a'

Node 0x000012
assigned-addresses:
81022910.00000000.00009400.00000000.00000008
reg:
00022900.00000000.00000000.00000000.00000000.01022910.00000000.00000000.00000000.00000008
compatible: 'pci1102,7002.1102.20.a' +
'pci1102,7002.1102.20' + 'pci1102,20' + 'pci1102,7002.a' +
'pci1102,7002' + 'pciclass,098000' + 'pciclass,0980'
model: 'Input controller'
power-consumption: 00000001.00000001
fast-back-to-back:
devsel-speed: 00000001
max-latency: 00000000
min-grant: 00000000
subsystem-vendor-id: 00001102
subsystem-id: 00000020
unit-address: '5,1'
class-code: 00098000
revision-id: 0000000a
vendor-id: 00001102
device-id: 00007002
name: 'pci1102,20'

Node 0x000013
assigned-addresses:
81023010.00000000.00009000.00000000.00000100.82023014.00000000.cc800000.00000000.00000100
reg:
00023000.00000000.00000000.00000000.00000000.01023010.00000000.00000000.00000000.00000100.02023014.00000000.00000000.00000000.00000100
compatible: 'pci10ec,8139.10ec.8139.10' + 'pci10ec,
8139.10ec.8139' + 'pci10ec,8139' + 'pci10ec,8139.10' + 'pci10ec,8139'
+ 'pciclass,020000' + 'pciclass,0200'
model: 'Ethernet controller'
power-consumption: 00000001.00000001
fast-back-to-back:
devsel-speed: 00000001
interrupts: 00000001
max-latency: 00000040
min-grant: 00000020
subsystem-vendor-id: 000010ec
subsystem-id: 00008139
unit-address: '6'
class-code: 00020000
revision-id: 00000010
vendor-id: 000010ec
device-id: 00008139
name: 'pci10ec,8139'

Node 0x000014
assigned-addresses:
82024010.00000000.cc000000.00000000.00001000
reg:
00024000.00000000.00000000.00000000.00000000.02024010.00000000.00000000.00000000.00001000
compatible: 'pci1033,35.807d.35.41' + 'pci1033,35.807d.
35' + 'pci807d,35' + 'pci1033,35.41' + 'pci1033,35' + 'pciclass,
0c0310' + 'pciclass,0c03'
model: 'Universal Serial Bus OHCI compliant'
power-consumption: 00000001.00000001
devsel-speed: 00000001
interrupts: 00000001
max-latency: 0000002a
min-grant: 00000001
subsystem-vendor-id: 0000807d
subsystem-id: 00000035
unit-address: '8'
class-code: 000c0310
revision-id: 00000041
vendor-id: 00001033
device-id: 00000035
name: 'pci807d,35'

Node 0x000015
assigned-addresses:
82024110.00000000.cb800000.00000000.00001000
reg:
00024100.00000000.00000000.00000000.00000000.02024110.00000000.00000000.00000000.00001000
compatible: 'pci1033,35.807d.35.41' + 'pci1033,35.807d.
35' + 'pci807d,35' + 'pci1033,35.41' + 'pci1033,35' + 'pciclass,
0c0310' + 'pciclass,0c03'
model: 'Universal Serial Bus OHCI compliant'
power-consumption: 00000001.00000001
devsel-speed: 00000001
interrupts: 00000002
max-latency: 0000002a
min-grant: 00000001
subsystem-vendor-id: 0000807d
subsystem-id: 00000035
unit-address: '8,1'
class-code: 000c0310
revision-id: 00000041
vendor-id: 00001033
device-id: 00000035
name: 'pci807d,35'

Node 0x000016
assigned-addresses:
82024210.00000000.cb000000.00000000.00000100
reg:
00024200.00000000.00000000.00000000.00000000.02024210.00000000.00000000.00000000.00000100
compatible: 'pci1033,e0.807d.1043.2' +
'pci1033,e0.807d.1043' + 'pci807d,1043' + 'pci1033,e0.2' +
'pci1033,e0' + 'pciclass,0c0320' + 'pciclass,0c03'
model: 'Universal Serial Bus EHCI compliant'
power-consumption: 00000001.00000001
devsel-speed: 00000001
interrupts: 00000003
max-latency: 00000022
min-grant: 00000010
subsystem-vendor-id: 0000807d
subsystem-id: 00001043
unit-address: '8,2'
class-code: 000c0320
revision-id: 00000002
vendor-id: 00001033
device-id: 000000e0
name: 'pci807d,1043'

John D Groenveld

2011-11-09 15:54:09 UTC

Post by Andy
bash-3.00$ prtconf -pv

I don't see the 3com NIC.
John
***@acm.org

Andy

2011-11-09 22:43:29 UTC

Post by John D Groenveld

Post by Andy
bash-3.00$ prtconf -pv

I don't see the 3com NIC.
John

Hi John,
I have the NIC working with the bge driver from Broadcom:
http://www.broadcom.com/support/ethernet_nic/netxtreme_server.php
# update_drv -a -i "pci10b7,1006" bge
("pci10b7,1006") already in use as a driver or alias.
# prtconf -pv | grep ,1006
compatible: 'pci14e4,1645.10b7.1006.15' +
'pci14e4,1645.10b7.1006' + 'pci10b7,1006' + 'pci14e4,1645.15' +
'pci14e4,1645' + 'pciclass,020000' + 'pciclass,0200'
name: 'pci10b7,1006'
# devfsadm
# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu
8232 index 1
inet 127.0.0.1 netmask ff000000
rtls0: flags=1004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu
1500 index 2
inet 192.168.1.37 netmask ffffff00 broadcast 192.168.1.255
ether 0:40:95:9:6a:db
# ifconfig -a plumb
ifconfig: SIOCSLIFNAME for ip: rtls0: already exists
# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu
8232 index 1
inet 127.0.0.1 netmask ff000000
rtls0: flags=1004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu
1500 index 2
inet 192.168.1.37 netmask ffffff00 broadcast 192.168.1.255
ether 0:40:95:9:6a:db
bge0: flags=1000842<BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
inet 0.0.0.0 netmask 0
ether 0:a:5e:1:65:d2

YTC#1

2011-11-10 10:43:23 UTC

In article

Post by Andy
bash-3.00$ prtconf -pv

I don't see the 3com NIC.
John

Hi John,

See, I said it would work :-)

Andy

2011-10-31 00:29:59 UTC

Post by Andy
I did it and it does not change anything. I think there should be a
problem with smf. Should I enter in single user mode and do something?

Are you positive the card is supported?
There were some 3Com's that were only supported under Sparc, not X86.
Probably much older ones than the one you are using but double check.
Like someone else pointed out, "it should just work".
One other thing, and this is vague because I don't remember all the details
but there was an older machine (like v20z or v40z) which didn't work with
the elxl0 when added because of the bge0/bge1 onboards.
Disabling the bge's caused the elxl0 to come up fine by itself. There was a
round-about fix, like not plumbing them in the global zone at boot but
assigning them to a couple zones.
Doesn't make sense typing that out, really don't remember.
Just suggesting if there are other ethernet interfaces, try disabiling them
and see if the 3C996 comes up.
-bruce

I think u are right. The nic does not have a driver on the Solaris 10
u9 dvd
I've checked with prtconf -pv after a new intallation.

cjt

2011-10-30 21:15:23 UTC

Post by Chris Ridd

You've done a reconfiguration boot? (boot with -r, or "touch
/reconfigure"& do a normal reboot)
--
Chris

I did it and it does not change anything. I think there should be a
problem with smf. Should I enter in single user mode and do something?

This may sound a bit flippant, but I'm serious. For the amount of time
one can easily spend trying to get something like this working, it's far
cheaper (assuming you value your time) and less frustrating to just buy
and install an Intel NIC.

Ian Collins

2011-10-30 20:27:55 UTC