Showing posts with label linux. Show all posts
Showing posts with label linux. Show all posts

Sunday 30 May 2010

Upgrading Fedora 12 to 13

I'm pleased to report that after problems upgrading from Fedora 10 to 11 and minor issues upgrading Fedora 11 to 12 that I've finally had a no problem upgrade from Fedora 12 to 13 on my home machine.

I have only a very slightly unusual setup in that I've got Fedora running on top of a hardware RAID environment which has caused some issues with preupgrade in the past. Upgrades I have tried on other equipment such as my work laptop have always been flawless and now it seems the issues with RAID installs have gone away too.

So this brings to an end my blog trilogy about upgrading Fedora, short and sweet, it just works! Now onwards to enjoy using a great new distribution that's pushing the boundaries in pretty much every area of Linux usage. Thanks to the Fedora team, Goddard looks fab.

Tuesday 25 May 2010

Pre-built Joggler Images

It seems everyone buying a Joggler is doing so for their own good reasons with thoughts about how to hack the device to their needs. I include myself in this too, why else write these blog posts? The majority of people aren't so interested in the hacking side of things as simply getting the device to do what they want and that's where using a pre-built, already hacked, operating system image can come in very handy indeed.

The Images
Easily the two most popular images are Ubuntu based although there are Joggler communities for Android, Mer and Meego, all of which are Linux based platforms. I've only tried the first of these but can lend my recommendation to either of

As I said, both are Ubuntu based with the key difference being the first image uses the Ubuntu Netbook Remix (a.k.a UNR, Ubuntu Netbook Edition and UNE) while the second one uses "normal" Ubuntu.  You'd perhaps expect them to be in fierce competition with each other but in good open source spirit quite the opposite is true. Both are produced by nice guys who help each other (and the rest of the community out) by sharing what they do.

There's no sense in me reproducing how to download and use either of these images.  Both come with pretty bullet-proof instructions on what to do.  I would, however, heartily recommend you produce the images from a Linux system having recently helped a friend struggling with downloading the images successfully and finding the right tools to do the job under Windows.

Fair's Fair
From my own investigations and messing around with putting Fedora on the Joggler I can certainly vouch for the amount of time and effort these guys have put into producing such good quality, usable hacks.  So, if you do more than just evaluate these for your own use i.e. you really are using your Joggler with either of these images then do give serious consideration to spending a few quid giving something back to the guys as they ask through a small donation.  I have no idea how much they might stand to make through donation and other revenue such as the Google ads, but it's probably not a huge amount and is definitely well earned.

Modification
If you try the images out and there's something you don't like, fine, you don't have to stick with that particular quirk.  There's never going to be a one-size fits all approach so if you don't like, for example, the on screen keyboard, the user interface or something else then feel free to change it.  It's your system once you've downloaded and booted it after all.  There are a lot of, dare I say, complaints on the forums about things not being quite right.  If it's something major then let the guy know who produced the image, it will probably get fixed in their next version.  Also, there's a huge wealth of help and support out there in various places so try looking for someone who's already "been there, done that".

Subject to some of the Joggler Hardware Gotchas it is possible to use these images on devices much bigger and faster than a 4GB USB stick.  I've tried with an 8GB stick and USB hard disks from 80GB through 320GB and even one disk of 1TB.  Simply follow the instructions for either image to write to your larger device as if it were a 4GB stick.  Then use a tool such as gparted (again I recommend Linux simply because it's easy and the tools are readily available) to resize the second partition to be as big as you like.  If you move to a hard disk (rather than USB stick) then you can undo some of the modifications made in the images for efficiency and to try and protect your stick:
  • Change the file system back to ext3 from ext2
  • Add a swap file or swap partition
You can change the file system type from ext2 to ext3 either before or after changing the size of the partition.  Simply boot the image on your Joggler and run the command "tune2fs -j /dev/sda2" then edit the file /etc/fstab to change bit that says ext2 to say ext3, save that file and you're all done.  The reason for making this change is your files will be a little safer in the event of unplanned events such as sudden loss of power.  This was quite rightly turned off for the USB stick images because more data is written to the device and since USB sticks are only capable of being written to a relatively small number of times the trade-off between stick reliability and file system reliability has to be made.

