Mobility Devices

I’ve been meaning to do a post with details of all the small devices I have. Not all the devices pictured below currently run Fedora although nine out of the twelve shown either currently run Fedora or I’ve had them boot Fedora. The three devices that don’t, as yet, boot Fedora are devices 8, 9 and 11. There’s no reason why they can’t as they all run some form of Linux, in the case of 8 and 11 its Android and 9 is a Logitech SqueezeBox Touch.

One of the things that I’ve been trying to achieve in Fedora for many years is slimming of the required dependencies of certain combinations of installs. Not everyone needs everything, and not everyone has Terabytes of storage that can be thrown about.

So what are all the devices above. I’ll go through each one and give some details of each:

  1. OLPC XO 1.75: 1Ghz ARMv7 Processor, 512Mb RAM, 4Gb eMMC storage, GPU Unknown
  2. OLPC XO 1.5: 1Ghz VIA C7 Processor, 1Gb RAM, 4Gb microSD storage, VIA VX855 GPU
  3. OLPC XO 1.0: 433Mhz AMD Geode Processor, 256Mb RAM, 1Gb Flash storage, Geode GPU
  4. Nokia n900: 800Mhz OMAP3 A8 ARMv7 Processor, 256Mb RAM, 32Gb eMMC storage, PowerVR SGX530 GPU
  5. BeagleBoard XM: 1Ghz OMAP3 A8 ARMv7 Processor, 512Mb RAM, 8Gb microSD storage, PowerVR SGX530 GPU
  6. Fit-PC 1.0: 500Mhz AMD Geode Processor, 256Mb RAM, 40Gb HDD, Geode GPU
  7. O2 Joggler: 1Ghz Z520 Atom Processor, 512Mb RAM, 2Gb Flash storage, GMA-500 Poulsbo GPU
  8. Orange SanFrancisco AKA ZTE Blade: 600Mhz Qualcomm MSM7227 ARMv6 processor, 512Mb RAM, 150Mb Flash, Adreno 200 GPU
  9. Logitech SqueezeBox Touch: 600Mhz ARMv6 Processor, 128Mb RAM, 128Mb Flash, GPU Unknown
  10. Toshia AC100: Dual Core 1Ghz Tegra 250 A9 ARMv7 Processor, 512Mb RAM, 8Gb SSD, GeForce ULP GPU
  11. Samsung Galaxy Tab:1Ghz Samsung A8 ARMv7 Processor, 512Mb RAM, 16Gb SSD, PowerVR SGX540 GPU
  12. Asus EeePC 901: 1.6 Ghz Atom Processor, 1Gb RAM, 4Gb Primary SSD, 16 Gb Secondary SSD, Intel G450 GPU

All the devices have WiFi, some have wired Ethernet, some 3G, GPS etc.

There’s two main issues with smaller “mobility” devices. Firstly is the GPU support is obviously a mixed bag, there’s obviously AdamW’s favourite GPU… the Poulsbo on the Intel Z5xx series atoms. The Poulsbo is basically a variant of the PowerVR GPU’s that Intel licenese. Unfortunately this is still basically the case for the new Z6xx series which contain a GMA-600 Poulsbo device. Buyer beware! Its been leaked this week that Intel for later generations isn’t going to improve the situation as they just going to use the PowerVR GPU directly.

The other issue is storage. Most of the devices just don’t have that much of it. This is why I spend so much time filing bugs to split out dependencies. While you can install the standard desktop into 4Gb it doesn’t leave that much for things like yum updates or fun things like music ๐Ÿ™‚

gnome 3

Well the new gnome 3 has certainly polarised the community. I must say I generally really like it, but also I’m not yet running it on my default machine. Historically I’ve upgraded my primary laptop to the current development release of Fedora around the beta release. This time I’ve not. Why? Well there’s one major feature that has “Just Worked” for me for as long as I remember and I use it every day I’m in the office that isn’t yet working well in gnome 3 and it would cost me way too much time on an average work day.

