May 2004 - openSUSE Autoinstall - openSUSE Mailing Lists

Modules update during auto installation.
by bigluo 24 May '04

24 May '04

How could I updated modules with additional .pcitable and .module-info files during auto installation. I would be advised to update modules during auto installation by putting modules into /..../root_for_autoyast/modules.However, seems I could not deal with modules, such as bcm5700, which need additional .pcitable and .module-info files as well as the module.As I know, this feature could be supported  by modifying modules.cgz during redhat auto installation. -- USTC Alumni Email System

1 0

Having dhclient installed and enabled instead of dhcpcd with AutoYaST.
by Hans Deragon 23 May '04

23 May '04

Greetings. We use a modified dhclient-script under RHL to get /etc/resolv.conf setup properly according to our network configuration. SuSE supports both dhcpcd and dhclient, but the default is dhcpcd. Anybody can inform me on how to setup dhclient as the default DHCP client using AutoYaST? Best regards, Hans Deragon -- Consultant en informatique/Software Consultant Deragon Informatique inc. Open source: http://www.deragon.biz http://facil.qc.ca (Promotion du libre) mailto://hans@deragon.biz http://autopoweroff.sourceforge.net (Logiciel)

2 1

Any documentation for modules's options available for yast2?
by Hans Deragon 21 May '04

21 May '04

Greetings. Newbie here with yast2. Typing "yast2 -l" shows a list of modules, and for each module, one can pass parameters. My problem: where can I find documentation about the options I can pass to a module? I have no clue what to pass to the modules. Best regards, Hans Deragon -- Consultant en informatique/Software Consultant Deragon Informatique inc. Open source: http://www.deragon.biz http://facil.qc.ca (Promotion du libre) mailto://hans@deragon.biz http://autopoweroff.sourceforge.net (Logiciel)

1 0

autoinstall problems (SuSE 9.1 Pro)
by Ivan Poddubny 20 May '04

20 May '04

