Bug 28197 - 6.2 everything upgrade-->7.1RC1-tulip driver mix-up
6.2 everything upgrade-->7.1RC1-tulip driver mix-up
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: kudzu (Show other bugs)
7.3
alpha Linux
medium Severity medium
: ---
: ---
Assigned To: Michael Fulbright
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-02-17 18:01 EST by Ben Levenson
Modified: 2007-04-18 12:31 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-03-12 10:46:34 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Ben Levenson 2001-02-17 18:01:39 EST
Not sure if this is an anaconda bug.... couldn't find out which package
owns /etc/modules.conf
build: qa0217.1
TUI upgrade 6.2 Everything --> 7.1 RC1

There was no network connectivity after upgrade.
/etc/modules.conf:
alias eth0 old_tulip

# insmod tulip
# service network restart
restored network connectivity
Comment 1 Bill Nottingham 2001-02-17 22:25:25 EST
What happens if you run '/usr/sbin/module_upgrade' from 
the command line?
Comment 2 Ben Levenson 2001-02-20 11:25:27 EST
executing 'module_upgrade' just caused the system
to pause momentarily -- it just returned me to the command
line when it was done.

modules.conf still refers to old_tulip.
Comment 3 Bill Nottingham 2001-02-20 18:01:14 EST
Is this machine still around somewhere?
Comment 4 Bill Nottingham 2001-02-20 19:27:18 EST
Fixed in kudzu-0.96.9-1.
Comment 5 Ben Levenson 2001-02-23 17:58:16 EST
fix verified in build qa0223.2
Comment 6 Ben Levenson 2001-03-12 10:46:30 EST
build qa0310.0
kudzu-0.97.6-1

modules.conf (after upgrade 7.0 --> 7.1):
alias eth0 old_tulip

executing /usr/sbin/module_upgrade _did_ update modules.conf
correctly.
Comment 7 Bill Nottingham 2001-03-12 21:30:30 EST
This should be fixed in kernel-2.4.2-0.1.27 or later.

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