Skip navigation

My TrimSlice Pro arrived today, so of course, I have to do the unboxing ritual.

TrimSlice Packaging


The cardboard box inside


First opening the cardboard box


Mains Adapter


Audio!


Bluetooth Adapter


Serial!


HDMI to DVI adapter


Wifi Antenna


The User's Manual


The TrimSlice itself


The Back of the TrimSlice


View of the right side of the case


The Front of the Trimslice


The Left side of the case


The Bottom of the TrimSlice

Okay, so now that the pictures are out of the way…
I’ve had the dev-kit for a while now, and I’d say, if you have 320 dollars to spare, and want a dual core ARM, and are a *developer*, this isn’t a bad deal. If you are a home user/end user, and want… flash/skype/purple ponies/perfect video/audio/whatever, don’t get it. The software support is being worked on hard, but it’s definitely not at an end user stage right now.

One thing to note, while the die cast case helps to dissipate the heat… this causes it to get *very* hot. It does have 4 rubber feet on the bottom though which cause it to be raised so it’s not just a “hunk of metal” sitting on your desk.

If you happen to have Windows 7, and it craps out on you like mine did (Power outage, when it attempted to boot it would simply say Disk read error, Press Ctrl+Alt+Del to restart) then in order to fix it, you just need to run the following command from the Windows 7 DVD (or USB disk if you happen to have it written to a USB key)

bootsect /nt60 c: /mbr

Once I did this, that machine was back in action. And it only took me two weeks or so in order to get around to it.

In a thread on the NetworkManager mailing list explaining why a dbus-python script wasn’t working, Dan posted this tutorial, and I thought it was a good one, and should go out to a bit of a broader audience. (This is copied verbatim from the email, no spell checking or such – again, I did not write this, I am merely posting it here for others to consume)
Read More »

Thanks to Jeremy Olexa (aka darkside) I now have 2 new Atheros based cards.

One is a Belkin N1 Wireless Notebook card, Part #F5D8011 – ath9k based, although I’ve gotten it recognized by the kernel and I can get an IP address via dhcp, as well as connected via WPA2, I can’t seem to pass traffic.
Two is a Buffalo AG54 WLI-CB-AG54L, this one seems to be ath5k based, although I haven’t attempted to use this one at all yet.

Currently towards the bottom of the todo list, is to get these both working, preferably using the N1 as an access point, so I can test out the speeds of the Efika MX’s wireless. This has a secondary goal of seeing if the wireless issue that I have (currently I cannot seem to ssh into any wireless clients) is the AP I am using (pfSense based) or if it is something more; I’m guessing the former.

While working on the Gnome overlay with the Gnome team, I decided to give Empathy a go.  I talk to maybe 3 total people on AIM, and no one on Yahoo, which just leaves me with Jabber (Gmail) contacts that I actually talk to.  So I installed it, I even enabled webkit so that I could use Adium themes with it (I personally prefer Stockholm, just be sure to look inside the folder and only move the style into the right place.)

It was kind of a disaster.  I’m running on a Quad Core, 2.4ghz machine, and double clicking on a contact would take up to 25 seconds for the window to show up.  I was not a happy camper.  Watching htop, I could see that my DBus session bus was working hardcore.  100% cpu usage on 1 core.

No problem, I thought to myself, whipped open my handy terminal, ran “dbus-monitor –session” to watch the traffic that was causing it to use so much cpu and…. nothing.  Zilch.  There was no (apparent) traffic going on but the session bus was still using 100% cpu.

I popped over to the Gnome bugzilla, and started reading through bugs, but none were coming close to what I was seeing.  In desperation, I turned to the faithful Google.    And I searched… and came up empty – not so much empty as simply results that weren’t helpful at all.

I let it go for a few days, asked a couple people if they were having any issues, and most don’t use Empathy, so that was a bust.  Then I was looking around while I was “at work” which really meant I was sitting in the office as opposed to my room using the computer, and I came across Bustle; http://willthompson.co.uk/bustle/

