Paul Durrant writes:
> On 10/26/06, Johann Myrkraverk Oskarsson <[EMAIL PROTECTED]> wrote:
> > Sorry, I was rather tired when I wrote my previous mail.
> >
> > Here is the relevant line from dmesg:
> >
> > Oct 24 22:56:09 king e1000g: [ID 801593 kern.warning] WARNING:
> > pci8086,1000 - e1000g[0] : Could not identify hardware
> >
> > Can anyone tell me what I need (to know) to fix it?
> >
>
> That message came from the e1000g driver itself so I guess the driver
> is correctly bound to the device (so /etc/driver_aliases is fine).
> However, it looks like the driver is doing some sort of attach-time
> test and does not like the h/w. Since the driver is not open source
> there's not a lot more one can diagnose.
It means that the PCI_CONF_DEVID returned by the card isn't one that's
recognized by the driver.
You should be able to use dtrace to find out what value the driver
sees. Something like this ought to do it:
fbt::e1000_set_mac_type:entry
{
printf("%x", ((struct e1000_hw *)arg0)->device_id);
}
I'm not sure why it must do this (I don't maintain the driver), but it
does. Because these things are compiled into the driver, and because
the driver itself is proprietary (cannot be open-sourced), you'll need
to file a bug to have this fixed or find an alternative driver
somewhere.
--
James Carlson, KISS Network <[EMAIL PROTECTED]>
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
_______________________________________________
networking-discuss mailing list
[email protected]
