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 101447] New: Nouveau on GP106 can't work with another framebuffer drivers (possibly uvesafb)
Date: Thu, 15 Jun 2017 12:03:23 +0000	[thread overview]
Message-ID: <bug-101447-8800@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1288 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=101447

            Bug ID: 101447
           Summary: Nouveau on GP106 can't work with another framebuffer
                    drivers (possibly uvesafb)
           Product: xorg
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
          Reporter: barracuda72-5URONGGNgjI@public.gmane.org
        QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org

At boot then uvesafb first picked up and then replaced with nouveau screen goes
into distorted state. X can be run but nothing apperars on the screen except
garbage. Switching between VT's works, but screen is still distorted.
Disabling all other framebuffer drivers in kernel config helped to solve this
issue.
Logs before disabling:
dmesg: https://pastebin.com/YC3kX7E3 (esp. lines 150 and 152 to 154)
Xorg: https://pastebin.com/JTyYynRd
Logs after disabling:
dmesg: https://pastebin.com/Dkgk67zA
Xorg: https://pastebin.com/VaJpqGxb

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2768 bytes --]

[-- Attachment #2: Type: text/plain, Size: 154 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau

             reply	other threads:[~2017-06-15 12:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-15 12:03 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-101447-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2017-06-15 21:29   ` [Bug 101447] Nouveau on GP106 can't work with another framebuffer drivers (possibly uvesafb) bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-01-29 14:06   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-01-29 17:35   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  9:29   ` 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-101447-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.