** Changed in: linux (Ubuntu)
Status: Confirmed = Fix Released
** Changed in: linux (Ubuntu Trusty)
Status: Confirmed = Fix Released
** Changed in: linux (Ubuntu Utopic)
Status: Confirmed = Fix Released
** Changed in: linux (Ubuntu Vivid)
Status: Confirmed = Fix
No surprise but since the 14.04.2 20150217 images still have 3.16.0-30
generic they are affected.
Since it's a hardware specific corner issue I don't know if it's worth
mentioning in the release notes or not.
--
You received this bug notification because you are a member of Ubuntu-X,
which is
** Description changed:
I've been testing the Ubuntu GNOME Vivid daily images in anticipation of
Alpha 2 and I noticed that with this specific hardware I get no graphics
at all other than a blank screen (see attached photo):
AMD Sempron Processor LE-1250 @ 2.2 GHz
nVidia C61 [GeForce
OK I did some more testing last night and this AM, so here's a quick
recap to reduce any confusion (both for others and myself):
Vivid: This is fixed in 3.18.0-13 generic. I verified that this AM by
testing the Ubuntu GNOME Vivid 20150215 amd64 iso.
Utopic: This is fixed in 3.16.0-31 generic
Regarding Trusty with the OEM 3.13 series kernel: This is NOT fixed in
3.13.0-46-generic from trusty-proposed. That can be verified because
using the nouveau.config=NvMSI=0 boot parameter gets me past the screen
corruption/X freeze. So evidently the upstream fix has not yet trickled
down to the
Sorry to take so long getting back to this. The affected PC is usually
used as my media center but I've now been able to move it into my
testing suite so hopefully once 14.04.2 milestone testing is out of the
way I'll be able to respond more quickly and efficiently.
Regarding the screen
I was encountering some issues installing 14.04.1 which I'll get into
later, but for now I moved on to testing 14.04.2, this one installed w
/Ubuntu-GNOME 14.04.2 LTS Trusty Tahr - Release amd64 (20150203), and
while 3.16.0-30-generic was affected I pulled 3.16.0-31-generic from
trusty-proposed
@ Tim Lunn,
This is totally unrelated, but to be certain that Vivid is working
properly w/3.18.0-13-generic I've been using it to post all of these
messages and on the last boot apport presented me with a gdm error so I
accepted the automated reporting which is bug #1421991. Poorly written
for
It turns out that both 14.04 and 14.04.1 are affected by this bug. I had
to look in the installer log to see what version I'd begun with (and
have been running on that box as my stable OS) = Ubuntu 14.04 LTS
Trusty Tahr - Alpha i386 (20140129). So I was undoubtedly able to
install Trusty at that
Lance, this is getting a little confusing to follow, can you file separate bugs
for the corruption and lockups above.
The original nouveau.config=NvMSI=0 bug should be fixed in vivid now? is it
fixed in trusty 14.04.2?
--
You received this bug notification because you are a member of Ubuntu-X,
Hi Tim,
As far as I can tell ATM the only difference in most of these
crashes/freezes/screen-corruptions is the frequency with which they
occur and the screen color depending on what point during boot and/or
operation the freeze occurs.
Like this is the pic I included with original bug report:
I have been able to reproduce that a few times in a gnome-shell session
but it's not specific to any one task. It crashed/froze twice just
looking for logs and once again while launching Firefox. OTOH I can use
the classic session w/o a problem - in fact I'm streaming the nightly
news right now.
That looks like video corruption, and it is possible that gnome-classic
has some of the animations disabled compared to gnome-shell, but I can't
think of any other difference.
.xsession-errors is obsolete, logs will by default be in
~/.cache/upstart/gnome-session-GNOME.log under upstart boot or
@ Joseph Salisbury,
There seemed to be some improvement in Ubuntu GNOME Utopic with the
amd64 version of 3.16.7-031607-generic, at least I was able to boot that
kernel w/o adding the nouveau.config=NvMSI=0 boot parameter, but then
after spending a couple of minutes fiddling around when I
Perhaps oddly (perhaps not oddly at all) I decided to reboot and select
GNOME Classic rather than booting into the standard GNOME Shell and it
seems to work fine - no screen tearing or X-freezes under fairly heavy
use. So maybe nouveau itself is simply not capable of running GNOME
Shell.
I find
Lance, gnome-classic is gnome-shell with a bunch of extensions, so for
classic to work and Shell not does seem odd. Was the issue in gnome-
shell repeatable or a one of crash?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
@ Joseph Salisbury,
I'll be glad to do that but it'll be a couple of days due to prior
commitments.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/1412602
Title:
No live
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: xserver-xorg-video-nouveau (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects:
Commit 4761703 is in mainline as of v3.19-rc4. It was also sent to
stable.
Not applicable in upstream 3.13.
It is in upstream 3.16 as of v3.16.7-ckt5.
It is in upstream 3.18 as of v3.18.4.
Can folks affected by this bug test the following kernels to see if this
bug is fixed:
v3.16.7-ckt5:
This was fixed upstream with this patch:
http://git.kernel.org/cgit/linux/kernel/git/stable/stable-queue.git/tree/releases/3.18.4/drm-nv4c-mc-disable-msi.patch
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
Trusty 3.13.0-44 was OK but 3.13.0-45 is affected.
** Tags added: trusty
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/1412602
Title:
No live DE in Vivid using nouveau
The latest two daily builds are failing for what must be a totally
unrelated issue because they're also failing with different hardware so
I went back to testing the Ubuntu GNOME Alpha 2 live image and it does
boot successfully with the boot parameter nouveau.config=NvMSI=0. So do
we need to edit
I tried the 3.19.0-031900rc5-generic mainline kernel on that
installation and both mutter and compiz based DE's work OK with nouveau,
but the nvidia module fails to build properly against that kernel. I
haven't yet researched what kernel we intend to ship with Vivid.
I started some testing with
** Also affects: nouveau via
https://bugs.freedesktop.org/show_bug.cgi?id=87361
Importance: Unknown
Status: Unknown
** Tags added: kernel-fixed-upstream
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in
Looks like this might be
https://bugs.freedesktop.org/show_bug.cgi?id=87361
can you try disable MSI As mentioned in that bug report (kernel
paramater: nouveau.config=NvMSI=0).
** Bug watch added: freedesktop.org Bugzilla #87361
https://bugs.freedesktop.org/show_bug.cgi?id=87361
--
You
Oh, I forgot to mention that I have tried the nomodeset boot parameter
to no avail.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/1412602
Title:
No live DE in Vivid using
Here's what Ubuntu GNOME Vivid 20150119 i386 boots to when it should
display Try or Install. I was able to enter the advanced boot menu and
run check disc for defects so I know it's not just a bad burn.
** Attachment added: IMG_4799.JPG
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1412602
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu-X,
which is
28 matches
Mail list logo
