October 2004 - openSUSE Autoinstall - openSUSE Mailing Lists

Interactive option checked BEFORE scripts?
by Jesse Keating 25 May '05

25 May '05

I'm using the modified.xml method of dynamic autoinstall control files. One of the things I wanted dynamic was the interactive or not choice, controlled by: <mode> <confirm config:type="boolean">false</confirm> If this was set to true, it should be interactive. I have this being set in modified.xml, however it does not take effect. Is this option checked BEFORE the pre-scripts run? -- Jesse Keating RHCE Pogo Linux -- Linux Systems Engineer tel: (888) 828-7646 ex: 436

3 2

Re: [suse-autoinstall] PXE install fails with SCSI disks
by Steve Glines 07 Dec '04

07 Dec '04

Hi Anas, Thanks for the help. I've made all the fixes you and Marcin Kurc suggested but the system still refuses to see the scsi disks. Here is the data. The target system is an HP Proliant ML350 G3 with a single 40GB SCSI disk. The script shown in sles9/CD1/docu/RELEASE-NOTES.en.html doesn't work so I've modified it thus (feel free to reuse it): #From the top directory umask 0 mkdir -p sles9/CD1 # now copy the contents of SLES CD1 into this directory echo "Mount CD1" read x mount /dev/cdrom sleep 10 cp -r /cdrom/* sles9/CD1 eject mkdir -p core9/CD1 # now copy the contents of SLES CD2 into this directory echo "Mount CD2" read x sleep 10 mount /dev/cdrom cp -r /cdrom/* core9/CD1 eject mkdir -p core9/CD2 # now copy the contents of SLES CD3 into this directory echo "Mount CD3" read x sleep 10 mount /dev/cdrom cp -r /cdrom/* core9/CD2 eject mkdir -p core9/CD3 # now copy the contents of SLES CD4 into this directory echo "Mount CD4" read x sleep 10 mount /dev/cdrom cp -r /cdrom/* core9/CD3 eject mkdir -p core9/CD4 now copy the contents of SLES CD5 into this directory echo "Mount CD5" read x sleep 10 mount /dev/cdrom cp -r /cdrom/* core9/CD4 eject mkdir -p core9/CD5 now copy the contents of SLES CD6 into this directory echo "Mount CD6" read x sleep 10 mount /dev/cdrom cp -r /cdrom/* core9/CD5 eject ln -s sles9/CD1/boot boot ln -s sles9/CD1/content content ln -s sles9/CD1/control.xml control.xml ln -s sles9/CD1/media.1 media.1 mkdir -p yast echo "/sles9/CD1 /sles9/CD1 /core9/CD1 /core9/CD1" > yast/instorder echo "/sles9/CD1 /sles9/CD1 /core9/CD1 /core9/CD1" > yast/order --------------------------------- After PXE booting the system stalls when it can't find a hard disk. When I look in /var/log/boot.log I find: kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter errorno=2 If I run "/sbin/modprobe -s -k scsi_hostadapter" directly from a shell I get "Kernel requires old modprobe no /sbin/modprobe.old." ------------------------------------------- Here is the current line from my default file: label suse kernel suse.kernel append initrd=suse.root ramdisk_size=65536 \ install=http://10.0.3.11/suse ---------------------------------------------- Here is the output of "find . -type d": . ./sles9 ./sles9/CD1 ./sles9/CD1/SLES-LICENSE ./sles9/CD1/SLES-LICENSE/cz ./sles9/CD1/SLES-LICENSE/de ./sles9/CD1/SLES-LICENSE/en_US ./sles9/CD1/SLES-LICENSE/es ./sles9/CD1/SLES-LICENSE/fr ./sles9/CD1/SLES-LICENSE/it ./sles9/CD1/SLES-LICENSE/nl ./sles9/CD1/SLES-LICENSE/pl ./sles9/CD1/SLES-LICENSE/pt_BR ./sles9/CD1/boot ./sles9/CD1/boot/loader ./sles9/CD1/docu ./sles9/CD1/docu/de ./sles9/CD1/docu/en ./sles9/CD1/docu/es ./sles9/CD1/docu/fr ./sles9/CD1/docu/HOWTOs ./sles9/CD1/docu/it ./sles9/CD1/docu/ja ./sles9/CD1/docu/ko ./sles9/CD1/docu/pt_BR ./sles9/CD1/docu/zh_CN ./sles9/CD1/dosutils ./sles9/CD1/dosutils/dparam ./sles9/CD1/dosutils/ext2tool ./sles9/CD1/dosutils/ext2tool/ext2fs ./sles9/CD1/dosutils/ext2tool/linux ./sles9/CD1/dosutils/ext2tool/src ./sles9/CD1/dosutils/ext2tool/sys ./sles9/CD1/dosutils/fips ./sles9/CD1/dosutils/fips/fips15 ./sles9/CD1/dosutils/fips/fips15/restorrb ./sles9/CD1/dosutils/fips/fips15/source ./sles9/CD1/dosutils/fips/fips20 ./sles9/CD1/dosutils/fips/fips20/restorrb ./sles9/CD1/dosutils/fips/fips20/source ./sles9/CD1/dosutils/gtar109 ./sles9/CD1/dosutils/gzip ./sles9/CD1/dosutils/install ./sles9/CD1/dosutils/lfn ./sles9/CD1/dosutils/loadlin ./sles9/CD1/dosutils/loadlin/doc ./sles9/CD1/dosutils/loadlin/src ./sles9/CD1/dosutils/ltools ./sles9/CD1/dosutils/pkunzip ./sles9/CD1/dosutils/putty ./sles9/CD1/dosutils/rawrite ./sles9/CD1/dosutils/rawwritewin ./sles9/CD1/dosutils/tightvnc ./sles9/CD1/dosutils/untgz ./sles9/CD1/dosutils/weirdx ./sles9/CD1/dosutils/weirdx/config ./sles9/CD1/dosutils/xfs186 ./sles9/CD1/dosutils/xfs32-11 ./sles9/CD1/dosutils/zipzp715 ./sles9/CD1/media.1 ./sles9/CD1/suse ./sles9/CD1/suse/i586 ./sles9/CD1/suse/noarch ./sles9/CD1/suse/nosrc ./sles9/CD1/suse/setup ./sles9/CD1/suse/setup/descr ./sles9/CD1/suse/src ./sles9/CD1/yast ./sles9/CD1/yast/core9 ./sles9/CD1/yast/core9/media.1 ./sles9/CD1/yast/core9/suse ./sles9/CD1/yast/core9/suse/setup ./sles9/CD1/yast/core9/suse/setup/descr ./core9 ./core9/CD1 ./core9/CD1/media.1 ./core9/CD1/suse ./core9/CD1/suse/i586 ./core9/CD1/suse/i686 ./core9/CD1/suse/noarch ./core9/CD1/suse/setup ./core9/CD1/suse/setup/descr ./core9/CD2 ./core9/CD2/media.2 ./core9/CD2/suse ./core9/CD2/suse/i586 ./core9/CD2/suse/i686 ./core9/CD2/suse/noarch ./core9/CD3 ./core9/CD3/media.3 ./core9/CD3/suse ./core9/CD3/suse/i586 ./core9/CD3/suse/i686 ./core9/CD3/suse/noarch ./core9/CD3/suse/src ./core9/CD4 ./core9/CD4/media.4 ./core9/CD4/suse ./core9/CD4/suse/nosrc ./core9/CD4/suse/src ./core9/CD5 ./core9/CD5/media.5 ./core9/CD5/suse ./core9/CD5/suse/nosrc ./core9/CD5/suse/src ./yast Marcin Kurc wrote: > > for graphical install you can say 'textmode=0' after 'install*' > please send me your 'default' file and output of 'find . -type d' in the > suse top directory > > > > thanks, > > Marcin Kurc > Linux Impact Team > Novell, Inc > > (973) 493-6235 > >>>>Steve Glines <sglines(a)is-cs.com> 09/01/04 3:37 pm >>> > Thanks - I missed that one and was following the instructions that came > with SUSE 9.1 Pro. It still boots into the non-X format via PXE and X > when I do a CDROM install. Is there a way to make it boot into Graphics > mode. The lab I'm building is supposed to simulate the experience of > installing via CDROM. By the way this is going to go into HP's main > learning lab. The Red Hat version is being used 30-50 times a day. > > Now I'm getting "Network error 404 not found." > > Cheers > Steve > > Marcin Kurc wrote: > >> >>it is not a problem with PXE, your installation tree is not configured >>correctly >>You should either use SLES9 system to build the tree or configure it >>according to the docu/RELEASE-NOTES.en.html which can be found on cd #1 >> >>Also, you need to point you install to top dir not CD1 i.e. >>'install=_/http://10.0.3.11/suse/_' >> >> >> >>thanks, >> >>Marcin Kurc >>Linux Impact Team >>Novell, Inc >> >>(973) 493-6235 >> >>>>>Steve Glines <sglines(a)is-cs.com> 09/01/04 2:30 pm >>> >>I’m building a PXE install lab for SUSE and other flavors of Linux. >> >>The DHCP and tftp servers are working. Note: I can fully install Red Hat >>from this lab but SUSE (SLES9 rc5) shows the following symptoms: >> >>1.a cdrom install on the target system runs to completion in graphics >>mode. System is an HP PC with SCSI disk. >>2.PXE install runs in non X-window mode (text) and fails to load scsi >>controllers – cannot find any disks. Fails even when modules are >>manually added. >> >>Here is the content of /tftpboot/pxelinux.cfg/default: >> >>default suse >>prompt 1 >>display boot.msg >>timeout 200 >> >>label redhat >> kernel redhat.kernel >> append initrd=redhat.root ramdisk_size=65536 >> >>label suse >> kernel suse.kernel >> append initrd=suse.root ramdisk_size=65536\ >>install=http://10.0.3.11/suse/CD1/ >> >>The file suse.kernel was copied from /boot/loader/linux in CD1 while >>suse.root was taken from /boot/loader/initrd in the same CD. >> >>I copied the contents of each CD into their own directories – I have CD1 >> – CD6 in the directory specified by http://10.0.3.11/suse/CD[1-6]. >> >>My test target system is a Celeron with 256MB Ram and an IDE disk; this >>setup fully installs SLES9. The only material change from this to the >>production lab is that the target system in the production lab has a >>SCSI disk and 1GB of ram. -- Steve Glines voice: 978-952-6340 www.is-cs.com fax: 978-952-8524 145 Foster Street cell: 617-549-7274 Littleton MA 01460 I'm a complex person. I have a real and an imaginary part.

