Bug 157580 - Bad:redhat exec of anaconda failed permission denied
Bad:redhat exec of anaconda failed permission denied
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: anaconda (Show other bugs)
i686 Linux
medium Severity high
: ---
: ---
Assigned To: Anaconda Maintenance Team
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2005-05-12 15:59 EDT by Sanjeev Shankar
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-09-21 17:10:00 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 Sanjeev Shankar 2005-05-12 15:59:53 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3

Description of problem:
Trying to install RHEL ES4.0 on a IBM R40. The install fails with
"redhat exec of anaconda failed: permission denied". Checked bugzilla and found
similar situations with FC1/2 where "linux allowcddma" was agreed upon solution.
This does not work for me. 

H/W: IBM ThinkPad R40, 100G HD and 1G RAM

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.Reboot system and boot from RHEL 4.0 install CD
2.At prompt 1. hit return OR 2. type "linux alllowcddma" OR 3.type "linux allowcddma notext" ........

Actual Results:  
The install process failed woth the following
"redhat exec of anaconda failed permission denied
sending termination signal......"

Expected Results:  Should have progressed through a successful install.

Additional info:
Comment 1 Jeremy Katz 2005-05-16 16:33:39 EDT
Have you verified your media according to the instructions at
Comment 2 Jeremy Katz 2005-09-21 17:10:00 EDT
Since there are insufficient details provided in this report for us to
investigate the issue further, and we have not received the feedback we
requested, we will assume the problem was not reproduceable or has been fixed in
a later update for this product.  If you have further details, feel free to
reopen the report with the additional details attached.

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