Have 5955 installed on the core. No problems at all. just shy of an hour for a complete install. First MD running diskless setup right now a Revo 1600. I still get a failed to start x. Rebooted and failed to start x.
Edit: I ran the EEE Box b202 and that completed. The first 2 screens of the AV wizard were way to large. I could only see maybe a quarter of the screen, but managed to get through the wizard. I finished the Sarah setup just waiting on the installing part. I am sure it will finish to the orbiter. Trying an onboard ATI Radeon 3000 right now. Also a failed to start x. I also tried another Nvidia based system, onboard 6100, and Failed to start x. So only the Intel worked.
The EEE Box works fine.
Managed to get the Revo to display the AV Wizard. The Nvidia drivers are failing to install. I had to apt-get install nvidia-260-kernel-source. gave me a error that it couldnt install dkms. I apt-get update, apt-get install dkms. Then apt-get install nvidia-260-kernel-source, rebooted and then AV wizard came up. Finished the setup and The first Revo is up and running.
Edit again.
My second revo also came up with failed to start x. I opened a terminal up and apt-get update and upgrade. It downloaded some updates. restarted it and it started installing the nvidia drivers. failed to start x, rebooted and AV Wizard came up.
Also I have always chroot to the md and passwd so I can ssh to the md's as root. I did it and when I ssh to any md, I get Bad owner or permissions on /root/.ssh/config.
Firstly, thanks so much for the feedback. I will address the errors as I understand them... and I am going to go backwards.
1. Don't do that. Your MDs and Core are designed to share a key. To ssh to the md just sudo ssh moonXX That will drop you into the MD as root and not break a bunch of stuff. Whether or not I have that working correctly again needs testing, but that can't happen on this snapshot because:
2. I am an idiot. I changed ownership of the /root directory. The next snapshot will not have this problem. You can try, as the regular user:
sudo chown -R $USER: /root that might get you back to normal, but it would be better if it never happened.
3. nVidia cards are failing on first install because the reboot function is not working. A reboot is required on nVidia installs. I am working on that.
4. ATI failed... that's a bummer. I expect that it is due to the same driver problem you experienced with the nvidia in that they are not downloading. If you could get me an lspci | grep VGA I can confirm it wants the fglrx driver.
5. Sizing. I am going to guess that you are using a monitor not attached to hdmi when you see the big screen. What is happening here is that it defaults to an HDMI output, however things have been changed so that AVWizard displays on ALL outputs at the same time, so it is piping to your monitor with the HDMI settings. If you press the number which correlates to your output, it will resize itself properly (eg 1 for VGA1). The old way, you wouldn't have a display at all, just a blank screen. I am keeping this this way, because I am trying to open up some multiple monitor scenarios in the future, and I figure an odd display is better than a black screen.
I believe an apt-get update must not be happening though it should... there is one in the firstrun file I edited to try and fix all the other ATIs... perhaps I broke it.
Again, can't thank you enough for testing and reporting back.
Coley... We are doing so much testing on various distros that fluffy is running out of space. Those broken .iso's eat up a lot of useless space. Try instead to rename whatever snapshot you have to the new name, or even the new name.part and run the zsync... it should just pick up and go.