I have a Dell Latitude E-Series laptop with a docking station and a second screen. Pretty much everyone in our 300 person office has this config. People use them all a different ways. Side by side, stacked on top of each other, laptop closed with one screen etc. Some Gnome 3 just doesn’t work well with dual screens in a dock evironment yet. On Fedora 14 I can undock the laptop and head off to a meeting. When I undock all the windows collapse down onto the laptop screen. When I redock it detects my second screen is back and all my windows go back to the way they were. At the end of the day I suspend my laptop and go home, it works, when I return the next day it returns them as I had them. On gnome 3 the undock generally works well most of the time. The redock doesn’t. It doesn’t turn on the screen, reconfigure it as a second screen and put all the windows back on there. To get my windows back to the way I had them takes a good 5 mins of moving stuff around. Do that ten times a day and it adds up to quite a bit of wasted time that I just don’t have! Chatting with Jon McCann at RedHat Summit he mentioned it was likely a gsettings (I think from memory) problem and should be easily fixed (I will test patches!).

But there are things I love in gnome 3 and I would love to move to it permanently. The new evolution 3 is lovely! Our office uses Exchange as its corporate collaboration system. evolution-mapi allows me to do all the email/contacts/calendaring within Fedora generally without too much issue. v3 adds to that and evo 3 works pretty well! To get this lovely in the office while retaining my dual screen functionality I run a lvm VM on my laptop with F-15 and have evo running over a X session to the main F-14 desktop.

There’s lots of other nice things about gnome 3 and I look forward to being able to run it properly to get access to those things. There’s other regressions I know, and I can live with those. WPA Enterprise support (which again we use through out all out offices in Europe) has work arounds, the timezones in the clock I’m reliably informed will be back in gnome 3.2, people are working on gnotes and there’s a gnome 3 plugin for pidgin flying about (I would move to empathy when I can import my 5 years of logs that I use daily for reference). Those are minor, it was a massive change and there will always be regressions. I look forward to decent dual screen support again soon ๐Ÿ™‚

More thoughts on the Fedora Feature Process

This is the second release running that another component of the Fedora Feature process has come and bitten me in the proverbial. This time its the “Major Features”(tm), must be landed by the Alpha release, part of the process.

For Fedora 14 the feature that abused this requirement was python 2.7. Rather than landing by the Alpha release it landed moments before we locked down for the Beta breaking things horribly and causing massive amounts of work post Beta when we were suppose to be stabilising the release. This affected Sugar amongst massively as that’s the language its primarily written in.

For Fedora 15 the abuse was by NetworkManager. Complete API borkage with very little notification (well at least that I saw) moments before the Beta release. Unfortunately again its Sugar that takes the hit and it looks like we’re not going to have it working by release. I’m doing my best to attempt to teach myself python to hack up some form of support but given I’m just learning python converting a network stack isn’t the easiest of things, and work seems to get in the way at the least opportune of moments.

I don’t want to blame developers. Everyone has different agenda’s and issues that they try and balance but what really pisses me off is that its not in by the alpha, or if its going to be massively late there needs to be a lot more heads up or assistance. BTW Massive big kudos to the Evolution developers for getting this pretty close to right for both the F-14 and F-15 releases as they were going through huge API changes. If that’s not going to happen then FESCo or The Board or whoever is in charge of developing the “feature rules and policy” actually needs to bloody well enforce them and say “sorry it needs to go in the next Release”. They do after all have all the way back to alpha of the previous release to land the feature (that was the whole purpose of forking rawhide at alpha and not later in the process) and have all the breakage they like. It gives six months for poor mugs like me to either, organise other busy upstream developers to help, or to work out how to code in python myself to fix it, rather than what seems like six days to attempt to scratch something together. It won’t be popular but maybe a single high profile incident will make everyone step back and think about others and how they may affect them.

With the upcoming FESCo and Board elections I look forward to what people have to say. Why not run for them yourself I hear you say? I’d personally love to but unfortunately with a number of other things going on in my life at the moment I don’t have the time. Either I would have to drop all the package and Sugar/OLPC stuff I’m currently doing to make enough time for it, becoming again a pure Fedora consumer, or remove all traces of the scant personal life that I currently have. I don’t currently wish to do either.

