December 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

SCR problem
by Brian Corriveau 05 Jan '05

05 Jan '05

How do I run this from the bash shell? (from clients/inst_finish.ycp) SCR::Write (.target.string, "/var/lib/YaST2/runme_at_boot", "") I want to try running this manually so I can understand why it is failing during autoinstallation. This is failing for my target, as are a couple other SCR commands. I can run the command from a chroot post-script to get the help output with: chroot /mnt /usr/lib/YaST2/servers/scr -h So the command seems to run somewhat, but for the runme_at_boot creation I get the Y2log error: 2004-12-18 02:34:13 <0> linux(3172) [liby2] Y2ProgramComponent.cc(launchExternall Program):292 Going to execute /usr/lib/YaST2/servers/scr with chroot /mnt 2004-12-18 02:34:13 <0> linux(519) [libycp] Scanner.cc(Scanner):107 Scanner settting builtinTable to 0x507d10 2004-12-18 02:34:13 <0> linux(519) [libycp] Scanner.cc(initTables):146 m_globalTT able 0x1776bb0 2004-12-18 02:34:13 <0> linux(519) [libycp] Scanner.cc(initTables):158 m_localTaable 0x52fd60 2004-12-18 02:34:13 <0> linux(519) [libycp] parser.yy(yyparse):284 ------------------------------------------- accept ------------------------------ -------------- 2004-12-18 02:34:13 <0> linux(519) [liby2] Y2ProgramComponent.cc(sendToExternal)) :377 Error writing to external program /usr/lib/YaST2/servers/scr: Couldn't sendd (`Write (.target.string, "/var/lib/YaST2/runme_at_boot", "")) (Broken pipe) 2004-12-18 02:34:13 <3> linux(519) [liby2] Y2ProgramComponent.cc(receiveFromExtee rnal):343 External program /usr/lib/YaST2/servers/scr died unexpectedly 2004-12-18 02:34:13 <3> linux(519) [Interpreter] scr:240 SCR::Write() did not reeturn a boolean So I'd like to understand what is wrong with my target's environment that this would fail. thanks, Brian

1 1

EXTRA_PROV_FILE missing from SLES8 s390
by Kohrs, Steven 03 Jan '05

03 Jan '05

I'm trying to update the package description of a SLES8 s390 distribution which is being housed on a SLES9 x86 server. /usr/bin/create_package_descr EXTRA_PROV_FILE location missing. Call this script with -x <location to EXTRA_PROV file>. The EXTRA_PROV is available on the first CD in the directory suse/setup/descr There is no "EXTRA_PROV" included with the SLES8 s390 media.

2 3

Firstboot questions
by Anthony Staples 03 Jan '05

03 Jan '05

Is there a way to easily force FIRSTBOOT to run the X11 and Network setup screen sections of YAST after a ghost image is loaded to a new machine? I have looked over the doc and I _think _it would involve adding information to the control.xml file under the firstboot section, but I am uncertain how to proceed. Basically I would like "firstboot" to behave as sysprep does for XP. I would also like to turn off the resetting of the root password... I don't want the user's changing the root password. Is it as simple as commenting out that section under "firstboot" in the control.xml file? Cheers, -T The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.

2 3

Re: Fw: [suse-autoinstall] customizing initrd
by Aaron Amauba 30 Dec '04

30 Dec '04

Thanks for the reply. 1st time doing this for me, so pls bear with... Also, this might be the wrong list for this, but since its breaking the AutoYast installation (Well, no network support = no AutoYast).... The x346 has the new BCM5721 chip. SLES8 does not have built in support for this chip, so to get network support into the install initrd I had to do the fillowing. Build the new module against the same kernel tree as the install kernel. The one I was using happaned to be 2.4.21-138 (I also used the smp the 1st time by accident). Save the original initrd zcat initrd > rd mount -oloop rd /mnt copy the new .o file to /mnt/modules/ umount /mnt gzip -9 rd mv rd.gz initrd So, now I had a initrd with the new bcm5700.o file (with support for the 5721 chip). The only modules.pcimap I could find was in /lib/modules/modules.pcimap in the build tree. Not in initrd. It didnt have an entry for the new chip. I know the vendor ID is 14e4 and the device ID is 1659. But I dont know the subvendor, sbudevice, class, class_mask or device_data. Im assuming this is the correct place to update. I am having difficulty finding docs for this. What I did find said the distro usually fills out this information. Any more suggestions or links to Doc's I should read? Thanks Joseph V Moss <jmoss(a)ichips.intel.com> 12/29/2004 04:30 PM To Aaron Amauba <aapa20032003(a)yahoo.com> cc suse-autoinstall(a)suse.com Subject Re: Fw: [suse-autoinstall] customizing initrd Update the modules.pcimap (in /lib/modules/<kernel_version>-default/ in the initrd) with the PCI ID of the new chip. > I am trying to do the same thing (except with a x346 instead). I added the new bcm5700.o file to the /modules directory in initrd. After I do that I have to add the module manually. Its nots found automatically. What else do I have to change? > > > > > > Thomas Mieslinger <Thomas.Mieslinger(a)gls-itservices.com> > 11/25/2004 12:26 PM > > > > > > To > > suse-autoinstall(a)suse.com > cc > > > Subject > > Re: [suse-autoinstall] customizing initrd > > > > > I'd like to install a new ibm x336 with bcm5721 network chips. These are > not support by the standard kernel so I need to change the bcm5700.o. > -- > GLS IT Services > Thomas Mieslinger > GLS Germany Str. 1-7 fon: +49 6677 17 463 > 36286 Neuenstein fax: +49 6677 17 111 > Germany eMail: thomas.mieslinger(a)gls-itservices.com > > Anas Nashif <nashif(a)suse.de> schrieb am 25.11.2004 21:22:33: > > > The trailing garbage message can be ignored. I have no idea where it > > comes from, but after recreating the initrd as described earlier, it > > works. What exactly did you change in the initrd? > > > > Anas > > > > Thomas Mieslinger wrote: > > > > > > > > > > > > Hi Andi, > > > > > > this initrd is right off the SLES 8 SP3 cd. Without the trailing > garbage it > > > doesn't boot anymore. How can I re-add this to the initrd? > > > > > > Thanks in advance > > > > > > Thomas > > > -- > > > GLS IT Services > > > Thomas Mieslinger > > > GLS Germany Str. 1-7 fon: +49 6677 17 463 > > > 36286 Neuenstein fax: +49 6677 17 111 > > > Germany eMail: thomas.mieslinger(a)gls-itservices.com > > > > > > Andi Kleen <ak(a)suse.de> schrieb am 25.11.2004 20:57:09: > > > > > > > > >>On Thu, Nov 25, 2004 at 08:52:05PM +0100, Thomas Mieslinger wrote: > > >> > > >>> > > >>> > > >>> > > >>>>Well I think the problem is that during uncompression I get this > > > > > > message. > > > > > >>>>root@deinst01> gzip -d initrd.gz > > >>>> > > >>>>gzip: initrd.gz: decompression OK, trailing garbage ignored > > >>>> > > >>>>when I recompress this file it is smaller than the original and > > >>>>doesn't boot anymore. > > >>>> > > >>>>What is that "trailing garbage ignored"? > > >> > > >>It's possible to append a custom DSDT to the initrd. DSDT is a BIOS > > >>ACPI table which is often buggy on laptops and can be replaced. > > >>But for non laptops that's rarely done and the installer never > > >>does it on its own. > > >> > > >>-Andi > > > > > > > > > > > > > -- > > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > > > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > > > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com --------------------------------- Do you Yahoo!? The all-new My Yahoo! � What will yours do?

