From: Stuart Brady <sdbrady@ntlworld.com>
To: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] No 2.6 kernel on 735/125 with CRX24?
Date: Sat, 2 Oct 2004 23:03:35 +0100 [thread overview]
Message-ID: <20041002220334.GA24389@ntlworld.com> (raw)
In-Reply-To: <200409241533.15399.j.raspe@t-online.de>
On Fri, Sep 24, 2004 at 03:33:15PM +0200, Johannes Raspe wrote:
> I tried the "official" 2.6.8 Debian-image and 2.6.8.1-pa11-image but none
> worked.
> After booting, the message "if this is the last..." about graphic and
> serial-console is printed and after that (I suppose when the kernel tries to
> initialize the framebuffer) the screen turns blue, no HDD-activity anymore,
> the system hangs.
> As far as I can see no other messages.
> With 2.4.27-pa4 everything is fine.
[snip]
I have no idea how stifb works, but perhaps this is the same problem:
http://lists.parisc-linux.org/pipermail/parisc-linux/2004-March/022600.html
Does passing "stifb=bpp:8" on the palo command-line make any difference?
Perhaps the 32 bpp code is broken? I can't find any other dmesgs posted
to the list with stifb using 32 bpp...
--
Stuart Brady
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next prev parent reply other threads:[~2004-10-02 22:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-24 13:33 [parisc-linux] No 2.6 kernel on 735/125 with CRX24? Johannes Raspe
[not found] ` <200409261719.31774.j.raspe@t-online.de>
[not found] ` <4156F0FE.2010301@tiscali.be>
2004-09-27 16:28 ` Johannes Raspe
2004-09-27 17:13 ` Joel Soete
2004-09-27 19:10 ` Johannes Raspe
2004-09-28 5:34 ` Joel Soete
2004-09-28 11:45 ` j.raspe
2004-10-02 22:03 ` Stuart Brady [this message]
2004-10-03 11:51 ` Johannes Raspe
-- strict thread matches above, loose matches on Subject: below --
2004-09-29 13:07 Joel Soete
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=20041002220334.GA24389@ntlworld.com \
--to=sdbrady@ntlworld.com \
--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