| Summary: | 3Com 3C509 EtherLink III Problem. | ||
|---|---|---|---|
| Product: | Base System | Reporter: | Andrey.Chepurko <Andrey.Chepurko> |
| Component: | i386 | Assignee: | freebsd-bugs (Nobody) <bugs> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | Unspecified | ||
| Hardware: | Any | ||
| OS: | Any | ||
|
Description
Andrey.Chepurko
2001-04-04 14:00:00 UTC
On Wed, 4 Apr 2001 Andrey.Chepurko@fth2.siemens.de wrote: > >Description: > Well, I have a 3Com EtherLinkIII isa pnp-card, when I load my machine > with kernel.GENERIC, it recognizes the card: > > Qoute from dmesg:"ep0 <3com.......> irq9 isa0 > ep0: eprom failed to come ready > ep0: Ethernet address 00:00:00:00:00:00 > ep1:<3Com...> at port... irq9 on isa0 > ep1: Ethernetaddress: 00:60:....:bb > ep1: promiscious mode enabled > ep1: promiscious mode disabled > ep1: promiscious mode enabled > ep1: promiscious mode disabled > " This isn't the real dmesg output. Boot verbose and capture the relevent information (anything that contains 'ep' and the PnP settings) and let me see that. > Andrey > >How-To-Repeat: > take a <3com etherlink III 3C509 combo isa-pnp> network card and > try to boot on 4.2-Realease with kernel.GENERIC. > >Fix: > I dunno, if you know, PLEASE let me know asap as well, or i'll install > solaris 7 on my box and will never be using freebsd again if there's > no support. Use the 3c5x9cfg.exe program (under DOS, available from the 3com FTP site) to refresh the cards config. I've seen what appears to be corrupted EEPROM contents cause the driver problems. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | State Changed From-To: open->closed Feedback timeout I had this same problem, and the 3c5x9cfg.exe program, along with just re-setting up my NIC solved it. Other notes from my problem 1. Problem happened at boot, system hung during boot, and rebooted 2. Had BSD 4.4 working with same NIC, and no problem at all.. (??) 3. Finally managed to upgrade my 4.4 to 5.2.1. yay. Nic Boie Shensey@shensey.com |