All of lore.kernel.org
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Karsten Merker <karsten@excalibur.cologne.de>,
	parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] configuration problems with cvs from 20001216 15:40 CET
Date: Wed, 20 Dec 2000 01:00:16 +0100	[thread overview]
Message-ID: <00122000445401.00303@P100> (raw)
In-Reply-To: <20001218230325.A934@excalibur.cologne.de>

On Monday 18 December 2000 23:03, Karsten Merker wrote:
> On Sun, Dec 17, 2000 at 09:20:51PM +0100, Helge Deller wrote:
> > > $CONFIG_FB_STI is set to "y" as can be seen in .config, nonetheless
> > > CONFIG_FBCON_STI is not declared.
[snip]
> I had activated "Console drivers -> Frame buffer support -> Advanced low
> level driver options", and whenever this is selected, CONFIG_FBCON_STI is
> not defined. If I unselect it, everything is ok. 
[snip]

Ok, thanks a lot for your investigation. I hadn't realized that and since 
most of the developers use the default config, this problem has not shown up 
yet. 

> Has anybody tried to run Linux with serial console on a 715/100? When I
> boot a kernel without support for STICON but with serial console enabled
> (and console=ttyS0 as commandline parameter) the system crashes just after
> displaying the "kernel command line" (system console is still in
> "graphics" mode - does this make a difference?).

This doesn't happen on my 715/64, which is afaik nearly the same machine as 
yours. And, you don't need "console=ttyS0", but I don't think, that this is 
related to your problem.

> When using STICON instead, the console output works in principle, but
> there is pixel garbage throughout the screen (it looks like it is between
> the character cells) after the second "mode switch" (when the first line
> on the screen is "Console: switching to colour STI console 160x64"). I
> have seen a similar effect on a 712/80 when using STICON. 

Yes, this is a known problem - it happens here too -, but since some of the 
developers currently work on better STI-support this will get fixed in the 
future - and I think this problem was not there, before we merged with linus.

> The keyboard
> works on the 712/80 but is dead on the 715/100 (in both cases the keyboard
> is a ps/2 model, connected directly on the 712/80 and via the small
> external adaptor box on the 715/100).

Hmm, does the other end of this external adaptor on the /100 looks like a 
RJ45-connector? If yes, I assume, that you have a PS/2 keyboard on a 
HIL-adaptor and need the HIL keyboard driver, which should already be enabled 
in defconfig. And the HIL keyboard works for me...
If you could send me your bootlog I could take a closer look at it.

Greetings,

	Helge

  reply	other threads:[~2000-12-19 23:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-17 10:51 [parisc-linux] configuration problems with cvs from 20001216 15:40 CET Karsten Merker
2000-12-17 20:20 ` Helge Deller
2000-12-18 22:03   ` Karsten Merker
2000-12-20  0:00     ` Helge Deller [this message]
2000-12-21 22:39       ` Karsten Merker
2000-12-22 13:30         ` Matthew Wilcox
2000-12-22 16:01           ` Alex deVries
2000-12-22 23:10             ` Matthew Wilcox

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=00122000445401.00303@P100 \
    --to=deller@gmx.de \
    --cc=karsten@excalibur.cologne.de \
    --cc=parisc-linux@thepuffingroup.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.