Arnaldo Carvalho de Melo wrote:
On 12/22/05, Michael Buesch <[EMAIL PROTECTED]> wrote:
On Thursday 22 December 2005 18:49, Martin Tessun wrote:
Johannes Berg wrote:
On Thu, 2005-12-22 at 17:51 +0100, Martin Tessun wrote:
At least you get them inserted ;) When I try to modprobe rate_control I
On 12/22/05, Michael Buesch <[EMAIL PROTECTED]> wrote:
> On Thursday 22 December 2005 18:49, Martin Tessun wrote:
> > Johannes Berg wrote:
> > > On Thu, 2005-12-22 at 17:51 +0100, Martin Tessun wrote:
> > >
> > >> At least you get them inserted ;) When I try to modprobe rate_control I
> > >> get th
On Thursday 22 December 2005 18:49, Martin Tessun wrote:
> Johannes Berg wrote:
> > On Thu, 2005-12-22 at 17:51 +0100, Martin Tessun wrote:
> >
> >> At least you get them inserted ;) When I try to modprobe rate_control I
> >> get the following:
> >
> > insmod 80211 first.
> >
> > johannes
>
>
Johannes Berg wrote:
On Thu, 2005-12-22 at 17:51 +0100, Martin Tessun wrote:
At least you get them inserted ;) When I try to modprobe rate_control I
get the following:
insmod 80211 first.
johannes
No, this ist not the problem.
When inserting 80211 I get the same message;
kernel: 80211: ie
On Thu, 2005-12-22 at 17:51 +0100, Martin Tessun wrote:
> At least you get them inserted ;) When I try to modprobe rate_control I
> get the following:
insmod 80211 first.
johannes
signature.asc
Description: This is a digitally signed message part
[EMAIL PROTECTED] wrote:
The combination of the latest devicescape stack ( 051221 )
and latest dscape branch makes my Powerbook hard lock after
rmmod the kernel modules and stopping wpa_supplicant.
Basicly i do the following before it hard locks :
rmmod bcm43xx
killall wpa_supplicant 2>/dev/n
