kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #96787
[Bug 1332220] Re: Backport hdmi_portclock_limit regression fix patch to allow forcing overclocking of DVI/HDMI signals
Some news: solution of Joseph S Tate (jtate) from on 2014-06-19 works partly (thanks Joseph!).
These changes allow to use 3.16.0-28 kernel, but during boot on encryption stage (before / is accessible) the resolution is still incorrect, so user has to enter password in blurred screen.
I insist this bug should be called an "unfixed regression", maybe
desirable or inevitable, but still a regression:
E.g. user bough a huge monitor which worked perfectly with Windows in the shop, came home and it doesn't work correctly with his favorite Linux distribution with the same DVI-D cable.
And for him it's impossible to make xorg-config, put there ModeLines from Xorg logs or xrandr output and etc. It's a step back to 1990th with all this manual xorg-config stuff.
And even more, this monitor worked perfectly the year before with the
same Linux distro, and now it doesn't. For sure it's a regression, isn't
it?
--
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/1332220
Title:
Backport hdmi_portclock_limit regression fix patch to allow forcing
overclocking of DVI/HDMI signals
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Trusty:
Fix Released
Status in linux source package in Utopic:
Fix Released
Bug description:
https://bugzilla.kernel.org/show_bug.cgi?id=72961
Summary: a patch included after upstream kernel 3.10 (and for ubuntu,
whatever was used in the live iso) restricted DVI-D single link
connections to 165MHz. Some monitors, which worked before that patch
via an overclocked single link connection stopped working. This patch
lets the user specify modes manually that are higher than 165MHz "at
their own risk".
I've tested the patch in the upstream bug against the current (as of
19 Jun 2014) git trusty kernel tree and everything seems to work fine.
While the patch listed on the above bug won't apply with git-am, it
will apply as patch -p0.
I have it patched on my local branch, and can send a diff if it's
needed.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-29-generic 3.13.0-29.53
ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
Uname: Linux 3.13.0-30-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: jtate 2315 F.... pulseaudio
jtate 2635 F.... pulseaudio
/dev/snd/controlC0: jtate 2315 F.... pulseaudio
jtate 2635 F.... pulseaudio
CurrentDesktop: KDE
Date: Thu Jun 19 13:30:52 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-06-16 (3 days ago)
InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1)
IwConfig:
eth0 no wireless extensions.
lo no wireless extensions.
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-30-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-3.13.0-30-generic N/A
linux-backports-modules-3.13.0-30-generic N/A
linux-firmware 1.127.2
RfKill:
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/23/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.30
dmi.board.name: Z97 Extreme4
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.30:bd05/23/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ97Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1332220/+subscriptions
References