Linux PARISC architecture development
 help / color / mirror / Atom feed
From: j.raspe@t-online.de (Johannes Raspe)
To: Helge Deller <deller@gmx.de>
Cc: ajwalker@broadpark.no, parisc-linux@lists.parisc-linux.org
Subject: Re: Fwd: Re: [parisc-linux] Re: STI crash on B132L with HCRX-24
Date: Sun, 31 Oct 2004 10:10:47 +0100	[thread overview]
Message-ID: <200410311010.47849.j.raspe@t-online.de> (raw)
In-Reply-To: <200410300125.12145.deller@gmx.de>

Hi Helge,

> Hi Johannes,
>
> On Friday 29 October 2004 22:28, Johannes Raspe wrote:
> > I just noticed that I lost my text-console. Don't know if this is the
> > patched stifb.c (I cant' check either :-)).
>
> I don't think so.

I had a strang idea about the text-consoles and it was right: The consoles are 
present, but they are black text on black background.
I can type in commands blindly and they are executed, but I don't see them. So 
it seems to be a minor problem with your patch I think. Somehow the colors 
got screwed up in textmode.

> > The getty processes are started on tty1  to tty6, but switching to those
> > consoles with "CTRL+ALT+F1-6" only gives a  black screen.
>
> Just tested and this works for me on 8bpp with Artist-gfx on a 715/64.
>
> > After switching system-console to graphics there are no bootmessages, I
> > have to switch back to serial console to see them.
> > X-Server still is working fine.
> >
> > Any suggestions?
>
> Do you still boot via serial console or is the cable still connected ?
> If yes, please stop at the IPL and delete the line "console=ttyS0", which
> is auto-appended by palo if you boot from serial console.

No, I changed the path to graphics in boot admin.

> You wrote in another mail:
> > The hppa "boot-penguin" looks a little bit psychedlic...
>
> could you describe this more exactly. Does the colors seem exchanged (e.g.
> red is blue and vice-versa) ?

The background of the penguin is green where it should be black. This is the  
obvious change. The rest just looks weird. If it helps I could make a picture 
of it.

> Helge

Regards Johannes

-- 
Johannes Raspe - j.raspe@t-online.de
GnuPG-Key ID: D342E105
Fingerprint: D681 F800 FB2D 913E D14C 1F17 C3DB B1F1 D342 E105

  reply	other threads:[~2004-10-31  9:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-29 20:28 Fwd: Re: [parisc-linux] Re: STI crash on B132L with HCRX-24 Johannes Raspe
2004-10-29 23:25 ` Helge Deller
2004-10-31  9:10   ` Johannes Raspe [this message]
2004-10-31 12:12     ` Helge Deller
2004-10-31 13:06       ` Johannes Raspe
2004-10-31 13:56         ` Penguin color problems on HCRX-24 (was: [parisc-linux] Re: STI crash on B132L with HCRX-24) Helge Deller
2004-10-31 14:06           ` Johannes Raspe
2004-10-31 22:20             ` Penguin color problems on HCRX-24 Andy Walker
2004-11-01 12:45               ` [parisc-linux] " Helge Deller
2004-11-01 14:03                 ` Andy Walker
2004-11-01 17:21                   ` [parisc-linux] " Helge Deller
2004-10-31 23:09           ` Penguin color problems on HCRX-24 (was: [parisc-linux] Re: STI crash on B132L with HCRX-24) Andy Walker

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=200410311010.47849.j.raspe@t-online.de \
    --to=j.raspe@t-online.de \
    --cc=ajwalker@broadpark.no \
    --cc=deller@gmx.de \
    --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