On Sat, 2008-07-12 at 21:26 -0700, Sam Leffler wrote:
Alexandre Sunny Kovalenko wrote:
On Sat, 2008-07-12 at 09:57 -0700, Sam Leffler wrote:
Alexandre Sunny Kovalenko wrote:
On Fri, 2008-07-11 at 20:29 -0700, Sam Leffler wrote:
Alexandre Sunny Kovalenko wrote:
Hi Sam,
do you know if there is anything done about cbb(4)? I have many
wireless adapters with ath(4), but only the one based on PCMCIA is
making problems on FreeBSD.
I cannot boot my notebook with the device inserted into the port, or it
will render the system unusable (100% load on cbb(4)).
On Sun, 2008-07-13 at 11:21 +0200, Martin wrote:
Hi Sam,
do you know if there is anything done about cbb(4)? I have many
wireless adapters with ath(4), but only the one based on PCMCIA is
making problems on FreeBSD.
I cannot boot my notebook with the device inserted into the port, or it
Am Sonntag, 13. Juli 2008 14:37:14 schrieb Alexandre Sunny Kovalenko:
snip
Just to chime into the discussion, I'm seeing something similar for if_ral
since my latest update of 7-STABLE from about two weeks ago (which I did not
see with a 7-STABLE from some time in march, so something must have
Hi Alexandre,
You can panic the box by unloading if_ath.ko while wpa_supplicant is
running on any form factor, so this one is not specific to the removable
devices.
I am not talking about unloading kernel modules (I wouldn't unload
if_ath by force and complain about it). The panic is
Martin wrote:
Hi Sam,
do you know if there is anything done about cbb(4)? I have many
wireless adapters with ath(4), but only the one based on PCMCIA is
making problems on FreeBSD.
I cannot boot my notebook with the device inserted into the port, or it
will render the system unusable (100%
Alexandre Sunny Kovalenko wrote:
On Sun, 2008-07-13 at 11:21 +0200, Martin wrote:
Hi Sam,
do you know if there is anything done about cbb(4)? I have many
wireless adapters with ath(4), but only the one based on PCMCIA is
making problems on FreeBSD.
I cannot boot my notebook with the device
On Fri, 2008-07-11 at 20:29 -0700, Sam Leffler wrote:
Alexandre Sunny Kovalenko wrote:
On Fri, 2008-05-16 at 12:23 -0400, Sam Leffler wrote:
Alexandre Sunny Kovalenko wrote:
On Mon, 2008-05-12 at 19:33 -0700, Sam Leffler wrote:
Alexandre Sunny Kovalenko wrote:
I seem to be able to lock
Alexandre Sunny Kovalenko wrote:
On Fri, 2008-07-11 at 20:29 -0700, Sam Leffler wrote:
Alexandre Sunny Kovalenko wrote:
On Fri, 2008-05-16 at 12:23 -0400, Sam Leffler wrote:
Alexandre Sunny Kovalenko wrote:
On Mon, 2008-05-12 at 19:33 -0700, Sam Leffler wrote:
On Sat, 2008-07-12 at 09:57 -0700, Sam Leffler wrote:
Alexandre Sunny Kovalenko wrote:
On Fri, 2008-07-11 at 20:29 -0700, Sam Leffler wrote:
Alexandre Sunny Kovalenko wrote:
On Fri, 2008-05-16 at 12:23 -0400, Sam Leffler wrote:
Alexandre Sunny Kovalenko wrote:
Alexandre Sunny Kovalenko wrote:
On Sat, 2008-07-12 at 09:57 -0700, Sam Leffler wrote:
Alexandre Sunny Kovalenko wrote:
On Fri, 2008-07-11 at 20:29 -0700, Sam Leffler wrote:
Alexandre Sunny Kovalenko wrote:
On Fri, 2008-05-16 at 12:23 -0400, Sam Leffler wrote:
On Fri, 2008-05-16 at 12:23 -0400, Sam Leffler wrote:
Alexandre Sunny Kovalenko wrote:
On Mon, 2008-05-12 at 19:33 -0700, Sam Leffler wrote:
Alexandre Sunny Kovalenko wrote:
I seem to be able to lock my machine by going into wpa_cli and asking it
to 'reassoc'. The reason for question
Alexandre Sunny Kovalenko wrote:
On Fri, 2008-05-16 at 12:23 -0400, Sam Leffler wrote:
Alexandre Sunny Kovalenko wrote:
On Mon, 2008-05-12 at 19:33 -0700, Sam Leffler wrote:
Alexandre Sunny Kovalenko wrote:
I seem to be able to lock my machine by going into wpa_cli and asking it
to
Alexandre Sunny Kovalenko wrote:
On Mon, 2008-05-12 at 19:33 -0700, Sam Leffler wrote:
Alexandre Sunny Kovalenko wrote:
I seem to be able to lock my machine by going into wpa_cli and asking it
to 'reassoc'. The reason for question mark after hard is that debug
information (caused by wlandebug
On Mon, 2008-05-12 at 19:33 -0700, Sam Leffler wrote:
Alexandre Sunny Kovalenko wrote:
I seem to be able to lock my machine by going into wpa_cli and asking it
to 'reassoc'. The reason for question mark after hard is that debug
information (caused by wlandebug and athdebug) is being
I seem to be able to lock my machine by going into wpa_cli and asking it
to 'reassoc'. The reason for question mark after hard is that debug
information (caused by wlandebug and athdebug) is being printed on the
console. The only way to get machine's attention is to hold power button
for 8
Alexandre Sunny Kovalenko wrote:
I seem to be able to lock my machine by going into wpa_cli and asking it
to 'reassoc'. The reason for question mark after hard is that debug
information (caused by wlandebug and athdebug) is being printed on the
console. The only way to get machine's attention is
17 matches
Mail list logo
