Bodhi is ARMing up for a new Year

The mainline Bodhi desktop repositories recently received the gift of stable E17 packages and this same present isn't far off for our ARMHF branch. In the mean time however I have prepared and shared new ARMHF images for the Raspberry PI and Samsung Chromebook.

For the Raspberry PI image, in addition to sporting the shiny new E17 packages - it now comes with the much requested WICD network manager by default. This means those of you using your Raspberry PIs with wireless devices will now have a GUI by default to configure/connect with this interface. You can find this new Raspberry PI image on our downloads page.

The Chromebook release is a bit more exciting. This image has audio working by default and the track pad functions much smoother - including two finger tap to simulate a right click. To get this latest images you follow the exact same install instructions I outlined here a couple weeks ago. For existing Bodhi-for-Chromebook users you can fix your audio by following this guide and improve the trackpad by following this one. One other thing worth noting is that the Chromebook automated installer now includes a md5sum check - so it will only complete the install if your download is valid.

I haven't forgotten about our Nexus 7 users - an update for you will be coming later this month as well.

~Jeff Hoogland

Introducing eAndora - Pandora Client

A good deal of the work I do with the Bodhi project is packaging software/releases and managing things. One of my goals for this new year is to spend some time doing some actual development work with the Enlightenment Foundation Libraries and, more specifically, Elementary. I have a good bit of background with python programming, so my first leap into this field is writing a few small GUI applications in python and elementary.

I finally have enough work done on one of these projects that I feel OK sharing my work with the world. Today I would like to share with you a very, very early release of an application I am calling eAndora:

eAndora is a front end for Pandora Internet Radio. I've started a git repository here that I will be publishing updates to as I write them. The interface is still very basic, but the player is completely functional in the aspect that it allows you to browse and play your Pandora stations and skip tracks you don't like. In addition to being developed with Elementary, eAndora differs from projects like Pithos in the fact that it uses VLC as a streaming back end as opposed to the more common gstreamer.

Here are a few screen shots of the first draft of the GUI:

Login Screen:

Main Window:

Station Select:

I've packaged eAndora for Bodhi Linux and users can get it via a simple:

sudo apt-get install eandora

This package includes a launcher that is placed in your Audio menu.

Folks on other operating systems will need at least EFL 1.7.3, version 1.7.0 of the python EFL bindings and VLC 2.0.  Once you have all these installed simply clone the git repo and launch eAndora with:

python eAndora.py 

Please feel free to let me know any issues you find with eAndora by dropping a comment on this post. Do not however report a lack of functionality as an issue - there is still a good deal of work that needs to be done on this project - I just believe in sharing early and often.

Cheers,
~Jeff Hoogland

Bodhi Linux gets E17 Stable Packages

Less than two weeks ago the E team finally had its stable E17 release. The Bodhi team and I have been working hard to deliver this release to our users in its best possible form in a timely fashion. Today we are happy to announce that these stable E17 packages have made their way into Bodhi's main repo. Existing Bodhi users can upgrade their systems to these latest packages by following the instructions detailed here.

Please be aware of a few things when upgrading to these packages:

First, since this is a major E17 release all current user configurations have to be reset. This means all of your current custom E17 profiles will need to be recreated starting with one of the Bodhi default profiles.

Second, the terminology terminal emulator has been having some stability issues with its most recent release. Because of this, I would highly recommend installing a secondary terminal emulator before installing these upgrades.

Finally, all of our wonderful E17 themes need updates to function with this latest E17 release. Currently we have around twenty themes that function well with the latest release. You can find them on our brand new art page.

Enjoy this fantastic new E release, folks! Also, please remember do NOT post support request on this blog post! We have a forum for that.

Also - for those wanting a brand-spanking new install with E17 stable - our Bodhi 2.2.0 discs should be out of testing by the end of this week.

Almost forgot! Happy 2013, folks.

Cheers,
~Jeff Hoogland

Bodhi ARMHF Alpha for Nexus 7

Earlier this month we collected enough donations that I was able to pick up a Nexus 7 to do some development work on for Bodhi. Today I would like to share our first public images for the Nexus 7. They install, they boot up, and they are semi functional. By that I mean the touchscreen and wireless work OOTB and the interface runs smoothly on the device. I haven't had time to try and make audio work fully yet - but I have gotten some noise to come out of the speakers.

With the help of my lovely fiance I filmed the following short demo video of Bodhi running on the device:

Anywho - installing Bodhi on the Nexus 7 follows the same process as installing Ubuntu on the device. I don't have an automated installer finished just yet so you will need to install the Bodhi images using a manual install process. This can be done using the following steps:

