shinmai
May 16th, 2009, 12:43 PM
I hadn't used Ubuntu in a while, (I run Debian on my desktop and use my laptop to try out other distros out of interest, the last Ubuntu release I'd installed was Feisty) and when Jaunty came out I thought I'd give it a go again.
I got a disc from a friend, and popped it in, and did a quick install alongside Vista on my HP Pavilion dv5-1021. The first boot went flawlessly, and I was very pleasantly surprised with all of it - 20 seconds (-ish) from poweron to desktop, wifi worked 'out of the box', as did X (with Feisty, I had to manually edit xorg.conf to use the right driver) and most impressive of all, suspend to disk, which hasn't worked without manual tweaking on any other distro with my dv5. I'd had my opinion of Ubuntu altered hugely, and powered down for the night and thought I'd do some more testing in the morning.
When I booted the OS up I was annoyed to find that the WLAN wouldn't connect to my AP, but merely asked for the passcode, but never established a connection. I tried to connect to one of my other APs with no success, and - on a whim - tried to disable and re-enable wireless networking in gnome network applet. What this acieved, was that now the network applet couldn't even get a list of APs, let alone connect to one.
At this point I was already running late for work, and just wanted to check my mail before leaving, so I rebooted to Vista, only to find to my horror, that I still couldn't find any wireless networks, or manually connect to my APs. I have no idea what the heck ubuntu installer or gnome network applet did, but it has now effectively managed to disable my onboard wireless adapter, and I have no idea how to re-enable it in either OS, the wifi switch on the laptop doesn't do anything, either.
All in all, I can't say that I'm too happy with how my Jaunty installation worked out, and hope HP, or someone here can shed some light on why disabling an option in a windowmanagers network helper seems completely disable the network hardware, and how one would revert such a change.
I got a disc from a friend, and popped it in, and did a quick install alongside Vista on my HP Pavilion dv5-1021. The first boot went flawlessly, and I was very pleasantly surprised with all of it - 20 seconds (-ish) from poweron to desktop, wifi worked 'out of the box', as did X (with Feisty, I had to manually edit xorg.conf to use the right driver) and most impressive of all, suspend to disk, which hasn't worked without manual tweaking on any other distro with my dv5. I'd had my opinion of Ubuntu altered hugely, and powered down for the night and thought I'd do some more testing in the morning.
When I booted the OS up I was annoyed to find that the WLAN wouldn't connect to my AP, but merely asked for the passcode, but never established a connection. I tried to connect to one of my other APs with no success, and - on a whim - tried to disable and re-enable wireless networking in gnome network applet. What this acieved, was that now the network applet couldn't even get a list of APs, let alone connect to one.
At this point I was already running late for work, and just wanted to check my mail before leaving, so I rebooted to Vista, only to find to my horror, that I still couldn't find any wireless networks, or manually connect to my APs. I have no idea what the heck ubuntu installer or gnome network applet did, but it has now effectively managed to disable my onboard wireless adapter, and I have no idea how to re-enable it in either OS, the wifi switch on the laptop doesn't do anything, either.
All in all, I can't say that I'm too happy with how my Jaunty installation worked out, and hope HP, or someone here can shed some light on why disabling an option in a windowmanagers network helper seems completely disable the network hardware, and how one would revert such a change.