August 2005 - openSUSE Autoinstall - openSUSE Mailing Lists

Problems installing Festival 1.9.5 on Suse 9.3
by Marc Scheib 27 Aug '05

27 Aug '05

Sorry for bothering you: I am trying to install the Festival RPM from the KDE Accessibility Project, but YAST does not show anything about the new Version. I am a bloody newbie to the Suse Installation System and therefore would like to ask you kindly for a hint on my installation problem. I am working on a Suse 9.3 Installation. Konqueror shows me a button 'Install Package with YAST' when I download the RPM from http:// accessibility.kde.org/developer/kttsd/index.php, but when I click on that button YAST shows me only the old Version 1.4.3 from the Suse- Repository.. Please, how can I point Yast towards the new RPM? Thank you for your cooperation, Marc Scheib (mailto:marc(at)mindbomb.de)

1 0

Re: [suse-autoinstall] autoyast fails on partitioning on Dell Precision 670
by Hans-Joachim Ehlers 26 Aug '05

26 Aug '05

Hi Tobin, the Example to determine the disk type is not from me. I found it on the net and used it as an example for our installation enviroment. But anyway. The Licensing prompt should stay for 10 seconds and then the installation should procced further. If not you have another problem. have a nice weekend Hajo who will be back on monday. >>> GrueMaster <gruemaster(a)yahoo.com> 08/26/05 8:32 pm >>> Thanks for the rules help. I've been studying the online documentation and was very confused about the directory structure needed for the rules.xml. Your rules.xml example worked flawlessly. I'd recommend adding your example as it is written to the documentation. I've now progressed to getting the system imaged and booting (Whoo Hoo!) Now to get my post install script running again (I yanked it to simplify debugging the partitioning issues). Next question, is there a setting to allow installing without the "Licensing" prompt, or does the timeout automaticly assume acceptance? ....

1 0

Re: [suse-autoinstall] autoyast fails on partitioning on Dell Precision 670
by Hans-Joachim Ehlers 26 Aug '05

26 Aug '05

My partitioning section is directly AFTER </general> . I have been told that the order shall not matter but who knows. So give it a try. If the order change will help then there is no need for a rules.xml At least at my site i have no problems with SATA and IDE drive. About SCSI i can not tell. If you need a rules.xml 1) Get the documentation about autoyast ( Mentioned in a previous post to this list by me ) 2) Below your autoinstallation source directory ( Example: MyServer:/export/suse/autoinstall/ ) create the following subdirectories: ./rules ( Will hold only the rules.xml ) ./classes ( Will hold the autoinstall.xml and sda.xml and hda.xml ) A few importent hints: A) The autoyast entry MUST end with an "/" . Example: autoyast=nfs://MyServer:/export/suse/autoinstall/ otherwise the rules.cml will NOT be parsed. B) The rules.xml MUST include a rule to include your standard "installation.xml" because it will be parsed only what has a MATCH in the rules.xml C) You must use " echo -n" in your script section to get rid of the NEWLINE. Otherwise the match will not work. The following is an example of a "rules.xml" to determine the disk type <?xml version="1.0"?> <autoinstall xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <rules config:type="list"> <rule> <custom1> <script> <![CDATA[ if grep hda /proc/partitions > /dev/null; then echo -n "hda" else echo -n "sda" fi; ]]> </script> <match>*</match> <match_type>exact</match_type> </custom1> <result> <profile>classes/@custom1@.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> <rule> <custom1> <match>*</match> <match_type>exact</match_type> </custom1> <result> <profile>classes/autoinst.xml</profile> <continue config:type="boolean">false</continue> </result> </rule> </rules> </autoinstall> ---------------------------------------------------------- The first rule will parse your ( sda.xml or hda.xml ) and continue to the next rule The second rule will match everything so it does include the classes/autoinst.xml File. Now further rules will be parsed afterwards. The sda.xml is just a stript down version from your autoinst.xml containing a Section like down below ( NOT tested ) . For the hda.xml you must just change the device section. To get these Section i would use "yast2 autoyast " and create a new xml file where only the paritioning section has been configured with yast2. Afterwards take everthing out of the file what is not related to the partitioning . Run "xmllint" to verify the file and you should be happy. <?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"> <install> <partitioning config:type="list"> <device>/dev/sda</device> <drive> <use>all</use> </drive> </partitioning> </install> </profile> hth Hajo >>> GrueMaster <gruemaster(a)yahoo.com> 08/26/05 5:49 pm >>> I fixed the boot loader section, but that isn't where the problem is. Yast fails at "Create partition plans". Hey, I think I figured it out (somewhat). I added <device>/dev/sda</device> to the partitioning section and it now blows past that and installs. Now I need to figure out how to use rules, as we have IDE, SCSI, and SATA systems. SATA and SCSI will work with this config, but IDE needs /dev/hda. Any suggestions?

