Bug 197623

Summary:	VIA-Rhine Ethernet not seen with kernel 2.6.17-1.2139_FC4
Product:	[Fedora] Fedora	Reporter:	mcisar
Component:	kernel	Assignee:	John W. Linville <linville>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:	Brian Brock <bbrock>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5	CC:	davej, wtogami
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:	NeedsRetesting
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-11-03 19:00:34 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description mcisar 2006-07-04 21:39:55 UTC

Description of problem:
After upgrading from kernel 2.6.16-1.2115_FC4 to 2.6.17-1.2139_FC4 system 
boots but reports "via-rhine device eth1 does not seem to be present"

Version-Release number of selected component (if applicable):


How reproducible:
always

Steps to Reproduce:
1. boot
2.
3.
  
Actual results:
"via-rhine device eth1 does not seem to be present delaying initialization"

Expected results:
network adaptor works

Additional info:

Comment 1 mcisar 2006-07-04 21:48:54 UTC

*** Bug 197622 has been marked as a duplicate of this bug. ***

Comment 2 Taras Pryjma 2006-07-09 04:16:55 UTC

This problem still persiss in build 2144.  The chip works fine in all previous
kernel releases to 2.6.17

Comment 3 John W. Linville 2006-07-25 16:41:59 UTC

Have you tried the FC5 netdev kernels?

   http://people.redhat.com/linville/kernels/fedora-netdev/

Please give those a try and indicate if the problem is still there...thanks!

Comment 4 Dave Jones 2006-09-17 01:01:56 UTC

[This comment added as part of a mass-update to all open FC4 kernel bugs]

FC4 has now transitioned to the Fedora legacy project, which will continue to
release security related updates for the kernel.  As this bug is not security
related, it is unlikely to be fixed in an update for FC4, and has been migrated
to FC5.

Please retest with Fedora Core 5.

Thank you.

Comment 5 Dave Jones 2006-10-16 20:03:54 UTC

A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
based upon a new upstream kernel release.

Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.

This bug has been placed in NEEDINFO state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.

Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.

In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed.  See bug 207474 for further details.

If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.

If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.

Thank you.

Comment 6 John W. Linville 2006-11-03 19:00:34 UTC

Closed due to lack of response.  Please reopen when the requested information 
becomes available...thanks!