All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 24996] Wrong display resolution in X, "windowed" console. FX 5600 XT
Date: Wed, 11 Nov 2009 12:18:02 -0800 (PST)	[thread overview]
Message-ID: <20091111201802.4FF4F1300DF@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-24996-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>

http://bugs.freedesktop.org/show_bug.cgi?id=24996





--- Comment #5 from Simon Siemonsma <simon-ox55uKOtYtiZyCGURLKNQw@public.gmane.org>  2009-11-11 12:18:01 PST ---
(In reply to comment #0)
> Created an attachment (id=31062)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=31062) [details]
> Dmesg
> 
> I'm getting 1024x768 display resolution in X, even though my monitors native is
> 1248x1024. When using console, it doesn't fill the whole screen it is
> "windowed" in corner.
> I'm using ArchLinux with latest git build of xf86-video-nouveau and this
> http://www.archlinux.org/packages/extra/i686/nouveau-drm/ nouveau-drm package.
> Using or not using fix_resolution_detection.patch doesn't change anything
> (superficially). I have enabled kms. Without it i had artifacts in different
> programs.
> I'll add dmesg and xorg.log.
> 

I have exactly the same problem. Only I have a NV43 video chip.
I'm using Gentoo amd64. Nouveau is compiled into the kernel.
without KMS set everything looks fine.
With KMS set as described by the original poster.
No other differences in the kernel configuration.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2009-11-11 20:18 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-09 11:37 [Bug 24996] New: Wrong display resolution in X, "windowed" console. FX 5600 XT bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-24996-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2009-11-09 11:38   ` [Bug 24996] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-11-09 13:46   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-11-09 16:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-11-10 22:47   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-11-11 20:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2009-11-11 20:38   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-11-13 14:33   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-11-13 14:58   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-11-13 15:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-11-14 20:50   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-11-17 12:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-11-18  3:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-11-18 16:04   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-11-18 19:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-11-19  1:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-11-19 14:31   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-11-19 14:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-11-19 14:38   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-11-19 17:50   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-11-23 20:25   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-11-24 15:15   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-12-20 11:42   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-12-20 11:43   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-12-20 13:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-12-20 14:08   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-12-20 14:15   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-12-20 14:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-12-20 22:48   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-12-21 20:00   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-12-22  0:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

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=20091111201802.4FF4F1300DF@annarchy.freedesktop.org \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@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.