Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] X startup failure
Date: Tue, 27 Dec 2005 23:38:10 +0100	[thread overview]
Message-ID: <200512272338.10264.deller@gmx.de> (raw)
In-Reply-To: <200512271437.jBREbxA8021653@hiauly1.hia.nrc.ca>

Hi Dave,

On Tuesday 27 December 2005 15:37, John David Anglin wrote:
> > On Monday 26 December 2005 22:34, John David Anglin wrote:
> > > X no longer starts on my c3k using unstable.  The problem seems
> > > to be:
> > > 
> > > (EE) FBDEV(0): FBIOPAN_DISPLAY: Invalid argument

This message has always been here.

> > > XF86Config-4 hasn't changed for at least a year.  Any ideas?
> > 
> > I assume your screen resolution changed. 
> 
> No.  I've had the following entries in XF86Config-4 since Sep 2003:
> 
> Section "Device"
>         Identifier      "HP Visualize-EG"
> 	Driver          "fbdev"
> 	Option          "UseFBDev"              "true"
> EndSection
> 
> Section "Monitor"
> 	Identifier      "NEC LCD1980SX"
> 	HorizSync       30-107
> 	VertRefresh     50-85
> 	Option          "DPMS"
> EndSection
> 
> Section "Screen"
> 	Identifier      "Default Screen"
> 	Device          "HP Visualize-EG"
> 	Monitor         "NEC LCD1980SX"
> 	DefaultDepth    8
> 	SubSection "Display"
> 		Depth           8
> 		Modes           "1280x1024"
> 	EndSubSection
> EndSection

Ok.

> > Maybe new monitor/setup or different graphic card is detected first ?
> 
> Possibly, the machine has two graphics cards.  However, the presence of
> the A1262A never caused a problem before:
> 
> STI GSC/PCI core graphics driver Version 0.9a
> STI PCI graphic ROM found at f6000000 (64 kB), fb at f8000000 (32 MB)
>     id 2d08c0a7-9a02587, conforms to spec rev. 8.0a
>     graphics card name: PCI_GRAFFITIX1280
> STI PCI graphic ROM found at f7000000 (2048 kB), fb at fa000000 (32 MB)
>     id 35acda30-9a02587, conforms to spec rev. 8.0d
>     graphics card name: A1262A
> sticon: Initializing STI text console.
> Console: switching to colour STI console 160x64
> Console: switching to colour frame buffer device 160x64
> fb0: stifb 1280x1024-8 frame buffer device, PCI_GRAFFITIX1280, id: 2d08c0a7, mmio: 0xf8100000
> stifb: 'A1262A' (id: 0x35acda30) not supported.


yep. neither..


> > Try fbset to get the current screen resolution.
> 
> mode "1280x1024"
>     geometry 1280 1024 1280 1024 8
>     timings 0 0 0 0 0 0 0
>     rgba 8/0,8/0,8/0,0/0
> endmode
> 
> From the above, it looks like the timings aren't beeing set.

They are always 0 for fb-devices.

I tried myself with current kernel.

- 32bit kernel on c3k works for me. Can you try again with current kernel ?

- 64bit kernel on my c3k crashes, but this doesn't seem (with strace) related to stifb. Maybe this is due to some mmap() problems ?

Sorry, no better idea...

Helge
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

  reply	other threads:[~2005-12-27 22:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-26 21:34 [parisc-linux] X startup failure John David Anglin
2005-12-27  7:29 ` Helge Deller
2005-12-27 14:37   ` John David Anglin
2005-12-27 22:38     ` Helge Deller [this message]
2005-12-28  1:22       ` [parisc-linux] X startup failure / PS/2 mouse failure Jean-Pierre HOFER
2005-12-28 21:19         ` Helge Deller
2005-12-28 21:46       ` [parisc-linux] X startup failure John David Anglin
2005-12-28 22:31         ` Kyle McMartin
2005-12-28 23:01           ` John David Anglin
2005-12-28 23:19             ` Michael S. Zick
2005-12-28 23:28               ` John David Anglin
2005-12-29 10:12     ` Joel Soete
2005-12-29 15:41       ` John David Anglin
2005-12-29 17:59         ` John David Anglin

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=200512272338.10264.deller@gmx.de \
    --to=deller@gmx.de \
    --cc=dave@hiauly1.hia.nrc.ca \
    --cc=parisc-linux@lists.parisc-linux.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