Hide Forgot
From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0b; Windows NT 5.1) Description of problem: After I select packages and confirm the installer's logging of everything to /tmp/install.log, I get a blue screen and the message "type read: Operation not permitted" How reproducible: Always Steps to Reproduce: 1.Boot setup CD 2.Configure everything, select packages 3.Press ok to start copying files Actual Results: System hangs and gives me: "type read: Operation not permitted" Expected Results: The files should've been copied. Additional info: I'm trying to install RH7.1 on a PC. I'm able to boot and start installing in text mode. I choose custom install and get through everything (partitioning, choosing packages, etc) and finally it tells me it'll log everything to /tmp/install.log. I press okay and get a blue error screen saying: "type read: Operation not permitted" The machine is a Pentium 200 MHz with 64 MB EDO. I've tried three hard drives, three cd-rom drives, other ram modules and another pair of installation cds. None of that worked. It had been running RH6.1 for a year or so but I wanted to upgrade. Google only finds one webpage where this problem is described ( http://www.mail-archive.com/linux-hardware@senator- bedfellow.mit.edu/msg04827.html ). I mailed the one who had the problem and he told me to use RH7.0 (but I haven't tried that yet).
try typing "linux ide=nodma" at the boot: prompt of the CD.
Closing due to inactivity. Please reopen if you have more information.
This bug looks similar to bug #37592, which we never got a satisfactory resolution on. ke7rt, can you provide some info about your hardware (motherboard, video card, etc.)? In particular, do you have a Digital Celebris computer?
Hi Brent, Hardware is : Digital Celebris GL 6180 ( did that sound like a death knell???????) video card : Matrox Millenium (as recognized by Linux install program???????) going to look at bug 37592 some more Ron
Yep, I thought it might be this system. Unfortunately, we don't have any of those machines in house, so we can't reproduce the problem. It looks like this bug is a dupe of bug 37592. Without the hardware in question, we don't have much chance of being able to fix this. *** This bug has been marked as a duplicate of 37592 ***