November 2002 - openSUSE Autoinstall - openSUSE Mailing Lists

Re: [suse-autoinstall] Newbie Problem with Video on 8.1 Install
by Dom Incollingo 09 Nov '02

09 Nov '02

Thanks very much for the info. Being a newbie, I am a little confused about this process. How exactly do I boot to the console rather than to X? In order to manually install the video driver, I assume that I would use Lynx to download the driver, and then install the driver as an RPM or perhaps by extracting it from a tar file. Is there an easier way? Thanks. ----- Original Message ----- From: Carl William Spitzer IV <cwsiv(a)juno.com> Date: Fri, 8 Nov 2002 14:24:28 PST To: dom_incollingo(a)linuxmail.org Subject: Re: [suse-autoinstall] Newbie Problem with Video on 8.1 Install you need to do a custome install and have the system boot directly to console not to X. Once there you can do a manual install of the updated driver. Your not the only one with nvidea problems. My local lug went through a week long discussion on that. cwsiv(a)linuxmail.org On Fri, 08 Nov 2002 22:04:09 +0800 "Dom Incollingo" <dom_incollingo(a)linuxmail.org> writes: >Hello, > >I recently tried to do a fresh install of 8.1 Professional from the >install CDs. The install process appeared to go normally (no obvious >error messages). Although I noticed that the install CD contained an >older version of the nVidia driver for my GeForce4 video card. After >the install completed, I tried to boot the system. The boot went >normally until late in the boot process when the screen flickers and >the video driver starts. At that point, the boot process >stopped and the screen went black. I tried to boot the system several >times with the same results. (I finally gave up and installed 8.0, >which which booted successfully.) Has anyone experienced this problem >with 8.1 or know how to solve it? Thanks very much for your help. > >Dom >-- >______________________________________________ >http://www.linuxmail.org/ >Now with POP3/IMAP access for only US$19.95/yr > >Powered by Outblaze > >-- >To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com >For additional commands, e-mail: suse-autoinstall-help(a)suse.com > > ________________________________________________________________ Sign Up for Juno Platinum Internet Access Today Only $9.95 per month! Visit www.juno.com -- ______________________________________________ http://www.linuxmail.org/ Now with POP3/IMAP access for only US$19.95/yr Powered by Outblaze

1 0

Two autoyast problems: bootloader location ignored and raid0 ignored
by Peter.Seiderer＠gmx.de 08 Nov '02

08 Nov '02

