First, let me note that this has NOTHING to do with my other issue (the high speed cable...I'm still waiting for). I can't even blame Earthlink's DSL service for this!
Last night, I suddenly lost my ability to connect to anything and, of course, immediately thought my DSL connection had gone out again. So I schlepped into the room where the modem is to take a disgusted look at its DSL and Internet lights being out...again...but they weren't. They were happily lit up. Huh?, I said to myself.
I went to another computer and, sure enough, its Internet connection was fine. So I schlepped back to the living room and sat looking at my laptop, puzzled. Its wireless light was flashing appropriately, and clicking on Network Management showed that I was connected to my wireless network. Everything looked perfectly normal. But I couldn't do anything. I logged out and back in, same result. I restarted and logged back in, same result. I logged in as root, same result. I logged in as root using GNOME, and couldn't even connect to the network; it SAW my wireless network (and all of my neighbors') but just kept asking for my network's password in an endless loop. I logged back in as me, with KDE, and plugged in an Ethernet cable. Voila, I was connected again.
A little while later I unplugged the cable and...wireless was working. It worked for a few minutes and then stopped again. Plugged the cable back in, unplugged it later, wireless worked, then stopped. I finally said "to hell with this" and went to bed.
This morning, it's working (but I have my trusty cable ready to go just in case).
Day before yesterday I added the Medibuntu repository and did some stuff like:
Afterward, everything was fine and dandy, but since this is the ONLY thing that's changed over the last couple days I have to suspect it.
One thing I noticed last night that I've never noticed before: When I look at Network Management, under WLAN Interface, it's showing iwlagn as the driver. I don't recall ever seeing--or even hearing of--that before. If it's changed, I can't even say for sure what it was before.
And now--FINALLY--comes my question: WTF?! Any ideas on what happened? And what I can do to fix it. Like I said, it's working right now, but that's no guarantee that it'll keep working.
Last night, I suddenly lost my ability to connect to anything and, of course, immediately thought my DSL connection had gone out again. So I schlepped into the room where the modem is to take a disgusted look at its DSL and Internet lights being out...again...but they weren't. They were happily lit up. Huh?, I said to myself.
I went to another computer and, sure enough, its Internet connection was fine. So I schlepped back to the living room and sat looking at my laptop, puzzled. Its wireless light was flashing appropriately, and clicking on Network Management showed that I was connected to my wireless network. Everything looked perfectly normal. But I couldn't do anything. I logged out and back in, same result. I restarted and logged back in, same result. I logged in as root, same result. I logged in as root using GNOME, and couldn't even connect to the network; it SAW my wireless network (and all of my neighbors') but just kept asking for my network's password in an endless loop. I logged back in as me, with KDE, and plugged in an Ethernet cable. Voila, I was connected again.
A little while later I unplugged the cable and...wireless was working. It worked for a few minutes and then stopped again. Plugged the cable back in, unplugged it later, wireless worked, then stopped. I finally said "to hell with this" and went to bed.
This morning, it's working (but I have my trusty cable ready to go just in case).
Day before yesterday I added the Medibuntu repository and did some stuff like:
Code:
$ sudo apt-get update $ sudo apt-get dist-upgrade
One thing I noticed last night that I've never noticed before: When I look at Network Management, under WLAN Interface, it's showing iwlagn as the driver. I don't recall ever seeing--or even hearing of--that before. If it's changed, I can't even say for sure what it was before.
And now--FINALLY--comes my question: WTF?! Any ideas on what happened? And what I can do to fix it. Like I said, it's working right now, but that's no guarantee that it'll keep working.
Comment