Bug#668620: Info. asked about megaglest crasher -

[shirish शिरीष]

in-line :-

On Fri, Apr 20, 2012 at 01:35, Tom Reynolds <tomreyn at megaglest.org> wrote:
> On 19.04.2012 06:38 Mark Vejvoda wrote:
>> What kind of video card do you have (And how much RAM does it have)?
>
> Based on the command output Shirish sent along he (I assume this is a
> man's name, sorry in case I'm wrong) has 256MB shared RAM in use by his
> integrated Intel G33 GPU, which is mounted to a P5KPL-VM mainboard.
> Based on other command output he provided, he has 966 MB RAM available
> (for MegaGlest only) on top of what Linux and the other applications
> consume, and has a Pentium E5400 (dual-core) CPU.

Hi Tom,
          I am a man/male last time I checked. Anyways, moving on I
have 2 GB DDR2 RAM but as rightly pointed out it's between 128-256
shared by the Intel Integrated graphics chipset (depending on whom you
ask/what is available) . The mainboard/motherboard specs are correct
as well.

> I had pointed him to the Glest forum thread which discusses how to
> configure MegaGlest to consume as little resources as possible, and
> based on his latest feedback my understanding is that the game works
> well for him after applying these modifications.

correct.

> It seems to me that 256 MB of video memory can be too little with the
> default configuration, and that 128 MB MB of video memory is almost
> always insufficient. We may need a test for this?

that would be nice.

> Tor what it's worth, it would seem that Shirish reports "works for me"
> and ask for this bug to be closed.

True, after the modifications, yes 'it works for me' .

As an aside though, I do have another query though, in your first
reply you had spoken about

"on a mixed Debian stable/testing/unstable system " . Was that because
of the policy ?

 APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'),
(1, 'experimental')

or something else. Because what I try to do is have the highest
version of each and every package in sid. The other releases are just
for me to check on what version numbers others are at (info. which
is/can be handy at times.) . Also if I do get some nasty update then
can switch to the testing or stable versions of software if need be
till it gets fixed (hasn't had to use that for a long time since
apt-listbugs does it job well).

Just thought I would mention it so there's no confusion.

> Tom

-- 
          Regards,
          Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
065C 6D79 A68C E7EA 52B3  8D70 950D 53FB 729A 8B17