Bug 522164 - [anaconda] fails to pick up correct wired connection at 2nd attempt
Summary: [anaconda] fails to pick up correct wired connection at 2nd attempt
Keywords:
Status: CLOSED DUPLICATE of bug 522138
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: David Cantrell
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 522138
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-09-09 16:04 UTC by Joachim Frieben
Modified: 2009-10-07 01:43 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-10-07 01:43:05 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
syslog file from F11 install (69.86 KB, text/plain)
2009-09-09 16:04 UTC, Joachim Frieben
no flags Details
dmesg output after F11 install (38.29 KB, text/plain)
2009-09-09 16:05 UTC, Joachim Frieben
no flags Details
Log of anaconda crash when not formatting any partition (257.54 KB, text/plain)
2009-09-10 07:46 UTC, Joachim Frieben
no flags Details
syslog file from rawhide install after successively chosing eth0 and eth1 (69.86 KB, text/plain)
2009-09-15 20:01 UTC, Joachim Frieben
no flags Details
syslog file from rawhide install after chosing eth1 (54.81 KB, text/plain)
2009-09-15 20:05 UTC, Joachim Frieben
no flags Details

Description Joachim Frieben 2009-09-09 16:04:28 UTC
Created attachment 360262 [details]
syslog file from F11 install

Description of problem:
When adding F11 updates to the DVD source during install, a dialog prompts for the network interface to be used. The system is connected to a router through eth1 which is an NVidia CK804 onboard Ethernet controller using the "forcedeth" driver. However, anaconda reports after a while that no network connection can be established.

Version-Release number of selected component (if applicable):
anaconda-11.5.0.59-1.fc11.x86_64

How reproducible:
Always.

Steps to Reproduce:
1. Add network channel during F11 DVD install.
2. Choose eth1 which is connected to the network.
  
Actual results:
No network connection can be established.

Expected results:
A working network connection is established

Additional info:
* After attaching the network cable to eth0 [Broadcom BCM5721, driver "tg3"], network connectivity is established instantaneously.
* After install, both interfaces eth0 and eth1 do provide network connectivity when connected to the network.
* Issue persists for F12/rawhide as checked about 1 month ago.
* http://www.smolts.org/client/show/pub_ce3d646e-2918-44c9-a6c0-10fb3d9a0180

Comment 1 Joachim Frieben 2009-09-09 16:05:58 UTC
Created attachment 360263 [details]
dmesg output after F11 install

Comment 2 Chris Lumens 2009-09-09 16:44:58 UTC
Can you check on tty3, tty4, and tty5 while it's trying to configure the forcedeth card to see if there are any helpful error messages?

Comment 3 Joachim Frieben 2009-09-10 07:46:07 UTC
Created attachment 360450 [details]
Log of anaconda crash when not formatting any partition

I tried to proceed to the stage where online repositories can be added. In order to do so non-destructively, I chose not to format any partition/volume, just setting mount points instead. However, after completing the filesystem setup, anaconda crashes returning the attached log file.
There is no 'update' option in anaconda as there used to be in the past. How then proceed any further?

Comment 4 Chris Lumens 2009-09-10 14:05:57 UTC
That's a completely different bug that we already have tracked by other bug reports.  Are you able to see any error messages on the TTYs I asked for when trying to configure that network card?

Comment 5 Joachim Frieben 2009-09-10 18:23:24 UTC
I had attached the anaconda dump file because this bug prevents me from getting beyond the storage configuration stage to the channel setup stage without formatting my file systems once again.
For the time being, I thus cannot reproduce the same scenario of activating a network connection when selecting the F11-updates channel.
Anyway, I have booted from the DVD adding option 'askmethod', and in this case, wired network is brought up correctly for the Nvidia CK804 Ethernet connection configured as eth1.
I will report on the original issue as soon as possible.

Comment 6 Joachim Frieben 2009-09-15 20:01:35 UTC
Created attachment 361129 [details]
syslog file from rawhide install after successively chosing eth0 and eth1

Fresh "rawhide" install with wired network devices eth0 (Nvidia CK804) and eth1 (Broadcom BCM5721). Only eth1 is actually connected to a network.
When proceeding to the stage where online repositories can be added/modified, a dialog window pops up prompting for the network device to be used. The default one is eth0 (probably by alphabetical order):

- eth0 is chosen for the 1st attempt: failure
  * eth1 is chosen for the 2nd attempt after eth0 has failed: failure (!)
- eth1 is chosen for the 1st attempt: success (!)

Attached log is for case one (both attempts fail).

Comment 7 Joachim Frieben 2009-09-15 20:05:15 UTC
Created attachment 361130 [details]
syslog file from rawhide install after chosing eth1

Comment 8 Joachim Frieben 2009-09-18 09:03:53 UTC
Swapping eth0 and eth1, the outcome remains the same:
- network connectivity is established if the correct wired interface is
  chosen immediately.
- network connectivity fails even for the correct wired interface when a
  failed attempt was made for the wrong not connected wired interface at
  first.
Thus, the issue is not a forcedeth one.

Comment 9 Matt Domsch 2009-09-19 17:20:13 UTC
Spanning Tree is enabled on the switch/router perhaps?

Comment 10 John Reiser 2009-09-19 17:43:49 UTC
Some aspects of bug 519188 (No chance for second interface ...) appear to be related to this bug.

Some aspects of bug 507084 (netinst.iso fails on second interface) appear to be related to this bug.

Comment 11 Joachim Frieben 2009-09-19 18:14:10 UTC
(In reply to comment #9)
According to the Speedport W 501V documentation, one should use a "network cable 10bT, 1.1 wired, STP" which is certainly fulfilled by the original one delivered with said (W)LAN modem/router. There is no further indication in the documentation.

Comment 12 Joachim Frieben 2009-09-19 18:21:05 UTC
(In reply to comment #9)
(W)LAN modem/router Speedport W 501V has a single Ethernet port only which is connected to one of the two Ethernet ports of this Tyan K8E (S2865) based system.

Comment 13 David Cantrell 2009-10-01 03:09:00 UTC
I think this bug may be related to bug #522138.  I have a patch for it and it's been tested on a system using a Broadcom NIC that was experiencing problems.  The patch works there, so this should make it in to the next build of anaconda.  I'll note here when the patch is in so you can try things again.

Comment 14 David Cantrell 2009-10-07 01:43:05 UTC

*** This bug has been marked as a duplicate of bug 522138 ***


Note You need to log in before you can comment on or make changes to this bug.