Step 0 - Getting the Tools

Installing Bodhi on the Nexus 7 can be done from any Linux distribution so long as you have the proper android tools installed (if you are using Bodhi on your desktop the Android tools can be found in our repositories). Namely you need the fastboot command.

Step 1 - Unlocking your Nexus 7

The bootloader on the Nexus 7 needs to be unlocked to accept other operating systems. Start with your device off, then while holding the volume down button power the device on - you will soon see the bootloader screen. Attach the Nexus 7 to your computer with a micro USB cable and run the command:

sudo fastboot oem unlock

After you run this command your Nexus 7 will ask you to confirm you want to unlock the bootloader - do so. Then run:

sudo fastboot reboot-bootloader

to finish the unlocking process.

Step 2 - Get the Bodhi Files

You need to download and then extract both the tarballs found here.

Step 3 - Writing the data to the Nexus 7

Open a terminal to the directory where you extracted both the files you downloaded above. Then run the following commands in order:

sudo fastboot erase boot

sudo fastboot erase userdata

sudo fastboot flash boot boot.img

sudo fastboot flash userdata rootfs.img

sudo fastboot reboot

After you run the last command your Nexus 7 will reboot and automagically extract and install the Bodhi file system on your device (this will take a few minutes). When it is finished it will boot right into the Bodhi desktop for you.


User Information

Default username:

armhf

Default password:

bodhilinux

The default user has sudo rights.



Getting Support

Please, please, please do not make a comment on this post asking for support with an issue you encounter with installing/running Bodhi on your Nexus 7! Comments asking for support will be removed from this post. Instead please open a support request thread in the Nexus 7 section of our user forums. It is much easier to manage/search/solve issues in a message board format than a comments section.


Other Notes

I do consider this an alpha quality release. As noted above the sound still doesn't work by default and I am sure there are some other minor niggles that need to be worked out.

Cheers,
~Jeff Hoogland

Bodhi ARMHF Alpha for Samsung Chromebook

As I mentioned in a post last weekend, I've got my hands on the new Samsung Chromebook. The hardware in this device is simply awesome (full formal review forthcoming), but ChromeOS left me wanting a real operating system with non-cloud applications. Thankfully I've been working on Bodhi's ARM branch for awhile now and it proved fairly simple to get at least a base system up and rolling on the Chromebook (largely due to the fact that ChromeOS is Linux based).

Now, unfortunately the current install process for getting an alternative operating system to boot on the Chromebook isn't as easy as our Genesi images - but if you follow the instructions I provide below to the letter you should have Bodhi booting on your Chromebook in no time!

Please note following these steps WILL permanently delete all local data and configurations of your ChromeOS! It essentially restores the system to factory defaults.

Step 1 - Boot in Recovery Mode

Make sure your chromebook is off. Then hold the escape and refresh keys (where f3 should be) and power on the device. This should get you to a recovery screen - press ctrl+d followed by enter. The system should now reboot into recovery mode.

Step 2 - Get to a TTY with Internet

Once the system reboots in recovery mode it will take a few moments to get everything configured (this requires no user input, just waiting - so grab a snack). Once the system starts up select a wireless access point to connect to, but do not log into a Google account. Now that we have an internet connection you need to drop to a TTY. To do this press ctrl+alt+-> (The "->" key is where f2 would be on a standard keyboard).

For the username type chronos and then press enter - no password is needed.

Step 3 - Download and run Bodhi installer

From the tty run:

wget http://goo.gl/HFG6a

Followed by:

sudo bash HFG6a

Both of the above commands are case sensitive so make sure you type them correctly! After running the second command you will be provided with some information about your Chromebook - press enter to continue.

Step 4 - Choose how much space you are giving Bodhi

The installer will prompt you for how much space you want to give to Bodhi. Enter an integer amount for how many gigs you would like to give Bodhi. On the 16gig smartbook the most I would recommend giving to Bodhi is 9gigs (with the max being 10).  For reference the base Bodhi install occupies around 1.6gigs. Once you select an amount of space to give Bodhi the drive will be re-partitioned automagically and then your system will restart. When it starts back up again you will need to walk through the ChromeOS setup process once more - again get as far as the Google login screen but do not log in.

Step 5 - Getting the Bodhi Filesystem

