On Wed, Dec 11, 2002 at 11:42:23PM +0100, Juliusz Chroboczek wrote:
> This is fixed in upstream CVS. It is due to the 4.2 version of the
> Savage driver mis-detecting the video memory size.
>
> A workaround is to set the size in your XF86Config-4 explicitly using
> the VideoRam keyword. A proper
On Wed, Dec 11, 2002 at 11:42:23PM +0100, Juliusz Chroboczek wrote:
> This is fixed in upstream CVS. It is due to the 4.2 version of the
> Savage driver mis-detecting the video memory size.
>
> A workaround is to set the size in your XF86Config-4 explicitly using
> the VideoRam keyword. A proper
This is fixed in upstream CVS. It is due to the 4.2 version of the
Savage driver mis-detecting the video memory size.
A workaround is to set the size in your XF86Config-4 explicitly using
the VideoRam keyword. A proper solution is to remove the code that
(mistakenly) probes for the memory size u
This is fixed in upstream CVS. It is due to the 4.2 version of the
Savage driver mis-detecting the video memory size.
A workaround is to set the size in your XF86Config-4 explicitly using
the VideoRam keyword. A proper solution is to remove the code that
(mistakenly) probes for the memory size u
4 matches
Mail list logo