Aug
25
2007
0

Additional Progress on Linux on the Vaio

After overcoming the FS key bug a few months ago, my latest efforts have been on increasing performance while running Linux on my Sony Vaio FS760/W .

Strangely, when my laptop was plugged into the wall via the AC adapter – Gnome System Monitor would indicate that my CPU usage (while idle) hovered around 20% utilization, and would erratically spike up past 60% for seemingly no reason. Performance was laggy, but unplugging the ac adapter would bring everything back to a normal state.

A really simple test to try if you are experiencing similar trouble on your Vaio running Linux is to open up a terminal and hold down a key. Whatever letter you are holding down will slowly creep across the terminal – now unplug the power while still holding down the key. You should see things smooth out drastically.

Doing some additional research around the Ubuntu Linux bugtracker – I realized that this may not be a Vaio compatibility problem as much as it is a bug with Centrino chipsets in the Ubuntu Generic kernel. As an experiment I installed the i386 architecture kernel, and the difference was night and day. While idle, cpu usage in Gnome is less than 2% and the system is running smoother than I ever remember it being. Shortly after, I removed all references to the generic kernel from my system and haven’t looked back.

Making this change did prompt me to redo my graphics and FS key settings, as the functionality of both is directly linked to kernel modules. My Geforce 6250GO was brought back online via the Envy script (which is awesome, and incredibly simple if you haven’t tried it) and I brought my FS key support back via my feisty-fsfn script previously published. However, changing the architecture to i386 caused my original script as written to fail due to a typo. I’ve fixed this and uploaded a correct copy.

Please let me know if you have any additional insight or experiences with this issue regarding Linux on Vaio laptops!

Written by mluebbe in: Hardware,Software |
Aug
23
2007
0

Midnight Programming

Recently read Soul of a New Machine which is a great read for any engineer, especially a Computer Engineer as the plot revolves around Data General’s battle to create a 16/32 bit hybrid computer in the late seventies.

One passage in particular stuck out to me, regarding a team member talking about their college experience:

It was an IBM Machine, archaic now but gaudy then. The university owned it, in effect, and it lay inside a room that none but the machine’s professional caretakers could enter during the day. But Alsing found that a student could just walk into that room at night and play with the computer. Alsing didn’t drink much and he never took any other drugs. “I was a midnight programmer,” he confessed…
…About ten other young undergraduates regularly attended these sessions of midnight programming. “It was a whole subculture. It’s been popularized now, but it was a secret cult in my days,” said Alsing. “The game of programming – and it is a game – was so fascinating. We’d stay up all night and experience it. It really is like a drug, I think.” A few of his fellow midnight programmers began to ignore their girlfriends and eventually lost them for the sake of playing with the machine all night. Some started sleeping days and missed all of their classes, thereby ruining their grades. Alsing and a few others flunked out of school.

As I read this – it was all too eerie and familiar. The allure of technology. When I first started undergrad, we didn’t have a computer in some obscure closet – but we did form our own nerd subcultures around certain projects and places. For the Computer Science students at the University of Arizona it was the Harvill Lab then later after Harvill was closed, the Gould-Simpson lab aka “GS228″ aka “The Human Fishtank”. The Human Fishtank was room that had been designed for big iron when the building was designed – air-conditioning coming out of the floors, and plexiglass walls for people to marvel at the latest room-filling mainframe industry had produced. Later when big iron fell out of style, they crammed the room full of cheap pcs and desks – and it was guaranteed that given any day of the year, any time of day (thanks to the 24 hour access), you could go in there, cut some code and find a person or two to talk shop with.

Or if you went over to the Aerospace and Mechanical Engineering building after 5pm – there was an entirely different, yet similar subculture that came out of the woodwork after dark. The SAE kids would work all night on their Formula car, occasionally sleeping under tables or in their 3rd floor office. The asian grad students had apparently evolved to a state in which they required no sleep and would be hard at work advancing the state of the art in fluids or rocket design. There wasn’t more than a handful of rooms in the 9 floor building that were uninhabited or let alone had the lights off. I would generally be in the Aerial Robotics lab working on code for Machine Vision or AI for our UAV, or sometimes on the other side of the building actually wrenching on an aircraft with some fellow students. On a slight tangent, I think a defining moment in my life was the night I turned 21. Popular tradition in college, is on this special occasion for your friends to take you to a bar for the first time to get you monumentally drunk. I spent my last night being 20 in a laboratory prepping a UAV for a maiden flight that ended in a spectacular crash.

In one way or another, like a drug – each one of us Midnight Engineers paid for our addiction in one way or another. Just like the book says, some lost their grades, some also flunked out of school. Myself, I lost my girlfriend – this caused me in the months that followed to look deeply into what else I had lost in this pursuit. I was no longer playing music, I spent most of my time alone debugging programs and hardware, I had lost touch with many of the people who cared about me, I no longer had a girlfriend that loved me.

What was the point?
Was I an addict?
This realization made these engineering pursuits less and less gratifying, until I lacked all interest and figured that some serious reevaluation of my current life was in order. Within a week, I had dropped out of school and was packing my belongings to head back to the Midwest to sort my life out.

That was about a year and a half ago, and I think that in the time I’ve learned a lot about life. Dropping out of college was probably the best thing that ever happened to me.

Written by mluebbe in: Computing,Life |
Aug
21
2007
1

T-Minus Six Days…

Next Monday I start attending college again as a junior in Computer Engineering at the University of Illinois at Chicago. Its been about a year and a half since the last time I set foot in a classroom, and it feels sort of strange to be going back. Since leaving school, most of my former classmates have graduated and I’ve spent the time working as a programmer for hire. Most of the people I interact with on a daily basis have long since been done with college – it creates the feeling that in a sense I’m going backwards, when deep down I know I’m progressing forward.

On a semi-related note due to the coincidental timing, I got an email from a Professor I used to work with in the Computer Science department at the University of Arizona wanting to know what I was up to. It’s nice to think that even after I up and vanished 18 months ago, I left enough of a mark that people there still remember me.

My latest code related diversion from reality is the Haiku OS, which I am working on getting involved with by working on bug fixes. Haiku is a rebuilt-from-scratch implementation of BeOS, an OS that’s been dead for years. The Haiku team has set up a very impressive and simple setup for developers, it was very simple for me to get the source from their subversion server, cross-compile it, and build a image to test with in VMWare, all from my Linux Desktop. Whether Haiku is the end-all-be-all to Desktop computing as the project aims to be, I’m not convinced at this point. What I am convinced of, that will probably become a post of its own is the necessity of alternatives in order to promote technology innovation. In order for Operating Systems to advance as a whole, there needs to be strong competition in the field – otherwise you end up with dogshit software like Windows Vista. I think Haiku/BeOS introduces some interesting concepts that are currently lacking in its competitors, particularly in respects to multithreaded architecture and responsiveness. Hopefully my skills will be enough to contribute a few lines of code that will make it into the R1 release.

Written by mluebbe in: Life,Software |

Powered by WordPress | Theme: Aeros 2.0 by TheBuckmaker.com