public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: John Mock <kd6pag@qsl.net>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.10-rc2 on VAIO laptop and PowerMac 8500/G3
Date: Fri, 19 Nov 2004 10:17:02 +1100	[thread overview]
Message-ID: <1100819822.25520.8.camel@gaston> (raw)
In-Reply-To: <E1CUv66-0000HA-00@penngrove.fdns.net>


> The PowerMac 8500/G3 does not come up at all.  Upgrading to 2.6.10-rc2-bk1
> fixed a couple of minor PPC problems, but it's still failing.  I can't see
> what's going on because it appears that the video parameters don't match
> the framebuffer geometry and almost everything is black with a few thin 
> diagonal lines of dots and dashes (which don't look like morse code...).  
> I have not mananged to get serial console to work on this machine, so i'm
> rather clueless.  So all i can offer is the .config for it (see below).  
> I tried to regress this problem and it seems to have appeared somewhere 
> between 2.6.8 and 2.6.9-rc1.
> 
> It does seem to be specific to CONFIG_FB_CONTROL, as if CONFIG_FB_OF is set
> instead, the PowerMac will boot OK, but all that will appear on the screen
> until 'xdm' is started is a cute penguin.  The nearly-blank screen with 
> CONFIG_FB_OF only set goes back at least until 2.6.3, after which i lost
> patience chasing the problem down.

You lack CONFIG_FRAMEBUFFER_CONSOLE maybe ? You should use the
pmac_defconfig ... Now, if controlfb still doesn't work, then I'll have
to dig out my old 8500, it's possible that the recent changes to the
fbdev layer broke some of those old drivers.

As for serial, check out CONFIG_SERIAL_PMACZILOG and
CONFIG_SERIAL_PMACZILOG_CONSOLE.

> In addition, to that on the PowerMac, when things are running normally
> (under 2.6.8 for example), switching to a virtual console from X windows 
> causes the vertical refresh rate to be set to about 47Hz, i.e. the screen
> loses sync.  It can be fixed (until X windows is visited again) using 'ssh' 
> from another machine and doing a 'fbset' with the correct vertical sync
> rate.  That problem has been with me for quite awhile.

Yes, that is due to the 2.6 changes in fbdev/fbcon, the loss of the per
VT mode data structure, the driver is now sort-of supposed to re-invent
a mode based on bogus stuff sent by fbcon on console switch. I don't
like it much, but I suppose I'll have to fix controlfb (and platinumfb
etc...).



  reply	other threads:[~2004-11-18 23:25 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-18 22:49 2.6.10-rc2 on VAIO laptop and PowerMac 8500/G3 John Mock
2004-11-18 23:17 ` Benjamin Herrenschmidt [this message]
2004-11-19 11:49 ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2004-11-19  1:05 John Mock
2004-11-19  2:26 ` Benjamin Herrenschmidt
2004-11-20 16:58 John Mock
2004-11-20 18:51 ` Pavel Machek
2004-11-20 19:11   ` Lee Revell
2004-11-22 11:58     ` Takashi Iwai
2004-11-30  0:35   ` Andrew Morton
2004-11-30 10:22     ` Pavel Machek
2004-12-02  8:51 John Mock
2004-12-02 10:25 ` Pavel Machek
2004-12-02 14:48 ` Russell King
2004-12-13 10:13   ` Russell King
2004-12-02 17:49 John Mock
2004-12-02 19:10 ` Andrew Morton
2004-12-02 19:24 Tovar

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=1100819822.25520.8.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=kd6pag@qsl.net \
    --cc=linux-kernel@vger.kernel.org \
    /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