Description of problem: When I try and install on a specific new machine I get a install exited abnormally [1/1] error Version-Release number of selected component (if applicable): this is trying to do an over the network brand new install of fc8 It actaully works probably in fc7 How reproducible: 100% Steps to Reproduce: 1. try and do a network install 2. get to anoconda and it crashes in a few seconds after the first line of the program running is displayed. 3. Tried to boot to rescue mode to see if I could find the problem, but it just kind of hangs at more or less the same spot.
By the say has anyone noticed that bugzilla still says that the current version is fc7 ;-)
Does it help if you boot with 'linux nopcmcia'?
Well the fc7 install worked fine.
The npcmcia didn't fix the problem with the fc8 boot.
Can you please attach a picture or the text of the error message to this bug report?
The error is as I specified above "install exited abnormally [1/1]" No other message is given on the screen. If I need to look somewhere else I can.
If this is not clear enough on the error, I oculd take a digital picture of the screen and attach it I guess. But will the system here allow a digital picture sized attachment. I have had problems in the past with just large text files being to large.
Created attachment 272121 [details] Picture of screen during failure
Created attachment 272131 [details] Picture of screen during failure
Created attachment 272151 [details] Picture of screen during failure
Created attachment 272161 [details] Picture of screen during failure
OK here are four pictures of the screen. One of the main screen and then a close up of it. The other two are the other two alt ctrl function screens. I hope this at least defines the error. Let me know what else you need to know.
Looks like the same bug I found, is your cpu i586 based? https://bugzilla.redhat.com/show_bug.cgi?id=367731
Pentium 3 600Mhz Processor
I am fully upgraded, but I still have some old machines which do this if I need to do a full reinstall for testing. To do the install of this machine I did an install of fc7 and then upgraded using yum.
Problems like this sometimes end up being random kernel errors that kill anaconda and we cannot detect. Are you able to reproduce this at all in rawhide?
Exactly how would I do the raw hide thing? It may be hard to actually test this, as this machine is now in production mode.
Could you reproduce this using a Fedora Unity Re-Spin (it has a newer kernel)? http://spins.fedoraunity.org/spins to get the bits
OK I found out how to do the rawhide thing. Good news, bad news. Good news I didn't get this error. But the bad news is that it exited before I could get to the place that the error occurred before. I don't know if this is a new bug or not. I get to a place where it says Checking if image is a initramfs it isn't (bad gzip magic number) Looks like an initrd and then just hangs. Now this is on the machine which had this other error before. The rawhide load seems to be working for many other machines so far. So is this a new error or a different display of the same error?
It looks to me like your initial problem is solved by Rawhide, but you have a new issue now. We'd need to see more details to know exactly what's going wrong but it looks like a possible bad download of the initrd or some sort of hardware failure. I'm going to close this bug. If you'd like to open a new one for your new issue, feel free.
Chris: I am not sure if I should open another one, or if we should do something with this one. It appears that my CPU is now too old to run fedora. I can find this commented on a bunch of places during doing google searches. I seem to be able to find comments on exactly my failure that mention that the older CPUs are no longer supported. BUT I can't find this anywhere in the official documentation. I also find several comments specifically that there is some kind of a test of the CPU being done, and if the test fails because the CPU is not up to the task the system rebooting. First one would think that minimum system requirements would be a matter somewhere prominent in the documentation, and I can't find it. Also one would think that a reboot with no message in response to a test of the CPU finding that it is not up to snuff to be a really bad choice of response to a test failure. I have a VIA c3-1 giga pro cpu. Is my problem that this is just not enough to cut the muster?
Sorry about this but I do have this problem on multiple machines. the p3 600 is now working.
And you are testing this with what release?
I have checked this with 9, alpha through production and 10 beta. (never got around to doing the alpha release) I have a fairly consistent set of problems through all of them. It works fine both for install and for operation on FC 8.
I can't see how the CPU would be a problem here anyway. If it were too old to work with Fedora, the kernel wouldn't even boot. You wouldn't just get partway into anaconda and fail.
I am not sure if I am getting to anaconda or not. You will note my comment 19. Is this a part of anoconda or the kernel? Could the CPU be causing this? If it is the kernel then probably we need a new bug report, if it is still anoconda then maybe we should continue as it may be the same bug with a different expression.