Cheap hardware to get involved in Fedora ARM?

For Fedora people that are interested in getting involved with the ARM secondary arch you can currently get a Pogo Plug from CompUSA for a smidg under 60 greenbacks. In hardware specs, its pretty much a SheevaPlug in pretty clothing, so its well supported on Fedora ARM. There should also be some nifty improvements soon to make it even easier to use Fedora on ARM devices thanks to some cool projects by students at Seneca College for kernel build rpms!

Voting….

Well in the vote for naming for Fedora 16 I’ve voted for a Beefy Miracle ๐Ÿ™‚

Having known of the Hot Dog for a while it wasn’t until FUDCon Tempe the fan base he has!

In other voting news Red Hat has announced the finalists for their 2011 Red Hat Certified of the Year Finalists. I’ve been nominated as the Finalist for the EMEA region continuing a fine Fedora tradition. I would appreciate your vote so the Fedora tradition can continue. So follow the link and cast your vote there as well (it takes even less time than voting for the release name!) and if I happen to be fortunate enough to win I’ll be at the Red Hat Summit continuing to where the Fedora hat ๐Ÿ™‚

FUDCon Day 1

Wow what a busy day! We started off with BarCamp pitches followed by the FPL traditional “Fedora State of the Union” talk from Jared.

The first BarCamp I went to was the Fedora on ARM including an update of OLPC on Fedora from Martin Langhoff. Very interesting and there was a lot of interest in my Toshiba AC100 SmartBook running Fedora 13 ARM on the nVidia Tegra250 dual core ARM A9 processor.

Lunch was very interesting. All the people involved in Sugar on Fedora got together for a chat about what everyone was up to and how things were working, and a quick discussion as to what different parties saw from Sugar on a Stick and whether it was useful. The people in attendance (from memory) were myself, Sebastian Dziallas, Mel Chua, Simon Schampijer, Martin Langhoff, Stephen Parish, Bernie Innocenti, Dennis Gilmore and Samuel Greenfeld. It was good to chat face to face about the requirements and challenges of Sugar in Fedora and the various requirements of Fedora, OLPC, SugarLabs and third party users like the Dextrose crew. There were many other hallway chats about various Sugar related things including with Adam Williamson and Samuel for QA related testing of Sugars and associated components, and with Martin about XS Server related things. The whole day was very sweet (pun intended!) with Sugar related discussions. Of course the discussions didn’t stop there and continued into the evening at FUDPub.

After lunch I attended the Education รผbertalk which was very interesting about various means of teaching open source from Mรกirรญn’s teaching of design and graphics through open source applications, to ctyler’s 15 minutes on teaching open source at universities and how that’s allowed them to use Fedora as a showcase of a release process because its all open, and of course Mel and Sebastian’s slot of POSSE. All very interesting and very different takes on getting open source out there.

I managed to make it to Mike McGrath’s talk on cloud, although I didn’t make it to enough cloud related talks over the weekend, because as always there seems to be way too many cool things to attend and way to many conflicts!

The discussion about Fedora Spins and the future there of was also very interesting. Its something that’s been long over due and while we didn’t have enough time to get through all the required bits to discuss I feel that we got enough of the root ideas out and discussed and noted down to be able to take the rest of the discussion to the lists. I was very interested in this and in time there should be some nice improvements to enable some improvements to the way the spins process that should greatly help both the Sugar and possible future MeeGo spins.

In the evening there was the traditional FUDPub. And what fun it was too. Although I do place the blame for how I felt the following day on Martin and Simon for moving me from drinking beer to Cuba Libre’s and big ones at that!

FUDCon Day 0

Having arrived in Tempe for FUDCon late on Thursday evening having been in transit for close to 24 hours it was great relief to meet up with Mel and Sebastian at the hotel. After a great nights sleep, except for a massively sore neck, it was great to get up on Friday morning to find people starting to arrive and the office hallway track begin to take shape.

