MrStar
07-18-2001, 09:34 AM
Hi. I'm having some strange problems. Here is my setup:
Athlon 1.33ghz 266mhz FSB
256MB PC133 Kingmax TinyBGA
Iwill KK266-R (RAID is disabled)
30gig HD - win2k
10gig HD - Linux
LNE100TX NIC
another generic NIC using the tulip driver
ES1370 Soundcard
Generic 50x CDROM
Plextor 8/4/32 CDRW
First of all, I had a hell of a time getting linux installed. Progeny, Redhat, as well as FreeBSD(yes, i know it's not linux), gave me errors. The only one that didn't was slack 8.
Slack 8 installed perfectly and is currently(after fixing it more than 3 times) running great. There is one little(read: major) problem. Whenever I compile my kernel and tell it I have a "Athlon/Duron/K7" processor, I get kernel panics on bootup. It really sucks. Right now I'm using the "386" option. Sure, it might not make a damn bit of different in terms of performance, but it *should* work (and hopefully help my performance). One time I thought I had it working, I went to /dev and did a "ls" and the kernel paniced. When I rebooted, the kernel paniced at somepoint when it was running the rc.M script.
I tried using the 2.4.6 kernel also, with the same results.
As of right now, I'm using the 2.4.5 kernel compiled for a 386 processor and things are working fine. Sound works, both NIC's work.. this kernel problem is the only problem(thus far..)
Could any of you guys think what might be causing this? Thanks.
Mr_Superstar
Athlon 1.33ghz 266mhz FSB
256MB PC133 Kingmax TinyBGA
Iwill KK266-R (RAID is disabled)
30gig HD - win2k
10gig HD - Linux
LNE100TX NIC
another generic NIC using the tulip driver
ES1370 Soundcard
Generic 50x CDROM
Plextor 8/4/32 CDRW
First of all, I had a hell of a time getting linux installed. Progeny, Redhat, as well as FreeBSD(yes, i know it's not linux), gave me errors. The only one that didn't was slack 8.
Slack 8 installed perfectly and is currently(after fixing it more than 3 times) running great. There is one little(read: major) problem. Whenever I compile my kernel and tell it I have a "Athlon/Duron/K7" processor, I get kernel panics on bootup. It really sucks. Right now I'm using the "386" option. Sure, it might not make a damn bit of different in terms of performance, but it *should* work (and hopefully help my performance). One time I thought I had it working, I went to /dev and did a "ls" and the kernel paniced. When I rebooted, the kernel paniced at somepoint when it was running the rc.M script.
I tried using the 2.4.6 kernel also, with the same results.
As of right now, I'm using the 2.4.5 kernel compiled for a 386 processor and things are working fine. Sound works, both NIC's work.. this kernel problem is the only problem(thus far..)
Could any of you guys think what might be causing this? Thanks.
Mr_Superstar