Re: ed0/probe solved (Was: re: ed0/probe problem in 4.0-CURRENT)

1999-05-19 Thread Daniel C. Sobral
Steven Ames wrote: > > *sigh* No suprise here. As 90% of these things are this was yet > another Dumb User Error. I had a base address conflict that kept > the card from being probed. So, can we say it was due? ;-) -- Daniel C. Sobral(8-DCS) d...@newsguy.com d...@freebsd.

Re: ed0/probe problem in 4.0-CURRENT

1999-05-19 Thread Steven Ames
> Read /usr/src/UPDATING. And, more to the point, junk your kernel > configuration file, and build a new one using GENERIC/LINT as > reference. Things changed a lot between 3.x and 4.x in this > particular respect. > Always good advice. And always advice that I use. This wasn't the issue. I track

Re: ed0/probe problem in 4.0-CURRENT

1999-05-19 Thread Daniel C. Sobral
Steven Ames wrote: > > Wow. I don't think that should ever happen but at this point I'll > try a lot of things :) > > Tried it. didn't work. > > really, isn't there a way to enable more verbose probing so that > it says 'ed0 not found at 0x280' or some such? I was waiting someone ELSE answer th

ed0/probe solved (Was: re: ed0/probe problem in 4.0-CURRENT)

1999-05-18 Thread Steven Ames
*sigh* No suprise here. As 90% of these things are this was yet another Dumb User Error. I had a base address conflict that kept the card from being probed. Thanks for everyone's help. As always FreeBSD is working just great! -Steve To Unsubscrib

Re: ed0/probe problem in 4.0-CURRENT

1999-05-18 Thread Steven Ames
p0 you might want to try that. > > > Brandon Hicks - Gate Keeper Technologies > "Trixster" > bhi...@gatekeep.net > > > -Original Message- > From: Steven Ames > To: freebsd-hackers@FreeBSD.ORG > Date: Tuesday, May 18, 1999 10:10 AM > Su

ed0/probe problem in 4.0-CURRENT

1999-05-18 Thread Steven Ames
Last night switched from 3.1 to 4.0. Smooth transition. The only error I've seen is one of my ethernet cards is no longer detected. In the previous kernel (3.1-STABLE) I had the following config line: device ed0 at isa? port 0x280 net irq 10 iomem 0xd8000 When the system booted it would detect