savage inproper init

[Alex Deucher]

On Dec 11, 2007 11:49 AM, Ralovich Kristóf <kristof.ralovich at gmail.com> wrote:
> Hi,
>
> I would like to report about hard lockups (ping and ssh stops too)
> caused by the savage driver. I am getting the same results no matter
> if I use the savage fbdev or not. Neither EXA / XAA changes the
> situation. Additionally if I use EXA, it garbles the bitmaps and the X
> screen around the cursor. The machine is an IBM T22. I can not find
> any further details in the system logs or X log.
>
> The symptom is if boot up, X wont run, it hangs before switching to
> the desired resolution. But if I run windows first then reboot and
> start linux, everything is going fine. GL and Xv works too.
>
> The other way avoiding the lockup2 was putting the AGPMode "2" line to
> the Device section, it was a little bit slower, but it was stable at
> least.

Savage IX/MX cards are only AGP 2x cards.  Some savage agp 2x cards do
not like 1x mode (the driver default).  I never had a chance to figure
out which cards this affected as it was hit or miss.  We should
probably just default to whatever AGP mode the bios sets up.

Alex