utopic 3.16.0-9 iso boots to desktop no unity

[jerrylamos]

Intel Core 2 Duo 3 gHz 4 gb Lenovo Think Centre.
Boots 3.16.0-6 amd64 fine, runs compiz 3D fine.

Today's amd64 iso download, 20 August, boots to desktop & cursor.
No unity.
Did ubuntu-bug from command line on the booted iso, saved report.

Booted 3.10.0-6 and ran ubuntu-bug apport on the saved file.

Planet Ubuntu asked for results on 3.16.0-9 so this is my result.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-9-generic 3.16.0-9.14
ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
Uname: Linux 3.16.0-9-generic x86_64
ApportVersion: 2.14.6-0ubuntu2
Architecture: amd64
CasperVersion: 1.341
Date: Wed Aug 20 16:57:57 2014
LiveMediaBuild: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140820)
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=(loop)/casper/vmlinuz.efi boot=casper iso-scan/filename=/utopic-desktop-amd64.iso noprompt noeject
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/10/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 5CKT69AUS
dmi.board.name: LENOVO
dmi.chassis.vendor: LENOVO
dmi.chassis.version: NONE
dmi.modalias: dmi:bvnLENOVO:bvr5CKT69AUS:bd01/10/2011:svnLENOVO:pn6234A1U:pvrThinkCentreM58p:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE:
dmi.product.name: 6234A1U
dmi.product.version: ThinkCentre M58p
dmi.sys.vendor: LENOVO

[Brad Figg (brad-figg)]

This change was made by a bot.

[jerrylamos (jerrylamos)]

Downloaded same day's i386 32 bit.

32 bit .iso booted to normal desktop, compiz, unity, and installed just fine.

I've been running 64 bit on this Intel Core 2 Duo 3 gHz 4 gb all along just fine up to and including 3.16.0-6. Looking at various posts, there's been a compiz change....

[Stephen M. Webb (bregma)]

Last change to Compiz was 2014-08-12, last change to Unity was 2014-08-11. I would suspect the video drivers again.

[Stephen M. Webb (bregma)]

These errors in the BootDmesg.txt indicate a driver problem that would prevent Compiz from running.

[ 4.352033] [drm:init_ring_common] *ERROR* render ring initialization failed ctl 0001f001 (valid? 1) head 00000298 tail 00000000 start 00503000 [expected 00503000]
[ 4.352041] [drm:i915_gem_init] *ERROR* Failed to initialize GPU, declaring it wedged

[jerrylamos (jerrylamos)]

32 bit 3.16.0-9 boots and runs fine (for a development release) using it right now.

Downloaded and tried both 32 and 64 same day, 64 fails 32 runs.

What's the difference between the drivers for 32 bit and 64 bit?

How do I tell which driver is being used?

Thanks for looking at this bug.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[jerrylamos (jerrylamos)]

Updated 22 August:

3.16.0-10 amd64 .iso boots to desktop, compiz and unity fail.

3.16.0-10 i386 32 bit running as expected (for a development release).

Other users see same problem, refer to

http://ubuntuforums.org/showthread.php?t=2240600

[jerrylamos (jerrylamos)]

Installed Lubuntu amd64 as well.

3.16.-10 amd64 runs fine, only faster. No compiz.....

[jerrylamos (jerrylamos)]

26 August 3.10.6-10 still not running on the amd64 .iso on Lenovo ThinkCentre. Intel Core 2 duo 3.0 gHz 4 mb.

Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03)

Just did an install here today, using the last 3.16.0-6 iso I have saved. Installed, compiz & unity running.

Updated to latest amd64 .iso, 26 August, which includes the 3.16.0-10 kernel.

3.16.0-10 kernel, boots to wallpaper. No compiz hence no unity.

Reboot selecting 3.16.0-6 out of /boot, compiz and unity running.

Whatever is wrong, it's in the kernel. Everything else is the same.

BTW, in i386 32 bit 3.16.0-10 compiz and unity run.

[jerrylamos (jerrylamos)]

Out of many boots today, 3.16.0-10 ran once. Almost all the time X is running, desktop is fine, compiz and unity fail.

