[Ubuntu-x-swat] [Bug 192508] Re: mouse keys turns on randomly
I'm facing the same issue with the following configuration: - ubuntu 10.04.1 32bit, with remote desktop enabled (vino version 2.28.2-0ubuntu2) - ubuntu 10.04.1 64bit, connecting to the above computer with vinagre (version 2.30.2-0ubuntu1) The mouse keys activate on the first computer (the VNC server) Based on the above comments and my personal experience, I don't think it could simply be some accidental Shift-NumLock -- 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/192508 Title: mouse keys turns on randomly ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 564617] Re: Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. Error referencing VRAM ctxdma: -12. Worked in alpha 3 and in karmic
The problem is still the same with the RC of lucid. - on first boot on the liveCD, I had the ubuntu logo, and then the grey lines symptom (see the photo of comment #4) - on second boot on the liveCD, I added the nouveau.noaccel=1 in the startup parameters, which allowed me to boot succesfully - on third and following boots, on this same liveCD, I don't have the ubuntu logo at all (the screen stays blank) -- Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. Error referencing VRAM ctxdma: -12. Worked in alpha 3 and in karmic https://bugs.launchpad.net/bugs/564617 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 564617] Re: Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. Error referencing VRAM ctxdma: -12. Worked in alpha 3 and in karmic
At least, if it's not possible or too complicated/risky before the final release, the video card should be blacklisted for acceleration, as it has been done for other cards : see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/544088 It seems to be called the noaccel quirk. I think it's still better to have an unaccelerated video than no video at all... -- Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. Error referencing VRAM ctxdma: -12. Worked in alpha 3 and in karmic https://bugs.launchpad.net/bugs/564617 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 564617] Re: Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. Error referencing VRAM ctxdma: -12. Worked in alpha 3 and in karmic
Christopher was right : I opened the upstream bug too quickly. I saw the same behavior on Fedora 13 beta, and thought these 2 distributions used very recent versions of nouveau. I was wrong : the problem seems to be already solved upstream. As suggested by Christopher, I enabled the xorg-edgers PPA https://edge.launchpad.net/~xorg-edgers/+archive/ppa and upgraded. Now my lucid beta 2 installation starts without any additional boot parameter. The PPA version number of libdrm is 2.4.20+git20100404.c7650003-0ubuntu0sarvatt3 (instead of 2.4.18-1ubuntu3) xserver-xorg-video-nouveau version is 1:0.0.15+git20100416.40636169-0ubuntu0sarvatt instead of 1:0.0.15+git20100219+9b4118d-0ubuntu5 The versions bundled with Fedora 13 beta are : xorg-x11-drv-nouveau 1:0.0.16-2.20100218git2964702.fc13 libdrm 2.4.19-1.fc13 IF the problem with Fedora is the same one (some people told me it could be another one), that would probably give a hint on where the fix might be : between versions 2.4.19-1.fc13 and 2.4.20+git20100404.c7650003-0ubuntu0sarvatt3. I know those versions are from different distros, so what I say is not completely true. But if we assume the fix comes from upstream (and not from a distro-specific patch), it should be between versions 2.4.19-1 and 2.4.20+git20100404.c7650003 Would it be possible to upgrade libdrm to 2.4.20 before the final release of lucid? Or else backport the fix (if we manage to find it : I might try to help but I'm no expert)? -- Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. Error referencing VRAM ctxdma: -12. Worked in alpha 3 and in karmic https://bugs.launchpad.net/bugs/564617 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 564617] [NEW] Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. Error referencing VRAM ctxdma: -12. Worked in alpha 3 and in karmic
Public bug reported: Binary package hint: xserver-xorg-video-nouveau I can't start the lucid beta 2 liveCD on a computer with a Nvidia GeForce 6200 SE (NV44A rev A1) : the screen stays blank after booting. It works properly with a lucid alpha 3 liveCD, and with a karmic liveCD. I managed to install the beta 2 on this computer through the alternate CD : the behavior is the same when booting on the hard drive. I installed all the updates (as of 16th april 2040) : same behavior I experience the precise same behavior with Fedora live : Fedora 12 live boots correctly (but relies on nv driver), Fedora 13 beta live gives the same blank screen (and also uses nouveau driver). I think this is a regression in the nouveau graphic driver : the version bundled with lucid alpha 3 works, the one with lucid beta 2 (or fedora 13 beta) does not. Here is an excerpt of the dmesg on beta 2 : nouveau :03:00.0: RAMHT space exhausted. ch=0 nouveau :03:00.0: Error referencing VRAM ctxdma: -12 nouveau :03:00.0: gpuobj -12 This error message does not appear when using lucid alpha 3. ** Affects: xserver-xorg-video-nouveau (Ubuntu) Importance: Undecided Status: New -- Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. Error referencing VRAM ctxdma: -12. Worked in alpha 3 and in karmic https://bugs.launchpad.net/bugs/564617 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 564617] Re: Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. Error referencing VRAM ctxdma: -12. Worked in alpha 3 and in karmic
** Attachment added: Dmesg when booting on lucid beta 2 (with all updates) http://launchpadlibrarian.net/44417313/dmesg-beta2 -- Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. Error referencing VRAM ctxdma: -12. Worked in alpha 3 and in karmic https://bugs.launchpad.net/bugs/564617 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 564617] Re: Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. Error referencing VRAM ctxdma: -12. Worked in alpha 3 and in karmic
** Attachment added: Dmesg when booting on lucid alpha 3 http://launchpadlibrarian.net/44417372/dmesg-alpha3 -- Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. Error referencing VRAM ctxdma: -12. Worked in alpha 3 and in karmic https://bugs.launchpad.net/bugs/564617 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 564617] Re: Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. Error referencing VRAM ctxdma: -12. Worked in alpha 3 and in karmic
Maybe this is related : before these error lines appear the following lines in dmesg : agpgart-nvidia :00:00.0: AGP 3.0 bridge agpgart: modprobe tried to set rate=x12. Setting to AGP3 x8 mode. agpgart-nvidia :00:00.0: putting AGP V3 device into 8x mode nouveau :03:00.0: putting AGP V3 device into 8x mode They appear only in beta 2, not in alpha 3. My video card is indeed plugged in a AGP port, that supports x8 mode. The motherboard is a Asus A7N8X-E deluxe and AGP mode x8 is enabled in the BIOS -- Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. Error referencing VRAM ctxdma: -12. Worked in alpha 3 and in karmic https://bugs.launchpad.net/bugs/564617 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 564617] Re: Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. Error referencing VRAM ctxdma: -12. Worked in alpha 3 and in karmic
Rarely, the screen doesn't stay blank : I can see the ubuntu logo, and then it shows a weird screen of grey lines (see attached photo) It happened only twice, and without changing anything to the configuration, boot options or BIOS Also, the first time I started this computer this morning, it reached the ubuntu desktop, but froze just after (no ctrl-alt-F1 available or anything). I have to insist on the fact that I don't have any of these behaviors on karmic, or in lucid alpha 3, or in fedora 12. I don't think it is caused by a damaged hardware. ** Attachment added: Photo of the grey lines that sometimes appear http://launchpadlibrarian.net/44418709/DSC08993.JPG -- Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. Error referencing VRAM ctxdma: -12. Worked in alpha 3 and in karmic https://bugs.launchpad.net/bugs/564617 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 564617] Re: Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. Error referencing VRAM ctxdma: -12. Worked in alpha 3 and in karmic
When the screen stays blank, ubuntu is not completely frozen : if I push the power button (without holding it), the hard disk flashes a few seconds and then it powers down : looks like a proper shutdown I found a temporary workaround by adding startup parameters in grub : if I add nouveau.modeset=0 nouveau.noaccel=1 blacklist=vga16fb, the desktop appears properly and ubuntu seems to work fine. -- Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. Error referencing VRAM ctxdma: -12. Worked in alpha 3 and in karmic https://bugs.launchpad.net/bugs/564617 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 564617] Re: Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. Error referencing VRAM ctxdma: -12. Worked in alpha 3 and in karmic
Adding nouveau.noaccel=1 in the grub parameters is sufficient to work around the problem -- Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. Error referencing VRAM ctxdma: -12. Worked in alpha 3 and in karmic https://bugs.launchpad.net/bugs/564617 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 564617] Re: Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. Error referencing VRAM ctxdma: -12. Worked in alpha 3 and in karmic
Adding nouveau.noaccel=1 in the grub parameters of the fedora 13 beta livecd makes it work too -- Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. Error referencing VRAM ctxdma: -12. Worked in alpha 3 and in karmic https://bugs.launchpad.net/bugs/564617 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 564617] Re: Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. Error referencing VRAM ctxdma: -12. Worked in alpha 3 and in karmic
** Attachment added: Dmesg when booting on lucid beta 2 with nouveau.noaccel=1 http://launchpadlibrarian.net/44427545/dmesg-beta2-noaccel -- Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. Error referencing VRAM ctxdma: -12. Worked in alpha 3 and in karmic https://bugs.launchpad.net/bugs/564617 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 564617] Re: Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. Error referencing VRAM ctxdma: -12. Worked in alpha 3 and in karmic
** Description changed: Binary package hint: xserver-xorg-video-nouveau - I can't start the lucid beta 2 liveCD on a computer with a Nvidia GeForce 6200 SE (NV44A rev A1) : the screen stays blank after booting. + I can't start the lucid beta 2 liveCD on a computer with a Nvidia GeForce 6200 (NV44A rev A1) : the screen stays blank after booting. It works properly with a lucid alpha 3 liveCD, and with a karmic liveCD. I managed to install the beta 2 on this computer through the alternate CD : the behavior is the same when booting on the hard drive. I installed all the updates (as of 16th april 2040) : same behavior I experience the precise same behavior with Fedora live : Fedora 12 live boots correctly (but relies on nv driver), Fedora 13 beta live gives the same blank screen (and also uses nouveau driver). I think this is a regression in the nouveau graphic driver : the version bundled with lucid alpha 3 works, the one with lucid beta 2 (or fedora 13 beta) does not. Here is an excerpt of the dmesg on beta 2 : - nouveau :03:00.0: RAMHT space exhausted. ch=0 - nouveau :03:00.0: Error referencing VRAM ctxdma: -12 - nouveau :03:00.0: gpuobj -12 + nouveau :03:00.0: RAMHT space exhausted. ch=0 + nouveau :03:00.0: Error referencing VRAM ctxdma: -12 + nouveau :03:00.0: gpuobj -12 This error message does not appear when using lucid alpha 3. -- Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. Error referencing VRAM ctxdma: -12. Worked in alpha 3 and in karmic https://bugs.launchpad.net/bugs/564617 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 564617] Re: Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. Error referencing VRAM ctxdma: -12. Worked in alpha 3 and in karmic
I opened a bug on the nouveau bugtracker : https://bugs.freedesktop.org/show_bug.cgi?id=27706 ** Bug watch added: freedesktop.org Bugzilla #27706 http://bugs.freedesktop.org/show_bug.cgi?id=27706 -- Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. Error referencing VRAM ctxdma: -12. Worked in alpha 3 and in karmic https://bugs.launchpad.net/bugs/564617 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 564617] Re: Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. Error referencing VRAM ctxdma: -12. Worked in alpha 3 and in karmic
** Also affects: fedora Importance: Undecided Status: New ** Also affects: nouveau via http://bugs.freedesktop.org/show_bug.cgi?id=27706 Importance: Unknown Status: Unknown -- Regression : no image when starting lucid beta 2, with Nvidia Geforce6200 NV44A. Error referencing VRAM ctxdma: -12. Worked in alpha 3 and in karmic https://bugs.launchpad.net/bugs/564617 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-nouveau in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 353126] Re: Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org prior to release 7.5
It works great on my ubuntu 10.04 alpha 3 (with Intel drivers), accessed from an ubuntu 9.04 VNC client, or a ubuntu 10.04 alpha 3 client. With compiz fully activated, the screen refreshes correctly, and I can see the desktop effects through VNC -- Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org prior to release 7.5 https://bugs.launchpad.net/bugs/353126 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 486837] Re: Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic
I now think that the freeze issue might come from a hardware problem : I made a test that worked well : - I removed the overclocking of my CPU (so that the CPU uses its normal speed). The overclocking was stable for years, but one never knows. My graphic card is not overclocked - I reduced the screen resolution to 1024x768 (instead of 1600x1200) - I used the DVI output instead of the VGA output (with the same flat screen) This time, the youtube video was stable. The reduced CPU speed made it choppy, but at least the machine did not freeze. That makes me think it could be simply related to the overclocking. Why did the freeze not happen when not using the proprietary nvidia driver? Maybe because the open-source driver does not use some hardware acceleration. Maybe in this case the AGP port draws more current or something similar. Why did the freeze happen only after the upgrade to karmic? Maybe a coincidence (even if I would find it surprising). Maybe the recent versions of the nvidia driver and/or the flash plugin make use of a feature that was not used before, and that leads to the problems with overclocking I only can make assumptions, but at least I have a workaround -- Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic https://bugs.launchpad.net/bugs/486837 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-180 in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 486837] Re: Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic
It does not seem to be related to the screen resolution (tried both 1024x768 and 1600x1200), or to the VGA/DVI port (tried both). So I assume it was related to the overclocking -- Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic https://bugs.launchpad.net/bugs/486837 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-180 in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 486837] Re: Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic
I change the status to invalid, as it seems to come from the overclocking of my CPU ** Changed in: nvidia-graphics-drivers-180 (Ubuntu) Status: New = Invalid -- Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic https://bugs.launchpad.net/bugs/486837 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-180 in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 486837] Re: Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic
At least I solved the problem of blank screen after hibernation : I found in the forums that I needed to put NvAGP 1 in my xorg.conf. See https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-173/+bug/34043 Now I can resume correctly from hibernation. But I still have freezes when watching flash videos -- Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic https://bugs.launchpad.net/bugs/486837 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-180 in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 486837] Re: Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic
This time, I reproduced the freeze on a ubuntu 9.04 liveCD. I installed version 180.44 of the nvidia proprietary drivers, and version 10.0.42.34 of adobe proprietary flash plugin. The computer froze again while displaying the Home movie. One interesting thing : I never experienced such freezes when I was running ubuntu 9.04 installed on my PC, before upgrading to 9.10. That leads me to 2 possible assumptions : - the problem comes from a software bug, that appeared in a recent version of nvidia drivers, or in a recent version of flash - the problem comes from a hardware issue, that appeared precisely when I upgraded to ubuntu 9.10 If it's a software bug in flash plugin, this bug appeared in version 10.0.32.18. Because I was certainly using the previous one (10.0.22.87) when I was using ubuntu 9.04. Cf http://changelogs.ubuntu.com/changelogs/pool/multiverse/f/flashplugin-nonfree/flashplugin-nonfree_10.0.42.34ubuntu0.9.04.1/changelog I'm not very confident that it could be a bug in nvidia drivers, because version 180.44 is the one I was certainly using with ubuntu 9.04. Cf http://changelogs.ubuntu.com/changelogs/pool/restricted/n/nvidia-graphics-drivers-180/nvidia-graphics-drivers-180_180.44-0ubuntu1/changelog I don't think it could be a hardware problem : it would be surprising that it happens only after upgrading to 9.10, and not when using the nvidia open-source drivers. -- Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic https://bugs.launchpad.net/bugs/486837 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-180 in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 486837] Re: Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic
I just made a test on a ubuntu 9.04 liveCD : installed nvidia drivers version 180.44, and version 10.0.22.87 of flash plugin (through http://pubmirrors.reflected.net/debian-multimedia/pool/main/f/flash- player/flashplayer-mozilla_10.0.22.87-0.0_i386.deb) The system froze after a few minutes watching Home. I suppose it shows that the problem does not come from a bug in flash plugin that appeared after 10.0.22.87 version... Too bad, I was really thinking it could be it. -- Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic https://bugs.launchpad.net/bugs/486837 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-180 in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 486837] Re: Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic
Today, I tried to watch the same youtube video in a virtualized environment. I made this test with Virtualbox 3.1.2 (non-OSE version), on two different virtual machines : - one under Ubuntu 10.04 alpha 2, on which I only installed the proprietary flash plugin (version 10.0.42.34). I did not install the guest additions on this one - one under Ubuntu 9.10 (with all updates installed), on which I also installed the same proprietary flash plugin (same version). I also installed the guest additions on this machine, and activated the 3D opengl acceleration of virtualbox I did not experience any freeze : not in a virtual machine, and not in my physical computer It seems to confirm that the problem only occurs when using both the nvidia proprietary drivers and the adobe flash proprietary plugin -- Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic https://bugs.launchpad.net/bugs/486837 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-180 in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 486837] Re: Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic
Same freezes after the kernel upgrade to 2.6.31-17.54 -- Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic https://bugs.launchpad.net/bugs/486837 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-180 in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 486837] Re: Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic
I reproduced the same problem on a ubuntu 9.10 liveCD : After booting on the liveCD, I installed version 185 of the nvidia proprietary drivers, as proposed a few seconds after the boot. Then, I installed the ubuntu-restricted-extras package (in order to have the proprietary flash plugin). I launched firefox, and opened the link above (Home movie in youtube) : the computer froze after a few minutes playing the movie. If it helps, here is the lspci output regarding my video card : 03:00.0 VGA compatible controller: nVidia Corporation NV44A [GeForce 6200] (rev a1) -- Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic https://bugs.launchpad.net/bugs/486837 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-180 in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 486837] Re: Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic
The flashplugin-nonfree update of yesterday (to version 10.0.42.34ubuntu0.9.10.1) does not solve the problem of freezes with flash videos -- Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic https://bugs.launchpad.net/bugs/486837 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-180 in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 486837] Re: Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic
The xorg updates of today did not solve the problem of wake up after an hibernation : the screen is blank on wake-up -- Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic https://bugs.launchpad.net/bugs/486837 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-180 in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 486837] Re: Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic
I was hoping that the recent kernel upgrade (to 2.6.31-15) could help with this issue. It does not : still the same freezes with flash videos. I can reproduce that easily : - activate nvidia proprietary drivers - open a flash video, for example http://www.youtube.com/watch?v=jqxENMKaeCU and watch it in full screen mode - after a few minutes, the freeze happens and all you can do is manually reboot the computer -- Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic https://bugs.launchpad.net/bugs/486837 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-180 in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 486837] Re: Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic
Watching the same youtube video from Totem works without freezing. Same thing for another fullscreen streaming video with VLC : no freeze. So I suspect something related to Adobe Flash and/or nvidia drivers -- Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic https://bugs.launchpad.net/bugs/486837 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-180 in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 486837] Re: Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic
Here is what a grep gives me in /var/log for the NVRM string : /var/log/dmesg:[ 16.933681] NVRM: loading NVIDIA UNIX x86 Kernel Module 185.18.36 Fri Aug 14 17:18:04 PDT 2009 /var/log/dmesg.0:[ 13.398677] NVRM: loading NVIDIA UNIX x86 Kernel Module 185.18.36 Fri Aug 14 17:18:04 PDT 2009 /var/log/kern.log:Nov 22 11:42:50 pcgeek kernel: [ 12.124545] NVRM: loading NVIDIA UNIX x86 Kernel Module 185.18.36 Fri Aug 14 17:18:04 PDT 2009 /var/log/kern.log:Nov 22 17:22:21 pcgeek kernel: [ 15.345567] NVRM: loading NVIDIA UNIX x86 Kernel Module 185.18.36 Fri Aug 14 17:18:04 PDT 2009 /var/log/kern.log:Nov 22 19:24:57 pcgeek kernel: [ 3701.184039] NVRM: Xid (0003:00): 8, Channel 0020 /var/log/kern.log:Nov 22 18:26:21 pcgeek kernel: [ 17.619952] NVRM: loading NVIDIA UNIX x86 Kernel Module 185.18.36 Fri Aug 14 17:18:04 PDT 2009 /var/log/kern.log:Nov 22 20:21:16 pcgeek kernel: [ 1242.523445] NVRM: loading NVIDIA UNIX x86 Kernel Module 185.18.36 Fri Aug 14 17:18:04 PDT 2009 /var/log/kern.log:Nov 22 20:23:18 pcgeek kernel: [ 11.622098] NVRM: loading NVIDIA UNIX x86 Kernel Module 185.18.36 Fri Aug 14 17:18:04 PDT 2009 /var/log/kern.log:Nov 22 20:52:04 pcgeek kernel: [ 16.084277] NVRM: loading NVIDIA UNIX x86 Kernel Module 185.18.36 Fri Aug 14 17:18:04 PDT 2009 /var/log/kern.log:Nov 22 21:27:22 pcgeek kernel: [ 13.047830] NVRM: loading NVIDIA UNIX x86 Kernel Module 185.18.36 Fri Aug 14 17:18:04 PDT 2009 /var/log/kern.log:Nov 22 22:40:33 pcgeek kernel: [ 4024.907797] NVRM: loading NVIDIA UNIX x86 Kernel Module 185.18.36 Fri Aug 14 17:18:04 PDT 2009 /var/log/kern.log:Nov 22 23:23:35 pcgeek kernel: [ 10.877873] NVRM: loading NVIDIA UNIX x86 Kernel Module 185.18.36 Fri Aug 14 17:18:04 PDT 2009 /var/log/kern.log:Nov 23 07:18:19 pcgeek kernel: [ 11.568953] NVRM: loading NVIDIA UNIX x86 Kernel Module 185.18.36 Fri Aug 14 17:18:04 PDT 2009 /var/log/kern.log:Nov 23 16:03:26 pcgeek kernel: [ 11.931277] NVRM: loading NVIDIA UNIX x86 Kernel Module 185.18.36 Fri Aug 14 17:18:04 PDT 2009 /var/log/kern.log:Nov 23 22:06:57 pcgeek kernel: [ 13.398677] NVRM: loading NVIDIA UNIX x86 Kernel Module 185.18.36 Fri Aug 14 17:18:04 PDT 2009 /var/log/kern.log:Nov 24 07:28:23 pcgeek kernel: [ 16.933681] NVRM: loading NVIDIA UNIX x86 Kernel Module 185.18.36 Fri Aug 14 17:18:04 PDT 2009 /var/log/kern.log.1:Nov 17 07:17:26 pcgeek kernel: [ 16.044435] NVRM: loading NVIDIA UNIX x86 Kernel Module 185.18.36 Fri Aug 14 17:18:04 PDT 2009 /var/log/kern.log.1:Nov 18 07:19:29 pcgeek kernel: [ 14.703952] NVRM: loading NVIDIA UNIX x86 Kernel Module 185.18.36 Fri Aug 14 17:18:04 PDT 2009 /var/log/kern.log.1:Nov 19 07:28:10 pcgeek kernel: [ 16.137322] NVRM: loading NVIDIA UNIX x86 Kernel Module 185.18.36 Fri Aug 14 17:18:04 PDT 2009 /var/log/kern.log.1:Nov 20 07:28:08 pcgeek kernel: [ 12.142568] NVRM: loading NVIDIA UNIX x86 Kernel Module 185.18.36 Fri Aug 14 17:18:04 PDT 2009 /var/log/kern.log.1:Nov 21 08:42:40 pcgeek kernel: [ 11.168483] NVRM: loading NVIDIA UNIX x86 Kernel Module 185.18.36 Fri Aug 14 17:18:04 PDT 2009 /var/log/kern.log.1:Nov 21 13:56:39 pcgeek kernel: [ 33.487021] NVRM: loading NVIDIA UNIX x86 Kernel Module 185.18.36 Fri Aug 14 17:18:04 PDT 2009 /var/log/kern.log.1:Nov 21 17:46:19 pcgeek kernel: [ 22.812073] NVRM: loading NVIDIA UNIX x86 Kernel Module 185.18.36 Fri Aug 14 17:18:04 PDT 2009 /var/log/kern.log.1:Nov 21 22:47:35 pcgeek kernel: [ 12.416117] NVRM: loading NVIDIA UNIX x86 Kernel Module 185.18.36 Fri Aug 14 17:18:04 PDT 2009 /var/log/kern.log.1:Nov 22 08:54:03 pcgeek kernel: [ 12.157922] NVRM: loading NVIDIA UNIX x86 Kernel Module 185.18.36 Fri Aug 14 17:18:04 PDT 2009 /var/log/messages:Nov 22 11:42:50 pcgeek kernel: [ 12.124545] NVRM: loading NVIDIA UNIX x86 Kernel Module 185.18.36 Fri Aug 14 17:18:04 PDT 2009 /var/log/messages:Nov 22 17:22:21 pcgeek kernel: [ 15.345567] NVRM: loading NVIDIA UNIX x86 Kernel Module 185.18.36 Fri Aug 14 17:18:04 PDT 2009 /var/log/messages:Nov 22 18:26:21 pcgeek kernel: [ 17.619952] NVRM: loading NVIDIA UNIX x86 Kernel Module 185.18.36 Fri Aug 14 17:18:04 PDT 2009 /var/log/messages:Nov 22 20:21:16 pcgeek kernel: [ 1242.523445] NVRM: loading NVIDIA UNIX x86 Kernel Module 185.18.36 Fri Aug 14 17:18:04 PDT 2009 /var/log/messages:Nov 22 20:23:18 pcgeek kernel: [ 11.622098] NVRM: loading NVIDIA UNIX x86 Kernel Module 185.18.36 Fri Aug 14 17:18:04 PDT 2009 /var/log/messages:Nov 22 20:52:04 pcgeek kernel: [ 16.084277] NVRM: loading NVIDIA UNIX x86 Kernel Module 185.18.36 Fri Aug 14 17:18:04 PDT 2009 /var/log/messages:Nov 22 21:27:22 pcgeek kernel: [ 13.047830] NVRM: loading NVIDIA UNIX x86 Kernel Module 185.18.36 Fri Aug 14 17:18:04 PDT 2009 /var/log/messages:Nov 22 22:40:33 pcgeek kernel: [ 4024.907797] NVRM: loading NVIDIA UNIX x86 Kernel Module 185.18.36 Fri Aug 14 17:18:04 PDT 2009 /var/log/messages:Nov 22 23:23:35 pcgeek kernel: [ 10.877873] NVRM: loading
[Ubuntu-x-swat] [Bug 486837] [NEW] Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic
Public bug reported: I did a standard dist-upgrade from jaunty to karmic. I have a nvidia graphic card and was using the standard proprietary drivers (proposed by jockey-gtk), and with desktop effects activated. Since the upgrade, I experience freezes that seem to be related to this proprietary driver : - whenever I hibernate the PC, and start it again, the boot seems fine, but the screen stays blank after the resume - the system freezes after a few minutes watching any flash video content (with the proprietary flash) I'm using version 185.18.36-0ubuntu9 of nvidia-glx-185. Both problems are solved if I disable this proprietary driver through jockey-gtk. I ran two tests : - upgrade to version 190.42 of the drivers (by adding the ppa deb http://ppa.launchpad.net/nvidia-vdpau/ppa/ubuntu karmic main ) - keep version 185.18.36 and disable desktop effects In both cases, the freezes are still there. The only workaround I found to avoid them was to disable the proprietary driver I found this bug : https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-180/+bug/474917 but it does not seem to be a duplicate, as my dkms status reports : nvidia, 185.18.36, 2.6.31-14-generic, i686: installed I did not find anything relevant in /var/log about these freezes ** Affects: nvidia-graphics-drivers-180 (Ubuntu) Importance: Undecided Status: New -- Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic https://bugs.launchpad.net/bugs/486837 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-180 in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 486837] Re: Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic
The version of adobe-flashplugin I use is 10.0.32.18-1karmic2, within firefox 3.5.5. The freezes make the computer completely unresponsive : the mouse does not move, ctrl-alt-F1 does nothing. The only thing I can do is a manual power-off -- Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic https://bugs.launchpad.net/bugs/486837 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-180 in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 486837] Re: Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic
I forgot to mention that everything was fine before upgrading to karmic (at least for flash videos, I did not use the hibernate feature at that time). The flash video does not necessarily have to be in fullscreen mode. And it works for a few minutes before freezing the system. -- Freezes with nvidia-glx-185 or -190 after upgrade from jaunty to karmic https://bugs.launchpad.net/bugs/486837 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-180 in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
