Sí, es Agosto. An update and some iPod hackery.

After a seven month period of almost total inactivity, this post is in attempt to save a now-defunct blog. Exactly what have I been up to?

I do have to say I have kept up activity on all of my favorite websites, including sites like http://phoronix.com and others. http://tuxmachines.org must be thanked as well, since the founder of that website has been a great resource for myself, expanding my readerbase and giving me inspiration for new posts. Thanks to srlinuxx!

Arch Linux continues to be my Linux distribution of choice, holding it's place as light and fit for my ASUS system. Head on over to Arch Linux to check it out!

This summer has been filled with advocacy and opportunity. This is the reason why the blog has not been updated in a while, not to forget the past time for school.

This truly is just a garbled bunch of thoughts, so while we are participating in it, let us continue on to the current project at hand.

iPod Touch as a Secondary Display on Linux

Unfortunately, the iPod Touch is an Apple-produced, close source device, with many free or paid applications. Luckily, despite limited integration with Linux, a user can still run it as a secondary display. This does not mean that the user will be able to mouse over to the iPod and click, but rather, the iPod is comparable to a second computer running on the first. Perhaps in the future, with a little bit of hackery, this will be possible. For now, sit tight and enjoy the ride.

First, Set Up a Working Environment for the iPod

What do you need?

For this mini-project, you will need the following:
  • A Linux Computer, Arch Linux, mentioned above is used primarily for experimentation.
  • An iPod Touch, or a device with a VNC client.
  • Information about the screen resolution on the device
  • A VNC Application. I am using Mocha VNC Lite for the iPod Touch.
  • The TightVNC package for the command vncserver
  • About an hour or so of time for basic functionality. You will need more time for understanding and tweaking.
  • Some applications on your Linux machine to test on the device.
  • A Wireless network
Please note, this project is currently incomplete. It will remain incomplete until it is

Roll up your sleeves.
  1. Start up your Linux Machine and prepare to get started. Have a working network connection.
  2. Ubuntu Users, please install the package tightvncserver Fedora Users should install tightvnc Arch Users should install tightvnc Other users should find a package that provides the vncserver command.
  3. Get Mocha VNC Lite from the Apple App Store.
  4. Find the computer's IP Address using ifconfig
  5. Run the vncserver command, using vncserver -geometry 320x480 :1 Note, the geometry sets the screen resolution. Customize this for your device. 320x480 is appropriate for iPod Touch and iPhone. Enter the required data. Note, I find that VNC does not like passwords that are not 8 characters.
  6. On Mocha VNC Lite, enter your computer IP Address, the VNC Server Port, which is 5901, the password, and a name. Change 32-bit Color mode to On.
  7. Connect. You will probably be given a TWM session, we can change that.
  8. Enter nano ~/.vnc/xstartup and change the included text to exec ck-launch-session openbox-session for openbox, or exec ck-launch-session gnome for Gnome.
  9. Enter vncserver -kill :1
  10. Enter the vncserver -geometry 320x480 :1 again. To ensure that the VNC server will always start up, enter vncserver -geometry 320x480 -alwaysshared :1
  11. Connect with your iPod
  12. Enjoy your iPod external monitor.

A Review on ASUS' RMA Process

Recently, my laptop charger had broken, and the laptop would not charge. The battery also had very little capacity. Luckily, I was able to borrow a charger from a good friend whom of which had the ASUS EeePC 1000H, with a compatible charger to my 904HA. With this, I was able to take off any files that I wanted. After this, I had to finish the RMA process.

The netbook was beginning to give me problems, the battery was unable to hold a charge for more than an hour, the charger was unable to charge the battery (Possibly caused by a frayed cable inside of the charging cable), and as we have known before, the audio did not work ( See Ubuntu on the EeePC 904HA). I also had a few filesystem errors (as named in the post entitled Saviour). The laptop was becoming something with very limited function, it was becoming unusable.

The First Encounter
The first encounter with ASUS was when I contacted them to ask if the issues were hardware or software issues, and if I could get a new netbook as a replacement. I was greeted by a couple nice people who stated that they were hardware issues, but unfortunately their policy states that they cannot offer a replacement. They promptly responded to this message and gave me a link to RMA the netbook. This was before my charger died. Once it did, I promptly filled out the RMA request.

The Second Encounter
Once I filled out the RMA, I waited for a while for my RMA number. I waited a total of one or two weeks. During these one or two weeks, I sent a second RMA request. After this, I was replied with two emails from ASUS, one stating the directions and the RMA number, and another stating that I had already been given an RMA number. I then proceeded to follow the directions. The directions were not in order, although they were easy to understand. After I recieved my RMA number, I readied, packaged, and sent my EeePC via USPS Priority Mail. Goodbye EeePC, See you sometime soon!

The Third Encounter
With the mailing, I ordered delivery conformation to ensure that ASUS recieved the laptop via USPS. I also insured it. After I had mailed it on Thursday of the previous week, I confirmed that ASUS had recieved the laptop on Monday. As soon as I noted this, I headed to ASUS' website, and clicked Live Chat. I spoke to a person named Roald, a very nice person (Thank you Roald!), who I asked what the state of my RMA was in. He replied with repair (This was Tuesday). I thanked him and continued on my way, expecting to not see my laptop until the next month.

The Final Encounter
After I checked the status, I waited for a little while not expecting to see my laptop for a while. The holiday of Christmas goes by, and I have not checked the status for a while. One day when I return home, there is a FedEx slip saying that the company had missed finishing shipment. This went on for another day. On the third day, my laptop was back. Thank you ASUS!

A Final Statement

The process of RMAing my laptop was decently short. ASUS has provided for every aspect of my laptop that needed to be fixed. Even my Audio is fixed. My charger and battery were replaced at a cost of nothing with an increased capacity. Thank you ASUS.