Brian,
After looking at it more closely again, I have an onboard Intel Pro/100 VE
Ethernet device but since it is on a different chipset (915G) than you are
using it has a device ID of 1064 and subsystem-id of 1028.
I added the following to /boot/solaris/devicedb/master:
pci8086,1064 pci8086,10
> hi dan,
>
> it's a device-subsystem-id. ...
Guys, glad you're working this out: this sounds like a great enhancement.
I'd like to ask one favor regarding e-mail etiquette though ... can we
limit the e-mail traffic and cc's to request-sponsor at opensolaris to the act
of
obtaining a sponsor and
hi dan,
it's a device-subsystem-id. it looks the subsystem-*-id's are being used to
construct the name string and not the vendor-id and device-id fields. looks as
though this device and the firewire controller are both attached via a PCI-PCI
bridge. are PCI devices attached via PCI-PCI bridg
actually, i did get it to work...i'm using that box right now to reply ;-)
where exactly did you get stuck?
This message posted from opensolaris.org
I spent some time trying to get Solaris 10 to work with this same device and
even if you put the information in for the device correctly, the iprb driver
will not work with the onboard LAN. In my case, it was on a Dell 4700 with the
Intel 915G Express chipset so I assume an incredible amount of