It’s never a good thing when your daily alarm on your computer (which is basically XMMS here) doesn’t go off in the morning. Seeing the keyboard LEDs blinking and a frozen screen saver aren’t much better. Once again, this new box kernel panicked in the middle of the night.
I’m not sure whether to blame the hardware, or the 2.4.26 kernel. The RAM checked out fine, and nearly everything works otherwise, with a few exceptions. My IntelliMouse Explorer keeps losing the ability to function, and I have to unplug it from the USB port and plug it back in every 20 minutes or so. I replaced mice, and it seems to work now. However, now the IntelliMouse is working fine in the iMac. I can’t tell if the mouse is going dead or if it’s a kernel issue.
I couldn’t get 2.4.26 working on the server box (which used to be my main desktop). It would lose all network connectivity, no matter what I did. Oddly, the same configuration works on this box, using the same network card. I suspect 2.4.26 is just a buggy kernel, but I haven’t seen a whole lot from other people to indicate that.
So anyhow, this morning, I rebooted and it came up with a whole bunch of filesystem errors. All kinds of stuff. Several of the errors said, "attempt to read block from filesystem resulted in short read." A quick google search indicates that this could be the disk going bad, so I’m sure I’m in for a lot of fun these next few days. Fortunately, the only data I lost were a bunch of KDE .desktop files and some .m4 files that apparently weren’t even lost. No clue what happened there. *sigh*
Some days, I really miss using my Commodore 64.