1 0

Re: [suse-autoinstall] autoyast fails on partitioning on Dell Precision 670
by Hans-Joachim Ehlers 26 Aug '05

26 Aug '05

Stripped down xml file ? You are kidding ;-) Does the creation of the partion fails or is just the bootloader not active. Also for troubleshooting: Have you verified your auto.xml with "xmllint" Does the driver for your hba are being loaded ? BTW: What i do not understand is your bootloader Section: Because it says not to activate it. Below yor xml File i have put an extract of my boatloader section. hth Hajo >From your xml File .... <bootloader> <activate config:type="boolean">false</activate> <global config:type="list"/> <loader_device></loader_device> <loader_type>grub</loader_type> <location>mbr</location> <repl_mbr config:type="boolean">false</repl_mbr> </bootloader> .... Extract from my xml File: <bootloader> <activate config:type="boolean">true</activate> <global config:type="list"/> <loader_device></loader_device> <loader_type>lilo</loader_type> <location>mbr</location> <repl_mbr config:type="boolean">true</repl_mbr> <sections config:type="list"/> </bootloader> >>> GrueMaster <gruemaster(a)yahoo.com> 08/26/05 2:03 am >>> I'm still trying to get autoinstall for Suse 9.3 to work on this system. Autoyast fails to create partitions. Works just fine installing manually, but I need to be able to implement autoinstall. Attached is my stripped down auto.xml file. It worked on a few older systems, but not here. Anything else I can try? Tobin --------------------------------- Start your day with Yahoo! - make it your home page ============================ Hans-Joachim Ehlers UNIX Systems Engineer EUMETSAT Am Kavalleriesand, 31 64295, Darmstadt, Germany Tel : +49 6151 807-7307 eMail : hansjoachim.ehlers(a)eumetsat.int iNet : www.eumetsat.de

3 2

Re: [suse-autoinstall] SLES SP2 AutoYast problems.
by Hans-Joachim Ehlers 26 Aug '05

26 Aug '05

>From my experience: Keep thinks simple in the beginning 1 ) So no software raid and what so ever. - Simple Partition schema - Do not name the disk for installation ( SATA will be detected as /dev/sd[a-z]X devices 2 ) use text mode for Installation ( Graphical Installations fails for me ) 3 ) Have a large defined swap partition because if you use http for installation autoyast will copy pretty much of the installation to its local ram disk ( memory ) You can use "top" on a different terminal 4) Take a look at the /var/log/Yast log files ( The ones on the ram disk ) 5) Switch to terminal 4 ( from memory ) to see what has been loaded and what has happend. hth Hajo >>> "Michael T. Halligan" <michael(a)halligan.org> 08/26/05 3:02 pm >>> So I've been struggling for a couple of days trying to get AutoYast to work. I can install on these servers manually.. However, if I create a reference profile, or creaet my own profile, or really do anything with autoyast, every time I try to install, the server gets as far as loading the device driver disks, then stops with a big red box reading "An error occurred during installation" That's it. I built an installation source using SLES 9S SP2 x86_64. I am trying to boot with y2debug and setting a loghost, but the messages i'm getting aren't exactly helpful. The servers I'm installing on are del sc1425s with single 3ghz procs and dual sata drives. I'm attempting to setup sles9-sp2 with software raid1. Any help would be appreciated. The last few lines I'll see in syslog are: ug 25 22:10:39 BOB yast2[3642]: <1> [ui-ncurses] NCurses.cc(Refresh):407 start refresh ... Aug 25 22:10:39 BOB yast2[3642]: <1> [ncurses] NCurses.cc(SetTitle):459 Draw title called Aug 25 22:10:39 BOB yast2[3642]: <1> [ui-ncurses] NCurses.cc(Refresh):411 done refresh ... Aug 25 22:10:39 BOB yast2[3606]: <1> [wfm] Y2WFMComponent.cc(SetLanguage):403 SET encoding to: UTF-8 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Accept" -> F10 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Add" -> F3 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Back" -> F8 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Cancel" -> F9 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Do Not Accept" -> F9 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Don't install" -> F9 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Finish" -> F10 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Help" -> F1 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Install" -> F10 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Next" -> F10 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "No" -> F9 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "OK" -> F10 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Quit" -> F9 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Save" -> F10 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Yes" -> F10 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Close" -> F10 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Continue" -> F10 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Delete" -> F5 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Edit" -> F4 Aug 25 22:10:39 BOB yast2[3606]: <1> [YCP] StorageDevices.ycp:243 before .probe.floppy Aug 25 22:10:39 BOB yast2[3606]: <1> [YCP] StorageDevices.ycp:245 after .probe.floppy Aug 25 22:10:39 BOB yast2[3606]: <1> [YCP] StorageDevices.ycp:267 FloppyDrives [] Aug 25 22:10:39 BOB yast2[3606]: <1> [ui-ncurses] YNCursesUI.cc(YNCursesUI):114 Stop YNCursesUI Aug 25 22:10:39 BOB yast2[3606]: <1> [ui-ncurses] NCurses.cc(NCurses):160 Shutdown NCurses... Aug 25 22:10:39 BOB yast2[3606]: <1> [ui-ncurses] NCurses.cc(NCurses):169 NCurses down Aug 25 22:10:39 BOB yast2[3606]: <1> [liby2] genericfrontend.cc(main):437 Finished YaST2 component 'y2base' -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