Hello, autoyast up and running (SuSE-8.1) but have two problems: - <bootloader><location>/dev/hda</location></bootloader> seems to be ignored by autoyast. The bootloader ist always installed in /dev/md1 (the location of /boot), in /etc/lilo.conf the configuration is 'boot = /dev/md1' afterwards. The same with mbr instead of /dev/hda. - Configuration of two raid devices, one raid0 the other one as raid1. But both are installed and entered to /etc/raidtab as raid1. Remark: all partitions from earlier are destroyed via fdisk to avoid trouble while running autoyast from auotmatic raid detection via persistent_superblock. Thanks for your help in advance, Peter My autoyast configuration file: <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/YaST2/include/autoinstall/profile.dtd"> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <configure> <files config:type="list"/> <networking> <dns> <dhcp_hostname config:type="boolean">false</dhcp_hostname> <dhcp_resolv config:type="boolean">false</dhcp_resolv> <domain>mydomain.de</domain> <hostname>linux</hostname> </dns> <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <broadcast>192.168.64.255</broadcast> <device>eth0</device> <ipaddr>192.168.64.2</ipaddr> <module>via-rhine</module> <netmask>255.255.255.0</netmask> <network>192.168.64.0</network> <startmode>onboot</startmode> <wireless>no</wireless> </interface> </interfaces> <routing> <ip_forward config:type="boolean">false</ip_forward> </routing> </networking> <runlevels> <default>3</default> </runlevels> <scripts> <post-scripts config:type="list"/> <chroot-scripts config:type="list"/> <pre-scripts config:type="list"/> </scripts> <users config:type="list"> <user> <encrypted>true</encrypted> <user_password>password</user_password> <username>testuser</username> </user> </users> <x11> <color_depth config:type="integer">24</color_depth> <configure_x11 config:type="boolean">true</configure_x11> <display_manager>kdm</display_manager> <enable_3d config:type="boolean">true</enable_3d> <monitor> <display> <max_hsync config:type="integer">64</max_hsync> <max_vsync config:type="integer">120</max_vsync> <min_hsync config:type="integer">31</min_hsync> <min_vsync config:type="integer">50</min_vsync> </display> <monitor_device>17SF</monitor_device> <monitor_vendor>SONY</monitor_vendor> </monitor> <resolution>1024x768</resolution> <start_x11 config:type="boolean">false</start_x11> </x11> </configure> <install> <bootloader> <activate config:type="boolean">true</activate> <kernel_parameters></kernel_parameters> <lba_support config:type="boolean">true</lba_support> <linear config:type="boolean">false</linear> <location>/dev/hda</location> <write_bootloader config:type="boolean">true</write_bootloader> </bootloader> <general> <clock> <hwclock>GMT</hwclock> <timezone>Europe/Berlin</timezone> </clock> <keyboard> <keymap>english-us</keymap> </keyboard> <language>en_US</language> <mouse> <id>20_imps2</id> </mouse> </general> <partitioning config:type="list"> <drive> <device>/dev/hda</device> <partitions config:type="list"> <partition> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">1</partition_nr> <size>1gb</size> </partition> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">2</partition_nr> <raid_name>/dev/md0</raid_name> <size>15gb</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <mount>/data_2_1</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">3</partition_nr> <size>15gb</size> </partition> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">4</partition_nr> <raid_name>/dev/md1</raid_name> <size>auto</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/hdc</device> <partitions config:type="list"> <partition> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">1</partition_nr> <size>1gb</size> </partition> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">2</partition_nr> <raid_name>/dev/md0</raid_name> <size>15gb</size> </partition> <partition> <filesystem config:type="symbol">reiser</filesystem> <mount>/data_2_2</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">3</partition_nr> <size>15gb</size> </partition> <partition> <format config:type="boolean">false</format> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">4</partition_nr> <raid_name>/dev/md1</raid_name> <size>auto</size> </partition> </partitions> <use>all</use> </drive> </partitioning> <raid config:type="list"> <device> <device_name>/dev/md0</device_name> <filesystem config:type="symbol">ext3</filesystem> <filesystem_id config:type="integer">131</filesystem_id> <format config:type="boolean">true</format> <mount>/data_1</mount> <persistent_superblock config:type="boolean">true</persistent_superblock> <raid_type>raid0</raid_type> </device> <device> <device_name>/dev/md1</device_name> <filesystem config:type="symbol">ext3</filesystem> <filesystem_id config:type="integer">131</filesystem_id> <format config:type="boolean">true</format> <mount>/</mount> <parity_algorithm>left-asymmetric</parity_algorithm> <persistent_superblock config:type="boolean">true</persistent_superblock> <raid_type>raid1</raid_type> </device> </raid> <software> <base>Minimal</base> <packages config:type="list"> <package>libxml2</package> <package>procmail</package> <package>src_vipa</package> <package>sysvinit</package> <package>timezone</package> <package>xfsprogs</package> <package>yast2-ncurses</package> <package>netcfg</package> <package>yast2-theme-SuSELinux</package> <package>aaa_version</package> <package>filesystem</package> <package>sash</package> <package>terminfo</package> <package>yast2-packager</package> <package>providers</package> <package>yast2-trans-en_US</package> <package>glibc</package> <package>ash</package> <package>attr</package> <package>libgcc</package> <package>libjpeg</package> <package>lsof</package> <package>m4</package> <package>mdadm</package> <package>ksymoops</package> <package>ncurses</package> <package>net-tools</package> <package>netcat</package> <package>bzip2</package> <package>cpio</package> <package>cpp</package> <package>pciutils</package> <package>gdbm</package> <package>hdparm</package> <package>iptables</package> <package>mktemp</package> <package>eject</package> <package>file</package> <package>fillup</package> <package>findutils</package> <package>diffutils</package> <package>e2fsprogs</package> <package>ed</package> <package>libxcrypt</package> <package>liby2util</package> <package>popt</package> <package>recode</package> <package>reiserfs</package> <package>sed</package> <package>tar</package> <package>textutils</package> <package>usbutils</package> <package>utempter</package> <package>zlib</package> <package>jfsutils</package> <package>lukemftp</package> <package>acl</package> <package>dialog</package> <package>libstdc++</package> <package>readline</package> <package>bash</package> <package>bc</package> <package>parted</package> <package>fileutils</package> <package>db</package> <package>yast2-packagemanager</package> <package>k_deflt</package> <package>liblcms</package> <package>logrotate</package> <package>less</package> <package>cracklib</package> <package>pcre</package> <package>perl</package> <package>grep</package> <package>gzip</package> <package>initviocons</package> <package>iproute2</package> <package>iputils</package> <package>modutils</package> <package>aaa_skel</package> <package>bootsplash-theme-SuSE</package> <package>devs</package> <package>dhcpcd</package> <package>gawk</package> <package>libmng</package> <package>openssl</package> <package>pam</package> <package>permissions</package> <package>gpg</package> <package>groff</package> <package>finger</package> <package>rsh</package> <package>tcsh</package> <package>telnet</package> <package>sitar</package> <package>man</package> <package>heimdal-lib</package> <package>curl</package> <package>sh-utils</package> <package>aaa_base</package> <package>cyrus-sasl</package> <package>vim</package> <package>yast2-transfer</package> <package>suse-build-key</package> <package>kbd</package> <package>bootsplash</package> <package>lvm</package> <package>openldap2-client</package> <package>pam-modules</package> <package>gpm</package> <package>hwinfo</package> <package>isapnp</package> <package>fbset</package> <package>portmap</package> <package>ps</package> <package>raidtools</package> <package>rpm</package> <package>sysconfig</package> <package>syslogd</package> <package>util-linux</package> <package>SuSEfirewall2</package> <package>lilo</package> <package>grub</package> <package>hotplug</package> <package>shadow</package> <package>w3m</package> <package>yast2-core</package> <package>at</package> <package>openssh</package> <package>postfix</package> <package>siga</package> <package>yast2</package> <package>yast2-pam</package> <package>mailx</package> <package>cron</package> <package>yast2-country</package> <package>yast2-mouse</package> <package>yast2-online-update</package> <package>yast2-storage</package> <package>yast2-sysconfig</package> <package>yast2-tune</package> <package>yast2-xml</package> <package>yast2-nfs-client</package> <package>yast2-nfs-server</package> <package>yast2-runlevel</package> <package>yast2-security</package> <package>yast2-support</package> <package>yast2-bootloader</package> <package>yast2-network</package> <package>autoyast2-installation</package> <package>yast2-inetd</package> <package>yast2-users</package> <package>yast2-installation</package> <package>yast2-backup</package> <package>yast2-firewall</package> <package>yast2-ldap-client</package> <package>yast2-mail</package> <package>yast2-nis-client</package> <package>yast2-nisplus-client</package> <package>yast2-update</package> <package>yast2-nis-server</package> <package>yast2-restore</package> <package>3ddiag</package> <package>freetype2</package> <package>libpng</package> <package>libtiff</package> <package>cups-libs</package> <package>xshared</package> <package>mesasoft</package> <package>xf86_glx</package> <package>xf86tools</package> <package>mesaglu</package> <package>xf86</package> <package>binutils</package> <package>glibc-devel</package> <package>libstdc++-devel</package> <package>samba-client</package> <package>gcc</package> <package>samba</package> <package>gcc-c++</package> <package>libxslt</package> <package>mkisofs</package> <package>perl-XML-DOM</package> <package>perl-XML-Generator</package> <package>alice-compat</package> <package>autoyast2</package> <package>yast2-x11</package> <package>perl-gettext</package> <package>qt3</package> <package>saxident</package> <package>xbanner</package> <package>xmodules</package> <package>saxtools</package> <package>xloader</package> <package>sax2</package> <package>telnet-server</package> <package>inetd</package> </packages> </software> </install> </profile> -- +++ GMX - Mail, Messaging & more http://www.gmx.net +++ NEU: Mit GMX ins Internet. Rund um die Uhr für 1 ct/ Min. surfen!

