Skip navigation

My adventuring into the vast and wonderful realm of open source software and Linux continued this week with the Ubuntu 7.04 Feisty Fawn release. So, I’m not sure if I mentioned this before but I’m using Ubuntu on a Compaq Presario v6000 that I bought back in January. So, it’s kind of a new laptop, which is bound to cause some issues. Has it ever.

So, I come home from work on Thursday night and I boot my laptop and slip into Ubuntu, even though I’d been downloading an install disk all day, Rob informed me that you could just download an update through the Update Manager. So, I gave that a shot. It took all night (partly because the net was being slow and partly because my screensaver was acting up and causing my computer to reboot whenever it came on). So, finally, Friday morning everything is updated and all I have to do is restart to have my very own copy of Feisty. So, I restart, and the computer tells me that there is an error in the XServer and it can’t load the UI. “Wha?” says I shaking my head with the accompanying shocked head shaking noise from cartoons. So, with my laptop next to me I sat at my desktop computer and went out in search of why the hell this thing wasn’t working. Turns out, the way to get the UI to start working was to change a setting on the xorg.conf file, change the configuration of xserver, from using the nvidia driver (which is the type of graphics card I have) to using something called “vesa.” I did that and yay! The UI loaded, but it looked kind of cruddy. So, I started poking around the Synaptic Package Manager and saw that though the nvidia-new driver was loaded (as it should have been) the nvidia-new kernel wasn’t loaded. I stroked my beard, nodded my head and installed the kernel, then went into the config file for xserver and changed it back from vesa to nvidia. I rebooted, and crossed my fingers. It worked, now my display is all shiny and wonderful.

Still, that was not my only issue with Feisty. No, you see, no matter what I do, whether it’s get a new computer, move and set up my computer at a new home, or install a new OS,  I always have one issue, connecting to the internet. Without fail, I will have issues connecting to the internet. I appear to be cursed. See, Ubuntu doesn’t currently work with the built in wireless card for my laptop (it’s a Broadcom Dell 1390 mini-PCI card wireless adapter … or some similar combination of those words). I tried for almost 3 solid days when I first installed Edgy to get the damn wireless card to work. Finally, I gave up on the internal wireless card and started fiddling with a Linksys WUSB54GC wireless adapter I happened to have lying around. I got that to work after several hours of poking around and then ordering a DLink DWL-122 off of EBay. So, for over a month now, I’d been using this Linksys adapter and just had the little DLink one sitting in it’s box off to the side. Yesterday, after having gotten the UI to work I had to try and get my damn internet to work, because not only does Feisty still not really deal with my internal wireless adapter, for some reason the Linksys one wasn’t really working. So, I tried to focus on getting the Linksys adapter to work, for about an hour or so I poked around the net looking for the instructions I’d used to make it work before. I couldn’t find them, so I grabbed the DLink and poked and prodded and finally tried one simple command in the terminal I was sure wouldn’t work, and it did, and now I have wireless access with the laptop again. So, as I explained to my delightful girlfriend, who politely held her tongue when I mentioned I got the Linksys adapter to work but the DLink adapter was already on the way, it wasn’t entirely a waste of money to get that DLink adapter. In fact, the DLink seems to be running faster than the Linksys did, which is pretty cool.

So, now I have Feisty up and running on the laptop, and I have to say that it is a definite improvement over Edgy, it seems to work a lot better. With Edgy I had issues with the laptop freezing and  having to reboot. Feisty hasn’t had that problem yet. Anyway, I also installed Beryl, and there were some issues, but overall that is pretty damn cool. I’ll post more on my adventures with Beryl later.

Advertisements

4 Comments

  1. ok, sounds like a hella ride. nice work. what’s Beryl, and why do I want it?

  2. I am not able to get DWL122 work under Feisty. Could you tell me how you got that usb dongle work under feisty? Thank You.

  3. I can give it a try … unfortunately my methods are far from methodical. So, I’m afraid however I got it to work may have something to do with all the other things I was doing. Still, it started working after I was fiddling in the terminal, here’s a really loose totally non-technical, sorry I can’t give you more info type explanation:
    In the terminal type: iwconfig
    This should list everything your computer can identify as wifi devices, these will probably be wlan1, wlan0, eth1, and/or eth0 (might only list 1, might list many). Most probably won’t list any details, if one does, that is probably the DWL122. If none of them do then you’ll just have to try the following on each device. Pick the one with details (if there is one), and do the following (for the sake of example I’ll use wlan0 here).
    In the terminal type: sudo ifdown wlan0
    This should deconfigure the wifi device you selected.
    Then type: sudo ifup wlan0
    This will configure the identified wifi device. Now, that is when mine started working … as if by magic. I suspect part of the reason it started working was because of how I set up the network interfaces while fiddling with another device. So you may want to learn a bit about how to fiddle with the file etc/network/interfaces (from the terminal type: gksudo gedit etc/network/interfaces).
    Again, really sorry I can’t be more specific I’m kind of a poke and prod things until they work sort of guy and unfortunately can never track down exactly what I did to make anything work so as I can explain it to someone else. Do let me know if that works, though, and thanks for the comment!

  4. I am trying install a Linksys Wireless-G USB Adapter, model WUSB54GC on my desktop, with a Linksys WRT54GS v1.1 Wireless Router installed and functioning properly through Ethernet on eth0. Here is what I got and the wireless adapter is still not working on Ubuntu Feisty on my desktop. I am not sure what this output means.
    sudo ifup wlan0
    Internet Systems Consortium DHCP Client V3.0.4
    Copyright 2004-2006 Internet Systems Consortium.
    All rights reserved.
    For info, please visit http://www.isc.org/sw/dhcp/

    wmaster0: unknown hardware address type 801
    wmaster0: unknown hardware address type 801
    Listening on LPF/wlan0/00:1a:70:a7:27:30
    Sending on LPF/wlan0/00:1a:70:a7:27:30
    Sending on Socket/fallback
    DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
    DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5
    DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 9
    DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 11
    DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 2
    No DHCPOFFERS received.
    No working leases in persistent database – sleeping.

    Subsequent attempts generated the folllowing output
    sudo ifup wlan0
    Ignoring unknown interface wlan0=wlan0.

    Any suggestions?


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: