Messages in this thread |  | | From | Herbert Rosmanith <> | Subject | Re: 1.99.14 & duplicate NE2000 | Date | Sat, 8 Jun 1996 22:46:38 +0200 (MET DST) |
| |
> > Anno Domini 8 Jun 96 at 20:56, Herbert Rosmanith wrote: > > happens with 1.99.14: > > > > kernel = monolithic, nearly every software compiled in. however, from a > > previous compile, there are still /lib/modules/1.99.14/* left over > > > > at booting, a NE2000 (the only network-card in the system!) is reported as: > > > > > ne.c:v1.10 9/23/94 Donald Becker (becker@cesdis.gsfc.nasa.gov) > > > NE*000 ethercard probe at 0x340: 00 00 e8 c6 d1 1f > > > eth0: NE2000 found at 0x340, using IRQ 15. > > > [..snip...> > > Look's like you are trusting on 'linux plug-and-play', autoprobing > and hopefull automagical configuration of hardware. >
not really.
> It does not work, not on Win95, not on Linux, not on PC hardware.. > Stupid hardware can not read your thoughts, unfortunately.. > > If you want _exact_ results, jumper your hardware properly and > then give this particular info on each and every load and > configuration command you use. > DO NOT TRUST on any automagigal autoprobings..
autoprobe ?
the question is, that ne.o should not get 0x340-0x35f because that io-ports have already been registerd previously. register_region (or whaterver this is called now, request_region?) should fail.
my article was meant as a bug report.
|  |