1 0

Newbie Problem with Video on 8.1 Install
by Dom Incollingo 08 Nov '02

08 Nov '02

Hello, I recently tried to do a fresh install of 8.1 Professional from the install CDs. The install process appeared to go normally (no obvious error messages). Although I noticed that the install CD contained an older version of the nVidia driver for my GeForce4 video card. After the install completed, I tried to boot the system. The boot went normally until late in the boot process when the screen flickers and the video driver starts. At that point, the boot process stopped and the screen went black. I tried to boot the system several times with the same results. (I finally gave up and installed 8.0, which which booted successfully.) Has anyone experienced this problem with 8.1 or know how to solve it? Thanks very much for your help. Dom -- ______________________________________________ http://www.linuxmail.org/ Now with POP3/IMAP access for only US$19.95/yr Powered by Outblaze

1 0

Re: [suse-autoinstall] Anas Nashif: Mounting before Installation?
by Alexander.Gehrig＠RSD.rohde-schwarz.com 08 Nov '02

08 Nov '02

Hi Thanks for answer! Yes i only want to format this disks without re-partitioning, because we are using an other tool do do this much better than yast2 can do it. So i have to use this tool for partitioning harddiskdrives - it is a standard of my company. Is there any possibility to do this with an pre-scripte? I found one: !/bin/bash modprobe reiserfs # load reiserfs module mkreiserfs -f `fdisk -l /dev/sda | grep "*" | cut -b 1-9` # find active partition and create a reiserfs mkswap 'fdisk -l /dev/sda | grep "Linux swap" | cut -b 1-9` # find Linux Swap Partition and create a new swap mount -t reiserfs `fdisk -l /dev/sda | grep "*" | cut -b 1-9` /mnt # mount the reiserfs-partition to /mnt What to do, that autoinstall using a already mounted partition, and do not try to mount an other? Is there any solution to do this? I only want to know how i can mount the partitions instead of the function of autoinstall. And what i have to do to get a working 'fstab'. Thanks a lot! bye Alexander Gehrig |--------+-----------------------> | | Anas Nashif | | | <nashif(a)suse.| | | de> | | | | | | 07.11.02 | | | 18:50 | | | | |--------+-----------------------> >----------------------------------------------------------------------------| | | | An: Alexander Gehrig/RSD@RSD | | Kopie: suse-autoinstall(a)suse.com | | Thema: Re: [suse-autoinstall] Anas Nashif: Mounting before | | Installation? | >----------------------------------------------------------------------------| * Alexander.Gehrig(a)RSD.rohde-schwarz.com <Alexander.Gehrig(a)RSD.rohde-schwarz.com> [Nov 07. 2002 16:45]: > Hi > > I have many problems by using a allready created partition. You will find many > requests to this object in this list from me. You dont have to put my name in the Subject to catch my attention :-) I have seen your previous posting and will look into this when the time allows, read 'now', one day after your initial posting... I still dont understand what are you trying to do. You have a pre-partitioned disk and you want to use already existing partitions by only formatting them and without actually re-partitioning the disk? If yes, then currently this wont work. With <use> you can specify which partitions you want to use and autoyast will only use the space that was occupied by those partitions. This requires that the partitions in question are at the end of the disk. Anas > > Problems: > I have a harddisk with some partitions. Two of this partitions are typ hex 83/82 > (131/130). I do not know the partitionnumber or size. > > so i had tried different possibilities without any success: > > <partitioning config:type="list"> > <drive> > <device>/dev/sda</device> > <partitions config:type="list"> > <partition> > <mount>/</mount> > <crypt_fs config:type="boolean">false</crypt_fs> > <filesystem config:type="symbol">reiser</filesystem> > <format config:type="boolean">true</format> > <size>auto</size> > </partition> > <partition> > <mount>swap</mount> > <filesystem config:type="symbol">swap</filesystem> > <format config:type="boolean">true</format> > <size>auto</size> > </partition> > </partitions> > </drive> > </partitioning> > > or this... > > <partitioning config:type="list"> > <drive> > <device>/dev/sda</device> > <partitions config:type="list"> > <partition> > <mount>/</mount> > <crypt_fs config:type="boolean">false</crypt_fs> > <filesystem config:type="symbol">reiser</filesystem> > <format config:type="boolean">true</format> > </partition> > <partition> > <mount>swap</mount> > <filesystem config:type="symbol">swap</filesystem> > <format config:type="boolean">true</format> > </partition> > </partitions> > </drive> > </partitioning> > > > Caused no of this solution works i found another: > > <pre-scripts config:type="list"> > <script> > <filename>preinstall</filename> > <interpreter>shell</interpreter> > <source> > <![CDATA[ > #!/bin/bash > echo "modprobe reiserfs" > modprobe reiserfs > echo "Format active partition to reiserfs" > mkreiserfs -f `fdisk -l /dev/sda | grep "*" | cut -b 1-9` > echo "Format swap" > mkswap 'fdisk -l /dev/sda | grep "Linux swap" | cut -b 1-9` > echo "Mount active partition to /mnt/" > mount -t reiserfs `fdisk -l /dev/sda | grep "*" | cut -b 1-9` /mnt > > ]]> > </source> > </script> > </pre-scripts> > </scripts> > .... > without drive TAG > > But this will not work too... what can i do? > Is there any solution? > What i have to do to get the right fstab for the installed system? > > > Please help me! > > Thanks! > > bye > > > Alexander > > > > > > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com -- Anas Nashif <nashif(a)suse.com>, SuSE Linux AG Montreal (Laval), Canada

