Re: AMD, Cyrix and 2.2r don't mix
On Sat, 3 Feb 2001 21:56:28 -0800, Nick whispered to the router:
!!This is a multi-part message in MIME format.
!!
!! ------=_NextPart_000_000D_01C08E2C.292B9080
!! Content-Type: text/plain;
!! charset="iso-8859-1"
!! Content-Transfer-Encoding: quoted-printable
!!
!! Hello list,
!!
!! I recently downloaded the CD image of potato, officially called '2.2r'
!! I tried an install on an AMD 1.1 TB Socket A w/ 768 mb ram, Asus AV7 =
!! motherboard
!! I got a kernel panic halt, then it completely freezes up, ctl-alt-del
=
!! don't even work.
!!
!! Last week I tried to install the same 2.2r, but for a different media,
=
!! onto a Compaq Presario w/ a Cyrix CPU,
!! same thing, kernel halt then it spits out is junk a mile long.
!!
!! I have installed this version successfully, just not on these two =
!! machines. =20
!! The machines I have had luck w/ all had Intel CPU Pentiums, and one =
!! Pentium !!!
!!
!! What this all boils down to is that I gotta be missing something here.
=
!! Do AMD and Cyrix CPU require a special boot mode or something?
!!
!! Anyone experienced the same problem with AMD and Cyrix?
!!
nope.. i've installed debian potato on a k7, a k6-3 and a p133. thats
all my machines. if you have the bandwidth, i suggest you use the
rescue floppy and the other disks needed, and do a network installation
so you are sure to get the more recent packages.
how exactly are you trying to install?
!! Maybe potato 2.2r official CD images aren't ready to be classified as
=
!! STABLE,=20
2.2r... what? the cd i have used once is 2.2r2, it's a release
revision. so, 2.2r doesn't make much sense
!!
!! ------=_NextPart_000_000D_01C08E2C.292B9080
!! Content-Type: text/html;
!! charset="iso-8859-1"
!! Content-Transfer-Encoding: quoted-printable
!!
!! <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
!! <HTML><HEAD>
!! <META http-equiv=3DContent-Type content=3D"text/html; =
!! charset=3Diso-8859-1">
!! <META content=3D"MSHTML 5.50.4611.1300" name=3DGENERATOR>
!! <STYLE></STYLE>
!! </HEAD>
!! <BODY bgColor=3D#ffffff>
!! <DIV><FONT face=3DArial size=3D2>Hello list,</FONT></DIV>
!! <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
!! <DIV><FONT face=3DArial size=3D2>I recently downloaded the CD image of
=
!! potato,=20
!! officially called '2.2r'</FONT></DIV>
!! <DIV><FONT face=3DArial size=3D2>I tried an install on an AMD 1.1
=
!! TB Socket A=20
!! w/ 768 mb ram, Asus AV7 motherboard</FONT></DIV>
!! <DIV><FONT face=3DArial size=3D2>I got a kernel panic halt, then it =
!! completely=20
!! freezes up, ctl-alt-del don't even work.</FONT></DIV>
!! <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
!! <DIV><FONT face=3DArial size=3D2>Last week I tried to install the same
=
!! 2.2r, but for=20
!! a different media, onto a Compaq Presario w/ a Cyrix CPU,</FONT></DIV>
!! <DIV><FONT face=3DArial size=3D2>same thing, kernel halt then it spits
=
!! out is junk a=20
!! mile long.</FONT></DIV>
!! <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
!! <DIV><FONT face=3DArial size=3D2>I have installed this version =
!! successfully, just=20
!! not on these two machines. </FONT></DIV>
!! <DIV><FONT face=3DArial size=3D2>The machines I have had luck w/ all
had =
!! Intel CPU=20
!! Pentiums, and one Pentium !!!</FONT></DIV>
!! <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
!! <DIV><FONT face=3DArial size=3D2>What this all boils down to is that I
=
!! gotta be=20
!! missing something here. Do AMD and Cyrix CPU require a special =
!! boot mode=20
!! or something?</FONT></DIV>
!! <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
!! <DIV><FONT face=3DArial size=3D2>Anyone experienced the same problem =
!! with AMD and=20
!! Cyrix?</FONT></DIV>
!! <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
!! <DIV><FONT face=3DArial size=3D2>Maybe potato 2.2r official CD images
=
!! aren't ready=20
!! to be classified as STABLE, </FONT></DIV></BODY></HTML>
!!
!! ------=_NextPart_000_000D_01C08E2C.292B9080--
!!
!!
--
Forrest English
http://truffula.net
"I don't like this air, but that doesn't
mean I'm going to stop breathing."
-Doug Martsch
Reply to: