[Kernel-packages] [Bug 556782]
If you're reading this bug and have this issue, it's been open for nearly three years, and isn't likely to be fixed, as far as I can tell. If 3d acceleration is important to you, it's almost definitely worth it to get some hardware that is better supported. I went with Intel graphics -- there's a lot less likelihood that support will be dropped for that, since Intel's more helpful than ATI regarding open-source drivers for their graphics hardware. Well, Brian, its true regarding older hardware, lets not be blind about all the post x1*** - 6*** cards, they are actually okay. Regardless, the RS690M was listed as supported, I bought hardware that I thought would be supported for that specific reason, and then that changed, and that leaves me with no experience or reason to recommend ATI or the radeon driver at this point, and plenty of reason to recommend against it. ..the stuff that is new now becomes old later. ..why should I think that my experience with any other ATI card should be different? ..at least on the Intel side, there's the blessing (and support) of the chip maker. Also, 3D is important is a bit exaggerated, because 3D pipeline and *everything* except this bug work really fine. No disagreement there. I've got an Intel graphics card that works superbly, and there are others out there with nVidia and ATI cards that run great, too. What I was said was saying was (indented, so that the if statements and their subjective clauses are more apparent): * If you're reading this and have this issue * This issue has been open for nearly three years * It isn't likely to be fixed, from what I can tell * If 3d is important to you * It is almost definitely worth it to get some hardware that is better supported. ..I stand by that statement. There are many factors in play on modern desktop for it to just work, but this only one bug really damages it. *nod* and a lot of them work fine, and this one doesn't. ..a perfectly functional car with a broken drive shaft that no one knows how to fix is still valuable -- it's just not valuable to someone who wants to drive a car, unless that person knows how to fix it, or can sell that car, and get another car which many people know how to fix, and which appears less likely to break. ..I'm not looking at this and thinking That's bad work they've done, I'm looking at it and saying No one has had the time, know-how, and the access to the hardware to fix this, so if you are waiting for it to get done, my opinion is that you're better off buying more compatible hardware in this particular case. ..then again, all it takes is someone who does have the time, know-how, and hardware to fix this, and who wishes to donate their work. ..if someone does do that -- thank you. ..that specifically won't benefit me at this point, but thank you just on the general principle of it, and for the people that it will benefit. ..and thank you to everyone else who has contributed to Linux, X, and all the layers in between and on top -- it's phenomenal work that provides a genuine alternative to the proprietary operating systems that are out there. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/556782 Title: [rs690m] [Gateway] Graphics corruption with ati x1200 Status in The Linux Kernel: Confirmed Status in X.org XServer - ATI gfx chipset driver: Fix Released Status in “linux” package in Ubuntu: Incomplete Bug description: [Edit] This bug has been around for a bit over a year now, and has gotten rather long, so this is a brief summary. There is a memory corruption issue that affects users of the rs690m, to varying degrees. For many most people, it makes the desktop unusable. Workaround: *Note: This is a workaround, not a fix. It will give you a usable system. [Natty]: Regression: This workaround now only provides 2d/software rendering, and one must either: * Choose choose the Ubuntu Classic session from the GDM Login screen or * Install the unity-2d package. [code] sudo su echo options radeon modeset=0 /etc/modprobe.d/radeon-kms.conf exit [/code] Note that this doesn't totally fix the issue, but brings your desktop to a workable state. Freedesktop.org has dealt with one bug having to do with graphics corruption on the rs690m. That bug has been fixed, but the issue of graphics corruption in general has not been resolved. A new bug has been opened with freedesktop.org to continue pushing through the resolution of this issue. [/edit] ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: xorg 1:7.5+3ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-19-generic i686 Architecture: i386 Date: Tue Apr 6 12:58:29 2010 DkmsStatus: Error: [Errno 2] No such file or directory InstallationMedia: Ubuntu 9.10 Karmic
[Kernel-packages] [Bug 556782]
(In reply to comment #70) If setting the vramlimit does work (I'm unable to test it at this point since I no longer have the hardware) than that's a reasonable option. Up until the time I had to get something else, none of the proposed solutions had worked for me -- but if a functional workaround is present, that's often preferable to buying new hardware. It is reported as a valid workaround on this very bug report. Has anyone else tried it? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/556782 Title: [rs690m] [Gateway] Graphics corruption with ati x1200 Status in The Linux Kernel: Confirmed Status in X.org XServer - ATI gfx chipset driver: Fix Released Status in “linux” package in Ubuntu: Incomplete Bug description: [Edit] This bug has been around for a bit over a year now, and has gotten rather long, so this is a brief summary. There is a memory corruption issue that affects users of the rs690m, to varying degrees. For many most people, it makes the desktop unusable. Workaround: *Note: This is a workaround, not a fix. It will give you a usable system. [Natty]: Regression: This workaround now only provides 2d/software rendering, and one must either: * Choose choose the Ubuntu Classic session from the GDM Login screen or * Install the unity-2d package. [code] sudo su echo options radeon modeset=0 /etc/modprobe.d/radeon-kms.conf exit [/code] Note that this doesn't totally fix the issue, but brings your desktop to a workable state. Freedesktop.org has dealt with one bug having to do with graphics corruption on the rs690m. That bug has been fixed, but the issue of graphics corruption in general has not been resolved. A new bug has been opened with freedesktop.org to continue pushing through the resolution of this issue. [/edit] ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: xorg 1:7.5+3ubuntu1 ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1 Uname: Linux 2.6.32-19-generic i686 Architecture: i386 Date: Tue Apr 6 12:58:29 2010 DkmsStatus: Error: [Errno 2] No such file or directory InstallationMedia: Ubuntu 9.10 Karmic Koala - Release i386 (20091028.5) MachineType: Gateway LT31 ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.32-19-generic root=UUID=617a7a50-d35f-4b03-8bf1-f91ec024381b ro quiet splash ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: xorg dmi.bios.date: 06/18/2009 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: v1.3201 dmi.board.name: SJM11-YK dmi.board.vendor: Gateway dmi.board.version: Not Applicable dmi.chassis.type: 10 dmi.chassis.vendor: Gateway dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrv1.3201:bd06/18/2009:svnGateway:pnLT31:pvrNotApplicable:rvnGateway:rnSJM11-YK:rvrNotApplicable:cvnGateway:ct10:cvrN/A: dmi.product.name: LT31 dmi.product.version: Not Applicable dmi.sys.vendor: Gateway system: distro: Ubuntu codename: lucid architecture: i686 kernel: 2.6.32-19-generic [lspci] 01:05.0 VGA compatible controller [0300]: ATI Technologies Inc RS690M [Radeon X1200 Series] [1002:791f] Subsystem: Acer Incorporated [ALI] Device [1025:028c] To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/556782/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1254897] Re: CVE-2013-4591
** Description changed: Buffer overflow in the __nfs4_get_acl_uncached function in fs/nfs/nfs4proc.c in the Linux kernel before 3.7.2 allows local users to cause a denial of service (memory corruption and system crash) or possibly have unspecified other impact via a getxattr system call for the system.nfs4_acl extended attribute of a pathname on an NFSv4 filesystem. - Break-Fix: - 7d3e91a89b7adbc2831334def9e494dd9892f9af + Break-Fix: 1f1ea6c2d9d8c0be9ec56454b05315273b5de8ce + 7d3e91a89b7adbc2831334def9e494dd9892f9af -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-armadaxp in Ubuntu. https://bugs.launchpad.net/bugs/1254897 Title: CVE-2013-4591 Status in “linux” package in Ubuntu: Invalid Status in “linux-armadaxp” package in Ubuntu: Invalid Status in “linux-ec2” package in Ubuntu: Invalid Status in “linux-fsl-imx51” package in Ubuntu: Invalid Status in “linux-lts-backport-maverick” package in Ubuntu: New Status in “linux-lts-backport-natty” package in Ubuntu: New Status in “linux-lts-quantal” package in Ubuntu: Invalid Status in “linux-lts-raring” package in Ubuntu: Invalid Status in “linux-lts-saucy” package in Ubuntu: Invalid Status in “linux-mvl-dove” package in Ubuntu: Invalid Status in “linux-ti-omap4” package in Ubuntu: New Status in “linux” source package in Lucid: New Status in “linux-armadaxp” source package in Lucid: Invalid Status in “linux-ec2” source package in Lucid: New Status in “linux-fsl-imx51” source package in Lucid: Invalid Status in “linux-lts-backport-maverick” source package in Lucid: New Status in “linux-lts-backport-natty” source package in Lucid: New Status in “linux-lts-quantal” source package in Lucid: Invalid Status in “linux-lts-raring” source package in Lucid: Invalid Status in “linux-lts-saucy” source package in Lucid: Invalid Status in “linux-mvl-dove” source package in Lucid: Invalid Status in “linux-ti-omap4” source package in Lucid: Invalid Status in “linux” source package in Precise: New Status in “linux-armadaxp” source package in Precise: New Status in “linux-ec2” source package in Precise: Invalid Status in “linux-fsl-imx51” source package in Precise: Invalid Status in “linux-lts-backport-maverick” source package in Precise: New Status in “linux-lts-backport-natty” source package in Precise: New Status in “linux-lts-quantal” source package in Precise: New Status in “linux-lts-raring” source package in Precise: Invalid Status in “linux-lts-saucy” source package in Precise: Invalid Status in “linux-mvl-dove” source package in Precise: Invalid Status in “linux-ti-omap4” source package in Precise: New Status in “linux” source package in Quantal: New Status in “linux-armadaxp” source package in Quantal: New Status in “linux-ec2” source package in Quantal: Invalid Status in “linux-fsl-imx51” source package in Quantal: Invalid Status in “linux-lts-backport-maverick” source package in Quantal: New Status in “linux-lts-backport-natty” source package in Quantal: New Status in “linux-lts-quantal” source package in Quantal: Invalid Status in “linux-lts-raring” source package in Quantal: Invalid Status in “linux-lts-saucy” source package in Quantal: Invalid Status in “linux-mvl-dove” source package in Quantal: Invalid Status in “linux-ti-omap4” source package in Quantal: New Status in “linux” source package in Raring: Invalid Status in “linux-armadaxp” source package in Raring: Invalid Status in “linux-ec2” source package in Raring: Invalid Status in “linux-fsl-imx51” source package in Raring: Invalid Status in “linux-lts-backport-maverick” source package in Raring: New Status in “linux-lts-backport-natty” source package in Raring: New Status in “linux-lts-quantal” source package in Raring: Invalid Status in “linux-lts-raring” source package in Raring: Invalid Status in “linux-lts-saucy” source package in Raring: Invalid Status in “linux-mvl-dove” source package in Raring: Invalid Status in “linux-ti-omap4” source package in Raring: New Status in “linux” source package in Saucy: Invalid Status in “linux-armadaxp” source package in Saucy: Invalid Status in “linux-ec2” source package in Saucy: Invalid Status in “linux-fsl-imx51” source package in Saucy: Invalid Status in “linux-lts-backport-maverick” source package in Saucy: New Status in “linux-lts-backport-natty” source package in Saucy: New Status in “linux-lts-quantal” source package in Saucy: Invalid Status in “linux-lts-raring” source package in Saucy: Invalid Status in “linux-lts-saucy” source package in Saucy: Invalid Status in “linux-mvl-dove” source package in Saucy: Invalid Status in “linux-ti-omap4” source package in Saucy: New Status in “linux” source package in Trusty: Invalid Status in “linux-armadaxp” source package in Trusty: Invalid Status in “linux-ec2” source package in Trusty: Invalid
[Kernel-packages] [Bug 1169143] Re: Headset support on some Dell machines
LP: #1249956 collects the info machines with this bug -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1169143 Title: Headset support on some Dell machines Status in HWE Next Project: In Progress Status in “linux” package in Ubuntu: Fix Released Status in “linux-lts-raring” package in Ubuntu: In Progress Status in “pulseaudio” package in Ubuntu: Fix Released Status in “pulseaudio” source package in Precise: Fix Released Status in “pulseaudio” source package in Raring: In Progress Bug description: [SRU Justification] Several new hardware has either headset jacks or headphone-or-mic jacks, where the system cannot detect what has been plugged in. E g, for such a headset jack you can either plug in a headphone or a headset, but since the system cannot tell which one it is, you have to manually tell the system whether you want to use the internal or external mic. In the case of a headphone-or-mic jack, you can have the jack functioning as either a headphone or a mic, but not as a headset. Without this patch, PulseAudio would not detect the jack correctly, and not making all options available to the user. [Regression Potential] is very low: this only affects machines with the specific name Headphone Mic Jack or Headset Mic Jack, which started to appear for a few machines in the 3.5 kernel. People who are running 12.04.0 or 12.04.1 will be unaffected. More machines are coming in the 3.10 kernel, so this is also a preparation for making certification easier later on. [Test case] On an affected machine, plug in something into the jack. Then go to Sound Settings and note what options there are: e g, for a headset jack, you should be able to select both external and internal mic manually. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1169143/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
