February 2004 - openSUSE Autoinstall - openSUSE Mailing Lists

connection to internet-server
by ACOTEC 12 Feb '04

12 Feb '04

Hi to all. having installed the SuSE Linux 9,0 by the CD's, I've got the problem that I can't connect to my service provider in the internet. I would prefer to configurate with DHCP with YaST2. the following part of this message contains several terms which I don't know in english language and I try to translate with my restricted english knowledges from my spanish version of Linux. So please excuse my translations. My system consists in two computers, both running actually on Windows. They are connected each other by a router (3Com 812 ADSL Router) and with Windows they work with internet through a service provider. In one computer I have installed the Linux with a partition, leaving operational the Windows. My PC works with a card, automatically configurated as eth0. A ping test was successful, but my Konqueror does not find my service provider. When I try to connect with the Konqueror, it says: There was produced an error charging http:www.suse.de Unknown machine www.suse.de I guess that the mistake(s) are in my internet configuration. Could somebody tell me please how to make a right configuration? When I enter YaST -> net devices -> net card -> modify -> edit -> net configuration, I have following window: net device: eth0 in the frame: select configuration method I have marked "authomatic adress (via DHCP)" in the lower frame: detailed configuration, there I have marked "change computer name via DHCP" In the lower part there are several buttons. If I click on "computer name and configuration of server names" it opens the window where by default it puts in "Computer name" : linux and in "domaine name" : local under the next button "DHCP client options" it opens the window, and should I mark there "requesting broadcast answers"? and in "DHCP client identifier" what shall I write? In "computer name for sending" it says by default AUTO : shall I leave it so? With the button "routing" the window which opens has a part where it says "routing" and a position to enter data called gateway. By default it's empty. Shall I leave it so? Below that I can mark "activate rerouting IP". Do I have to mark it? Cliquing the button Hardware specifications it opens a window "manual net card configuration". There it says Net device: eth0 In a frame "Kernel module" it says: Module name: "via-rhine" The position "Options" is empty Please help me solve this situation and thanks in advance for your patience. W. Schuch

2 1

[suse-autoinstall] Installation from diskettes
by Manuel Balderrábano 12 Feb '04

12 Feb '04

I already sent this query but no one helped me yet, I really need to get a SuSE 9.0 working as fast as possible! Please, somebody? Hi to all. I am trying to install SuSE 9.0 from the suse ftp server. 1.- I created the boot, modules1 and modules3 diskettes. 2.- Booted from first diskette, selected install-manually. 3.- Loaded network card's module(Realtek 8139) from modules3. 4.- Configured network IP, gateway and DNS (ping to the new PC from other PC in the network responds ok) 5.- Tried to install from FTP 195.135.221.130, but after a while I get: Failed to connect to FTP server What am I doing wrong? Thanks in advance.

2 1

autoyast.xml & eject
by grant williamson 11 Feb '04

11 Feb '04

Instead of rebooting at the end of a text based autoyast install, is there a simply option which prompts or automatically ejects the cd? -- grant williamson <traxtopel(a)fastmail.fm>

2 2

slec autoinstall
by grant williamson 11 Feb '04

11 Feb '04

Why is there no autoyast2 included with slec-1.0? It is possible to build it via the autoyast2-installation src rpm, but then slec misses alice & some perl rpms (which I grabbed instead from suse-8.1). Having said that I managed to get something running. Here comes the problem, irrespective if I hardcode the X config for an IBM Thinkpad T20 in my autoyast.xml file, it does get read. It always defaults to a 640x480 8 colour vesa screen. Could this be to do with incorrect rpms? or is there a more general issue with autoyast on slec-1.0? -- grant williamson <traxtopel(a)fastmail.fm>

3 2

Problems with autoinstall of sles8 via HTTP
by Jeff Crow 10 Feb '04

10 Feb '04

