From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0) Description of problem: After selecting the packages and X server, the dialogue window for the install log pops up, and when you press "OK", the installer crashes. It says "type read: Operation not permitted," then: "pfd: 9install exited abnormally" then: "sending terminattion signals...done" (you know the rest) note, I've seen different numbers after the pfd, including 8,9, and 14, also the output of the crash has newlines, but no line feeds. I have tried a variety of configurations: workstation, server, and custom. I have also tried to install from CD-ROM and FTP, and booting from floppy and CD-ROM. I am limited, however, a lowres or text install. I've looked throught the anaconda source, and it seems to crash when it get to the todo.doInstall() method. I've seen other reports of this error, search for "type read" and "operation not permitted" on Google Groups (Deja). <http://groups.google.com/groups?q=%22operation+not+permitted%22+% type+read%22> Some reports have the same computer I have, a Celebris GL 6180. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Go through normal installation steps... 2. When it tells you the location of the install log, say "OK" 3. Anaconda crashes. Actual Results: type read: Operation not permitted pfd: 9install exited abnormally sending termination signals...done ETC. Expected Results: It should be formatting the filesystems. Additional info: I using an old Celebris GL 6180 (PII 180) with a 15GB Maxtor harddrive (16383C, 63S, 16H).
try booting with "linux ide=nodma" at the boot: prompt.
Tried "linux ide=nodma". Again, it crashed with "type read: Operation no permitted." Note, the error messages in the graphical install (this is the first time I could do a graphical install besides "lowres") are slightly different than the text install, it says: type read: Operation not permitted pfd: 16xlib: unexpected async reply (sequence 0x58b2)! Also, nice enough, in this mode it doesn't send the term signals to everything, so the shell on "F2" is still working. These results are the same, with or without ide=nodma.
I just did an FTP install of SuSE 7.2 to see if it was specific to the RedHat distrobution or if it was a problem with Linux and my hardware. SuSE's YaST worked quite well. Nevertheless, I want RedHat, not SuSE. I have also experienced this problem with the RedHat 7.0 distribution.
I tried to upgrade to RedHat 7.1 from SuSE 7.2 to see if upgrading could provide a work around. All seemed to go well until it said I didn't have enough free space on /usr. Anaconda reported I needed 536MB under /usr, I have 750MB free out of 1GB, and another 4GB free mounted as /usr/local. There does seem to be a related bug on Anaconda not reading free space correctly, but I don't have the permmissions to view it.
try booting with "linux nousb"
Same results. Note: in the Graphical install, the error message doesn't appear in the X session, but whan you go to the other console at "CTRL-ALT-F1". If you don't look at the F1 console, the installer just appears to hang.
Just to cover everything, I made some ISO images of the CDs and tried to install from the hard drive. It still didn't work. (Same error message.)
This looks like a dupe of bug #37592. Red Hat just doesn't work on Celebris machines, and we don't have the hardware to duplicate this bug.
*** This bug has been marked as a duplicate of 37592 ***