From: luoyi <luoyi.ly@gmail.com>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Pavel Machek <pavel@ucw.cz>, linux-kernel@vger.kernel.org
Subject: Re: w35und driver unusable
Date: Wed, 18 Mar 2009 22:22:23 +0800 [thread overview]
Message-ID: <e9e614960903180722h49f3719fp3a947fd194066233@mail.gmail.com> (raw)
In-Reply-To: <84144f020903170940nf76d905t43bfa497bd5fe6d5@mail.gmail.com>
just rmmod and modprobe it will trigger the oops.
I've just upload a oops snapshot picture onto flickr:
http://www.flickr.com/photos/21260339@N03/3364812089/
hope it will help for you.
2009/3/18 Pekka Enberg <penberg@cs.helsinki.fi>:
> Hi!
>
> (off-list)
>
> On Tue, Mar 17, 2009 at 5:43 AM, luoyi <luoyi.ly@gmail.com> wrote:
>> Wow, thanks for your advice. and I can get it work now after I set my
>> wireless AP's channel to 1 and mode to "b/g auto".
>>
>> 3 problems:
>>
>> 1. it can only work with 802.11b mode
>>
>> 2. rmmod w35und
>> modprobe w35und
>> Kernel Panic
>>
>> 3. after it get IP address with dhcpcd, if I execute iwlist scan, then
>> it will lose the connection and never restore again, the only way make
>> it work again is to restart my computer.
>
> Just to let you know, I am traveling right now and dont have my laptop
> with me. I wont be able to look at the issues until next week but
> please do post the oops as requested in the other email so other
> people can take a look at it meanwhile.
>
next prev parent reply other threads:[~2009-03-18 14:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-17 4:41 luoyi
2009-03-17 6:07 ` Pekka Enberg
2009-03-17 9:03 ` Pavel Machek
2009-03-17 12:43 ` luoyi
2009-03-17 16:38 ` Pekka Enberg
[not found] ` <84144f020903170940nf76d905t43bfa497bd5fe6d5@mail.gmail.com>
2009-03-18 14:22 ` luoyi [this message]
2009-03-23 8:20 ` Pekka Enberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e9e614960903180722h49f3719fp3a947fd194066233@mail.gmail.com \
--to=luoyi.ly@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=penberg@cs.helsinki.fi \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®