Trying to get compiz and unity running from Ctrl-Alt-F1 or F2 gets a whole screen of messages, including:

.......
Unity is fully supported by your hardware
Unity is not supported by your hardware, loading software.....
-----

Somehow are two consecutive tests being done?

I could do a ubuntu-bug linux at that point if it is any help.

[Stephen M. Webb (bregma)]

The two consecutive test results sound like the desktop shell is being restarted after the first attempt fails.

Compiz requires hardware 3D acceleration (GPU) to be available through the X11 server. The X11 server does not require hardware 3D acceleration to run, which explains why the X server is running but not Compiz. The error messages reported in the attachments to this bug indicate the 3D acceleration is not working at the driver level, for whatever reason.

The error described initially in this bug report resembles bug #1346096. Perhaps the same solution suggested there will solve this problem as well?

[jerrylamos (jerrylamos)]

Looked at bug #1346096. That user got success with apt-get update, apt-get dist-upgrade. Not me.

As of 27 August updates the 3.10.0-10 kernel still fails. Of course, booting the corresponding .iso fails no surprise.

On the same install, same everything else but the kernel, selecting 3.10.0-6 kernel out of /boot (instead of 3.16.0-10 kernel) 3D acceleration runs fine. As it does on all previous utopic, trusty, etc.

3D runs fine on this hardware, for some reason compiz is deciding isn't supported. There's been mention of a compiz change in August.

I don't know what test current compiz does, or where X is in initialization when compiz does the test vs. the compiz level on July 31..

I wouldn't have a clue how to downgrade compiz for testing purposes.....

BTW, running different kernels on the same install, one runs and one fails, is compiz in the kernel?

Thanks for any ideas.

[jerrylamos (jerrylamos)]

Still trying to get 3.16.0-10 to run unity on Intel Core 2 Duo.

Many boots yesterday, just one time 3.16.0-10 ran just fine with 3D hardware support. All the rest, I assume "compiz" has decided that the hardware does not support 3D. It does.

Viewing all this as a "black box", what's going on inside is a defective test by compiz.

I put in a /etc/grub.d/06_custom to boot the -6 kernel on power up. The -10 is available for testing. apt-get update didn't find anything so no use running -10.

[Christopher Townsend (townsend)]

@jerrylamos,

Compiz is *not* part of the kernel. Compiz is deciding your hardware doesn't support 3D because there is an issue in the video driver which is failing the loading of OpenGL (the 3D). This is strictly an issue with the video driver in the kernel and is causing Compiz to fail. There isn't anything that the Compiz team can do about this.

That said, I'm going to subscribe the kernel task to this bug and see if more traction can happen there.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.17 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.17-rc2-utopic/

[Joseph Salisbury (jsalisbury)]

And just to confirm, booting with a prior kernel version will prevent the bug from happening?

[jerrylamos (jerrylamos)]

Joseph, on your comment #18,

yes, booting with prior kernel 3.16.0-6 works. Like right now. As has all utopic kernels previous to 3.10.0-7.

Tried latest 3.17.0-031700rc2-generic on three different installs:

1. On a 3.16.0-9 install, compiz/unity fail as usual. installed 3.17.0-031700rc2-generic which worked until I screwed up an update and killed the install. Flying fingers....

2. Fresh amd64 3.16.0-10 install, compiz & unity fail, then installed 3.17.0-031700rc2-generic. Does not even complete boot. Nada. Recovery mode didn't fix anything. Of course in recovery with primitive screen support it does come up.

3. On this 3.16.0-6 updated to 3.16.0-10, the 3.17.0-031700rc2-generic fails to complete boot. And as usual with -10 compiz and unity fail, but 3.16.0-6 still works, 3D and all. /boot has all three kernels so I can try whichever.

With multiple boots, very rarely like twice in days, 3.10.0-10 compiz and unity work. Smells like a timing race to me, does compiz test for 3D before X is quite ready for the test?

Yes, I'm a retired computer engineer and have time to try various things within my capability and interest.

Thanks for your attention.

[Christopher Townsend (townsend)]

@jerrylamos,

> Smells like a timing race to me, does compiz test for 3D before X is quite ready for the test?