Get to a TTY again by following the instructions outlined in step 2 once more. Then run the same two commands provided in step 3. This time the Bodhi installer will see your drive has already been partitioned and it will begin downloading the Bodhi Chromebook image which it will then install. Note that this will take awhile depending on your internet connection speed as a 300MB tarball needs to be downloaded and extracted. After it finishes installing your system will reboot and you will be greeted by the Enlightenment desktop!

User Information

Default username:

armhf

Default password:

bodhilinux

The default user has sudo rights.

Getting back to ChromeOS

If you need to get back into ChromeOS after installing Bodhi on your Chromebook - don't worry it is still there. In a terminal client on Bodhi run:

sudo cgpt add -i 6 -P 0 -S 1 /dev/mmcblk0

Once you are done with ChromeOS you can run the following in the ChromeOS TTY to get back to Bodhi:

sudo cgpt add -i 6 -P 5 -S 1 /dev/mmcblk0

Getting Support

Please, please, please do not make a comment on this post asking for support with an issue you encounter with installing/running Bodhi on your Chromebook! Comments asking for support will be removed from this post. Instead please open a support request thread in the ARM section of our user forums. It is much easier to manage/search/solve issues in a message board format than a comments section.

Other Notes

In the current image the track pad is kinda fickle (tap to click doesn't work) and OpenGL support is currently non-functional. Other than that the image is very functional - I have been using it for my day to day activities for the last week now and I have been very pleased with the results. With that being said - please note I consider this an alpha quality release and as such Bodhi's ARMHF testing repos are enabled by default in the current Chromebook image.

One other thing to note is that the top row of keys acts as "function" keys (f1-f10) in Bodhi as though it was a normal keyboard. I personally use the volume up/down/mute keys often on my systems though - as such I have bound the alt key to act as a "function" key normally would on a laptop. Meaning alt+volume key will perform it's indicated action. Also - to make any noise come out of the speakers see this.

Closing Remarks

I would like to extend my thanks the author of this post who created a script for getting Ubuntu setup on the Chromebook. My own Bodhi install script is based directly on his.

Cheers,
~Jeff Hoogland

Bodhi Linux ARMHF RootFS

If you've been following my blog (or my updates on Google+) then odds are you know I currently have my hands on two ARM devices (plus a third in the mail) I am working on creating Bodhi Linux images for. With this in mind I've decided I am going to start maintaining a generic ARMHF root file system to make creating Bodhi Linux images for new ARM devices easier for myself and others.

You will always be able to find the latest copy of this file system on Bodhi source forge page here. The default user name is armhf and the default password is bodhilinux. The default user has sudo access by default.

Essentially on any device we have a functioning Linux kernel for - it should simply be as easy as extracting that file system to a bootable location. Copying over /lib/firmware and /lib/modules and then telling your ARM system to boot from this new file system.

As an aside - this is the first blog post I am writing from the Samsung ARM Chromebook with the Bodhi desktop! Hopefully have install instructions for this device online soon.

Cheers,
~Jeff Hoogland

HOWTO: Start an SSH Session from ChromeOS

My lovely fiance knows how much I love my toys and opted to get me one of the new ARM based Chrome books as an early Christmas present. I'd been talking a lot about the device because the hardware on it is fairly fantastic for the 250$ price tag it comes with. At any rate - I'll be writing up a full formal review of the device at a later date (once I have had a chance to use it more). I also plan to create Bodhi ARM images for the device once time permits.

Until I have time to get Bodhi running on the device though I am stuck with ChromeOS - which while interesting leaves some to be desired. At the very least I need my operating system to have a web browser and a ssh connection - the former ChromeOS provides very obviously (the whole OS is one giant web browser). Getting an SSH connection from the device was not as straight forward however. I started by searching for a terminal emulator on the Chrome Web Store. As you can see - there are a few options there, but none of them would successfully open a ssh connection to my build servers from my Chrome Book.

A little bit off searching on the Linux answer machine yielded me a proper solution from the comment section of a posting. To get a SSH connection on ChromeOS you do not need to add any software! Pressing the key combination:

ctrl+alt+t

Will open a browser based terminal emulator called "crosh" in a new tab of your browser on ChromeOS. Now my build servers are accessed from a non-default ssh port. On any Debian based operating system I would use the following to connect:

ssh -p username@myserveraddy.com

The ssh client on ChromeOS doesn't seem to like the -p argument for a port number though. I found two ways to connect to a ssh server using a different port number. The first is simply:

ssh username@myserveraddy.com

The second is a whole lot less intuitive. In order you type:

ssh

host myserveraddy.com

user username

port  

connect

Have fun sshing from ChromeOS!

~Jeff Hoogland