XFree86-4.2.0_1,1 Config failure -- for ATI Mach 64 Rage Pro 8MB

XFree86-4.2.0_1,1 Config failure -- for ATI Mach 64 Rage Pro 8MB

Post by Michael Sierchi » Fri, 21 Jun 2002 12:06:36



Apologies if this post is duplicated...

X -configure yields a config file which blips hopelessly, probably
due to bad sync freqs.  I am trying to upgrade from 3.3.6, and
have attached the config that seems to work for that.  Any insights
(esp. a working config!) would be appreciated.

My monitor is an NEC MultiSync LCD 1700V, which works (according
to xvidtune) at

Res:
        1280x1024
Pixel Clock:    110 MHz
Depth:
        24
HSync:
        64.25 kHz
VSync:
        60.96 Hz

That is,

"1280x1024"   110.00   1280 1328 1512 1712   1024 1025 1028 1054

3.3.6 recognizes the card as



-----------------------------------------------------

# See 'man XF86Config' for info on the format of this file

Section "Files"
    RgbPath    "/usr/X11R6/lib/X11/rgb"
    FontPath   "/usr/X11R6/lib/X11/fonts/75dpi:unscaled"
    FontPath   "/usr/X11R6/lib/X11/fonts/75dpi"
    FontPath   "/usr/X11R6/lib/X11/fonts/100dpi:unscaled"
    FontPath   "/usr/X11R6/lib/X11/fonts/100dpi"
    FontPath   "/usr/X11R6/lib/X11/fonts/Speedo"
    FontPath   "/usr/X11R6/lib/X11/fonts/Type1"
    FontPath   "/usr/X11R6/lib/X11/fonts/local"
    FontPath   "/usr/X11R6/lib/X11/fonts/misc:unscaled"
    FontPath   "/usr/X11R6/lib/X11/fonts/misc"
EndSection

Section "ServerFlags"
EndSection

Section "Keyboard"
    Protocol        "Standard"
    XkbRules        "xfree86"
    XkbModel        "pc101"
    XkbLayout       "us"
EndSection

Section "Pointer"
    Protocol        "Intellimouse"
    Device          "/dev/psm0"
    BaudRate        1200
    SampleRate      2
    Resolution      100
    Buttons         3
    ZAxisMapping    4 5
EndSection

Section "Monitor"
    Identifier   "Primary Monitor"
    VendorName   "NEC"
    ModelName    "MultiSync LCD 1700V"
    HorizSync    31.5-80
    VertRefresh  56.3-75
    Gamma    1.1
    Modeline "1280x1024" 110.00 1280 1328 1512 1712 1024 1025 1028 1054
EndSection

Section "Device"
    Identifier      "Primary Card"
    VendorName      "Unknown"
    BoardName       "None"

EndSection

Section "Screen"
    Driver          "Accel"
    Device          "Primary Card"
    Monitor         "Primary Monitor"
    DefaultColorDepth 24
    SubSection "Display"
       Depth        24
       Modes        "1280x1024"
    EndSubSection
    SubSection "Display"
       Depth        32
       Modes        "1280x1024"
    EndSubSection
EndSection

 
 
 

XFree86-4.2.0_1,1 Config failure -- for ATI Mach 64 Rage Pro 8MB

Post by walt » Fri, 21 Jun 2002 21:53:39



> Apologies if this post is duplicated...

> X -configure yields a config file which blips hopelessly, probably
> due to bad sync freqs.  I am trying to upgrade from 3.3.6, and
> have attached the config that seems to work for that.  Any insights
> (esp. a working config!) would be appreciated.
> Section "Monitor"
>     HorizSync    31.5-80
>     VertRefresh  56.3-75
>     Modeline "1280x1024" 110.00 1280 1328 1512 1712 1024 1025 1028 1054
> EndSection
> Section "Screen"
>     DefaultColorDepth 24
>     SubSection "Display"
>        Depth        24
>        Modes        "1280x1024"
>     EndSubSection
>     SubSection "Display"
>        Depth        32
>        Modes        "1280x1024"
>     EndSubSection
> EndSection

The lines above are the ones I always have to add back in to a file
generated by X -configure because it just doesn't seem to add them.

You might make sure that your new XF86Config contains them--which it
won't if you didn't add them yourself.  The HorizSync and VertRefresh
default values may cause the server to use video modes your monitor
can't display.

 
 
 

XFree86-4.2.0_1,1 Config failure -- for ATI Mach 64 Rage Pro 8MB

Post by Dave Uhrin » Sat, 22 Jun 2002 05:23:56




>> Section "Monitor"
>>     HorizSync    31.5-80
>>     VertRefresh  56.3-75
>>     Modeline "1280x1024" 110.00 1280 1328 1512 1712 1024 1025 1028
>>     1054
>> EndSection

>> Section "Screen"
>>     DefaultColorDepth 24
>>     SubSection "Display"
>>        Depth        24
>>        Modes        "1280x1024"
>>     EndSubSection
>>     SubSection "Display"
>>        Depth        32
>>        Modes        "1280x1024"
>>     EndSubSection
>> EndSection

> The lines above are the ones I always have to add back in to a file
> generated by X -configure because it just doesn't seem to add them.

> You might make sure that your new XF86Config contains them--which it
> won't if you didn't add them yourself.  The HorizSync and VertRefresh
> default values may cause the server to use video modes your monitor
> can't display.

With the Rage Pro 8MB and a Compaq P70 monitor I had the same problems.
 The /etc/X11/XF86Config-4 file had no errors whatsoever and upon
starting X the monitor reported that the frequency was out of range
regardless of whether I chose a dot clock of 110.00 as above or 157.50
as my monitor uses with XFree86-4 in Solaris 8, Linux and OpenBSD-3.1.

