Jerry Springer + Congress = Awesome
If US Congress was more like Taiwan's Parliament, I think many more people would be interested in politics.
Stupid Motherboard
Ok, this is retarded. About 2 years ago, I bought a DFI K8M800 MLVF motherboard to act as the foundation for my HTPC/PVR box. This was before I had my 6.1-channel sound system, so at the time, I was ok with the onboard VIA 8237 sound chip, which, without buying an extra connector bracket, would more or less just give me 2 channels.
However, after setting stuff up, I had no sound. I was not pleased. I googled and googled, and found that the ALSA driver for that chipset (snd-via82xx) was a little messy, and sometimes you had to pass special parameters to the driver to get it to work for your particular hardware. I tried a bunch of combinations, but had no luck. Eventually I gave up, and bought a cheap Turtle Beach card. By that time, I'd bought my surround sound system, and wanted something that could do digital S/PDIF out (though this card only does coaxial, not optical, but whatever).
Lately I've been thinking about reducing power usage on the HTPC, with the possible intent of retiring my desktop machine and moving all the data to the HTPC on a RAID array that I'd build and put in an external box using something like eSATA. I'd also need to free up a PCI slot: even though I'm only using 2 of the 3 slots, the 3rd slot is effectively blocked by the large fan on my AGP video card. So, I thought it would be a good idea to try to get the integrated sound working again.
So, I resumed googling, and messing around, and still, no luck. Tonight, I decided to google my specific motherboard. This led me to the ALSA bug tracker, where I put in a broader search query for all bugs related to the via82xx driver where there was no sound. With a little luck, I came across a post that said something about having disabled the rear outputs in favor of the front outputs on their multimedia-oriented case.
This rang a bell.
I dug out my motherboard's manual, and, sure enough, connecting the front in/outs on a case to the appropriate header on the motherboard will disable the rear outputs. Of course, I'd never done this, as I hadn't cared about the front audio jacks. But I thought I'd look anyway. Apparently, two pairs of pins on the header need to be shorted if you don't intend to use the front outputs. Otherwise the rear outputs still get disabled. You'd think that DFI would ship the motherboard with these pins already shorted, since you'd want to get some sound out of the box if you don't go and connect anything to the front outputs. But no, I see the header, plainly sitting there with its pins un-shorted. So, I dig out some jumpers, short the pins, boot the box, load the driver, unmute the mixer channels, and... voila... I have sound.
I can't believe the amount of time I wasted on this, and it turned out to be a hardware problem in the end! I was so afraid that it was a Linux software issue, and it was actually hardware. Sigh.
Time to go order that S/PDIF bracket...
Patented Farts
Those guys over at United Aircraft really take their flatulence seriously.
Stupid Words
I'm very curious as to where the words "orientate" and its opposite, "disorientate," came from. They sound incredibly stupid. What was wrong with "orient" and "disorient?" Fewer letters, and you don't sound like a retard when you say them. Dictionary.com even says that the longer versions just mean "to orient" and "to disorient." Everybody wins when you use the shorter form. Using the longer form means you like to kill puppies.
Rejection
From The Examiner:
Lots of schools are vying for the “most emphatic rejection” prize. Cornell is leading the race, informing students in consecutive sentences that the electronic rejection they are reading will be confirmed in a follow-up letter that will make the rejection official. We don’t want you. Get it? We really don’t want you. The “snuff out all hopes” double rejection strategy appears to be colleges’ latest attempt to improve their U.S. News & World Report selectivity rating. Two rejections for the price of one. What tipped the scale in Cornell’s favor is that they even include an invitation for you to visit their Web site to get information about applying to transfer to Cornell after your freshman year, so they can reject you again.
Awesome. Absolutely awesome. My alma mater never stops entertaining me.
Open Phones
Screw you, iPhone. I want one of these.
I stumbled across a blog post about the OpenMoko platform today. I'd heard of it before, but never really looked into what it was.
I'm not sure I'm quite ready to give up my insistence on a small flip-phone in favor of a more multi-function device, but if I did, this would be what I'd want. Sadly, I'm afraid it won't gain much traction in the US without some kind of deal with a major wireless carrier. US cellular customers aren't used to buying a phone, and then later finding service for it. Hell, most US cellular customers aren't used to buying a phone, period: the phone comes free (or at a very low cost) with a service contract.
And the carriers won't like this phone. The end-user can modify any aspect of the software that runs on it? That's a big no-no. The carriers love their closed systems, and love controlling what you can and can't run on the phone.
But still, I remain optimistic. It might start out as a geek toy, but that's how most popular tech advancements begin to enter the mainstream.
I'll definitely be keeping tabs on OpenMoko to see where it goes.
Back from CeBIT marathon
I just came back from my CeBIT marathon (i mean my one day trip to CeBIT). The first word that comes into my mind after visiting CeBIT is “_HUGE_”. This event takes place into around 23 showrooms, each of them big enough to host an entire commercial aircraft. I have been walking all day long (including a 6km long walk just for the trip to the nearest Burger King) and i’m exhausted now.
I dropped by the GNOME and KDE booth and was a bit deceived. In comparison with the other booths, these ones were pretty small and without any attractive posters, sport car :p or whatever. But I took some pictures of the suggestion board that had some interesting notes :D.
Unfortunately, I couldn’t meet with Jens because he was working today. May be next time.
Airconfig Screenshots
By popular demand, here are a few Airconfig screenshots. Note how the signal strengths are all 100% in my menu; part of the blame lies with the bcm43xx driver's inability to report proper quality values. (But hey, I'm just thrilled I can use wireless on my PowerBook under Linux with a nice set of free [as in speech] drivers. Yes, consider that a middle finger tossed in the direction of Broadcom.)
Airconfig
Sometime last November or December I posted about GUI wireless networking config options for Linux, and I mentioned I was planning on writing one if I couldn't find one that met my needs (and actually worked).
Well, I went ahead and did it. It's not finished. There are things that don't work yet, buttons in the settings window that aren't connected to anything, and probably a bunch of error conditions I haven't handled yet. But it's starting to actually work for me, and I'm going to start actually using it for day-to-day stuff.
I haven't made any releases yet, but you can grab it from my Subversion repository (warning: sometimes the server decides to go off into the weeds and becomes unreachable). See the website here for download/install information, and do pay careful attention to the requirements list: older versions of the stuff in that list will almost certainly not work. I'm sorry about the high required versions of glib/gtk+, but I'm not going to try to reduce those until the app actually is "finished" and I have some spare time.
Please look at the README as well. There are a few dependencies that are required that probably aren't already set up properly on your system. (For example, there are only two distros I know of offhand that package wpa_supplicant with the D-Bus control interface compiled in.)
Note that Airconfig is more or less cross-desktop. It doesn't require any Xfce or GNOME libraries to function. It might not be particularly friendly (in the blending-in sense) for KDE users, as it does use gtk+. (A small exception: xfce4-dev-tools is required, but only for building from SVN. When I make release tarballs, you won't even need xfce4-dev-tools.) However, currently the GUI stuff is confined to two files, so it wouldn't be too difficult to write a Qt/KDE frontend (or even a wildly different gtk+ frontend) for it if you don't mind that it depends on gobject. That's probably a project for somewhat far in the future, though (I might do it myself; I haven't touched Qt since 2.x, and it would be fun to re-learn it).
Anyway, give it a look if you're interested. I've added Airconfig to Xfce Bugzilla, so feel free to report problems there (I greatly prefer that instead of email). I may not get to your bug for a while since there's still a lot to do.
Xfce and Choice
Since my last entry, a several important things happened. A number of users and developers chose to engage in a flamewar on the mailing lists. A few developers chose to leave. Many chose to just ignore the problems and focus on their work. Meanwhile, the council has chosen to start doing something about it. Since that last entry ("It's not about choice"), many things have happened. Well, we're Gentoo. We're flexible. We choose when to do things and when to do nothing. We'll adapt, and hopefully we'll weather the storm.
This weekend I chose (there's that word again) to update my Xfce Guide for 4.4, which is now being stabilized. Kudos to the arch teams and the xfce team; you guys rock!
You'll find new package suggestions, new descriptions, tips, links, and even a chapter on migrating from 4.2 to 4.4.
Now, you can choose (that was the last one, I promise) to do many things, but I hope you'll choose (okay, maybe not; I'm such a tease) to read the updated guide and try out Xfce 4.4 yourself.
And now, I choose to go to bed, since the PST to PDT change means the clock just struck 3AM.
Edit: Who's this joker over here? Who chose to write up that kind of wackiness?!?