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 39194 - running anaconda bad argument --overhead unknown option
running anaconda bad argument --overhead unknown option
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: 2001-05-05 04:21 EDT by rich van steenberg
Modified: 2007-04-18 12:33 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-05-20 13:22:10 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 rich van steenberg 2001-05-05 04:21:59 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)

Description of problem:
mounts ramdisk then says 
running anaconda bad argument --overhead unknown option
exits install

How reproducible:

Steps to Reproduce:
1.restart install

Actual Results:  mounts ramdisk then says 
running anaconda bad argument --overhead unknown option
exits install

Expected Results:  correct full install

Additional info:
Comment 1 Brent Fox 2001-05-05 20:01:43 EDT
Are you passing in any boot options in or are you just booting off the cd and
pressing <Enter>?
Comment 2 rich van steenberg 2001-05-05 20:08:05 EDT
i created a bootnet.img install disk. i then run an ftp install from the web. 
when the routine starts it mounts a ramdisk and then it transfers from the blue 
screen to a black text srcreen and appears to call either anaconda or anaconda 
runtime? It them returns the --overhead unknown option - I am not passing it 
any options -
Comment 3 Brent Fox 2001-05-07 11:25:50 EDT
Can you post the contents of the syslinux.cfg file on the boot floppy that you
are using?  Something sounds very strange here.  Also, did you try installing
from a different ftp site?
Comment 4 rich van steenberg 2001-05-10 02:40:39 EDT
I did a dd if=bootnet.img of=/dev/fd0, then i ran the install.
when i put the boot disk in a different 7.0 box, mount /dev/fdo, cd fd and do a 
ls -la it doesn't show a syslinux.cfg file
Comment 5 Brent Fox 2001-05-10 11:40:13 EDT
Ok, something is horribly wrong with your boot disk.  If there's no syslinux.cfg
file, I'm amazed that the system even boots.  I did a little experimenting by
making a bootnet.img boot disk and then I removed the syslinux.cfg file.  When I
rebooted the system, I get the syslinux prompt followed by a message:
"Could not find kernel image: linux"

Sounds like something is wrong with your installation media, since it looks like
you made the boot disk correctly...something else must be wrong with the
bootnet.img itself.
Comment 6 Brent Fox 2001-05-20 13:22:06 EDT
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)
Comment 7 Brent Fox 2001-05-20 13:23:51 EDT
Closing due to inactivity. Please reopen if you have more information.

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