Asus 900A EeePC with Puppy linux on SDHC

Getting a suitable linux for my old Asus Eee PC 900A netbook has been a bit of a trial.

Chromium OS was a LOCK-N-FREEZE disaster. Android was only marginally better. There is no straight Ubuntu that is not quirky and a wifi nightmare. And there is the worry that some update to ACPI settings will leave the fan disabled and the Intel Atom CPU toasted.

Today I finally have what MAY be workable: Puppy linux for Eee PC. I have one basic version on the SSD and a version with some add-ins on an SDHC chip.

 Two web pages were essential :

• http://wiki.eeeuser.com/howto:installpuppylinux 
• http://www.murga-linux.com/puppy/viewtopic.php?t=34159 

From the latter, I install the drivers (the first and then the group-of-4.) Click DOWNLOAD but don't download when prompted : opt to open in the default package installer. You will have to start with an ethernet cable and use the simple connection tool once the drivers are in place for wifi.

The default browser is SeaMonkey, so on the expendable SDHC chip I have installed Chromium. Firefox is also available as a package already listed for download in the pakage manager. So far, so good ...

---

Asus Netbook and EeeBuntu (again)

Again I find myself coming back from a sleeping netbook to no wireless connection.

I thought I would post what seems to work well enough short of a diagnosis or fix:

The idea is to stop and restart two processes.
Open a terminal session then enter

sudo pkill nm-applet
sudo pkill NetworkManager
sudo NetworkManager &
sudo nm-applet &

Now the nm-applet returns to the topbar, shows wireless connections and my wireless in fact reconnects automatically within a few seconds of completing this little reset task.

The trailing ampersands leave the process running; you may not need the sudo if you run as root (for daily use I always login as a user)
You may also run the "services" app from the applications menu to check that you are not needlessly running a Bluetooth process which you do not use.

I have not had time to look into which update(s) to this EeeBuntu 3.0 may be the culprit(s).

Post a comment if you have a tip or correction ...

And I still love EeeBuntu on this lil' netbook !