Thanks Rocko (my fellow Perthian?). It seems you're right the modeset
driver is just not /inventing/ the fake modes you desire.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Confirmed
** Summary changed:
- mod
** Changed in: xorg-server (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1606103
Title:
modeset driver does not detect all screen resolutions
Sta
** Bug watch added: Debian Bug tracker #832432
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832432
** Also affects: xorg-server (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832432
Importance: Unknown
Status: Unknown
--
You received this bug notification becau
The output is the same for the 4.7.0 kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1606103
Title:
modeset driver does not detect all screen resolutions
Status in linux package
This is the output for kernel 4.6.4-040604-generic (running back on
Ubuntu 16.04, but I guess that shouldn't make any difference if we're
just reading the kernel info):
/sys/class/drm/card0-eDP-1/modes:3840x2160
(There's a bunch of other modes but they are all for the various
resolutions on the H
This bug might need reassigning to the kernel instead.
I'm guessing that (like Mir) the mode-setting driver doesn't invent in-
between modes like Xorg drivers do (and like legacy VGA BIOS's do for
old CRTs)
Please run this command to see if the kernel is the one failing to report those
modes:
6 matches
Mail list logo