Re: System freeze
- To: firstname.lastname@example.org
- Subject: Re: System freeze
- From: email@example.com
- Date: Tue, 31 Oct 2006 20:34:40 -0500
- Message-id: <[🔎] 20061101013440.GD1665@topoi.pooq.com>
- In-reply-to: <1162313153.2393.22.camel@ix>
- References: <1162245792.3861.9.camel@localhost> <firstname.lastname@example.org> <1162249108.3446.1.camel@localhost> <1162289377.3416.1.camel@localhost> <20061031160723.GA738@topoi.pooq.com> <1162313153.2393.22.camel@ix>
On Tue, Oct 31, 2006 at 10:45:53AM -0600, Stephen Olander Waters wrote:
> All of you with X system freezes,
> Check the top of your dmesg for any warnings about "aperture size". I
> kept getting freezes because my AGP aperture was too small (32MB) for
> what Linux wanted (64MB) on a Radeon 9200 256MB. I hadn't noticed the
> warning because X didn't complain in Xorg.0.log and the kernel driver
> didn't complain when X was loading.
On my ubuntu system (the one that doesn't crash)
hendrik@april:~$ dmesg | grep -i aperture
[ 0.000000] Checking aperture...
[ 0.000000] CPU 0: aperture @ 0 size 32 MB
hat's on my Ubuntu system, which does not freeze.
Will try etch (same machine, dual boot) when I get the chance.
By the way, how does one change the aperture size? Or is it
I have nvidia graphic chips on the motherboard. I get crashes in etch
but not in dapper. Can't try etch right now because I have several
users on the system. Will try tomorrow.