[opensuse-autoinstall] How can I fix network configuaration settins of multiple NIC cards using AutoYast on OpenSUSE 11.0

newer
[opensuse-autoinstall] openSUSE...

Alan Keng

25 Jul 2008 25 Jul '08

19:22

Hi, I configured 2 NICs on my system with 2 static IP in 2 different subnets. Then I used Autoinstallation to save the XML control file. <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <device>eth0</device> <ipaddr>172.24.255.11</ipaddr> <name>CK804 Ethernet Controller</name> <netmask>255.255.0.0</netmask> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> <interface> <bootproto>static</bootproto> <device>eth1</device> <ipaddr>172.19.1.1</ipaddr> <name>82541PI Gigabit Ethernet Controller</name> <netmask>255.255.0.0</netmask> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> </interfaces> After many installations with AutoYast, most of the time the system would detect CK804 NIC (MAC address) as eth0 and 82541PI (MAC address) as eth1. However, it is not true all the time. So there would be the case that the eth0 with name of CK804 is set to the MAC address of 82541PI NIC and eth1 with name of 82541PI is set to the MAC address of CK804. (CK804 is an integrated NIC and 82541PI is a PCI NIC card). Is there a way to make sure the network settings would be the same after every installation using AutoYast?? (I would like to have one NIC with specific IP setting and the other one has another specific IP setting all the time)? If I use the XML control file to autoinstall on another system with different 2 NICs (not CK804 and 8254 PI anymore), what will happen? By the way, the Linuxrc would always see the CK804 NIC as eth1 and 82541PI as eth0 (at least so far). Is it possible you could kindly point me to some directions so that I could solve those problems. I am not sure how the NICs are detected as eth0, eth1, etc. Why the Linuxrc always detects CK804 as eth1 but most of the time the AutoYast would detect CK804 as eth0? Thank you so much for your time and I look forward to hearing from you. Sincerely, Alan -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org

Show replies by thread

Alan Keng

20 Aug 20 Aug

01:43

New subject: [opensuse-autoinstall] Problem with updating installation source with new RPMs on OpenSUSE 11.0

Hi, I am trying to add some RPMs from the oss repositoiy to the AutoYast installation. I used the following instructions: Suppose the source resides in myInstallSource ./create_update_source.sh myInstallSource cp -a myPackage-x86_64.rpm myInstallSource/updates/suse/x86_64 cd myInstallSource/updates/suse create_package_descr -x setup/descr/EXTRA_PROV cd setup/descr ls > directory.yast cd ../../.. create_sha1sums -x -n ./ And added following lines to the control XML file: <add-on> <listentry> nfs://"Server IP"/myInstallSource/updates <product>SuSE-Linux-Updates</product> true / </listentry> </add-on> I also added the following lines between the <general><signature-handling> … </signature-handling></general> tags: <signature-handling> true true true true true </signature-handling> I believe I got the NFS server all setup correctly because the control file is also located on the NFS server. During the installation, I got the "Add-on is not available via NFS" error: "Please make the add-on "SuSE-Linux-Updates" available via "nfs://"Server IP"/myInstallSource/updates" Any one can help? What went wrong? Thanks, Alan -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org

Georg Wallner

05:54

New subject: [opensuse-autoinstall] Problem with updating installation source with new RPMs on OpenSUSE 11.0

Hello, Am Mittwoch, 20. August 2008 03:43:31 schrieb Alan Keng:

...

Hi,

I am trying to add some RPMs from the oss repositoiy to the AutoYast installation.

I used the following instructions:

Suppose the source resides in myInstallSource ./create_update_source.sh myInstallSource cp -a myPackage-x86_64.rpm myInstallSource/updates/suse/x86_64 cd myInstallSource/updates/suse create_package_descr -x setup/descr/EXTRA_PROV cd setup/descr ls > directory.yast cd ../../.. create_sha1sums -x -n ./

