Okay, I'm back at work, and have cable internet here, so that I actually did
some debugging and checking up on the problem just now. I think I narrowed
the interrupt storm down to the end of scanning with the card. First of all a
vmstat -i in three seconds interval while I was simply inserting t
Am Mittwoch, 14. November 2007 08:55:49 schrieb Heiko Wundram (Beenic):
>
Just for an update: I was stupid, really stupid enough not to check with any
of the APs I tried to connect to whether they had MAC-filtering enabled, and
all of them did. I turned that off just now for my private AP, and
Am Mittwoch, 14. November 2007 20:48:00 schrieb Sam Leffler:
> I don't think I can help w/ the interrupt storm but you didn't provide
> any logs for wpa_supplicant or wlandebug so it's hard to help w/ that
> issue.
Sorry for not providing any logs, but I just got the card yesterday, and
haven't h
Am Mittwoch, 14. November 2007 16:51:16 schrieb Heiko Wundram (Beenic):
>
FSCK, sorry, I meant to repost to [EMAIL PROTECTED]
Sorry for the noise...
--
Heiko Wundram
Product & Application Development
___
freebsd-stable@freebsd.org mailing list
http:/
Hi all!
I just recently bought a RT2561C based (at least I think so) wireless card,
which is also happily recognized by the ral-driver:
ral0: mem 0x8800-0x88007fff irq 17 at device
0.0 on cardbus0
ral0: MAC/BBP RT2561C, RF RT2527
ral0: Ethernet address: 00:80:5a:51:23:53
ral0: [ITHREAD]
A
Hi all!
I just recently bought a RT2561C based (at least I think so) wireless card,
which is also happily recognized by the ral-driver:
ral0: mem 0x8800-0x88007fff irq 17 at device
0.0 on cardbus0
ral0: MAC/BBP RT2561C, RF RT2527
ral0: Ethernet address: 00:80:5a:51:23:53
ral0: [ITHREAD]
A
