From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 110660] GeForce GT 750M Mac Edition fullscreen issues
Date: Sun, 01 Dec 2019 10:06:01 +0000 [thread overview]
Message-ID: <bug-110660-8800-nSL93H0avP@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110660-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1144 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110660
--- Comment #43 from Alexey Kuznetsov <axet-BUHhN+a2lJ4@public.gmane.org> ---
Created attachment 146055
--> https://bugs.freedesktop.org/attachment.cgi?id=146055&action=edit
LVDS/eDP mode fix
For some reason kernel 5.3.0 end up with your 'adjusted_mode' patch instead
correct 'mode' patch. As result recent Ubuntu 9.10 (which I'm testing right
now) still have problem with 9 displays... That quite strange since I expect
this issue was fixed. I've checked kernel sources (for Ubuntu 19.10 kernel
5.3.0-23-generic), patch f8d6211ac (drm/nouveau/disp/nv50-: force scaler for
any non-default LVDS/eDP modes) indeed persisted but with your first attempt
fixing the issue!
I did manually rebuild kernel 'mode' and it works again!
Not sure what I have to do here...
* https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/eoan/
*
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/eoan/commit/?id=f8d6211ac77f0d1f7aebc64e961dc28771ba0052
Here MY patch ;)
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2331 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2019-12-01 10:06 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 12:01 [Bug 110660] New: GeForce GT 750M Mac Edition fullscreen issues bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-110660-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2019-05-10 12:01 ` [Bug 110660] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-10 12:07 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-10 12:08 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-10 12:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-10 14:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-10 14:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-10 14:58 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-10 15:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-10 16:06 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-10 16:21 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-10 16:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-10 16:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-10 16:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-10 16:47 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-10 16:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-10 16:54 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-10 17:16 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-10 17:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-10 17:49 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-10 18:19 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-10 18:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-10 18:55 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-11 0:59 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-11 1:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-11 7:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-11 16:20 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-12 14:42 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-12 14:42 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-12 14:43 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-25 18:35 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-25 18:54 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-25 22:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-26 19:11 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-28 16:58 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-28 17:19 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-28 20:28 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-28 20:31 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-29 1:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-29 7:18 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-29 7:58 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-29 8:03 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-05-29 11:34 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-08-26 16:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-01 10:06 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2019-12-04 9:49 ` 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-110660-8800-nSL93H0avP@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox