Skip to main content

OS upgrade

Although its been a month or so since I received my AMD 64 3200+ and DFI LANparty UT nF3 Ultra-D from a friend, I'm still only setting it up and breaking it in.

One of the first few questions I tried to figure out was what operating system are I going to load in it or rather what was the best OS around to use on it. So, I decided to try a few after buying a few more parts for it.

I bought a ASUS AGP Nvidia 7600 GS Silent (no fan) and a couple of 320GB SATA drives with the Gigabyte 550W power suppy and centurion 5 case with 1GB PC DDR 400 memory.

The first OS I decided to try was Vista, after all it was the latest and greatest right? Well, it installed no problems, and I even liked the new Windows movie maker that can with it. Yes, some "WOW". My PC scored a 4 on the Vista performance scale. Not too bad, with the CPU having the lowest score of 4. And more WOW, the sound didn't work. Yes, there were no drivers for it and when I went to the Vista site to look for audio support, it turns out that Vista had very bad support for soundcards, in fact it virtually didn't support much at all, like anything slightly fancy is totally out and you can basically forget about surround sound.

Ok, so I decided to go back to old faithful, this time I was brave and decided to try the nvidia on board RAID 1. I dug out a old floppy drive from my retired PII and loaded the drivers. Yay! Sound at last. Hmm, the odd thing was the computer seemed rather unstable. crashing, etc, but of course I ignored it and played Dawn of War, Dark Crusade with high detail and 1024 x 768 graphics. It seems that with slower CPUs and higher end graphics card, the detailing can be set high with lower resolution, my guess is that the CPU has to process more objects and the graphics card only puts in the detail. Alas, a whole bunch of dodgy stuff happened again, and the most irritating thing about XP is that it refuses to tell you the real problem. It blue screened on boot continuously and I had to get down and dirty to fix it.

I looked in the bios and reset everything to factory default and started to configure it again. I tried different installation media and alas, the RAID floppy died. Well, I could install without the raid, but I decided to do something different.

The final selection of OS, Centos 5 vs Fedora core 6. I managed to download both the distributions from using cygwin ncftp. I installed Centos first succesfully after a couple more bouts with the BIOS and hard drives. I disabled the RAIDto avoid confusion and unplugged my third drive on the SATA 3. This I gathered from the error messages on /dev/sdc. See why can't windows let you know stuff like that.

Centos 5 is flash, and I mean cool. Its changed some core concepts from Centos 4, but basically its all quite capable for a newbie to get a hold of and start using immediately. I'll have to consider it definately one of the greater advances in Desktop/Server operating systems. I used the Logical Volume Manager and was suprised how easy it was to add space and extend an existing logical volume over additional drives. The security might be a bit hard to get a handle with Selinux. If you were an end-user, it would be a no brainer. It really does protect. Once you want to start creating your own servers, e.g. SAMBA, you might encounter some issues with it. I just set it up as Permissive to get some idea on what it was trying to do initially.

Alas, for bleeding edge, I will have to go with Fedora core 6. I'm downloading the x64 DVD iso as I write this blog and I have a feeling that this will most likely stay on this machine if nothing really bad happens again. If "touch wood" something does, I guess you can't go wrong with Centos 5. It really does ROCK!


Melven said…
final installed distribution: fedora core 6 x86_64

Installation issues: X refused to display anything after the installation.

resolution: check the router dhcp address and ssh from another machine with root to init 3. Desktop goes to terminal and I log in as root to run "system-config-display". I also decided to "adduser username" and init 5 to login. You can reboot "ctrl-alt-delete" to get to the configuration screen after running the system-config-display in init 3.

Terminal and applications takes a long time to load. This is because the hostname I set was not in an entry in the /etc/hosts file. I changed it to static anyway as I planned to run services off the box.

Everything worked fine.

Popular posts from this blog

Multiple Broadlink RM mini 3 integration using MQTT

Broadlink now has quite a lot of integration options almost out of the box. If you enable Broadlink IHC, you can directly link it to Alexa by giving the device a unique name.

There is a homebridge plug in for homekit integration but I haven't tried or tested this.

I wanted to put the device in domoticz so I can have more control over what can trigger my broadlink. I decided to use broadlink-mqtt for this, which is a fairly easy method to trigger from any source.

Setup Instructions for broadlink-mqtt

1. git clone

2. vi /home/pi/broadlink-mqtt/mqtt.conf

3. Update the mqtt.conf file with the device type set as multiple_lookup

device_type = 'multiple_lookup'
mqtt_multiple_subprefix_format = '{type}_{mac_nic}/'
4. Start the python script and check that it started and detected all the RM devices.
Check the log file to see what the IP / MAC addresses are. DEBUG Connected to RM2 Broadlink device at …

Fibaro HCL Virtual Device Slider

How to setup Fibaro home center lite (HCL) slider for virtual devices.

As the Fibaro HCL does not support LUA. The question was how to update the number value of the slider to send to the HTTP string. Thanks to this site which is a really good reference

The 2 use cases here are;

Sonos HTTP API Volume

To allow for volume control for all Sonos devices, add a virtual device with the IP address for SONOS HTTP API and specify the default port to 5005. Create Slider and put the following text into the string.

GET /volume/_sliderValue_ HTTP/1.10x0D0x0A0x0D0x0A

Domotiz Virtual Devices

GET /json.htm?type=command&param=switchlight&idx=XX&switchcmd=Set%20Level&level=_sliderValue_ HTTP/1.10x0D0x0A0x0D0x0A

Replace XX with the device ID.

Restart Fibaro HCL when it stops working automatically

It seems that the Fibaro HCL seems to hang every now and then. Instead of trying to restart it regularly, which doesn't really work, as it's almost impossible to predict when this will happen.

This method checks that the HCL is actually running and in the event it stops working, trigger a script that will restart it.

1. Get a non Fibaro controlled power plug and scripts to control it.

I used a wifi smart plug, TP-link HS100 and downloaded the scripts from

2. Create a bash script to restart the Fibaro, e.g.



$scripts/ -t $ip_addr -c off
sleep 10
$scripts/ -t $ip_addr -c on

3. Create a test global variable in the Fibaro HCL

Go to the variables panel and create a test variable, e.g. Test

4. Add a cron entry to test that the Fibaro API is still working and restart if it's not.

The cron script is scheduled ev…