3 6

Newbie requires help with autoinstall on 9.0 - no display!
by mark＠atoneassociates.com 04 Nov '04

04 Nov '04

Hi - I am a newbie to linux so please forgive my ignorance. I recently tried to install 9.0 on to my machine. Its set up as dual boot with windows 98. The windows works fine (well as god as it normally does). When I boot into Linux everything works fine I think but when I am meant to get a login screen the monitor goes blank and the on light flashes like the computer isn't communicating with it anymore. The computer still seems to work bcasue if I hit any key I get some sort of repsonse but I still can't see anything. During the installation I had a warning message about the graphics card an Nvidia. I read some stuff and saw that I need to download different drivers. The problem is of course that I don't have a system to work on (at least I don't know how to access it wihtout the monitor!). Can anyone help please? Do I need to reinstall differently? Thanks for your patience, Mark

2 1

Password not being set right
by Jesse Keating 30 Oct '04

30 Oct '04

I've got an issue where my password for root isn't being set right. Or at all for that matter. My autoinstall file has the following sections: <security> <console_shutdown>reboot</console_shutdown> <cracklib_dict_path>/usr/lib/cracklib_dict</cracklib_dict_path> <cwd_in_root_path>no</cwd_in_root_path> <cwd_in_user_path>no</cwd_in_user_path> <displaymanager_remote_access>no</displaymanager_remote_access> <enable_sysrq>yes</enable_sysrq> <fail_delay>3</fail_delay> <faillog_enab>yes</faillog_enab> <gid_max>60000</gid_max> <gid_min>101</gid_min> <kdm_shutdown>all</kdm_shutdown> <lastlog_enab>yes</lastlog_enab> <obscure_checks_enab>yes</obscure_checks_enab> <pass_max_days>99999</pass_max_days> <pass_max_len>12</pass_max_len> <pass_min_days>0</pass_min_days> <pass_min_len>5</pass_min_len> <pass_warn_age>7</pass_warn_age> <passwd_encryption>md5</passwd_encryption> <passwd_use_cracklib>yes</passwd_use_cracklib> <permission_security>secure</permission_security> <run_updatedb_as>nobody</run_updatedb_as> <uid_max>60000</uid_max> <uid_min>100</uid_min> </security> <users config:type="list"> <user> <encrypted config:type="boolean">true</encrypted> <username>root</username> <user_password>$1$QyzzjhWY$/wFY11PqReGKyxDSydLgh.</user_password> <forename></forename> <surname></surname> </user> </users> However once my system installs, root has NO password. And furthermore, if I run yast2 on the installed system, it would appear that the password encription is set to DES rather than MD5. Is this just flatly ignored, and since my password is too long for DES I get no password instead? Please help me to understand what is going on here. -- Jesse Keating RHCE Pogo Linux -- Linux Systems Engineer tel: (888) 828-7646 ex: 436

