Bug 157580

Summary:	Bad:redhat exec of anaconda failed permission denied
Product:	Red Hat Enterprise Linux 4	Reporter:	Sanjeev Shankar <sshankar>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED CANTFIX	QA Contact:	Mike McLean <mikem>
Severity:	high	Docs Contact:
Priority:	medium
Version:	4.0
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-09-21 21:10:00 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Sanjeev Shankar 2005-05-12 19:59:53 UTC

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:
Always

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" ........
3.
  

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 20:33:39 UTC

Have you verified your media according to the instructions at
http://rhlinux.redhat.com/anaconda/mediacheck.html?

Comment 2 Jeremy Katz 2005-09-21 21:10:00 UTC

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.