Clearly X is broken for the ATI Rage Pro card in FreeBSD-4.6.  I blew
away the install and restored 4.5 with XFree86-3 and then did a binary
(and source) upgrade to 4.6 except for X.  All works well now.

 
 
 

XFree86-4.2.0_1,1 Config failure -- for ATI Mach 64 Rage Pro 8MB

Post by Erik Nygre » Sat, 22 Jun 2002 18:30:23




...
> With the Rage Pro 8MB and a Compaq P70 monitor I had the same problems.
>  The /etc/X11/XF86Config-4 file had no errors whatsoever and upon
> starting X the monitor reported that the frequency was out of range
> regardless of whether I chose a dot clock of 110.00 as above or 157.50
> as my monitor uses with XFree86-4 in Solaris 8, Linux and OpenBSD-3.1.

> Clearly X is broken for the ATI Rage Pro card in FreeBSD-4.6.  I blew
> away the install and restored 4.5 with XFree86-3 and then did a binary
> (and source) upgrade to 4.6 except for X.  All works well now.

I run into this problem as well - switching ati_drv.o and atimisc_drv.o
to XFree86 v4.1-versions solved my problems. The files are located in
/usr/X11R6/lib/modules/drivers/ (I think only ati_drv.o had to be replaced
but I switched both, and will not try to fix what is no longer broken)
If I understood this correctly, the ATI-drivers has gone through a major
rewrite between XFree86 4.1 and XFree86 4.2. Something to make them more
portable to other platforms (other than Intel x86 that is).

--
Erik Nygren
e r i k { a t } s w i p { d o t } n e t
Linux - If you hate Microsoft, FreeBSD - If you love Unix

 
 
 

XFree86-4.2.0_1,1 Config failure -- for ATI Mach 64 Rage Pro 8MB

Post by Michael Sierchi » Sat, 22 Jun 2002 23:26:24





> ...

>>With the Rage Pro 8MB and a Compaq P70 monitor I had the same problems.
>> The /etc/X11/XF86Config-4 file had no errors whatsoever and upon
>>starting X the monitor reported that the frequency was out of range
>>regardless of whether I chose a dot clock of 110.00 as above or 157.50
>>as my monitor uses with XFree86-4 in Solaris 8, Linux and OpenBSD-3.1.

>>Clearly X is broken for the ATI Rage Pro card in FreeBSD-4.6.  I blew
>>away the install and restored 4.5 with XFree86-3 and then did a binary
>>(and source) upgrade to 4.6 except for X.  All works well now.

> I run into this problem as well - switching ati_drv.o and atimisc_drv.o
> to XFree86 v4.1-versions solved my problems. The files are located in
> /usr/X11R6/lib/modules/drivers/ (I think only ati_drv.o had to be replaced
> but I switched both, and will not try to fix what is no longer broken)
> If I understood this correctly, the ATI-drivers has gone through a major
> rewrite between XFree86 4.1 and XFree86 4.2. Something to make them more
> portable to other platforms (other than Intel x86 that is).

I'll try that.  Note that it works with an old Apple-branded Sony
monitor, but I'm uncertain about my desk (Ikea) being able to
bear the weight ;-)  Besides, I like my LCD display.

Back in a few minutes...

 
 
 

XFree86-4.2.0_1,1 Config failure -- for ATI Mach 64 Rage Pro 8MB

Post by Michael Sierchi » Sat, 22 Jun 2002 23:47:06


Quote:>> I run into this problem as well - switching ati_drv.o and atimisc_drv.o
>> to XFree86 v4.1-versions solved my problems. The files are located in
>> /usr/X11R6/lib/modules/drivers/ (I think only ati_drv.o had to be
>> replaced
>> but I switched both, and will not try to fix what is no longer broken)
>> If I understood this correctly, the ATI-drivers has gone through a major
>> rewrite between XFree86 4.1 and XFree86 4.2. Something to make them more
>> portable to other platforms (other than Intel x86 that is).

Switching both was required -- though XFree86 went from <20MB to >40MB --
is this a * by memory manufacturers?
 
 
 

XFree86-4.2.0_1,1 Config failure -- for ATI Mach 64 Rage Pro 8MB

Post by Steve O'Hara-Smit » Sun, 23 Jun 2002 02:51:44


On Fri, 21 Jun 2002 07:47:06 -0700

MS> Switching both was required -- though XFree86 went from <20MB to >40MB --
MS> is this a * by memory manufacturers?

        It may just be mapped video memory :)

--
C:>WIN                                          |     Directable Mirrors
The computer obeys and wins.                    |A Better Way To Focus The Sun
You lose and Bill collects.                     |  licenses available - see:
                                                |   http://www.veryComputer.com/

 
 
 

XFree86-4.2.0_1,1 Config failure -- for ATI Mach 64 Rage Pro 8MB

Post by Michael Sierchi » Mon, 24 Jun 2002 08:18:51



> On Fri, 21 Jun 2002 07:47:06 -0700

> MS> Switching both was required -- though XFree86 went from <20MB to >40MB --
> MS> is this a * by memory manufacturers?

>    It may just be mapped video memory :)

Doh!
 
 
 

XFree86-4.2.0_1,1 Config failure -- for ATI Mach 64 Rage Pro 8MB

Post by Michael Sierchi » Wed, 26 Jun 2002 08:54:42


Erik et alia -

I don't know if you noticed my later post on this matter, but
I managed to get this working for the ATI Rage Pro with the 4.2.0
version of the drivers, by adding Option "NoCompositeSync" to
the "Device" section of the config file.