linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fredrik Noring <noring@nocrew.org>
To: Antonino Daplas <adaplas@pol.net>
Cc: Linux Fbdev development list <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: rivafb "Badness" using fbdev.diff.gz and 2.5.5[45]
Date: 19 Jan 2003 17:42:25 +0100	[thread overview]
Message-ID: <1042994545.1071.9.camel@localhost.localdomain> (raw)
In-Reply-To: <1042990791.1058.12.camel@localhost.localdomain>

sön 2003-01-19 klockan 16.41 skrev Antonino Daplas:
> The other patch (in reply to Jak) should hopefully fix the initial 
> screen corruption on insmod and the kobject trace message.

It did - thanks!

> Can you try running an fbdev-based application, such as X, at 8bpp, just
> to find out if the hardware is incorrectly initialized from the very
> start or if this is more fbcon-related?

I've tried two things. This:

   modprobe rivafb     <-- loads OK, no visual side effects
   modprobe fbcon      <-- garbage graphics, complete hang

And this:

   modprobe rivafb     <-- loads OK, no visual side effects
   fbset 640x480-60    <-- screen turns black, complete hang

The mode looks like this:

   mode "640x480-60"
       # D: 25.175 MHz, H: 31.469 kHz, V: 59.94 Hz
       geometry 640 480 640 480 8
       timings 39722 48 16 33 10 96 2
    endmode

I haven't found any crash reports or similar in /var/log/messages. The
system simply freezes completely.

	Fredrik




-------------------------------------------------------
This SF.NET email is sponsored by: FREE  SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your  SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en

  reply	other threads:[~2003-01-19 16:41 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-19 11:29 rivafb "Badness" using fbdev.diff.gz and 2.5.5[45] Fredrik Noring
2003-01-19 15:41 ` Antonino Daplas
2003-01-19 16:42   ` Fredrik Noring [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-11 13:30 Jak
2003-01-15  0:43 ` James Simmons
2003-01-18 20:28   ` Jak
2003-01-19 15:40     ` Antonino Daplas
2003-01-20 19:09       ` Jak
2003-01-20 22:44         ` Antonino Daplas
2003-01-21 10:29           ` Geert Uytterhoeven
2003-01-21 11:31             ` Antonino Daplas
2003-01-24 22:53             ` James Simmons
2003-01-25  9:00               ` Geert Uytterhoeven
2003-01-30 23:00                 ` Antonino Daplas
2003-02-12 20:13                   ` James Simmons
2003-01-21  0:08         ` Antonino Daplas
2003-01-24 20:14       ` James Simmons
2003-01-30 23:01         ` Antonino Daplas
2003-02-12 20:15           ` James Simmons
2003-02-12 23:37             ` Antonino Daplas
2003-01-24 19:09     ` James Simmons

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=1042994545.1071.9.camel@localhost.localdomain \
    --to=noring@nocrew.org \
    --cc=adaplas@pol.net \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    /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).