As I stated in a previous comment, the reason why Compiz says it does not support the hardware is because there is an error in the graphics kernel driver, not because there is some race between X and Compiz. Compiz cannot start until X is up.

As Stephen pointed out in comment #5 (https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1359299/comments/5), this is the error from the driver that is causing your issues.

[jerrylamos (jerrylamos)]

3.16.0-6 works for me. Looking at Xorg.0.log - is this the driver that's being used?

[ 9.623] (II) intel(0): Using Kernel Mode Setting driver: i915, version 1.6.0 20080730
[ 9.623] (II) intel(0): SNA compiled: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1 (Maarten Lankhorst <email address hidden>)
[ 9.623] (II) intel(0): SNA compiled for use with valgrind
[ 9.623] (WW) Falling back to old probe method for modesetting
[ 9.623] (WW) Falling back to old probe method for fbdev
[ 9.623] (II) Loading sub module "fbdevhw"
[ 9.623] (II) LoadModule: "fbdevhw"
[ 9.624] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 9.624] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 9.624] compiled for 1.15.1, module version = 0.0.2
[ 9.624] ABI class: X.Org Video Driver, version 15.0
[ 9.624] (WW) Falling back to old probe method for vesa
[ 9.624] (--) intel(0): Integrated Graphics Chipset: Intel(R) Q45/Q43
[ 9.624] (--) intel(0): CPU: x86-64, sse2, sse3, ssse3, sse4.1

[jerrylamos (jerrylamos)]

Here's the same thing from 3.16.0-10 where compiz fails and hence unity fails.
I'm no developer, looks to me like the same driver works for 3.16.0-6 and fails with 3.16.0-10 ?
Am I looking in the wrong place?

[ 9.469] (II) intel(0): SNA compiled: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu1 (Maarten Lankhorst <email address hidden>)
[ 9.469] (II) intel(0): SNA compiled for use with valgrind
[ 9.469] (WW) Falling back to old probe method for modesetting
[ 9.469] (WW) Falling back to old probe method for fbdev
[ 9.469] (II) Loading sub module "fbdevhw"
[ 9.469] (II) LoadModule: "fbdevhw"
[ 9.469] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
[ 9.470] (II) Module fbdevhw: vendor="X.Org Foundation"
[ 9.470] compiled for 1.15.1, module version = 0.0.2
[ 9.470] ABI class: X.Org Video Driver, version 15.0
[ 9.470] (WW) Falling back to old probe method for vesa
[ 9.470] (--) intel(0): Integrated Graphics Chipset: Intel(R) Q45/Q43
[ 9.470] (--) intel(0): CPU: x86-64, sse2, sse3, ssse3, sse4.1

Thanks for any insight.

[Stephen M. Webb (bregma)]

The output from x.org shows the x.org video module in use by the x.org server. A more useful comparison would be to run "grep EE /var/log/Xorg.0.og" and compare the difference between runs with the two Linux kernels. "EE" is the error tag I would expect to see in the X.org log when an error is encountered.

My suspicion is that the problem is in the video driver in the Linux kernel. Try "grep -i i915 /var/log/dmesg" and look for a difference between runs with the two Linux kernels.

[jerrylamos (jerrylamos)]

Stephen, thanks for your interest.

Here's EE results from booting 3.16.0-6 which is fully working:

 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 7.504] Initializing built-in extension MIT-SCREEN-SAVER
[ 7.631] (EE) intel: Failed to load module "dri3" (module does not exist, 0)
[ 7.631] (EE) intel: Failed to load module "present" (module does not exist, 0)
[ 13.286] (II) XKB: reuse xkmfile /var/lib/xkb/server-7C75F152E85183199599C3E0B919739C0EE668AA.xkm

Here's EE results from booting kernel 3.16.0-11 with compiz failing to start:

 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 11.036] Initializing built-in extension MIT-SCREEN-SAVER
