Bug 12987

Summary: 3com 3c90x driver version incorrect
Product: [Retired] Red Hat Linux Reporter: Becky Miller <becky_miller>
Component: kernelAssignee: Michael K. Johnson <johnsonm>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: high    
Version: 7.0CC: johnsonm, mark_rusk, matt_domsch
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard: Winston rc1
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2000-08-17 15:34:46 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 Becky Miller 2000-06-24 13:35:09 UTC
The 3c90x driver in beta 2 is 1.0.0d, it should be 1.0.0i.
This is the latest drvier availible from 3com and needs to be included in 
the kernel.

Comment 1 Matt Domsch 2000-06-26 18:11:09 UTC
Driver 1.0.0i may be found at:
http://support.3com.com/infodeli/tools/nic/linuxdownload.htm

Comment 2 Matt Domsch 2000-07-21 19:09:10 UTC
Winston beta 4 still contains the 3c90x v1.0.0d driver.


Comment 3 Matt Domsch 2000-07-27 15:48:27 UTC
Pinstripe (aka Winston beta 5) still contains v1.0.0d of this driver.

Comment 4 Alan Cox 2000-08-01 14:44:34 UTC
Glen this one is critical. 1.0.0d hangs machines solidly especially SMP. 1.0.0i
does actually work


Comment 5 Michael K. Johnson 2000-08-01 16:19:26 UTC
OK, I've sucked 1.0.0i into our current srpm.

Comment 6 Glen Foster 2000-08-01 18:09:46 UTC
This defect is considered MUST-FIX for Winston Release-Candidate #1

Comment 7 Michael K. Johnson 2000-08-03 18:45:14 UTC
It is built into our current tree, 2.2.16-18 and higher
should include this version or later...

Comment 8 Matt Domsch 2000-08-11 16:19:29 UTC
Nope, kernel 2.2.16-21 has 3c90x v1.0.0d still...  RC1 has this kernel.  How 
can this be?


Comment 9 Michael K. Johnson 2000-08-16 16:34:26 UTC
Go download it yourself and look in patch-2.2.5 -- it calls itself
1.0.0d...  I can't help that.  Am I missing something?

Comment 10 Michael K. Johnson 2000-08-16 16:39:02 UTC
Never mind, 3com appears to have forgotten to regenerate the 2.2
patch; I recreated it from the source code.  It didn't occur to
me that they would ship two different versions of the driver in
one package.  Sigh...

Fixing now...

Comment 11 Michael K. Johnson 2000-08-16 21:11:03 UTC
The new driver breaks on the Alpha.  Grrrrrrrrr.

Comment 12 Michael K. Johnson 2000-08-16 21:54:58 UTC
That is, *compilation* breaks on alpha -- it's not clear that
the driver has actually ever *worked* on alpha.  :-(  I have
disabled it on alpha now.

Comment 13 Michael K. Johnson 2000-08-17 14:59:25 UTC
Not only that, it doesn't compile on i386 either.
Back to 1.0.0d.  We will not update again for Winston.

Comment 14 Michael K. Johnson 2000-08-17 15:00:46 UTC
When 3com have a working driver, we'll look at an update.

Comment 15 Michael K. Johnson 2000-08-17 15:34:41 UTC
Florian may have found the problem...

Comment 16 Michael K. Johnson 2000-08-17 19:07:05 UTC
Florian did indeed find the problem, and 1.0.0i will be
in 2.2.16-21.2 and later, unless we find horrible bugs
in 1.0.0i...