1 0

RE: [suse-autoinstall] Anas Nashif: Mounting before Installation?
by Neruda, Steve (SCI TW) 07 Nov '02

07 Nov '02

I'm not sure why thos partitions aren't be deleted. I had a problem with LVM partitions because the volume groups get activated and therefore can't be properly reformated since the kernel already has the lvm info. To get around it I wrote this slash and burn pre-script that nukes the volume groups and the erases the partition table using dd. Note: it does not reboot automatically as I wish it did and has no way of returning a message because no useful utilities such as "init", "reboot", or even "halt" are available at this point. I do have a machine language 60 byte reboot code that a friend was able to hack together in x86 assembler that I've though of including but it hasn't been tested. --- use at your own risk --- <pre-scripts config:type="list"> <script> <filename>nukepart.sh</filename> <interpreter>shell</interpreter> <source> <![CDATA[#!/bin/sh #Nuke all existing logical volumes and volume groups # The machine will report not enough room for installation and # require a manual reboot but at least this takes care of the # tedious task of deleting them before installation had2nuke=0 for invg in `vgscan | grep "inactive volume group" | tr "\"" " " | awk '{print $ 7}'`; do vgchange -a y $invg; done for acvg in `vgscan | grep "active volume group" | tr "\"" " " | awk '{print $7} '`; do for lv in `lvscan | grep "ACTIVE" | tr "\"" " " | awk '{print $4}'`; do lvremove -f $lv; done; vgchange -a n $acvg; vgremove $acvg; had2nuke=1 done dd if=/dev/zero of=/dev/sda bs=512 count=10 if [ $had2nuke -eq 1 ] ; then reboot won't work anyway cause no userful binaries to cause a reboot are installed yet...sigh fi ]]> </source> </script> </pre-scripts>

