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 18234] New: c51 lvds script failure in randr12 mode. if I start the X server the screen is black and the framebuffer too because it trys to link the whole output to the monitor
Date: Sun, 26 Oct 2008 15:43:16 -0700 (PDT)	[thread overview]
Message-ID: <bug-18234-8800@http.bugs.freedesktop.org/> (raw)

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

           Summary: c51 lvds script failure in randr12 mode. if I start the
                    X server the screen is black and the framebuffer too
                    because it trys to link the whole output to the monitor
           Product: xorg
           Version: 7.3
          Platform: Other
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
        AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
        ReportedBy: maxmusterm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
         QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org


I use a md98300 medion notebook with a nVidia Geforce Go 6150 graphic
processor.
You have to change the BIOSLOG to work.
I will later add a few Xorg logs for debugging.


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

             reply	other threads:[~2008-10-26 22:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-26 22:43 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-18234-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2008-10-26 23:46   ` [Bug 18234] c51 lvds script failure in randr12 mode. if I start the X server the screen is black and the framebuffer too because it trys to link the whole output to the monitor bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-10-27  0:07   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-10-27  0:19   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-10-27  0:26   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-10-27 19:55   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-10-28  0:10   ` 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=bug-18234-8800@http.bugs.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.