yeah, i am using the mem=nopentium option.

sorry i forgot the mention that.


----- Original Message -----
From: "kingsley" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, February 20, 2002 12:18 AM
Subject: Re: [Xmame] Xmame.xgl Freeze


> Samuel Davidoff wrote:
> > This one's got me puzzled. I run xmame.xgl on an Athlon 800, linux
> > 2.4.17, tnt2 agp card, and via mb with onboard sound and nic.
>
> I'm running an Athlon 1400, 2.4.17, Matrox g550, SB-16 'Vibra' clone.
> (got it after giving up on the ac'97 audio) 1.5G RAM...
>
> > I randomly get a lockup while playing. The game will freeze and the
> > sound will loop indefinitely. Other than that the box is locked up hard.
> > Can't ssh in or anything. I though maybe it was a RAM problem but I
> > doubled my RAM from 128 to 256 and still get the lockup. I also thought
> > maybe the video card, and tried setting the motherboard back to 2x AGP.
> > Still got the lockup. Checked CPU temp., that seems fine too.
>  >
> > It's truly intermittent sometimes it will happen after a few minutes,
> > other times after hours (and hours) of play. Haven't seen it on any
> > other apps. Though they don't get nearly as much airtime as mame.
>  >
> > I'm currently suspecting the via onboard sound (see previous posts), but
> > before I buy another card, was wondering if anyone had any ideas? Seen
> > it before?
>
> I've had almost *exactly* these problems with "Return to Wolfenstien" in
the
> last few days, and Quake III to a lesser extent (less as in less-frequent
> lockups). X-lockup, looping sound.
>
> I tweaked just about everything in the bios, agp speed, apperture size
> (whadda's this do anyway), and various Enable/Disable things.  Not a
single
> thing helped.  I also tweaked the crap out of Wolfensiten (Essentially
> a hacked version of Q3)  After many many tries, I eventually set the
> texture detail to 'low low low' with a particular combination of other
things.
>
> That was it, it stopped locking up.
>
> I don't see how you can use this information directly with xmame.xgl,
> but it might give you some pointers.
> Sorry this has become off-topic, but the hardware and problem is
> uncannily matched to what I was having last night.
>
> Personally I think it's an AGP/GART/DRI problem.
> are you booting with the "mem=nopentium" option ?
>
> -kt
>
> --
> Kingsley Turner,
> (mailto: [EMAIL PROTECTED])
> http://MadDogsBreakfast.com - Travel Tales: The good, bad, and down-right
ugly
>
>
> _______________________________________________
> Xmame mailing list
> [EMAIL PROTECTED]
> http://toybox.twisted.org.uk/mailman/listinfo/xmame


_______________________________________________
Xmame mailing list
[EMAIL PROTECTED]
http://toybox.twisted.org.uk/mailman/listinfo/xmame

Reply via email to