1 0

installation_sources
by Michael Shannon 30 Dec '04

30 Dec '04

Is there anyway to make installation_sources use active instead of passive ftp? -m Michael Shannon | Sr. Systems Engineer - UNIX Systems Engineering Schedule: In between 06:30 and 07:00 Out around 15:00 PST InfoSpace INC 601 108th Ave NE | Suite 1200 | Bellevue, WA 98004 Tel 425.201.8750 | Fax 425.201.6160 | Mobile 206.310.4664 michael.shannon(a)infospace.com <mailto:michael.shannon@infospace.com> | www.infospaceinc.com

1 0

how to install suse via http proxy?
by Kai Zhang 30 Dec '04

30 Dec '04

I can install suse via direct ftp access to ftp.mirror.ac.uk with no problem. But now I am behind firewall with only http proxy. With boot disk I can see it loading data into ramdisk from ftp server and load GUI. The major problem prevent me from completing the installation is the error msg: Software Cannot read package data from installation media. Media Error? For god sake it's suppose to be a ftp installation. I tried different ftp suse download servers, all have the same problem! I guess this is because it can't read the packages (or at least the list of the packages) on the ftp server. I've searched everywhere for solution. Please help! Regards, Kai

1 0

Re: Fw: [suse-autoinstall] customizing initrd
by Aaron Amauba 30 Dec '04

30 Dec '04

I am trying to do the same thing (except with a x346 instead). I added the new bcm5700.o file to the /modules directory in initrd. After I do that I have to add the module manually. Its nots found automatically. What else do I have to change? Thomas Mieslinger <Thomas.Mieslinger(a)gls-itservices.com> 11/25/2004 12:26 PM To suse-autoinstall(a)suse.com cc Subject Re: [suse-autoinstall] customizing initrd I'd like to install a new ibm x336 with bcm5721 network chips. These are not support by the standard kernel so I need to change the bcm5700.o. -- GLS IT Services Thomas Mieslinger GLS Germany Str. 1-7 fon: +49 6677 17 463 36286 Neuenstein fax: +49 6677 17 111 Germany eMail: thomas.mieslinger(a)gls-itservices.com Anas Nashif <nashif(a)suse.de> schrieb am 25.11.2004 21:22:33: > The trailing garbage message can be ignored. I have no idea where it > comes from, but after recreating the initrd as described earlier, it > works. What exactly did you change in the initrd? > > Anas > > Thomas Mieslinger wrote: > > > > > > > > Hi Andi, > > > > this initrd is right off the SLES 8 SP3 cd. Without the trailing garbage it > > doesn't boot anymore. How can I re-add this to the initrd? > > > > Thanks in advance > > > > Thomas > > -- > > GLS IT Services > > Thomas Mieslinger > > GLS Germany Str. 1-7 fon: +49 6677 17 463 > > 36286 Neuenstein fax: +49 6677 17 111 > > Germany eMail: thomas.mieslinger(a)gls-itservices.com > > > > Andi Kleen <ak(a)suse.de> schrieb am 25.11.2004 20:57:09: > > > > > >>On Thu, Nov 25, 2004 at 08:52:05PM +0100, Thomas Mieslinger wrote: > >> > >>> > >>> > >>> > >>>>Well I think the problem is that during uncompression I get this > > > > message. > > > >>>>root@deinst01> gzip -d initrd.gz > >>>> > >>>>gzip: initrd.gz: decompression OK, trailing garbage ignored > >>>> > >>>>when I recompress this file it is smaller than the original and > >>>>doesn't boot anymore. > >>>> > >>>>What is that "trailing garbage ignored"? > >> > >>It's possible to append a custom DSDT to the initrd. DSDT is a BIOS > >>ACPI table which is often buggy on laptops and can be replaced. > >>But for non laptops that's rarely done and the installer never > >>does it on its own. > >> > >>-Andi > > > > > > > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com > -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

2 1

RE: [suse-autoinstall] re-visited YaST.firstboot question
by Michael Shannon 28 Dec '04

28 Dec '04

Excellent, once I started editing the right section of control.xml everything fell into place :) -m -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Monday, December 27, 2004 4:10 PM To: Michael Shannon Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] re-visited YaST.firstboot question The answer to your question lies in the control.xml file which controls the workflow of the installation. autoyast has a different workflow than the manual installation and it shows no proposals in second stage. If you want the network proposal, you have to added it to the autoinstallation workflow. See http://yast2.suse.com/tdg/html/yast2-installation.html#product_control for more detailes. (Above document is still work in progress). Anas Michael Shannon wrote: > I know I've asked this once before, but I've spent some more time going > through the scripts and still can't find out how to accomplish what I'm > looking for (having the lan module run during Yast2.firstboot, without > taking the default proposals) > > From what I gather, if you use autoyast it does a few things to prep the > system for the first. > 1) creates the /var/lib/YaST2/runme_at_boot file and > 2) creates the /etc/install.inf > > ... It does other stuff, but I'm not worried about that right now. > > When /etc/init.d/boot is run it checks for runme_at_boot and if that > exists then /usr/lib/YaST2/bin/YaST2.firstboot runs and that starts > > /usr/lib/YaST2/bin/YaST2 installation continue > > This reads the /etc/install.inf file and the values there are used for > the rest of the autoinstall. > > If I make Manual = 1 in /etc/install.inf, yast asks about the network > modules, but never drops me to the yast2 lan module, it looks like it > just accepts the proposal based on the autoyast=file///a.xml file. > > If I could force the lan module to run and not accept any defaults it > would save me the hassle of having to generate new ssl certificates > after running yast lan (host name changes). > > > Thanks again, > > -m > > > > > -----Original Message----- > From: Michael Shannon [mailto:Michael.Shannon@infospace.com] > Sent: Tuesday, December 21, 2004 2:42 PM > To: suse-autoinstall(a)suse.com > Subject: [suse-autoinstall] YaST.firstboot question > > > For a while we thought using DHCP with autoyast sounded like a good > idea, but then we decided not to go that direction. > > I would really like YaST.firstboot to run the lan module on first boot, > I've read through the scripts and its not very obvious to me how to make > this happen. I've completely removed the lan configuration from > autoyast.xml hoping that would force YaST.firstboot to run the lan > module, but my efforts yielded very little fruit :( > > It looks like there might be something in the install.inf file that is > telling YaST that the interface has been configured, is there a way > around this? > > Thanks, > > -m > > > >

1 0

