https://bugzilla.novell.com/show_bug.cgi?id=379501 User harbaugh@ncifcrf.gov added comment https://bugzilla.novell.com/show_bug.cgi?id=379501#c2 Toni Harbaugh-Blackford changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |harbaugh@ncifcrf.gov Status|NEEDINFO |NEW Info Provider|harbaugh@ncifcrf.gov | --- Comment #2 from Toni Harbaugh-Blackford 2008-04-14 07:06:21 MST --- This happens during manual install *before* yast installation has started, so there are no y2logs. Is the serial console log enough? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=379501 User harbaugh@ncifcrf.gov added comment https://bugzilla.novell.com/show_bug.cgi?id=379501#c4 Toni Harbaugh-Blackford changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|harbaugh@ncifcrf.gov | --- Comment #4 from Toni Harbaugh-Blackford 2008-04-14 08:03:08 MST --- Yes, it probably is a linuxrc issue. I do the install via serial console with "manual=2" set. Then I get a menu that allows me to load the modules I want, and check that devices are seen properly before the install starts. Here is the main menu: Main Menu 1) Settings 2) System Information 3) Kernel Modules (Hardware Drivers) 4) Start Installation or System 5) Verify Installation CD-ROM/DVD 6) Eject CD 7) Exit or Reboot 8) Power off After I load all the modules, I select item 4. I get the error about 129.43.1.108 being in use, despite the fact that it is my own IP address that is already in DNS. I have to use DHCP in order to do the install. Here is the reset of the log, beginning with where I select menu item 4:

4

Start Installation or System 1) Start Installation or Update 2) Boot Installed System 3) Start Rescue System

1

Choose the source medium. 1) CD-ROM 2) Network 3) Hard Disk

2

Choose the network protocol. 1) FTP 2) HTTP 3) NFS 4) SMB / CIFS (Windows Share) 5) TFTP

3

Enter your temporary SSH password> Choose the network device. 1) eth0 : ethernet network card 2) eth1 : ethernet network card 3) eth2 : ethernet network card 4) eth3 : ethernet network card

1

Automatic configuration via DHCP? 1) Yes 2) No

2

Enter your IP address> 129.43.1.108 Enter your netmask. For a normal class C network, this is usually 255.255.255.0 [255.255.255.0]> If you need a gateway to reach the server, enter the IP address of the gateway. If you do not need a gateway, enter your own IP address [129.43.1.108]> 129.43.1.1 *** IP address 129.43.1.108 is already in use by another machine! *** An error occurred during the network configuration. Your network card probably was not recognized by the kernel. *** No repository found. Choose the network protocol. 1) FTP 2) HTTP 3) NFS 4) SMB / CIFS (Windows Share) 5) TFTP

3

Choose the network device. 1) eth0 : ethernet network card 2) eth1 : ethernet network card 3) eth2 : ethernet network card 4) eth3 : ethernet network card

1

Automatic configuration via DHCP? 1) Yes 2) No

1 Sending DHCP request...

Enter the IP address of the NFS server [129.43.3.91]> Enter the directory on the server [/dist/vol/suse_rsync/Factory/inst-source]> Loading Installation System (1/4) (16928 kB) - 100% Loading Installation System (2/4) (42716 kB) - 100% Loading Installation System (3/4) (3631 kB) - 100% Loading Installation System (4/4) (62 kB) - 100% Sorry, repository failed checksum test. If you really trust your repository, you may continue in an insecure mode. 1) OK 2) Back

1 Reading Driver Update...

No new Driver Updates found starting hald... ok starting syslogd (logging to /dev/tty4)... ok starting klogd... ok sshd found, prepare remote login generating SSH keys ... Generating /etc/ssh/ssh_host_key. Generating public/private rsa1 key pair. . . . -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=379501 User snwint@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=379501#c5 Steffen Winterfeldt changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |snwint@novell.com AssignedTo|snwint@novell.com |mantel@novell.com --- Comment #5 from Steffen Winterfeldt 2008-04-14 08:19:44 MST --- The above message means that the ip address responded to a 'ping'. You can use 'forceip=1' to skip the check. If you are sure there is no other machine using that address, please boot with 'linuxrc.log=/dev/console linemode=1' and attach the session log. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=379501 User mantel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=379501#c7 Hubert Mantel changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WONTFIX | --- Comment #7 from Hubert Mantel 2008-04-16 06:47:22 MST --- Sorry for jumping in so late; I have been busy with another project in the last days. While I understand that the forceip parameter is an acceptable workaround for you, I still would like to understand the issue. So I'm re-opening the bug in order it does not get lost. As Steffen already said, we only check if there is another machine that responds to the arping. I suspect the reason for the failure is the fact that your machine has more than one network card. So far we only tested with a single NIC. Since machines with multiple NICs are very common nowadays, the chances are high other people will run into the same problem. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=379501 User mantel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=379501#c9 --- Comment #9 from Hubert Mantel 2008-04-16 07:45:45 MST --- Thanks a lot. This is highly appreciated. Your use case is not exotic and really should work without the need to manually enter parameters. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=379501 User suse-beta@cboltz.de added comment https://bugzilla.novell.com/show_bug.cgi?id=379501#c10 Christian Boltz changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mantel@novell.com, suse-beta@cboltz.de AssignedTo|mantel@novell.com |snwint@novell.com Severity|Normal |Critical Status|ASSIGNED |NEW Version|Alpha 3 |Beta 1 --- Comment #10 from Christian Boltz 2008-04-20 12:09:52 MST --- I probably hit the same problem in beta1 *and* know the reason ;-) This has nothing to do with DNS entries etc., the reason is much simpler. From linuxrc log: interface setup: eth1 net_activate: ifconfig eth1 up net_activate: arping -c 1 -I eth1 -D 10.12.80.30 1>&2 sh: arping: command not found <----------------------------------------- net_activate: ifconfig eth1 down So the reason is that linuxrc calls arping which doesn't exist in the initial stage of installation. I didn't know about the forceip parameter and used this workaround: cp /bin/mv /bin/arping echo true > /bin/arping This might look ugly, but chmod isn't available at this time. Copying an existing executable file is a(nother) workaround that helps. Reassigning to Steffen because this is an issue in linuxrc, not in the kernel. BTW: The "forceip" parameter is not documented on en.opensuse.org/Linuxrc -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.