From: Sven Luther <sven.luther@wanadoo.fr>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
debian-powerpc@lists.debian.org, debian-boot@lists.debian.org
Cc: Chris Tillman <toff1@cox.net>,
Sven Luther <sven.luther@wanadoo.fr>,
Linux Frame Buffer Device Development
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Mach64Gx not working on pmac 9500 (Was : tdfx & multiple voodoo cards : supposed to work ? + Mach64Gx question.)
Date: Thu, 30 Oct 2003 10:56:20 +0100 [thread overview]
Message-ID: <20031030095620.GA5088@iliana> (raw)
In-Reply-To: <Pine.GSO.4.21.0310301031110.15545-100000@waterleaf.sonytel.be>
Ok.
Chris, can you have a look at this, and see if can provide this
information, by using a serial console, or maybe blindly typing :
# dmesg >somplace
and also by visual confirmation ?
Friendly,
Sven Luther
On Thu, Oct 30, 2003 at 10:38:45AM +0100, Geert Uytterhoeven wrote:
> On Thu, 30 Oct 2003, Sven Luther wrote:
> > BTW, i had had reports from Chris Tillman about what seems an fbdev
> > failure on his 9500 powermac with 2.4.22 kernels. The pci greaphic cards
> > declares to be a Mach64GX, and lspci gives :
> >
> > 00:0b.0 Host bridge: Apple Computer Inc. Bandit PowerPC host bridge (rev 02)
> > 00:0f.0 VGA comppatible controller: ATI Technolgies Inc 210888GX [Mach64 GX] (rev 02)
> > 00:10.0 Class ff00: Apple Computer Inc. Grand Central I/O (rev 02)
> >
> > 00:0f.0 Class 0300: 1002:4758 (rev 02)
> > Flags: stepping, medium devsel, IRQ 25
> > Memory at 81000000 (32-bit, non-prefetchable)
> >
> > Any idea on what is going on here (the kernel works, but there is no
> > video output).
>
> Mach64 GX is difficult to handle, since it needs an external clockchip and
> RAMDAC, unlike the later variants.
>
> The first thing to know is which external clockchip and RAMDAC are used on this
> particular board? Atyfb should print it during initialization, but it's better
> to do a visual verification on the board, too.
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
>
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
next prev parent reply other threads:[~2003-10-30 9:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-29 9:36 tdfx & multiple voodoo cards : supposed to work ? Sven Luther
2003-10-29 18:25 ` Kronos
2003-10-29 19:56 ` Sven Luther
2003-10-29 20:25 ` Kronos
2003-10-29 22:19 ` James Simmons
2003-10-30 6:49 ` tdfx & multiple voodoo cards : supposed to work ? + Mach64Gx question Sven Luther
2003-10-30 9:38 ` Geert Uytterhoeven
2003-10-30 9:56 ` Sven Luther [this message]
2003-10-30 18:27 ` James Simmons
2003-10-30 18:31 ` Sven Luther
2003-10-30 18:45 ` James Simmons
2003-10-30 20:47 ` Geert Uytterhoeven
2003-10-30 20:31 ` Geert Uytterhoeven
2003-10-29 20:04 ` tdfx & multiple voodoo cards : supposed to work ? James Simmons
2003-10-30 9:15 ` Sven Luther
2003-10-30 11:32 ` Sven Luther
2003-10-30 18:27 ` James Simmons
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=20031030095620.GA5088@iliana \
--to=sven.luther@wanadoo.fr \
--cc=debian-boot@lists.debian.org \
--cc=debian-powerpc@lists.debian.org \
--cc=geert@linux-m68k.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=toff1@cox.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).