I am able to replicate the this bug 100% of the time by scrolling up and
down quickly in Google Image search results. The bug seems to be fixed
as early as 3.3.6 (maybe earlier). Appears to be a GPU hang. There are
three i915 related commits in 3.3.6.
--
You received this bug notification because
Timo, I'm building a test kernel with this patch committed in 3.3.5:
http://permalink.gmane.org/gmane.comp.freedesktop.xorg.drivers.intel/10832
I don't see it in 3.2.0-25 and the description appears relevent - the
patch applies a GPU hang fix for gen 6 (Sandy Bridge) to >= gen 6 (gen 7
including
Timo, our system froze with the patch - no good. We'll keep hacking from
our side as well. Let me know if we can help split up the work.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.ne
Timo, nice work! Your kernel is running beautifully here as well. Please
try to get this in -26. Are kernel SRU releases scheduled?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bug
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/873495
Title:
Xorg freeze on boot when installed in OEM mode after nvidia-current or
nvidia-current-updates are installed
To manage notifications
Public bug reported:
Occurs reliably with Sandy Bridge hardware.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: xorg 1:7.6+7ubuntu7
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus.0: Error: [E
** Summary changed:
- Xorg freeze on boot when installed in OEM mode after nvidia-current or
nvidia-current-updates are installed
+ LightDM fails to start when installed in OEM mode after nvidia-current or
nvidia-current-updates are installed
** Description changed:
- Occurs reliably with Sand
** Description changed:
Occurs reliably on fast Sandy Bridge hardware with a fast GPU - GTX
485M, GTX 560M or GTX 580M.
Appears to be a race condition. LightDM attempts to start before
/dev/nvidiactrl is created. As a workaround add "sleep 1 && service
lightdm start" to /etc/rc.local
We've found that adding "sleep 2" above "exec lightdm" in
/etc/init/lightdm.conf also resolves the booting issue (though we need
to test more cold boots). sleep 1 was adequate on reboots but failed on
some cold boots.
Doesn't explain why this only occurs in OEM mode.
--
You received this bug not
Yes, this bug still occurs and has expanded to include very fast Haswell
hardware with Intel graphics. This seems to be race condition where X is
not ready for lightDM to start. We suspect an upstart bug or
lightdm.conf config file issue. This fix works consistently:
-
We've found that adding "sle
AceLan, we are experiencing some issues with nVidia in OEM mode on
12.04. At this time, we have not determined if it's the same bug. We're
investigating and will follow up with additional information.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed
Acelan,
We are still experiencing the bug in Ubuntu 11.10 with your test kernel.
Please note, we are no longer shipping or testing OEM mode for Ubuntu
11.10 as of this week.
The bug is present in OEM mode on Ubuntu 12.04.
--
You received this bug notification because you are a member of Ubuntu-
** Also affects: nvidia-drivers-ubuntu
Importance: Undecided
Status: New
** Project changed: nvidia-drivers-ubuntu => system76
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers in Ubuntu.
https://bugs.launchpad.ne
This patch includes new Elantech models from previous patches and fixes
excessive wobble on the ETF1059 (ETF5900) model used in the System76
Pangolin Performance model. We've created a DKMS module that we're
distributing until the patch makes it upstream and into Ubuntu. You can
use the module wit
Hi Jamie,
Great find! With vga=799 my Serval boots on vt7 every time. As you noted
vga=799 is depreciated and replaced by gfxpayload. You can have the
correct boot image and start on VT7 by adding the following lines to
/etc/default/grub and then "sudo update-grub".
I have tested this on the
@Jamie,
I tested a Serval with a full 1080p HD LCD (1920x1080). Interestingly,
1600x900x32 provides a clean splash screen and starts on VT7.
GRUB_GFXMODE=1600x900x32
GRUB_GFXPAYLOAD_LINUX=1600x900x32
Also, it appears this bug is fixed in Maverick. However, the splash
screen when using nVidia's p
16 matches
Mail list logo
