> From the source code, the driver is trying to read the media type
> setting from the eeprom and failing to get anything it understands.
> This looks like only the second bit of info that is looked at from the
> eeprom, and the first bit wouldn't give an error if it too was returning
> 0x0. This is just my quick reading of the code, though! I would
> definitely be starting to think that adding the memory triggered a
> hardware problem, perhaps static, or something physical.
I am very afraid of that :-( The motherboard was not cheap (although
refurbished) and replacing it is a pain even if it were free.
> Presumably you don't have another OS installed on the machine (<dread
> look> Windows or Linux) because if it too couldn't see the ethernet that
> would be a strong indicator of hardware problems.
I'm going to try installing something else. I need to check a slow-writing
harddrive too. Thanks,
-mi
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hardware
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
