From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows 98) Description of problem: The fedora core 3 install do not start on my k6-2+ @500 Mhz. It hangs during startup at "Uncompressing linux...". I switch the processor with an ordinary k6-2 @500 Mhz (without +, i.e without the L2 cache on die) and the install boot normally. My k6-2+ works fine with other OS: win98, winXP, redhat 7.3. After I install FC3 with the system working with the k6-2@500, I switch back to the k6-2+. The system boots with the installed kernel. My mother supersoket 7 mobo support k6-2+ and k6-3+ processors. My sytem configuration: AMD k62+@500 Mhz (5x100), 120 SDRAM PC100, Matsonic 6260S mobo 1Mb cache, Matrox G200 8Mb graphic adapter, 10 GB HDD Wester Digital Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Get a super socket 7 motherboard with 100 FSB support and 5x multiplier 2. A k6-2+ proccesor (important: the L2 cache on die) 3. Try to boot the install of FC3 from cd Actual Results: The boot process hangs during startup at "Uncompressing linux...". Expected Results: Boot, of course ;) Additional info: After I install FC3 with the system working with the k6-2@500, I switch back to the k6-2+. The system boots with the installed kernel. Something miss, or it's wrong compiled in the boot kernel of the install cd. The same behavior I've got with another Linux distro: Ubuntu.
Which kernel are you running with (is it an i686 or an i586 kernel)? What is the output of uname -a ? To the best of my knowledge the k6-2+ was a mobile k6-2 but it's not impossible that there were some bugs present not in a regular k6-2 or that some "unnecessary" instructions were left out...
On the fresh install fc3, system running with the k6-2+ processor: #uname -a Linux Darius 2.6.9-1.667 #1 Tue Nov 2 14:41:31 EST 2004 i586 i586 i386 GNU/Linux
sorry, :(, false alarm. FC3 install cd booted ok after I set "System BIOS Cacheable" to Disable. Some incompatibility between de my k6-2+ processor and the Ali V chipset. Anyway, this should be noted in some FAQ.