Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 21692 - Anaconda dies with EATA driver + BOOTNET.IMG
Anaconda dies with EATA driver + BOOTNET.IMG
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Brent Fox
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2000-12-04 13:03 EST by Need Real Name
Modified: 2007-04-18 12:30 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-04-18 12:00:13 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Need Real Name 2000-12-04 13:03:11 EST
The content of bootnet.img is not up to date: if one takes the
redhat CD and a boot disk using the CD, with an EATA (DPT PM2144UW2)
controler, everything is fine.

If one tries to do the same from the bootnet.img file to perform
a net install, the installation process will die just after loading
the eata driver from the stage2 file. I tried with the latest version
of stage2 (october), I did not try to use eata from a driver disk.

Anaconda says that cpio of libm is fine. However, Python can not find

I dropped net install and went back to CD install.
Comment 1 Michael Fulbright 2000-12-04 14:03:17 EST
Passed to QA to reproduce.
Comment 2 Brent Fox 2001-04-11 14:57:20 EDT
Is there a Python traceback that appears?  If so, it would be helpful to know
what it is.
Comment 3 Need Real Name 2001-04-12 04:42:25 EDT
Sorry no Python traceback: this bug report is now 4 months old and I just 
installed all the required patches on your web site: performing again a full 
install on one of the concerned running computers would be a nightmare that 
I'de like to spare :-)
Comment 4 Brent Fox 2001-04-18 12:00:08 EDT
Ok.  I understand.  But since I can't see the traceback, I can't debug it.

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