Re: [XFree86] problem on powermac G4 dualie

2003-01-25 Thread Fred Heitkamp
On Mon, 13 Jan 2003, Daniel Stone wrote:

 On Sun, Jan 12, 2003 at 06:35:54PM -0500, Fred Heitkamp scrawled:
  I have a powermac G4 dual 533 snakebite with GForce 2MX. I am using Linux
  pmac 2.4.21-pre2 #2 SMP Thu Jan 2 07:32:33 EST 2003 ppc unknown.  The last
  couple CVS compiles of XFree with gcc (GCC) 3.2.2 20021212 (Debian
  prerelease) just cause one CPU to be used up.  The screen just goes black
  and there is no X Window.
  XFree86 Version 4.2.99.3 / X Window System
  (protocol Version 11, revision 0, vendor release 6600)
  Release Date: 6 January 2003
 
  X Applications run remotely seem to work though.
 
  Anyone else had this or similar problem?

 If you have a flat panel display, you need 'Option FlatPanel'.

That didn't help.  Here is a excerpt from the log file.  I can't
see anything wrong.

(II) NV(0): Not using default mode 320x240 (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode 320x240 (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode 320x240 (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode 320x240 (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode 400x300 (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode 400x300 (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode 400x300 (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode 400x300 (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode 400x300 (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode 1024x768 (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode 512x384 (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode 512x384 (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode 512x384 (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode 512x384 (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode 512x384 (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode 576x432 (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode 640x480 (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode 640x480 (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode 640x512 (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode 640x512 (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode 1280x1024 (hsync out of range)
(II) NV(0): Not using default mode 640x512 (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode 800x600 (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode 800x600 (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode 1600x1200 (hsync out of range)
(II) NV(0): Not using default mode 800x600 (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode 1600x1200 (hsync out of range)
(II) NV(0): Not using default mode 800x600 (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode 1600x1200 (hsync out of range)
(II) NV(0): Not using default mode 800x600 (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode 896x672 (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode 1792x1344 (hsync out of range)
(II) NV(0): Not using default mode 896x672 (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode 928x696 (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode 1856x1392 (hsync out of range)
(II) NV(0): Not using default mode 928x696 (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode 1920x1440 (hsync out of range)
(II) NV(0): Not using default mode 960x720 (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode 1920x1440 (hsync out of range)
(II) NV(0): Not using default mode 960x720 (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode 416x312 (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode 576x384 (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode 700x525 (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode 700x525 (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode 800x512 (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode 1920x1440 (hsync out of range)
(II) NV(0): Not using default mode 960x720 (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode 2048x1536 (hsync out of range)
(II) NV(0): Not using default mode 1024x768 (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode 2048x1536 (hsync out of range)
(II) NV(0): Not using default mode 1024x768 (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode 2048x1536 (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode 1024x768 (bad mode clock/interlace/doublescan)
(II) NV(0): Not using default mode 1856x1392 

[XFree86] problem on powermac G4 dualie

2003-01-12 Thread Fred Heitkamp
I have a powermac G4 dual 533 snakebite with GForce 2MX. I am using Linux
pmac 2.4.21-pre2 #2 SMP Thu Jan 2 07:32:33 EST 2003 ppc unknown.  The last
couple CVS compiles of XFree with gcc (GCC) 3.2.2 20021212 (Debian
prerelease) just cause one CPU to be used up.  The screen just goes black
and there is no X Window.
XFree86 Version 4.2.99.3 / X Window System
(protocol Version 11, revision 0, vendor release 6600)
Release Date: 6 January 2003

X Applications run remotely seem to work though.

Anyone else had this or similar problem?

Fred


___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86



Re: [XFree86] problem on powermac G4 dualie

2003-01-12 Thread Daniel Stone
On Sun, Jan 12, 2003 at 06:35:54PM -0500, Fred Heitkamp scrawled:
 I have a powermac G4 dual 533 snakebite with GForce 2MX. I am using Linux
 pmac 2.4.21-pre2 #2 SMP Thu Jan 2 07:32:33 EST 2003 ppc unknown.  The last
 couple CVS compiles of XFree with gcc (GCC) 3.2.2 20021212 (Debian
 prerelease) just cause one CPU to be used up.  The screen just goes black
 and there is no X Window.
 XFree86 Version 4.2.99.3 / X Window System
 (protocol Version 11, revision 0, vendor release 6600)
 Release Date: 6 January 2003
 
 X Applications run remotely seem to work though.
 
 Anyone else had this or similar problem?

If you have a flat panel display, you need 'Option FlatPanel'.

-- 
Daniel Stone [EMAIL PROTECTED]
Developer, Trinity College, University of Melbourne



msg00160/pgp0.pgp
Description: PGP signature