linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Helge Hafting <helgehaf@aitel.hist.no>
To: James Simmons <jsimmons@infradead.org>,
	linux-fbdev-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: Fbdev 2.5.49 BK fixes.
Date: Wed, 27 Nov 2002 12:04:47 +0100	[thread overview]
Message-ID: <3DE4A6CF.F62CFF41@aitel.hist.no> (raw)
In-Reply-To: Pine.LNX.4.44.0211262306070.30451-100000@phoenix.infradead.org

James Simmons wrote:

> Perfect. I found the problem and I'm about to commit to BK. I posted the
> latest patch against 2.5.49 at
> 
> http://phoenix.infradead.org/~jsimmons/fbdev.diff.gz

I tried this patch, but it crashed during boot.

I have a 
01:00.0 VGA compatible controller: ATI Technologies Inc 3D Rage Pro AGP
1X/2X (rev 5c)

and use this in lilo.conf:
image=/boot/2.5.49fb
        label=2.5.49fb
        append="video=atyfb:1280x1024-16@85"

This got me a 160x64 framebuffer with yellow text on
blue background.  Nice, but only got about 10 lines before
the kernel hung. The disk light got stuck on and there were
no response to things like sysrq.  
The few lines displayed was about the fb, drm, and finally
the 3com network adapter.  Then nothing more.

2.5.49 without this patch works.  I use devfs & preempt,
the machine is UP and I use gcc-2.95.4 for compiling.

Helge Hafting

  reply	other threads:[~2002-11-27 11:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20021122100215.GA4998@pazke.ipt>
2002-11-26 23:22 ` Fbdev 2.5.49 BK fixes James Simmons
2002-11-27 11:04   ` Helge Hafting [this message]
2002-11-27 17:49     ` James Simmons
2002-11-27 18:08       ` Helge Hafting
2002-11-27 23:18         ` James Simmons
2002-11-28  8:32           ` Joseph Fannin
2002-12-02 21:11             ` [Linux-fbdev-devel] " James Simmons
2002-11-28  8:35           ` Joseph Fannin

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=3DE4A6CF.F62CFF41@aitel.hist.no \
    --to=helgehaf@aitel.hist.no \
    --cc=jsimmons@infradead.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).