In the previous post I've described my first experience with an Acer Aspire One D250 netbook together with eeeBuntu (based on Ubuntu 9.04 Jauntry). I was quite impressed of how easy it was for the most part to get going. In this part I will look at how to get eeeBuntu working witch a 3G USB dongle and a mobile phone.
Easy Installation and Use
EeeBuntu detected both my Huawei E220 3G dongle and my Nokia N95 as wireless modems straight away, no configuration necessary. The first time they are connected, a configuration menu automatically appears which contains a pretty extensive network operator and APN settings list. After selecting a country and network, a profile is automatically created and added to the network list in the taskbar. Strangely enough, the menu entry did not appear straight away in all cases, sometimes a reboot was necessary when adding an new profile. In case the operator is not in the database, it’s possible to just select one of the operators and then edit the configuration by hand.
PIN protection Issue
Most of my SIM cards are not PIN protected so clicking on the new network profile entry connects to the network very quickly. With some of my SIMs, however, the PIN can’t be deactivated so the 3G dongle requires the PIN before launching the connection. While this worked pretty well the first day, I started to get problems since then and the behavior became pretty erratic. In the end, I wrote a shell script to send the PIN to the modem before using one of the 3G profiles.
Disconnecting and Status Information Missing
Disconnecting from the network also worked well via the network menu during my experiments the first day. Since then, however, for reasons unknown, clicking on “disconnect” has no effect, not with the E220 and also not with the N95. Unplugging the dongle or the mobile cuts the connection but brings further trouble. In many cases plugging the E220 back into the USB port has no effect and eeeBuntu needs to be rebooted. In Windows on the same machine, unplugging and plugging the dongle back in works well, so it’s not a hardware issue. With the N95 unplugging and plugging in again works in most cases.
Another thing that bugs me is that I have no means of seeing signal strength or to lock the 3G dongle to a certain operator or network technology as I can easily do in the launcher program provided for Windows. Too bad as this is a very handy functionality in some situations!
While the basic implementation for 3G connectivity works well, it is unfortunately a bit unreliable in eeeBuntu version 3. While I can maneuver around the issues, a normal user is likely to get frustrated.
One thought on “Netbook, eeeBuntu and Mobility – Part 2”
I was wondering when you will finally discover the Atom ;-).
You should’ve tried the original – EeePC ;-). I played at work with a 1000H and a 901, both the Go version (with 3G built-in). With 6 cells I got 5-6 hours. Pretty amazed on what can you get for 400Euro, as compared to the Thinkpad X200 that I use everyday and did cost about 2500Euro! I would say that for 80% of the daily tasks there’s no noticeable difference, so really is 2100 Euro worth the rest?
The eeebuntu it’s a bit nasty. If you don’t go crazy for out of the box buttons working and stuff like that, I was much more happy with a default Jaunty. Also Android Cupcake runs decently on it.
Then the 3rd Atom that I tried was the LG x110 – great build, good quality materials, speakers, lcd, etc… but… ridiculous battery life compared to the eee. The 4th was the EeeBox – also very nice (quiet and very low power consumption), but as the HTPC that could be mostly on, although the HD playback capabilities are not there yet… so waiting for some Nvidia powered ones.
Also, just think about that CPU in your smartphone ;-). Because this is what Intel is aiming with it anyway.
Comments are closed.