Re: 3c509b getting `eeprom failed to come ready' in current

On Fri, 26 Nov 1999, Thierry Herbelot wrote: > If it is not possible to hardwire the ep boards, how do I recognize them > in a "router" setting ? > > (I have an oldish PC with to ep boards, used as a WAN simulator, with > dummynet : how do I tell ep0 form ep1 ?) > Look for the "ether" (mac-

Re: 3c509b getting `eeprom failed to come ready' in current

On Fri, 26 Nov 1999, Thierry Herbelot wrote: > If it is not possible to hardwire the ep boards, how do I recognize them > in a "router" setting ? > > (I have an oldish PC with to ep boards, used as a WAN simulator, with > dummynet : how do I tell ep0 form ep1 ?) The ISA enumerator detects cards

Re: 3c509b getting `eeprom failed to come ready' in current

< said: > What is really needed here is for the resource manager to handle > 'requests' as well as allocations. It does. That's the difference between `allocate' and `activate'. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same [EMAIL PROTECTED] |

Re: 3c509b getting `eeprom failed to come ready' in current

If it is not possible to hardwire the ep boards, how do I recognize them in a "router" setting ? (I have an oldish PC with to ep boards, used as a WAN simulator, with dummynet : how do I tell ep0 form ep1 ?) TfH To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-

Re: 3c509b getting `eeprom failed to come ready' in current

On Fri, 26 Nov 1999, Poul-Henning Kamp wrote: > >I'm going to look closer at those two drivers and find the place where > >they disagree with if_ep. > > They don't disagree, they do some stuff to some registers to detect > their respective hardware, which unfortunately hoses a ep0 card if > one h

Re: 3c509b getting `eeprom failed to come ready' in current

In message <[EMAIL PROTECTED]>, "Matthew N. Dodd" writes: >On Fri, 26 Nov 1999, Poul-Henning Kamp wrote: >> Can we somehow mark the if_ep as "fickle hardware" so it gets probed >> before the if_ex/it_ie ? We used to have such a facility. > >I'm going to look closer at those two drivers and fin

Re: 3c509b getting `eeprom failed to come ready' in current

On Fri, 26 Nov 1999, Poul-Henning Kamp wrote: > In message <[EMAIL PROTECTED]>, "Matthew > N. Dodd" writes: > > >Yes, and when I converted if_ep to newbus I mentioned that hardwire was no > >longer supported. > > Couldn't we simply ignore such hardwiring (with a warning) if present ? I'm not s

Re: 3c509b getting `eeprom failed to come ready' in current

In message <[EMAIL PROTECTED]>, "Matthew N. Dodd" writes: >Yes, and when I converted if_ep to newbus I mentioned that hardwire was no >longer supported. Couldn't we simply ignore such hardwiring (with a warning) if present ? >I'm a little annoyed that if_ep has issues working with if_ex/if_ie

Re: 3c509b getting `eeprom failed to come ready' in current

On 26 Nov 1999, Assar Westerlund wrote: > there's (to my mind) a difference between it's not done by default and > it will not work. I did it because I had hardwired it in my previous > config. Yes, and when I converted if_ep to newbus I mentioned that hardwire was no longer supported. I'm a l

Re: 3c509b getting `eeprom failed to come ready' in current

"David O'Brien" <[EMAIL PROTECTED]> writes: > > +# don't try to hardware ep0 - it will not work > > If we don't hardware it in GENERIC, then why do people think they should > be doing so? (s/hardware/hardwire/ of course) there's (to my mind) a difference between it's not done by default and it

Re: 3c509b getting `eeprom failed to come ready' in current

> Not hardwiring ep0 in the configuration file made it work. Thanks > again. ... > +# don't try to hardware ep0 - it will not work If we don't hardware it in GENERIC, then why do people think they should be doing so? -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROT

Re: 3c509b getting `eeprom failed to come ready' in current

Poul-Henning Kamp <[EMAIL PROTECTED]> writes: > no. Try to disable ep1 (if you can). Not hardwiring ep0 in the configuration file made it work. Thanks again. Here's an trivial patch to GENERIC to add comments about these characteristics about ep0. /assar Index: GENERIC ==

Re: 3c509b getting `eeprom failed to come ready' in current

In message <[EMAIL PROTECTED]>, Assar Westerlund writes: >Poul-Henning Kamp <[EMAIL PROTECTED]> writes: >> Don't use the generic kernel unchanged with the 3com card. >> >> Disable the ex0 and ie0 drivers, one of those pummel the 3com >> cards magic config registers. > >Tack. Now it manages to fi

Re: 3c509b getting `eeprom failed to come ready' in current

Poul-Henning Kamp <[EMAIL PROTECTED]> writes: > Don't use the generic kernel unchanged with the 3com card. > > Disable the ex0 and ie0 drivers, one of those pummel the 3com > cards magic config registers. Tack. Now it manages to find ep0 properly. It still finds a `ghost' ep1 and hangs hard wh

Re: 3c509b getting `eeprom failed to come ready' in current

Don't use the generic kernel unchanged with the 3com card. Disable the ex0 and ie0 drivers, one of those pummel the 3com cards magic config registers. >ep0: <3Com EtherLink III (3c509-Combo)> at port 0x300-0x30f irq 9 on isa0 >ep0: eeprom failed to come ready >... >Ethernet address ff:ff:ff:ff:

3c509b getting `eeprom failed to come ready' in current

Hi. When upgrading a box from current ~ 1999-11-15 to ~ today, the 3c509b network interface fails to work. These are the kernels (the first one working, the second one not). /kernel.old: FreeBSD 4.0-CURRENT #1: Mon Nov 15 00:03:00 CET 1999 /kernel: FreeBSD 4.0-CURRENT #0: Fri No