Lenovo onelink pro dock (USB3) - second screen not configurable

[Ray-Ven]

Hello,

this is actually a regressin. In Saucy I was able to use all 3 Displays (including the ones of the onelink pro dock) seperately. In trusty and ubopic only the second screen is configurable. The 3rd is a clone of the second and won't be recognized as a seperate screen

thanks for helping
Ray

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-25-generic 3.16.0-25.33
ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
Uname: Linux 3.16.0-25-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: KDE
Date: Sun Nov 30 16:20:59 2014
HibernationDevice: RESUME=UUID=01f1e5f4-97d0-4694-abef-4770404e46be
InstallationDate: Installed on 2014-11-09 (20 days ago)
InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: LENOVO 20C0S0AX00
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-25-generic.efi.signed root=/dev/mapper/ray-root ro rootflags=subvol=@ kopt=root=/dev/mapper/ray-root quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-25-generic N/A
 linux-backports-modules-3.16.0-25-generic N/A
 linux-firmware 1.138
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/16/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: GQET37WW (1.17 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20C0S0AX00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50510 Pro
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrGQET37WW(1.17):bd06/16/2014:svnLENOVO:pn20C0S0AX00:pvrThinkPadS1Yoga:rvnLENOVO:rn20C0S0AX00:rvrSDK0E50510Pro:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 20C0S0AX00
dmi.product.version: ThinkPad S1 Yoga
dmi.sys.vendor: LENOVO

[Brad Figg (brad-figg)]

This change was made by a bot.

[Ray-Ven (ray-ven)]

sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
GQET40WW (1.20 )
11/07/2014

same same - 3rd screen cannot be configured indipendently from 2nd screen

[penalvch (penalvch)]

Ray-Ven, could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue.

If the test did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested exactly shown as:
kernel-fixed-upstream-3.18-rc7

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Ray-Ven (ray-ven)]

kernel-fixed-upstream-3.18.0-031800-generic

[penalvch (penalvch)]

Ray-Ven, the next step is to fully reverse commit bisect from kernel 3.16 to 3.18 in order to identify the last bad commit, followed immediately by the first good one. Once this commit has been identified, then it may be reviewed as a candidate for backporting into your release. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ? Please note, finding adjacent kernel versions is not fully commit bisecting.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Ray-Ven (ray-ven)]

It looks like v3.16.7-utopic (30-Oct-2014 18:15) is the last NOT working Kernel.
v3.17-rc1-utopic (02-Sep-2014 18:51) works fine.
But I think you need me to do https://wiki.ubuntu.com/Kernel/KernelBisection#Reverse_commit_bisecting_upstream_kernel_versions
right?
Will look into that asap

[Ray-Ven (ray-ven)]

if i get this right, I just have to do this:

git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git && cd linux

git checkout v3.17-rc1
git bisect start
git bisect good v3.16.7
git bisect bad v3.17-rc1

is this correct?

[Ray-Ven (ray-ven)]

hmm, what happens if i'm not able to do anything further :-/

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]