All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alessandro Suardi <alessandro.suardi@oracle.com>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: radeon still broken (was: Linux 2.4.22-pre8)
Date: Fri, 25 Jul 2003 13:36:24 +0200	[thread overview]
Message-ID: <3F211638.3090807@oracle.com> (raw)
In-Reply-To: <Pine.LNX.4.55L.0307241721130.7875@freak.distro.conectiva>

Marcelo Tosatti wrote:
> Hello,
> 
> Here goes -pre8. It contains network driver updates, IEEE1394 update, a
> POSIX compliance fix introduced by the execve() security fixes during
> early -pre, amongst others.
> 
> Detailed changelog below

radeon is still broken. Looks obvious since it was broken for me
  since -pre6, and -pre8 didn't change anything apparently... but
  I decided to give -pre8 a spin anyway.

To my surprise, the framebuffer didn't go wild as it happened in
  earlier occasions - as in here:

http://www.ussg.iu.edu/hypermail/linux/kernel/0307.2/0732.html

However, firing startx resulted in a black screen and a hard hang
  (had to keep the poweroff button for 10" to actually power off).

So I tried booting -pre8 again, and this time the framebuffer went
  wild again. It looks like there is a timing issue perhaps ?

I'm available for testing and debugging this - so far I'm stuck
  with -pre4 which is the latest working.


Thanks in advance for any help/insight.

--alessandro

  "Prima di non essere sincera / Pensa che ti tradisci solo tu"
       (Vasco Rossi, 'Prima di partire per un lungo viaggio')


      parent reply	other threads:[~2003-07-25 11:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-24 20:23 Linux 2.4.22-pre8 Marcelo Tosatti
2003-07-25  1:05 ` Geert Uytterhoeven
2003-07-25  7:10   ` Andreas Gruenbacher
2003-07-25  3:15 ` Nuno Silva
2003-07-25 12:41   ` Marcelo Tosatti
2003-07-27 16:31     ` Roy Sigurd Karlsbakk
2003-07-25 11:36 ` Alessandro Suardi [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=3F211638.3090807@oracle.com \
    --to=alessandro.suardi@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    /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.