From: "Stephane Marchesin" <marchesin-YynmYXH4S6491FlJP1ih0VAUjnlXr6A1@public.gmane.org>
To: Jasper Bryant-Greene <jasper-XrxwZhJB1KNIJsTUW+i+0g@public.gmane.org>
Cc: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: NV86 (Quadro NVS 140M) errors in dmesg
Date: Sat, 2 Aug 2008 04:10:51 +0200 [thread overview]
Message-ID: <6a89f9d50808011910g560e2953p374d48829e240b6b@mail.gmail.com> (raw)
In-Reply-To: <1217640709.3619.12.camel-UfQkq/qJUt3chhi/u/9I76VXKuFTiq87@public.gmane.org>
On 8/2/08, Jasper Bryant-Greene <jasper-XrxwZhJB1KNIJsTUW+i+0g@public.gmane.org> wrote:
> On Sat, 2008-08-02 at 10:02 +1000, Ben Skeggs wrote:
> > Am Samstag, den 02.08.2008, 10:20 +1200 schrieb Jasper Bryant-Greene:
>
> > > [ 22.586502] [drm:nouveau_graph_trapped_channel] *ERROR* AIII,
> > > invalid/inactive channel id 128
> > > [ 22.586509] [drm] PGRAPH_ERROR - nSource: PROTECTION_ERROR, nStatus:
> > > [ 22.586513] [drm] PGRAPH_ERROR - Ch -1/0 Class 0x0000 Mthd 0x0000
> > > Data 0x00000000:0x00000000
> > That's a bug - I see it on my FX570M, it'll only happen on first X
> > start. Will look into it when it annoys me enough.
>
>
> OK, let me know if you need any details from me when you get around to
> looking at this. It doesn't seem to actually cause any problems.
>
> Also, is there any way to force the DPI with nouveau? I'm specifying
>
> -dpi 96
>
> ... on the X command line, but I still see
>
> (**) NOUVEAU(0): DPI set to (129, 203)
>
Your panel size should be reported in the X.Org log, check that it is correct.
> ... in the Xorg.0.log, and the font sizes are all weird in X. With the
> nvidia binary driver I used to have to use
>
> Option DPI "96 x 96"
>
> ... in xorg.conf - is there something similar with nouveau?
>
> I'm guessing its my laptop panel reporting incorrect values for
> something, but I still need to work around it :)
>
You can use the xrandr utility to force the panel size/dpi value.
Stephane
next prev parent reply other threads:[~2008-08-02 2:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-01 22:20 NV86 (Quadro NVS 140M) errors in dmesg Jasper Bryant-Greene
[not found] ` <1217629252.3619.5.camel-UfQkq/qJUt3chhi/u/9I76VXKuFTiq87@public.gmane.org>
2008-08-02 0:02 ` Ben Skeggs
2008-08-02 1:31 ` Jasper Bryant-Greene
[not found] ` <1217640709.3619.12.camel-UfQkq/qJUt3chhi/u/9I76VXKuFTiq87@public.gmane.org>
2008-08-02 2:10 ` Stephane Marchesin [this message]
[not found] ` <6a89f9d50808011910g560e2953p374d48829e240b6b-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-08-02 2:16 ` Jasper Bryant-Greene
[not found] ` <1217643398.3619.16.camel-UfQkq/qJUt3chhi/u/9I76VXKuFTiq87@public.gmane.org>
2008-08-02 3:03 ` Stephane Marchesin
2008-08-02 9:54 ` Jasper Bryant-Greene
[not found] ` <1217670874.4622.4.camel-UfQkq/qJUt3chhi/u/9I76VXKuFTiq87@public.gmane.org>
2008-08-02 11:35 ` Ben Skeggs
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=6a89f9d50808011910g560e2953p374d48829e240b6b@mail.gmail.com \
--to=marchesin-yynmyxh4s6491fljp1ih0vaujnlxr6a1@public.gmane.org \
--cc=jasper-XrxwZhJB1KNIJsTUW+i+0g@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@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.