Bug #1599952 “Blurred images with kernels after 4.2.x” : Bugs : xorg package : Ubuntu

Revision history for this message

penalvch (penalvch) wrote on 2016-07-10:

#1

RD, thank you for reporting this and helping make Ubuntu better.

While booted into a Ubuntu release that is working for you, could you please run the following command once from a terminal by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information:
apport-collect -p xorg 1599952

When reporting xorg related bugs in the future, please do so via the above method. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

Changed in xorg (Ubuntu):
importance:	Undecided → Low
status:	New → Incomplete

Revision history for this message

supusr (richolad-1) wrote on 2016-07-10: Re: [Bug 1599952] Re: i915 driver not supported in kernels after 4.2.x

#2

Very well. I'll need to reinstall 14.04.4, as that is the only one I
have that works. All of the 16.04 flavors run with unreadable
displays. Let me know if that will be useful for you, and I'll do it today.

RD

On 07/09/2016 05:17 PM, Christopher M. Penalver wrote:
> RD, thank you for reporting this and helping make Ubuntu better.
>
> While booted into a Ubuntu release that is working for you, could you please run the following command once from a terminal by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information:
> apport-collect -p xorg 1599952
>
> When reporting xorg related bugs in the future, please do so via the
> above method. You can learn more about this functionality at
> https://wiki.ubuntu.com/ReportingBugs.
>
> ** Changed in: xorg (Ubuntu)
> Importance: Undecided => Low
>
> ** Changed in: xorg (Ubuntu)
> Status: New => Incomplete
>

Revision history for this message

penalvch (penalvch) wrote on 2016-07-10: Re: i915 driver not supported in kernels after 4.2.x

#3

RD, you could use a live environment via http://releases.ubuntu.com/ to run the command if doing a reinstall will disrupt your current OS.

Revision history for this message

supusr (richolad-1) wrote on 2016-07-10: Fwd: Re: [Bug 1599952] Re: i915 driver not supported in kernels after 4.2.x

#4

On second thought, I suspect you need me to do what you ask from a current release (one I am having trouble with). Therefore, I'm downloading the torrent for MATE 16.04 64-bit, and will install it and suffer through the blurry screen long enough to do what you ask. Give me a couple hours, please. I appreciate the interest in my problem.

RD

-------- Forwarded Message --------
Subject: Re: [Bug 1599952] Re: i915 driver not supported in kernels after 4.2.x
Date: Sun, 10 Jul 2016 08:26:37 -0700
From: RD <email address hidden><mailto:<email address hidden>>
To: Bug 1599952 <email address hidden><mailto:<email address hidden>>

Very well. I'll need to reinstall 14.04.4, as that is the only one I
have that works. All of the 16.04 flavors run with unreadable
displays. Let me know if that will be useful for you, and I'll do it today.

RD

On 07/09/2016 05:17 PM, Christopher M. Penalver wrote:
> RD, thank you for reporting this and helping make Ubuntu better.
>
> While booted into a Ubuntu release that is working for you, could you please run the following command once from a terminal by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information:
> apport-collect -p xorg 1599952
>
> When reporting xorg related bugs in the future, please do so via the
> above method. You can learn more about this functionality at
> https://wiki.ubuntu.com/ReportingBugs.
>
> ** Changed in: xorg (Ubuntu)
> Importance: Undecided => Low
>
> ** Changed in: xorg (Ubuntu)
> Status: New => Incomplete
>

Revision history for this message

supusr (richolad-1) wrote on 2016-07-10: Re: [Bug 1599952] Re: i915 driver not supported in kernels after 4.2.x

#5

Thanks very much. I will do the install, send you the requested output,
and then reload a distro that I can see. It is more than worth it to me
since you are willing to look at my issue. I have always liked Ubuntu
(especially MATE), and this is a small price to pay for a chance to help
you improve it. You'll have the information in a few hours.

RD

On 07/10/2016 08:47 AM, Christopher M. Penalver wrote:
> RD, you could use a live environment via http://releases.ubuntu.com/ to
> run the command if doing a reinstall will disrupt your current OS.
>

Revision history for this message

supusr (richolad-1) wrote on 2016-07-10: CurrentDmesg.txt

#6

CurrentDmesg.txt Edit (59.0 KiB, text/plain)

apport information

tags:	added: apport-collected ubuntu xenial
description:	updated

Revision history for this message

supusr (richolad-1) wrote on 2016-07-10: Dependencies.txt

#7

Dependencies.txt Edit (5.6 KiB, text/plain)

apport information