1 0

Anas Nashif: Mounting before Installation?
by Alexander.Gehrig＠RSD.rohde-schwarz.com 07 Nov '02

07 Nov '02

Hi I have many problems by using a allready created partition. You will find many requests to this object in this list from me. Problems: I have a harddisk with some partitions. Two of this partitions are typ hex 83/82 (131/130). I do not know the partitionnumber or size. so i had tried different possibilities without any success: <partitioning config:type="list"> <drive> <device>/dev/sda</device> <partitions config:type="list"> <partition> <mount>/</mount> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <size>auto</size> </partition> <partition> <mount>swap</mount> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <size>auto</size> </partition> </partitions> </drive> </partitioning> or this... <partitioning config:type="list"> <drive> <device>/dev/sda</device> <partitions config:type="list"> <partition> <mount>/</mount> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> </partition> <partition> <mount>swap</mount> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> </partition> </partitions> </drive> </partitioning> Caused no of this solution works i found another: <pre-scripts config:type="list"> <script> <filename>preinstall</filename> <interpreter>shell</interpreter> <source> <![CDATA[ #!/bin/bash echo "modprobe reiserfs" modprobe reiserfs echo "Format active partition to reiserfs" mkreiserfs -f `fdisk -l /dev/sda | grep "*" | cut -b 1-9` echo "Format swap" mkswap 'fdisk -l /dev/sda | grep "Linux swap" | cut -b 1-9` echo "Mount active partition to /mnt/" mount -t reiserfs `fdisk -l /dev/sda | grep "*" | cut -b 1-9` /mnt ]]> </source> </script> </pre-scripts> </scripts> .... without drive TAG But this will not work too... what can i do? Is there any solution? What i have to do to get the right fstab for the installed system? Please help me! Thanks! bye Alexander

2 1

FW: Behavior change with http/ftp vs NFS install
by Neruda, Steve (SCI TW) 06 Nov '02

06 Nov '02

> I have a repository setup and I'm wanting to switch from using NFS to > using HTTP. Things work fine when I do this: > > > linux ip=1.1.1.1 netmask=255.255.255.0 insmod=e100 > autoyast=nfs://1.1.1.2/autoyast.xml install=nfs://1.1.1.2/suse81 > instmod=nfs > > but when I try using http > > > linux ip=1.1.1.1 netmask=255.255.255.0 insmod=e100 > autoyast=nfs://1.1.1.2/autoyast.xml install=nfs://1.1.1.2/suse81 > instmod=nfs > > it works fine but then asks for CD-2 to be inserted. I can't figure out > why it wants a CD and why the difference in install transport changes this > behavior. > > SteveN >

1 0

Autoyast2 do not mount /dev/sda
by Alexander.Gehrig＠RSD.rohde-schwarz.com 06 Nov '02

06 Nov '02

Hi All, at the moment i have many problems with autoyast. I want to use old partitions, but everytime this partition will not be formated and mounted. Any idea? <partitioning config:type="list"> <drive> <use>3,5</use> # it will not work without this line too <device>/dev/sda</device> <partitions config:type="list"> <partition> <mount>/</mount> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <size>auto</size> # it will not work without this line too </partition> <partition> <mount>swap</mount> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <size>auto</size># it will not work without this line too </partition> </partitions> </drive> </partitioning> Thanks! bye Alexander

1 0

RE: [suse-autoinstall] Problems autoinstalling to a Compaq server
by Green, Christopher (HOU - ESG) 05 Nov '02

05 Nov '02

Steve what particular Compaq hardware are you trying to land on ? What Model ? What version of SuSE ? I may be able to help. Chris Green Systems Engineer Proliant Essentials Development Group ISS Management, Networking, and High Availability Tel: (281) 518-8840 Fax: (281) 518-6632 Email: C.Green(a)hp.com --------------------------------------- Hewlett-Packard Company P.O. Box 69200 - MS090203 Houston, TX 77070-2698 -----Original Message----- From: Neruda, Steve (SCI TW) [mailto:Steve_Neruda_TW@stercomm.com] Sent: Tuesday, November 05, 2002 9:47 AM To: 'suse-autoinstall(a)suse.com' Subject: [suse-autoinstall] Problems autoinstalling to a Compaq server I have a couple of problems getting autoinstallation to work with a Compaq system 1) The SmartArray uses logical device naming rather than traditional ie: rather than sd0a it would have /dev/ida/c0d0p1 (controller 0, disk 0, partition 0 Can the autoinstall disk partitioning section be configured to grok this type of disk addressing? 2) I'm not using dhcp because of the enviroment I'm working in so I kick things off with explicit linux rc options: linux ip=10.1.1.1 netmask=255.255.255.0 insmod=e100 autoyast=nfs://10.1.1.2/depot/suse80.xml install=nfs://10.1.1.2/depot/suse80 instmod=nfs In the case of the compaq server I also need to insert two more modules "cpqarray" and "ncr53c8xx". I've tried using multiple insmod= lines insmod=e100 insmod=cpqarray insmod=ncr53c8xx and also using comma seperated modules insmod=e100,cpqarray,ncr538xx but neither method seems to work. I've done fairly extensive searches on google and other places and can't seem to find decent documentation for linuxrc and how to do this. Does anyone have a clue? SteveN -- 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] Problems autoinstalling to a Compaq server
by Neruda, Steve (SCI TW) 05 Nov '02

05 Nov '02

The documentation is excellent but I still don't see an example of passing multiple insmod's or other parameters. Should "insmod=e100,pcqarray,ncr53c8xx" or "insmod=e100 insmod=pcqarray insmod=ncr53c8xx" be used? Neither method seems to work for inserting multiple modules at the kernel boot prompt. SteveN -----Original Message----- From: Anas Nashif [mailto:nashif@suse.de] Sent: Tuesday, November 05, 2002 11:12 AM To: Neruda, Steve (SCI TW) Cc: 'suse-autoinstall(a)suse.com' Subject: Re: [suse-autoinstall] Problems autoinstalling to a Compaq server * Neruda, Steve (SCI TW) <Steve_Neruda_TW(a)stercomm.com> [Nov 05. 2002 16:47]: > > but neither method seems to work. I've done fairly extensive searches on > google and other places and can't seem to find decent documentation for > linuxrc and how to do this. Does anyone have a clue? There is a new version of the docs that is still to be linked, which has all linuxrc options: http://www.suse.de/~nashif/autoinstall/SLES/autoyast2/advanced.html Anas > > SteveN > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com -- Anas Nashif <nashif(a)suse.com>, SuSE Linux AG Montreal (Laval), Canada

1 0