I am having difficulties with the autoinstall of sles8 via HTTP. When I boot up, I receive the following error after the hardware detection and activation of usb devices: "Could not find the UnitedLinux Installation Source. Activating manual setup program." So I then go through the manual screen and verify that my network card (eth0) is loaded, and select 'Start Installation / System > Start Installation / Update > network > HTTP. If I choose 'Automatic Configuration via DHCP?', I get this error: "DHCP Configuration Failed." If I choose no on 'Automcatic Configuration via DHCP" and manually put in my static IP address, netmask and gateway, I get this error: "An error occurred during the network configuration. Probably your network card was not recognized by the kernel!" Here are some more details of my setup. My installation source is loop mounted ISO's setup as described here: http://www.suse.de/~nashif/autoinstall/faq.html#id2459380. I am using the SP3 kernel, initrd and have the driverupdate at the root of the source as suggested. I have tried this on multiple machines with the same result. I would appreciate any suggestions or solutions. Thanks, Jeff

3 2

FTP installation from diskettes
by Manuel Balderrábano 10 Feb '04

10 Feb '04

Hi to all. I am trying to install SuSE 9.0 from the suse ftp server. 1.- I created the boot, modules1 and modules3 diskettes. 2.- Booted from first diskette, selected install-manually. 3.- Loaded network card's module(Realtek 8139) from modules3. 4.- Configured network IP, gateway and DNS (ping to the new PC from other PC in the network responds ok) 5.- Tried to install from FTP 195.135.221.130, but after a while I get: Failed to connect to FTP server What am I doing wrong? Thanks in advance.

1 0

various problems with SLSS
by Tom Davidson 10 Feb '04

10 Feb '04

