linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Jahns <Thomas.Jahns@epost.de>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Mach64 GX driver problems in post 2.4.22 kernels
Date: Sat, 5 Jun 2004 20:56:47 +0200	[thread overview]
Message-ID: <20040605185647.GG5668@mercury.jahnsnet.de> (raw)

Hi,

I have the following problem when I try to build a new kernel for my  
PowerMac 7500 (604e CPU, PCI adapters: Adaptec 2940UW SCSI, Apple  
Mach64 GX card):

Kernel versions newer than my last build (of 2.4.22 plus preempt, benh,  
lowlatency, ea+acl+nfsacl, cryptoloop patches, all from debian sid  
source packages of that time) show a blank screen when switching to the  
Mach64 framebuffer (BootX pre-boot messages are fine). The kernel  
continues to boot and even activates the atyfb driver so I can login  
blind on the console or remotely via ssh.

I have so far built the following kernels: 2.4.25 from debian package  
kernel-source-2.4.25_2.4.25-3, with and without the debian kernel- 
patch-2.4.25-powerpc patch derived from Benjamin Herrenschmidt's source  
tree, a kernel from each of www.kernel.org 2.4.26 and 2.4.25 archives  
(without any patches) and a downloaded kernel from Benjamin's site  
directly (rsync'ed on 2004/06/01, ca. 16:30). All of these builds show  
the behaviour outlined above: kernel boots fine but screen blanks  
immediatly.

As Mach64 is obviously quite important to a number of PowerMacs I hope  
someone already stumbled across the same problem, although I couldn't  
find anything truely specific by googling.

Please tell if you need any more specific logs or info, I'll include  
the dmesg lines and lspci -v output relevant to the card for a start:

> dmesg | grep -i \(aty\|console\)
Kernel command line: root=/dev/sda7 video=atyfb:vmode:18:cmode:8  
panic=60
Console: colour dummy device 80x25
atyfb: mach64GX (ATI888GX00) [0x00d7 rev 0x03] 4M VRAM, 14.31818 MHz  
XTAL, 135
MHz PLL, 50 Mhz MCLK
Console: switching to colour frame buffer device 144x54
fb0: ATY Mach64 frame buffer device on PCI
MacOS display is /bandit/ATY,mach64

I noticed one of these lines reads differently on my 2.4.22 kernel:

atyfb: mach64GX (ATI888GX00) [0x00d7 rev 0x03] 4M VRAM, 14.31818 MHz
XTAL, 135 MHz PLL, 50 Mhz MCLK
                   ^^^^^^^^^^^
Would that be a sign of the culprit?

> lspci -v -s 00:0f.0
0000:00:0f.0 VGA compatible controller: ATI Technologies Inc 210888GX  
[Mach64
GX] (rev 03) (prog-if 00 [VGA])
       Flags: stepping, medium devsel, IRQ 25
       Memory at 81000000 (32-bit, non-prefetchable) [size=16M]
       Expansion ROM at <unassigned> [disabled] [size=64K]



Thanks for any input you can provide with respect to my problem.

Ciao, Thomas Jahns
-- 
"Computers are good at following instructions,
 but not at reading your mind."
D. E. Knuth, The TeXbook, Addison-Wesley 1984, 1986, 1996, p. 9


-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the one
installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504

             reply	other threads:[~2004-06-05 18:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-05 18:56 Thomas Jahns [this message]
2004-06-06 10:45 ` Mach64 GX driver problems in post 2.4.22 kernels Thomas Jahns
2004-06-18  9:48   ` Thomas Jahns
2004-06-21  8:08     ` David Eger
2004-06-21  8:52       ` Geert Uytterhoeven
2004-06-24 20:37       ` Thomas Jahns
2004-06-23 18:31     ` David Eger
2004-06-24 21:20       ` Thomas Jahns

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040605185647.GG5668@mercury.jahnsnet.de \
    --to=thomas.jahns@epost.de \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).