Amahi running but can't log in locally

[warrenway]

Everything seems to be running. Amahi dashboard works and I can access shares from my Win7 box, but the Fedora 14 install is stuck at the blue 'f' screen. No ctrl-alt-F* combination takes me away froim the screen and I'm afraid to power down manually and restart with various keystrokes to boot to a command line. Can someone give me a hand on getting to a command prompt or (even better) my login screen.

BTW I only have one user created on the Fedora machine and I use those credentials to access my shares, so I don't think the account is gone. I was in the process of setting up VNC when this problem showed up, so no remote access to Gnome desktop as far as I know, nor is VPN running according to Amahi's website.

[retinalcircus]

please clarify, are you installing Fedora 14 on a machine that is already running Amahi? Typically, you would install Fedora 14 and then install Amahi from the repository... at which point you wouldn't need to install Fedora again...

Confused...

[retinalcircus]

BTW- the Amahi Interactive Network Troubleshooter is a great tool:

http://net.pommepause.com/network_troubleshooter/

[warrenway]

please clarify, are you installing Fedora 14 on a machine that is already running Amahi? Typically, you would install Fedora 14 and then install Amahi from the repository... at which point you wouldn't need to install Fedora again...

Confused...

I installed Fedora 14 then Amahi (had been running Amahi on F12 for a short time but some hardware died on me). I have had the F14 install running fine except I had trouble with VNC. I uninstalled then reinstalled tigervnc and was in the midst of configuring it when I had a brownout. After that, when I rebooted it seemed I was stuck just before the login screen and would have thought the system had frozen except the lights on my external RAID were blinking like crazy. I can read from and write to the Greyhole shares and map them to my Windows machine but I cannot login to the F14 machine locally or over the network (unless F14 installs some sort of remote desktop by default) because VNC was not finished configuring.

When I looked for some way to bypass the blue 'f' screen everything required I change a config file, but as I cannot login I can't change anything. The ctr-alt-<function> keystrokes don't work at the point my machine is "stuck" at. Is there a way to bypass the GUI while booting ala Windows F8 key?

[retinalcircus]

Oh, man. I see now. Brownouts suck. I do not know of any way to bypass the GUI to get to the terminal before the GUI is done booting. There is a built-in remote desktop functionality in Fedora 14- In the GUI under System/Preferences/Remote Desktop- but you have to check a box that allows others to see your desktop. The box is not checked by default, so it won't help you in this case. I don't know how to help you. I guess you may have to risk powering down altogether to reboot and restart the install somehow...

[warrenway]

Okay it's fixed. I *was* able to open up a terminal using PuTTY, which I found in the troubleshooting site you sent me to, so thanks.

Turns out I would have had the problem even without the power failure. When I tried to start the GUI from the command line the system said screen 0 was already in use. 0 is the setting I used configuring VNC. I guess I was following the wiki instructions too literally. I changed the setting to 1 and voila.