View previous topic :: View next topic |
Author |
Message |
kyotodude n00b
Joined: 06 Dec 2005 Posts: 14
|
Posted: Sun Jan 22, 2006 4:54 am Post subject: Borked Wireless |
|
|
Since installing Gentoo, my D-Link wireless card has been working fine. But then, after either an update or an emerge -e, it stopped connecting. I've tried messing with my /etc/conf.d/net, and here it is:
# This blank configuration will automatically use DHCP for any net.*
# scripts in /etc/init.d. To create a more complete configuration,
# please review /etc/conf.d/net.example and save your configuration
# in /etc/conf.d/net (this file :]!).
config_eth0=( "dhcp" )
dhcp_eth0="nodns nontp nonis"
config_ath0=( "dhcp" )
dhcp_ath0="nodns nontp nonis"
modules=("iwconfig")
essid_ath0="any"
config_ESSID=( "dhcp" )
mode_ath0="managed"
associate_order="any"
I really need my wireless to work, its my only network. Any suggestions please! Thanks! |
|
Back to top |
|
|
GenKreton l33t
Joined: 20 Sep 2003 Posts: 828 Location: Cambridge, MA
|
Posted: Sun Jan 22, 2006 5:08 am Post subject: |
|
|
I think the primary concern would be, can you connect manually using iwlist, iwconfig, and dhcpcd? That would tell us if the problem is with the card or with the networking scripts. |
|
Back to top |
|
|
kyotodude n00b
Joined: 06 Dec 2005 Posts: 14
|
Posted: Sun Jan 22, 2006 6:00 am Post subject: |
|
|
Iwconfig shows my wireless card, but both it and dhcpcd time out when trying to connect, with the message that the connection could not be setup. I sould also add that I'm not using any encryption. |
|
Back to top |
|
|
GenKreton l33t
Joined: 20 Sep 2003 Posts: 828 Location: Cambridge, MA
|
Posted: Sun Jan 22, 2006 6:08 am Post subject: |
|
|
When connecting with iwconfig and you tell it to associate with your wireless access point doing something like:
Code: | iwconfig eth1 essid MY_ESSID | If you wait for a reasonable amount of time (10 seconds?) and run iwconfig again, does it show the WAP's mac address? If it does not, you are not associating with the WAP. With some cards (my ipw2200 included - some versions had firmware restarting errors) there can be other problems that will be shown in dmesg. If you are associating with the WAP then you know the error is at a later stage. |
|
Back to top |
|
|
ahubu Guru
Joined: 16 Aug 2003 Posts: 400 Location: Groningen, The Netherlands
|
Posted: Sun Jan 22, 2006 12:50 pm Post subject: |
|
|
Also make sure your wireless device is still called ath0, I noticed some drivers changing it to wlan0 in a update. You should be able to see this in iwconfig. If it has changed you should change the /etc/conf.d/net parameters accordingly.
Also make sure the driver is loaded correctly (it should show up in dmesg when loading the module).
Oh, and when you have an external driver emerged, loaded as a kernel module, you should re-emerge that module with every kernel update (it couldn't hurt to re-emerge it anyway to be sure it's still installed). Or look it up with an 'lsmod' command. _________________ Anne // Light travels faster than sound. That's why people appear bright until
you hear them speak. -Unknown |
|
Back to top |
|
|
|