2 2

Network Config not used
by Jesse Keating 30 Oct '04

30 Oct '04

I have network config set up so that eth0 is setup for DHCP: <networking> <dns> <dhcp_hostname config:type="boolean">true</dhcp_hostname> <dhcp_resolv config:type="boolean">true</dhcp_resolv> <domain></domain> <hostname></hostname> <nameservers config:type="list"/> <searchlist config:type="list"/> </dns> <interfaces config:type="list"> <interface> <bootproto>dhcp</bootproto> <device>eth0</device> <module></module> <startmode>onboot</startmode> <wireless>no</wireless> </interface> </interfaces> <routing> <ip_forward config:type="boolean">false</ip_forward> <routes config:type="list"/> </routing> </networking> However once the system is installed, running yast2 shows that NO network devices were configured, and I have no network. Is there something wrong with my script, or is this yet another SUSE bug? -- Jesse Keating RHCE Pogo Linux -- Linux Systems Engineer tel: (888) 828-7646 ex: 436

3 4

Packages failing to install
by Nicholas DeClario 28 Oct '04

28 Oct '04

Hey guys. I am using SLES9 and have setup a custom package selection in the installer. Pretty much in the suse/setup/descr directory I created another .sel file, linked it all in and it's working. I have a list of packages custom to that .sel file that install fine. However, I recently started adding packages to it that are for some reason not installing. These are packages that are already found in the suse CORE CDs. Some I added work fine, others do not. I added telnet and telnet-server to the list. Telnet installs fine, telnet-server does not. I have scanned the logs in /var/log/YaST and have not even found any references to the packages that are not getting installed. I don't understand why this is happening. Thanks, -Nick