SLES SP2 AutoYast problems.
by Michael T. Halligan 26 Aug '05

26 Aug '05

So I've been struggling for a couple of days trying to get AutoYast to work. I can install on these servers manually.. However, if I create a reference profile, or creaet my own profile, or really do anything with autoyast, every time I try to install, the server gets as far as loading the device driver disks, then stops with a big red box reading "An error occurred during installation" That's it. I built an installation source using SLES 9S SP2 x86_64. I am trying to boot with y2debug and setting a loghost, but the messages i'm getting aren't exactly helpful. The servers I'm installing on are del sc1425s with single 3ghz procs and dual sata drives. I'm attempting to setup sles9-sp2 with software raid1. Any help would be appreciated. The last few lines I'll see in syslog are: ug 25 22:10:39 BOB yast2[3642]: <1> [ui-ncurses] NCurses.cc(Refresh):407 start refresh ... Aug 25 22:10:39 BOB yast2[3642]: <1> [ncurses] NCurses.cc(SetTitle):459 Draw title called Aug 25 22:10:39 BOB yast2[3642]: <1> [ui-ncurses] NCurses.cc(Refresh):411 done refresh ... Aug 25 22:10:39 BOB yast2[3606]: <1> [wfm] Y2WFMComponent.cc(SetLanguage):403 SET encoding to: UTF-8 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Accept" -> F10 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Add" -> F3 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Back" -> F8 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Cancel" -> F9 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Do Not Accept" -> F9 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Don't install" -> F9 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Finish" -> F10 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Help" -> F1 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Install" -> F10 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Next" -> F10 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "No" -> F9 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "OK" -> F10 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Quit" -> F9 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Save" -> F10 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Yes" -> F10 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Close" -> F10 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Continue" -> F10 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Delete" -> F5 Aug 25 22:10:39 BOB yast2[3642]: <1> [ui] YUI_builtins.cc(evaluateSetFunctionKeys):1652 Mapping "Edit" -> F4 Aug 25 22:10:39 BOB yast2[3606]: <1> [YCP] StorageDevices.ycp:243 before .probe.floppy Aug 25 22:10:39 BOB yast2[3606]: <1> [YCP] StorageDevices.ycp:245 after .probe.floppy Aug 25 22:10:39 BOB yast2[3606]: <1> [YCP] StorageDevices.ycp:267 FloppyDrives [] Aug 25 22:10:39 BOB yast2[3606]: <1> [ui-ncurses] YNCursesUI.cc(YNCursesUI):114 Stop YNCursesUI Aug 25 22:10:39 BOB yast2[3606]: <1> [ui-ncurses] NCurses.cc(NCurses):160 Shutdown NCurses... Aug 25 22:10:39 BOB yast2[3606]: <1> [ui-ncurses] NCurses.cc(NCurses):169 NCurses down Aug 25 22:10:39 BOB yast2[3606]: <1> [liby2] genericfrontend.cc(main):437 Finished YaST2 component 'y2base'

1 0

autoyast fails on partitioning on Dell Precision 670
by GrueMaster 26 Aug '05

26 Aug '05

I'm still trying to get autoinstall for Suse 9.3 to work on this system. Autoyast fails to create partitions. Works just fine installing manually, but I need to be able to implement autoinstall. Attached is my stripped down auto.xml file. It worked on a few older systems, but not here. Anything else I can try? Tobin --------------------------------- Start your day with Yahoo! - make it your home page

1 0

USEFUL AutoYast logging information?
by Michael T. Halligan 24 Aug '05

24 Aug '05

