[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for unity (Ubuntu) because there has been no activity for 60
days.]
** Changed in: unity (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for Unity because there has been no activity for 60 days.]
** Changed in: unity
Status: Incomplete = Expired
--
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/1359299
Title:
If you are still experiencing this bug, please set its status back to
confirmed.
** Changed in: unity (Ubuntu)
Status: Confirmed = Incomplete
** Changed in: unity (Ubuntu)
Importance: Undecided = Medium
** Changed in: unity
Status: Confirmed = Incomplete
--
You received this
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
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.
--
You received this
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,
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:
Joseph, will give them a try.
--
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/1359299
Title:
utopic 3.16.0-9 iso boots to desktop no unity
Status in Unity:
Confirmed
Status in “linux”
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,
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.
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.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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
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.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: unity
Status: New = Confirmed
--
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/1359299
Title:
utopic 3.16.0-9 iso boots to desktop no unity
Status in Unity:
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]
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.
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
Next 3 boots unity/compiz failed.
Had to do nomodeset to post this comment.
--
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/1359299
Title:
utopic 3.16.0-9 iso boots to desktop no unity
Thanks. If I can do any testing let me know.
--
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/1359299
Title:
utopic 3.16.0-9 iso boots to desktop no unity
Status in “linux” package in
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.
--
You received this bug notification because you are a member
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
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
** Tags added: needs-bisect
--
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/1359299
Title:
utopic 3.16.0-9 iso boots to desktop no unity
Status in “linux” package in Ubuntu:
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
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.
--
You received this bug notification because you are a
@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
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
And just to confirm, booting with a prior kernel version will prevent
the bug from happening?
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete
--
You received this bug notification because you are a member of
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
@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
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
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
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
** Package changed: linux (Ubuntu) = unity (Ubuntu)
** Changed in: unity (Ubuntu)
Status: Confirmed = New
--
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/1359299
Title:
utopic
35 matches
Mail list logo
