From: Larry Finger <Larry.Finger@lwfinger.net>
To: alupu@verizon.net
Cc: linux-wireless@vger.kernel.org
Subject: Re: r8712u staging in kernel 3.2.9
Date: Sun, 11 Mar 2012 19:19:25 -0500 [thread overview]
Message-ID: <4F5D410D.2030005@lwfinger.net> (raw)
In-Reply-To: <17646354.573873.1331505374568.JavaMail.root@vms170029>
On 03/11/2012 05:36 PM, alupu@verizon.net wrote:
> Hi Larry,
>
> A few _quick_ notes ("impressions") so you can get me more/detailed
> instructions while I'm getting the hang of openSUSE :)
>
>> Could you please download a Live KDE CD from
>> software.opensuse.org/121/en
>> It should not matter whether you use the 32- or 64-bit version.
>> After you boot it, use the NetworkManager system tray
>> applet to connect to your system.
>> Does that work?
>
> Yes. How? Very smoothly.
>
>> Next, use 'ps ax' to get the PID for NetworkManager and kill it.
>> Then try your iwconfig/ifconfig command sequence.
>> Does that work?
>
> No. Same old story.
> Actually, I tried the "iwconfig/ifconfig" (from the KDE terminal) first.
> It didn't work so then, quite discouraged, I went to the NM above.
> As I said, worked AOK, I then killed the guy, so I can try
> the "iwconfig/ifconfig" again. No cigar, as I explained above.
>
> Note: in retrospect, I'm wondering if in Knoppix what would've
> happened if I had tried his graphics mode (some sort of KDE clone).
> An even bigger wonder. I'll be looking into that:
> When doing 'ps ...' I noticed there was a wpa_supplicant(?) running.
> If that was a requirement for NM, it should've helped when I went "down"
> in command (KDE terminal) mode as well. ???
> I don't remember if the supplicant process was killed (as a side effect).
I know that the openSUSE Live CD works on my computer with the Rosewill device
and WEP encryption. That tells me that the driver is working correctly, and that
the user-space stuff is OK. Let's see if we can find what is wrong for you.
After the Live CD boots, do you see the NM applet in the lower-right hand corner
of the screen?
When you click on it, do you see a list of APs that are in range?
If you click on yours, do you get a screen that wants to know the WEP key? You
will need to enter the hexadecimal key, not any passphrase. You will also get a
popup asking if you want to use kwallet. Say yes and give it a blank password.
Did you get a connection? Note, NM uses wpa_supplicant even for WEP. That is normal.
Larry
next prev parent reply other threads:[~2012-03-12 0:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-11 22:36 r8712u staging in kernel 3.2.9 alupu
2012-03-12 0:19 ` Larry Finger [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-03-13 4:13 alupu
2012-03-12 23:02 alupu
2012-03-13 0:54 ` Larry Finger
2012-03-12 1:46 alupu
2012-03-12 2:54 ` Larry Finger
2012-03-11 19:57 alupu
2012-03-11 19:57 alupu
2012-03-10 18:10 alupu
2012-03-11 4:23 ` Larry Finger
2012-03-10 4:53 alupu
2012-03-09 19:06 alupu
2012-03-10 2:17 ` Larry Finger
2012-03-07 5:31 alupu
2012-03-07 16:15 ` Larry Finger
[not found] <31991817.2926129.1331079358141.JavaMail.root@vznit170116>
2012-03-07 3:22 ` Larry Finger
2012-03-07 1:44 alupu
2012-03-06 2:22 alupu
2012-03-06 20:21 ` Larry Finger
2012-03-05 17:07 alupu
2012-03-05 19:10 ` Larry Finger
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=4F5D410D.2030005@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=alupu@verizon.net \
--cc=linux-wireless@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).