The problem seems to be that it's trying to download "driverupdate" from

As it turns out it was a corrupted control.xml in the source tree. Thanks to those who sent their suggestions and advice! Paul -----Original Message----- From: Paul Anthony Rae (QC/EMC) [mailto:Paul.Anthony.Rae@ericsson.com] Sent: May 19, 2005 5:33 PM To: suse-autoinstall@suse.com Subject: RE: [suse-autoinstall] Network Installation Problems Well I am still battling with this issue. I still get big red "Error in Installation" trying to do an autoinstall over the network. Possible issues: 1) I have no DNS server on my little private network where I am attempting the install. Is this a problem? 2) Control file validity checks out ok, but maybe there is something busted? What kinds of problems might lead to 'Error in Installation" just after control file download, assuming the control file is sane? Below is the last version of the control file I have been using. Any weirdnesses I am missing? Paul <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/autoinstall/dtd/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <configure> <runlevel> <default>3</default> </runlevel> </configure> <install> <general> <clock> <hwclock>UTC</hwclock> <timezone>US/Pacific</timezone> </clock> <keyboard> <keymap>english-us</keymap> </keyboard> <language>en_US</language> <mode> <confirm config:type="boolean">false</confirm> <forceboot config:type="boolean">false</forceboot> </mode> <mouse> <id>ignore</id> </mouse> </general> <partitioning config:type="list"> <drive> <device>/dev/cciss/c0d0</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>13.9GB</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/usr</mount> <partition_id config:type="integer">131</partition_id> <partition_type>primary</partition_type> <size>4GB</size> </partition> <partition> <crypt>twofish256</crypt> <format config:type="boolean">false</format> <loop_fs config:type="boolean">false</loop_fs> <mount>Swap</mount> <partition_id config:type="integer">131</partition_id> <size>4GB</size> </partition> <partition> <crypt>twofish256</crypt> <format config:type="boolean">false</format> <loop_fs config:type="boolean">false</loop_fs> <mount></mount> <partition_id config:type="integer">131</partition_id> <size>12GB</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <fstopt>acl</fstopt> <label></label> <loop_fs config:type="boolean">false</loop_fs> <mount>/opt</mount> <mountby config:type="symbol">device</mountby> <noauto config:type="boolean">false</noauto> <partition_id config:type="integer">131</partition_id> <size>6GB</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/tmp</mount> <partition_id config:type="integer">131</partition_id> <size>4GB</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/var</mount> <partition_id config:type="integer">131</partition_id> <size>max</size> </partition> </partitions> <use>all</use> </drive> </partitioning> <report> <errors> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">0</timeout> </errors> <messages> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">0</timeout> </messages> <warnings> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">0</timeout> </warnings> <yesno_messages> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">0</timeout> </yesno_messages> </report> <software> <addons config:type="list"> <addon>Base-System</addon> <addon>YaST2</addon> </addons> <base>Minimal</base> </software> </install> </profile> -----Original Message----- From: Paul Anthony Rae (QC/EMC) [mailto:Paul.Anthony.Rae@ericsson.com] Sent: May 10, 2005 11:32 AM To: suse-autoinstall@suse.com Subject: RE: [suse-autoinstall] Network Installation Problems Quite sure. The distro I have is 9.0 enterprise, I have checked and double checked. Also I was able to complete an interactive network installation just fine so I haven't the foggiest what is going wrong when I try to get it to auto-install. Is the request for driverupdate triggered by the control file? Is it possible somehow the control file I have generated is asking for it, or needs to be set to ignore it or somesuch? It's the only thing I can think of, but I can't see anything in the control file that clues me in to what is happening. Paul -----Original Message----- From: Michael Marion [mailto:mmarion@qualcomm.com] Sent: May 9, 2005 6:20 PM To: Paul Anthony Rae (QC/EMC) Cc: suse-autoinstall@suse.com Subject: Re: [suse-autoinstall] Network Installation Problems On 9 May, Paul Anthony Rae (QC/EMC) wrote: the

source directory, but no such file exists. After it can't find that file the Installation stops with "Error in Installation".

Are you sure you're not booting from the sp1 cd's linux kernel and initrd files? I don't think I've ever seen a non-sp installer look for the driverupdate file. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com Homer: "I'm not normally a religious man, but if you're up there, save me, Superman!" -- Simpsons -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe@suse.com For additional commands, e-mail: suse-autoinstall-help@suse.com