[ 11.081] (EE) intel: Failed to load module "dri3" (module does not exist, 0)
[ 11.081] (EE) intel: Failed to load module "present" (module does not exist, 0)
[ 14.907] (II) XKB: reuse xkmfile /var/lib/xkb/server-7C75F152E85183199599C3E0B919739C0EE668AA.xkm
[ 15.879] (II) XKB: reuse xkmfile /var/lib/xkb/server-7C75F152E85183199599C3E0B919739C0EE668AA.xkm
[ 16.792] (II) XKB: reuse xkmfile /var/lib/xkb/server-7C75F152E85183199599C3E0B919739C0EE668AA.xkm
[ 17.696] (II) XKB: reuse xkmfile /var/lib/xkb/server-7C75F152E85183199599C3E0B919739C0EE668AA.xkm
[ 18.577] (II) XKB: reuse xkmfile /var/lib/xkb/server-7C75F152E85183199599C3E0B919739C0EE668AA.xkm
[ 19.458] (II) XKB: reuse xkmfile /var/lib/xkb/server-7C75F152E85183199599C3E0B919739C0EE668AA.xkm
[ 20.349] (II) XKB: reuse xkmfile /var/lib/xkb/server-7C75F152E85183199599C3E0B919739C0EE668AA.xkm
[ 21.239] (II) XKB: reuse xkmfile /var/lib/xkb/server-7C75F152E85183199599C3E0B919739C0EE668AA.xkm
[ 22.166] (II) XKB: reuse xkmfile /var/lib/xkb/server-7C75F152E85183199599C3E0B919739C0EE668AA.xkm
[ 23.071] (II) XKB: reuse xkmfile /var/lib/xkb/server-7C75F152E85183199599C3E0B919739C0EE668AA.xkm
[ 23.954] (II) XKB: reuse xkmfile /var/lib/xkb/server-7C75F152E85183199599C3E0B919739C0EE668AA.xkm
[ 24.853] (II) XKB: reuse xkmfile /var/lib/xkb/server-7C75F152E85183199599C3E0B919739C0EE668AA.xkm
[ 25.732] (II) XKB: reuse xkmfile /var/lib/xkb/server-7C75F152E85183199599C3E0B919739C0EE668AA.xkm

Here's i915 results from 3.16.0-6 fully working:

[ 4.272561] i915 0000:00:02.0: irq 45 for MSI/MSI-X
[ 4.544420] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[ 4.544421] i915 0000:00:02.0: registered panic notifier
[ 4.567686] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0

Here's i915 results from 3.16.0-11 compiz fails to run:

[ 8.648069] i915 0000:00:02.0: irq 45 for MSI/MSI-X
[ 8.712041] [drm:i915_gem_init] *ERROR* Failed to initialize GPU, declaring it wedged
[ 8.842619] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[ 8.842620] i915 0000:00:02.0: registered panic notifier
[ 8.865302] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0

Note both these kernels are from the same /boot on the same install originally done with -06 and updated to -11. Booting the .iso for -11 gets the same compiz fail to start.

Anything else to try?

[jerrylamos (jerrylamos)]

As a computer development engineer, if something failed that ran before, suspect would be whatever was new (kernel in this case). Did the new item fail, or did it react in such a way to cause something else to fail that was running O.K. before?

Can you tell if the same Intel driver is being used for both 3.16.0-6 and 3.16.0-11 since, it is the same install except for the kernel chosen from /boot?

Is -11 doing something different that causes the driver to fail?

Thanks much for any insight.
32 bit Utopic runs O.K. on this Intel Core 2 Duo.
64 bit Utopic running O.K. as is on both my Intel Atom duo netbook and Amd/ATI duo notebook.

[Stephen M. Webb (bregma)]

Yes, that is what bisection does. It essentially performs a binary search on all of the dozens to hundreds of patches that go into minor kernel point releases in an effort to identify the changeset that resulted in the unwanted behaviour.

[jerrylamos (jerrylamos)]

Thanks. If I can do any testing let me know.

[jerrylamos (jerrylamos)]

BTW, if there's any way to try Compiz with bisection, from my past ubuntu testing over the years since Compiz was introduced, Compiz code has a lot of hardware dependencies....

Just tried 3.16.0-11 updates on 30 August still no go.

[jerrylamos (jerrylamos)]

As far as triangulation from the bird's eye view:

utopic fails:

ubuntu unity/compiz amd64 after July 31

utopic works:

