Posts Tagged bugs
Removing Ubuntu annoyances
Here are a few Ubuntu 9.04 annoyances that I finally got around to addressing:
Constant “routine” disk checks on boot
Ubuntu 9.04 is lauded by critics for its improved boot times, and in most cases my machines running it boot to the login screen in less than 45 seconds. This is a solid improvement and it’s supposed to be under 10 seconds by the release of 10.04. The improved boot time in 9.04 is great: when I turn my computer on, I want to use it, not wait for an hour while the hard drive clicks and groans and the mouse cursor spins endlessly. It’s all well and good except that about every tenth boot takes forever thanks to an annoying disk checking routine. Are drive failures really that common that my drive has to be picked over by a fine-toothed comb every week? If so, a new storage technology is desperately needed. In the past 20 years or so, I’ve only had one memorable drive failure.
So, to fix the irritating disk checks on boot:
da1
sudo tune2fs -c 0 /dev/s
-c specifies the rate at which your disk is checked on boot and /dev/sda1 is your boot partition.
PC Speaker
Aside from the Caps Lock key, the PC speaker is an extremely annoying and useless “feature” of nearly every PC. Depending on your configuration, quite a few things can cause the PC speaker to beep, such as hitting backspace in a console when you haven’t typed anything. For some reason, when I shut down the computer using the Gnome shut down menu, I get several beeps from the PC speaker. This appears to be a bug. The best solution appears to be preventing the PC speaker module from loading at all. Create a blacklist file in /etc/modprobe.d called blacklist-custom.conf:
sudo gedit /etc/modprobe.d/blacklist-custom.conf
Then, add the following line to blacklist-custom.conf, save the file, and exit:
blacklist pcspkr
This will cause the “pcspkr” module not to load on boot. You can unload the module without rebooting by running the following in a terminal window:
sudo modprobe -r pcspkr
Update Manager Pop-under
Update nags are one of the worst “features” of many current operating systems. On Windows XP, I am spammed by a torrent of nag balloons forcing me to install updates and restart when the installation is complete. In OS X, a similar update manager jumps out at me in the dock until I deal with it. Until 9.04, Ubuntu had it right. In previous versions of Ubuntu, a small notification balloon would appear once and go away when new updates were available to install. I could either click on it to install the updates, or ignore it if I was in the middle of something. Now, what happens is about ten minutes after turning on my computer, which is right about the time I really get to working on something, the whole system grinds to a halt with the hard drive going nuts. Then, the Update Manager window opens underneath all the windows I have running, blinking and nagging at me to install whatever it found.
To go back to the original notification window functionality, run the following in a terminal window:
gconftool -s --type bool /apps/update-notifier/auto_launch false
Force Shutdown
When I click the “Shut Down” button to turn off my computer, I want it to turn off. No exceptions. Instead, if Firefox takes its merry time to save its session or something is running in the background (mounted drive through nfs or samba that won’t unmount), I get a nice “x is not responding. Logout anyway?” prompt. I don’t care if something isn’t responding: kill everything and shut down. To force shutdowns, edit your menu.lst:
sudo gedit /boot/grub/menu.lst
Scroll down and add “acpi=force noapic” to the kernel line of the default boot option:
title Ubuntu 9.04, kernel 2.6.28-11-generic
uuid f9d46e73-4aae-4203-ad97-93df87196054
kernel /boot/vmlinuz-2.6.28-11-generic root=UUID=... ro quiet splash acpi=force noapic
initrd /boot/initrd.img-2.6.28-11-generic
quiet
Video Playback Flicker in Ubuntu
I’ve noticed some people have stumbled here looking for how to solve Ubuntu video flickering issues. While I still haven’t figured out how to use both outputs of my dualhead ATI card without flicker, I do know how to fix video playback flickering.
I use VLC as my default media player. During an Ubuntu upgrade (I think it was 8.04 to 8.10), video playback in VLC started flickering.
In VLC, go to Tools->Preferences and click the Video button. Change output to X11 video output. This fixed the problem for me. There may be some way to change the output system-wide if you use other players, but I’ve had no reason to do this. Also, I don’t think I’ve had any issues with Internet Flash videos.
I just used a floppy…
I almost forgot these things existed, but I’ve had a nagging BIOS issue with my old desktop. When I hit the power button, sometimes the system would power on, then turn off for a few seconds, and then turn on again. More importantly, sometimes the CPU fan wouldn’t come on leading to it overheating and shutting down. The BIOS is so old that I had to flash it with a floppy, and I had to go home and do some digging around until I found one.
I even had to screw around in Ubuntu to get the drive mounted. The floppy has been seriously neglected, but what do you do when you’ve got an old BIOS that won’t flash from USB?
Fortunately, the flash worked, but I hope the CPU fan issue is resolved. I really hate looking down to see if the fan has started up when I turn on the computer. I used to just leave it on indefinitely so I wouldn’t have to worry, but it gets too hot in here.
PC vs. Console: I think I’m crossing over to the dark side…
Over the past few years I’ve lost some of my interest in gaming and as a result my desktop PC is several years old and rusting under my desk. I don’t use Windows for anything anymore and I’ve heard so many bad things about Vista, so I’ve been using Mac and Linux exclusively for awhile.
I would really like to get back into more games, but I just can’t see myself throwing out $2000 for a computer that I would use exclusively for games and be unable to carry around anywhere without a lot of effort. It just isn’t worth it anymore. So, I’m pretty sure I’m going to get an Xbox.
It seems that a real shift is taking place with developers placing emphasis on console games over PC, making most PC games a buggy port of their console counterparts. Most new PC games are packed with nasty copy protection rootkits that are nearly impossible to remove. Finally, new PC games all seem to have extremely steep system requirements, meaning you have to undertake a massive and expensive upgrade in order to get acceptable performance. All these are things I don’t want to deal with, especially when I can get a top of the line Xbox for less than the price of a halfway decent video card.
My main concern over console games is the controller. I started on PC games and feel natural with keyboard and mouse. At my height of gaming, I became one with the computer, leveling the crosshairs on an opponent and blasting away without the slightest thought of what keys to press and how much to move the mouse. I’ve played on a fair number of consoles and I’ve never adjusted to the controllers. I always feel sluggish and usually have to remember where the buttons are and what they do. Because of the controller, many RTS and simulation games are exclusively developed for the PC, which is a drawback in and of itself.
Regardless, I think I’m going to make the switch anyway. With enough practice, I can adjust to the controller. It’s also going to be a huge cost savings since it’s far easier to shell out $400 every four or five years for a new console compared to several thousand for PC upgrades. The additional money for PC upgrades would be more justifiable if I were to use the computer for work, but Windows is useless for development and the lack of portability is also detracting.
This leads into my proposed setup: get a new monitor with DVI and DisplayPort for my laptops and HDMI input for consoles. This way I can use the monitor for computing and for games. My current external monitor has a 4:3 aspect ratio with only one digital input and I would also prefer something widescreen. With only one digital input, it’s a real pain when I want to switch the Mac laptop for the Linux one or on the rare occasion that I want to boot up the desktop.
It seems that 16:9 1080p monitors are rare and are pretty limited in terms of functionality. The only one that remotely interests me is the Dell S2409W and I’ve it uses the poor quality TN panel which gets a lot of complaints. It may be okay for the Xbox, but I don’t know about using it with the computers. So, it seems 16:9 monitors are out since all the other ones I can find are also TN panels. Larger 30+ in TV-style monitors are also out since the cheapest of those runs about $800, which is out of my price range, especially for something that may not fare well as a computer monitor several feet from my face.
So, this means PC-oriented 16:10 aspect monitors. I would prefer something at least 24 inches and I can’t really get anything with a resolution greater than 1920 x 1200 since my laptops have terrible video cards. Being 16:10, it means that when I plug in the Xbox, I’ll get 100 pixel black bars on the bottom and top of the screen, but that’s something I can live with since the screen will be large enough. Two 16:10 monitors interest me: the Dell 2408WFP and the HP LP2475W. Of those, the HP seems the better buy since its panel is the highly coveted IPS and it also seems to be nearly $100 cheaper depending on the vendor. Both have an HDMI input, two DVI inputs, and a DisplayPort input.
Then, I can pick up a Pro Xbox for about $300. I can’t see the advantage of the Elite except for the 120 GB hard drive (vs. 60 on the Pro). Games are a bit more on the expensive side compared to the PC, but it’s probably all worth it not having to worry too much about endless installs, wasted hard drive space, and hardware-specific bugs.
So, I get an XBox Pro for about $300 and a 24 inch monitor for about $600, which is quite the savings over a massive PC upgrade. But there’s one problem: sound. Consoles are oriented towards those with dedicated 7.1 surround receivers to make it sound like a battle is being fought in the room. I don’t have that — I would prefer to just plug in some headphones, but the Xbox doesn’t have a headphone jack. This leaves me with three options, none of which I really care for:
1) Get a receiver. My dad’s got an old receiver that could handle the analog AV from the Xbox. I would really like to avoid this because it means yet another large piece of electronic junk sitting in my room. Furthermore, it would do nothing except provide me with a headphone jack for my games. This seems like a waste.
2) Connect the analog AV cables from the Xbox to a pair of headphones with some adapters. This isn’t really a good option either since there is no way to control the volume. I’ve heard of at least one person doing this and having it work, but as he said, there’s no volume control. You’re just stuck at whatever volume the Xbox puts out.
3) Connect the analog AV cables to the line in on my Macbook. I can also do this with some adapters and then plug the headphones into the Macbook and use the laptop as an amplifier. I’m not sure how well this would work either in terms of losing signal clarity and whines from the laptop making their way into my headphones. Also, I’m not even sure if the line in on the Macbook is stereo. I really don’t care about surround on headphones, but I would at least like to have stereo.
At this point, the third option is probably the best bet, and if that doesn’t work, try the others. I can’t seem to find many others on the Internet with this kind of setup. Most who use a PC monitor with their console still connect their sound to a dedicated receiver or a powered set of PC speakers.
I’ll probably wind up doing more research before I settle on something. Or, I might just forget it if it really looks like this won’t work.
Caveat Emptor, Early Adopters
Posted by Matt in Uncategorized on November 11, 2008
I upgraded to Ubuntu Intrepid Ibex last night and now I can’t connect to any WPA2 Enterprise networks. Unencrypted works fine, but the school’s WPA2 APs seem to be more pervasive.
This issue seems to be happening to a lot of people so I’m hoping someone is working on it. That’s the best thing about open source — if something bothers you about the software you can change it yourself. Unfortunately this problem isn’t in my area of expertise and I have plenty of programming to do for a project of my own.
I should have waited at least a month after the release to upgrade instead of jumping right in. New builds always have some serious problems that have to be worked out. I hear on message boards that new vehicle models and redesigns of old ones are prone to all kinds of quirks during the first model year. It’s best to wait until the second year to buy one so all the issues can be worked out. The same seems to go with electronics — the first iPhone had no GPS and a terrible 2G data connection, while the second version fixed these issues. And, of course, this quirkiness happens with software. Windows XP was a mess when it first came out and Vista was worse when it came to drivers and stability. XP is stable today (arguably), but Vista still has its problems.
Early adopters pay a high premium to get a product with limited functionality along with some unwanted side effects. As I sometimes forget, it’s best to wait until the problems have been worked out and the price comes down (if it’s not free software). Usually new and improved features get added in as the bugs get worked out.
So now I’m not even sure if I can drag my laptop around campus until this issue gets worked out. Serves me right for just following the appeal of something new, but not necessarily better.
Software Testing: The school IT department needs to clean up their act
Posted by Matt in Uncategorized on March 26, 2008
The room selection for the gradplex was supposed to be this morning. I get up before 8, log in, and try to pick out a room: none available. I screw around for ten minutes and it still says the same thing. So, I call Residence Life and they say something’s screwed up with the system and they were on the phone with IT. Then I get an email saying the whole thing just broke and they’ll try again tomorrow.
This happened last year to the undergrads and a lot of them got screwed. Happening once is less than marginally understandable since last year was the first time it was implemented and deployed on a large scale. However, this time the IT department needs some serious butt-kicking.
The graduate housing selection wasn’t quite right last year, either. The night before it was to open up, I was just messing around and found I was able to select a room before I was supposed to.
Working for five summers as a web developer for large database type systems, big time screwups like this are inexcusable. It was no joke that we had several staging servers for deployment and testing. There were tons of tedious test scripts we had to write and perform and all kinds of roadblocks to releasing a showstopping bug into the wild. Testing was a pain, but it prevented large meltdowns like these. We also made sure a subset of users extensively tested the pre-release versions on the staging server to ensure everything worked in practice. I got a few calls about stuff that made it that far, but better have the bugs stopped there than when someone’s document repository disappears. Of course, as with most large systems, there were always minor bugs that did make it out, but they were always things that could be fixed in the next release.
Edit: I just got an email reporting the whole thing was caused by an off-by-one error. Someone really didn’t do their homework before releasing this.
So much to do and school hasn’t even started yet
Posted by Matt in Uncategorized on January 11, 2008
Or has it?
There were some bugs in the gridding software I am using for my Master’s project which kept me stuck for the past week and a half. Now that the issues have been worked out, it’s still slow going. The more I get done the more likely I will graduate (or more appropriately, the sooner I will get my Master’s degree). I also got handed a bunch of papers by my to-be PhD adviser so I have to finish those by the time school starts next week. On top of all that, there are a bunch of things that NASA Ames wants implemented. I finish up with Ames at the end of the month regardless, but I should be able to handle their requests.
It looks like I’ll be a part time TA this semester too so that will add more stuff for me to handle. I think it’s going to be a rough semester, one that will either make me or break me. I’m going to have to make a good effort not to waste time since I tend to screw around on the Internet sometimes when I should be doing work (like now). I probably won’t be able to go to practice much due to my class times and work load, but it would be nice. Actually, at this point, I just hope I can continue to train as I have during previous semesters. I’ve got to have some kind of release since I’m not big on the social scene sort of things.
If things turn out well, my RA stuff will start in the summer, which is probably good. First, I won’t have to get another summer internship and deal with looking for places that will take me. Second, I’ll be able to get a head start on my PhD research which is also a good thing. The downside is that I’ll most likely be in Williamsburg in the summer, which is a lifeless, bug-infested jungle. I’ll probably be able to come home a lot since I won’t have classes, but I’ll have plenty of stuff to do from my advisor, I’m sure. At this point, I think I would like to try to find my own apartment so I won’t have to deal with roommates making a mess of things. Living in the graduate complex is getting old and it still has a bit of a dorm atmosphere to it. Regardless, that’s about number 4000 on the things I have to do this semester and I’m on number 6.
The replacements for my failing equipment came this week. The watch arrived yesterday and unlike the first, actually worked. There isn’t much to say about it except that it does what I want it to do. It’s better than the last one since the numbers are larger and easier to read when running. Also, I can make the primary display show the lap split and not the total running time. I’ve had a few watches that only show the total running time in the primary display for the chronograph, which seems pointless. The whole purpose of the lap/split feature is for interval type training. When you use it, you want to see the time of your current interval, not the total running time. Anyways, that’s definitely a plus with the new watch. Unlike my last watch, you can’t set the year, so I’m wondering what happens on leap years. I’m guessing it will have to be reset.
Frustrated with the intermittent R key on the Saitek Eclipse 2, I broke down and ordered the new Apple wired keyboard from Newegg. I looked at the Razer Lycoza, mentioned by
The keyboard came an hour ago and plugging it in gave me an excuse to pound out this entry. Two things right off the bat — the cord is really short, less than three feet long. It comes with a small extension cable, but together it still isn’t very long and barely reaches behind my desk to connect with the computer. I have a 10 foot USB extension cable at school I can use if I really need it. The other thing is that it has two USB ports, which won’t power my mouse. They are both low power ports. I’m not sure what USB devices are low power anymore. Maybe something with its own internal power supply, like a camera.
With that aside, the keyboard is definitely good. It’s really compact, even smaller than the Saitek Eclipse 2. It’s also well made — very heavy and not flimsy at all. Since it has such a low profile, there isn’t a need for a wrist pad, which really helps. The keys have a bit more feedback than the Macbook, but have a similar feel to most laptop keyboards. They are spaced out a bit more than a normal keyboard which causes me to mistype occasionally, but it’s something I can get used to in time. And, of course, the R key works. Compared to a regular keyboard, I feel I can type faster on this since I don’t have to slam down my fingers to make every keystroke register. I have yet to try it out in any games, but I can’t see it being any different than playing games on a laptop. It seems that many hardcore gamers are using laptop style keyboards nowadays anyway.
Another weird thing I just noticed — my Dell LCD seems to have experienced some burn in since I’ve plugged it into the Macbook. The Apple menu bar is slightly visible during the boot sequence. Doing some reading suggests that it can be removed by running an all-white screen as a screensaver. The 2001FP is another “older” piece of equipment I’ve got that hopefully won’t break down anytime soon like my keyboard or watch. I would like to get a massive 1080P TV/monitor to use with my computer or even the new Dell 30 inch display. Those would be great for games and for displaying a ton of junk on the screen at once when I’m working. Unfortunately, monitors that big aren’t conducive to someone in my situation who moves back and forth to school every few months (and likely will for awhile).
The weather has been weird again lately, with it being very warm and windy. Each day the forecast is for the cold to return, but it never really does. It’s been good for running, but I’m sure it will be back to cold and nasty rain just in time for school to start next week.
I also saw No Country for Old Men this week, which was definitely the best movie I’ve seen all year with the exception of the ending. The bad guy gets away after killing all but one of the good guys. There isn’t any final showdown, either — each character dies in a different scene without putting up much of a fight. The one guy you want to win dies a quick death offscreen while the one good character left stops chasing the bad guy simply because he just doesn’t care anymore. The first three quarters were great though, a couple of street smart rednecks barely outsmarting a cool and calculated hit man. There were plenty of tense moments mixed in with slower paced character and setting building scenes. The atmosphere and dialog were great and reminded me a lot of the driving out west this summer.
Well, back to work some more before it gets any later.
Third Semester = Done
Posted by Matt in Uncategorized on December 14, 2007
As of yesterday, I’ve finished my third semester in graduate school. At this point, however, the contrast between work in one semester and the next is starting to blur. Things are seemingly no more semester to semester but now are more blended together.
Since the due dates for my Masters project are so early, I’ve made an effort to get everything rolling on that. For what I am doing, there appears to be a lot of licensing issues that have to be worked out and it’s taking some time to get all the paperwork. Good thing I tried to start early, because the CS office admin told me that 50% of students don’t finish their project in time and have to get their degrees in the summer. Yuck.
But it might not matter. Here I was a month ago, really getting tired of the day to day school stuff, just waiting to get my degree and leave. And then, an opportunity struck that I will probably never get again. I was approached by one of my professors about a possible RA position if I wanted to stay for my PhD. I hadn’t even considered this before, since I never really considered myself to be “PhD material”. I do know that if I leave school, I won’t be going back. I met with the prof who would provide the RA position, who specializes in Wireless Sensor Networks. It’s a new, up and coming area of research for computer science and there are so many applications for it. I took a class that dealt with it last semester and I’ll be taking another in the spring. I think it would be a good research area for me and being a PhD student would allow me to focus on fleshing out some of the ideas I’ve had in class projects. It seems that there are a lot of things that would be good to work on more in depth, but classes and the end of the semester always get in the way. Having no classes and just doing research would allow me to do that.
Anyways, this would mean I could potentially be here for another three to four years. That’s ten years here in Williamsburg. Already, my freshman year of college seems so long ago and everything seems so much different now. I can’t imagine what I will think of it if I leave in another three or four years.
I was thinking that next semester would be really easy since I would only have to take one other class on top of my project to graduate, the wireless sensor networks class. Now, for the PhD, I need another class. Between three required classes and four electives 600 level or above, I have to get a 3.7 average. That is going to make things tough. Two classes I just finished will also count towards those seven classes and I’m hoping I did well in both of them. The two classes in the spring would also count towards those four electives and I will have to bust my butt to do well. Otherwise, I’ll have to take something in the fall and push back my PhD candidacy until I finish. Hopefully I can pull it off, because the only two other classes available next spring that I haven’t taken and also fulfill the PhD requirements seem pretty hard. One is a really programming heavy advanced compilers class which everyone I knew that took last year said took a lot of time and work. The other is a theory class that seems to mostly deal with NP-completeness with weekly written assignments. My math background isn’t that strong, but I’ve gotten through two similar algorithms classes. I’ll have to decide which will be better.
In the spring, I also want to try my hand at a marathon, so that should also make things interesting. At this point, though, my priorities are really going to shift. If the going gets tough, something is going to have to give, which probably means my training. Depending on my class schedule, I might not be able to make it to practice most days anyways, so running on my own will free up some time. I know most of my professors seemed concerned last year when I was still on the travel roster because they thought it would really screw with my performance. I managed to prove them wrong, but it seems that the PhD track is yet another level of intensity that I haven’t experienced yet.
This fall I didn’t really do any hard core training for anything. I did a road race at home over Thanksgiving that was more of a workout and I planned to do an indoor 3k last weekend, but I was worried about my achilles so I didn’t go. That’s one good thing about not being on the team — I can decide when I’m at the breaking point and back off. I would rather not race and still be able to run than vice versa. In terms of training this fall, I did some workouts on my own and attempted to do a couple with the team but got completely owned. I’m not in the shape I used to be in, but maybe with a plan I can make some progress. For the marathon, I’ve got to gain weight so I can have more energy to expend over long distances. Apparently the big thing with the marathon is getting your body used to drinking and eating stuff midway through the race so you don’t crash. The dining hall food has really sucked which is part of the problem for me right now. It’s been affecting my every day runs since I can tell I don’t have the same energy. Standing in line for 10 minutes for 3 strands of watery spaghetti just doesn’t cut it. If I don’t deal with this now, I’ll just get injured like I did in the summer.
This whole thing is going to be a big adventure for me. I have nothing to lose, except if something weird happens and I don’t finish my project, decide not to stay for the PhD, and wind up graduating in the summer. I guess in the long run that doesn’t matter too much.
Over break, I’ll have to get going on my M.S. project as well as continue work for NASA Ames. Ames has a list of stuff for my visualization plug in that they want finished. It seems every time I fire it up there are more bugs. Hopefully I can clean it up and get done what they want while still having time for my school project. I don’t want to burn out before the spring semester starts, either. The best thing is that I can do all of this from home on my own time. I don’t have to go to an office from 9 to 5 when I worked during the winter before. It sucked running in the dark, driving home in the dark, and not seeing daylight except when I drove to work in the morning.
For the most part, the weather has been great this fall. I remember freezing my butt off walking back from class at this point in the year. It makes things more enjoyable when the climate is more temperate. Also, my winter coat has a broken zipper.
Hopefully I’ll be out of here within an hour or two so the traffic won’t be too bad on the way home. I’ve got another meeting to attend two and then I’ll really be finished.
Back East
Posted by Matt in Uncategorized on August 24, 2007
It’s all over now. This summer is, at least.
Last week my presentation went pretty well, but I lost my place twice and forgot what I was going to say. I stood there like an idiot for a few seconds until I could remember. That’s how it goes, I guess. You just have to practice until you get it right.
Before I left, I met with my supervisor who said I could work part time during school if I wanted. That sounds great since it would be really flexible, unlike becoming a TA/grader with the Computer Science department. I could only work a few hours a week if school got tough. He also said I could go full time during winter break and I could work completely from home just like a few of the other guys in our team. Hopefully I can get everything set up for that within a few weeks because the beginning of school always has the least amount of work.
My mom came in Thursday afternoon and took Caltrain from the airport to Mountain View. I came by around noon and picked her up. That was pretty easy.
On Friday I met with everyone for the last time and went over my source code. I was very surprised nobody really complained about it. In fact, nobody really made any suggestions about changing my code, which was really surprising. Everyone said if I was able to fix the few bugs that still remain it could be released in the next version.
Friday afternoon I was able to leave early and my mom and I drove into San Francisco and walked along the Embarcadero. We went into Pier 39 and saw sea lions duking it out on the dock. We bought some sourdough bread which we took with us on the trip back and was really good.
For dinner we met our old neighbors again at the Fog City Diner. I got this dish with crab, scallops, clams, and scallops in a broth. I had never ordered anything before where you had to break apart the crab to get at the meat. It was kind of messy for only a little meat, but still good.
On the way back I realized that this was my last trip to San Francisco and down the 101 towards Moffett. I really didn’t want to leave.
Day 1 (Saturday): Mountain View, CA to Williams, AZ:
The following morning I got up early and biked on the usual route, but there wasn’t nearly as much traffic so I wasn’t caught at all the lights. It was weird realizing that this was also my last few hours in California and I would be heading home.
We got the car packed up and left around 9:30 from Moffett and headed down 101, crossed over to I-5 around Gilroy, and then took CA 58 through Bakersfield and Barstow before getting on I-40. We stopped outside of Bakersfield at a Subway for lunch. They served avocados on their subs That part of California isn’t that nice. It’s hot, dry, and smoggy. I definitely wouldn’t want to live there. There were also tons of trucks carrying tomatoes and melons. After getting on I-40, we passed into the Sierra Nevada — this far south it wasn’t nearly as spectacular as on I-80, more like a handful of desert hills. There were a lot of ghost towns out there.
There was an aircraft graveyard and a ton of windmills in Mojave. The whole area was hot, dusty, and dry. I can’t believe that Dan and his friend hiked through that for the first month or so of their trip on the Pacific Crest Trail. That whole area is inhospitable and I couldn’t imagine walking for days in the desert.
We got to Needles, CA, along the Colorado, at around 6 PM Pacific and stopped at a Denny’s. It was the only place around. Needles was a ghost town, even on a Saturday evening. Gas there was insane — like $3.57 or something, while even in Mountain View it was under $3.00. Afterwards, my mom and I continued across the Colorado into Arizona with anothe two and a half hours to go until Williams. I drove the windy, hilly, and desolate roads through the sunset and into the dark. Signs every mile warned of deer and elk and everyone around us had their high beams on to look out for them. We passed a place called Black Mesa. It wasn’t much different looking than the Black Mesa from Half Life. There were plenty of striated sandstone mesas that faded into the darkness along the way. We finally got to Williams around 9:30 Pacific and we were both exhausted. It was over 10 and a half hours of driving that day.
Day 2 (Sunday): Williams, AZ to Amarillo, TX:
The second day sucked because of the time change. We lost two hours that day because Arizona is on Pacific time for the summer and Mountain time in the winter. Finishing the day in Texas meant we would be on Central time, so we only went 9 hours that day. My mom had thought about driving up to the Grand Canyon, but a couple hours out of the way would have slowed things down a lot. Instead, we headed out of Williams on I-40 instead of going north to the Grand Canyon.
This day had a lot of scenery changes. Near Flagstaff there were mountains and forests of pine trees, but crossing into the eastern part of the state there were more deserts. We went by the Painted Desert, Meteor Crater, and the Petrified Forest. I had been to all of these places when I was little and only remembered bits and pieces. It was possible to see chunks of petrified logs as well as some of the Painted Desert from the interstate.
New Mexico was more arid and dry and was like Mojave, but with more scrubby vegetation. There were also bigger mountains. We drove through a few canyons which were pretty cool. When we got to Albuquerque, we went into the downtown area and drove around the Old Town and stopped at the University of New Mexico. Their classes were starting the next day. It was also incredibly hot there but fortunately no humidity.
The rest of New Mexico was pretty desolate and flat. There was some grass and cattle, and that was about it. We stopped at a steakhouse for dinner in some forgotten town. The beef was good, though. Not long after, we passed into Texas, which was more of the same endless flat terrain.
Day 3 (Monday): Amarillo, TX to Forrest City, AR:
We got in over ten hours this day and had time to do some sightseeing since we were on Central time the whole day. Texas on I-40 was just flat and grass as it had been the day before. There was almost nothing there. Oklahoma had some of that, but more trees cropped up as we headed east towards Oklahoma City.
We stopped in Oklahoma City at a deli for lunch and walked to the Oklahoma City Bombing Memorial. I remember seeing the memorial on the news when it was finished. It was pretty interesting to see. There is a big reflecting pool and a metal chair for each person who died. I remember hearing somewhere that no references to the bombers themselves are made either in the memorial or the museum next door. I didn’t see any.
I nearly fell asleep on the drive from Oklahoma until we stopped in Little Rock for dinner. It was just rolling hills and trees and wasn’t much different than I-64 from Williamsburg to Richmond. We went to a Cracker Barrel and got a huge pile of food. My mom and I shared everything we got and I wound up eating most of her pecan pancakes. They were really good. There was also this hash brown casserole which I liked that I got as part of my dish.
From Little Rock it was only about another 45 minutes or so to Forrest City.
Day 4 (Tuesday): Forrest City, AR to Christiansburg, VA:
This was the last full day of driving and was another ten hours. We started the day just switching to Eastern time so it would be easier later on. There wasn’t much traffic going into Memphis, but there were a few nasty car accidents on the other side of the highway that made things a mess for everyone going the other way. Looking at the map, I noticed Mississippi was only about 10 miles from where we were so my mom drove 20 minutes out of the way just so I could say I had been there. Now I’ve been to all the southern states. I doubt I would have reason to return to Mississippi, so I’m glad we stopped.
There was well over 500 miles of driving in Tennessee, about as much as Sarah and I did in Nebraska on the way out, but this was a lot better since there were several big cities (Memphis, Nashville, Knoxville), more traffic, and hills and mountains. Still, I made sure to get a Mountain Dew at lunch so that I could stay awake for my portion of the drive. I don’t drink stuff with caffeine much so I can really feel it when I get some. It’s like chemically induced awakeness — I can tell I’m not supposed to be as alert as I am. When it wears off I can really tell too, but by that time we had almost made it to Virginia after getting off I-40 and on to I-81.
I had never been to that little corner of Virginia before, so even that was a first for me. There was a Bob Evans in Wyethville that we stopped at for dinner, and again, it wasn’t much farther to Christiansburg.
Day 5 (Wednesday): Christiansburg, VA to Virginia Beach, VA:
Finally, the last day of driving. The car was a mess on the outside and I was anxious since I hadn’t run or biked since we left California. It was a little over 5 hours on US 460 from Christiansburg back to Virginia Beach. There was almost no traffic until we got to Petersburg, so it was probably a good way to go.
It was weird coming back home after all this time and especially after driving from the west coast. It was great to get out of the car and bike. I went down to the oceanfront and back and it was a welcome release. Of course, it was overcast with jungle-esque humidity with some rain.
My achilles was really sore the day after I tried running on it before I left California. I tried again yesterday but it was pretty tight during the run so I cut it short after about 20 minutes. Fortunately, it wasn’t sore today, only pretty tight. I may try going in the afternoons instead of the morning so it will be looser. Hopefully it will improve soon.
Basically I only have a day or two before I go back to school with school starting next Wednesday. I feel really rushed, but that’s how it goes. Going back to school always sucks, but after a week or so I get into a routine and it’s fine.
Well, my trip this summer has come full circle and now it’s back to the same old stuff. I’m glad I had this experience, though, because it was like nothing else I’ve ever done.
Road Trip
Posted by Matt in Uncategorized on June 3, 2007
I made it.
The road trip across the country was nothing like I expected. My main surprise was that so much of the country is filled with open space. I’m used to the east coast, where all the cities butt up against each other and there isn’t any land that hasn’t been plowed or paved. Once you get past St. Louis, that all changes.
The route was pretty simple: I-64 West until St. Louis, then I-70 from there to Kansas City. From Kansas City we took I-29 to Nebraska City, NE and then NE 2 to Lincoln. Then, from Lincoln all the way to San Francisco we were on I-80.
The first day we went from Virginia Beach to Shelbyville, Kentucky. I left at about 9:15 from my house to pick up Sarah and we got going around 9:45. She drove the first half of the day until we got near the West Virginia border. The highways in West Virginia were hilly and snaked in between the mountains. The turns were much tighter than any of the other mountain ranges we crossed and there was plenty of traffic as we approached Charleston. This was also the only toll section of the trip, with the exception of the two bridge tolls (San Rafael-Richmond and Golden Gate) we encountered near San Francisco. At Huntington, the interstate was closed off completely and everyone was forced to exit into a huge mess towards the city. The road atlas we had got us around that through some narrow back roads until we got to an interstate entrance farther along. I learned later there was a fatal accident that caused that. We got dinner at a Fazoli’s in Morehead and then made it to the Days Inn in Shelbyville around 9:00 that night. I was probably the most tired after this day than any of the others.
The second day we went from Shelbyville, Kentucky to Nebraska City, Nebraska. The Days Inn wasn’t the best place to run, but I managed to get in about 5 miles around the hotel and along US 60 in Shelbyville. The humidity was insane. US 60 parallels I-64 the entire way to St. Louis and they intersect countless times. It seemed that every other exit was for US 60. Along the way, we passed through Louisville before entering Indiana and then Illinois, which were mostly farms. The farther we went, the fewer trees there were and the less like home it looked.
We got to St. Louis, crossed the Mississippi and got off to see the Arch. It was really hot and humid but there were tons of people around. The arch was a lot taller than I expected but wasn’t very big around. We headed back to the car and I took over driving for the rest of the day, going through Kansas City, stopping for dinner, and then continuing north on I-29 until we passed into Iowa. We got to Nebraska City not long afterwards and checked in to a Super 8.
With the hotels, we booked everything one day in advance. The night before, I looked up driving distances on Google Maps to see how far we could get in 9 – 10 hours of driving. Then, I looked up hotels in that area on Orbitz or Expedia to find ones with the best price. I also made sure they had internet access so I could book a room for the next night the same way. It worked out pretty well.
The next morning I tried to run into Nebraska from the hotel, since the hotel was actually still in Iowa. It wound up being too far and I had to turn around. The wind was insane and there wasn’t much around to stop it. What few trees there were had all grown slanted due to the wind. It was also a lot cooler than the previous day.
The third day was from Nebraska City to Rawlins, Wyoming and consisted mostly of endless miles of I-80 in Nebraska. I-80 covers nearly 500 miles in Nebraska, but we didn’t do all of it since we cut over on NE 2 from Nebraska City. Still, it was pretty bad, just straight and flat with nothing interesting to look at. The wind was rough, too. We did a quick turn off into Colorado and then came back just to say we went there. That part of Colorado was nothing like Denver or the mountains near Steamboat Springs I had visited before. Instead, it was just like Nebraska: mostly flat and covered with farmland.
Towards Wyoming, the terrain got hillier and some small mesas started to appear. There was also a huge cluster of nasty thunderstorms. Somehow we managed to escape most of it. Mainly, I was worried about hail since I had heard there was golf ball sized hail in Denver the day before. There were also auto body shops along the way that had signs proclaiming “Hail Repair”. That wasn’t a good sign, but the storms only gave us rain.
We stopped in Cheyenne for awhile and walked around. It was a nice town, but it seemed really deserted considering it was only 4 PM. Some of the parking spaces had signs indicating “Horse Parking”, which was interesting. I wonder who would take a horse to work instead of a car. We walked in front of the capital and took some pictures. It was really weird with almost nobody around, but if I remember correctly, the entire state has a population of about that of Virginia Beach but has an area about twice the size of Virginia. There was a pizza place off one of the main streets that we ate at that had an interesting combination of cheeses. I think it was similar to what I’ve heard to be called St. Louis-style pizza, but I’m not sure. It was really good, but also much different than anything I’ve had before. Going back to the car, a little girl made some comment about the Virginia license plate on the car. I guess they don’t get too many visitors in Cheyenne.
After dinner, we hit the road again and made it to Rawlins just as it got dark. Along the way there were some snow covered peaks, the first big mountains in the trip. We also passed a few large refineries, which may explain why the gas prices got cheaper. The other weird thing I noticed about the gas was that in Wyoming, Utah, and Nevada, the octane rating for regular gas was 85 instead of the usual 87. I’m thinking it has something to do with the altitude.
Rawlins was more or less a no-frills town. It seemed the people there just wanted to survive and didn’t care too much for aesthetics. I could easily see it being an old west town with muddy streets and saloons with the swinging doors. There weren’t any trees, just dust, scrubby little weeds, and mountains. Definitely nothing like Steamboat Springs, which was only about two hours to the south. The hotel I got wasn’t any better. Everything else I found was way expensive or overbooked. The lady working the front desk said that Rawlins was one of the few towns along I-80 with hotels so everyone wanted to stay in what few hotels there were. She also said that some places in the next town (150 miles west) were booked three weeks in advance. The place didn’t have internet either, but I had written down the numbers for several hotels for the next night in Fernley, Nevada and managed to get a reservation.
The next morning I got my first experience running “at altitude”. Rawlins was at 6800 feet, so I don’t know exactly how that weighs in with high altitude training, but I’ve heard that anything over a mile can get to you. I ran from the hotel along a paved bike path and then onto some BLM dirt trails outside the town and then back. It was freezing outside, too, in the 30s, which was a huge change from the 90s in St. Louis and at home. I felt a little lightheaded and maybe a little tired during the run, but that was about it. I bet if I was racing it would be a lot tougher.
The fourth day was from Rawlins to Fernley, Nevada. Sarah drove the rest of Wyoming, which was extremely barren. No towns for 200 miles, except for Rock Springs, no trees, and almost no vegetation, either. I thought Scotland was desolate, but this took the cake. Road signs periodically announced there were no services for 60 or 70 miles. Run out of gas out here and you’re toast. Very few cars, either – most of the traffic was trucks. There weren’t many mountains, either. There were some snow-covered mountains out in the distance at one point, but that was about it.
The real mountains came when we entered Utah and went into a big canyon. The road wound around large, towering peaks, and continued to do so even as we approached Salt Lake City and the traffic became heavy. We went by Park City and saw what appeared to be the ski jump facilities from the Olympics. We also made a quick stop in Salt Lake to get gas and wash the car. The car was a huge mess after several days of travel and was covered in dirt and bugs.
Then began the trek into the desert. Salt Lake City dropped away as quickly as it had appeared and then we passed by the Great Salt Lake. That too soon disappeared and we were driving down an endless stretch of road in the middle of a flat, barren desert. There were mountains lurking in the background and the whole thing seemed like some kind of old video game where the road and cars move, but the background doesn’t. Eventually the mountains got closer, and upon reaching them, we entered Nevada.
Nevada was just like Wyoming in terms of desolation, except that it was hotter. Again there were plenty of signs indicating that you better get your gas or food now or you may regret it. There were a few small mountain ranges to cross and a few small towns. Like Wyoming, there were no radio stations. Sometimes we got NPR or some random country station, but they all faded out quickly with all the mountains. Occasionally there was a house or building with trees surrounding it, which was obviously irrigated at a hefty price. At a truck stop, another person made a comment when seeing the car about how far away from home we were. Indeed.
The speed limits for all these western states were 75 mph, starting in Nebraska. I found that to be plenty fast, since the car could barely handle 80 with all the stuff in it, including the bike mounted to the back. Most cars and trucks didn’t seem to go that fast, so we did a lot of passing. Occasionally, someone would blaze past us, and they were almost always from out of state. I didn’t see but a few cop cars in those western states, either.
We stopped in Battle Mountain at a diner type place, which wasn’t too bad for the price. Half of the place was filled with slot machines. Tumbleweeds blew across the street as we ate. Another two hours and we were in Fernley, which had the nicest hotel we stayed at for the whole trip. It was also the most expensive.
The next morning I went out past some industrial warehouses, including one for Amazon, and found another BLM trail network that went out into the desert. It was probably at least 80 degrees but it felt much cooler than that because there wasn’t any humidity. It was strange running in such a place with the mountains, sand, and scrubby weeds. Someone had turned part of the trail into a shooting range, which was covered in hundreds of pistol and shotgun shell casings. I ran into some power lines that were low hanging and sizzling. The trail went underneath them, but I turned around, not wanting to decrease my life expectancy by going near those things.
The fifth, and last day was from Fernley to Mountain View, California. The terrain stayed desert-like and mountainous until we reached Reno. From there, it was into the Sierra Nevada, where there were plenty of snow covered mountains. A sign announced we entered California and the mountains began to sprout trees and finally began to resemble more of Northern California than the desert we left behind. On top of the mountains, we took an exit for the Pacific Crest Trailhead and stopped to look around. We hiked a small trail that led to the PCT that still had snow on the ground, despite it being over 70 degrees. It must have taken a ton of accumulation for the snow to still be there. Horsefly sized mosquitoes attacked from all directions as we hiked, but it was really nice with the large fir trees and views of nearby mountains.
A thousand miles to the south, Dan and his friend are making their way up the entire length of the PCT. Here’s to hoping they will make it to where we were and beyond to Oregon and Washington.
We got back in the car and began a long descent towards Sacramento. It seemed the downhill was much longer than the uphill. Nevada must have been at a much higher altitude to begin with. The traffic became worse as we approached Sacramento. Despite the 65 mph speed limit, everyone was hauling past us.
We passed Sacramento and approached San Francisco on 580, going over the San Rafael-Richmond bridge, and then onto 101 and the Golden Gate. The bay and the city were covered with clouds and fog and it was a cool 50 degrees. We stopped on the San Francisco side of the bridge and walked around for a bit and took some pictures. It was so weird to be here with the car and to realize that we drove here. All the other times I’ve flown. There seemed to be a disconnect between places I’ve been in a car and places I’ve flown and now that gap has been closed. All that driving can be cancelled out by a five hour plane flight. The car started with over 41,000 miles and now it had well over 44,000.
We drove into San Francisco, passing through the Presidio. Giant Russian Hill loomed in front of us. The hill got worse and worse as we approached the top. The manual gearshift didn’t help, but I made it without flying backwards down the hill. I also managed to parallel park the car on the hill too, even with the bike and all the other junk in it. We walked over the top to the crooked part of Lombard and took a few more pictures. The place was crammed with tourists, which made me wonder what all the residents think of living there. I guess they knew what they were getting into when they moved in.
By then it was about 4PM on Friday and the 101 to Mountain View was a parking lot. It took an hour or more to get to Moffett Field, but checking into the lodge proved easy. There were some other interns hanging around the base, reading in a grass field, and walking around the lodge. The room was much nicer than I expected, with a TV, microwave, and full-sized fridge. My main complaint is that I can’t get a signal for the NASA-provided wireless internet from my room. I can get a crappy signal from Google’s free Mountain View wifi if I put the computer against the window, but it works great if I go outside.
Sarah and I went to Buca di Beppo in Palo Alto for dinner, which has provided me with leftovers for the past two days. It was nice to go back there again. It was also weird since all the other times I had a big race coming up, but this time was different. I have no idea what to expect since everything is new. After that I tried in vain to find a grocery store, but just wound up driving in circles for 30 minutes. In the morning, I ran loops around the base, exploring. It wasn’t as big as I thought it was, mainly because parts of it are restricted. It was also really deserted.
That afternoon I drove Sarah to the airport and waited for her flight back home to leave. It was strange going to that airport and not going home. Every time I’ve been there I was always coming from home and going home, but yesterday I wasn’t doing that. This is now my home, at least for a few months. This is basically the first time I’ve moved anywhere, since going to school in Williamsburg isn’t that far from home and I was already pretty familiar with the area.
Driving back, I stopped at a Fry’s, the first time I’ve ever been to one. They need to open up a couple in Virginia – they have everything. I got a high gain wireless antenna and extension cable for a USB wireless adapter that I ordered on Newegg today. I finally found the grocery store and a Trader Joe’s and wound up blowing over $100 on food. I got as much non-perishable stuff as I could as well as things that I could easily make. After getting back, I got the whole room organized and found it hard to believe that I had actually made the trip and everything was actually happening. It’s a huge change from being at school or at home.
Overall, the trip probably ran over $800 including gas, hotels, and food for the two of us. It came in well under the $1000 I had expected, mostly due to lower hotel and gas prices. Gas mileage was spot on 24 mpg, which is the government estimate. I paid as much as $3.40 in Illinois and as little as $3.05 in Covington, VA. I don’t think many places have cheaper gas than at home. Yesterday I paid $3.47 in Los Altos.
This morning I ran outside the gate to the Stevens Creek Trail, which was really cool – it went along the bay and has plenty of dirt sections that parallel the bike path. There seem to be a lot of these type trails in the area and I hope to explore all of them. I also want to drive to a couple of the nearby parks and run there, as well as possibly bike from here to the coast.
The base is really weird. Most of it is vacant since most of the NASA stuff goes on at the Research Park, which is its own little area. There are large airship hangars and some planes on the tarmac. The buildings look like they are right out of Black Mesa in Half Life. I went looking for the laundry room, but it’s actually more of a laundry “bunker”. The building is recessed into the ground and three sides of it are sloped and covered in grass. It’s surrounded by abandoned living quarters with asbestos warnings.
Well, tomorrow is the start of my first day of work. I’m sure it will be an experience, no matter what happens. This whole trip so far has been a real change of pace and nothing like anything I’ve ever done before. It’s exactly why I decided to do this. Something new and exciting.
Recent Comments