Found it! It was the RAM chip at 10M. The chip itself was fine, but the trace to pin 16 was intermittent. I got the board with a socket already at that location, and I'm guessing that when the chip was pulled out the board got damaged. I also found that flexing the board would get it to work briefly.

Got a board in that when it booted up the attract screen was messed up. Colors of characters aren't quite right Flexing the board around the area of 1A cleared up the problem. Looking at the back of the board I see someone tried to reflow the solder around a bunch of the sockets. I'm going to start ripping them up one at a time and replacing them with new clean ones. Update: Replacing the socket at 2A fixed it.

Played a bit with the power management today. Couldn't really it get it to do much that'll be useful. I turned on the ACPI in the kernel and turned off APM and rebuilt/rebooted. My power button stopped doing an immediate shutdown and I could cat a file and see everytime I pushed it, which was neat. When I tried to put the computer into S3 it went to sleep, but didn't quite want to wake up. Had problems with both the video and the USB keyboard/mouse. I also had no luck at all finding...

After much tinkering I finally got advmame to fire up Donkey Kong! It was a problem with the framebuffer driver. Sort of. :-) The site that the driver originally came from used an old style of separating the boot args. It said that you separate args with a : and the values with an =. Well, under the 2.6.11 kernel it's args with a , and values with a : This is what I'm using for a boot arg: video=i810fb:xres:1024,bpp:16,hsync1:30,hsync2:65,vsync1:50,vsync2:100,accel,mtrr Unfortunately it...