>> I noticed there was some changes in the ath code. But it has little to
>> no effect on the periodic drops of the radio signal. This time,
>> suddently, the input is garbaged; at least, the card say so:
> I get all sorts of bad trouble with ath:
> I get SSIDs with spaces truncated. I get drops in the driver. I get
> failures to associate. If I try to change the power save state, I get
> error messages when I try to use ifconfig to change the power save
> settings of the device. Those are just bugs that I remember off the
> top of my head -- I think there are others.
> Six months ago none of this was a problem, but right now I'm unaware
> of users of the ath device on NetBSD who are having a good time with
> it. I'm very annoyed. Drivers should not get this much worse with
> time. :(

After upgrading to NetBSD-current a few days ago, wi/fi scanning
with the ath0 interface no longer works and crashes the interface
requiring me to bring the interface down then up before I can use
it again.  It is disappointing when before then the ath driver
was previously much more reliable.

================================================================
# wiconfig ath0 -D
scanning .............wiconfig: ioctl: Operation now in progress
================================================================

> Honestly I sometimes now think it was a major mistake for me to get a
> laptop with a built in ath -- it is extremely unpleasant to work with
> the driver in its current state.

My laptop also boot WinXP and SuSE Linux, and the ath card works
great only those OS, so this is a NetBSD specific driver issue.

Alicia.