// timers list gets corrupted here and timer-2 gets
removed from list.
Fixes: https://bugs.freedesktop.org/show_bug.cgi?id=86288
Signed-off-by: Nikhil Mahale
Reviewed-by: Julien Cristau
v2: Apply warning fixes from Keith Packard
Reviewed-by: Aaron Plattner
Does it work if you use a path that doesn't have any spaces in it?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1220426
Title:
[nvidia-prime]Freeze while using touchpad
To manage notif
Ah, thanks for the clarification.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-180 in Ubuntu.
https://bugs.launchpad.net/bugs/269904
Title:
Screen refresh problems with nvidia cards
To manage notifications about thi
Christopher, is there some actual discussion somewhere where licensing
is called out as a problem, or are you just referring to Stephen's
comment #325? I'll bet it just that no one who has permission to push
updated packages has noticed this bug and I don't know how to attract
the attention of som
Is there still some concern about accepting the patch? It was indeed
authored by James Jones and signed off by him for public release.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-180 in Ubuntu.
https://bugs.launchpad.
As Daniel mentioned, the problem is in OpenGL. If you are willing to
run without it, you can work around the problem for now by disabling the
"glx" module in /etc/X11/xorg.conf by adding the following lines:
Section "Module"
Disable "glx"
EndSection
This issue was caused because the video dr
No, the Xid messages are not documented, they're internal error codes to
help us with debugging. In Anoop's case, all they really mean is that
the driver stopped hearing from the graphics card suddenly and was
unable to restore communications with it.
--
You received this bug notification becaus
Anoop, these symptoms sound very much like a hardware problem that
causes the GPU to sometimes lose contact with the rest of the system.
Please make sure your case is free of dust and that the fans are
unobstructed, that all connectors are seated firmly, and that your power
supply has a sufficientl
Thanks, Joakim. On the contrary, that's quite interesting. The first
four bytes should never be all 0xff if the GPU is configured correctly
by the kernel. If the kernel has misconfigured the GPU in such a way
that it cannot respond to register reads, the driver has no hope of
working.
--
You r
I think that's the wrong resource0 file (for bus 0 device 2, rather than bus 2
device 0). Probably easier to use the symlinks:
/sys/bus/pci/devices/:02:00.0/resource0
However, you can't call read() on those files, they can only be mmap'd.
/dev/mem should work, though. I would recommend read
@TJ: The BAR configuration registers are in the PCI configuration space.
I'm talking about the registeres accessed via memory read/write cycles
to the addresses configured there. E.g., open /dev/mem and read at the
offset that lspci reports for "Region 0" for your GPU. Alternatively,
mmap /sys/de
TJ, that rm_is_supported_device function reads registers that it sounds
like are reading back as 0x. You should be able to read the
DWORD at BAR0 offset 0. If it reads as 0x, then the GPU is not
configured correctly. You should be able to do that before even loading
the NVIDIA RM
xserver 1.10 doesn't exist yet, and the ABI it's going to use won't be
frozen until 1.10 RC2 (a.k.a 1.9.99.902) is released. Until then, the
NVIDIA driver can't assume that the ABI won't change in the future.
I pinged the people responsible for releases, but didn't hear anything
back. The offici
Please give 96.43.19 a try. It was just released, so it might be a
while before somebody packages it for Ubuntu.
--
ABI change in xorg 1.9 breaks legacy nvidia-96 drivers in Maverick
https://bugs.launchpad.net/bugs/626974
You received this bug notification because you are a member of Ubuntu-X,
w
The GPU is not responding correctly to CPU accesses, hence the nouveau
error message of, "Unsupported chipset 0x". This is not a
driver bug: it could be a bug in the kernel, or a hardware problem.
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: Confirmed => Invalid
--
Nvi
Crap, I didn't mean to add this. Marking invalid.
** Also affects: nvidia-drivers-ubuntu
Importance: Undecided
Status: New
** Changed in: nvidia-drivers-ubuntu
Status: New => Invalid
** Also affects: xfce4
Importance: Undecided
Status: New
** Changed in: nvidia-graph
This doesn't sound at all like a graphics driver bug, but rather a
communication problem between the various XFCE components. The driver
does not control the appearance of fonts or icons, but simply processes
the drawing requests sent to it by applications. Does the problem still
occur with the "
On Sat, Oct 02, 2010 at 11:38:49AM -0700, Aldo Maggi wrote:
> a...@paperino:~$ dpkg -l nvidia-173
>
> ii nvidia-173 173.14.27-0ubuntu1 NVIDIA
> binary Xorg driver, kernel module and VDPAU library
>
> should i uninstall it and get the 173.14.28 binary from nvidia site?
Please try 173.14.28.
--
/usr/lib/xorg/extra-modules/nvidia_drv.so: undefined symbol: miEmptyData
https://bugs.launchpad.net/bugs/626918
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-173 in ubuntu.
Please try 260.19.06:
http://www.nvnews.net/vbulletin/showthread.php?t=155137
--
nvidia 256.53 xorg-server 1.9.0 performance regression with antialiased text
https://bugs.launchpad.net/bugs/629910
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvid
"At least NVidias Aaron Plattner claims it is merely a regression in
xserver 1.9."
I didn't say that. All I said was that if an experiment shows that
using the same driver, xserver 1.8 is fast and xserver 1.9 is slow, that
it's not reasonable to immediately assume that t
A driver with support for the new ABI should be out relatively soon,
though I can't make any actual promises as to a release date.
If scrolling using the same driver but a different X server shows
different performance, it's highly likely that the regression is in the
X server and not the driver.
Hi Benjamin. This is the first I've heard of this bug, so I'll try to
take a look at it as soon as I can.
Please note that just checking for the NV-CONTROL extension is not
sufficient, because some screens may be using the NVIDIA driver while
others use different drivers. If the extension exists
Thanks, Philip. I've attached Bert's patch to our internal bug for
this, which is #357963.
--
nvidia-settings "Configure Display Device" menu should be drop-down list
instead of dialog box
https://bugs.launchpad.net/bugs/604525
You received this bug notification because you are a member of Ubun
Hi Tim. nvidia-settings hasn't generated an RgbPath line since 177.67.
Can you please confirm that the problem does not occur with the latest
version?
** Changed in: nvidia-settings (Ubuntu)
Status: New => Fix Released
--
nvidia-settings generates broken xorg.conf files
https://bugs.laun
Right, the code was added for xserver 1.7.0, so Lucid should work since
it ships a newer point release of the same server branch.
You mentioned Karmic, which ships xserver 1.6.4:
http://packages.ubuntu.com/karmic-updates/x11/xserver-common
I would not expect that to work correctly with Vino+Compi
The code I added relies on a feature I added to xserver 1.7 to work
correctly. It should still be broken in Karmic, since it ships xserver
1.6.
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx
driver using X.org
https://bugs.launchpad.net/bugs/353126
You receive
> while the screen updates under this setting, it was noticeably slower
than having visual effects set to none (no compiz)
This is expected. When no composite manager is running, the X server
sends damage events only for the parts of the screen that changed.
Because Compiz uses a much more comple
No, the legacy branches do not have the code to take advantage of the
code I added to the X server, and are unlikely to get it because those
branches are limited to support for new kernels and X servers, and
critical bug fixes only. This is basically a new feature. The latest
drivers do have code
Doug, the code to enable damage events for this sort of use case is only
available in relatively recent driver releases. The code in the X
server that allows it to work was only added in the xserver 1.7
timeframe.
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx
I looked into this today and found that the NVIDIA driver does not
correctly generate damage events for a given window when the OpenGL
rendering is actually happening to a child window. In this case, x11vnc
is listening for damage events on the root, but Compiz is rendering to
the Composite Overla
TiGR, please reinstall the 96.43.17 driver, try to start X again, run
nvidia-bug-report.sh, and attach the resulting nvidia-bug-report.log.gz
file here.
--
Mouse and keyboard stop working after selecting user
https://bugs.launchpad.net/bugs/553200
You received this bug notification because you ar
This is fixed in a release candidate. Reassigning to Alberto to update the
Ubuntu packages.
ftp://download.nvidia.com/XFree86/Linux-x86/96.43.17/
ftp://download.nvidia.com/XFree86/Linux-x86_64/96.43.17/
** Changed in: nvidia-graphics-drivers-96 (Ubuntu)
Assignee: Aaron Plattner
Darrin, what fix are you referring to? The fix for this bug has not yet
been released.
--
Mouse and keyboard stop working after selecting user
https://bugs.launchpad.net/bugs/553200
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-dr
I should also mention that there's no indication in the log file that
the NVIDIA driver is related. I don't think any of the usual suspects,
like crashes (SEGV or BUS), unresolved symbols (ABRT), or divides by
zero (FPE), can be blamed here. I would guess that some external
program is sending SIG
Please subscribe Daniel Dadap to NVIDIA bugs instead of me. He's our
support engineer now.
--
nvidia driver sometime does not load at boot
https://bugs.launchpad.net/bugs/532436
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-driver
NoOp unsubscribed, so the point is mostly moot, but the original report
is not the same symptom, it describes a black screen and an X server
restart *after* logging in. Bug #553200 is a hang or crash as soon as
the password prompt is displayed. In addition, Saša's report confirming
the original s
It should affect any card using the 96.43.* drivers.
--
Mouse and keyboard stop working after selecting user
https://bugs.launchpad.net/bugs/553200
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-96 in ubuntu.
__
*** This bug is a duplicate of bug 553200 ***
https://bugs.launchpad.net/bugs/553200
NoOp, I already mentioned in the other bug that I don't think electhor's
original problem is related. Electhor was using a GeForce 8600 GT,
which is not supported by the 96.43.* legacy driver, so can't have b
disco_stew: I don't know when an updated driver will be released. Once
a driver is released, I'll reassign this bug to Alberto to handle the
Ubuntu nvidia-96 package update. Presumably this bug would be an SRU
candidate, if it turns out that's necessary.
You ought to be able to work around this
NoOp, it looks like that bug got hijacked. This problem sounds
unrelated to the problem originally reported in that bug.
--
Mouse and keyboard stop working after selecting user
https://bugs.launchpad.net/bugs/553200
You received this bug notification because you are a member of Ubuntu-X,
which i
This should be fixed in the next legacy driver release.
** Changed in: nvidia-graphics-drivers-96 (Ubuntu)
Status: In Progress => Fix Committed
--
Mouse and keyboard stop working after selecting user
https://bugs.launchpad.net/bugs/553200
You received this bug notification because you are
I managed to track down the cause of this problem. I'll try to get it
fixed soon. It is indeed a bug in the NVIDIA X driver.
** Changed in: nvidia-graphics-drivers-96 (Ubuntu)
Assignee: Daniel Dadap (ddadap) => Aaron Plattner (aplattner)
** Changed in: nvidia-graphics-drivers-96
** Changed in: nvidia-graphics-drivers-96 (Ubuntu)
Assignee: Aaron Plattner (aplattner) => Daniel Dadap (ddadap)
--
Mouse and keyboard stop working after selecting user
https://bugs.launchpad.net/bugs/553200
You received this bug notification because you are a member of Ubuntu-X,
which
I can't reproduce this problem. I used the default Ubuntu GDM setup,
and I also tried installing xubuntu-gdm-theme. I don't think the latter
worked correctly, though because I get a boring purple background and a
little terminal picture at the top of the login prompt. Hopefully the
xubuntu theme
I'll try to take a look at this soon. It's suspicious that it started
occurring with a GDM update, but it'll take some digging to figure out
what's going wrong.
** Changed in: nvidia-graphics-drivers-96 (Ubuntu)
Assignee: (unassigned) => Aaron Plattner (aplattner)
Thanks Mario. I just made an 0.3 release with these changes:
http://lists.freedesktop.org/archives/xorg-
announce/2009-November/001200.html
It now builds the documentation too, so you'll probably want a libvdpau-
doc package at some point.
--
nvidia-180-libvdpau packages both libvdpau and libvd
> The library will look for drivers in /usr/lib/vdpau/libvdpau_.so
I'm sorry, that should have read /usr/lib/vdpau/libvdpau_.so.1
(i.e. versioned in case we ever change the libvdpau <-> driver interface)
--
nvidia-180-libvdpau packages both libvdpau and libvdpau_nvidia
https://bugs.launchpad.net/
Mario, does this layout look okay to you? I'd like to make an 0.3
release tonight.
Yet-to-be-released NVIDIA drivers will install:
/usr/lib/libvdpau.so -> libvdpau.so.1
/usr/lib/libvdpau.so.1 -> libvdpau.so.190.NN
/usr/lib/libvdpau.so.190.NN
/usr/lib/libvdpau_nvidia.so -> vdpau/libvdpau_nvidia.s
I just pushed a change that should address the concerns. Please let me
know if this is sufficient or if additional changes are necessary.
http://cgit.freedesktop.org/~aplattner/libvdpau/commit/?id=0537b13e292bc772e984872a3986e41fb51f9258
--
nvidia-180-libvdpau packages both libvdpau and libvdpau
lewmur, .nvidia-settings-rc is not an executable, it's a configuration
file that nvidia-settings uses to save user preferences for the server
configuration. Wearing my "Ubuntu user" hat, I would personally prefer
not having it save things like my brightness and contrast settings in
root's home dir
It's a kernel parameter. The README entry I was referring to is this one:
ftp://download.nvidia.com/XFree86/Linux-x86/185.18.14/README/chapter-09.html#kva_exhaustion
It appears that the message changed, but I believe this is the same
problem. The "RmInitAdaptor failed" messages are a direct resu
Here's the problem:
[ 30.912314] vmap allocation failed: use vmalloc= to increase size.
Please see the section in the README about this error.
** Changed in: nvidia-graphics-drivers-180 (Ubuntu)
Status: Incomplete => Invalid
--
X: NVidia 8800 GT not being initialized correctly
https://b
How large is your cursor? This looks like typical corruption that is
caused by a fundamental incompatibility between GLX and the X server's
software cursor code. If it's larger than 64x64, please try using a
smaller cursor. It doesn't look that big from the screenshot, but it
could have a lot of
Whenever you see the message, "Failed to initialize the NVIDIA graphics
device," you need to check your kernel log to see why the kernel module
couldn't be initialized. Your best bet is to reproduce the problem, run
nvidia-bug-report.sh, and then attach the resulting log.
** Changed in: nvidia-gr
This is not a bug in the graphics driver -- the X server tells the
driver which screens' cursors to display, what they should look like,
and where to place them. If the cursor is appearing in the wrong place
or on the wrong screen, then the bug is almost certainly in the X server
itself.
--
Curs
56 matches
Mail list logo
