Description of problem: net install CD crashes early Version-Release number of selected component (if applicable): F10 alpha How reproducible: reproduceable Steps to Reproduce: 1. Boot netinst CD 2. Select "Install or upgrade ... 3. Watch Loading vmlinuz ... 4. Watch Loading initrd ... Actual results: BUG Int 14: CR2 f000e7e9 Expected results: Starting anaconda ... Additional info: Via C3
I'm guessing this issue has been resolved in later releases. Can you confirm John? Did you try any other net installs later on?
I did not do another netinst on the Via, and worse yet, I moved it to a service 100 miles away. I assume the Via is old enough that it simply won't play with F10. I did try an F9 and F8 install, neither worked, but one (unfortunately I can't recall which) said the processor was unsupported. So, I installed FC6 and moved it to a service that isn't so demanding.
If this is still an issue and hasn't been fixed, I think it's a GA Blocker. Someone please correct me if I'm wrong.
I don't fully understand the rules, so perhaps this is inappropriate. But it seems to me that the Via C3 was a tiny player to begin with, and the number of Via C3 systems that might attempt to run F10 would be vanishingly small. Of course, I suppose it is possible that the Via issue is indicative of some larger issue, but keep in mind that neither F8 nor F9 would install on this box, although neither failed quite as dramatically.
(In reply to comment #4) > I don't fully understand the rules, so perhaps this is inappropriate. But it > seems to me that the Via C3 was a tiny player to begin with, and the number of > Via C3 systems that might attempt to run F10 would be vanishingly small. Of > course, I suppose it is possible that the Via issue is indicative of some > larger issue, but keep in mind that neither F8 nor F9 would install on this > box, although neither failed quite as dramatically. C3 should work, but we'd need to see the complete message from a later version of Fedora 10 to debug the problem.
We've tested F10 on a C3 here, and were unable to reproduce the problem. If you see it again, please re-open with the full trace from the kernel. Thanks!