openSUSE Autoinstall June 2002

autoinstall@lists.opensuse.org

23 participants
32 discussions

by Marcel Ritter

Hi there! Can anyone tell me - when exactly the pre.sh script is run? I fear that it's run *after* the (re)partitioning takes place, which is no use to me, as I'd like to save some ssh keys and similar stuff from the old partittions and copy it back after installation. Ciao, Marcel ---- Marcel Ritter Linux Betreuer Regionales Rechenzentrum Erlangen ---- Unix _IS_ user friendly... It's just selective about who its friends are.

19 years, 7 months

Installing NIC in SuSE 8.0

by Ken Graham

I don't know if this is the correct place for this question, I got here after reading about DHCP problems in config files in the archives. I've been banging my head against the monitor for a week now trying to get a NIC to work! I've checked, double checked, and had my IT guys check, the configuration and nothing seems to be wrong. I've tried three different cards with the same results; YAST recognizes the cards, and installs the correct module for each card. But, when I ping I get a Destination Host Unreachable error. I've looked for IRQ conflicts, faulty hardware (I took a card out of a Linux box that works and put it in mine - didn't help!), and I've changed a few lines in /etc/sysconfig/network/ifcfg-eth0 , and other config files in there, to values that should of worked. Nothing seems to help. I was wondering if something happened in the installation process that is causing the NIC to not work. If anyone has any suggestions on what to try next I'd REALLY appreciate it. Thanks, Ken Graham

19 years, 7 months

install floppy fails with SuSE 8.0 ftp version

by Kevin Ivory

We have a single AutoYaST2 install floppy that worked fine two weeks ago. Since then our NFS-server doesn't offer the DVD version anymore but a copy of SuSE's FTP version. Now our Auto- YaST2 formats the partitions but says it is unable to mount them. Any ideas what might have changed and what we can do to get it working again? Kevin -- _ | Kevin Ivory | Tel: +49-551-37000041 |_ |\ | | Service Network GmbH | Fax: +49-551-3700009 ._|ER | \|ET | Bahnhofsallee 1b | mailto:Ivory@SerNet.de Service Network | 37081 Goettingen | http://www.SerNet.de/

19 years, 7 months

Intel Board d850gb (chipset ADI 1885) on SuSE 7.3

by Juan Francisco Torres Chacón

