Another Zalmon ZM460 bites the dust. This one probably because the load on the server is more than 460 watts I expect. Put in a Cooler Master Silent PRO 800. And it is silent. Probably will stick with Cooler Masters for now.

Frequently get this:

$ evince

Maximum number of clients reachedCannot parse arguments: Cannot open display:

Flew to Melbourne today, for a few holidays + the Drupal Down Under. Had a problem with my K3805-Z stick, wasn't recognised anymore on this machine. Perhaps the Oneiric upgrade? According to syslog usb-modeswitch crashed when inserting the stick. The solution was to get the 1.21 usb_modeswitch, compile and install it, and that fixed the problem.

Good for performance as the always reliable K3565 Vodem worked, but is feeling a bit slow these days.

The only problem I still have is that Ubuntu itself doesn't pickup on the USB sticks anymore. It used to that, perhaps my playing around a year ago to get the K3805-Z working killed things. So need the latest vodafone-mobile-connect-card-driver-for-linux to connect me.

Today was a bit of poking around day. Tried to setup PXE booting from my FreeBSD 8. Didn't get it working using the guides (1, and 2 were particularly helpful) until I understood that the host setting (with MAC address) is really, really required. You can't have a setup where a PXE client boots something default.

After some playing was also able to get linux booting to work. Now installing Ubuntu 10.04 LTS on a Dell PowerEdge R210 using my new PXE boot capabilities.

Lot of changes to my network recently. The old PIII-800MHz became a pfSense router for a friend, and the server is the Intel Core2 4400 at 2GHz, so quite a step up. But getting it all configured was major pain.

After putting the new motherboard into the case, the system sort-of booted, but not really. Couldn't find the kernel. As this was the server, my network was down, so not easy to download a bootable cd, which I should have prepared actually. Somehow I had a FreeBSD 8.0 disk, so was able to boot with that in the end and poke around. It appears the kernel was ad4, instead of ad0 ??? Still don't understand it. The disk was ATA, but I also put in a SATA disk which became ad6. And the MBR was corrupt or perhaps the next boot loader was corrupt. Had to reinstall to boot and set it up to load the kernel from ad4.

Putting the old motherboard in another case went wrong too as the PSU (Zalman ZM460B-APS) died in the process.