I've got a number of problems with SLSS autoinstall, ranging from minor to serious: 1) *minor* Somewhere, somehow, the initial part of the textmode (and prolly X) installer runs in German. It switched to English as configured once it has the autoinstall XML file. But it hald reverts to German when installing the RPMs, as the descriptions are in German. The resulting box is installed in English OK however. I'm installing via PXE, and I haven't specified anything on the append line for language, but even if I specify on it, I still get the same. 2) *serious* I'm installing on servers ranging from HP DL360 G2/G3s up to possible DL580s (developing on a DL360 G2). The raid controller is detected and the module loaded fine, but when it comes to allocating the partitioning, it fails saying "no free space available on /dev/cciss/c0d0". There will be partitions on there as I've constantly rebuilding testing, but it shouldn't care as I've specified <use>all</use> for the disk /dev/cciss/c0d0 (configured in RAID 1 obviously). This is a pretty unhelpful error message for debugging purposes - where can I suitable logging to tell me why this fails? I've looked in /var/adm/autoinstall, /var/log/YaST2, /tmp/YaST2-####/pre-scripts. Where else does stuff get logged? I've tried a pre-install script hack of dd if=/dev/zero of=/dev/cciss/c0d0 bs=1024 count=1, and it doesn't work when booting with a system that already has partitions - presumably these must get cached earlier on somewhere (a bad practice IMHO). But if I abort the installation, or reboot and try again, nothing is there to get cached, and it half works, which brings me on to the third problem. 3) *serious* I've got a number of partitions configured, including a fixed size of swap (I've included my autoinstall file at the end - apologies for the length). / gets configures as a primary, and I let YaST sort out the rest, which numbers swap c0d0p9. So from issue 3 above, when it installs over a blank disk, it successfully creates all the filesystem partitions, but moans about being unable to create swap with another very unhelpful error message: "could not set up swap partition /dev/cciss/c0d0p9". Why should it successfully create everything but swap? It's not a space issue (they have 18Gb disks), because the "max" setting for /usr/local gobbles up the space that swap should have taken. 4) *concerning* I install SP3 via a finish script that is called from the finish script in the autoinstall file as below. However, when I install it, the kernel it installs hangs on reading the partition table for /dev/cciss/c0d0. I've narrowed this down to acpi, so I've put acpi=off into the kernel parameters section on the autoinstall file, but I'm certain that it shouldn't do that! Please can anyone help with these, especially the serious ones. I'm sure I have more, but I can't think of them right now... Cheers, Tom <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/YaST2/include/autoinstall/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <configure> <users config:type="list"> <user> <encrypted config:type="boolean">false</encrypted> <user_password>foo</user_password> <username>root</username> </user> </users> <networking> <dns> <dhcp_hostname config:type="boolean">false</dhcp_hostname> <dhcp_resolv config:type="boolean">false</dhcp_resolv> <domain>localnet</domain> <hostname>susedev-lin-01</hostname> </dns> <interfaces config:type="list"> <interface> <device>eth0</device> <bootproto>dhcp</bootproto> <startmode>onboot</startmode> </interface> <interface> <device>eth1</device> <bootproto>static</bootproto> <broadcast>10.10.10.255</broadcast> <ipaddr>10.10.10.10</ipaddr> <netmask>255.255.255.0</netmask> <network>10.10.10.0</network> <startmode>onboot</startmode> </interface> </interfaces> <routing> <routes config:type="list"> <route> <destination>default</destination> <device>-</device> <gateway>10.144.128.1</gateway> <netmask>-</netmask> </route> </routes> </routing> </networking> <scripts> <chroot-scripts config:type="list"> <script> <filename>chroot.sh</filename> <interpreter>shell</interpreter> <source> <![CDATA[#this is chroot #!/bin/sh # Functions die() { echo "$@";exit 1; } # Global Variables NFS_SERVER=foo NFS_PATH=/img NFS_MOUNT_POINT=/a export NFS_SERVER NFS_PATH NFS_MOUNT_POINT # Local Variables BASE=${BASE:-"/mnt"} # mount up the finish scripts test -d $NFS_MOUNT_POINT || mkdir $NFS_MOUNT_POINT test -d $NFS_MOUNT_POINT/suse || \ mount $NFS_SERVER:$NFS_PATH $NFS_MOUNT_POINT || die "couldn't perform NFS mount" fin=$NFS_MOUNT_POINT/suse/scripts # copy the finish scripts test -d $BASE/fin || mkdir $BASE/fin cd $BASE/fin && rm * cp -p $fin/* . 2> /dev/null # unmount the finish scripts cd / umount $NFS_MOUNT_POINT #end chroot]]> </source> </script> </chroot-scripts> <post-scripts config:type="list"> <script> <filename>postinst.sh</filename> <interpreter>shell</interpreter> <source> <![CDATA[#this is postinst #!/bin/sh #FAKE=echo # Functions die() { echo "$@";exit 1; } # Global Variables NFS_SERVER=foo NFS_PATH=/img NFS_MOUNT_POINT=/mnt export NFS_SERVER NFS_PATH NFS_MOUNT_POINT # Local Variables # run the finish scripts cd /fin echo "params: 1=$1 2=$2 3=$3 4=$4 5=$5" script_list=${@:-"F*"} script_list="F*" for i in $script_list do test -x $i || interpreter="sh" echo "### executing $i" $FAKE $interpreter ./$i if [ $? = 10 ]; then die "argh! cannot continue. see /var/adm/autoinstall/logs/" fi unset interpreter done cd / #$FAKE rm -rf /fin #end postinst]]> </source> </script> <script> <filename>setrootpw</filename> <interpreter>shell</interpreter> <source> <![CDATA[/usr/bin/perl -pi -e 's#^root::.*$#root:<MDD5Encryption>:::::::\n#' /etc/shadow exit 0]]> </source> </script> </post-scripts> <pre-scripts config:type="list"> <script> <filename>preinst.sh</filename> <interpreter>shell</interpreter> <source> <![CDATA[#this is preinst dd if=/dev/zero of=/dev/cciss/c0d0 bs=1024 count=1 #end preinst]]> </source> </script> </pre-scripts> </scripts> </configure> <install> <bootloader> <location>mbr</location> <loader_type>grub</loader_type> <loader_device>/dev/cciss/c0d0</loader_device>   <kernel_parameters>acpi=off</kernel_parameters> </bootloader> <general> <clock> <hwclock>UTC</hwclock> <timezone>Europe/London</timezone> </clock> <keyboard> <keymap>english-uk</keymap> </keyboard> <language>en_GB</language> <mode> <confirm config:type="boolean">false</confirm> <forceboot config:type="boolean">false</forceboot> <reboot config:type="boolean">true</reboot> </mode> <mouse> <id>00_ps2</id> </mouse> </general> <partitioning config:type="list"> <drive> <device>/dev/cciss/c0d0</device> <use>all</use> <partitions config:type="list">  <partition> <filesystem config:type="symbol">ext3</filesystem> <mount>/</mount> <size>1g</size> <partition_type>primary</partition_type> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <mount>/usr</mount> <size>1g</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <mount>/var</mount> <size>4g</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <mount>/home</mount> <size>2g</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <mount>/usr/local</mount>  <size>max</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <mount>swap</mount>  <size>2g</size> </partition> </partitions> </drive> </partitioning> <software> <base>Minimal</base> <packages config:type="list"> <package>xntp</package> <package>rcs</package> <package>cvs</package> <package>xinetd</package> <package>tcpdump</package> <package>tcpd</package> <package>screen</package> </packages> </software> </install> </profile> -- Dr. Tom Davidson RHCE Unix Engineer Energis (http://www.energis.com)