Adding a swap file (if you don't know what this is then have a go at understanding paging)is probably easier in many ways than adding a swap partition and with a recent version of Linux such as the ones used in these images doesn't lead to any loss of performance as might have been expected in older versions of Linux.  Feel free to add a swap partition in gparted though, don't forget to add a line to /etc/fstab to tell Ubuntu to use this partition as swap.  To add a 1GB swap file simple run the command "dd if=/dev/zero of=/swap bs=1M count=1024; swapon /swap" then add a line to /etc/fstab so next time you reboot Ubuntu will use this file for swap space.

You can find a lot more of my information about the Joggler at my Joggler Index post. I also have a list of Joggler Bookmarks.

Thursday 20 May 2010

Getting a Joggler, the how and the why?

Buying a Joggler is pretty simple, you can just go to the O2 shop and get one for one hundred of our UK pounds, or fifty if it's on sale.  The reason for putting "the how" in this isn't to teach you how to buy stuff on the net.  No no, more to say you can get it for less than fifty quid if you're careful!  Those of us who work for IBM have been buying them through a money saving web site we have access to as IBMers such that you buy the Joggler and a PAYG Mobile Internet USB dongle (which you're not obliged to use) for a total of £60 and get £25 cashback for doing so.  That's £35 for a Joggler and mobile Internet, bargain!  I would think this sort of offer must be out there in the wider world too if you look carefully enough.

So why do I, or you for that matter, want one?  There's lots of different uses for it.  Even if you look at it as a dumb wireless digital photo frame then it's far cheaper than other wifi frames out there.  The neat thing about it is it runs a version of Linux internally, has a USB port and is also capable of booting from USB.  This means you can run pretty much anything you like on there instead of the default O2 interface.  So, it's the ideal hacking toy and can become a fully fledged computer system disguised as a photo frame if you choose to do so.  The sky is the limit.

For me, I use it as a low power home server running:
  • remote login to home (ssh)
  • music streaming (squeezebox server)
  • internet connected photo frame (gphotoframe)
  • trivial internet browsing (chrome + touchscreen addon)
  • file server (nfs, http, ftp, smb, etc as required)
  • backup server (rsync) 

I've also found it very useful to have a computer connected to my printer for wifi print serving from my laptop in the past.  Currently the Joggler isn't located next to my printer so I'm not doing this but it's definitely an option for the future.  Similarly I may eventually reconnect my current cost meter for home power monitoring, sending daily electricity bill via email, graphing and storing stats.  Another use I could put it to is as a WOL client so wake up other machines in the house remotely so I don't leave them powered on all day (not that I do this anyway), but I haven't configured WOL yet.

Not investigated yet but it seems to me it should be possible to run the OpenPeak apps on Linux too.  These are just flash applications so I should be able to run them on the Linux desktop without any issues which would provide me with the same functionality I would get from the original O2 interface under my own Linux.

You can find a lot more of my information about the Joggler at my Joggler Index post. I also have a list of Joggler Bookmarks.

Wednesday 19 May 2010

Joggler Index

This post will be kept up to date serving as an ordered index to my notes about the O2 Joggler; essentially a glorified digital picture frame with a touch screen.  All posts will use the joggler tag too but these may appear in any order.

The very brief tech spec is:
  • Intel Atom Z520 with GMA 500 chipset
  • 512MB RAM
  • 1GB Internal Storage (to run the O2 operating system and interface)
  • 7 inch touch screen
  • USB port, audio jack, wired Ethernet and wireless network
