Subject: Re: vr0 driver weirdness?
To: None <port-i386@netbsd.org>
From: T. M. Pederson <salvage@galaxy.plethora.net>
List: port-i386
Date: 12/29/1999 20:37:49
-----BEGIN PGP SIGNED MESSAGE-----
>Verily did Peter Seebach write:
>
>> So, I've got a couple machines using these cards, and I've built a handful
>> of 'em. My friend, who has a hardware jinx, starts building a box - and
>> these cards absolutely don't work, either in 1.4.1 or in -current. In
>> -current, symptom is 'vr0 ... unable to map device registers'. Any idea
>> why this might have started happening, or what may have gone wrong near
>> him?
>
>> (This happens to any hardware he's near, sometimes.)
Only sometimes? I thought it was edging up on 'most', plus you've been
getting some spillover.
>I'm using one on a 1.4.2-ish box, and it appears to be working ok (I'm having
>problem with NAT dropping packets or something, but I'm still debugging that).
>
>Which vendor? Mine is a D-Link.
Tried two subtly different D-Links and a 3C905-TX. Both D-Links get the
same symptom, and the 3C905-TX gets 'ex0 ... unable to map I/O space'.
The motherboard is an ASUS P3B-F.
- --
T. M. Pederson <salvage@galaxy.plethora.net>
PGP key can be found at http://pgpkeys.mit.edu:11371
"I'm not talking about people here; I'm talking about me." --anon.
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3a
Charset: noconv
iQCVAwUBOGrFZIpCfoshjxMpAQFrtwP+Ly/MQ+y/S960Qau5L5wzalWtRjqZrCr/
dLaDaGOUYc3syh/svuMTbvWnVrTsbpuUiPKkdyGarEQPVMQKnqdH9ZjPn050aCoL
1WtxyBTzn30RfQLLvBjeSn1dzMDiSVndwYUxjqeuv+0gjRnWQMK13DGoIUBUb0xU
RS60Dvii8XU=
=wgG7
-----END PGP SIGNATURE-----