Bustle is very nice, in that it can show you timings.  Once I had that compiled, I used Recordmydesktop to take a video of me using Empathy, with Bustle running, logging everything that went on with Empathy.  Then I popped in to the Empathy IRC channel (#empathy on irc.gnome.org) and mentioned in the channel that it was taking a long time for my IM windows to open, and pointed them at the video ( http://dev.gentoo.org/~steev/files/empathy-dbus.ogv (21MB)) and then at the two screenshots of Bustle ( http://dev.gentoo.org/~steev/files/screenshots/empathy-bustle1.png andhttp://dev.gentoo.org/~steev/files/screenshots/empathy-bustle2.png ), and Danni replied to me, asking why I was using the logger, when it shouldn’t be enabled.  So I disabled it, and removed telepathy-logger from my system, re-compiled Empathy, and sure enough, the IM window pops up instantly.  I’ve removed the dependency as well as got rid of the useflag (with a note in the ebuild about why) and committed it to the Gnome overlay.  Due to Danni saying that no one should be using telepathy-logger, I’ve also package.masked it in the Gnome overlay.  I must say, using Bustle is *very* nice, and I’d like to thank Will Thompson for writing it.

I also smiled at the “How?” section of the Bustle website, considering that was the exact purpose for me downloading it.

I’m hoping to write an ebuild for Bustle, and apparently it is really easy to do with Haskell as the Gentoo Haskell team has a script that you run that will write the ebuild for you.  I haven’t started working with it yet, but I definitely plan to, as Bustle is now definitely on my radar for usage in debugging what is going on with apps and their DBus usage.

Client Reason Code…Description…Meaning
0…noReasonCode…Normal operation.
1…unspecifiedReason…Client associated but no longer authorized.
2…previousAuthNotValid…Client associated but not authorized.
3…deauthenticationLeaving…The access point went offline, deauthenticating the client.
4…disassociationDueToInactivity…Client session timeout exceeded.
5…disassociationAPBusy…The access point is busy, performing load balancing, for example.
6…class2FrameFromNonAuthStation…Client attempted to transfer data before it was authenticated.
7…class2FrameFromNonAssStation…Client attempted to transfer data before it was associated.
8…disassociationStaHasLeft…Operating System moved the client to another access point using non-aggressive load balancing.
9…staReqAssociationWithoutAuth…Client not authorized yet, still attempting to associate with an access point.
99…missingReasonCode…Client momentarily in an unknown state.

Just posting it here for future reference

So I was going through some of my backups, because I accidentally blew away my Linux partition on my desktop when attempting to do something silly, and I came across an old AIM screenname that I used to use, and hadn’t for a while… So since I was bored and waiting for things to install, I started going through my buddy list reading the various names and remembering the people behind them… and I noticed that AIM has a Member Since: line… Here is mine:

Member Since: 1/7/1998 5:24:26 AM

So, I failed to backup my gpg keys, and I am just now noticing… So, since there was a new improved version of Seahorse released a while ago, I decided to try it out again. First order of business was making a key that actually expires… and that has a revocation certificate (and backed it up!)

So from now on, if you want to contact me, please use key ID 0x564F6F68. If you click the more link, you will get the asc version of my public key as well. If you prefer to get it from a keyserver, Verisign has a spiffy web front end to their keyserver, located at
http://keyserver.veridis.com:11371/
Read More »

Okay, so this may not be news to anyone else – but I just discovered it earlier when looking something up…


steev@setsuka ~ $ eix virtual/cdrtools
* app-cdr/cdrkit
Available versions: 1.1.6 {hfs kernel_FreeBSD kernel_linux unicode}
Homepage: http://cdrkit.org/
Description: A suite of programs for recording CDs and DVDs, blanking CD-RW media, creating ISO-9660 filesystem images, extracting audio CD data, and more.


app-cdr/cdrtools
Available versions: 2.01-r1 2.01.01_alpha25 2.01.01_alpha34 (~)2.01.01_alpha36 (~)2.01.01_alpha36-r1 {unicode}
Installed versions: 2.01.01_alpha36-r1(01:30:17 01/06/08)(unicode)
Homepage: http://cdrecord.berlios.de/
Description: A set of tools for CD/DVD reading and recording, including cdrecord

Found 2 matches.

I get asked a lot of times when I am doing things, how I did it – a lot of times they are Google searches with very specific keywords, however there are a few documents I always keep around in my bookmarks…
Writing udev Rules from dsd – this I would say is pretty much the definitive guide for writing udev rules – while it isn’t exhaustive, it does cover everything you would need to write your own. This isn’t Gentoo specific either – any distro that uses udev can follow these instructions!

I have a few machines, once in a while, I will do a clean install, and when I do, I always read the Gentoo Linux x86 with Software Raid and LVM2 Quick Install Guide – While I have been using Gentoo for the better part of 5 years, I am getting… uhh, older… and sometimes those little things slip through – so even though I don’t need to constantly read it – I always double check after I’ve done everything just to be sure I’ve gotten all the bases covered – nothing more annoying than rebooting into your amazing new clean install and having forgotten to emerge grub so it doesn’t boot! Yes, I will admit that I’ve done it (more than once!) but that is neither here nor there.
Gentoo Security Handbook – I don’t think I really need to explain why I keep this one bookmarked – always a good thing to have. While I won’t link them, the Infra documentation on hardened servers is also very good and easy to follow and understand what/why things are done the way they are.
Gentoo Linux Cron Guide – The question often comes up – which cron should I use? This guide is very good at explaining some of the differences between a few of the implementations available in Portage, and guides the user through the various installations and how to use cron as well.
GCC Upgrading Guide – This is pretty much a must-read as a Gentoo user/system administrator/developer – there are times where an upgrade is non-trivial, and this documentation is always good to follow when there is an upgrade available.
How to get meaningful backtraces in Gentoo – Another essential guide – if you are having an application crash on you, it is likely a developer will want to see a backtrace – this guide walks you through getting something that is actually meaningful.

While these documents may be talking about Gentoo for the most part, they are easily converted to another distro – definitely recommend checking them out at your convenience, and bookmark them, as they may be called up multiple times. If you don’t want to keep them bookmarked on your machine (since you are always out and about…. right? right!?) you can always use a service like diigo which is what I use personally (and any time I add a bookmark, they get posted here to my blog as well so I can find them without surfing over there), del.icio.us which is also a great site, however I no longer use it because I used to use an irssi script that posted all urls posted on IRC to it…. okay if you are in a few channels… not so good when you are in 20+ ;)
And a newcomer of sorts – Mozilla Weave – which requires Mozilla Firefox 3.0 (which is currently in beta or nightlies only) any basically allows you to sync all your settings to their servers, and when you login to another machine with Firefox 3.0, you can sync your settings down from there and have them. There are other things planned for it – and there are already addons for doing the same thing for Firefox already.