Hello All, I'm trying to install SuSE 9.1 Pro onto 50+ systems and having some difficulties with the process. Any help would be appreciated. First of all, does anyone have an explanation why AutoYaST GUI and documentation (I'm using 9.0 docs as an example) creating different output then described in DTD files? Many DTDs are simply missing (like there are no definitions of samba-server), the other have different structure. Is it suppose to be so and we should correct DTD files ourselves or is this wrong? Anyway, I probably could live with this issue (at least I found some workarounds) but there are several other problems I can't resolve: (1) the documentation does not specify what users created (if any) during installation. I suspected that root is created but when I tried to login on test system after installing it using empty password for root, I got "Login incorrect". So I modified the control file and I tried to create user and assign a password for him. I got same results (Login incorrect) after installation. Is there any kind of special tricks here? BTW, I specified NIS but I suppose that users like root should be read from local files (i.e. /etc/nsswitch.conf has either "passwd: compat" or "passwd: files nis"). (2) my installation seems to be hanging at the very end. All packages installed, system rebooted and then installer is running SuSEconfig.* scripts. At the end of this process (or maybe right after it: step with copying preconfigured files onto system has been completed) I'm getting black screen (monitor stays on) and no disk activity. The only solution is reset button (which could lead to some missing configuration steps). I'm configuring X11 and suspecting that error comes from this part. Video adapter on test system supports the resolution I'm trying to use (1024x768 @ 16bpp). Is there anything I could do to debug the problem? (3) (this is sort of goes back to problem with DTDs). I was trying to use new syntax to describe LVM part when partitioning hard disk. The validation of control file goes OK. But when installing a test system, I got "lvremove cannot delete group sysdg" and after that installation fails. I tried to remove <use>all</use> tag from description of LVM partition, but it didn't help. The only solution was to go back to old syntax of LVM. However, there's a hidden (for me) problem: in the configuration I choose I have two volumes then belong to same disk group: root and home. While the size of root is always static (let's say 12GB), the size of home may vary due to different size of the harddrive. When using old syntax there's no way to specify "use maximum available space" for a volume, the size has to be defined. With new syntax it's possible to use key word "max". Is there anything could be done to either use new syntax of LVM's description or how could I specify "use all available space" with the old one? Thank you! --ivan

1 0

Large Amount Physical Memory and Automatic Swap Size
by Eric Schroeder 20 May '04

20 May '04

I have set the swap partition size to auto, which works great unless I try to install on a machine with a large amount of physical memory. The swap partition is never bigger than 1GB. Is this a limitation of autoyast, and is there any way to have the swap partition be 1.5 times the size of physical memory, regardless of the size? Thanks in advance, Eric Schroeder "Postmaster" made the following annotations. ------------------------------------------------------------------------------ This message may contain confidential information, and is intended only for the use of the individual(s) to whom it is addressed. ==============================================================================

1 0

Re: [suse-autoinstall] Broadcom NICs - tg3 WORKED
by Mouncef_Belcaid＠blm.gov 19 May '04

19 May '04

The automated installation worked using the tg3 module for the Broadcom NICs. Thank you all, especially Bjorn, you saved me a few hours of troubleshooting. Mouncef |---------+----------------------------> | | Bjorn Tore Sund | | | <bjornts(a)mi.uib.n| | | o> | | | | | | 05/19/2004 02:21 | | | AM | | | | |---------+----------------------------> >--------------------------------------------------------------------------------------------------------------| | | | To: suse-autoinstall(a)suse.com | | cc: | | Subject: Re: [suse-autoinstall] Broadcom NICs | >--------------------------------------------------------------------------------------------------------------| On Tue, 18 May 2004 Mouncef_Belcaid(a)blm.gov wrote: > I have used Autoyast successfully to install SuSE 8.2 Pro on multiple IBM > Blade servers. Each one of these servers comes with two Broadcom gigabit > cards, I used the bcm5700 module which worked fine during and after the > installation. We purchased more of these Blades, which come with the next > generation Broadcom cards, they work fine after a manual installation is > complete. > The problem is during the automated installation. After the installation > kernel loads, the card tries to get a DHCP IP from the NFS server (before > YAST starts), that's when it hangs. I checked the DHCP server logs and it > doesn't seem like the request is even reaching the server. > I tried loading 9.0 on one of the Blade servers, and it worked using > Autoyast. But I have to stick with SuSE 8.2 for now. Is there an updated > version of the SuSE 8.2 Pro loader files (initrd, linux, memtest...)? On 32bit systems I've found that the tg3 driver is a lot more stable than the bcm5700 driver. Have you tried that? Bjørn -- Bjørn Tore Sund Phone: (+47) 555-84894 Stupidity is like a System administrator Fax: (+47) 555-89672 fractal; universal and Math. Department Mobile: (+47) 918 68075 infinitely repetitive. University of Bergen VIP: 81724 Support: system(a)mi.uib.no Contact: teknisk(a)mi.uib.no Direct: bjornts(a)mi.uib.no -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Broadcom NICs
by Mouncef_Belcaid＠blm.gov 19 May '04

19 May '04

Hi everyone, I have used Autoyast successfully to install SuSE 8.2 Pro on multiple IBM Blade servers. Each one of these servers comes with two Broadcom gigabit cards, I used the bcm5700 module which worked fine during and after the installation. We purchased more of these Blades, which come with the next generation Broadcom cards, they work fine after a manual installation is complete. The problem is during the automated installation. After the installation kernel loads, the card tries to get a DHCP IP from the NFS server (before YAST starts), that's when it hangs. I checked the DHCP server logs and it doesn't seem like the request is even reaching the server. I tried loading 9.0 on one of the Blade servers, and it worked using Autoyast. But I have to stick with SuSE 8.2 for now. Is there an updated version of the SuSE 8.2 Pro loader files (initrd, linux, memtest...)? Thanks for your time, Mouncef

3 2

Antwort: [suse-autoinstall] Broadcom NICs [FinanzIT: Viruscheck]
by Hartmut.Dunker＠finanzit.com 19 May '04

19 May '04

Hi Mouncef, we had the same Problem with SLES8 and HP Proliants. Old systems worked with an old boot kernel. After purchasing a new Proliant some weeks ago the system wasn't able to get a DHCP IP after PXE boot. After changing the boot kernel to the SLES8 SP3 kernel in the tftp directory pxe boot and autoinstallation works fine. Just try to use the boot kernel from the 9.0 CD for installation. Regards Hartmut Dunker Mouncef_Belcaid@b lm.gov An: suse-autoinstall(a)suse.com Kopie: 18.05.04 21:22 Thema: [suse-autoinstall] Broadcom NICs [FinanzIT: Viruscheck] Hi everyone, I have used Autoyast successfully to install SuSE 8.2 Pro on multiple IBM Blade servers. Each one of these servers comes with two Broadcom gigabit cards, I used the bcm5700 module which worked fine during and after the installation. We purchased more of these Blades, which come with the next generation Broadcom cards, they work fine after a manual installation is complete. The problem is during the automated installation. After the installation kernel loads, the card tries to get a DHCP IP from the NFS server (before YAST starts), that's when it hangs. I checked the DHCP server logs and it doesn't seem like the request is even reaching the server. I tried loading 9.0 on one of the Blade servers, and it worked using Autoyast. But I have to stick with SuSE 8.2 for now. Is there an updated version of the SuSE 8.2 Pro loader files (initrd, linux, memtest...)? Thanks for your time, Mouncef -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Post script not created/executed.
by Hans Deragon 17 May '04

17 May '04

Greetings. Newbie with AutoYaST here trying to install SuSE 9.0. I have a config.xml file that works fine, except that the post script is not created (not found in var/adm/autoinstall/scripts). I cannot understand why it is not created and executed. The /var/log/y2log does show that the script's entry has been parsed. But I could not find any error messages regarding this. Following, the <scripts> section. <scripts> <post-scripts config:type="list" > <script> <filename>post.sh</filename> <interpreter>shell</interpreter> <source><![CDATA[echo "POST TEST passed."]]></source> </script> </post-scripts> </scripts> Pretty basic, huh? Can anybody point me to log files that would show me error messages related to my problem or provide me some clues? Best regards, Hans Deragon -- Consultant en informatique/Software Consultant Deragon Informatique inc. Open source: http://www.deragon.biz http://autopoweroff.sourceforge.net mailto://hans@deragon.biz (Automatically poweroff home servers)

3 3

Unable to uninstall YaST2 Installed Package (SuSE 9.0)
by Mike Blonder 14 May '04

14 May '04

Hi. I used YaST2 to install a Content Management System call midgard to a SuSE 9.0 system. Now I am denied by YaST2 when I attempt to uninstall it. It should be noted that I installed a second iteration of the package (non RPM) directly from the source group. Even worse, I cannot restart Apache. I am prompted to run SuSEconfig --module apache. When I run said command it also bombs with the following error message: No FQHOSTNAME SET! Quitting When I look at the config files httpd.SuSEconfig and suse_include.conf I notice advisories at the top of the screen to "Please don't edit these files" What do I do now? Thanks Mike

1 0