FW: [suse-autoinstall] re-visited YaST.firstboot question
by Michael Shannon 28 Dec '04

28 Dec '04

Sorry, Anas, didn't mean to send this directly to you.. -----Original Message----- From: Michael Shannon Sent: Tuesday, December 28, 2004 8:46 AM To: 'Anas Nashif' Subject: RE: [suse-autoinstall] re-visited YaST.firstboot question Yup, that's exactly what I was looking for: ) I looked through the control.xml file and it wasn't clear to me how to translate this: <module> <label>Network</label> <name>proposal</name> <arguments>true,true,`net</arguments> </module> I know it starts the inst_proposal module in `net mode, but its not clear to me what "true,true" does. I read /usr/share/doc/packages/yast2-installation/autodocs/inst_proposal.html /usr/share/doc/packages/yast2-installation/proposal-API.txt And /usr/share/YaST2/clients/inst_proposal.ycp I didn't anything in inst_proposal.ycp that parses the arguments, so I'm wondering if those arguments actually do anything? I'm going to change the values and see what happens, but if there's even more documentation to be read, I'd be happy to read that instead of bother the list. Thanks, -m -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Monday, December 27, 2004 4:10 PM To: Michael Shannon Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] re-visited YaST.firstboot question The answer to your question lies in the control.xml file which controls the workflow of the installation. autoyast has a different workflow than the manual installation and it shows no proposals in second stage. If you want the network proposal, you have to added it to the autoinstallation workflow. See http://yast2.suse.com/tdg/html/yast2-installation.html#product_control for more detailes. (Above document is still work in progress). Anas Michael Shannon wrote: > I know I've asked this once before, but I've spent some more time going > through the scripts and still can't find out how to accomplish what I'm > looking for (having the lan module run during Yast2.firstboot, without > taking the default proposals) > > From what I gather, if you use autoyast it does a few things to prep the > system for the first. > 1) creates the /var/lib/YaST2/runme_at_boot file and > 2) creates the /etc/install.inf > > ... It does other stuff, but I'm not worried about that right now. > > When /etc/init.d/boot is run it checks for runme_at_boot and if that > exists then /usr/lib/YaST2/bin/YaST2.firstboot runs and that starts > > /usr/lib/YaST2/bin/YaST2 installation continue > > This reads the /etc/install.inf file and the values there are used for > the rest of the autoinstall. > > If I make Manual = 1 in /etc/install.inf, yast asks about the network > modules, but never drops me to the yast2 lan module, it looks like it > just accepts the proposal based on the autoyast=file///a.xml file. > > If I could force the lan module to run and not accept any defaults it > would save me the hassle of having to generate new ssl certificates > after running yast lan (host name changes). > > > Thanks again, > > -m > > > > > -----Original Message----- > From: Michael Shannon [mailto:Michael.Shannon@infospace.com] > Sent: Tuesday, December 21, 2004 2:42 PM > To: suse-autoinstall(a)suse.com > Subject: [suse-autoinstall] YaST.firstboot question > > > For a while we thought using DHCP with autoyast sounded like a good > idea, but then we decided not to go that direction. > > I would really like YaST.firstboot to run the lan module on first boot, > I've read through the scripts and its not very obvious to me how to make > this happen. I've completely removed the lan configuration from > autoyast.xml hoping that would force YaST.firstboot to run the lan > module, but my efforts yielded very little fruit :( > > It looks like there might be something in the install.inf file that is > telling YaST that the interface has been configured, is there a way > around this? > > Thanks, > > -m > > > >

1 0

re-visited YaST.firstboot question
by Michael Shannon 28 Dec '04

28 Dec '04

I know I've asked this once before, but I've spent some more time going through the scripts and still can't find out how to accomplish what I'm looking for (having the lan module run during Yast2.firstboot, without taking the default proposals) >From what I gather, if you use autoyast it does a few things to prep the system for the first. 1) creates the /var/lib/YaST2/runme_at_boot file and 2) creates the /etc/install.inf ... It does other stuff, but I'm not worried about that right now. When /etc/init.d/boot is run it checks for runme_at_boot and if that exists then /usr/lib/YaST2/bin/YaST2.firstboot runs and that starts /usr/lib/YaST2/bin/YaST2 installation continue This reads the /etc/install.inf file and the values there are used for the rest of the autoinstall. If I make Manual = 1 in /etc/install.inf, yast asks about the network modules, but never drops me to the yast2 lan module, it looks like it just accepts the proposal based on the autoyast=file///a.xml file. If I could force the lan module to run and not accept any defaults it would save me the hassle of having to generate new ssl certificates after running yast lan (host name changes). Thanks again, -m -----Original Message----- From: Michael Shannon [mailto:Michael.Shannon@infospace.com] Sent: Tuesday, December 21, 2004 2:42 PM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] YaST.firstboot question For a while we thought using DHCP with autoyast sounded like a good idea, but then we decided not to go that direction. I would really like YaST.firstboot to run the lan module on first boot, I've read through the scripts and its not very obvious to me how to make this happen. I've completely removed the lan configuration from autoyast.xml hoping that would force YaST.firstboot to run the lan module, but my efforts yielded very little fruit :( It looks like there might be something in the install.inf file that is telling YaST that the interface has been configured, is there a way around this? Thanks, -m -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

RE: [suse-autoinstall] NIC module confusion
by Suffin, Charles 23 Dec '04

23 Dec '04