2 1

VS: DASD_Parameter, linuxrc, does not recognzie
by Steen Bank Johnsen 10 Feb '04

10 Feb '04

> I have tried to use parmfile to setup the DASD specification for > autoinstall. But no matter how I put it in the parmfile linuxrc does not > recognize it. I have tried mixed case,upper case and lower case. But > nothing helps, has any actually succeded in this ? I'm using SLES8 64 bit > for s390. > > Regards, > > Steen

1 0

Typo on loop mounting instructions?
by Jeff Crow 10 Feb '04

10 Feb '04

I was just wondering if there was a typo error on the instructions for "creating an installation source by loop mounting ISO images instead of copying them to the local disk". The instructions can be found here: http://www.suse.de/~nashif/autoinstall/faq.html#id2459380 The second to last instruction says to do the following: printf "/SLES/CD1\t/SLES/CD1" >> yast/instorder However, there is no CD1 under the SLES directory because there is only one CD for this. Is this a mistake?? Thanks, Jeff

2 1

nfs-Verzeichnisse werden nicht gemountet
by Stefan Preihs 09 Feb '04

09 Feb '04

Hallo ! Ich habe ein privates kleines Computernetz mit 3 Computern. Ich verwende Suse 9.0. 1. Frage: Bei Comp. A habe ich als nfs-server Verzeichnise freigegeben. Comp. B kann diese als nfs-client aber nicht mounten. Es kommt die Fehlermeldung: "Die nfs-Verzeichnisse, die in der Datei etc/fstab eingetragen sind, konnten nicht gemountet werden." Das jeweilige anpingen funktioniert. Die Comp. haben eine statische IP-Adresse (10.100.0.1/3) mit Subnet mask 255.255.255.0. Gleichzeitig verwende ich sie auch als Samba-Netz, d.h. Comp. A ist der Samba Server und Comp. B und C sind Windows Computer. Nur bei Comp. B habe ich Linux und Windows installiert. Ich möchte also bei Comp. B, wenn er in linux arbeitet, auch auf Comp. A mit nfs zugreifen. Ich habe Comp B auch als Samba-client mit YaST2 konfiguriert. Was könnte der Fehler sein? Hängt das mit Samba zusammen? 2. Frage: Wenn Comp. B als linux gestartet ist, kann er auch nicht mittels Samba auf A zugreifen. A ist Samba-server und B ist als Samba-client konfiguriert. Es funktioniert nur wenn ich in den browser (netzwerkumgebung) die IP von A eingebe. Den Namen von A findet er nicht. Ich habe versucht bei den DNS Einstellungen einiges zu verändern und auszuprobieren. Es geht aber nicht. Stefan Mit schönen Grüßen von Yahoo! Mail - http://mail.yahoo.de

1 0