All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Happe <andy-L2Gnq7z6Vd1eoWH0uzbU5w@public.gmane.org>
To: Pekka Paalanen <pq-X3B1VOXEql0@public.gmane.org>
Cc: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: "Unknown LVDS configuration bits, please report" -	Error
Date: Mon, 28 Apr 2008 18:59:32 +0200	[thread overview]
Message-ID: <1209401972.27356.3.camel@wolverine> (raw)
In-Reply-To: <20080428193358.451274bb-cxYvVS3buNOdIgDiPM52R8c4bpwCjbIv@public.gmane.org>

On Mon, 2008-04-28 at 19:33 +0300, Pekka Paalanen wrote:
> "Framebuffer loaded" is usually a bad sign. The Nouveau driver does not
> work reliably with a framebuffer driver loaded. Granted, there are rumours
> that vesafb should work, and that on PPC you have to use the... hm, I fail
> to recall the driver name, offb?

OT:
Yeah, that open firmware thingy was a problem with my old powerbook. I
just disabled framebuffer-use at X.org driver level (on the powerbook),
could that be a stability problem:

> To my unexperienced eyes, this looks just a not-fully-supported hardware.
> Have you searched the bugzilla? I guess there might already be a report
> for this specific case. If not, please add a bug, so the developers can
> track it.

Silly me, there were already two bug reports for that problem, I will
just watch the mailing list and report it again if there's no progress
in some weeks.

cheers,
andy

  parent reply	other threads:[~2008-04-28 16:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-27 13:29 "Unknown LVDS configuration bits, please report" - Error Andreas Happe
2008-04-28 16:33 ` Pekka Paalanen
     [not found]   ` <20080428193358.451274bb-cxYvVS3buNOdIgDiPM52R8c4bpwCjbIv@public.gmane.org>
2008-04-28 16:59     ` Andreas Happe [this message]
2008-04-28 18:17       ` Maarten Maathuis

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=1209401972.27356.3.camel@wolverine \
    --to=andy-l2gnq7z6vd1eowh0uzbu5w@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    --cc=pq-X3B1VOXEql0@public.gmane.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.