Unfortunately, trying to install VMWare ESXi 4 on Intel Atom D945GCLF2 using USB Flash drive FAILS :( :( :(
You can get trial version of ESXi 4 on VMWare website. This is good for 60 days. You can extract the downloaded ISO image and extract a boot image from it. This boot image can be directly flashed to a USB pen drive (larger than 1GB) and boot off directly without setting up entire stuff.
More info can be found on net for this process.
I am not sure what you would miss if you pop the ISO image on a DVD and boot using it.
You will have to enable USB boot support in BIOS setup and move USB higher up in boot order. Also make sure that USB boot emulation is set to Hard Disk. On Intel D945GCLF2, setting USB boot emulation to AUTO did not work for me.
To my dismay...the boot fails with following two errors...
Failed to load tpm
Failed to load lvmdriver
This had worked on Intel Laptop so I was quiet hopeful that it runs on D945GCLF2, being an Intel motherboard.
Quick googling reveals that the Realtek NIC in Intel Atom motherboards is not supported. The installation error is not specific i.e. "Unsupported Network Adaptor" or something like that...Apparently, the boot code uses NIC MAC address to generate unique identifier for some kind and that code fails.
Temp solution is to install a supported Network adaptor and install. My system cabinet does not have slot to add any card, even though the motherboard supports one PCI slot. This should have been checked while buying soI cant complain now. The Zebronics Chotu cabinet is quiet compact. But this lack of slot makes it bad buy for D945GCLF2 boards. The SMPS provided is also not fully enclosed. The heat generated by SMPS shares is not barred by entering cabinet. This causes the system temperature to rise by few degrees when covered up.
No plans to test ESX further on Atom now :(
Showing posts with label intel atom 330. Show all posts
Showing posts with label intel atom 330. Show all posts
Tuesday, August 11, 2009
Friday, June 19, 2009
Home Server Project - Remote management and configuring alets about system/hdd temperature
The box is back in its final place - my personal-data centre. As observed before, closed cabinet adds warmth to the cabinet and adds almost 10 degree Celsius in the temperature reading. For now, it would remain uncovered and temperature lies between 50-60C
This rack is 8 feet above the ground hence turning the machine on is a challenge. WOL came to rescue. The onboard NIC supports wake on lan so I got one wol utility from internet. There are plenty available. I tried with two and both worked well.
Sendmail for google apps has been already configured for this box. The box is able to mail whenever apache has been started or stopped. To extend this further, I am trying to schedule cron jobs to mail me temperature status of various components. A quick tutorial and hddtemp package is now able to send me HDD temperature over mail, every 15 mins. Following command has been scheduled for it
mail -s `hddtemp /dev/sda | awk '{print $2$3}'` test@example.com < /dev/null
I am still trying to get sensor temperature but not able to get HTML mail out. It looks like a permission issue. The script works fine when ran as root, but not when through crontab.
This rack is 8 feet above the ground hence turning the machine on is a challenge. WOL came to rescue. The onboard NIC supports wake on lan so I got one wol utility from internet. There are plenty available. I tried with two and both worked well.
Sendmail for google apps has been already configured for this box. The box is able to mail whenever apache has been started or stopped. To extend this further, I am trying to schedule cron jobs to mail me temperature status of various components. A quick tutorial and hddtemp package is now able to send me HDD temperature over mail, every 15 mins. Following command has been scheduled for it
mail -s `hddtemp /dev/sda | awk '{print $2$3}'` test@example.com < /dev/null
I am still trying to get sensor temperature but not able to get HTML mail out. It looks like a permission issue. The script works fine when ran as root, but not when through crontab.
Monday, June 15, 2009
Home Server Project - Configuring PHPMyAdmin
The steps are getting tougher :) I had to spend a complete day trying to setup phpMyAdmin on the server. It was crazy.
I was able to install php and php-mysql correctly. phpMyAdmin is needed to manage databases using browser. I could otherwise login to CLI and manage things well. Decided to configure phpMyAdmin and it ate up whole day.
First I was stopped by SELinux...
Jun 14 12:16:16 atom setroubleshoot: SELinux is preventing the /usr/sbin/httpd from using potentially mislabeled files (/var/www/phpMyAdmin-3.1.5-english). For complete SELinux messages. run sealert -l b25683a9-e1ea-429d-aa13-4130012ee64d
Tried renaming folders but no luck. One option was to disable SELinux but it was not straightforward either. after a lot of searches and reads, found the simple solution. The error itself asks to run sealert command. Ran it and it tells what to do to stop this from happening!
Next was the Apache authentication prompt. It turned out to be lack of configuration for authusers and authgroups, well not easily again, took another hour I think :)
Now page would just indicate on top corner - PHP 5.2+ required. This was a bummer. I thought it was there, but it wasn't. The DVD ISO was on the client laptop, so thought of copying it over to server and see if php 5.2 was there. The copy software indicated 40 mins ETA for copying over 54Mbps WIFI connection. "Why not copy it by 1Gbps crosscable network?", I asked myself.
The copy broke after connecting using crossover link. Apparently the server lost DNS servers by this and sshd broke. grrrrrrrrr....
Another hour worth of fiddling finally got this done. Just to tell me that the default php that came with installation was 5.1.
Next step was to download PHP 5.2 manually and compile. It was done and next problem - PHP would work fine on cli, just wont enable itself with httpd :|
I decided to go back completely on 5.1. I had avoided pointing to CentOS repo since begining. I tried doing it now. I had to manually edit repo files to replace $releaseserver by "5". And it was faily quick.
Finally at night the brain worked. I installed older version of phpMyAdmin and that was all that I needed to do in morning :) :) :)
Hopefully I can start writing php-mysql toy-code tomorrow!
I was able to install php and php-mysql correctly. phpMyAdmin is needed to manage databases using browser. I could otherwise login to CLI and manage things well. Decided to configure phpMyAdmin and it ate up whole day.
First I was stopped by SELinux...
Jun 14 12:16:16 atom setroubleshoot: SELinux is preventing the /usr/sbin/httpd from using potentially mislabeled files (/var/www/phpMyAdmin-3.1.5-english). For complete SELinux messages. run sealert -l b25683a9-e1ea-429d-aa13-4130012ee64d
Tried renaming folders but no luck. One option was to disable SELinux but it was not straightforward either. after a lot of searches and reads, found the simple solution. The error itself asks to run sealert command. Ran it and it tells what to do to stop this from happening!
Next was the Apache authentication prompt. It turned out to be lack of configuration for authusers and authgroups, well not easily again, took another hour I think :)
Now page would just indicate on top corner - PHP 5.2+ required. This was a bummer. I thought it was there, but it wasn't. The DVD ISO was on the client laptop, so thought of copying it over to server and see if php 5.2 was there. The copy software indicated 40 mins ETA for copying over 54Mbps WIFI connection. "Why not copy it by 1Gbps crosscable network?", I asked myself.
The copy broke after connecting using crossover link. Apparently the server lost DNS servers by this and sshd broke. grrrrrrrrr....
Another hour worth of fiddling finally got this done. Just to tell me that the default php that came with installation was 5.1.
Next step was to download PHP 5.2 manually and compile. It was done and next problem - PHP would work fine on cli, just wont enable itself with httpd :|
I decided to go back completely on 5.1. I had avoided pointing to CentOS repo since begining. I tried doing it now. I had to manually edit repo files to replace $releaseserver by "5". And it was faily quick.
Finally at night the brain worked. I installed older version of phpMyAdmin and that was all that I needed to do in morning :) :) :)
Hopefully I can start writing php-mysql toy-code tomorrow!
Wednesday, May 27, 2009
Home Server Project - getting the web server up for alpha testing
Just got the server up for some time. For those who are not aware (almost all of you would be :) ), its following configuration...
Intel 945GCLF2 motherboard with Atom330 (Dual atom, dual core) CPU
2GB DDR RAM
Seagate 320GB internal SATA HDD
miniature keyboard, mouse and DVD-RW drive, though not to be connected
This is low power consumption system and low in size, thanks to Intel Atom. Planned to be run up and running 24/7, either as a web server, HTPC, home server or any combination of these :)
The mobo and SMPS went kaput just on the day when it was pieced up :( :( managed to get it back after 4 weeks.
So now the box is hunting for its final place, waiting for work at home to finish for this. Just powered it on for a while of testing.
Was trying to setup Apache on Linux. SSHed to it and started Apache service. Came up fine. Checked up local page access, and it was fine. But could not be accessed from other machine on network or internet.
Tried to scratch my head hard, and "iptables" hit me. Checked if iptables was running and stopped it.
Voila! The Atom is on the net now :)
Intel 945GCLF2 motherboard with Atom330 (Dual atom, dual core) CPU
2GB DDR RAM
Seagate 320GB internal SATA HDD
miniature keyboard, mouse and DVD-RW drive, though not to be connected
This is low power consumption system and low in size, thanks to Intel Atom. Planned to be run up and running 24/7, either as a web server, HTPC, home server or any combination of these :)
The mobo and SMPS went kaput just on the day when it was pieced up :( :( managed to get it back after 4 weeks.
So now the box is hunting for its final place, waiting for work at home to finish for this. Just powered it on for a while of testing.
Was trying to setup Apache on Linux. SSHed to it and started Apache service. Came up fine. Checked up local page access, and it was fine. But could not be accessed from other machine on network or internet.
Tried to scratch my head hard, and "iptables" hit me. Checked if iptables was running and stopped it.
Voila! The Atom is on the net now :)
Subscribe to:
Posts (Atom)