From: Grant <emailgrant@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Can't connect to new router
Date: Wed, 22 Sep 2010 09:35:52 -0700 [thread overview]
Message-ID: <AANLkTikxYC43PBfchtz-gA3dJpZdzaAKbh5dATVEh3Ea@mail.gmail.com> (raw)
In-Reply-To: <201009221251.52397.michaelkintzios@gmail.com>
>> >> >> I just got a new TP-Link TL-WR1043ND wireless router but I can't seem
>> >> >> connect to it. I've tried the Gentoo initscript as well as wicd.
>> >> >> With the initscript, I get:
>> >> >>
>> >> >> wlan3: carrier lost
>> >> >> wlan3: timed out
>> >> >>
>> >> >> I see a lot of this in dmesg:
>> >> >>
>> >> >> b43-phy0 ERROR: MAC suspend failed
>> >> >>
>> >> >> I can connect to other wireless routers just fine, and I can connect
>> >> >> to this one via ethernet. I've tried configuring it in various ways,
>> >> >> security is disabled, and I've tried specifying static IPs with no
>> >> >> luck. Does anyone know what I could be doing wrong?
>> >> >
>> >> > Check that you're using the latest kernel and the latest firmware. I
>> >> > used to get this error with a particular cisco access point and it
>> >> > went away when I updated to 2.6.34 kernel series and also updated the
>> >> > firmware. Have a good look in here to find the latest suitable
>> >> > firmware for your NIC:
>> >> >
>> >> > http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware
>> >>
>> >> I upgraded to the latest firmware in portage and the "MAC suspend
>> >> failed" errors have disappeared, but I still can't connect to the
>> >> router. Here is the only clue I see in dmesg:
>> >>
>> >> No probe response from AP a1:b2:c3:d4:e5:f6 after 500ms, disconnecting.
>> >>
>> >> Any ideas?
>> >
>> > Try a later kernel which would have a more up to date driver. Last time
>> > I had this problem it was corrected by unmasking and using a newer
>> > kernel. It's something to do with the TTL that the driver uses and I'm
>> > not sure that this is a parameter that you can see listed under modinfo.
>> > I believe it is hard coded.
>>
>> I'm on the latest hardened-sources kernel so I'll wait it out. In the
>> meantime I've plugged in a USB wireless NIC and it's working fine.
>> Thank you for your help.
>
> I'm on 2.6.34-gentoo-r6 and the b43 driver works fine here, but only a few
> kernels back it was exhibiting the same symptoms like yours.
>
> Some users have mentioned that if you use WPA/WPA2 encryption the symptoms are
> surprisingly less frequent!
>
> So until a more up to date kernel shows up you may want to look into
> experimenting with wpa_supplicant.
I'm actually using the same kernel version, for me it's
2.6.34-hardened-r6. I've tried softmode with the same results. I'm
using wicd and WPA2, and I tried wpa_supplicant when I first started
having the problem with the same results.
Thanks for your help. I'm sure it will be fixed up soon. Probably
already fixed in newer kernel versions.
- Grant
prev parent reply other threads:[~2010-09-22 16:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-28 2:31 [gentoo-user] Can't connect to new router Grant
2010-08-28 9:19 ` Mick
2010-09-09 3:44 ` Grant
2010-09-09 19:10 ` Mick
2010-09-22 1:26 ` Grant
2010-09-22 11:51 ` Mick
2010-09-22 16:35 ` Grant [this message]
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=AANLkTikxYC43PBfchtz-gA3dJpZdzaAKbh5dATVEh3Ea@mail.gmail.com \
--to=emailgrant@gmail.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