You are not logged in.
I'm typing this on a laptop connected to the network in question (which is only WEP anyway, not even WPA) on stable w/ backports, and I haven't had an issue, so I assume something involved with the upgrade has made it impossible to connect to the network.
lspci tells me it's an AR9285 PCI-E adapter, wext is the WPA supplicant driver (if that matters), and the settings are exactly the same on this computer, which has an Intel WiFi Link 5100.
Seems like I'm having a rough couple of days! But there's no hair-pull-out emoticon here! >_<
Anyway, thanks for your patience. This seems like the only thing left standing between me and my ideal system~
Last edited by Jabroneous (2012-01-25 21:03:51)
Offline
I'm not sure what the question is exactly, but...
did you try running
sudo nm-connection-editorfrom terminal?
sed 's/stress/relaxation/g'
Privacy & Security on #!
Offline
^that's for network manager. Jabroneus, maybe you're not choosing the correct WEP option, there's hex and paraphrase.
Offline
^that's for network manager. Jabroneus, maybe you're not choosing the correct WEP option, there's hex and paraphrase.
Nope, it's on hex, as intended.
Offline
^^^ isn't that command a network-manager command? because the OP mentions Wicd in the thread title?
edit: el_koraco beat me to it 
Offline
Well, let's try to connect you manually and see if it works.
sudo -i
service wicd stop
ip link set wlan0 down
ip link set wlan0 up
iwconfig essid YOURSSID
iwconfig key YOURKEY (in hex)wait five seconds
dhclient wlan0Offline
Well, let's try to connect you manually and see if it works.
sudo -i service wicd stop ip link set wlan0 down ip link set wlan0 up iwconfig essid YOURSSID iwconfig key YOURKEY (in hex)wait five seconds
dhclient wlan0
Are you sure that's the right syntax? When I try to "iwconfig essid MYSSID", I get "unknown command 'MYSSID'"
Offline
Well, you need to type in your essid (network's name). Mine is called OptiDSL_6E after my ISP.
Offline
root@crunchbang:~# iwconfig essid ######
iwconfig: unknown command "######"The #s being my essid. Am I interpreting that wrong?
Offline
You need to specify an interface:
iwconfig wlan0 essid ######Offline
No dice, I can't seem to connect manually either.
Last edited by Jabroneous (2012-01-24 21:59:46)
Offline
^ you get an error message from that last command mynis posted? and if so, post it here?
Offline
Nope, no error message. Just didn't connect as usual. 
Edit: Found some quotes from this thread:
...LightDM is OK, but requires some changes to the session scripts and doesn't seem to play well with network manager...
...LightDM works fine with wicd and I did not need to make any changes to session scripts...
Now, I'm obviously using Wicd rather than NM, but could my DM be part of the problem?
Last edited by Jabroneous (2012-01-24 22:25:14)
Offline
^ you're using LightDM? not used it, so don't know. i'm on the February Statler with GDM and everything works fine. don't use NM or Wicd, just used Ceni to configure etc/network/interfaces, as per el_koraco's WPA-supplicant-thread.
Offline
ok, first stop wicd, then edit /etc/network/interfaces and add this in:
allow-hotplug wlan0
iface wlan0 inet dhcp
wireless-mode managed
wireless-essid YOURSSID
wireless-key YOURKEYThen run
sudo ifdown wlan0 && sudo ifup wlan0Post output there.
Offline
Wow. How could I forget to state the fact that I'm using LightDM... 
I'm a big fan of ceni, but I'm not sure of how well it'd work when I'm trying to connect to a new network. I've been reading up on it in aptosid's manuals while trying to fix this (and of course, refreshing these forums), but when I'm on the go, a lot of command line stuff would probably be really cumbersome.
I suppose I could switch back to GDM, but now that I'm in unstable, it looks like there's only GDM3 available. There's also the issue of the dependencies it comes with... I'd rather try to find out if something else is causing it before going there.
Offline
eeepc@crunchbang:~$ sudo ifdown wlan0 && sudo ifup wlan0
[sudo] password for eeepc:
ifdown: interface wlan0 not configured
Internet Systems Consortium DHCP Client 4.2.2
Copyright 2004-2011 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
RTNETLINK answers: Operation not possible due to RF-kill
Listening on LPF/wlan0/00:25:d3:48:c3:bb
Sending on LPF/wlan0/00:25:d3:48:c3:bb
Sending on Socket/fallback
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6
send_packet: Network is down
receive_packet failed on wlan0: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
send_packet: Network is down
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 15
send_packet: Network is downLast edited by Jabroneous (2012-01-24 22:53:59)
Offline
Oh, well, how about
sudo rfkill listI'm off to bed, will check back tomorrow.
Last edited by el_koraco (2012-01-24 22:55:11)
Offline
rfkill: command not found

Offline
rfkill doesn't come installed by default.
sudo apt-get install rfkillAfterwards you can just unblock all interfaces with
sudo rfkill unblock allOffline
This is really strange. I thought for sure that that would work, but it still hasn't done the trick. After some more Googling, I think LightDM actually is the culprit. It definitely has something to do with rfkill switches acting strangely, so I'm going to go ahead and give GDM a shot to see if it helps.
Offline
You could just use rcconf or bum to disable your display manager completely, restart, and see what happens from a tty.
Offline
Wow. How could I forget to state the fact that I'm using LightDM...
I'm a big fan of ceni, but I'm not sure of how well it'd work when I'm trying to connect to a new network. I've been reading up on it in aptosid's manuals while trying to fix this (and of course, refreshing these forums), but when I'm on the go, a lot of command line stuff would probably be really cumbersome.
I suppose I could switch back to GDM, but now that I'm in unstable, it looks like there's only GDM3 available. There's also the issue of the dependencies it comes with... I'd rather try to find out if something else is causing it before going there.
FWIW when I was using Debian Sid these past weeks I was using GDM and it worked fine -- it was an smxi dist-upgrade from Squeeze. 
Offline
Jabroneous wrote:Wow. How could I forget to state the fact that I'm using LightDM...
I'm a big fan of ceni, but I'm not sure of how well it'd work when I'm trying to connect to a new network. I've been reading up on it in aptosid's manuals while trying to fix this (and of course, refreshing these forums), but when I'm on the go, a lot of command line stuff would probably be really cumbersome.
I suppose I could switch back to GDM, but now that I'm in unstable, it looks like there's only GDM3 available. There's also the issue of the dependencies it comes with... I'd rather try to find out if something else is causing it before going there.
FWIW when I was using Debian Sid these past weeks I was using GDM and it worked fine -- it was an smxi dist-upgrade from Squeeze.
I'm updating to sid using smxi from a fresh install of the Feb Xfce iso, this time without messing with DMs. I'll post how it goes.
Offline
i'm using siduction - a sid distro using lightDM and ceni . . . Ceni works very well on siduction, so switch to it of you like it so much
all your Base are belong to us
Offline
Copyright © 2012 CrunchBang Linux.
Proudly powered by Debian. Hosted by Linode.
Debian is a registered trademark of Software in the Public Interest, Inc.