All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Carlos O'Donell Jr." <carlos@baldric.uwo.ca>
To: John Newbigin <jnewbigin@it.swin.edu.au>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] STI problem on 715/50 with new kernels
Date: Sun, 2 Jun 2002 19:16:02 -0400	[thread overview]
Message-ID: <20020602191602.A1819@systemhalted> (raw)
In-Reply-To: <Pine.LNX.4.44.0206021923310.11687-100000@mars.it.swin.edu.au>; from jnewbigin@it.swin.edu.au on Sun, Jun 02, 2002 at 07:30:55PM +1000

> I have an Appolo 715/50 with debian installed on it.  I have upgraded to 
> the 2.4.18 kernel but when the kernel boots, the STI display goes blank.  
> Everything works except I can't see the image.  When I press reset, the 
> firmware comes up and I can see the output from the linux kernel on the 
> screen still.
> 
> If someone can help it would be much appreciated.  The 2.4.9 kernel has 
> some kind of problem with the framebuffer so I can't run X.
> 
> John.
>

I would recommend getting the latest kernel source from 
cvs.paris-linux.org and compiling a new kernel with STI 
fbdev enabled. 

http://cvs.parisc-linux.org/

Make sure that the following is in your ~/.cvsrc
cvs -z3 -q
diff -uNp
update -Pd
remove -f

And then...

export  CVSROOT=:pserver:anonymous@cvs.parisc-linux.org:/var/cvs  
cvs co linux palo
cd linux
make oldconfig 
make menuconfig (enable fbdev and all the goodies you need)
... munge ./palo/Makefile for any custom parameters to your kernel
make dep
make palo

Then boot ./palo/lifimage :)

c.

      reply	other threads:[~2002-06-02 23:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-02  9:30 [parisc-linux] STI problem on 715/50 with new kernels John Newbigin
2002-06-02 23:16 ` Carlos O'Donell Jr. [this message]

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=20020602191602.A1819@systemhalted \
    --to=carlos@baldric.uwo.ca \
    --cc=jnewbigin@it.swin.edu.au \
    --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 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.