3 4

RE: cd-creator "skipping" files?
by anders.g.karlsson＠seb.se 28 Oct '04

28 Oct '04

Hi again, thought I'd try again and see if anyone has any hints for me. Perhaps someone knows where I can start looking to find out which application or code is responsible for copying the correct initrd, linux kernel, isolinux.bin, isolinux.cfg and other system files into the correct directory structure from which the iso is then created. I have a hard time dechiphering the y2log to find the correct referenses. Any hint whatsoever would be appreciated. Regards, Anders K.

2 1

Creating a bootable CD with info file
by fraser_bailey＠agilent.com 27 Oct '04

27 Oct '04

Hi does anyone know how to create a bootable CD which includes an info file? linuxrc is supposed to look in the root directory of the initrd, but I can't figure out how to get it into the initrd and then rebuild the CD. I've tried the instructions at http://www.tcm.phy.cam.ac.uk/~mr349/suse/boot.html after having modified the boot/loader/initrd file but I get an isolinux checksum error when I boot the CD. All I have to show is about 15 unusable CDs! any help would be appreciated

2 1

cd-creator "skipping" files?
by anders.g.karlsson＠seb.se 27 Oct '04

27 Oct '04

Hi all, I'm having some serious difficulty getting my home-made SLES9 installation CD working. I used to be able to create a fully functioning iso image, but after I upgraded to the latest patches things have stopped working. I use the autoyast and cd-creator modules to create my xml configuration and the generating the iso. For some reason I'm suddenly not getting anything copied into my boot/loader directory. So, I'm missing the initrd, isolinux.bin, isolinux.cfg among others. This makes the y2mkiso fail of course. Am I missing some fundamental knowledge here? I'm using: yast2-cd-creator Version 2.9.11, Release 0.2 autoyast2 Version 2.9.45, Release 0.2 All insight to the matter is welcome. Regards, Anders Karlsson Network & Internet SEB IT Mobile phone +46 70 639 30 57 Office phone +46 8 639 30 57 Postal address R C5, 106 40 Stockholm Visiting address Rissneleden 110 E-mail anders.g.karlsson(a)seb.se www.seb.net > > >

1 0

Skips ntp.
by Miro Barby 25 Oct '04

25 Oct '04

Hi. My problem is when i do a Minimal installation based on the default Minimal.sel file The ntp section in my autoinst.xml works out fine. With the exact same autoinst.xml where only the software sel. is different, the entire ntp section is skipped.?? Only difference in autoinst.xml: <software> <base>easy</base> </software> <software> <base>Minimal</base> </software> Any ideas.. Thanks in advance Miro.

1 0