One of the things I really love about the Ubuntu community is how helpful it is. By following these easy directions, I was able to get the wired network up and running on my netbook. Yes, that’s right. I have a situation where the wireless works and the wired doesn’t! Even stranger, the fix is in an wireless network adapter package!
Because I’ve been burned by stale links, I’m going to repeat some information here.
Netbook: Acer AspireONE D255
01:00.0 Ethernet controller: Atheros Communications AR8152 v1.1 Fast Ethernet (rev c1)
02:00.0 Network controller: Intel Corporation WiFi Link 1000 Series
- Go here (http://linuxwireless.org/download/compat-wireless-2.6) and download “compat-wireless-2.6.tar.bz2”
- Run the following commands:
sudo apt-get update
sudo apt-get install build-essential
tar -xjvf compat-wireless-2.6.tar.bz2
sudo make install
At this point a reboot should load the network driver. For me, the “sudo make install” took a very long time. Well, 10 minutes. But it felt like an eternity.
If a reboot doesn’t load the module, try “modprobe atl1c” (that’s ay-tee-el-one-cee).
And that was it. Lovely! Again, I can’t promote the friendliness and helpfulness of the Ubuntu community enough. They have been great.
Update 2011-03-30: I had to repeat these steps after upgrading to kernel 2.6.32-28 or -29. But it worked.
Today I finally upgraded my primary system to Kubuntu 10.04 LTS 64-bit. I have performed two upgrades to 32-bit machines with no problems. I waited this long to upgrade this system to see how the few weeks following the release panned out. There have been hiccups sometimes, and I am more tolerant of those on secondary systems.
Flawless. Smooth. Painless.
My dual-boot configuration was unaffected, but that is a result of grub still being present as apposed to grub2. With the rumors I have heard about the nuisance in editing the grub2 menu list, I’ll stick with the tried and true for now.
To use a favorite phrase: The Way Life Should Be.
I find it funny the day after I make a glowing comment about support in FOSS projects, I run into a snag that is not documented anywhere.
I filed a bug on it, but was able to resolve it myself. Trying to look at this from a newbie or non-technical point of view, I’m not sure how I would have reached the same conclusion. I happen to know that all *-dbg packages are “debug” packages and are therefore implicitly optional. Removing them was a reasonable step, and it happened to fix it.
However, as a normal end-user, I am not likely to have known about this. In fact, when seeking help, I may have been asked to install these packages to gather more information about a problem.
This is not a good problem to have during an upgrade process. But I did draw this problem down upon myself by installing packages from the backports. However, I seem to recall this same issue when performing a supported upgrade from the previous version of the distribution (Kubuntu 9.04) to the current version (Kubuntu 9.10).
Getting VMware installed got ugly again for a short time. I should have expected this. At least there is a solution, and typically a patch is out within a couple of months to fix the RPM (which can be alien‘d to a DEB).
fronk is my 32-bit file-server & quazi back-up machine. I use this for random bits of development, testing, and primarily as a backup destination.
Saturday & Sunday I performed the 9.10 upgrade on this machine — in place. I made sure to backup my xorg.conf, smb.conf, fstab, and source.list (apt) as those have been clobbered in the past.
- KPackageKit exited with a failure — I think the servers were overloaded. Rerunning it got all of the packages downloaded.
- KPackageKit exited with an error code of <1> — whatever that means. I ran sudo aptitude full-upgrade from the CLI. The only thing remaining to do was to remove packages.
- sudo apt-get upgrade showed nothing to do, and all repositories queried were karmic (9.10)
So, only one reboot, some hiccups that were resolved with persistence, and a lot of leaving this computer to do its own thing, the upgrade took about 16 hours. I think that time is due to heavy traffic on the server. I’ve never had it take this long.
Update from my future self: yes, it was the server traffic. Two other upgrades took about an hour.
I have had to run this more than twice. I thought also keeping this up here as an easy way to find it again would be good. This assumes starting from Kubuntu 9.04.
sudo apt-get install kde-icons-oxygen kdebase-runtime-data-common kdebase-workspace-libs4+5 kdelibs-bin kdelibs5 kdelibs5-data kdepimlibs-data ksysguardd libakonadiprivate1 libeet1 libkdecorations4 libkexiv2-7 libkipi6 libkonq5-templates libkwineffects1 libokularcore1 libplasma3 libqedje0 libqt4-assistant libqt4-core libqt4-dbus libqt4-designer libqt4-help libqt4-network libqt4-opengl libqt4-qt3support libqt4-script libqt4-sql libqt4-sql-mysql libqt4-sql-sqlite libqt4-svg libqt4-test libqt4-webkit libqt4-xml libqt4-xmlpatterns libqtcore4 libqtgui4 libqzion0 libsoprano4 policykit-kde python-qt4-dbus qt4-qtconfig soprano-daemon system-config-printer-kde
sudo apt-get install akregator amarok amarok-common ark dolphin dragonplayer gwenview kaddressbook kamera kate kde-printer-applet kde-window-manager kde-zeroconf kdebase-bin kdebase-data kdebase-plasma kdebase-runtime kdebase-runtime-bin-kde4 kdebase-runtime-data kdebase-workspace-bin kdebase-workspace-data kdegraphics-strigi-plugins kdemultimedia-kio-plugins kdepasswd kdepim-kresources kdepim-strigi-plugins kdepim-wizards kdepimlibs5 kdeplasma-addons kdm kfind khelpcenter4 klipper kmag kmail kmix kmousetool knotes konqueror konqueror-nsplugins konsole kontact kopete korganizer krdc krfb ksnapshot ksysguard ksystemlog ktimetracker kuser kwalletmanager libkcddb4 libkdepim4 libkleo4 libkonq5 libkpgp4 libksieve4 libmimelib4 okular okular-extra-backends plasma-widget-network-manager python-kde4 python-qt4 python-sip4 systemsettings kdeartwork-emoticons python-kde4-dbg python-qt4-dbg konq-plugins kdebase akonadi-server
In newegg’s infamous delivery speed, I received my AOD250 today. My first impressions are quite good.
- solid seating of power plug
- tolerable keyboard –touchtyping is relatively easy (I just typed a few pages in a story I am working on, and my typing suffered very little)
- nice display
- Kubuntu 9.04 installed beautifully with no more hitches than normal — better than my old HP laptop
- touchpad buttons are not as hard to press as some reviews claimed — but I like the resistance
- wireless networking worked instantly (under Kubuntu, that is)
- bluetooth is toggled by a hardware button … very nice (and KDE 4.3 nicely picks up on that and displays the BT system tray icon when BT is enabled)
- Comes with1GB of RAM — and I’m not sure why people are instantly upgrading to 2GB as this works nicely for me. However, it is only $30 …
I have a few instant nits though:
- “End” is Fn+PgDn, “Home” is Fn+PgUp — I use these two keys a lot; these two things are becoming the top annoyance (but not enough to say not to buy one of these)
- USB ports don’t seem to hold things squarely, but I seldom use them
- hardware switch to shutoff touchpad would be nice — Fn+F7 toggles the touchpad; not as convenient as a hardware switch, but tolerably serves the purpose (updated 2009-09-06)
- wired networking isn’t working right now (see this post)
- the glossy screen is tolerable, but I can imagine it being intolerable if I were backlit or sitting outdoors (hmm…)
- the touchpad can be a little fussy about the “touch click” — but it appears to err on the side of less sensitivity; I would prefer it erring in that direction
Overall, the install of Kubuntu was easy, and this is working exactly as I expected. In my first few hours of owning it, I liked it! As if it isn’t already apparent, I plan to keep updating this post. I will ultimately post a review on Newegg.