Difference between revisions of "Express Disc troubleshooting"
(30 intermediate revisions by 4 users not shown) | |||
Line 1: | Line 1: | ||
− | + | {{MessageBox| | |
− | + | backgroundcolor = #faa| | |
− | + | image =Warning.png| | |
+ | heading =WARNING| | ||
+ | message = Amahi 7 for Fedora 19<br />Maintenance Support ONLY!}} | ||
+ | = '''WARNING''' = | ||
+ | |||
+ | = Amahi 7 Express Disc = | ||
+ | |||
+ | ==System crashes during Install== | ||
+ | |||
+ | Install crashes after the initial information gathering section, but before the files start to be copied from the DVD: | ||
+ | * Check if the BIOS has any UEFI boot settings and if so, disable them or set the options to legacy only boot. | ||
+ | * Disable secure boot mode if available. | ||
+ | |||
+ | |||
+ | This fixed a crash with a Gigabyte motherboard. | ||
+ | |||
+ | ==tsc fast calibration failed== | ||
+ | After selecting the first '''Install Amahi 7''' option, you received the error ''tsc fast calibration failed''. Shortly after this the screen may go blank, and although the DVD drive continued to spin for a few minutes, install may never progress. | ||
+ | |||
+ | To overcome the error, select the '''Troubleshooting''' option, and choosing the '''Install with basic graphics''' option. Installation should now proceed. | ||
+ | |||
+ | == Second reboot does not occur == | ||
+ | |||
+ | If the second reboot does not occur, this means the install is not finished. One reason for this to happen is a wrong setting in the Network page of your Installer. By default it says this and we recommend this is left as is: | ||
+ | |||
+ | Hostname: localhost.localdomain | ||
+ | |||
+ | However, I had filled in my host names (which resolved). | ||
+ | |||
+ | The solution was to reinstall and leave the Network page of the installer the defaul localhost.localdomain | ||
+ | |||
+ | == HTTP server is not running == | ||
+ | After succesfull second reboot I noticed that the Amahi dashboard did not work. I noticed that there was not running the http server, via the command | ||
+ | |||
+ | ps -ef | grep http | ||
+ | |||
+ | This command showed me that an error occurred during startup of the http service. It could not resolve the hostname I gave it: | ||
+ | |||
+ | systemctl status httpd | ||
+ | |||
+ | These commands started the httpd server, showing me that it was started correctly: | ||
+ | |||
+ | systemctl restart httpd | ||
+ | systemctl status httpd | ||
+ | |||
+ | After a reboot this error occurred again. Now changing the value in /etc/hostname to | ||
+ | |||
+ | localhost | ||
+ | |||
+ | fixed this. After a reboot the http service is now started as it should be. | ||
+ | |||
+ | We recommend you leave the values in the Amahi express install at the network section to its default value: | ||
+ | |||
+ | localhost.localdomain | ||
+ | |||
+ | <!--= Amahi 6 Express = | ||
− | = | + | ==Reboot Loop== |
+ | Sometimes, the express cd installer gets caught in a reboot loop. | ||
− | + | It asks you to reboot, then it tells you it needs to reboot again over and over. | |
− | + | If you are one of the lucky ones experiencing this, here's what to do: | |
− | |||
− | |||
− | |||
− | |||
− | + | If there is no network, you can try this: | |
− | edit | + | * Select debug |
+ | * system-config-network (configure your network interface correctly ( I used static ) / also make sure your dns are configured exit the system-config-network) | ||
+ | * /etc/init.d/network restart | ||
+ | * check that eth0 has started, if not edit /etc/sysconfig/network-scripts/ifcfg-eth0; modify ONBOOT=no to ONBOOT=yes; then issue the "ifup eth0" command. | ||
+ | * ConfigAmahi (wait for a while untill it says reboot, then reboot)--> | ||
+ | ==Yum Update fails== | ||
+ | If you try to do yum update after install and have problems, try this [http://digitizor.com/2009/06/17/how-to-fix-the-cannot-retrieve-repository-metadata-repomd-xml-error-in-fedora-11/ solution]. |
Latest revision as of 00:55, 15 September 2015
WARNING | |
---|---|
Amahi 7 for Fedora 19 Maintenance Support ONLY! |
Contents
WARNING
Amahi 7 Express Disc
System crashes during Install
Install crashes after the initial information gathering section, but before the files start to be copied from the DVD:
- Check if the BIOS has any UEFI boot settings and if so, disable them or set the options to legacy only boot.
- Disable secure boot mode if available.
This fixed a crash with a Gigabyte motherboard.
tsc fast calibration failed
After selecting the first Install Amahi 7 option, you received the error tsc fast calibration failed. Shortly after this the screen may go blank, and although the DVD drive continued to spin for a few minutes, install may never progress.
To overcome the error, select the Troubleshooting option, and choosing the Install with basic graphics option. Installation should now proceed.
Second reboot does not occur
If the second reboot does not occur, this means the install is not finished. One reason for this to happen is a wrong setting in the Network page of your Installer. By default it says this and we recommend this is left as is:
Hostname: localhost.localdomain
However, I had filled in my host names (which resolved).
The solution was to reinstall and leave the Network page of the installer the defaul localhost.localdomain
HTTP server is not running
After succesfull second reboot I noticed that the Amahi dashboard did not work. I noticed that there was not running the http server, via the command
ps -ef | grep http
This command showed me that an error occurred during startup of the http service. It could not resolve the hostname I gave it:
systemctl status httpd
These commands started the httpd server, showing me that it was started correctly:
systemctl restart httpd systemctl status httpd
After a reboot this error occurred again. Now changing the value in /etc/hostname to
localhost
fixed this. After a reboot the http service is now started as it should be.
We recommend you leave the values in the Amahi express install at the network section to its default value:
localhost.localdomain
Yum Update fails
If you try to do yum update after install and have problems, try this solution.