[Bug 1418706] Re: Vivid: UEFI: blank drive incorrectly detected as existing BIOS-mode install

2015-04-03 Thread G-philip
If you choose not to download updates from the internet, it works anyway. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1418706 Title: Vivid: UEFI: blank drive incorrectly detected as existing BIOS-

[Bug 1433310] Re: Installer stuck at "Force UEFI installation" dialog

2015-04-03 Thread G-philip
*** This bug is a duplicate of bug 1418706 *** https://bugs.launchpad.net/bugs/1418706 If you choose not to download updates from the internet, it works anyway. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpa

[Bug 1275794]

2014-02-13 Thread G-philip
(In reply to comment #117) > That is beta firmware. > The Lenovo guy in there said final firmware would likely be released next > week. > > And I asked for a bootable CD update, and other people did so as well. > The Lenovo guy in there said he'd pass on the request for a bootable CD > update. Ju

[Bug 1275794]

2014-02-13 Thread G-philip
(In reply to comment #118) > Just installed the firmware update. Now dock shows firmware version 2.17. > Firmware update utility required Intel display-driver installed on my > Windows 8.1 installation, otherwise it was unable to update to detect the > DP-hub. It also required a least one display

[Bug 1275794]

2014-02-13 Thread G-philip
(In reply to comment #125) > (In reply to comment #115) > > I tried applying the two patches which you posted on intel-gfx[1], ported to > > 3.13. > > > > [1] http://article.gmane.org/gmane.comp.freedesktop.xorg.drivers.intel/33737 > > > > Using a T540p and an Ultradock, connected to a Dell U2410

[Bug 1275794]

2014-02-13 Thread G-philip
(In reply to comment #131) > (In reply to comment #129) > > It seems the hang is resolved with the dock firmware update (2.17) provided > > by Lenovo. As far as I am concerned I think this bug can be closed. > > From the kernel perspective it's fixed when we don't freeze the machine even > when a

[Bug 1275794]

2014-02-13 Thread G-philip
(In reply to comment #128) > (In reply to comment #124) > > There seems to be still a problem enumerating the devices connected to the > > DP hub > > We currently do not support MST (multistream) DP branch devices. If it works > for multiple monitors, great, but it's more or less by accident. Tha

[Bug 1275794]

2014-02-13 Thread G-philip
(In reply to comment #122) > I also get a mirrored output on VGA, however I could not extend to that > adapter. (it seems to be a hardware mirror, I only see one external display, > DP2, in XrandR...) Same here. Switching to one external DP display now works like a charm. Gets identified as DP2 in