Ok, this is the story: The standard configuration using YAST2 in SuSE7.3 (just after installation) didn't detected the sound card (or chipset in this case) Finally, I used "alsaconf" in text mode, and it was detected as "Intel 82820 820 Camino2 AC97" I used "gamix" in Xwindows to "unmute" the sound. Sound is playing, BUT 1- Everything is "quicker" than it should. Every sound or song is played a little quicker than normal..... 2- I get the following messages: - xconsole: Jun 14 09:34:31 winlinux kernel: snd: snd_intel8x0_chip_init: invalid AC'97 codec Jun 14 09:34:31 winlinux kernel: snd: Intel ICH soundcard not found or device busy Jun 14 09:36:34 winlinux insmod: insmod: a module named snd-mixer-oss already exists Jun 14 09:36:34 winlinux insmod: insmod: insmod sound-service-0-3 failed - /var/log/boot.msg (messages when the machine boots) /etc/init.d/rc5.d/S21alsasound start Starting sound driver: intel8x0/lib/modules/2.4.10-4GB/misc/snd-card-intel8x0.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters /lib/modules/2.4.10-4GB/misc/snd-card-intel8x0.o: insmod /lib/modules/2.4.10-4GB/misc/snd-card-intel8x0.o failed /lib/modules/2.4.10-4GB/misc/snd-card-intel8x0.o: insmod snd-card-intel8x0 failed failed <notice>'/etc/init.d/rc5.d/S21alsasound start' exits with status 1 - /var/log/messages Jun 14 09:34:31 winlinux kernel: PCI: Found IRQ 9 for device 00:1f.5 Jun 14 09:34:31 winlinux kernel: PCI: Sharing IRQ 9 with 00:1f.3 Jun 14 09:34:31 winlinux kernel: PCI: Setting latency timer of device 00:1f.5 to 64 Jun 14 09:34:31 winlinux kernel: snd: snd_intel8x0_chip_init: invalid AC'97 codec Jun 14 09:34:31 winlinux kernel: snd: Intel ICH soundcard not found or device busy Jun 14 09:34:31 winlinux kernel: Switching off penguin. Jun 14 09:36:20 winlinux PAM-unix2[975]: session started for user jtorres, service xdm Jun 14 09:36:34 winlinux kernel: PCI: Found IRQ 9 for device 00:1f.5 Jun 14 09:36:34 winlinux kernel: PCI: Sharing IRQ 9 with 00:1f.3 Jun 14 09:36:34 winlinux kernel: PCI: Setting latency timer of device 00:1f.5 to 64 Jun 14 09:36:34 winlinux insmod: insmod: a module named snd-mixer-oss already exists Jun 14 09:36:34 winlinux insmod: insmod: insmod sound-service-0-3 failed - /etc/modules.conf # Alsa sound support. # Warning: please don't modify comments over aliases 'snd-card-#' alias char-major-116 snd alias char-major-14 off options snd snd_cards_limit=1 snd_major=116 options snd-card-intel8x0 snd_index=0 # uniq.virtual:Sound card alias snd-card-0 snd-card-intel8x0 # YaST2: sound system dependent part # alias sound-slot-0 snd-card-0 alias sound-service-0-0 snd-mixer-oss alias sound-service-0-1 snd-seq-oss alias sound-service-0-3 snd-pcm-oss alias sound-service-0-8 snd-seq-oss alias sound-service-0-11 snd-mixer-oss alias sound-service-0-12 snd-pcm-oss Anyone has any idea? I think the messages from kernel are generated by "alias" and "sound" being all mixed up.. is this true? Thank you all -------------------------------------------------------- Juan Francisco Torres Ch. Desarrollo, Tecnología y Redes NETCO LTDA

19 years, 7 months

My first experience with autoyast

by Tor Sigurdsson

Hi people, I just wanted to share my first experience. I installed ~30 machines ( two computer labs ) using autoyast. The two labs have different machines ( old 400MHz IBMs and brand new 1.7GHz DELLs ). The change in the config files was ~5 lines between platforms :-) The install went without a hinch. Only one thing had to be done manually after installing: Rebuilding the SuSE-Helpcenter database ( hint - hint ;-) Wonderful product ! :-) ( ps: where can I get that xml editor you show in the book Mr. Nashif ? ) Thanks all that have come with hints to this list Special thanks to those that gave instructions on how to create the boot-cdrom :-) Best regards, Tor Sigurdsson

19 years, 7 months

Antwort: Re: [suse-autoinstall] Issues with custom rpms, SuSEconfig and kdm

by Andreas Rother

Phone : unbekannt / Fax : unbekannt / Mobile : unbekannt Anas Nashif <nashif(a)suse.de> 14.06.2002 03:29 An: suse-autoinstall(a)suse.com Kopie: Thema: Re: [suse-autoinstall] Issues with custom rpms, SuSEconfig and kdm >* Andreas Rother <Andreas.Rother(a)eplus.de> [Jun 13. 2002 17:34]: >> Will It soon be possible to add users with a certain uid and gid? I'm able >> to add a bunch of users with a postinstall-script, but it would be nicer, >> if they were added from config file. Maybe even home directory or shell >> can be set in the xml file... > > It is already possible, consider the following... > (...) > http://www.suse.de/~nashif/autoinstall/autoyast2/profile.elem.user.html Well, I must have skip this section competely. Is there any tag to add custom groups, too? Kind regards, Andreas Rother -- Andreas Rother - E-Plus Mobilfunk GmbH & Co. KG

19 years, 7 months

Issues with custom rpms, SuSEconfig and kdm

by Andreas Rother

