As I write this, I'm logged into my Ubuntu partition on my laptop. We have total and complete success!
This is great. Not only can I scan for wireless networks now, I can also connect! I'm so excited.
Lessons learned:
network-manager: friend
orinoco: friend
hostap: THE DEVIL
Ubuntu Fiesty Fawn: Completely f-ing awesome.
Now, to sit back and enjoy my intrawebs on my linux partition! How shall I celebrate?
I know. Watch as many Flight of the Conchords episodes as I can!
Then some Planet Earth! ^-^
I am completely pleased with myself.
Wireless Adventure: Success!
Showing posts with label wireless. Show all posts
Showing posts with label wireless. Show all posts
Wednesday, August 08, 2007
Wireless Adventure - Part III (Blacklisting hostap)
So blacklisting Orinoco had some positive effects. Now, I can scan for wireless networks (whoopee!) As you can imagine, this was very exciting. I thought I had finally got it to work.
Unfortunately no.
I'm now thinking about blacklisting hostap instead of Orinoco:
my etc/modprobe.d/blacklist file should now read like this:
blacklist prism2_pci
blacklist hostap_pci
blacklist hostap
Let's see how this works!
More update goodness soon.
Unfortunately no.
I'm now thinking about blacklisting hostap instead of Orinoco:
my etc/modprobe.d/blacklist file should now read like this:
blacklist prism2_pci
blacklist hostap_pci
blacklist hostap
Let's see how this works!
More update goodness soon.
Wireless Adventure - Part II (Blacklisting Orinoco)
More poking around the internets. Lucking I found this.
To quote:
The problem is that the hostap and orinoco kernel modules are competing for control of the card. This is mentioned as a likely problem on NetworkManager site:
(http://live.gnome.org/NetworkManagerHardware)
hostap: "Supports unencrypted, WEP, WPA, and WPA2 networks. Be aware that if you have both this driver and the 'orinoco' driver installed, they may fight for control of the wireless card and render it inoperable to NetworkManager. You should either disable one of these drivers, or ensure that only one driver is able to control the card."
Thank you, Brett!
To summarize the instructions:
1. Check to make sure I'm dealing with the right network card: I entered the following command in bash:
:~ lspci | grep Network
I got:
02:02.0 Network controller: Intersil Corporation Prism 2.5 Wavelan chipset (rev 01)
HA! It matched. Yes! Next, for adding some blacklisting marks to
/etc/modprobe.d/blacklist:
blacklist orinoco
blacklist orinoco_pci
blacklist hermes
blacklist p80211
blacklist prism2_pci
Last step, reboot!
Completing this process took less than two minutes (even less time than it took me to install WICD), and it was relatively straightforward.
I still don't know if it will work yet. I have to go home and see. But I have my fingers crossed! Results later. Hopefully, this should do it!
To quote:
The problem is that the hostap and orinoco kernel modules are competing for control of the card. This is mentioned as a likely problem on NetworkManager site:
(http://live.gnome.org/NetworkManagerHardware)
hostap: "Supports unencrypted, WEP, WPA, and WPA2 networks. Be aware that if you have both this driver and the 'orinoco' driver installed, they may fight for control of the wireless card and render it inoperable to NetworkManager. You should either disable one of these drivers, or ensure that only one driver is able to control the card."
Thank you, Brett!
To summarize the instructions:
1. Check to make sure I'm dealing with the right network card: I entered the following command in bash:
:~ lspci | grep Network
I got:
02:02.0 Network controller: Intersil Corporation Prism 2.5 Wavelan chipset (rev 01)
HA! It matched. Yes! Next, for adding some blacklisting marks to
/etc/modprobe.d/blacklist:
blacklist orinoco
blacklist orinoco_pci
blacklist hermes
blacklist p80211
blacklist prism2_pci
Last step, reboot!
Completing this process took less than two minutes (even less time than it took me to install WICD), and it was relatively straightforward.
I still don't know if it will work yet. I have to go home and see. But I have my fingers crossed! Results later. Hopefully, this should do it!
Wireless Adventure - Part I (WICD)
I looked for suggestions. The first one was WICD. It looked great. A lot of people seemed to be having the same problem, and WICD seemed to just fix it very quickly. Also, the Digg reviewers were treating it like the second coming of Christ: "GREAT interface! network-manager BLOWS! ALL my wirless problems were FIXED when I started using WICD! AND it improved my sex life! FIVE+++ StArS!" Sheesh.
Installation was breeze. I was liking this already! Now came the fun part: testing it out. The interface was lot larger than network-managers. One thing I didn't like about it right away, is that it didn't automatically connect to my WIRED network, which was annoying. Furthermore it required me to create a profile for each IP (for -wired- connections). I didn't like this at all. Since I connect to the internet all over the place, the last thing I wanted was to have a bunch of "profiles" cluttering up the interface, most of which I will probably never use again. Of course, I won't delete any of them in the off-chance that I -do- use them again(and who wants to enter all that information again?). Too aggravating. The kicker was that it wasn't detecting the wireless network present.
That would have been okay. network-manager wouldn't automatically detect wireless networks. I just had to enter them in manually. But, as it would turn out, in WICD, there is no way for me to manually enter a wireless network it didn't detect (they had a "hidden network" box, which allowed you to enter a ESSID, and no encryption key, which wasn't satisfactory.) Maybe I should have given WICD more time. Maybe I should have poked around more. Maybe I was dumb and wasn't looking at the interface closely enough. Could the solution have still been there?
Whatever. I uninstalled WICD and reinstalled network-manager. Back to square one!
Installation was breeze. I was liking this already! Now came the fun part: testing it out. The interface was lot larger than network-managers. One thing I didn't like about it right away, is that it didn't automatically connect to my WIRED network, which was annoying. Furthermore it required me to create a profile for each IP (for -wired- connections). I didn't like this at all. Since I connect to the internet all over the place, the last thing I wanted was to have a bunch of "profiles" cluttering up the interface, most of which I will probably never use again. Of course, I won't delete any of them in the off-chance that I -do- use them again(and who wants to enter all that information again?). Too aggravating. The kicker was that it wasn't detecting the wireless network present.
That would have been okay. network-manager wouldn't automatically detect wireless networks. I just had to enter them in manually. But, as it would turn out, in WICD, there is no way for me to manually enter a wireless network it didn't detect (they had a "hidden network" box, which allowed you to enter a ESSID, and no encryption key, which wasn't satisfactory.) Maybe I should have given WICD more time. Maybe I should have poked around more. Maybe I was dumb and wasn't looking at the interface closely enough. Could the solution have still been there?
Whatever. I uninstalled WICD and reinstalled network-manager. Back to square one!
Wireless Adventure - Introduction
So my IBM ThinkPad T30, Phoenix, got a makeover earlier this summer. Due to my general laziness and strange attachment to Ubuntu Breezy, I didn't update to Dapper. When Feisty came out, I found out that I could no longer update my system, period. Shit.
Among other things, this meant that I couldn't do an automatic update to Dapper, and then from there, into Feisty. So, I wiped my partition (after backing up my data) and did a clean install of Ubuntu Feisty Fawn 7.04. That, plus giving Phoenix a new fan and an additional 512 MB stick of RAM, she seemed ready to rock the world.
I really like Feisty Fawn. It's sleeker, cleaner, and it got rid of some minor annoyances I had with Breezy. Perfect set up, I thought.
Then it turned out that my wireless card wouldn't work.
I was mystified. In Breezy, my wireless card worked fine. There was a bug that prevented me from scanning for wireless networks, but as long as I knew the SSID and/or password of the network I was trying to connect to, things worked fine.
Did something go horribly wrong? Did I do something wrong? Why is my wireless card not being recognized? I rebooted into Windows. Maybe it's the network that's at fault?
In XP (where I can scan for wireless networks fine), I located the wireless network I wanted to connect to. I entered the WEP key. Everything worked fine. So nope, nothing wrong with the card, nothing wrong with the network.
Doing some poking around the internets revealed that this is a known bug with network-manager, which, of course, made things so much easier for me. But how to fix the bug?
This multipart (hopefully not too long) series of posts in this blog will chronicle my wireless adventures. Will end when either I give up, or my wireless works in Ubuntu. And, I don't want to "rollback" (if that's even possible for me, considering I did a clean install of Feisty) to Dapper Drake. Let's see who wins!
Among other things, this meant that I couldn't do an automatic update to Dapper, and then from there, into Feisty. So, I wiped my partition (after backing up my data) and did a clean install of Ubuntu Feisty Fawn 7.04. That, plus giving Phoenix a new fan and an additional 512 MB stick of RAM, she seemed ready to rock the world.
I really like Feisty Fawn. It's sleeker, cleaner, and it got rid of some minor annoyances I had with Breezy. Perfect set up, I thought.
Then it turned out that my wireless card wouldn't work.
I was mystified. In Breezy, my wireless card worked fine. There was a bug that prevented me from scanning for wireless networks, but as long as I knew the SSID and/or password of the network I was trying to connect to, things worked fine.
Did something go horribly wrong? Did I do something wrong? Why is my wireless card not being recognized? I rebooted into Windows. Maybe it's the network that's at fault?
In XP (where I can scan for wireless networks fine), I located the wireless network I wanted to connect to. I entered the WEP key. Everything worked fine. So nope, nothing wrong with the card, nothing wrong with the network.
Doing some poking around the internets revealed that this is a known bug with network-manager, which, of course, made things so much easier for me. But how to fix the bug?
This multipart (hopefully not too long) series of posts in this blog will chronicle my wireless adventures. Will end when either I give up, or my wireless works in Ubuntu. And, I don't want to "rollback" (if that's even possible for me, considering I did a clean install of Feisty) to Dapper Drake. Let's see who wins!
Subscribe to:
Posts (Atom)