Sun Dual GigE on V890

[Rob McMahon]

Sorry to follow up to myself, but I think I wasn't very clear.
> I've just installed a shiny new X7285A Sun PCI-X Dual GigE UTP Low 
> Profile card in a V890 running Solaris 10:
>
> SunOS narcissus 5.10 Generic_118833-36 sun4u sparc SUNW,Sun-Fire-V890 
> Solaris
>
> It shows up in prtdiag as
>
>                          Bus  Max
>      IO   Port Bus       Freq Bus  Dev,
> Brd  Type  ID  Side Slot MHz  Freq Func State 
> Name                              Model
> ---- ---- ---- ---- ---- ---- ---- ---- ----- 
> --------------------------------  ----------------------          
> I/O  PCI   9    B    5    33   33  3,0  ok    
> ethernet-pci8086,1079.8086.118a.+                      
> I/O  PCI   9    B    5    33   33  3,1  ok    
> ethernet-pci8086,1079.8086.118a.+                      
>
> So far so good, but no sign of life.  Checking around a bit it seems 
> this needs the e1000g driver, which wasn't installed by default, so I 
> added the SUNWintgige package from the original media.  Still no sign of 
> life.
>
> prtconf -vp shows them as
>
>             compatible: 'pci8086,1079.8086.118a.3' + 
> 'pci8086,1079.8086.118a' + 'pci8086,118a' + 'pci8086,1079.3'
> + 'pci8086,1079' + 'pciclass,020000' + 'pciclass,0200'
>             name:  'ethernet'
>             subsystem-id:  0000118a
>             subsystem-vendor-id:  00008086
>             revision-id:  00000003
>             device-id:  00001079
>             vendor-id:  00008086
>
> and having installed the e1000g driver, the line
>
> e1000g "pci8086,1079"
>
> has been added to /etc/driver_aliases.  `modload -p drv/e1000g' says
>
> can't load module: No such device or address
>   
I should have been more careful than saying "no sign of life", the 
driver didn't appear to find any devices.  I've re-run `devfsadm'.  
This, plus the add_drv from the install (which has clearly been run 
because of the entries in driver_aliases) should be enough to find the 
devices, no ?  Do I really need another reconfiguration reboot after 
adding the driver.  What does this do extra that I can't do from the 
command line ?  I'd really rather not schedule any more downtime.

 >> modload -p drv/e1000g
can't load module: No such device or address
(I've tried both this, and `modload /kernel/drv/sparcv9/e1000g', both 
the same.  A truss shows
modctl(MODLOAD, 0x00000000, 0xFFFFFFFF7FFFF4C0, 0xFFFFFFFF7FFFF4BC, 
0xFF0000000000) Err#6 ENXIO
)
 >> (gzcat messages.0.gz ; cat messages) | fgrep -i e1000g
Exit 1

No drivers attached in prtconf:
 >> prtconf -vD | egrep 'network|ether'
        network, instance #0 (driver name: ge)
        network, instance #0 (driver name: eri)
        ethernet
        ethernet

No entries in /etc/path_to_inst:
 >> fgrep e1000g /etc/path_to_inst
Exit 1

Of course
 >> ifconfig e1000g0 plumb
ifconfig: plumb: e1000g0: No such file or directory

Why isn't the driver at least trying to attach to these 'pci8086,1079' 
compatible devices.  I'd expect to at least see something logged.

Cheers,

Rob

-- 
E-Mail:	Rob.McMahon at warwick.ac.uk		PHONE:  +44 24 7652 3037
Rob McMahon, IT Services, Warwick University, Coventry, CV4 7AL, England