Revision history for this message

supusr (richolad-1) wrote on 2016-07-10: DpkgLog.txt

#8

DpkgLog.txt Edit (1.6 MiB, text/plain)

apport information

Revision history for this message

supusr (richolad-1) wrote on 2016-07-10: GconfCompiz.txt

#9

GconfCompiz.txt Edit (297 bytes, text/plain)

apport information

Revision history for this message

supusr (richolad-1) wrote on 2016-07-10: JournalErrors.txt

#10

JournalErrors.txt Edit (7.7 KiB, text/plain)

apport information

Revision history for this message

supusr (richolad-1) wrote on 2016-07-10: LightdmDisplayLog.txt

#11

LightdmDisplayLog.txt Edit (8.5 KiB, text/plain)

apport information

Revision history for this message

supusr (richolad-1) wrote on 2016-07-10: LightdmGreeterLog.txt

#12

LightdmGreeterLog.txt Edit (3.2 KiB, text/plain)

apport information

Revision history for this message

supusr (richolad-1) wrote on 2016-07-10: LightdmLog.txt

#13

LightdmLog.txt Edit (40.2 KiB, text/plain)

apport information

Revision history for this message

supusr (richolad-1) wrote on 2016-07-10: Lspci.txt

#14

Lspci.txt Edit (13.2 KiB, text/plain)

apport information

Revision history for this message

supusr (richolad-1) wrote on 2016-07-10: Lsusb.txt

#15

Lsusb.txt Edit (610 bytes, text/plain)

apport information

Revision history for this message

supusr (richolad-1) wrote on 2016-07-10: MonitorsUser.xml.txt

#16

MonitorsUser.xml.txt Edit (731 bytes, text/plain)

apport information

Revision history for this message

supusr (richolad-1) wrote on 2016-07-10: ProcCpuinfo.txt

#17

ProcCpuinfo.txt Edit (3.6 KiB, text/plain)

apport information

Revision history for this message

supusr (richolad-1) wrote on 2016-07-10: ProcEnviron.txt

#18

ProcEnviron.txt Edit (103 bytes, text/plain)

apport information

Revision history for this message

supusr (richolad-1) wrote on 2016-07-10: ProcInterrupts.txt

#19

ProcInterrupts.txt Edit (3.0 KiB, text/plain)

apport information

Revision history for this message

supusr (richolad-1) wrote on 2016-07-10: ProcModules.txt

#20

ProcModules.txt Edit (3.8 KiB, text/plain)

apport information

Revision history for this message

supusr (richolad-1) wrote on 2016-07-10: UdevDb.txt

#21

UdevDb.txt Edit (163.3 KiB, text/plain)

apport information

Revision history for this message

supusr (richolad-1) wrote on 2016-07-10: XorgLog.txt

#22

XorgLog.txt Edit (24.1 KiB, text/plain)

apport information

Revision history for this message

supusr (richolad-1) wrote on 2016-07-10: XorgLogOld.txt

#23

XorgLogOld.txt Edit (24.9 KiB, text/plain)

apport information

Revision history for this message

supusr (richolad-1) wrote on 2016-07-10: Xrandr.txt

#24

Xrandr.txt Edit (10.0 KiB, text/plain)

apport information

Revision history for this message

supusr (richolad-1) wrote on 2016-07-10: xdpyinfo.txt

#25

xdpyinfo.txt Edit (9.6 KiB, text/plain)

apport information

Revision history for this message

penalvch (penalvch) wrote on 2016-07-10:

#26

RD, I clarified your Bug Description to focus on one problem (one issue per report), and correct the fact that the issue isn't your hardware isn't supported (it is) but you have a regression that is causing this problem.

With this in mind, could you please attach a picture or screenshot of the blurred images to this report?

tags:	added: latest-bios-1301
description:	updated
summary:	- i915 driver not supported in kernels after 4.2.x + Blurred images with kernels after 4.2.x
Changed in xorg (Ubuntu):
importance:	Low → Medium

Revision history for this message

supusr (richolad-1) wrote on 2016-07-10: Re: [Bug 1599952] Re: i915 driver not supported in kernels after 4.2.x

#27

Download full text (4.8 KiB)

At this point I have reinstalled MX-Linux. I will try to generate a
screenshot in a live environment and send it to you. Give me 30 minutes
or so...

RD