I went out in the afternoon to get out and about from the hotel and see a little of the surrounding areas. By the time I got back a huge crowd had started to gather and it was good to catch up with adamw, jsmith, dgilmore, pfrields and many many others.

FUDCon officially started with the first birthday party of OpenSource.com with beers, pizza and cake provided them to assist the conversations and celebrations.

FUDCon Tempe

Well its not long before I’ll be jumping on a plane to head over the pond to Tempe, Arizona to the latest and greatest FUDCon. This will be my forth FUDCon event. I always enjoy them. Its lots of fun catching up with friends and fellow contributors who’ll no doubt become friends. There’s always one thing I really don’t like about FUDCon…. its that there’s always too many awesome topics of discussion and sessions that I want to attend but they conflict with other sessions that I want to go to ๐Ÿ™‚

So what do I want to discuss and see discussed at FUDCon Tempe? Well as per usual there’s lots so here’s a quick bullet list:

  • Fedora Mobility: How to take it forward and who wants to achieve what, and how we all go about it. As devices get smaller and every company and their dog release tablets I think mobile devices will become more key to Fedora. It also fits in very well with a number of the Fedora Board Long Term Goals in particular I think it fits well for the help people control their content and devices and the Access from anywhere strategy.
  • Sugar, OLPC and Sugar on a Stick: there’s going to be quite a few people from various OLPC and Sugar projects in attendance. Also the awesome adamw and the Fedora QA team is going to be there so there’s plans to extend the discussions we started at FUDCon Zurich. The OLPC project is arguably the largest deployment of devices based on Fedora. The OLPC OS that runs on their XO laptops is pretty close to a vanilla Fedora release and as the last of the XO kernel patches make it upstream you can run vanilla Fedora on them with few issues.
  • Fedora ARM and secondary architectures: dgilmore, ctyler, PaulW will (I think) all be there and Fedora ARM is really starting to amp up with their awesome work! This also crosses over somewhat into OLPC and is hand in hand with Fedora Mobility. I suspect the discussions will revolve around getting Fedora 14 and rawhide building, ARMv7 + hardfp builds and ensuring ARM becomes a solid secondary arch.
  • Cloud: This sort of stuff is part of what I do for my $dayjob and it interests me greatly! I just wish I had more time to contribute to the SIG.
  • MeeGo Netbook UX: yes, this was a big FAIL for Fedora 14 and I need to blog on this. Looking much better for Fedora 15. Watch this space!
  • IPv6. There’s been some interesting posts on using IPv6 with various ISPs with that other Linux based desktop OS. Why isn’t there the same for Fedora??
  • Friends: One of the big ones of the four F’s of Fedora.
  • There’s always lots of random hallway discussions.

There’s no doubt a number of things that I’ve missed. The other thought I have is what of my Mobility tech toys to bring along. I have my laptop obviously. My atom based netbook running MeeGo Netbook UX on rawhide, my XO 1.5 running Fedora 14, my Toshiba AC100 running Fedora ARM 13 but I don’t think I can pack 4 laptop/netbook devices ๐Ÿ˜›

Fedora ARM on the Toshiba AC100 Smart Book

I finally sat down on the weekend to try and get some OS other than Android running on the Toshiba AC100 I bought off ebay on a whim. The AC100 doesn’t look that different to your average 10.1 inch netbook except its extremely thin and and light and on the inside it has a Nvidia Tegra 2 SoC based on the dual core ARM Cortex A9. My initial plan was to get Ubuntu running on due to the instructions about doing that to be found on the net. After doing some reading and while part way through the process I decided that I would try Paul Whalen’s Fedora 13 ARM rootfs instead as the process of creating a linux rootfs is similar across all distributions! There’s still quite a way to go. For starters its currently a very base system and its currently running a 2.6.29 kernel for ubuntu based on the code released by Toshiba but its a start. Over the next couple of days I plan on getting networking up and from there X plus gnome. Once I’ve got that done I’ll put up a more defined process and add the details to the ARM wiki devices page.