I'm failing miserably at installing SLES9 on a pile of Dell SC1425s. I have no idea why. I'm booting with verbose=1 and loghost=my.loghost .. The messages I'm seeing when the install fails are "An error occured during installation". The only information being sent to my loghost is : Aug 23 16:22:35 newhost yast2[1860]: <1> [YCP] StorageDevices.ycp:243 before .probe.floppy Aug 23 16:22:35 newhost yast2[1860]: <1> [YCP] StorageDevices.ycp:245 after .probe.floppy Aug 23 16:22:35 newhost yast2[1860]: <1> [YCP] StorageDevices.ycp:267 FloppyDrives [] Aug 23 16:22:35 newhost yast2[1860]: <1> [ui-ncurses] YNCursesUI.cc(YNCursesUI):114 Stop YNCursesUI Aug 23 16:22:35 newhost yast2[1860]: <1> [ui-ncurses] NCurses.cc(NCurses):160 Shutdown NCurses... Aug 23 16:22:35 newhost yast2[1860]: <1> [ui-ncurses] NCurses.cc(NCurses):169 NCurses down Aug 23 16:22:35 newhost yast2[1860]: <1> [liby2] genericfrontend.cc(main):437 Finished YaST2 component 'y2base' The problem has been compounded by the complete worthlessness of Dell's BMC and their broken serial port.

1 0

Re: [suse-autoinstall] Question about ndiswrapper
by Hans-Joachim Ehlers 24 Aug '05

24 Aug '05

On my Suse 9.3 PC i have found: # modprobe -l ndiswrapper /lib/modules/2.6.11.4-20a-default/extra/ndiswrapper.ko and a # rpm -qf /lib/modules/2.6.11.4-20a-default/extra/ndiswrapper.ko kernel-default-2.6.11.4-20a hth Hajo >>> "Malcom Kemp" <mkemp(a)bellsouth.net> 08/21/05 8:48 pm >>> This may be a little off subject, but if someone could point me in the right direction, I would appreciate it. I have 9.3 and am trying to get an unsupported WAN card to work. I have used Yast to install the ndiswrapper package, which it does. I have used the -i to install the driver, and with the -l option it tells me it is there and that it looks correct. When I try to modprobe ndiswrapper however, it gives me fatal error, "Module ndiswrapper not found". I removed the package and reinstalled it, but still have same error. How do I get the kernel module put on the system? -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

1 0

Re: [suse-autoinstall] Adding the file "info" to an bootable CD/DVD
by Hans-Joachim Ehlers 24 Aug '05

24 Aug '05

Hi Lee, thanks to you and the others as well. I had to do only cometic changes to your example: ----> gzip -dc /work-iso/initrd >/tmp/initrd.img <------ mkdir /work-initrd; cd /work-initrd # make a place to extract it cpio -i < /tmp/initrd.img # Extract it from cpio archive cp YOUR_INFO_FILE info # Put your info file in there ----> find . | cpio -H newc -o > /tmp/initrd.img <----- ----> gzip -c /tmp/initrd.img >/work-iso/initrd <----- So thanks a lot Hajo >>> Lee Mayes <autoinst(a)mayeses.com> 08/23/05 2:12 pm >>> Hi Hajo, initrd is on the CD, but it's in its compressed form. Starting with 9.3 for suse (I think it's linux 2.6.10 and greater but don't hold me to that, Fedora Core 4 is the same way :) initrd.img is now a cpio image, not a filesystem, so you don't have to loopmount it to make changes. # I assume the original ISO is exploded under /work-iso gzip -dc /work-iso/initrd.img >/tmp/initrd.img # Uncompress it mkdir /work-initrd; cd /work-initrd # make a place to extract it cpio -i </tmp/initrd.img # Extract it from cpio archive cp /YOUR_INFO_FILE info # Put your info file in there find . | cpio -H newc -o /tmp/initrd.img # make new initrd.img gzip -c /tmp/initrd.img >/work-iso/initrd.img # Put in iso dir run mkisofs against /work-iso to create a new ISO image with your info file in it. Since I've got initrd open anyway, I also poke my autoyast.xml file in there and add: AutoYaST: file:///autoyast.xml to the info file so the bootimage is 100% self contained. Hope that helps! Lee On Tue, 2005-08-23 at 13:48 +0200, Hans-Joachim Ehlers wrote: > Hi folks, > Give 9.3 Suse Pro > Booting from CD > Installation from Network > > > I would like to put the file "info" with is used by linuxrc on the > installation cd because using an additional floppy causes to much > trouble. > > But i am a little bit lost about howto do that. > > Do i have to change the isolinux.cfg ? > Documentation tells me that the info file should be in initrd but i can > not find that directory. ? > > Any tips ? > tia > Hajo > > > > > > > ============================ > Hans-Joachim Ehlers > UNIX Systems Engineer > EUMETSAT > Am Kavalleriesand, 31 > 64295, Darmstadt, Germany > Tel : +49 6151 807-7307 > eMail : hansjoachim.ehlers(a)eumetsat.int > iNet : www.eumetsat.de > -- Lee Mayes <autoinst(a)mayeses.com>

1 0