On 07/10/2016 01:44 PM, Christopher M. Penalver wrote:
> RD, I clarified your Bug Description to focus on one problem (one issue
> per report), and correct the fact that the issue isn't your hardware
> isn't supported (it is) but you have a regression that is causing this
> problem.
>
> With this in mind, could you please attach a picture or screenshot of
> the blurred images to this report?
>
> ** Tags added: latest-bios-1301
>
> ** Description changed:
>
> - Have used Ubuntu or its flavors for 3 years with no issues on this machine. Installed Ubuntu 16.04 64-bit lts, and successively xubuntu 16.04, ubuntuMATE 16.04, and lubuntu 16.04. Each installed, but with blurred images. Could not get native 1920x1080 resolution to display. Would like to use one of these, but am relegated to Debian or Debian derivatives using older kernels and packages that support the driver. Sandy Bridge integrated graphics with my i5 cpu were manufactured in 2011 -- in my opinion not too old to still work or at least be supported somehow. A patch or updated driver would be great. There were a bunch of these Asus cm6850 machines made.
> - ---
> + Have used Ubuntu or its flavors for 3 years with no issues on this
> + machine. Installed Ubuntu 16.04 64-bit lts, and successively xubuntu
> + 16.04, ubuntuMATE 16.04, and lubuntu 16.04. Each installed, but with
> + blurred images.
> +
> + ---
> ApportVersion: 2.20.1-0ubuntu2.1
> Architecture: amd64
> CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
> CompositorRunning: None
> CurrentDesktop: MATE
> DistUpgraded: Fresh install
> DistroCodename: xenial
> DistroRelease: Ubuntu 16.04
> DistroVariant: ubuntu
> ExtraDebuggingInterest: Yes, if not too technical
> GraphicsCard:
> - Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
> - Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:844d]
> + Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
> + Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:844d]
> InstallationDate: Installed on 2016-07-10 (0 days ago)
> InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
> MachineType: ASUSTeK Computer INC. CM6850
> Package: xorg 1:7.7+13ubuntu3
> PackageArchitecture: amd64
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-30-generic root=UUID=30188e44-b1e6-4cdc-bd16-62f107d213a7 ro quiet splash vt.handoff=7
> ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13
> Tags: xenial ubuntu
> Uname: Linux 4.4.0-30-generic x86_64
> UpgradeStatus: No upgrade log present (probably fresh install)
> UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>...

Attached are two .jpg files that are digital photos of the install screen to illustrate my blurred screen.

Tnx for your patience

-------- Forwarded Message --------
Subject:        Fwd: Re: [Bug 1599952] Re: i915 driver not supported in kernels after 4.2.x
Date:   Sun, 10 Jul 2016 15:50:31 -0700
From:   RD <richolad@outlook.com><mailto:richolad@outlook.com>
To:     Bug 1599952 <1599952@bugs.launchpad.net><mailto:1599952@bugs.launchpad.net>

I tried to save a screenshot to a thumb drive, and to a folder in my main OS from the live environment, but the Ubuntu live environment won't let one do that.  Any ideas short of reinstalling again?

-------- Forwarded Message --------
Subject:        Re: [Bug 1599952] Re: i915 driver not supported in kernels after 4.2.x
Date:   Sun, 10 Jul 2016 15:14:14 -0700
From:   RD <richolad@outlook.com><mailto:richolad@outlook.com>
To:     Bug 1599952 <1599952@bugs.launchpad.net><mailto:1599952@bugs.launchpad.net>

At this point I have reinstalled MX-Linux.  I will try to generate a
screenshot in a live environment and send it to you. Give me 30 minutes
or so...

RD

