Successful Alpha2.37 Internet Install - MD Creation "Failed to setup X"

[rocketlynx]

After a successful Clean 8.10 - Alpha2.37 Internet install, everything OK as far as the Core is concerned, even a Windows Vista Orbiter working correctly.  I then wanted to create my MDs that were working with my previous 8.10 - Alpha2.37 installation without any problems.  Upon the first MD's connecting to the DCERouter, the creation ended with a blue screen (of death) and a message that the AVWizard, "Failed to setup X".

A second time yielded the same results.  I tried a second Media Director and it also gave the same results.  After checking the /etc/X11 directories for the diskless MDs, I found that both had No xorg.conf files created.  I watched carefully as each MD tried to reboot from the core and at some point the MD wanted to download and install packages that had to do with the nVidia drivers necessary for each MDs on-motherboard nVidia 8300 display chipset.

Messages going to fast to write all information correctly, I saw time out failures from "archive.ubuntu.org, deb.linux.org, etc., all dealing, apparently with the glx-180-pluto-nvidia-video-drivers necessary form the diskless MDs.

These same drivers downloaded and installed correctly for the core just yesterday.

Is the source list for the diskless creation of MDs incorrect or different from the core's basic install script source list? These same MDs have been working and installable from my previous Alpha2.37 system of which had been built on about Alpha2.19 and constantly upgraded to and included Alpha2.37.  Never a problem before!

The only reason for the re-install was to utilize a new much larger and much needed OS hard drive, rather than the small one the system was originally installed on.

All of the hardware is the same.  The core's PC is the same!  The MDs are the same!  The only thing that is different is LinuxMCE's current installation files or Ubuntu's installation repos and archives but I believe there must be a bad source list for the MD creation default image.

Does anybody have a referrence, correct source list for the MDs, or is the problem somewhere else?


Thanks and Best Regards,

Charles

[team_steeze]

Occasionally, I've noticed that the repositories will go down for a spell.  I was just trying to update my Karmic Koala (kubuntu 9.10) on my laptop last night and some of the repositories were down.  The failure from "archive.ubuntu.org" is no surprise as its supposed to be "us.archive.ubuntu.org.  No worries though because if you take a took at your sources.list, its in there both correctly and incorrectly.  I just # that section out on mine to avoid that error.  It shouldn't have anything to do with the fact that your on a MD now and it worked fine on the core - coincidence.  Here's my sources.list:

Code: [Select]

deb http://www.avenard.org/files/ubuntu-repos/ intrepid  release
deb file:/usr/pluto/deb-cache/ ./
deb http://us.archive.ubuntu.com/ubuntu/ intrepid  main restricted universe multiverse
deb-src http://us.archive.ubuntu.com/ubuntu/ intrepid  main restricted universe multiverse
deb http://us.archive.ubuntu.com/ubuntu/ intrepid-updates  main restricted universe multiverse
deb-src http://us.archive.ubuntu.com/ubuntu/ intrepid-updates  main restricted universe multiverse
deb http://security.ubuntu.com/ubuntu/ intrepid-security  main restricted universe multiverse
deb-src http://security.ubuntu.com/ubuntu/ intrepid-security  main restricted universe multiverse
deb http://deb.linuxmce.org/ubuntu/ intrepid  lmce-alpha-latest lmce-alpha-latest-updates
deb http://debian.slimdevices.com/ stable  main
deb http://packages.medibuntu.org/ intrepid  free non-free
#deb http://archive.ubuntu.com/ubuntu/ intrepid  main universe multiverse
#deb http://archive.ubuntu.com/ubuntu/ universe  main non-free contrib
deb http://deb.linuxmce.org/ubuntu/ 20dev_ubuntu  main
deb http://deb.linuxmce.org/ubuntu/ replacements_debian  main

Your basic issue seems to be that X isn't starting.  You should be able to get X going without the upgraded Nvidia drivers.  You just won't have VDPAU support (if you card supports it) and you'll want to run UI1.
To get you going, log in as root on the MD (http://wiki.linuxmce.org/index.php/Logging_In and run:

Code: [Select]

dpkg-reconfigure xserver-xorgThis should generate a valid enough Xorg.conf to get the A/V Wizard running.  To test, from the terminal run:

Code: [Select]

XAnd an x window system should start
Once you are able to get your Nvidia drivers, run:

Code: [Select]

nvidia-xconfigThat will get you an Xorg.conf with better graphic support.  After you have a new Xorg.conf, always re-run your A/V Wizard.

-team_steeze

[Techstyle]

Rocketlynx,

did doing what team_steeze suggested solve your problem?  I have the same problem with the DVD 0810 Beta install on all my MD's

Techstyle

[Enigmus]

I had this issue as well.  This information was one piece of the puzzle to solve my issue.  Indeed the xorg.conf was not configured.  In my situation, the Xorg.conf took vesa as the driver which persisted in generating the same error.  After switching this to nvida it was smooth sailing.

[rocketlynx]

Rocketlynx,

did doing what team_steeze suggested solve your problem?  I have the same problem with the DVD 0810 Beta install on all my MD's

Techstyle

The repos just happened to be down at the time I was creating a new MD.  I deleted it and later when I tried, it was ok.
Hope this helps.
Charles