ubuntu unity/compiz amd64 July 31 and before
ubuntu unity/compiz i386 today
kubuntu amd64 today
xubuntu amd64 today
lubuntu amd64 today

I'm no particular fan of unity, but as a tester I run it looking for bugs.....

[Alan Fry (alan-fry)]

Just to add my findings to this, the i915 fault also appears on a Ubuntu-Mate install but apparently recovers from it to log-in and run correctly.

Fully working boot using 3.13.0-34.60 kernel, otherwise fully updated Ubuntu Utopic
alan@alan-ubuntu:~$ grep -i i915 /var/log/dmesg
[ 4.188060] i915 0000:00:02.0: irq 46 for MSI/MSI-X
[ 5.535026] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[ 5.535027] i915 0000:00:02.0: registered panic notifier
[ 5.558936] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
(Conclusion - No i915 failure with old, non current kernel)

alan@alan-ubuntu:~$
Failed boot on same install using 3.16.0-11.16 kernel
[ 4.435951] i915 0000:00:02.0: irq 48 for MSI/MSI-X
[ 4.587670] [drm:i915_gem_init] *ERROR* Failed to initialize GPU, declaring it wedged
[ 4.739567] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[ 4.739569] i915 0000:00:02.0: registered panic notifier
[ 4.794288] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
(Conclusion - i915 failure with current kernel. Boot fails to 'wallpaper only' after login.)

Working boot on Ubuntu-Mate install, same machine, using 3.16.0-11.16 kernel
alan@Ubuntu-Mate:~$ grep -i i915 /var/log/dmesg
[ 7.964054] i915 0000:00:02.0: irq 47 for MSI/MSI-X
[ 8.112029] [drm:i915_gem_init] *ERROR* Failed to initialize GPU, declaring it wedged
[ 9.350789] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[ 9.350790] i915 0000:00:02.0: registered panic notifier
[ 9.394907] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
alan@Ubuntu-Mate:~$
(Conclusion - i915 failure with current kernel but system apparently recovers to work normally)

[jerrylamos (jerrylamos)]

On Intel Core 2 Duo 3.0 gHz Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03)
Trying 3.17.0-rc3
3.16.0-11.iso actually boots to unity. First time in a month. Very shaky 1920x1024 mouse hardly works.
boots to desktop only. No unity. .iso did get unity, install didn't.
command line Install rc3 and booted, rc3 hangs. Power off.
boot rc3 nomodeset actually boots, unity and all.
rc3 settomgs thinks the VGA is Gallium 0.4 on llvmpipe (LLVM 3.4, 128 bits). No idea what that is.

Resolution is a peculiar 1280x1024 everything looks fat.
settings cannot change to anything else, what should work is 1360x768.

nomodeset is shades of ubuntu intrepid.....

[jerrylamos (jerrylamos)]

Well, 3.16.0-11 has booted to desktop only, and for the first time booted normally on Intel Core 2 Duo 3.0 gHz. rc3 kernel is also in /boot I select which kernel at boot time......and sets to 1360x768 which the rc3 nomodeset would not do.

.iso is
http://cdimage.ubuntu.com/cdimage/daily-live/current/utopic-desktop-amd64.iso 01-Sep-2014 08:58
which booted to unity pretty shaky but did install. See comment #31
First boot after install was to desktop only, did my usual install including update & dist-upgrade, and installed rc3.

Hmmm. I guess I could keep a count how many times unity comes up on a boot and how many times it doesn't.

[jerrylamos (jerrylamos)]

Next 3 boots unity/compiz failed.
Had to do nomodeset to post this comment.

[jerrylamos (jerrylamos)]

linux-image-3.16.0-12 booted O.K. several times this morning.
I wouldn't know whether there is actually a fix for compiz or just whether the timing race of compiz/x is better.....

So as of 3.16.0-12 this problem has not reproduced over several boots.....

BTW, 3.17...rc3 still fails unless nomodeset. Waiting for rc4.....

[Alan Fry (alan-fry)]

Regret that kernel 3.16.0-12 does NOT reliably resolve this problem.

See post #30 above. I get exactly the same result with the -12 kernel.

[jerrylamos (jerrylamos)]