On 07/10/2016 01:44 PM, Christopher M. Penalver wrote:
> RD, I clarified your Bug Description to focus on one problem (one issue
> per report), and correct the fact that the issue isn't your hardware
> isn't supported (it is) but you have a regression that is causing this
> problem.
>
> With this in mind, could you please attach a picture or screenshot of
> the blurred images to this report?
>
> ** Tags added: latest-bios-1301
>
> ** Description changed:
>
> - Have used Ubuntu or its flavors for 3 years with no issues on this machine.  Installed Ubuntu 16.04 64-bit lts, and successively xubuntu 16.04, ubuntuMATE 16.04, and lubuntu 16.04.  Each installed, but with blurred images.  Could not get native 1920x1080 resolution to display.  Would like to use one of these, but am relegated to Debian or Debian derivatives using older kernels and packages that support the driver.  Sandy Bridge integrated graphics with my i5 cpu were manufactured in 2011 -- in my opinion not too old to still work or at least be supported somehow.  A patch or updated driver would be great.  There were a bunch of these Asus cm6850 machines made.
> - ---
> + Have used Ubuntu or its flavors for 3 years with no issues on this
> + machine. Installed Ubuntu 16.04 64-bit lts, and successively xubuntu
> + 16.04, ubuntuMATE 16.04, and lubuntu 16.04. Each installed, but with
> + blurred images.
> +
> + ---
>    ApportVersion: 2.20.1-0ubuntu2.1
>    Architecture: amd64
>    CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
>    CompositorRunning: None
>    CurrentDesktop: MATE
>    DistUpgraded: Fresh install
>    DistroCodename: xenial
>    DistroRelease: Ubuntu 16.04
>    DistroVariant: ubuntu
>    ExtraDebuggingInterest: Yes, if not too technical
>    GraphicsCard:
> -  Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
> -    Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:844d]
> +  Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
> +    Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:844d]
>    InstallationDate: Installed on 2016-07-10 (0 days ago)
>    InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
>    MachineType: ASUSTeK Computer INC. CM6850
>    Package: xorg 1:7.7+13ubuntu3
>    PackageArchitecture: amd64
>    ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-30-generic root=UUID=30188e44-b1e6-4cdc-bd16-62f107d213a7 ro quiet splash vt.handoff=7
>    ProcVersionSignature: Ubuntu 4.4.0-30.49-generic 4.4.13
>    Tags:  xenial ubuntu
>    Uname: Linux 4.4.0-30-generic x86_64
>    UpgradeStatus: No upgrade log present (probably fresh install)
>    UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>    _MarkForUpload: True
>    dmi.bios.date: 12/21/2011
>    dmi.bios.vendor: American Megatrends Inc.
>    dmi.bios.version: 1301
>    dmi.board.asset.tag: To be filled by O.E.M.
>    dmi.board.name: CM6850
>    dmi.board.vendor: ASUSTeK Computer INC.
>    dmi.board.version: Rev 1.xx
>    dmi.chassis.asset.tag: Asset-1234567890
>    dmi.chassis.type: 3
>    dmi.chassis.vendor: Chassis Manufacture
>    dmi.chassis.version: Chassis Version
>    dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd12/21/2011:svnASUSTeKComputerINC.:pnCM6850:pvrSystemVersion:rvnASUSTeKComputerINC.:rnCM6850:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
>    dmi.product.name: CM6850
>    dmi.product.version: System Version
>    dmi.sys.vendor: ASUSTeK Computer INC.
>    version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
>    version.ia32-libs: ia32-libs N/A
>    version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
>    version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
>    version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
>    version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
>    version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
>    version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
>    version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
>    version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1
>    version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
>
> ** Summary changed:
>
> - i915 driver not supported in kernels after 4.2.x
> + Blurred images with kernels after 4.2.x
>
> ** Changed in: xorg (Ubuntu)
>     Importance: Low => Medium
>

Revision history for this message

penalvch (penalvch) wrote on 2016-07-11:

#30

RD, in order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel 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 issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically requested to do so.

Once testing of the latest upstream kernel is complete, please mark this report Status Confirmed. Please let us know your results.

Thank you for your understanding.

Revision history for this message

supusr (richolad-1) wrote on 2016-07-11:

#31

Thanks again for your interest. I can report that I tested upstream kernel 4.7-6 as requested. And it did not resolve my issues. Due to the fact that I am now using Mx-15 (Fusion), and I must install Ubuntu to perform further testing, I will not be able to spare any more time in these efforts. I hope the work done so far is sufficient to point others in the right direction.

RD

Revision history for this message

supusr (richolad-1) wrote on 2016-07-11:

#32

I saw no yellow circle, but:

kernel-bug-exists-upstream
kernel-bug-exists-upstream-4.7-rc6

RD

Revision history for this message

supusr (richolad-1) wrote on 2016-07-11: Re: [Bug 1599952] Re: Blurred images with kernels after 4.2.x

#33

Thanks again for your interest. I can report that I tested upstream kernel 4.7-6 as requested. And it did not resolve my issues. Due to the fact that I am now using Mx-15 (Fusion), and I must install Ubuntu to perform further testing, I will not be able to spare any more time in these efforts. I hope the work done so far is sufficient to point others in the right direction.

I saw no yellow circle, but:

kernel-bug-exists-upstream
kernel-bug-exists-upstream-4.7-rc6

RD

On 07/10/2016 05:51 PM, Christopher M. Penalver wrote:

RD, in order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel 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 issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is
the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of
kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically
requested to do so.

Once testing of the latest upstream kernel is complete, please mark this
report Status Confirmed. Please let us know your results.