public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Elmar Hinz <oss.elmar@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Still Struggling With Wireless
Date: Tue, 17 Aug 2010 13:11:40 +0200	[thread overview]
Message-ID: <AANLkTimoet3yxFQf_QvYMsK-T5M3124MqjRV8xawXuse@mail.gmail.com> (raw)
In-Reply-To: <4C69E9A3.6020801@gmail.com>

@ CJoeB

It can be really hard. I needed days. There is more than one difficulty.

For example I needed to set my laptop type in the kernel (asus_laptop).
Without that, the card is not turned on at all, even if the card driver itself
is loaded.

Then you need to compile the password for wpa_supplicant with wpa_password.
It doesn´t take the plain passphrase.

So don´t be afraid to ask. wlan still is really hard stuff.

Regards

Al


2010/8/17 CJoeB <colleen.beamer@gmail.com>:
>  Hi,
>
> I'm biting the bullet here and asking for help.  Yes! I've posted
> before.  And before anyone asks, I have read the responses to my
> previous posts which helped little.  I have read the documentation and
> the wikis - ad nauseum.  I'm still having problems with wireless.
>
> Things were so much easier when I could just use the ipw3945 driver.
> However, I can't build that because it requires TKIP and CCMP, neither
> of which I can find settings for in my active kernel, 2.6.34-gentoo-r1.
> In one of the responses to my previous posts someone told me about the /
> trick while in the kernel configuration to bring up a search menu.  I
> did this and the only reference I could find for TKIP was one related to
> debugging.
>
> So, I'm left with trying to use the iwl3945 driver in the kernel.  I
> followed the wiki for setting this up and thought I had succeeded.  I
> got to the point where I was told to type the following:
> ifconfig wlan0 up (this does activate the wireless led on my computer)
> iwlist wlan0 scan
> iwconfig wlan0 essid "network name"  (where the network name is the
> essid that has been set)
>
> When I got this to work, I thought I was home free despite the "kludgy"
> way of getting wireless working.  However, I rebooted and now, when I
> type iwlist wlan0 scan I get told that scanning is not supported.  Yes,
> I have iwl3945-ucode installed and yes, it was recompiled after the
> kernel was rebuilt.
>
> I have no idea what I'm doing wrong.  Help would be appreciated.
>
> Regards,
>
> Colleen
>
> --
>
> Registered Linux User #411143 with the Linux Counter, http://counter.li.org
>
>
>
>



  parent reply	other threads:[~2010-08-17 11:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-17  1:45 [gentoo-user] Still Struggling With Wireless CJoeB
2010-08-17  1:55 ` Adam Carter
2010-08-17 10:55   ` Jake Moe
2010-08-17 23:04     ` CJoeB
2010-08-18  1:12       ` Jake Moe
2010-08-18  2:56         ` CJoeB
2010-08-18 18:50           ` Elmar Hinz
2010-08-18 21:47           ` Jake Moe
2010-08-20 15:44           ` Mick
2010-08-17  8:36 ` David Abbott
2010-08-17 11:05   ` Elmar Hinz
2010-08-17 22:49   ` CJoeB
2010-08-20  8:24     ` Neil Bothwick
2010-08-20 12:11       ` Elmar Hinz
2010-08-17 11:11 ` Elmar Hinz [this message]
2010-08-17 11:55   ` Adam Carter
2010-08-17 16:09     ` Elmar Hinz
2010-08-17 11:19 ` Elmar Hinz

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=AANLkTimoet3yxFQf_QvYMsK-T5M3124MqjRV8xawXuse@mail.gmail.com \
    --to=oss.elmar@googlemail.com \
    --cc=gentoo-user@lists.gentoo.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