4 September amd64 .iso boots to flashing desktop, no unity.

3.16.0-12 kernel in the .iso according to ls /boot fails to start unity.

My -11 updated to -12 does work.

Now the .iso is usually behind apt-get update. Past experience if the .iso isn't running correctly the install won't either. Not sure it's worth my while to install the non-unity .iso and try an update.

Bummer.

[jerrylamos (jerrylamos)]

U + 1 forums for last few days a number of people on a variety of hardware booting to black screen or command line or ....

Anything we can do to test anything?

Thanks.

[Joseph Salisbury (jsalisbury)]

Just to confirm, the 3.16.0-6 kernel does not exhibit this bug, but the 3.10.0-7 kernel does? If that is the case, can you test the following two upstream kernels:

v3.16-rc7: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16-rc7-utopic/
v3.16 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16-utopic/

The Ubuntu -6 kernel is based on rc7 and the -7 Ubuntu kernel is based off 3.16 final. I can bisect between these two versions if we confirm the first is good and the latter is bad.

[jerrylamos (jerrylamos)]

Joseph, will give them a try.

[Alan Fry (alan-fry)]

Pleased to advise that kernel 3.16.0-13-19, recieved by updates today appears to resolve the problems reported in posts #30 and #35 above.

[jerrylamos (jerrylamos)]

Joseph, tried the rc7 and the -7 kernels on a new install which is at -12 level. The .iso boots to desktop so I do a Ctrl-Alt-F1 for a command .ine. The .deb's were previously downloaded with a utopic -12 which works.

With the fresh .iso install, no updates, did dpkg -i on the rc7. Booted, hung before anything useful on screen.
If this is the kernel the 3.16.0-6 is based on, didn't work for me on the .iso at 3.16.0-12 level.

dpkg -i on the 3.16 final to the .iso at -12 level. The 3.16 final (base for the -7 kernel). Flashing desktop on and off. No go.

--------------------------------------------

Gave up and installed .iso at the 3.16.0-6 level. Runs fine for a development level.

Did dpkg -i on the rc7 and booted. Desktop only. If this is the same level as the -6 does not run the same here.

Rebooted with the 3.16.0-6 that came with the .iso. Runs fine like right now.

In times past I've been able to install debian kernels even on ubuntu.

No luck with the kernels in the post #38 on either installs at 3.16.0-6 level or at 3.16.0-12 level.

Maybe there's something I should be doing instead of just dpkg -i on the three deb files and rebooting?

------------------------------------------

Let me try Alan Fry's suggestion, install the 3.16-12 which is the latest .iso, boots to desktop only for me, and then apt-get update to 3.16.0-13.

Hmmm....Thanks for your efforts .

[jerrylamos (jerrylamos)]

As of 10 September, the amd64 daily build hasn't been built since 5 September and is still at the 3.16.0-12 level.
The .iso boots to desktop as usual. No compiz/unity.
From command line do apt-get update and then apt-get dist-upgrade, reboot at 3.16.0-14 whereupon compiz/unity work.
BTW, 3.17.0-rc4 unity/compiz work when added to the 3.16.0-14 install.

[jerrylamos (jerrylamos)]

As of 11 September, the daily(?)-live current amd64 .iso is still at 5 September, 3.16.0-12, boots to desktop no compiz/unity.

Daily-live pending amd64 was at 10 3.16.0-14, boots to compiz/unity fine. Installed fine (for a develompment image).

I haven't heard that there was any change in the Intel driver. Unity/compiz are under constant development.

I presume "pending" isn't ready for "current" and anything could happen....

[jerrylamos (jerrylamos)]

daily-live current now dated 11 September. Zsync vs. yesterday's daily-live pending updated said 82% complete.
.iso amd64 booted normally, unity panels O.K. kernel 3.16.0-14.
First daily-live current that booted O.K. since July.

So as of today, this bug did not occur.

[Alberto Salvia Novella (es20490446e)]

If you are still experiencing this bug, please set its status back to confirmed.

[Launchpad Janitor (janitor)]

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

[Launchpad Janitor (janitor)]

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

[Launchpad Janitor (janitor)]

[Expired for Unity because there has been no activity for 60 days.]