Try also create_sha1sums -x -n . If it dosn't help, I followed this instruction for my Own Packages: mkdir -p /installation/repository/OpenSuSE110/ownpackages cd /installation/repository/OpenSuSE110/ownpackages mkdir media.1 vi media.1/media (Copy from OpenSuSE repository, changed to my needs) vi content (Copy from OpenSuSE repository, changed to my needs) mkdir suse cd suse mkdir i386 i486 i586 i686 noarch x86_64 tar ls -A1 > directory.yast Copy the relevant packages to it's folders create_package_descr -l german -l english -d suse/ create_sha1sums -x -n ./ (content file unter setup/descr create_sha1sums -x -n . (für das content file im rootdirectory) The nfs share is /installation

...

And added following lines to the control XML file:

<add-on> <listentry> nfs://"Server IP"/myInstallSource/updates

nfs://"ServerIP"/installation/repository/OpenSuSE110/ownpackages/ <product>Own Packages</product> / false

...

true / </listentry> </add-on>

looks OK

...

I also added the following lines between the <general><signature-handling> … </signature-handling></general> tags:

<signature-handling> true true true true true </signature-handling>

looks OK

...

I believe I got the NFS server all setup correctly because the control file is also located on the NFS server.

During the installation, I got the "Add-on is not available via NFS" error:

"Please make the add-on "SuSE-Linux-Updates" available via "nfs://"Server IP"/myInstallSource/updates"

Any one can help? What went wrong?

Thanks, Alan

Georg -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org

Alan Keng

26 Aug 26 Aug

19:41

New subject: [opensuse-autoinstall] How to install bootloader on both disks with software RAID 1 (openSUSE 11.0)

Hi, When I used AutoYast with Software RAID 1 partition, I installed the GRUB bootloader on MBR. Apparently, the bootloader was only installed on one of the physical hard disk. How can I set it up to install the bootloader on both of the disks, so whenever one of the disk's gone bad and doesn't matter which on it is, I am still able to boot the system? This is extracted from my control XML file if it helps: <bootloader> <firmware>fd0</firmware> <linux>/dev/fd0</linux> <firmware>hd0</firmware> <linux>/dev/sda</linux> <firmware>hd1</firmware> <linux>/dev/sdb</linux> <global> <activate>true</activate> true <default>openSUSE 11.0 - 2.6.25.5-1.1</default> <gfxmenu>/boot/message</gfxmenu> 3 <timeout config:type="integer">8</timeout> </global> <module>processor</module> <module>thermal</module> <module>sata_nv</module> <module>pata_amd</module> <module>fan</module> <module>reiserfs</module> <module>raid1</module> <module>edd</module> grub <sections config:type="list"> <section> <append>resume=/dev/md1 splash=silent showopts</append> <image>/boot/vmlinuz-2.6.25.5-1.1-default</image> <initial>1</initial> <initrd>/boot/initrd-2.6.25.5-1.1-default</initrd> 0 <name>openSUSE 11.0 - 2.6.25.5-1.1</name> linux <root>/dev/md2</root> <type>image</type> <vga>0x317</vga> <vgamode>0x317</vgamode> </section> <section> <append>showopts ide=nodma apm=off acpi=off noresume edd=off x11failsafe</append> <image>/boot/vmlinuz-2.6.25.5-1.1-default</image> <initrd>/boot/initrd-2.6.25.5-1.1-default</initrd> 1 <name>Failsafe -- openSUSE 11.0 - 2.6.25.5-1.1</name> failsafe <root>/dev/md2</root> <type>image</type> <vga>0x317</vga> <vgamode>0x317</vgamode> </section> <section> <blockoffset>1</blockoffset> <chainloader>/dev/fd0</chainloader> 2 <name>Floppy</name> <noverifyroot>true</noverifyroot> floppy <type>other</type> </section> </sections> </bootloader> <partitioning config:type="list"> <drive> <device>/dev/md</device> <partitions config:type="list"> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/boot</mount> <mountby config:type="symbol">device</mountby> 0 false raid1 </partition> <partition> <create config:type="boolean">true</create> <mount>swap</mount> <mountby config:type="symbol">device</mountby> 1 false raid_unknown </partition> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <mountby config:type="symbol">device</mountby> 2 false raid1 </partition> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/home</mount> <mountby config:type="symbol">device</mountby> 3 false raid1 </partition> </partitions> <type config:type="symbol">CT_MD</type> <use>all</use> </drive> <drive> <device>/dev/sda</device> <partitions config:type="list"> <partition> <create config:type="boolean">true</create> 253 253 1 primary /dev/md0 <size>2gb</size> </partition> <partition> <create config:type="boolean">true</create> 253 253 2 primary <size>8gb</size> </partition> <partition> <create config:type="boolean">true</create> 253 253 3 primary /dev/md2 <size>20gb</size> </partition> <partition> <create config:type="boolean">true</create> 253 253 4 primary /dev/md3 <size>max</size> </partition> </partitions> <type config:type="symbol">CT_DISK</type> <use>all</use> </drive> <drive> <device>/dev/sdb</device> <partitions config:type="list"> <partition> <create config:type="boolean">true</create> 253 253 1 primary /dev/md0 <size>2gb</size> </partition> <partition> <create config:type="boolean">true</create> 253 253 2 primary /dev/md1 <size>8gb</size> </partition> <partition> <create config:type="boolean">true</create> 253 253 3 primary /dev/md2 <size>20gb</size> </partition> <partition> <create config:type="boolean">true</create> 253 253 4 primary /dev/md3 <size>max</size> </partition> </partitions> <type config:type="symbol">CT_DISK</type> <use>all</use> </drive> </partitioning> Thanks, Alan -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org

Mike Diehn

27 Aug 27 Aug

20:37

New subject: [opensuse-autoinstall] How to install bootloader on both disks with software RAID 1 (openSUSE 11.0)

Alan, Did you use the "yast2 autoyast" tool to create the control xml? If you can, it'll be pretty easy to see how to do what you want. You can start the tool and then File->Open your existing control.xml and then modify, I think. Root around in the Bootloader section. if ! "$luck" == "good" then write back && I can probably hack together the xml for you fi Best, Mike Mike Diehn Sr. SysAdmin mike.diehn@ansys.com +1-603-727-5492

...

-----Original Message----- From: Alan Keng [mailto:akeng@aehr.com] Sent: Tuesday, August 26, 2008 3:42 PM To: opensuse-autoinstall@opensuse.org Subject: [opensuse-autoinstall] How to install bootloader on both disks with software RAID 1 (openSUSE 11.0)

Hi,

When I used AutoYast with Software RAID 1 partition, I installed the GRUB bootloader on MBR.

Apparently, the bootloader was only installed on one of the physical hard disk. How can I set it up to install the bootloader on both of the disks, so whenever one of the disk's gone bad and doesn't matter which on it is, I am still able to boot the system?

This is extracted from my control XML file if it helps:

<bootloader> <firmware>fd0</firmware> <linux>/dev/fd0</linux> <firmware>hd0</firmware> <linux>/dev/sda</linux> <firmware>hd1</firmware> <linux>/dev/sdb</linux> <global> <activate>true</activate> true <default>openSUSE 11.0 - 2.6.25.5-1.1</default> <gfxmenu>/boot/message</gfxmenu> 3 <timeout config:type="integer">8</timeout> </global> <module>processor</module> <module>thermal</module> <module>sata_nv</module> <module>pata_amd</module> <module>fan</module> <module>reiserfs</module> <module>raid1</module> <module>edd</module> grub <sections config:type="list"> <section> <append>resume=/dev/md1 splash=silent showopts</append> <image>/boot/vmlinuz-2.6.25.5-1.1-default</image> <initial>1</initial> <initrd>/boot/initrd-2.6.25.5-1.1-default</initrd> 0 <name>openSUSE 11.0 - 2.6.25.5-1.1</name> linux <root>/dev/md2</root> <type>image</type> <vga>0x317</vga> <vgamode>0x317</vgamode> </section> <section> <append>showopts ide=nodma apm=off acpi=off noresume edd=off x11failsafe</append> <image>/boot/vmlinuz-2.6.25.5-1.1-default</image> <initrd>/boot/initrd-2.6.25.5-1.1-default</initrd> 1 <name>Failsafe -- openSUSE 11.0 - 2.6.25.5-1.1</name> failsafe <root>/dev/md2</root> <type>image</type> <vga>0x317</vga> <vgamode>0x317</vgamode> </section> <section> <blockoffset>1</blockoffset> <chainloader>/dev/fd0</chainloader> 2 <name>Floppy</name> <noverifyroot>true</noverifyroot> floppy <type>other</type> </section> </sections> </bootloader>

<partitioning config:type="list"> <drive> <device>/dev/md</device> <partitions config:type="list"> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/boot</mount> <mountby config:type="symbol">device</mountby> 0 false raid1 </partition> <partition> <create config:type="boolean">true</create> <mount>swap</mount> <mountby config:type="symbol">device</mountby> 1 false raid_unknown </partition> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <mountby config:type="symbol">device</mountby> 2 false raid1 </partition> <partition> <create config:type="boolean">true</create> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/home</mount> <mountby config:type="symbol">device</mountby> 3 false raid1 </partition> </partitions> <type config:type="symbol">CT_MD</type> <use>all</use> </drive> <drive> <device>/dev/sda</device> <partitions config:type="list"> <partition> <create config:type="boolean">true</create> 253 253 1 primary /dev/md0 <size>2gb</size> </partition> <partition> <create config:type="boolean">true</create> 253 253 2 primary <size>8gb</size> </partition> <partition> <create config:type="boolean">true</create> 253 253 3 primary /dev/md2 <size>20gb</size> </partition> <partition> <create config:type="boolean">true</create> 253 253 4 primary /dev/md3 <size>max</size> </partition> </partitions> <type config:type="symbol">CT_DISK</type> <use>all</use> </drive> <drive> <device>/dev/sdb</device> <partitions config:type="list"> <partition> <create config:type="boolean">true</create> 253 253 1 primary /dev/md0 <size>2gb</size> </partition> <partition> <create config:type="boolean">true</create> 253 253 2 primary /dev/md1 <size>8gb</size> </partition> <partition> <create config:type="boolean">true</create> 253 253 3 primary /dev/md2 <size>20gb</size> </partition> <partition> <create config:type="boolean">true</create> 253 253 4 primary /dev/md3 <size>max</size> </partition> </partitions> <type config:type="symbol">CT_DISK</type> <use>all</use> </drive> </partitioning>

Thanks, Alan

-- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org

Alan Keng

10 Sep 10 Sep

18:38

New subject: [opensuse-autoinstall] How to enable automatic login w/ AutoYast (openSUSE 11.0)

Hi, I was wondering if there way to enable the user auto login using AutoYast? Any XML element can be used for that? Thanks, Alan -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org

Uwe Gansert

11 Sep 11 Sep

10:01

New subject: [opensuse-autoinstall] How to enable automatic login w/ AutoYast (openSUSE 11.0)

On Wednesday 10 September 2008, Alan Keng wrote:

...

I was wondering if there way to enable the user auto login using AutoYast?

Any XML element can be used for that?

untested! <sysconfig config:type="list" > DISPLAYMANAGER_AUTOLOGIN /etc/sysconfig/displaymanager uwe </sysconfig> -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/~ug listening to: "Post Blue" by Placebo -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org

Alan Keng

14 Oct 14 Oct

00:20

New subject: [opensuse-autoinstall] How to set the User Class Option for DHCP w/ AutoYast (openSUSE 11.0)

Hi, I was wondering if there way to set the DHCP client User Class Option (Option 77) for a network interface using AutoYast or even from the linuxrc boot options? The purpose of doing this is that we would like to have different pools of IP addresses for each user classes so we could assign the dynamic IP to systems based on their user classes. Thanks, Alan -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org

Alan Keng

23 Oct 23 Oct

23:30

New subject: [opensuse-autoinstall] Autoyast installation with BISO Raid 1 (fake raid)

Hi, I was trying to use AutoYast to install number of systems with BIOS Raid1. The raid is created by Intel Matrix Storage Manager that comes w/ the system. In my case, when a BIOS Raid1,named Volume0, is created, the name of the device would be like, isw_xxxxx_Volume0. In the autoinst.xml, "/dev/mapper/isw_xxxxx_Volume0", are the values of many parts of the profile. e.g. <bootloader> <linux>/dev/mapper/isw_bbcihdbdh_Volume0</linux> <sections config:type="list"> <section> <append>resume=/dev/mapper/isw_bbcihdbdh_Volume0_part6 splash=silent showopts</append> <root>/dev/mapper/isw_bbcihdbdh_Volume0_part7</root> <partitioning config:type="list"> <drive> <device>/dev/mapper/isw_bbcihdbdh_Volume0</device> The name of BIOS Raid1 would be different each time it gets created and it will cause problems when using the profile to do the installations with different names. Is there a way to get around with it? Like having it to have the same name always? Or can the installation be more dynamically to set the values? Just like the "Ask". However, instead of asking the user to enter values, can we use pre-defined linux commands or scripts in the profile to set the values based on the system settings? Thank you for your time. Regards, Alan -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org

Uwe Gansert

28 Oct 28 Oct

10:15

New subject: [opensuse-autoinstall] Autoyast installation with BISO Raid 1 (fake raid)

Am Freitag 24 Oktober 2008 01:30:09 schrieb Alan Keng:

...

In my case, when a BIOS Raid1,named Volume0, is created, the name of the device would be like, isw_xxxxx_Volume0.

Which SUSE Linux version? Since openSUSE 11.0 autoyast should autodetect raid device names if the <device> tags are missing in the profile. If that does not work, you can use a pre-script to detect the device name on your own and modify your profile before the installation starts: http://www.suse.de/~ug/autoyast_doc/createprofile.scripts.html#pre- install.scripts -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/~ug -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org

Stephens, Bill {PBSG}

14:11

New subject: [opensuse-autoinstall] Autoyast installation with BISO Raid 1 (fake raid)

Can you run a pre-install script to determine which device should be used for the partioning plan (SLES 10)? We have some servers where fiber attached drives are being identified first (SDA) as opposed to locally attached drives. We have other servers where we would like to SAN boot, but the first drive detected is sometimes a 5 mb lun. -----Original Message----- From: Uwe Gansert [mailto:ug@suse.de] Sent: Tuesday, October 28, 2008 5:16 AM To: opensuse-autoinstall@opensuse.org Subject: Re: [opensuse-autoinstall] Autoyast installation with BISO Raid 1 (fake raid) Am Freitag 24 Oktober 2008 01:30:09 schrieb Alan Keng:

...

In my case, when a BIOS Raid1,named Volume0, is created, the name of the device would be like, isw_xxxxx_Volume0.

Uwe Gansert

15:10

New subject: [opensuse-autoinstall] Autoyast installation with BISO Raid 1 (fake raid)

Am Dienstag 28 Oktober 2008 15:11:42 schrieb Stephens, Bill {PBSG}:

...

Can you run a pre-install script to determine which device should be used for the partioning plan (SLES 10)? We have some servers where fiber attached drives are being identified first (SDA) as opposed to locally attached drives. We have other servers where we would like to SAN boot, but the first drive detected is sometimes a 5 mb lun.

yes, you can change the partitioning section via pre-script on SLES10 -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/~ug listening to: "Phoenix" by Unheilig -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org

Stephens, Bill {PBSG}

20:14

New subject: [opensuse-autoinstall] Autoyast installation with BISO Raid 1 (fake raid)

Does anyone have any examples of how to present a list of disks and their sizes to the user at install time to let them choose which disk to install to? -----Original Message----- From: Uwe Gansert [mailto:ug@suse.de] Sent: Tuesday, October 28, 2008 10:11 AM To: opensuse-autoinstall@opensuse.org Subject: Re: [opensuse-autoinstall] Autoyast installation with BISO Raid 1 (fake raid) Am Dienstag 28 Oktober 2008 15:11:42 schrieb Stephens, Bill {PBSG}:

...

Can you run a pre-install script to determine which device should be used for the partioning plan (SLES 10)? We have some servers where fiber attached drives are being identified first (SDA) as opposed to locally attached drives. We have other servers where we would like to SAN boot, but the first drive detected is sometimes a 5 mb lun.

Alan Keng

23:43

New subject: [opensuse-autoinstall] Autoyast installation with BISO Raid 1 (fake raid)

Hi, I use version 11.0. This is what I did for the pre-script in Perl to solve the problem although I am not sure if it is efficient enough. my $infile = "/tmp/profile/autoinst.xml"; my $outfile = "/tmp/profile/modified.xml"; my $line = `dmraid -s -c`; chomp $line; open IN, $infile; open OUT, ">$outfile"; while (<IN>) { if (/(.*)isw(.*)Volume0(.*)/) { print OUT "$1$line$3\n"; } else {print OUT $_;} } close IN; close OUT; ------------------------------------- Any comments? Thanks, Alan On Tuesday 28 October 2008 08:10:56 am Uwe Gansert wrote:

...

Am Dienstag 28 Oktober 2008 15:11:42 schrieb Stephens, Bill {PBSG}:

...
Can you run a pre-install script to determine which device should be used for the partioning plan (SLES 10)? We have some servers where fiber attached drives are being identified first (SDA) as opposed to locally attached drives. We have other servers where we would like to SAN boot, but the first drive detected is sometimes a 5 mb lun.

yes, you can change the partitioning section via pre-script on SLES10

-- ciao, Uwe Gansert

Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/~ug listening to: "Phoenix" by Unheilig

-- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org

Alan Keng

29 Oct 29 Oct

22:34

New subject: [opensuse-autoinstall] Autoyast installation with Network Card Interfaces Detection (openSuse 11.0)

Hi, I have 2 NICs on the system and one is used to connect to the NFS server for AutoYast installation. When AutoYast has completed the system configuration and booting the system for the first time, quite oftenly, one of the NICs cannot be detected by the system and causing the LAN setting cannot be set correctly based on the profile later on. It would be even worse If the un-found interface is the one used for connecting to the server. Is this the problem of AutoYast or openSuse itself? Why all the NICs can't be picked up all the time? Thanks -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org

5675

Age (days ago)

5771

Last active (days ago)

List overview

Download

14 comments

5 participants

participants (5)

Alan Keng
Georg Wallner
Mike Diehn
Stephens, Bill {PBSG}
Uwe Gansert