It seems you're running quantal with the wrong nouveau driver.
The nouveau driver you're running is the xorg-edgers version for precise.
So, switch to xorg-edgers for quantal and if that doesn't solve your
problem then purge xorg-edgers.
--
You received this bug notification because you are a
Well, it might be relevant when running a mainstream precise version.
In this case you should report this issue to the xorg crack pushers team as the
ppa says:
For questions and bugs with software in this PPA please contact xorg crack
pushers.
--
You received this bug notification because you
Works with kernel 3.5.0-14 too so seems to have been fixed.
** Changed in: libdrm (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1039125
Title:
I made some further investigations for the nouveau driver today.
Kernels 3.5.0-10 to 3.5.0-12:
The issue is present with a corrupted screen and massive logging of
PFIFO_CACHE_ERROR messages.
Kernel 3.5.0-13
The issue seems gone, i.e the nouveau driver again!
It seems that the fixes for kernel
For the record this proprietary driver works just fine:
nvidia-current 304.43-0ubuntu2
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1039125
Title:
[drm] nouveau :02:00.0:
I'm attaching the kern.log when running the 3.5.0-11 kernel.
** Attachment added: kern.log
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1039125/+attachment/3271727/+files/kern.log
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
@dino99
vblank only works for some nvidia graphic cards (not mine) but worth testing as
a workaround.
I guess .udeb packages exist in the repos but not visible as those are
special stripped ditto packages for special use to save ram. The kernel
uses those instead of the more memory consuming
Another workaround to avoid this drm issue is to remove the grub splash
option.
** Description changed:
Screen corruption occurs at start up and reboot, for
- login screen
- desktop screen
Prerequisities:
- running the nouveau driver
- - running the 3.5.0-10 and -11 kernels
+ -
** Description changed:
Screen corruption occurs at start up and reboot, for
- login screen
- desktop screen
Prerequisities:
- running the nouveau driver
- running the 3.5.0-10 and -11 kernels
At non-autologin one can type the login password blindly but just to
enter a
** Description changed:
Screen corruption occurs at start up and reboot, for
- login screen
- desktop screen
Prerequisities:
- running the nouveau driver
- running the 3.5.0-10 and -11 kernels
At non-autologin one can type the login password blindly but just to
enter a
The following messages in the kern.log seem to cause this issue:
Aug 22 00:25:01 ltop1 kernel: [ 32.421438] [drm] nouveau :02:00.0: fail
set_domain
Aug 22 00:25:01 ltop1 kernel: [ 32.421444] [drm] nouveau :02:00.0:
validate vram_list
Aug 22 00:25:01 ltop1 kernel: [ 32.421447]
Public bug reported:
Screen corruption occurs at start up and reboot, for
- login screen
- desktop screen
Prerequisities:
- running the nouveau driver
- running the 3.5.0-10 and -11 kernels
At non-autologin one can type the login password blindly but just to
enter a corrupted desktop screen.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1039125
Title:
[drm] nouveau :02:00.0: PFIFO_CACHE_ERROR - Ch 2/2 Mthd 0x0800
Data 0x
To manage notifications about this bug go
Thanks for the link confirming it's an nvidia bug. Maybe it's doable to
port the xorg-edgers nvidia patch to quantal.
You're right about the headers and a more correct workaround would
have been to copy system.h from a 3.2 kernel, Anyway this proposed
workaround works too.
--
You received this
Public bug reported:
Installing the kernel 3.4.0-1.2 fails to build the nvidia-current module
due to missing kernel header files.
Workaround:
Copy the missing header files from arm
cd /usr/src/linux-headers-3.4.0-1/arch
sudo cp arm/include/asm/system.h x86/include/asm/
sudo cp
--
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.net/bugs/993506
Title:
nvidia-current 295.40-0ubuntu1: nvidia-current kernel module failed to
build
To manage notifications about this
It seems to be fixed now in Oneiric Beta 1.
$ jockey-text -l
xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, Enabled,
In use)
kmod:nvidia_current - nvidia_current (Proprietary, Disabled, Not in use)
and under Additional Drivers it now says:
This driver is activated and
Great, then I'm marking this bug as Invalid as it's resolved :-)
** Changed in: xorg-server (Ubuntu)
Status: Confirmed = Invalid
--
On my first attempt to log in, GDM crashes and restarts.
https://bugs.launchpad.net/bugs/626171
You received this bug notification because you are a member
Mesa 7.9 that is required seems to have been postponed to Natty Narwhal
(11.04).
For those who want to try out the Maverick Netbook Edition (UNE) and are
stuck with an ATI board that does cause a white screen there may be a
workaround by installing the xorg-edgers for Maverick, of course on your
Jon, my suggestion is that you reinstall using the beta-version to see
if the bug still exits.
I've made a number of new installationen lately and have not been able
to reproduce this bug. A lot of things can happen during the development
cycle and as you've done using dist-upgrade each time is
Some observations.
If I login using the desktop mouse both to select the user and to
confirm the password X does not crash. But then using the Enter key for
one of those actions immediatelly crashes X the first time and gdm is
restarted now running on VT8 instead of VT7 where VT7 here unveils the
As far as I know I'm running the classic r300c driver.
The extension GL_ARB_texture_non_power_of_two seems to be disabled by
default and when enabling that one
(MESA_EXTENSION_OVERRIDE=GL_ARB_texture_non_power_of_two unity) UNE is
started and the left-side panel (dock) gets visible but with
This bug seems to have been narrowed down to the AMD/ATI graphic
drivers.
Packages concerned thus are:
xserver-xorg-video-ati
xserver-xorg-video-radeonhd
I confirm this behaviour for a Radeon 9800 Pro (R350) that runs on the
radeon driver and marking the source package xserver-xorg-video-ati as
23 matches
Mail list logo