I have a list of Joggler bookmarks.

    Wednesday 30 December 2009

    Upgrading Fedora 11 to 12

    After writing recently about my previous upgrade experience, it seems fair to report my latest upgrade experience going from F11 to F12 using pre-upgrade on the same machine at home.

    Everything progressed very smoothly, even more so than last time as I'm pleased to report the bug I had written about is now fixed. Fedora now detects hardware raid devices and employs the correct work-around solution to ensure the upgrade proceeds unhindered. So far so good then and I thought I would be sailing through to another smooth upgrade. However, it appears even at Fedora 12 level there are still some small issues as it proved later in the upgrade process.

    This time the upgrade was smooth right through to the end of the upgrade process, after all the packages had been installed. Just as the bootloader config was being adjusted I was presented with a rather user-unfriendly Python stack trace with an "unhandled exception" error. By switching to another console I was able to work out the upgrade had in fact completed successfully all except for the final adjustments to the grub menu and removing the pre-upgrade cache. I reported this behaviour in a new Red Hat bugzilla bug report and have been informed this bug has already been fixed upstream in Fedora development and should not occur in pre-upgrade F12 to F13, lets wait and see.

    So it seems the pre-upgrade path for slightly more complicated configurations such as the one I have at home is finally starting to look good. I'm slightly disappointed it's still not quite there yet though but all things considered this was another smooth upgrade and one which someone less informed about Linux might be successful.

    Tuesday 17 November 2009

    Upgrading Fedora 10 to 11

    Writing on the day of the scheduled release of Fedora 12 it might seem strange to be talking about two previous versions. However, I thought I would take stock briefly looking over my shoulder before moving forward with the very latest and greatest.

    I upgraded both my home machines shortly after F11 was eventually released in early June after I had been tweeting about it for some time. Aside from a small problem with my main machine at home, both upgrades progressed seamlessly with the Fedora pre-upgrade tool. I'm a bit more conservative with my main work laptop usually staying 3 months behind the latest release, after eventually finding time to upgrade I've been running F11 on my laptop very smoothly for over a month now.

    The issue I had upgrading my home machine was related to the fact my boot partition is on a (hardware) RAID device. It appears there is a bug in pre-upgrade in this area which I found out after a rare question to the fedora forums. In my experience pre-upgrade is pretty decent these days but beware that it still has some pitfalls such as this!

    After pre-upgrade finishes your box reboots, in this case taking you from your F10 desktop to F11. All in all I've noticed very little difference between the two versions which raises some interesting questions for me, basically summarised by "What's the point in upgrading?". Having noticed very little difference after the upgrade this may well be a question many less experienced users ask too. On F10 my laptop worked flawlessly, I had compatibility with all the apps I need, accelerated 3d graphics with RandR 1.2 support (for easily switching between display devices), printing and some of the more traditionally contentious Linux functionality worked perfectly, namely wireless and suspend. F11 was exactly the same after my first boot into the system, flawless.

    So what, indeed, is the point in an upgrade such as this? For me, I like to stay near (but in the case of my main machine not on) the bleeding edge of development. The upgrade for me was all about getting a few little extras in the Kernel (namely support for hard disk parking which I've not yet played with, and better web cam support) as well as all the little feature additions and bug fixes you get with every library and app you use on your box. The main point though, and the clincher, is that the upgrade process SHOULD be this smooth; these things SHOULD happen without causing any new problems while fixing as many old problems as possible. I'm glad to say F10 to F11 did work like this, it was a breeze, Fedora are getting this right and long may it continue.

    Monday 12 January 2009

    BBC iPlayer Coming to Linux

    BBC iPlayer Logo
    As the BBC recently announced they have developed a version of iPlayer that works on Linux, Windows and Mac: "The BBC, working with Adobe, has developed the new version, known as BBC iPlayer Desktop."

    In a similar way (and name) to Google Labs, the BBC have come up with iPlayer Labs where they will trial the latest beta features for iPlayer before full release to the masses. This brings an exciting addition to current iPlayer capabilities, the iPlayer Desktop. Written for the Adobe Air platform, it works across all the supported operating systems and desktops, bringing the benefits of Air to the BBC developers. I think this is a safe and sensible choice for the BBC and should provide great functionality for we end users along with the slick Adobe interface. The reason this is exciting for Linux users is the desktop version brings the download capability, so no more 2nd class citizen for Linux users as we can now download the higher quality versions of BBC programming. Thanks Beeb!

    If you want to give it a try, go to the iPlayer Labs page, click the link to say you would like to be a labs tester, then next time you attempt to download a programme, you'll be prompted to download and install the Adobe Air iPlayer bundle first. After that, just use the iPlayer desktop app in the same way as your other Air apps.

    Tuesday 12 August 2008

    Byebye Ubuntu, Hello Fedora

    My recent experiments with installing Ubuntu on my little home server came to an end this weekend. I'm working hard to debug problems with my media streamer software, SqueezeCenter. After finding tons of forum posts and various problems with installing SqueezeCenter on Hardy Heron I decided to try another approach so I'm now running Fedora 9 at home instead. Both Hardy and Fedora 9 are supposed to be supported by Slim Devices for their Squeeze-stuff. However, it appears neither of these work but I'll save that rant for another day once I've worked out what's wrong (I have my suspicions about Slim Devices testing against Perl 5.10).

    I'm actually quite relieved to be back in my comfort zone with Fedora at home again. I really enjoyed the experience of playing with Ubuntu but it's just not for me for various reasons...

    I've met quite a few Canonical guys in my professional role and they've all been great; helpful, very approachable and in the case of some, such as Jono Bacon very decent techies too. That's not my experience with non-Canonical Ubuntu contributors though. I found if the Ubuntu documentation (which is excellent for pretty much everything before Hardy Heron right now) failed me, then talking to the community was not a good experience. I found I was met with an abrupt RTFM attitude in most instances, where the assumption of the community is that people asking questions are dumb. Personally, I blame this on the typical Ubuntu user being non-technical where Linux is concerned so I guess the community receive lots of silly questions which must get annoying at times. All that said, I still believe Ubuntu is really important and plays an extremely valuable role in trying to bring Linux to a more mass audience.

    I also found Hardy to be down level in various instances compared with the packages available in Fedora 9. The big one for me here, on my little server, is the OpenChrome drivers for the graphics chipset. Fedora have the version that supports my chipset, but when I asked about inclusion in Ubuntu there was no interest in updating the down level version in their repositories. I also enquired about the broken Via proprietary driver in Ubuntu which resulted in the Via driver being marked for removal! So rather than update the open drivers or fix the package for the proprietary drivers, the response was to remove the proprietary one and not update the open driver which left me in a position of manually maintaining my own graphics driver until the next major Ubuntu release.

    I've used RPM and yum way more than I have deb and apt so I sway towards the former simply through familiarity. Having the chance to play with debs again recently has been great too, there's some nice additional touches you don't get with RPM such as the suggested packages and the ability to remove dependencies installed with a certain package, etc. Ubuntu have done a nice job of packaging this all up with Synaptic too. Aside from those few nice-to-haves I don't really see any other advantages to the Ubuntu system, yum and RPM would do exactly the same job when fronted by Synaptic but as ever in the world of open source having choice and competition is good.

    Hiding root from the general user is a decent idea too, no need for that confusion in a simple desktop environment, and makes it feel a little closer to what people expect from a Windows box.

    Gnome is the desktop of choice for both mainstream Ubuntu and for Fedora so I've been going with that recently instead of my usual choice of KDE. I've been really impressed with Gnome too, for a simple desktop environment it's fantastic but I know if I were to use it every day there would be some features and tools I use regularly under KDE that I would dearly miss. However, I think I've been converted for home use over to Gnome, particularly as KDE is going through turbulent times with their version 4 releases right now. Having everything written in one toolkit is really nice, you can't avoid running GTK and QT apps under KDE but at least under Gnome you have the option of not running QT and sticking with the same look and feel everywhere.

    I hope I managed to stabalise on one distribution soon so SqueezeCenter actually works, I get the feeling that will likely be Fedora 8 in the short term until Slim Devices get their act together for Perl 5.10 if my current thoughts are correct. So for now at least it's goodbye to Ubuntu until the next time I give it a run somewhere.

    Friday 8 August 2008

    Mobile Internet over Bluetooth Part 2

    Following on from configuring your mobile phone for Internet over bluetooth...

    Once you have your device configured, the next thing you need is to connect over bluetooth to some machine to route your traffic for you. I have a laptop with built-in bluetooth and I'm running Redhat Enterprise Linux version 5. You need to configure and setup bluetooth, a ppp bluetooth daemon, and some simple routing to get your phone on the Internet. First off you need to pair your laptop with your phone, there's plenty of info on how to do this around the web and it's simple enough I'll assume you now have a GnuBox configured phone paired with your laptop.

    First off you need to set up Internet Connection Sharing (in windows speak) or IP Masquerading (to anybody who know's what they're talking about), on Linux this is done with iptables. Insert the following rules:
    • iptables -A FORWARD -i ppp0 -j ACCEPT
    • iptables -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT
    • iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
    The last rule for the postrouting chain should point to the interface on your laptop where you have an outgoing Internet connection enabled. In my case this can be either eth0 (the first Ethernet device) or wlan0 (my wireless device, could also be ath0, eth1, etc), so I insert two rules to cover both devices, even though I only show one of these above.

    Enable IP forwarding:
    • echo 1 > /proc/sys/net/ipv4/ip_forward
    With your bluetooth device turned on, and previously paired with your phone, now all you need to do is set up a ppp daemon listening for incoming bluetooth "serial" type connections. This can be done in a couple of easy commands, first to add the serial protocol to your bluetooth SDP server, then to set up the listening daemon:
    • sdptool add SP
    • dund -n --listen --msdun noauth 192.168.1.1:192.168.1.2 crtscts 115200 ms-dns lock
    The second command will start a dun daemon on the command line that doesn't background itself so you can debug your connection if necssary. It will set up a point to point connection between your laptop and the bluetooth connecting device with IP addresses 192.168.1.1 and 192.168.1.2, you can replace these with any addresses you like. It will also ensure the connection is operating at a sensible speed and you should provide a DNS server that will be passed to the device to resolve Internet server names - you can see this from the contents of your current /etc/resolv.conf file.

    Start your web browser on your phone and tell it to connect using the Bt access point you have already configured. On the command line on your laptop you should see something similar to:
        Using interface ppp0
    Connect: ppp0 <--> /dev/rfcomm1
    local IP address 192.168.1.1
    remote IP address 192.168.1.2
    This shows your phone and your laptop are now connected through a ppp serial type connection over bluetooth using the /dev/rfcomm1 device, your phone will have the IP address 192.168.1.2 and your laptop ppp0 device will have the ipaddress 192.168.1.1. Your phone should have 192.168.1.1 set as the gateway automatically by GnuBox and the DNS address will be passed when dund sets up the ppp connection as per your command line options. Once connected, you should be able to browse the web on your phone for free through your laptop!

    As I said, I run Red Hat, which provides for several handy interfaces to help with the setup of Internet over bluetooth from my phone. Here are some further instructions specific, but not limited to, how I've done things on my machine so I everything happens neatly during boot and I don't need to run any commands to set up the connection...
    • You'll want your iptables rules in place when you boot, you can append rules to /etc/iptables.d/ to do this:
      • Add the following lines to a file in /etc/iptables.d/filter/FORWARD/
        • -A FORWARD -i ppp0 -j ACCEPT
        • -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT
      • Add the following lines to a file in /etc/iptables.d/nat/POSTROUTING/
        • -A POSTROUTING -o eth0 -j MASQUERADE
        • -A POSTROUTING -o ath0 -j MASQUERADE
    • Use sysctl to configure IP forwarding at boot time
      • Add (or change) the following definition in /etc/sysctl.conf
        • net.ipv4.ip_forward = 1
    • Register the serial protocol at boot time for your SDP server
      • Add the following line to the start definition after SDP is started in /etc/init.d/bluetooth
        • sdptool add SP
    • Start the dund daemon at boot time with the correct configuration options
      • chkconfig dund on (to start the service at boot time)
      • Create a file called /etc/ppp/peers/dun with the following contents
        • noauth
        • 192.168.1.1:192.168.1.2
        • crtscts 115200
        • ms-dns
        • lock
      • Edit the file /etc/sysconfig/dund so you have the following configuration
        • DUNDARGS='--listen --msdun call dun'
    These settings should be enough that you can connect your phone to your laptop without having to modify any settings or start any services every time you boot. Once all the services are configured and started, and your phone is paired with the laptop, you will be able to connect to the phone's Bt access point to access the Internet any time you're in range of your laptop.

    Friday 1 August 2008

    What Ubuntu Thinks of a TinyTuxbox

    I've been meaning to log some, I think I'll call it... Linux type stuff, to do with the TinyTuxbox for a while. Here's my attempt to look at what Ubuntu makes of this little box.

    First, the CPU (from /proc/cpuinfo):
    processor : 0
    vendor_id : CentaurHauls
    cpu family : 6
    model : 13
    model name : VIA Eden Processor 500MHz
    stepping : 0
    cpu MHz : 498.706
    cache size : 128 KB
    fdiv_bug : no
    hlt_bug : no
    f00f_bug : no
    coma_bug : no
    fpu : yes
    fpu_exception : yes
    cpuid level : 1
    wp : yes
    flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge cmov pat clflush acpi mmx fxsr sse sse2 tm nx up pni est tm2 xtpr rng rng_en ace ace_en ace2 ace2_en phe phe_en pmm pmm_en
    bogomips : 998.77
    clflush size : 64


    The interestingness here comes from the fact we have a 500MHz Via Eden with 128k cache and just under 1000 bogomips which (although it shouldn't be) is often used as a trivial performance metric of a processor. Next, lets have a look at what's on the PCI bus (courtesy of lspci):
    00:00.0 Host bridge: VIA Technologies, Inc. CX700 Host Bridge (rev 03)
    00:00.1 Host bridge: VIA Technologies, Inc. CX700 Host Bridge
    00:00.2 Host bridge: VIA Technologies, Inc. CX700 Host Bridge
    00:00.3 Host bridge: VIA Technologies, Inc. CX700 Host Bridge
    00:00.4 Host bridge: VIA Technologies, Inc. CX700 Host Bridge
    00:00.7 Host bridge: VIA Technologies, Inc. CX700 Host Bridge
    00:01.0 PCI bridge: VIA Technologies, Inc. VT8237 PCI Bridge
    00:08.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
    00:0f.0 IDE interface: VIA Technologies, Inc. CX700M2 IDE
    00:10.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 90)
    00:10.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 90)
    00:10.4 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 90)
    00:11.0 ISA bridge: VIA Technologies, Inc. CX700 PCI to ISA Bridge
    00:11.7 Host bridge: VIA Technologies, Inc. CX700 Internal Module Bus
    00:13.0 PCI bridge: VIA Technologies, Inc. CX700 Host Bridge
    01:00.0 VGA compatible controller: VIA Technologies, Inc. CX700M2 UniChrome PRO II Graphics (rev 03)
    02:01.0 Audio device: VIA Technologies, Inc. VIA High Definition Audio Controller (rev 10)


    Highlights here come from the Realtek Ethernet which is well catered for out of the box by pretty much any major Linux these days. There are also two IDE controllers, USB controllers and an audio controller that are all well supported. It's interesting that most of the PCI devices are provided by the single CX700M2 chipset which I believe is built onto the processor board for the Via Eden's. The one thing from this list that has been a pain in the back side is the graphics controller. It works out of the box both in frame buffer mode and via the open source via unichrome driver called Openchrome. However, Openchrome don't support the CX700M2 board yet (not officially anyway, the code is still in SVN according to the guys I spoke to on their IRC channel) so graphics processing was eating lots of CPU. Fortunately, I found a link to later via drivers at linux.via.com.tw than are available through the official Via driver site where they're still only supporting Ubuntu 7.04 and 7.10. Seems I'm caught in the middle for now, the Via drivers work nicely but will be a pain to maintain until the Openchrome drivers find their way into Ubuntu and I switch back over to them.

    Then there's the memory. For a small box this one has a relatively generous helping of 512MB RAM, some of which is stolen by the CX700M2 for graphical shared memory. Free is currently showing 439MB total memory, 390MB used and 49MB available; swap is 100% free. That's not bad at all considering I'm running Xorg with Gnome, SSH, SqueezeCenter, 2 instances of MySQL (SqueezeCenter starts its own instance), and a Nanobroker with some Perl code to log my Current Cost data. It'll be running Apache soon too as I move towards writing some more web based Current Cost facilities.

    Just in case anyone is interested, here's the list of modules currently loaded into Ubuntu's 2.6.24-19-generic kernel: drm af_packet ipv6 cpufreq_powersave cpufreq_conservative cpufreq_ondemand cpufreq_stats freq_table cpufreq_userspace sbs container sbshc video output dock battery iptable_filter ip_tables x_tables ac parport_pc lp parport loop snd_hda_intel snd_pcm_oss snd_mixer_oss snd_pcm snd_page_alloc snd_hwdep snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd soundcore serio_raw evdev psmouse pl2303 usbserial pcspkr button i2c_viapro i2c_core shpchp pci_hotplug via_agp agpgart ext3 jbd mbcache sg sd_mod pata_acpi pata_via ata_generic 8139cp ehci_hcd uhci_hcd libata usbcore 8139too mii scsi_mod thermal processor fan fbcon tileblit font bitblit softcursor fuse

    I'll spare the full dmidecode output but from this information I can determine it has an AMI Bios version 8.14 released on 03/28/2008. The CPU is listed with, amusingly, Family "out of spec" and 128K L1 parity cache and 128K L2 ECC cache. A single soldered 512MB Dimm.

    I'm still surprised at just how well it matches up to being a standard x86 box, providing all the interfaces you would expect of such a box given its size. Clearly it's never going to be the fastest or have the most memory, but it really does stack up nicely for all but the most intense home serving tasks or gaming. It certainly shows me we can fill most of our computing needs with such a small box and only 8 watts of power. Ubuntu seems no problem for it and it's reported to run Windows XP too. I'll definitely be bearing it in mind next time someone asks me to recommend a box simply for browsing the web, e-mail or a bit of word processing!

    <Edit>
    Memtest86+ shows the processor as a Via C3 Samuel 2 clocked at 498.7MHz, 128K L1 cache @ 2035MB/s, it doesn't detect L2 cache, and shows 447MB RAM @ 367MB/s.
    </Edit>

    Wednesday 23 July 2008

    Next Generation Linux

    The folk following me on Twitter are probably sick of hearing about identity management, the main stay of my work this year. So I was glad to get out of the office last week to present at an IBM conference in London called "Next Generation Linux". A thank you note I received reminded me I should blog about it, always nice to receive those! Next Generation Linux is an event IBM are running in various worldwide locations this year looking at what comes next for Linux for businesses.

    Being a Linux geek working in a software services organisation called Emerging Technology Services and with my contacts I like to think I was the natural choice for the pitch titled "Emerging Linux Technologies". I only had a short amount of time to present a vast field of topics so I narrowed it down to just five topics compelling for business and talked about the following:
    1. Virtualisation
      OK, not strictly an emerging technology as many businesses have already adopted it. But, it was a good opener setting the scene for some of my other topics and allowed the opportunity for me to briefly run through a few virtualisation technologies for Linux.
    2. Cloud Computing
      An exciting name and concept for what is essentially some very well thought out system administration. This technology has always been feasible but it's being made possible now with commodity hardware capable of remote management and some neat software ideas holding it all together. The really novel thing is the way applications can be deployed to run in the cloud environment and the fact we can actually package this up as a solution now. It's the realisation of "On Demand" computing.
    3. Project Big Green
      Green computing is becoming much more of a concern as business starts to run out of room in data centers, power requirements head skywards and running costs steadily increase. Last year IBM announced a re-investment of $1 billion into research towards green computing which gives business the opportunity to cut running costs and jump on the green band wagon at the same time. Green computing is essentially about consolidation of services, allowing spare compute power to be utilised elsewhere, and making sure equipment is environmentally produced and disposed of. It's those three words we hear in all good green campaigns, reduce-reuse-recycle, do it!
    4. Security Enhanced Linux (SELinux)
      One of my specialisms and a topic I could ramble on about for a long time, I'll try to keep it brief. In this short pitch I indicated security is still an issue in 2008 and it can cost you big time if your security is breached. Enter SELinux, an overview of what SELinux is and where it comes from and a comparison with other technologies such as AppArmour is a good start. To get to the crunch of SELinux though, I explain the differences between Discretionary Access Control (DAC) and Mandatory Access Control (MAC) and the ultimate advantages SELinux brings for security.
    5. Real Time Linux
      Real time really is an emerging area with both of IBMs current Linux partners, Red Hat and SUSE, bringing out offerings recently. Real time is built from the hardware up through the OS and in the case of hard real time into the applications too. IBM have certified some particular System X hardware to be real time capable and provide firmware and support for this now. Next comes the Linux piece where some of the firmware functionality removed from hardware must now be implemented in the kernel, there's loads of ways of doing this but to get support for it SUSE and Red Hat take care of that. IBM have also built some enhancements to Java, by introducing a modified garbage collector (Metronome) and providing ahead of time (AOT) compilation while complying with RTSJ, all of which add up to the ability to write real time Java apps - interesting! Now we can offer a full real time system on non-specialised hardware, using a commercially available operating system and a language loads of people can program, backed by IBM through Websphere Real Time. Boy that sounds like an advert, sorry about that, but it is a great idea, very cool!

    This is all very much in brief, if you want to know more then get in touch or leave a comment.

    Thursday 17 July 2008

    Installing Ubuntu On A TinyTuxbox

    With my new toy now in hand the time soon came to get it installed with Linux. At first glance it might appear to be tricky to install given the lack of CD or Floppy drives. However, it boots from just about anything you attach to it whether that's USB, Compact Flash or Network Boot. Setting up a one-time PXE server seemed a little over the top so I was planning to boot from a USB stick until I found someone at work with a USB CDROM.

    Ubuntu IconUsually I like to run Fedora at home, it's the thing I'm most comfortable with having spent my career tinkering with Red Hat and SUSE based distributions so one of the things I wanted to do with this box was install the much hyped Ubuntu distribution. This wasn't to see what all the fuss is about (I'm familiar with Ubuntu having tried it a couple of times before but always gone back to Fedora) but really just so I can get to know it even better. This machine is going to be part desktop and part server so Ubuntu kind of makes sense too.

    I installed the hard disk into the box myself and once I got over some initial hardware niggles (that I caused I should add) the installation was simple. Boot from USB CDROM with the Hardy Heron CD in it and the rest is history. It's amazing how such a small box can run a full whack desktop operating system and do all that on just 8 watts.

    In these early days, I have three things in mind for the box. The primary use will be to serve my music collection to my stereo; next is to connect my current cost meter to allow some more in-depth analysis of our power usage at home; then there's simply using it as a desktop for the simpler day-to-day computer usage i.e. browsing the web.

    Setting up the music streaming was pretty easy after transferring my collection to the hard disk. I added the apt sources for the SqueezeCenter software that operates with my SqueezeBox Duet, did an apt-get update and an apt-get install squeezecenter and job done. The TinyTuxbox can much better cope with running the MySQL server this is based on along with the web front end and the music collection scanning services associated with the software than the SLUG I tried previously. All in all, couldn't have been much easier.

    I've not tried hooking up my current cost meter yet, ironically I've run out of power sockets near the computer with only a six-way adapter and plugs for the PC, TinyTuxbox, Printer, Monitor, ADSL Modem Router, and speakers although it shouldn't be a hard problem to rectify.

    Last of all, one of the additional benefits of this low-power box is every day usage. It can easily run a web browser so instead of starting up a large PC just for this, we can switch to the TinyTuxbox desktop and browse there. This should add to our power saving, even though it's likely the TinyTuxbox will be run all the time soon to serve the current cost data. That reminds me, I really should discuss batch-uploading of current cost data so I can save even the 8 watts the TinyTuxbox uses most of the time too.

    Wednesday 18 June 2008

    New Thinkpad T61p

    Gutted! A couple of weeks ago now I had a bad Friday, the train home from London where I'd been working with a customer all day was stupidly late and I had to change twice instead of going directly home. Then I get home and fire up my laptop to send the e-mail's I'd written during the day and the darned thing didn't work, argh! Seems in spite of working all day, my T41p had died on the trip home. After reporting the problem at work the following Monday it was decided the T41p needed a new motherboard and this wasn't economical to fix, so I was issued with a shiny new T61p a few days later.


    I've been pleasantly surprised by my new laptop, I wasn't expecting great things since IBM sold the Thinkpad business to Lenovo but this thing is actually quite nice. I'll spare listing the full gory details to the technical specifications page. However, it has some nice additions over my previous laptop, namely built-in firewire (not that I'm likely to use it), built-in SD card reader (used that already), an extra USB port (always handy), a DVD writer, a hardware wireless off switch (presumably for use in planes), an enormous hard disk (compared to the T41p anyway), and a lovely 15.4" widescreen capable of 1920x1200 backed by a 256MB NVidia graphics card.

    Unfortunately, it came pre-installed with Vista so that (along with the stupid Vista sticker next to the keyboard) were the first things to go. I've installed Redhat Enterprise Workstation 5.2 on it which may sound like an odd choice, but IBM have a layer of software designed to sit on top of Redhat to enable us to install things like Lotus Notes, Sametime, etc. This is known as the Open Client internally and works really nicely. Clearly, there are later and greater distributions I could use but on this issue I like to support IBM and the internal community of Linux desktop users so I choose to go with the officially provided solution.

    I've been up and running for a week now with no problems so far, I've been able to do all the things I could do with my old laptop and all the things I need to be able to do in order to do my job. Of course, I make some modifications to the way things work to suit my tastes (such as running KDE instead of Gnome) but all these work well too which is a great reflection on the modular nature of all things involved with Linux. I hope I continue to be surprised and pleased with the machine, and I'm definitely surprised at the ease of transition between the two machines for me.

    Tuesday 3 June 2008

    Showing Off Linux

    Thanks to Ian Hughes for the picture on his flickr. Yesterday, at work, the Hursley Linux Special Interest Group ran a little trade show type event for a couple of hours after lunch. The idea was to provide a bit of away from your desk time for folks around the lab to see what we Linux geeks have been getting up to. Various people interested in using Linux inside and outside work came along to demo their gadgets.

    The picture shows me showing off my old Linux audio centre. But, also at the event were the main organiser of the day Jon Levell (showing Fedora 9 and an eeepc), and Nick O'Leary (showing his N800 and various arduino gadgets), Gareth Jones (showing his accelerometer based USB rocket launcher and bluetooth tweetjects), Andy Stanford-Clark (showing his NSLU2 driven house, and an OLPC), Laura Cowen (showing an OLPC), Steve Godwin (showing MythTV), and Chris law (showing Amora).

    I thought it was quite a nice little selection of Linux related stuff to look through for the masses of people turning up, plenty of other things we could have shown too of course. The afternoon seemed very much a success, generating some real interest in the various demo items and lots of interesting questions too. Thanks to everyone for taking part!