Bug 30563 - Installer loops on FTP install using bootnet.img
Summary: Installer loops on FTP install using bootnet.img
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda   
(Show other bugs)
Version: 7.1
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Matt Wilson
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2001-03-04 17:37 UTC by Stephen Williams
Modified: 2007-04-18 16:31 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-03-09 16:18:38 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Stephen Williams 2001-03-04 17:37:04 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.2.18 i686; en-US; Galeon)

Using the bootnet.img from the Wolverine distro does not allow me to
perform an FTP install.  When selecting FTP from the menu then selecting my
NIC from the list (3Com type), the installer loops back to prompting for
the type of install (FTP, NFS, HTTP).  If I select FTP again, the 3Com
option is no longer listed in the NIC list.  I have tried the graphical,
text, lowres, nofb, and expert installs, all have the same result.

Reproducible: Always
Steps to Reproduce:
1.  Create network boot disk with the bootnet.img file on the Wolverine
2.  Boot with it, select any install method except driver disk or rescue
3.  Try an FTP install

Actual Results:  The installer loops back to prompting for an installation

Expected Results:  Should proceed and ask for ftp address

I checked the consoles, there is no additional output when this occurs.

Comment 1 Preston Brown 2001-03-05 18:03:40 UTC
not a bug in pax, a bug in the installer if anything.

Comment 2 Michael Fulbright 2001-03-05 20:28:58 UTC
What is the exact model of your 3com NIC?

Comment 3 Stephen Williams 2001-03-05 21:09:24 UTC
Sorry about the incorrect component.  The NIC is a 3Com Etherlink III ISA

Comment 4 Bill Crawford 2001-03-08 12:28:59 UTC
This is solved by using the driver disk (drivers.img).  The 3Com Etherlink
II/III is not supported by the 59x driver.  I bumped into this one doing an FTP
upgrade on a friend's machine.
You also need to boot with ramdisk_size set to greater than the size of the /usr
ramdisk image, e.g. set to 8192 (i.e. 8M) as the default maximum size is 4M.

Comment 5 Michael Fulbright 2001-03-09 16:18:33 UTC
Matt will you please make sure we have any required changes reflected in our
internal tree?

Comment 6 Matt Wilson 2001-03-09 16:35:13 UTC
the kernel has a compiled-in default of 8M for the BOOT kernel.  The real issue
here was the card needing the driver disk

Comment 7 Bill Crawford 2001-03-09 16:35:49 UTC
Could I suggest you try to fit the 3c509 driver on the boot floppy?  It is a
*very* common card in older machines, and most people (myself included) expect
it to work "out of the box" ... and it's easy to misread the 59x entry on the
menu that appears.  In particular, the EtherLink cards are ones that we tend to
hunt down and scavenge for use on older boxes.

Comment 8 Bill Crawford 2001-03-09 16:40:21 UTC
And, uh, no, I had to specify the ramdisk_size parameter too.  Otherwise it
didn't work.  I only realised this after watching it fail to load the /usr image
several times.  I've done this on two machines, one of which had a 3c905B in and
so worked immediately ... until it came time to fetch the images.  This was in
Wolverine, the Raw Hide version may be fixed now.

Comment 9 Matt Wilson 2001-03-09 16:51:03 UTC
I've forgotten, are those ISA cards?

Comment 10 Bill Crawford 2001-03-09 17:49:04 UTC
The one I have in my desktop box is a PCI (3c905B).
The one in the older box is an ISA card (3c509something, EtherLinkIII).

Point being that older boxes which still have ISA slots, and are being used by
technical folks, may well have these older cards in ... they're still fairly
common ... the driver is 11k, so it shouldn't be too hard to squeeze in?

Every box we have here over a year old has either one of these or a newer 3com
card in.

Comment 11 Bill Crawford 2001-03-19 18:16:43 UTC
Can you confirm whether the ramdisk_size issue has been resolved?  There is at
least one other known case of the problem, on the Wolverine mailing list, which
was fixed by booting with this parameter at the syslinux prompt.

Comment 12 Matt Wilson 2001-03-19 19:42:45 UTC
if you are using the wolverine bootnet.img, you should *not* need to pass in

Comment 13 Bill Crawford 2001-03-19 21:58:02 UTC
I definitely used bootnet.img from Wolverine, because I'd downloaded the CD
images, then had to copy all the files off the images into a tree to make a
network install work.
I *did* have to use the ramdisk_size parameter, and two people in the last two
days have "me-too"ed on Wolverine-list that it fixed an install failure for
I only twigged because I looked at the messages on one of the VTs and saw
something about a write failure to the ramdisk.

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