Sunday... does it ever stop?
May. 24th, 2010 09:12 amSunday, more of the same. Run around to pick up the girls, who'd already eaten breakfast at their respective overnight events. Take them home. Omaha jumps into the car with two thermoses (thermii?) of milk and two sandwich boxes filled with bagels & cream cheese. We hurtle into downtown for our monthly haircuts. Omaha is first, so I hit the bookstore looking for Jillian Weise's The Colony. I don't find that, but I do finally find a copy of Myst: Masterpiece Edition, which is a huge deal because it actually runs on Win32, not Win16, and that means I have a good chance of playing it on my Linux boxes.
No such luck.
Omaha, meanwhile, rants about how I get to play Portal on my Linux desktop (DVD, not Steam, edition) running an Nvidia GeForce FX Series 5, but her Mac with a Series 7 can't run it; she needs a Series 8, at least. WTF?
I get home and now there's more housework. Not the garden this time, the fence. The west-facing fence had fallen over, so now it was me and the neighbor's brawny teenage boys (he was out of town) putting in two new fenceposts, concrete and all. We measured and straightened and dug. I pointed out to the Mrs. next door that it didn't matter that we'd done it right this time-- four foot deep holes, 50kg of concrete-- if they didn't get a retaining terrace up soon, her property was going to erode into the side of my house, and those stresses would be unfortunate. They have plans to finish the terracing soon.
And just before our D&D game, I figured out why I couldn't get my 3D drivers working. I'd tried everything, for weeks, switching out the radeon and radeonhd drivers, the radeon and radeonhd Mesa OpenGL handlers, over and over, and it was driving me nuts. I'd even put Mesa into debug mode and that didn't help. Finally, I hit upon a comment that I could run the GLInfo program in debug mode with the argument LIBGL_DEBUG=verbose, and when I tried it, it kept saying that it couldn't open the card device.
All this time, I, the owner of the laptop, had not been listed as for direct rendering. I wasn't a member of group video in the damn access control lists. I felt pretty dumb.
Neither Myst or PlantsVsZombies ran any better. I'm still working on it.
No such luck.
Omaha, meanwhile, rants about how I get to play Portal on my Linux desktop (DVD, not Steam, edition) running an Nvidia GeForce FX Series 5, but her Mac with a Series 7 can't run it; she needs a Series 8, at least. WTF?
I get home and now there's more housework. Not the garden this time, the fence. The west-facing fence had fallen over, so now it was me and the neighbor's brawny teenage boys (he was out of town) putting in two new fenceposts, concrete and all. We measured and straightened and dug. I pointed out to the Mrs. next door that it didn't matter that we'd done it right this time-- four foot deep holes, 50kg of concrete-- if they didn't get a retaining terrace up soon, her property was going to erode into the side of my house, and those stresses would be unfortunate. They have plans to finish the terracing soon.
And just before our D&D game, I figured out why I couldn't get my 3D drivers working. I'd tried everything, for weeks, switching out the radeon and radeonhd drivers, the radeon and radeonhd Mesa OpenGL handlers, over and over, and it was driving me nuts. I'd even put Mesa into debug mode and that didn't help. Finally, I hit upon a comment that I could run the GLInfo program in debug mode with the argument LIBGL_DEBUG=verbose, and when I tried it, it kept saying that it couldn't open the card device.
All this time, I, the owner of the laptop, had not been listed as for direct rendering. I wasn't a member of group video in the damn access control lists. I felt pretty dumb.
Neither Myst or PlantsVsZombies ran any better. I'm still working on it.