When I initially installed my new Asus K7M (Athlon 600) motherboard under an already existing linux system that was compiled for an AMD k6-3, I had no problems, and it ran like a champ. Something caused me to have to reinstall Windows 98 again which replaced my boot sector with Windows 98. The usual cure for this is to boot into linux using the Suse boot disk or an alternate boot disk, then rerun lilo. The problem I ran into was booting from the Suse floppy for 6.2, which contains kernel 2.2.10. I got around this by making a DOS floppy, put loadlin on it and compiling a kernel on another machine for the AMD and other useful options. I mention this because I think it will be darn near impossible to install Suse linux from scratch on the Asus K7M unless an alternate boot floppy is used. I suspect it is chipset related, and not related to the CPU itself. -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
On Tue, 21 Mar 2000, you wrote:
When I initially installed my new Asus K7M (Athlon 600) motherboard under an already existing linux system that was compiled for an AMD k6-3, I had no problems, and it ran like a champ. Something caused me to have to reinstall Windows 98 again which replaced my boot sector with Windows 98. The usual cure for this is to boot into linux using the Suse boot disk or an alternate boot disk, then rerun lilo. The problem I ran into was booting from the Suse floppy for 6.2, which contains kernel 2.2.10. I got around this by making a DOS floppy, put loadlin on it and compiling a kernel on another machine for the AMD and other useful options.
I mention this because I think it will be darn near impossible to install Suse linux from scratch on the Asus K7M unless an alternate boot floppy is used. I suspect it is chipset related, and not related to the CPU itself.
No it is not chipset related it is kernel 2.2.10 and cpu related, specifically the mtrr setting in the kernel. If one is inclined to they can download the necessary files to make a boot floppy for SuSE 6.2 then rebuild the kernel with the proper setting for mtrr which I believe is no/off. This of course is not anything new.
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
I mention this because I think it will be darn near impossible to install Suse linux from scratch on the Asus K7M unless an alternate boot floppy is used. I suspect it is chipset related, and not related to the CPU itself.
I have had this problem when I tried to install Linux SUSE 6.2 on my Athlon. I had to download the image file from ftp.suse.com, and make another boot disk for Suse 6.2. I use an Athlon 600, but I had a different chipset and a different MB. So I am sure it's CPU related. -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
participants (3)
-
jkrough＠cojones.chem.lsu.edu -
jlm＠compgen.com -
praise.tazio＠mclink.it