Hello List! I have some trouble with SuSEconfig and kdm. In the xml file I define a certain value for KDM_BACKGROUND and KDM_GREETSTRING in /etc/sysconfig/displaymanager. But after finishing the autoinstall process and booting into runlevel 5 I still see the SuSE background. When I run SuSEconfig manually at least the value for background picture is written to /etc/kde3/(...)/kdmrc. The greetstring is still not changed :-( As I want to add some custom rpms with pics and scripts, I use the <extra_packages> tag in the xml file. It's quite confusing that you have to write the full rpm name without .rpm suffix. Suppressing known suffixes reminds me of another "famous" OS :-) The name of the package is backgrounds-0.0.1-1.rpm so I would assume that yast2 is smart enough to find the package if it's named just "backgrounds" in the xml file or wants to have a real full name of that package. Will It soon be possible to add users with a certain uid and gid? I'm able to add a bunch of users with a postinstall-script, but it would be nicer, if they were added from config file. Maybe even home directory or shell can be set in the xml file... Mit freundlichem Gruß/Kind regards Andreas Rother PS: I have already upgraded to yast2-module-autoinst-2.5.26-0.noarch.rpm and yast2-config-network-2.5.53-0.noarch.rpm -- Andreas Rother - E-Plus Mobilfunk GmbH & Co. KG

19 years, 7 months

Major update package

by Anas Nashif

Hi, I am currently working on an update package for all issues and bugs reported recently. It's obvious that fixing bugs 'while we go' eventually might produce other bugs, so I want to make sure the next update package has it all. So expect an update package next week, and even if I dont have an answer to your problems now, be sure I am working on it. :-) Thank you all for the feedback and the patience. Regards, Anas -- Anas Nashif <nashif(a)suse.com>, SuSE Linux AG Montreal (Laval), Canada

19 years, 7 months

Q: autoyast with NFS install root and DHCP

by Rainer Krienke

Hello, I am new to this list and just exploring the possibilities with the yast2 autoinstallation with suse8.0. I came across several questions that were not really clear to me after reading the documentation: I would like to configure a client to be installed as far as possible by DHCP. So the client should receive the SuSE-NFS installation source DIR and its server from DHCP and as far as possible I would like the client to get the location of the autoinst-controlfile as well from DHCP. At the moment my DHCP-server sets the nextserver and the filename options with IP-Address and PATH of the NFS server with the SUSE-CDs. Now when I start the installation and enter eg. autoyast=tftp://my-tftp-serverip/path/control.xml it seems autoyast does something different than expected. It configures the networkinterface via DHCP (gets correct values) but then complains that it cannot find the installation source. Well I had expected that the installtion source is received automatically by DHCP using the filename and nextserver-options and the the controlfile would then be received by tftp from the server given. But it is not. How can I do this? Ideally I would like to enter only something like autoyast=dhcp on the kernel commandline and then it should retrieve all information needed from the DHCP-server and start autoinstallation. Can this be done? What dhcp options are needed? A last question is, if it is possible to do a semi automatic installtion. Installing a client I always have to answer questions like Installation source, language, where to install the bootloader etc. My answers are usually always the same but on the other side the partitioning of the harddisk is different. So I would like to have defaults for most of the questions yast2 asks me during a manual installtion without beeing asked but have a way to partition the haddisk myself interactively. Does anyone know a way for this? Thanks Rainer -- ---------------------------------------------------------------------------- Rainer Krienke krienke(a)uni-koblenz.de Universitaet Koblenz, http://www.uni-koblenz.de/~krienke Rechenzentrum, Voice: +49 261 287 - 1312 Rheinau 1, 56075 Koblenz, Germany Fax: +49 261 287 - 1001312 -----------------------------------------------------------------------------

19 years, 7 months

Partition order with new autoinst-rpm

by felix.schumacher＠epost.de

Hi, I tried the new autoinst rpms for an install. But it generates the partitions in the wrong order and creates an extended partition, even if there are only four partitions to be created. The order for the partitions (which are /, /boot, swap and lvm) should be /boot first, after that / or swap and the last should be lvm (probably inside an extended partition). Is there any way to force this order? bye Felix ________________________________________ Zeitschriftenabos online bestellen - jetzt neu im Infoboten! http://www.epost.de

19 years, 7 months

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

openSUSE Autoinstall June 2002