linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: Frans Pop <aragorn@tiscali.nl>, adaplas@pol.net
Cc: debian-sparc@lists.debian.org, sparclinux@vger.kernel.org,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [atyfb] No display on Sparc Ultra 10 with kernel 2.6.10-rc2 or later
Date: Tue, 15 Feb 2005 07:40:58 +0800	[thread overview]
Message-ID: <200502150741.01702.adaplas@hotpop.com> (raw)
In-Reply-To: <200502141855.29202.aragorn@tiscali.nl>

On Tuesday 15 February 2005 01:55, Frans Pop wrote:
> Hello Tony,
>
> Thanks for your reaction.
>
> On Monday 14 February 2005 17:59, Antonino A. Daplas wrote:
> > The above timings are screwed.  This is 1024x768 at 85Hz INTERLACED.
> > The fb_find_mode() function picked up this mode when you specified
> > 1024x768@75, since there is no such mode in the mode database.
> > And the atyfb driver accepted the mode without differentiating between
> > interlaced and non-interlaced.
>
> Right. I tried with 1024x768@70 and that gives some improvement.
> For a very, very short time I see the Linux logo and some boot messages
> flash on the display, but then the monitor still goes into suspend.
>
> It really is just a flash, but I think I see some of the atyfb debug
> messages. That would indicate that the suspend is activated somewhere near
> the end of console initialization (maybe at the "switching to colour frame
> buffer device 128x48"?). But again, this is based on an impression.
>
> So it seems there are two bugs:
> - missing/incorrect default mode settings for sparc in the driver;
> - incorrect activation of suspend.

Try editing drivers/video/console/fbcon.c, look for the function
fbcon_startup(). After the line 'ops->currcon = -1;', insert this line:

ops->blank_state = -1;

Also, try changing the graphics state such as doing an
fbset -depth 16 or the like.

What happens if you switch consoles?

You can also try commenting out .fb_blank = atyfb_blank from
static struct fb_ops atyfb_ops and disable CONFIG_PM from your kernel
config.

>
> > PS:  There was also a massive atyfb update between 2.6.10-rc1 and rc2.
> > Here's the changelog:
>
> How best to proceed? Can you help?

I'll CC fbdev-devel list.

>
> Cheers,
> Frans Pop

Tony

>
>
> For comparison, here are the relevant lines from kern.log when
> booting with a Debian 2.6.8 kernel:
> atyfb: 3D RAGE (GT) [0x4754 rev 0x9a] 2M SGRAM, 14.31818 MHz XTAL, 200 MHz
> PLL, 67 Mhz MCLK fb0: ATY Mach64 frame buffer device on PCI
> Console: switching to mono PROM 80x34
> Console: switching to colour frame buffer device 144x56
>
> And here the lines from 2.6.10-rc2 with video=atyfb:1024x768@70:
> atyfb: 3D RAGE (Mach64 GT) [0x4754 rev 0x02]
> atyfb: 2M SGRAM (1:1), 14.31818 MHz XTAL, 200 MHz PLL, 67 Mhz MCLK, 67 MHz
> XCLK atyfb: setting up CRTC
> atyfb: set primary CRT to 1024x768 NN composite N
> atyfb: CRTC_H_TOTAL_DISP: 7f00a5
> atyfb: CRTC_H_SYNC_STRT_WID: 310082
> atyfb: CRTC_V_TOTAL_DISP: 2ff0325
> atyfb: CRTC_V_SYNC_STRT_WID: 260302
> atyfb: CRTC_OFF_PITCH: 20000000
> atyfb: CRTC_VLINE_CRNT_VLINE: 0
> atyfb: CRTC_GEN_CNTL: b000200
> atyfb: atyfb_set_par
> atyfb:  Set Visible Mode to 1024x768-8
> atyfb:  Virtual resolution 1024x2016, pixclock_in_ps 13373 (calculated
> 13373) atyfb:  Dot clock:           74 MHz
> atyfb:  Horizontal sync:     56 kHz
> atyfb:  Vertical refresh:    69 Hz
> atyfb:  x  style: 74.10398 1024 1048 1184 1328   768 771 777 806
> atyfb:  fb style: 13373  144 1024 24 136 29 768 3 6
> debug atyfb: Mach64 non-shadow register values:
> debug atyfb: 0x2000:  007F00A5 00310082 02FF0325 00260302
> debug atyfb: 0x2010:  01AA0000 20000000 08000020 0B000200
> debug atyfb: 0x2020:  00380727 0120051B 00000000 00000000
> debug atyfb: 0x2030:  00000000 00000031 00000000 00000000
> debug atyfb: 0x2040:  00000000 00000000 00000000 00000000
> debug atyfb: 0x2050:  00000000 00000000 00000000 00000000
> debug atyfb: 0x2060:  00000000 AAAAAA0F 00000000 00000000
> debug atyfb: 0x2070:  00000000 00000000 00003020 00000000
> debug atyfb: 0x2080:  00000000 00000000 00000000 00000000
> debug atyfb: 0x2090:  00A63000 00000000 00000000 00000000
> debug atyfb: 0x20A0:  7B23A040 00000000 00000000 05000001
> debug atyfb: 0x20B0:  004210B3 00010000 00010000 00000000
> debug atyfb: 0x20C0:  00FF0000 86010182 00000000 00000000
> debug atyfb: 0x20D0:  00000100 00000000 00000000 00003842
> debug atyfb: 0x20E0:  9A004754 0000001D 00000000 00000000
> debug atyfb: 0x20F0:  00000000 00008E0D E17FFCF8 00000000
>
> debug atyfb: Mach64 PLL register values:
> debug atyfb: 0x00:  CDD52414 A80341BC 8E82E701 A61B0000
> debug atyfb: 0x10:  CDD52414 A80341BC 8E82E701 A61B0000
> debug atyfb: 0x20:  CDD52414 A80341BC 8E82E701 A61B0000
> debug atyfb: 0x30:  CDD52414 A80341BC 8E82E701 A61B0000
>
> Console: switching to colour frame buffer device 128x48
> atyfb: fb0: ATY Mach64 frame buffer device on PCI




       reply	other threads:[~2005-02-14 23:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200502140251.00645.aragorn@tiscali.nl>
     [not found] ` <200502150059.12789.adaplas@hotpop.com>
     [not found]   ` <200502141855.29202.aragorn@tiscali.nl>
2005-02-14 23:40     ` Antonino A. Daplas [this message]
2005-02-15  0:31       ` [atyfb] No display on Sparc Ultra 10 with kernel 2.6.10-rc2 or later David S. Miller
2005-02-15  6:22       ` Frans Pop
2005-02-15 10:03         ` [Linux-fbdev-devel] " Geert Uytterhoeven
2005-02-15 12:10         ` Antonino A. Daplas
2005-02-15 16:49           ` David S. Miller
2005-02-16  2:27             ` Frans Pop
2005-02-16  3:20               ` David S. Miller
2005-02-16 11:30                 ` Antonino A. Daplas
2005-02-16  2:27           ` Frans Pop
2005-02-16 11:27             ` Antonino A. Daplas
2005-02-16 15:51               ` David S. Miller
2005-02-16 22:10                 ` Frans Pop
2005-02-16 23:02                   ` Antonino A. Daplas
2005-02-16 23:18                     ` [Linux-fbdev-devel] " Antonino A. Daplas
2005-02-16 23:24                     ` Antonino A. Daplas
2005-02-17 14:16                       ` Frans Pop
2005-02-17 21:30                         ` Antonino A. Daplas

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=200502150741.01702.adaplas@hotpop.com \
    --to=adaplas@hotpop.com \
    --cc=adaplas@pol.net \
    --cc=aragorn@tiscali.nl \
    --cc=debian-sparc@lists.debian.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=sparclinux@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;
as well as URLs for NNTP newsgroup(s).