Andreas, Regarding the configuration options that are available through XML: I've been using the DTD files that you can find in /usr/share/autoinstall/dtd/ These are the files that are used by the autoinstaller to verify the XML script. That, of course, presupposes that the DTD files themselves are complete -- i.e., that they have all the available options. I agree that a documented list of these things and what they mean (some are obvious, others perhaps not) would be useful. I'm intending to read the source soon to get a handle for how autoyast actually uses this stuff to control installation. -- charlie -----Original Message----- From: Andreas Octav [mailto:Andreas.Octav@anykey.de] Sent: Wednesday, December 22, 2004 6:26 PM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] NIC module confusion Hi folks, I´m having some trouble autoinstalling SLES9 on a HP Proliant DL 360. The box has a Broadcom GBit NIC onboard and I want to use it with the bcm5700 module. But autoyast doesn´t seem to care about the module information i entered in the xml control file. After finishing the installation my NIC uses the tg3 module. I configured the bcm5700 module for eth0 (and eth1) in the xml control file but it does not seem to work the way it should (i think). There is a module entry in the /etc/sysconfig/network/ifcfg-ethxxx files mentioning bcm5700. Also modifying the modprobe.conf (alias eth0 bcm5700) doesn´t do the job :-( By the way, i did not find any documentation about how to configure a finish-script when installing SLES9. Is there any information about this i overlooked? A complete list of all availlable xml tags would also be very helpful. The documentation at www.suse.com/~nashif doesn´t seem to reveal all the magic that lies in this product... Kind regards, Andreas Octav -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

NIC module confusion
by Andreas Octav 22 Dec '04

22 Dec '04

Hi folks, I´m having some trouble autoinstalling SLES9 on a HP Proliant DL 360. The box has a Broadcom GBit NIC onboard and I want to use it with the bcm5700 module. But autoyast doesn´t seem to care about the module information i entered in the xml control file. After finishing the installation my NIC uses the tg3 module. I configured the bcm5700 module for eth0 (and eth1) in the xml control file but it does not seem to work the way it should (i think). There is a module entry in the /etc/sysconfig/network/ifcfg-ethxxx files mentioning bcm5700. Also modifying the modprobe.conf (alias eth0 bcm5700) doesn´t do the job :-( By the way, i did not find any documentation about how to configure a finish-script when installing SLES9. Is there any information about this i overlooked? A complete list of all availlable xml tags would also be very helpful. The documentation at www.suse.com/~nashif doesn´t seem to reveal all the magic that lies in this product... Kind regards, Andreas Octav

1 0

Interacting with script-launched shell
by Suffin, Charles 22 Dec '04

22 Dec '04

Hi folks, I'm new to this autoinstall email forum, and I am currently learning and using the SuSE installation products. I hope I can participate here as I've seen some good information exchanged in the archives. I am doing some testing with SLES 9.0 on a standard Intel PC. While creating a pre-install script via autoyast's XML control file, I've put in the following lines so I can do some debugging. This was a clever suggestion that I found on Cambridge University's web site (thanks guys!): <source><![CDATA[#!/bin/bash exec /bin/bash -x ]]></source> I believe this should drop me into a bash shell, but if YaST is doing so I can't seem to interact with the shell at all. The console (running YaST in text mode) indicates that I am executing the pre-install script, so I suspect the shell is actually running, but I can't see any output from the shell at all. Ctrl-C seems to let me proceed, so perhaps the shell is taking input from my keyboard, but it is hard to tell. I have found that if I use ctrl-alt-<f2>, <f5>, <f6>, or <f9>, there appear to be shells already running on those alternate ttys which I can use for debugging. That's cool. However, I don't think they're related to the shell I'm starting in my script. Anyone know what I'm doing wrong? TIA. -- Charlie ----- A. Charles Suffin Senior Software Engineer Stratus Technologies, Inc. 111 Powdermill Road Maynard, MA 01754-3409 US (978)461-7590

2 1

RE: [suse-autoinstall] SCR problem
by Suffin, Charles 22 Dec '04

22 Dec '04

Brian, I'm not sure what is wrong with your script, but you can get access to a shell window during any of the three script environments (pre, chroot, post) by putting the following line at the top of your script: exec /bin/bash -x This pauses the autoinstall dead in its tracks until you kill the shell... Even though I have not figured out yet how to interact with *that* shell when it starts, what you *can* do is hit ctl-alt-F2 to get to a shell that's already running on ttyN. From there, you can run each of your commands manually and find out what's wrong. Hope that helps. -- Charlie -----Original Message----- From: Brian Corriveau [mailto:bcorriveau@cray.com] Sent: Monday, December 20, 2004 5:25 PM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] SCR problem How do I run this from the bash shell? (from clients/inst_finish.ycp) SCR::Write (.target.string, "/var/lib/YaST2/runme_at_boot", "") I want to try running this manually so I can understand why it is failing during autoinstallation. This is failing for my target, as are a couple other SCR commands. I can run the command from a chroot post-script to get the help output with: chroot /mnt /usr/lib/YaST2/servers/scr -h So the command seems to run somewhat, but for the runme_at_boot creation I get the Y2log error: 2004-12-18 02:34:13 <0> linux(3172) [liby2] Y2ProgramComponent.cc(launchExternall Program):292 Going to execute /usr/lib/YaST2/servers/scr with chroot /mnt 2004-12-18 02:34:13 <0> linux(519) [libycp] Scanner.cc(Scanner):107 Scanner settting builtinTable to 0x507d10 2004-12-18 02:34:13 <0> linux(519) [libycp] Scanner.cc(initTables):146 m_globalTT able 0x1776bb0 2004-12-18 02:34:13 <0> linux(519) [libycp] Scanner.cc(initTables):158 m_localTaable 0x52fd60 2004-12-18 02:34:13 <0> linux(519) [libycp] parser.yy(yyparse):284 ------------------------------------------- accept ------------------------------ -------------- 2004-12-18 02:34:13 <0> linux(519) [liby2] Y2ProgramComponent.cc(sendToExternal)) :377 Error writing to external program /usr/lib/YaST2/servers/scr: Couldn't sendd (`Write (.target.string, "/var/lib/YaST2/runme_at_boot", "")) (Broken pipe) 2004-12-18 02:34:13 <3> linux(519) [liby2] Y2ProgramComponent.cc(receiveFromExtee rnal):343 External program /usr/lib/YaST2/servers/scr died unexpectedly 2004-12-18 02:34:13 <3> linux(519) [Interpreter] scr:240 SCR::Write() did not reeturn a boolean So I'd like to understand what is wrong with my target's environment that this would fail. thanks, Brian -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

YaST.firstboot question
by Michael Shannon 21 Dec '04

21 Dec '04

For a while we thought using DHCP with autoyast sounded like a good idea, but then we decided not to go that direction. I would really like YaST.firstboot to run the lan module on first boot, I've read through the scripts and its not very obvious to me how to make this happen. I've completely removed the lan configuration from autoyast.xml hoping that would force YaST.firstboot to run the lan module, but my efforts yielded very little fruit :( It looks like there might be something in the install.inf file that is telling YaST that the interface has been configured, is there a way around this? Thanks, -m

1 0

SLES9 and modems
by Patrick B. O'Brien 20 Dec '04

20 Dec '04

What SLES9 util would I run to config my modem in my Dell PC? TIA.

1 0

Bug: network setup and Myrinet
by Karsten Petersen 19 Dec '04

19 Dec '04

Hi, I have a problem with SuSE 9.1 autoyast, a static network setup and Myrinet host adapters which are in the machines. My autoyast files have a network configuration that looks like this: <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <broadcast>192.168.21.127</broadcast> <device>eth-0</device> <ipaddr>192.168.21.102</ipaddr> <netmask>255.255.255.224</netmask> <network>192.168.21.96</network> <startmode>onboot</startmode> </interface> </interfaces> There is no <modules> declaration in <networking>, just the above <interfaces>, <dns> and <routing>. But if a machine is installed with this configuration, the network setup ends up totally wrong: Autoyast assigns the given IP to the Myrinet interface - which is senseless because there is no driver loaded and Myrinet does not need an IP to work. This is because the hwinfo tool detects the Myrinet card and yast declares it to be a "netcard" named "myri". When autoyast goes to use the given interface setup, it calls SelectHW() which returns the first netcard: myri. Neither of the following attempts worked: - add another <interface> declaration in front of the eth-0 one - add a <modules> section - rename <device> to eth0 Fixing this in a postinstall script failed because the ifcfg-* files are only created afterwards. So now I am trying a postinstall script that patches the file /usr/share/YaST2/modules/NetworkDevices.ycp and runs ycpc afterwards. :-/ Does anyone have a better idea? Nevertheless I believe this is a bug - autoyast should just ignore the Myrinet card. A related problem is, that it seems impossible to exactly declare which device an interface configuration is for, without giving the MAC address in <device>. This is very impractical for large amounts of mostly identical machines. :-( It would be good if I could tell autoyast something like this: <interface> <device>eth0</device> ... </interface> And autoyast would then use this declaration for the kernels eth0 device, no matter what other devices are around or what MAC this device has. Best wishes Karsten Petersen -- Karsten Petersen email: petersen(a)megware.de HPC System Engineer phone: +49 - 3722 - 528 43 MEGWARE Computer GmbH home: www.megware.de Chemnitz / Germany

2 1

missing device nodes
by Rajiv Aaron Manglani 17 Dec '04

17 Dec '04

hello. we are seeing a problem with autoyast on 9.1 where device entries for hard drive partitions are missing. i mentioned it briefly in a pervious post: http://lists2.suse.com/archive/suse-autoinstall/2004-Nov/0050.html as an example of the problem, autoyast is going to install onto hda using hda1 as boot, hda2 as swap, hda3 as root. when trying to format the file systems, an error will come up saying that it could not format. we have found that the device entry for just that partition is missing, but `fdisk -l` shows all three partions on the disk. so /dev/hda1 and /dev/hda[3-9] exist, but /dev/hda2 does not. manually creating the device node (eg, `mknod /dev/hda2 b 3 2`) fixes the problem and autoyast can continue. anyone else see this? what can i do to further debug the problem?

1 0

yast-cd-creator and autoinstall on SuSE Linux 9.2
by Pierre Allix 17 Dec '04

17 Dec '04

Hi, I would like to know if we can find yast cd-creator and yast autoinstall on SuSE Linux 9.2 ? Thanks, Pierre

1 0

finish auto-installing without initrd?
by Brian Corriveau 17 Dec '04

17 Dec '04

Hi, my target doesn't normally boot with an initrd. Is is possible to get autoyast working without an initrd on the initial boot of an auto-installed systed? Or for auto-installing do I need to do the initial boot (after installing) with initrd so it will kick off the last part of the auto install? Brian

4 9

what is component scr?
by Brian Corriveau 17 Dec '04

17 Dec '04

I get these error messages repeated over and over again in my /var/log/YaST2/y2log 2004-12-15 00:33:56 <1> linux(3244) [liby2] genericfrontend.cc(main):133 Launched YaST2 component 'scr' 2004-12-15 00:33:56 <1> linux(3244) [liby2] genericfrontend.cc(main):422 YAST_IS_RUNNING is yes 2004-12-15 00:33:56 <2> linux(3244) [liby2] Y2StdioComponent.cc(doActualWork):110 Communication ended prior to result () message 2004-12-15 00:33:56 <1> linux(3244) [liby2] genericfrontend.cc(main):437 Finished YaST2 component 'scr' 2004-12-15 00:33:56 <1> linux(3245) [liby2] genericfrontend.cc(main):133 Launched YaST2 component 'scr' 2004-12-15 00:33:56 <1> linux(3245) [liby2] genericfrontend.cc(main):422 YAST_IS_RUNNING is yes 2004-12-15 00:33:56 <2> linux(3245) [liby2] Y2StdioComponent.cc(doActualWork):110 Communication ended prior to result () message This doesn't sound good. What does it mean? thanks Brian

2 3

having no luck with autoyast
by Joe Landman 17 Dec '04

17 Dec '04

Hi folks: I do not seem to be able to generate reasonably simple/minimal autoyast configurations for building a cluster. I have the PXE boot bit working nicely. The configs I seem to have created take about 30 minutes to install, then kernel panic on boot. I am trying to create cluster compute nodes, and I need smaller configurations. Basically the hardest thing I want to do is to build a RAID0 out of the pair of SATA drives. Are there examples of such autoyast configs around somewhere that are set up for clusters, or minimal installs, and do RAID0's? Basically, I want to know what I can omit from the autoyast xml file, and still generate good working bootable 9.2 based systems. Platforms are Opteron 250's running on Tyan s2882's, and Opteron 850's running on Tyan s4882's. Thanks. Joe

1 0

Help with Classes
by fraser_bailey＠agilent.com 16 Dec '04

16 Dec '04

Hi, I must be dumb. I can't get classes to work. I've tried the following but when it pulls in install1.xml it says Namespace prefix config is not defined I've obviously got the whole structure wrong. I'm not sure that the format of the class file I've written is valid. I do know that if I load using the xml file unsplit into classes it does work so it must be way in which I've broken it up. Can someone furnish me with some files which demonstrate a working example? thanks ever so much fraser bailey <?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> <classes config:type="list"> <class> <class_name>common</class_name> <configuration>configure.xml</configuration> </class> </classes> </configure> <install> <classes config:type="list"> <class> <class_name>common</class_name> <configuration>install1.xml</configuration> </class> <class> <class_name>rsp</class_name> <configuration>disk.xml</configuration> </class> <class> <class_name>common</class_name> <configuration>install2.xml</configuration> </class> </classes> </install> </profile> one of the class files: <partitioning config:type="list"> <drive> <device>/dev/sda</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">1</partition_nr> <size>auto</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">2</partition_nr> <size>max</size> </partition> </partitions> <use>all</use> </drive> </partitioning>

1 0

Up to date Novell Linux Desktop segfaults with local source
by Pierre Allix 16 Dec '04

16 Dec '04

Hello, I created three local directories (/var/cds/cd1/, ..., /var/cds/cd3) and an index with genIS_PLAINcache to have a local source of packages. I needed it for yast cd-creator. When generating the index, I've got the following errors : 'error: no dbpath has been set' 'error: cannot open Packages database in' When adding this source in YaST, it segfaults when I try to install software. I used YOU to keep my NLD up to date. What can I do ? Thanks for your help, Pierre

2 2

yast2-installation 2.9.89 provides no installation client module
by Deke Clinger 15 Dec '04

15 Dec '04

Greetings, I seem to have found a bug. The latest yast2-installation RPM does not provide an installation client module: ------------------------------------------------------------------------------ linux:~ # rpm -qa | grep ^yast2-installation yast2-installation-2.9.86-0.2 linux:~ # yast2 installation <yast runs - shows curses interface> linux:~ # rpm -Uvh yast2-installation-2.9.89-0.2.noarch.rpm Preparing... ########################################### [100%] 1:yast2-installation ########################################### [100%] linux:~ # rpm -qa | grep ^yast2-installation yast2-installation-2.9.89-0.2 linux:~ # yast2 installation No such client module installation Run 'yast2 -h' for help on usage ------------------------------------------------------------------------------ This means that if yast2-installation-2.9.89-0.2.noarch.rpm is included in an autoyast updates directory the installation will not complete: network devices aren't set up, passwords aren't set, etc. If I remove this package and rebuild the descriptions the installation goes as expected. So, this is an FYI to the list and a request to any SuSE/Novell people to get this corrected. Regards, -Deke

2 4

SLES8 installation from authenticating HTTP
by Johannes Klug 15 Dec '04

15 Dec '04

Hello, I'd like to install SLES8 via HTTP, and use authentication. It works fine with YOU, but SLES seems to be unable to install via auth. http. "401 Authorization required" is all I get, is there a way to set username and password? I also tried install=http://username:password@<ip-addr>/sles8 at the install prompt, but this fails, too. Thanks in advance, Johannes Klug

1 0

Up to date SLES 9.0 segfaults with local source
by Pierre Allix 15 Dec '04

15 Dec '04

Hi, I created seven local directories (/var/cds/cd1/, ..., /var/cds6/, /var/cds/sdk1) and an index with genIS_PLAINcache to have a local source of packages. I needed it for yast cd-creator. When adding this source in YaST, it segfaults when I try to install software. I used YOU to keep my SLES up to date. What can I do ? Thanks for your help, Pierre

1 0

YaST CD Creator SLES9 - sources missing?
by Kai Groshert 15 Dec '04

15 Dec '04

Hello all, I'm trying to use the YaST CD Creator in SLES9 to create an installation CD of my current system (just a minimal install). I'm starting "yast2 cd-creator", choose "Add", now I select my generated autoyast.xml file or "Package Manager". In any case I get the "Source Selection" screen next but the list is completely empty, so I cannot continue. As I understand there should be the same SuSE CDs listed here which are also listed in "YaST2 -> Software -> Change Source of Installation". Any idea how to get some sources into the list? Thanks for any help... PS: I'm using the vanilla "RC5" images downloadable from the Novell website. Regards, Kai -- Kai Groshert mailto:kai.groshert@porsche.de PIKS GmbH, CC-Unix phone:+49-(0)711-911-18541 Porschestrasse, D-71287 Weissach fax:+49-(0)711-911-3188 PIKS GmbH - The Porsche IT-Company - Competence Center UNIX-Systems

2 3

RE: [suse-autoinstall] SLES8 user setup failing with uid/gid/home
by Michael Shannon 15 Dec '04

15 Dec '04

I had problems getting user and group creation to work correctly as well, so I just created a post install script that called groupadd and useradd, not as elegant as using yast, but not nearly as frustrating either. groupadd -g 123 groupname useradd -d /home/username -m -c "gecos info" -s /bin/shell username -m -----Original Message----- From: Michael Czyz [mailto:czyzm@yahoo.com] Sent: Tuesday, December 14, 2004 4:44 PM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] SLES8 user setup failing with uid/gid/home I've been beating against this for almost a full day now and it defies any sense as far as i can tell. I can successfully create users without a problem, unless i try to specify a uid, gid, or home element. using the following config: <users config:type="list"> <user> <encrypted config:type="boolean">true</encrypted> <username>root</username> <user_password/> </user> <user> <encrypted config:type="boolean">false</encrypted> <username>eaws</username> <user_password>xxx</user_password> <forename>EA</forename> <surname>Admin</surname> <uid>1011</uid> </user> <user> <encrypted config:type="boolean">false</encrypted> <username>ftpuser</username> <user_password>xxx</user_password> <forename>FTP</forename> <surname>Account</surname> <gid>205</gid> <uid config:type="integer">480</uid> <home>/usr/ftproot/triggerjobs</home> </user> </users> i get errors on both the eaws and ftpuser users. for the eaws user: 2004-12-14 03:46:47 <3> wfgGCbase(495) [Interpreter] modules/UserWriteStack.ycp:152 Invalid initial value "1011" for variable uid, which has been declared as integer 2004-12-14 03:46:47 <3> wfgGCbase(495) [Interpreter] modules/UserWriteStack.ycp:157 [WFM] Undeclared variable uid etc.. for the ftpuser i get the same error message, even though i explicitly declare uid as integer. but i also get an error on the gid. this seems to get parsed correctly, and turned into the correct group name based on the gid (no integer problem there) but the useradd line that gets created contains: -G dialout,uucp,video,audio ftpuser, which causes an error because of the lack of , between audio and ftpuser i also sometimes seem to get an error creating the home directory specified above, but this seems to be intermitent. any ideas on why uid isn't treated as an integer, gid gets parsed but not added to the useradd correctly, or a home directory won't get created? -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

SLES8 user setup failing with uid/gid/home
by Michael Czyz 15 Dec '04

15 Dec '04

I've been beating against this for almost a full day now and it defies any sense as far as i can tell. I can successfully create users without a problem, unless i try to specify a uid, gid, or home element. using the following config: <users config:type="list"> <user> <encrypted config:type="boolean">true</encrypted> <username>root</username> <user_password/> </user> <user> <encrypted config:type="boolean">false</encrypted> <username>eaws</username> <user_password>xxx</user_password> <forename>EA</forename> <surname>Admin</surname> <uid>1011</uid> </user> <user> <encrypted config:type="boolean">false</encrypted> <username>ftpuser</username> <user_password>xxx</user_password> <forename>FTP</forename> <surname>Account</surname> <gid>205</gid> <uid config:type="integer">480</uid> <home>/usr/ftproot/triggerjobs</home> </user> </users> i get errors on both the eaws and ftpuser users. for the eaws user: 2004-12-14 03:46:47 <3> wfgGCbase(495) [Interpreter] modules/UserWriteStack.ycp:152 Invalid initial value "1011" for variable uid, which has been declared as integer 2004-12-14 03:46:47 <3> wfgGCbase(495) [Interpreter] modules/UserWriteStack.ycp:157 [WFM] Undeclared variable uid etc.. for the ftpuser i get the same error message, even though i explicitly declare uid as integer. but i also get an error on the gid. this seems to get parsed correctly, and turned into the correct group name based on the gid (no integer problem there) but the useradd line that gets created contains: -G dialout,uucp,video,audio ftpuser, which causes an error because of the lack of , between audio and ftpuser i also sometimes seem to get an error creating the home directory specified above, but this seems to be intermitent. any ideas on why uid isn't treated as an integer, gid gets parsed but not added to the useradd correctly, or a home directory won't get created?

1 0

Using only Linux partitions and blank space to autopartition
by Jesse Keating 14 Dec '04

14 Dec '04

Is there a partition <use></use> option to just reuse existing Linux partitions and blank space? Red Hat has this for kickstart, looking for the same with autoinstall. Thanks. Oh, target SUSE is SLES9 and SUSE Pro 9.2 -- Jesse Keating RHCE Pogo Linux -- Linux Systems Engineer tel: (888) 828-7646 ex: 436

1 1

Own RPM's
by cozypaul＠web.de 14 Dec '04

14 Dec '04

Hi All, Finally works my server correct, thanx a lot for all :=)). Now i have another qestion, i'd like to install via autoyast my own RPM's, first idea was a postinstall script with wget URL && rpm -ihv, it works, but i want to integrate this packages (own RPM's) in my repository. Have anyone own good experinces with such a problem ? Thank you very much for any advice greetings Cozy Paul __________________________________________________________ Mit WEB.DE FreePhone mit hoechster Qualitaet ab 0 Ct./Min. weltweit telefonieren! http://freephone.web.de/?mc=021201

1 0

custom kernel name
by Brian Corriveau 14 Dec '04

14 Dec '04

Hello, Our kernel is not normally called vmlinuz. I see when the installer is running a message flash by that says "cannot open kernel image /boot/vmlinuz". How can I customize the install data so that it uses a different name? thanks Brian

1 0

HTTP Installationsource using Port other than 80????
by Clormann, Stefanie 13 Dec '04

13 Dec '04

Hi, I am using sles9 and i am trying to install via http port 8080. But it seems that it does not pick up the port. It gets the xml file but it cannot connet to the installationserver on port 8080 What`s wrong? Do I need a patch or something like that? My isolinux.cfg looks like that: label http kernel linux append initrd=initrd autoyast=http://IP:8080/workstation/autoyast/profile/autoinst.xml UseDHCP=1 Install=http://IP:8080/autoyast/ Please help me!!!! Thanks. Stefanie

1 0

Repository...
by cozypaul＠web.de 13 Dec '04

13 Dec '04

Hi all, I would like to ask all, who can help.Can anyone please tell how to setup http or nfs repository. I've read a howto from Nashif 5 or 7 times. Maybe i'am making a mistake. The whole time a get the following message :"could not set base selection : default" . many greetings and thanks a lot Cozy Paul __________________________________________________________ Mit WEB.DE FreePhone mit hoechster Qualitaet ab 0 Ct./Min. weltweit telefonieren! http://freephone.web.de/?mc=021201

2 1

SuSE 9.2: nbgrub, sata
by Martin Fischer 13 Dec '04

13 Dec '04

hiya @all, since suse 9.2 prof. i get in trouble with netbootgrub. tftpd do his job well.. after loading the kernel and initrd via netbootgrub no decompression starts.. no failure message, just nothing happens... suse 9.0 works fine with netbootgrub.. i disabled the 'grubstuff' in dhcpd.conf and configure a 'fall back' to pxelinux and this works fine with suse 9.2.. how can i fix this problem to get a running netbootgrub with suse 9.2? the second problem i have: i would like to install suse 9.2 on a sata-drive but autoyast fails, because autoyast can't find /dev/sda for formatting.. with suse 9.0 works everything fine (sata = ide-support = /dev/hda)... any ideas? -- regards Martin Fischer BCC Business Communication Company GmbH Mittelweg 7 38106 Braunschweig Tel. 0800/2223733 Fax 0531/383-4385 Communication for Your Business

2 2

Re: [suse-autoinstall] Installing SLES 9 with autoyast
by Jochen Schaefer 13 Dec '04

13 Dec '04

Hi, it seems that the setup of your repository is wrong. But if you install vi HTTP you should see the missing parts for autoyast in a logfile of your webserver. Mostly /var/log/httpd/access.log with apache. >>> <cozypaul(a)web.de> 12/13/04 10:03 AM >>> Hi All, i' trying to install my SLES9 server. For this goal i've got two repositorys on the same server (NFS and HTTP). When i try to install via http each time i get an error message : "could not set base selection : default" I've thought ,that the xml file was corrupt and put this file on the floppy. After that i've started install from cdrom: install=cd autoyast=floppy:///autoinst.xml and it works ... Could anyone help me Greetings and thanx Cozy Paul __________________________________________________________ Mit WEB.DE FreePhone mit hoechster Qualitaet ab 0 Ct./Min. weltweit telefonieren! http://freephone.web.de/?mc=021201 -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Installing SLES 9 with autoyast
by cozypaul＠web.de 13 Dec '04

13 Dec '04

Hi All, i' trying to install my SLES9 server. For this goal i've got two repositorys on the same server (NFS and HTTP). When i try to install via http each time i get an error message : "could not set base selection : default" I've thought ,that the xml file was corrupt and put this file on the floppy. After that i've started install from cdrom: install=cd autoyast=floppy:///autoinst.xml and it works ... Could anyone help me Greetings and thanx Cozy Paul __________________________________________________________ Mit WEB.DE FreePhone mit hoechster Qualitaet ab 0 Ct./Min. weltweit telefonieren! http://freephone.web.de/?mc=021201

2 1

Hardware detection
by wilhelm koestinger1 10 Dec '04

10 Dec '04

Hello! Is it possible to deactivate hardware autodetection during AutoYaST install? The installation process finds USB and wants to load the usb kernel module. Autoinstallation is interrupted because you have to confirm this step. Thats what i don't want to. Best Regards Wilhelm Koestinger ____________________________________________________ IT Specialist AIX / Linux, RHCE IBM Global Services - Integrated Technology Services IBM Austria 66/839 Maxglaner Hauptstrasse 72 A-5017 SALZBURG Email: wilhelm_koestinger(a)at.ibm.com Cellular: +43 (664) 618 5032 Phone: +43 (662) 8388 - 9201 Fax: +43 (662) 8388 - 9330

2 1

PXE config line limited to 256 chars
by Hao Luo 09 Dec '04

09 Dec '04

Hi, all This is my pxe config file: DEFAULT test LABEL test KERNEL test/yast-SLES8.1-GA-i386z APPEND load_ramdisk=1 initrd=csm/yast-SLES8.1-GA-i386.gz ramdisk_size=65536 autoyast=nfs://172.20.3.2//netinstall/csm/1.4.1 /autoyast.SLES8.1/172.20.3.25.xml install=nfs://172.20.3.2 /netinstall/Linux/SLES/8.1/i386/GA/ ip=172.20.3.25 netmask=255.255.255.0 acpi=oldboot netdevice=eth0 As I know, pxe cmd line passed to autoyast will be cut by kernel to no more than 256 chars, but last line in my config file is far more than 256 chars, how can I pass the line to autoyast without being cut? Info file is not exactly what I want because I have to prepare different initrd for different machine. Yours Sincerely, Luo Hao IBM China Software Development Laboratory Tel:86-10-82782244-3420 Mail:luohao@cn.ibm.com Address: North Area, 8/F, Ying Chuang Building No.1, East Road, Shangdi, Haidian District Beijing 100085, PRC

3 3

PXE install?
by Steve Glines 09 Dec '04

09 Dec '04

Has anyone successfully performed a PXE install of SLES9 on a system with SCSI disks? The lab I'm building works flawlessly with IDE disks but fails when I use SCSI disks. In the logs it says: modprobe -s -k scsi_hostadapter fail=2 when I run the command alone I get needs modprobe.old. Is there anyone with a clue here? Cheers -- 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 4

Cannot find installation server
by Clormann, Stefanie 09 Dec '04

09 Dec '04

Hello, I am try ing to install SLES9 via a http installation server via port 8080. But yast ist simply ignoring the port. My isolinux.cfg has the following entry: label workstation kernel linux append initrd=initrd AutoYaST=http://192.168.12.1:8080/profile/autoinst.xml UseDHCP=1 Install=http://192.168.12.2:8080/autoyast/sles9-i386/CD1/ What am I missing? I am using the original boot cd that comes with sles9. (First CD.)

1 0

custom kernel selection
by Brian Corriveau 09 Dec '04

09 Dec '04

One more question for today: I am trying to use the <kernel>my-kernel</kernel> (I've also tried just kernel like the package name) in my control file in the software part. When running auto installation I can see the kernel rpm being installed, but at the end I am informed that the kernel package failed to install and then it has trouble installing the bootloader correctly. Here is what I get when I create_packages. Is there someting missing here that I need to add or add to my kernel rpm spec file to make this work? ##---------------------------------------- =Pkg: kernel 2.4.21_Z_01_01 6 x86_64 +Req: /bin/sh -Req: +Prq: /bin/sh -Prq: +Prv: /boot/vmlinuz.boot my-kernel kernel-2.4.21_Z_01_01 -Prv: =Grp: System Environment/Kernel =Lic: GPL =Src: kernel 2.4.21_Z_01_01 6 src =Tim: 1099525554 =Loc: 1 kernel-2.4.21_Z_01_01-6.x86_64.rpm =Siz: 3079829 7714275 ##---------------------------------------- thanks Brian

2 1

Re: [suse-autoinstall] PXE install?
by Steve Glines 09 Dec '04

09 Dec '04

I don't think dhcp is the problem because I can load both Red Hat and Debian just fine this way. The Red hat kernel and initrd is a little bigger than Suse's and they are being fed off the same server. Since Suse never sees the disks at all I'm not sure what you mean by the /dev's. When Red hat boots it sees /dev/cciss/c?d? if that's what you mean. SG Marcin Kurc wrote: > I have installed many DL{360,380,...} g2 and g3, all of them worked > just fine. You might have to adjust your dhcp timeout, since it takes > a while for the NIC to initialize. Also, I assume you are using > /dev/cciss/c?d? device and not /dev/sd? > > -marcin > > > >>>> Steve Glines <sglines(a)is-cs.com> 12/08/04 3:39 pm >>> > > J.H.M. Dassen (Ray) wrote: > > >> On Wed, Dec 08, 2004 at 13:05:35 -0500, Steve Glines wrote: >> >> >>> Has anyone successfully performed a PXE install of SLES9 on a >>> system with SCSI disks? >>> >>> The lab I'm building works flawlessly with IDE disks but fails >>> when I use SCSI disks. >> >> >> It seems quite unlikely that the problem you're having is actually > > related > >> to PXE as such. You may want to test with a manual install first, >> debug > > that > >> and then base your PXE setup on those experiences. >> >> If it turns out that your SCSI controller or your SCSI disks aren't >> detected, try booting with the following kernel parameter: >> acpi=oldboot (see >> http://support.novell.com/cgi-bin/search/searchtid.cgi?/en/2004/08/wessels_… >> > > >> for more information). >> >> HTH, > > > Thanks - I would never have thought of that. I'll try it. > > For the record the target install is on a standard production HP > ProLiant system (indeed the lab is at HP). Booting from a CD works > just fine but when I do a PXE boot it can't find any disks. Using the > exact same PXE install with an old Pavilion with IDE disks works just > fine. > > I'll report any success or failure. > > SG > > -- 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.

1 0

Re: [suse-autoinstall] PXE install?
by Marcin Kurc 09 Dec '04

09 Dec '04

I have installed many DL{360,380,...} g2 and g3, all of them worked just fine. You might have to adjust your dhcp timeout, since it takes a while for the NIC to initialize. Also, I assume you are using /dev/cciss/c?d? device and not /dev/sd? -marcin >>>Steve Glines <sglines(a)is-cs.com> 12/08/04 3:39 pm >>> J.H.M. Dassen (Ray) wrote: >On Wed, Dec 08, 2004 at 13:05:35 -0500, Steve Glines wrote: > >>Has anyone successfully performed a PXE install of SLES9 on a system >>with SCSI disks? >> >>The lab I'm building works flawlessly with IDE disks but fails when I >>use SCSI disks. > > >It seems quite unlikely that the problem you're having is actually related >to PXE as such. You may want to test with a manual install first, debug that >and then base your PXE setup on those experiences. > >If it turns out that your SCSI controller or your SCSI disks aren't >detected, try booting with the following kernel parameter: >acpi=oldboot >(see >http://support.novell.com/cgi-bin/search/searchtid.cgi?/en/2004/08/wessels_… >for more information). > >HTH, Thanks - I would never have thought of that. I'll try it. For the record the target install is on a standard production HP ProLiant system (indeed the lab is at HP). Booting from a CD works just fine but when I do a PXE boot it can't find any disks. Using the exact same PXE install with an old Pavilion with IDE disks works just fine. I'll report any success or failure. SG -- 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. -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Turn off IPv6 at install-time?
by Johannes Klug 08 Dec '04

08 Dec '04

Hello! Is it possible to turn ipv6 completely off at install-time? TIA, Johannes Klug

1 0

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

Custom Package Selection
by Brian Corriveau 07 Dec '04

07 Dec '04

Hi, I'm trying to load a target with a customized minimal set of packages. I followed the instructions on Config and Installation Options 5.2 but I get to the Configure Software Selections part and a window pops up saying "Cannot set base selection", and when I ok that I get "Error while configuring software selections". I'm suspicious of the examples 4.20 and 4.21 because it seems like the =Sel should be 'My' and the category should be Base-System and not addon in order to be picked up in 4.21 by the <base>My</base>. I've tried the examples and variations and I always get the same errors. Here's what it looks like <software> <addons config:type="list"> <addon>Base-System</addon> <addon>YaST2</addon> </addons> <base>My</base> </software> If I replace My with Minimal it works fine. What am I missing? Is there some way to know in greater detail what is going wrong? The My.sel has a large list of packages from a previous inhouse installation. Could that be interacting in a bad way so that I would see the errors I'm getting? Maybe I need to cull out any overlap between My and Base-System? One more easy one, how do I select a valid =Ord value for my Selection? Thanks a lot, Brian

2 5

RE: [suse-autoinstall] has anyone been able to use AutoYast with PXE boot on a tg3 based machine?
by Benjamin Shi 07 Dec '04

07 Dec '04

Try pxe boot with pxelinux.0, we have bcm5700 on tyan working with autoyast just fine. -----Original Message----- From: Joe Landman [mailto:landman@scalableinformatics.com] Sent: Saturday, December 04, 2004 12:01 PM To: 'suse-autoinstall(a)suse.com' Subject: [suse-autoinstall] has anyone been able to use AutoYast with PXE boot on a tg3 based machine? Hi folks: Not directly autoyast, but one of the supporting utils ... My machines have Broadcom chips that map into the tg3 driver. I set up autoyast as per the howto posted here recently (thanks!), and tried the boot. It probes for an RTL8139 and hangs. They units are Tyan S2882 based, and work fine when booting by DVD. From what I read, the issue are the drivers compiled into grub (pxegrub to be precise). Has anyone a working rpm or build of grub with the relevant patches, or a pointer to them? This is on a SuSE 9.2 AMD64 unit. Thanks! Joe -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1