[Kernel-packages] [Bug 1570802] Re: ATI Radeon not working: from no rendering to system freeze
@ nicola: Did you have activated the option "download updates during installation" ? If not, is the system updated to most current state? Background: see Release Notes/Known issues [1] since you have a Intel Skylake-iGPU I've seen that you are also capable to speak other languages from your profile, so if you like to lear more how to use the Hybrid-graphics on open-source drivers you can find some content on a local-community-wiki [2]. Please note also that AMDgpu is considered to still receive fixes [3]. Sound doesn't work for me with 4.6 RC4. It does with Mainline-Kernel 4.5.2 [1] https://wiki.ubuntu.com/XenialXerus/ReleaseNotes#A6th_gen_Intel_Core_CPUs_and_llvmpipe_software_rasterizer [2] http://wiki.ubuntu-it.org/Hardware/Video/GraficaIbrida/Prime] [3] https://www.phoronix.com/scan.php?page=news_item=Linux-4.6-APR21-DRM-Fixes -- 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/1570802 Title: ATI Radeon not working: from no rendering to system freeze Status in linux package in Ubuntu: Confirmed Bug description: Release: Ubuntu 16.04 LTS (pre-release daily build) Hardware: Dell Inspiron 15 5000 Series (Intel(R)) - 5559, hybrid graphics: Intel integrated + AMD Radeon(TM) R5 M335 4GB DDR3 GPU. I can't get the GPU to work properly. Examples: glxgears not showing output or crashing, blender causing the system to freeze. What I've tried: 1] with the default configuration (integrated Intel card activated by default), glxgears works fine. 2] DRI_PRIME=1 glxgears: THe windows gets drawn, but no content is rendered 3] Output from xrandr --listproviders: Providers: number : 3 Provider 0: id: 0x66 cap: 0x9, Source Output, Sink Offload crtcs: 4 outputs: 3 associated providers: 2 name:Intel Provider 1: id: 0x3f cap: 0x6, Sink Output, Source Offload crtcs: 0 outputs: 0 associated providers: 2 name:HAINAN @ pci::01:00.0 Provider 2: id: 0x3f cap: 0x6, Sink Output, Source Offload crtcs: 0 outputs: 0 associated providers: 2 name:HAINAN @ pci::01:00.0 So I change with: xrandr --setprovideroffloadsink 0x3f 0x66 4] DRI_PRIME=1 glxgears now gives: radeon: Failed to allocate virtual address for buffer: radeon:size : 65536 bytes radeon:alignment : 4096 bytes radeon:domains : 4 radeon:va: 0x0080 radeon: Failed to deallocate virtual address for buffer: radeon:size : 65536 bytes radeon:va: 0x0080 radeon: Failed to allocate virtual address for buffer: radeon:size : 65536 bytes radeon:alignment : 4096 bytes radeon:domains : 4 radeon:va: 0x0080 radeon: Failed to deallocate virtual address for buffer: radeon:size : 65536 bytes radeon:va: 0x0080 radeonsi: Failed to create a context. radeon: Failed to allocate virtual address for buffer: radeon:size : 65536 bytes radeon:alignment : 4096 bytes radeon:domains : 4 radeon:va: 0x0080 radeon: Failed to deallocate virtual address for buffer: radeon:size : 65536 bytes radeon:va: 0x0080 radeon: Failed to allocate virtual address for buffer: radeon:size : 65536 bytes radeon:alignment : 4096 bytes radeon:domains : 4 radeon:va: 0x0080 radeon: Failed to deallocate virtual address for buffer: radeon:size : 65536 bytes radeon:va: 0x0080 radeonsi: Failed to create a context. X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 154 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Value in failed request: 0x0 Serial number of failed request: 30 Current serial number in output stream: 32 "Apport" for this bug was run after going back to "xrandr --setprovideroffloadsink 0x66 0x3f". ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-generic 4.4.0-18.34 [modified: boot/vmlinuz-4.4.0-18-generic] ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicola 1402 F pulseaudio CurrentDesktop: Unity Date: Fri Apr 15 11:55:17 2016 HibernationDevice: RESUME=UUID=449a6774-7719-42e0-ad0d-0941778d2be5 InstallationDate: Installed on 2016-04-14 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160414) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 8087:07dc Intel Corp. Bus 001 Device 007: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader
[Kernel-packages] [Bug 1570802] Re: ATI Radeon not working: from no rendering to system freeze
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/1570802 Title: ATI Radeon not working: from no rendering to system freeze Status in linux package in Ubuntu: Confirmed Bug description: Release: Ubuntu 16.04 LTS (pre-release daily build) Hardware: Dell Inspiron 15 5000 Series (Intel(R)) - 5559, hybrid graphics: Intel integrated + AMD Radeon(TM) R5 M335 4GB DDR3 GPU. I can't get the GPU to work properly. Examples: glxgears not showing output or crashing, blender causing the system to freeze. What I've tried: 1] with the default configuration (integrated Intel card activated by default), glxgears works fine. 2] DRI_PRIME=1 glxgears: THe windows gets drawn, but no content is rendered 3] Output from xrandr --listproviders: Providers: number : 3 Provider 0: id: 0x66 cap: 0x9, Source Output, Sink Offload crtcs: 4 outputs: 3 associated providers: 2 name:Intel Provider 1: id: 0x3f cap: 0x6, Sink Output, Source Offload crtcs: 0 outputs: 0 associated providers: 2 name:HAINAN @ pci::01:00.0 Provider 2: id: 0x3f cap: 0x6, Sink Output, Source Offload crtcs: 0 outputs: 0 associated providers: 2 name:HAINAN @ pci::01:00.0 So I change with: xrandr --setprovideroffloadsink 0x3f 0x66 4] DRI_PRIME=1 glxgears now gives: radeon: Failed to allocate virtual address for buffer: radeon:size : 65536 bytes radeon:alignment : 4096 bytes radeon:domains : 4 radeon:va: 0x0080 radeon: Failed to deallocate virtual address for buffer: radeon:size : 65536 bytes radeon:va: 0x0080 radeon: Failed to allocate virtual address for buffer: radeon:size : 65536 bytes radeon:alignment : 4096 bytes radeon:domains : 4 radeon:va: 0x0080 radeon: Failed to deallocate virtual address for buffer: radeon:size : 65536 bytes radeon:va: 0x0080 radeonsi: Failed to create a context. radeon: Failed to allocate virtual address for buffer: radeon:size : 65536 bytes radeon:alignment : 4096 bytes radeon:domains : 4 radeon:va: 0x0080 radeon: Failed to deallocate virtual address for buffer: radeon:size : 65536 bytes radeon:va: 0x0080 radeon: Failed to allocate virtual address for buffer: radeon:size : 65536 bytes radeon:alignment : 4096 bytes radeon:domains : 4 radeon:va: 0x0080 radeon: Failed to deallocate virtual address for buffer: radeon:size : 65536 bytes radeon:va: 0x0080 radeonsi: Failed to create a context. X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 154 (GLX) Minor opcode of failed request: 3 (X_GLXCreateContext) Value in failed request: 0x0 Serial number of failed request: 30 Current serial number in output stream: 32 "Apport" for this bug was run after going back to "xrandr --setprovideroffloadsink 0x66 0x3f". ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-generic 4.4.0-18.34 [modified: boot/vmlinuz-4.4.0-18-generic] ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicola 1402 F pulseaudio CurrentDesktop: Unity Date: Fri Apr 15 11:55:17 2016 HibernationDevice: RESUME=UUID=449a6774-7719-42e0-ad0d-0941778d2be5 InstallationDate: Installed on 2016-04-14 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160414) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 8087:07dc Intel Corp. Bus 001 Device 007: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5559 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic.efi.signed root=UUID=1505ea58-b580-4f52-b408-26294cb50da1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-18-generic N/A linux-backports-modules-4.4.0-18-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/16/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.6 dmi.board.name: 0664DJ dmi.board.vendor: Dell Inc. dmi.board.version: A00
[Kernel-packages] [Bug 1559576] Re: Ubuntu GNOME boots to black screen when using proprietary Nvidia drivers on a laptop with Optimus
** Summary changed: - Ubuntu Gnome boots to black screen when using proprietary Nvidia drivers on a laptop with Optimus + Ubuntu GNOME boots to black screen when using proprietary Nvidia drivers on a laptop with Optimus -- 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/1559576 Title: Ubuntu GNOME boots to black screen when using proprietary Nvidia drivers on a laptop with Optimus Status in gdm: New Status in Ubuntu GNOME: New Status in gdm3 package in Ubuntu: Triaged Status in linux package in Ubuntu: Invalid Status in gdm3 source package in Xenial: Triaged Status in linux source package in Xenial: Invalid Bug description: Using latest Ubuntu Gnome x64 daily build with all updates installed. Lenovo Z70-80 laptop with Nvidia 840M, BIOS updated to latest version, secure boot and other potentially problematic BIOS settings disabled. Can only see a black screen instead of a log-in screen after boot completes when proprietary Nvidia drivers are installed. Regular Ubuntu works absolutely fine on the same machine with the same driver version. Attempting to use older drivers on Ubuntu Gnome made no difference. Bug is affecting more than just me. We were talking about workarounds in ubuntuforums. User fthx claims that switching to lightdm fixes the issue http://ubuntuforums.org/showthread.php?t=2317628=13457703#post13457703 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-14-generic 4.4.0-14.30 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-14-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Sat Mar 19 23:19:21 2016 HibernationDevice: RESUME=UUID=4f8fb76c-f99d-4c54-8a67-eed0653d8eb6 InstallationDate: Installed on 2016-03-19 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160318) MachineType: LENOVO 80FG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-14-generic.efi.signed root=UUID=572a19f6-7324-4269-ad36-7ffc9919f7a2 ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-14-generic N/A linux-backports-modules-4.4.0-14-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: ABCN96WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo Z70-80 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z70-80 dmi.modalias: dmi:bvnLENOVO:bvrABCN96WW:bd09/22/2015:svnLENOVO:pn80FG:pvrLenovoZ70-80:rvnLENOVO:rnLenovoZ70-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoZ70-80: dmi.product.name: 80FG dmi.product.version: Lenovo Z70-80 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1559576/+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 1559576] Re: Ubuntu Gnome boots to black screen when using proprietary Nvidia drivers on a laptop with Optimus
Similar issue covered on Archlinux-bugbase: https://bugs.archlinux.org/task/47140 ([bumblebee] can not handle nvidia-modeset.ko) -- 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/1559576 Title: Ubuntu Gnome boots to black screen when using proprietary Nvidia drivers on a laptop with Optimus Status in gdm: New Status in Ubuntu GNOME: New Status in gdm3 package in Ubuntu: Triaged Status in linux package in Ubuntu: Invalid Status in gdm3 source package in Xenial: Triaged Status in linux source package in Xenial: Invalid Bug description: Using latest Ubuntu Gnome x64 daily build with all updates installed. Lenovo Z70-80 laptop with Nvidia 840M, BIOS updated to latest version, secure boot and other potentially problematic BIOS settings disabled. Can only see a black screen instead of a log-in screen after boot completes when proprietary Nvidia drivers are installed. Regular Ubuntu works absolutely fine on the same machine with the same driver version. Attempting to use older drivers on Ubuntu Gnome made no difference. Bug is affecting more than just me. We were talking about workarounds in ubuntuforums. User fthx claims that switching to lightdm fixes the issue http://ubuntuforums.org/showthread.php?t=2317628=13457703#post13457703 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-14-generic 4.4.0-14.30 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-14-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Sat Mar 19 23:19:21 2016 HibernationDevice: RESUME=UUID=4f8fb76c-f99d-4c54-8a67-eed0653d8eb6 InstallationDate: Installed on 2016-03-19 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160318) MachineType: LENOVO 80FG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-14-generic.efi.signed root=UUID=572a19f6-7324-4269-ad36-7ffc9919f7a2 ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-14-generic N/A linux-backports-modules-4.4.0-14-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: ABCN96WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo Z70-80 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z70-80 dmi.modalias: dmi:bvnLENOVO:bvrABCN96WW:bd09/22/2015:svnLENOVO:pn80FG:pvrLenovoZ70-80:rvnLENOVO:rnLenovoZ70-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoZ70-80: dmi.product.name: 80FG dmi.product.version: Lenovo Z70-80 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1559576/+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 1559576] Re: Ubuntu Gnome boots to black screen when using proprietary Nvidia drivers on a laptop with Optimus
@ TIm The above mentioned just works in VirtuaBox. Nvidia driver is using the new nvidia-drm and NOT module (nvidia.ko). subscribing Alberto to look into that. -- 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/1559576 Title: Ubuntu Gnome boots to black screen when using proprietary Nvidia drivers on a laptop with Optimus Status in gdm: New Status in Ubuntu GNOME: New Status in gdm3 package in Ubuntu: Triaged Status in linux package in Ubuntu: Invalid Status in gdm3 source package in Xenial: Triaged Status in linux source package in Xenial: Invalid Bug description: Using latest Ubuntu Gnome x64 daily build with all updates installed. Lenovo Z70-80 laptop with Nvidia 840M, BIOS updated to latest version, secure boot and other potentially problematic BIOS settings disabled. Can only see a black screen instead of a log-in screen after boot completes when proprietary Nvidia drivers are installed. Regular Ubuntu works absolutely fine on the same machine with the same driver version. Attempting to use older drivers on Ubuntu Gnome made no difference. Bug is affecting more than just me. We were talking about workarounds in ubuntuforums. User fthx claims that switching to lightdm fixes the issue http://ubuntuforums.org/showthread.php?t=2317628=13457703#post13457703 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-14-generic 4.4.0-14.30 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-14-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Sat Mar 19 23:19:21 2016 HibernationDevice: RESUME=UUID=4f8fb76c-f99d-4c54-8a67-eed0653d8eb6 InstallationDate: Installed on 2016-03-19 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160318) MachineType: LENOVO 80FG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-14-generic.efi.signed root=UUID=572a19f6-7324-4269-ad36-7ffc9919f7a2 ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-14-generic N/A linux-backports-modules-4.4.0-14-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: ABCN96WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo Z70-80 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z70-80 dmi.modalias: dmi:bvnLENOVO:bvrABCN96WW:bd09/22/2015:svnLENOVO:pn80FG:pvrLenovoZ70-80:rvnLENOVO:rnLenovoZ70-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoZ70-80: dmi.product.name: 80FG dmi.product.version: Lenovo Z70-80 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1559576/+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 1559576] Re: Ubuntu Gnome boots to black screen when using proprietary Nvidia drivers on a laptop with Optimus
Hey Tim, it's just a guess, but could you try adding iomem=relaxed to the boot-parameter line? (Linux section, where you find the "quiet splash") -- 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/1559576 Title: Ubuntu Gnome boots to black screen when using proprietary Nvidia drivers on a laptop with Optimus Status in gdm: New Status in Ubuntu GNOME: New Status in gdm3 package in Ubuntu: Triaged Status in linux package in Ubuntu: Invalid Status in gdm3 source package in Xenial: Triaged Status in linux source package in Xenial: Invalid Bug description: Using latest Ubuntu Gnome x64 daily build with all updates installed. Lenovo Z70-80 laptop with Nvidia 840M, BIOS updated to latest version, secure boot and other potentially problematic BIOS settings disabled. Can only see a black screen instead of a log-in screen after boot completes when proprietary Nvidia drivers are installed. Regular Ubuntu works absolutely fine on the same machine with the same driver version. Attempting to use older drivers on Ubuntu Gnome made no difference. Bug is affecting more than just me. We were talking about workarounds in ubuntuforums. User fthx claims that switching to lightdm fixes the issue http://ubuntuforums.org/showthread.php?t=2317628=13457703#post13457703 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-14-generic 4.4.0-14.30 ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5 Uname: Linux 4.4.0-14-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Sat Mar 19 23:19:21 2016 HibernationDevice: RESUME=UUID=4f8fb76c-f99d-4c54-8a67-eed0653d8eb6 InstallationDate: Installed on 2016-03-19 (0 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160318) MachineType: LENOVO 80FG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-14-generic.efi.signed root=UUID=572a19f6-7324-4269-ad36-7ffc9919f7a2 ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-14-generic N/A linux-backports-modules-4.4.0-14-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: LENOVO dmi.bios.version: ABCN96WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo Z70-80 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z70-80 dmi.modalias: dmi:bvnLENOVO:bvrABCN96WW:bd09/22/2015:svnLENOVO:pn80FG:pvrLenovoZ70-80:rvnLENOVO:rnLenovoZ70-80:rvrNODPK:cvnLENOVO:ct10:cvrLenovoZ70-80: dmi.product.name: 80FG dmi.product.version: Lenovo Z70-80 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1559576/+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 1546572] Re: Pull in upstream AMD code (amdgpu) in Xenial
** Summary changed: - Pull in upstream AMD code in Xenial + Pull in upstream AMD code (amdgpu) in Xenial -- 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/1546572 Title: Pull in upstream AMD code (amdgpu) in Xenial Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: AMD have made a lot of progress on the amdgpu driver (especially in Linux 4.5), plus a few fixes for radeon, and the code will definitely benefit our HWE efforts. The new code includes Powerplay support for discrete GPUs (integrated GPUs are already supported). This will help us move away from the fglrx driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1546572/+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 95940] Re: No way to reset ALSA state from GUI
** Tags added: hardy ** Tags added: jaunty -- 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/95940 Title: No way to reset ALSA state from GUI Status in gnome-applets: Won't Fix Status in KDE Multimedia: New Status in gnome-applets package in Ubuntu: Triaged Status in linux package in Ubuntu: Invalid Status in linux-source-2.6.20 package in Ubuntu: Won't Fix Status in gnome-applets source package in Hardy: Won't Fix Status in linux source package in Hardy: Invalid Status in linux-source-2.6.20 source package in Hardy: Won't Fix Bug description: There is no way to reset the ALSA state from the mixer applet. Several users have found that they lose sound, and that the problem turns out to be an asound.state file which does not work for their hardware. It has not been established how the file came to be corrupt or whether the problem was caused by upgrades to newer versions which did not handle the file as written by the previous version. It has not been established what aspect of the asound.state files caused the problem. But several approaches can fix the problem: 1. Removing the ALSA modules, deleting the asound.state file, and reloading the modules. This is difficult to do for non-expert users, because applications such as the Gnome mixer and volume control can be using the modules, preventing their unloading. 2. Removing the ALSA modules, and editing the asound.state to an ultra-minimal state that reflects only the primary card, and reloading the modules. 3. Invoking the alsa-utils "reset" option. On Ubuntu, typing this fixes the problem for Intel sound cards: /etc/init.d/alsa-utils reset Intel The latter option is thought to be best, because it doesn't require unloading and reloading modules. It would be very useful to be able to invoke that "reset" command from the GUI Gnome mixer applet, which is why this bug has been filed on that. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-applets/+bug/95940/+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 1506774] Re: package bluez 5.35-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 (without linux-image-extra*)
pitti this sru has hit Kubuntu in a strange way -> bug #1509334 (30 seconds delay for final desktop) JUST be4 the final release :-( The fix for Wily is stuck now in the "proposed-queue", actually thinking this bitesize-bugfix (there) should enter "wily-updates" Could you take a look at it? best regards -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1506774 Title: package bluez 5.35-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 (without linux-image-extra*) Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Won't Fix Status in bluez source package in Vivid: New Status in bluez source package in Wily: Fix Released Bug description: Bluez installation fails on vivid and wily without linux-image-extra* because BT kernel modules are unavailable. ProblemType: Package DistroRelease: Ubuntu 15.10 Package: bluez 5.35-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu2 Architecture: amd64 Date: Thu Oct 15 22:06:50 2015 DuplicateSignature: package:bluez:5.35-0ubuntu1:subprocess installed post-installation script returned error exit status 1 Ec2AMI: ami-0f6e Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: cpu10-ram10-disk10-ephemeral20 Ec2Kernel: aki-022a Ec2Ramdisk: ari-022a ErrorMessage: subprocess installed post-installation script returned error exit status 1 InterestingModules: bnep bluetooth Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: OpenStack Foundation OpenStack Nova ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: dpkg 1.18.2ubuntu4 apt 1.0.10.2ubuntu1 SourcePackage: bluez Title: package bluez 5.35-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2011 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2011:svnOpenStackFoundation:pnOpenStackNova:pvr2013.2.3:cvnBochs:ct1:cvr: dmi.product.name: OpenStack Nova dmi.product.version: 2013.2.3 dmi.sys.vendor: OpenStack Foundation hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1506774/+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 930447] Re: Unable to start Ubuntu 12.04 live CD with syslinux loader on Pentium M x86 Laptop due to bug in PAE kernel, initramfs or syslinux
** Changed in: baltix Status: Triaged => Fix Released -- 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/930447 Title: Unable to start Ubuntu 12.04 live CD with syslinux loader on Pentium M x86 Laptop due to bug in PAE kernel, initramfs or syslinux Status in linux package in Ubuntu: Fix Released Status in syslinux package in Ubuntu: Invalid Status in Baltix: Fix Released Bug description: Ubuntu 12.04 doesn't start from Desktop CD or USB with syslinux boot loader on Pentium M 1.6Ghz or faster Pentium M CPU - displays error message about missing PAE feature in CPU, but *the same* *Ubuntu 12.04* Desktop CD/LiveUSB starts fine on *the same CPU* (and same PAE kernel) if GRUB boot loader is used, for example when WUBI or LiveUSB with GRUB boot loader, like Multisystem (http://liveusb.info/dotclear/index.php?pages/install ) is used! The error message is: "This kernel requires the following features not present on the CPU: pae. Unable to boot - please use a kernel appropriate for you CPU." THIS IS AN IMPORTANT REGRESSION! People are able to install and successfully use Ubuntu 12.04 on such pretty new hardware, like IBM Thinkpad T42 laptop with Pentium M 1700Mhz processor, but the bug in syslinux (or something related) forbids Ubuntu 12.04 installation. This bug is reproducible on lots of computers, there are several log files and /proc/cpuinfo file attached to this bugreport, AFAIK it's enough to reopen this bug. --- ApportVersion: 1.23-0ubuntu4 Architecture: i386 CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied MachineType: IBM 2373PPU dmi.bios.date: 06/18/2007 dmi.bios.vendor: IBM dmi.bios.version: 1RETDRWW (3.23 ) dmi.board.name: 2373PPU dmi.board.vendor: IBM dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: IBM dmi.chassis.version: Not Available dmi.modalias: dmi:bvnIBM:bvr1RETDRWW(3.23):bd06/18/2007:svnIBM:pn2373PPU:pvrThinkPadT42:rvnIBM:rn2373PPU:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: dmi.product.name: 2373PPU dmi.product.version: ThinkPad T42 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/930447/+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 1305522] Re: Backport Synaptics HID touchpad driver for 14.04
** Tags added: hw-specific trusty -- 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/1305522 Title: Backport Synaptics HID touchpad driver for 14.04 Status in “linux” package in Ubuntu: In Progress Status in “linux” source package in Trusty: In Progress Bug description: Synaptics just upstreamed a new set of HID touchpad driver: http://git.kernel.org/cgit/linux/kernel/git/jikos/hid.git/commit/?h=for-3.16/rmi4id=9fb6bf02e3ad04c20edb8e46536ce3eeda32c736 It's better we can have it in 14.04 . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1305522/+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 930447] Re: Unable to start Ubuntu 12.04 live CD with syslinux loader on Pentium M x86 Laptop due to bug in PAE kernel, initramfs or syslinux
** Changed in: syslinux (Ubuntu) Status: Invalid = Confirmed -- 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/930447 Title: Unable to start Ubuntu 12.04 live CD with syslinux loader on Pentium M x86 Laptop due to bug in PAE kernel, initramfs or syslinux Status in “linux” package in Ubuntu: Confirmed Status in “syslinux” package in Ubuntu: Confirmed Status in Baltix GNU/Linux: Triaged Bug description: Ubuntu 12.04 doesn't start from Desktop CD or USB with syslinux boot loader on Pentium M 1.6Ghz or faster Pentium M CPU - displays error message about missing PAE feature in CPU, but *the same* *Ubuntu 12.04* Desktop CD/LiveUSB starts fine on *the same CPU* (and same PAE kernel) if GRUB boot loader is used, for example when WUBI or LiveUSB with GRUB boot loader, like Multisystem (http://liveusb.info/dotclear/index.php?pages/install ) is used! The error message is: This kernel requires the following features not present on the CPU: pae. Unable to boot - please use a kernel appropriate for you CPU. THIS IS AN IMPORTANT REGRESSION! People are able to install and successfully use Ubuntu 12.04 on such pretty new hardware, like IBM Thinkpad T42 laptop with Pentium M 1700Mhz processor, but the bug in syslinux (or something related) forbids Ubuntu 12.04 installation. This bug is reproducible on lots of computers, there are several log files and /proc/cpuinfo file attached to this bugreport, AFAIK it's enough to reopen this bug. --- ApportVersion: 1.23-0ubuntu4 Architecture: i386 CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied MachineType: IBM 2373PPU dmi.bios.date: 06/18/2007 dmi.bios.vendor: IBM dmi.bios.version: 1RETDRWW (3.23 ) dmi.board.name: 2373PPU dmi.board.vendor: IBM dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: IBM dmi.chassis.version: Not Available dmi.modalias: dmi:bvnIBM:bvr1RETDRWW(3.23):bd06/18/2007:svnIBM:pn2373PPU:pvrThinkPadT42:rvnIBM:rn2373PPU:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: dmi.product.name: 2373PPU dmi.product.version: ThinkPad T42 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/930447/+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 930447] Re: Unable to start Ubuntu 12.04 live CD with syslinux loader on Pentium M x86 Laptop due to bug in PAE kernel, initramfs or syslinux
** Tags added: trusty -- 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/930447 Title: Unable to start Ubuntu 12.04 live CD with syslinux loader on Pentium M x86 Laptop due to bug in PAE kernel, initramfs or syslinux Status in “linux” package in Ubuntu: Confirmed Status in “syslinux” package in Ubuntu: Confirmed Status in Baltix GNU/Linux: Triaged Bug description: Ubuntu 12.04 doesn't start from Desktop CD or USB with syslinux boot loader on Pentium M 1.6Ghz or faster Pentium M CPU - displays error message about missing PAE feature in CPU, but *the same* *Ubuntu 12.04* Desktop CD/LiveUSB starts fine on *the same CPU* (and same PAE kernel) if GRUB boot loader is used, for example when WUBI or LiveUSB with GRUB boot loader, like Multisystem (http://liveusb.info/dotclear/index.php?pages/install ) is used! The error message is: This kernel requires the following features not present on the CPU: pae. Unable to boot - please use a kernel appropriate for you CPU. THIS IS AN IMPORTANT REGRESSION! People are able to install and successfully use Ubuntu 12.04 on such pretty new hardware, like IBM Thinkpad T42 laptop with Pentium M 1700Mhz processor, but the bug in syslinux (or something related) forbids Ubuntu 12.04 installation. This bug is reproducible on lots of computers, there are several log files and /proc/cpuinfo file attached to this bugreport, AFAIK it's enough to reopen this bug. --- ApportVersion: 1.23-0ubuntu4 Architecture: i386 CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied MachineType: IBM 2373PPU dmi.bios.date: 06/18/2007 dmi.bios.vendor: IBM dmi.bios.version: 1RETDRWW (3.23 ) dmi.board.name: 2373PPU dmi.board.vendor: IBM dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: IBM dmi.chassis.version: Not Available dmi.modalias: dmi:bvnIBM:bvr1RETDRWW(3.23):bd06/18/2007:svnIBM:pn2373PPU:pvrThinkPadT42:rvnIBM:rn2373PPU:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: dmi.product.name: 2373PPU dmi.product.version: ThinkPad T42 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/930447/+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 930447] Re: Unable to start Ubuntu 12.04 live CD with syslinux loader on Pentium M x86 Laptop due to bug in PAE kernel, initramfs or syslinux
hi there! reverted bug-status back to confirmed. There are other bug-statii like opinion, incomplete, fix released, fix commited Non of these reflect the situation, neither. The bug-report is valid since a lot of users have confirmed it's existance. May be one-hundred-papercuts is the right place if you feel a bug doesn't get enough attention foralongtime. Another valuable thought is that one cannot blame the ubuntu-people solely for not getting this right - Intel should include the regarded little Pentium-M-boxes in the package 'intel-microcode' - probabely they'll lend us an open ear with the forthcoming end of W$ XP. BUT they won't take any action w/o a valuable bug-report. @ roland aus koeln: Keep in mind: a bug report disappears from list once it's marked as invalid. But is also appears in trusty -- 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/930447 Title: Unable to start Ubuntu 12.04 live CD with syslinux loader on Pentium M x86 Laptop due to bug in PAE kernel, initramfs or syslinux Status in “linux” package in Ubuntu: Confirmed Status in “syslinux” package in Ubuntu: Confirmed Status in Baltix GNU/Linux: Triaged Bug description: Ubuntu 12.04 doesn't start from Desktop CD or USB with syslinux boot loader on Pentium M 1.6Ghz or faster Pentium M CPU - displays error message about missing PAE feature in CPU, but *the same* *Ubuntu 12.04* Desktop CD/LiveUSB starts fine on *the same CPU* (and same PAE kernel) if GRUB boot loader is used, for example when WUBI or LiveUSB with GRUB boot loader, like Multisystem (http://liveusb.info/dotclear/index.php?pages/install ) is used! The error message is: This kernel requires the following features not present on the CPU: pae. Unable to boot - please use a kernel appropriate for you CPU. THIS IS AN IMPORTANT REGRESSION! People are able to install and successfully use Ubuntu 12.04 on such pretty new hardware, like IBM Thinkpad T42 laptop with Pentium M 1700Mhz processor, but the bug in syslinux (or something related) forbids Ubuntu 12.04 installation. This bug is reproducible on lots of computers, there are several log files and /proc/cpuinfo file attached to this bugreport, AFAIK it's enough to reopen this bug. --- ApportVersion: 1.23-0ubuntu4 Architecture: i386 CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied MachineType: IBM 2373PPU dmi.bios.date: 06/18/2007 dmi.bios.vendor: IBM dmi.bios.version: 1RETDRWW (3.23 ) dmi.board.name: 2373PPU dmi.board.vendor: IBM dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: IBM dmi.chassis.version: Not Available dmi.modalias: dmi:bvnIBM:bvr1RETDRWW(3.23):bd06/18/2007:svnIBM:pn2373PPU:pvrThinkPadT42:rvnIBM:rn2373PPU:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable: dmi.product.name: 2373PPU dmi.product.version: ThinkPad T42 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/930447/+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 1076414] Re: Transitioning between nvidia drivers (updates, 304, 310) results in install failure due to conflicting nvidia-settings
** Tags added: removal-candidate -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1076414 Title: Transitioning between nvidia drivers (updates, 304, 310) results in install failure due to conflicting nvidia-settings Status in “nvidia-settings” package in Ubuntu: Invalid Status in “nvidia-settings-experimental-304” package in Ubuntu: Invalid Status in “nvidia-settings-experimental-310” package in Ubuntu: Invalid Status in “nvidia-settings-updates” package in Ubuntu: Invalid Status in “nvidia-settings” source package in Precise: Invalid Status in “nvidia-settings-experimental-304” source package in Precise: Invalid Status in “nvidia-settings-experimental-310” source package in Precise: Invalid Status in “nvidia-settings-updates” source package in Precise: Invalid Bug description: package nvidia-settings was installed. Seemed to conflict somehow. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: nvidia-settings-experimental-310 (not installed) ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30 Uname: Linux 3.2.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu14 AptOrdering: nvidia-settings-experimental-310: Install nvidia-settings-experimental-310: Configure Architecture: amd64 Date: Thu Nov 8 17:00:14 2012 DpkgTerminalLog: Unpacking nvidia-settings-experimental-310 (from .../nvidia-settings-experimental-310_310.14-0ubuntu0.1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/nvidia-settings-experimental-310_310.14-0ubuntu0.1_amd64.deb (--unpack): trying to overwrite '/usr/bin/nvidia-settings', which is also in package nvidia-settings-updates 304.43-0ubuntu0.2 DuplicateSignature: Unpacking nvidia-settings-experimental-310 (from .../nvidia-settings-experimental-310_310.14-0ubuntu0.1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/nvidia-settings-experimental-310_310.14-0ubuntu0.1_amd64.deb (--unpack): trying to overwrite '/usr/bin/nvidia-settings', which is also in package nvidia-settings-updates 304.43-0ubuntu0.2 ErrorMessage: trying to overwrite '/usr/bin/nvidia-settings', which is also in package nvidia-settings-updates 304.43-0ubuntu0.2 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: nvidia-settings-experimental-310 Title: package nvidia-settings-experimental-310 (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/nvidia-settings', which is also in package nvidia-settings-updates 304.43-0ubuntu0.2 UpgradeStatus: Upgraded to precise on 2012-05-16 (176 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1076414/+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 1259237] Re: Hybrid graphics enablement in 12.04.4
Hello there! With reference to comment#8 : Could 304 drivers kindly get released? There is the urge to close bug #1262752 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1259237 Title: Hybrid graphics enablement in 12.04.4 Status in “bbswitch” package in Ubuntu: Invalid Status in “jockey” package in Ubuntu: In Progress Status in “lightdm” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-173” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-304” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-331” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: In Progress Status in “nvidia-prime” package in Ubuntu: Invalid Status in “nvidia-settings” package in Ubuntu: In Progress Status in “screen-resolution-extra” package in Ubuntu: Invalid Status in “bbswitch” source package in Precise: In Progress Status in “nvidia-prime” source package in Precise: Fix Committed Status in “screen-resolution-extra” source package in Precise: Fix Committed Bug description: SRU request: Please accept the following packages in precise-proposed. lightdm nvidia-prime nvidia-graphics-drivers-331 nvidia-graphics-drivers-331-updates nvidia-graphics-drivers-304 nvidia-graphics-drivers-304-updates nvidia-graphics-drivers-173 nvidia-settings screen-resolution-extra bbswitch [Rationale] This is the result of the HWE effort to bring power management to systems with NVIDIA Optimus. [Impact] Without this work, we keep both GPUs on all the time, thus heavily impacting on battery life. Thanks to this work, it is now possible to easily disable the discrete card when raw power is not needed. Furthermore nvidia-prime has better hardware detection now, and won't try to enable hybrid graphics on desktop systems any more. As for the technical details: * bbswitch is a backport of the package that now lives in main in 14.04. * The actual work happened in lightdm, nvidia-331, nvidia-331-updates, nvidia-prime, screen-resolution-extra, and nvidia-settings. * nvidia-settings now replaces all the different nvidia-settings flavours, so as to reduce the maintainance effort. I patched the app so that it checks the driver version (at runtime) and doesn't expose features that older driver releases do not support. * nvidia-331 and nvidia-331-updates replace 319 and 319-updates. These are the new LTS releases by NVIDIA. * nvidia-304 and nvidia-304-updates recommend the new nvidia-settings, include a security update, and build against the upcoming Linux 3.11 (lts-saucy). * nvidia-173, in addition to being compatible with Linux 3.11 (lts-saucy), also introduces transitional packages for 173-updates, as it doesn't make sense to maintain a separate -updates flavour any more. [Test Case] After installing the update, users should be able to boot the system as usual, with no regressions of any kind. * Systems with a single NVIDIA card: nvidia-prime will detect the hardware and do nothing at all on unsupported systems (such as the one card use case, or the desktop use case) * Systems with NVIDIA Optimus: nvidia-prime will preserve its previous behaviour by leaving both GPUs on. Users can launch nvidia-settings and switch to the power profile that they need. [Regression Potential] Low. The new features are enabled only if the user manually selects them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1259237/+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 1266680] Re: Localization support for nvidia-settings
Looks to me like a dupe of bug #723432, opend 1-11-2011-02-21 ? ** Tags added: saucy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1266680 Title: Localization support for nvidia-settings Status in NVIDIA Drivers Ubuntu: New Status in Ubuntu Translations: Triaged Status in “nvidia-settings” package in Ubuntu: New Bug description: On Ubuntu 14.04 dev with nvidia-settings 331.20-0ubuntu6 it is still only in english. Maybe nvidia-settings can be enhanced to support language files too at some point in the future. To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1266680/+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 723432] Re: We need a way to translate the nvidia-settings tool
** Tags removed: proprietary -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/723432 Title: We need a way to translate the nvidia-settings tool Status in “nvidia-settings” package in Ubuntu: Confirmed Bug description: Binary package hint: nvidia-settings Currently there is no way to localize the nvidia-settings tool (except for translating in source), this makes it hard for end userse to configure there monitor settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/723432/+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 1259237] Re: Hybrid graphics enablement in 12.04.4
Alberto, can you pls include the last patch from Trusty's nvidia- prime_0.5.2 ? https://launchpadlibrarian.net/160288342/nvidia- prime_0.5.1_0.5.2.diff.gz Single GPU users would appreciate this on KDE/GDM. Thanks in advance best wishes to you for the new year. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1259237 Title: Hybrid graphics enablement in 12.04.4 Status in “bbswitch” package in Ubuntu: Invalid Status in “lightdm” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-173” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-304” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-331” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: In Progress Status in “nvidia-prime” package in Ubuntu: Invalid Status in “nvidia-settings” package in Ubuntu: In Progress Status in “screen-resolution-extra” package in Ubuntu: Invalid Status in “bbswitch” source package in Precise: In Progress Status in “nvidia-prime” source package in Precise: In Progress Status in “screen-resolution-extra” source package in Precise: Fix Committed Bug description: SRU request: Please accept the following packages in precise-proposed. lightdm nvidia-prime nvidia-graphics-drivers-331 nvidia-graphics-drivers-331-updates nvidia-graphics-drivers-304 nvidia-graphics-drivers-304-updates nvidia-graphics-drivers-173 nvidia-settings screen-resolution-extra bbswitch [Rationale] This is the result of the HWE effort to bring power management to systems with NVIDIA Optimus. [Impact] Without this work, we keep both GPUs on all the time, thus heavily impacting on battery life. Thanks to this work, it is now possible to easily disable the discrete card when raw power is not needed. Furthermore nvidia-prime has better hardware detection now, and won't try to enable hybrid graphics on desktop systems any more. As for the technical details: * bbswitch is a backport of the package that now lives in main in 14.04. * The actual work happened in lightdm, nvidia-331, nvidia-331-updates, nvidia-prime, screen-resolution-extra, and nvidia-settings. * nvidia-settings now replaces all the different nvidia-settings flavours, so as to reduce the maintainance effort. I patched the app so that it checks the driver version (at runtime) and doesn't expose features that older driver releases do not support. * nvidia-331 and nvidia-331-updates replace 319 and 319-updates. These are the new LTS releases by NVIDIA. * nvidia-304 and nvidia-304-updates recommend the new nvidia-settings, include a security update, and build against the upcoming Linux 3.11 (lts-saucy). * nvidia-173, in addition to being compatible with Linux 3.11 (lts-saucy), also introduces transitional packages for 173-updates, as it doesn't make sense to maintain a separate -updates flavour any more. [Test Case] After installing the update, users should be able to boot the system as usual, with no regressions of any kind. * Systems with a single NVIDIA card: nvidia-prime will detect the hardware and do nothing at all on unsupported systems (such as the one card use case, or the desktop use case) * Systems with NVIDIA Optimus: nvidia-prime will preserve its previous behaviour by leaving both GPUs on. Users can launch nvidia-settings and switch to the power profile that they need. [Regression Potential] Low. The new features are enabled only if the user manually selects them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1259237/+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 1100994] Re: The quantal version of nvidia-settings doesn't support legacy nvidia driver (173) and tends to be backported to Precise 12.04.3
anyone? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1100994 Title: The quantal version of nvidia-settings doesn't support legacy nvidia driver (173) and tends to be backported to Precise 12.04.3 Status in “nvidia-settings” package in Ubuntu: Confirmed Bug description: When I tried to configure my display using the nvidia-settings package from Quantal repository, I meet the error message: The NVIDIA X driver on (...) is not new enough to support the nvidia-settings Display Configuration page.. It makes sense, because I'm using the legacy nvidia-173 driver. My non-elegant soluction was install the nvidia-settings from Precise repository, that solved the problem. Being more precise: $ dpkg -l |grep nvidia ii nvidia-173 173.14.36-0ubuntu0.1 i386 ii nvidia-settings 304.51-0ubuntu2 i386 DIDN'T WORKS but $ dpkg -l |grep nvidia ii nvidia-173 173.14.36-0ubuntu0.1 i386 ii nvidia-settings 295.33-0ubuntu1 i386 WORKS There is no package that the name is something like nvidia- settings-173 available in Quantal repository, but it's required to configure properly a old Nvidia device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1100994/+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 873375] Re: nvidia-settings freeze on activating TwinView [needs nvidia-settings 290]
** Changed in: nvidia-settings (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/873375 Title: nvidia-settings freeze on activating TwinView [needs nvidia-settings 290] Status in “nvidia-settings” package in Ubuntu: Fix Released Status in “nvidia-settings” package in Debian: Fix Released Bug description: When I try to activate my secondary display the nvidia-settings software will freeze when i choose the option TwinView. After killing the program I cant start it in this session again, so I have to logout und relogin then. My system: Notebook: Dell Latitude E6500 Videocard: Nvidia Quadro NVS 140M Architecture: amd64 Windowmanager: Fluxbox ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: nvidia-settings 280.13-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Thu Oct 13 16:16:09 2011 ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-settings UpgradeStatus: Upgraded to oneiric on 2011-10-12 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/873375/+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 873375] Re: nvidia-settings freeze on activating TwinView [needs nvidia-settings 290]
The TwinView solution was given up in favour RandR. This means that screen configuration is possible with the system provided graphical tools. There is enough reason to understand this bug can be closed as a newer version of software-package didn't make it appear any longer. Thanks for reporting this bug and all the energy you gave in order to make Ubuntu better. If you dont think the update resolved the initial problem then feel free to reopen the bug and attach logs that are necessary to get evidence. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/873375 Title: nvidia-settings freeze on activating TwinView [needs nvidia-settings 290] Status in “nvidia-settings” package in Ubuntu: Fix Released Status in “nvidia-settings” package in Debian: Fix Released Bug description: When I try to activate my secondary display the nvidia-settings software will freeze when i choose the option TwinView. After killing the program I cant start it in this session again, so I have to logout und relogin then. My system: Notebook: Dell Latitude E6500 Videocard: Nvidia Quadro NVS 140M Architecture: amd64 Windowmanager: Fluxbox ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: nvidia-settings 280.13-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Thu Oct 13 16:16:09 2011 ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-settings UpgradeStatus: Upgraded to oneiric on 2011-10-12 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/873375/+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 920353] Re: nvidia-settings freeze on activating TwinView
** Changed in: nvidia-settings (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/920353 Title: nvidia-settings freeze on activating TwinView Status in “nvidia-settings” package in Ubuntu: Incomplete Bug description: This bug still affects me. When I try to activate my secondary display the nvidia-settings software will freeze when i choose the option TwinView. After killing the program I cant start it in this session again, so I have to logout und relogin then. My system: Notebook: Dell Latitude E6420 Videocard: NVIDIA Quadro NVS 4200M Architecture: amd64 The issues I'm experiencing are exactly the same as in bug #873375 The proposed fixes are not working. Neither in 11.10 nor in 12.04 (inculuding all current updates) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/920353/+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 920353] Re: nvidia-settings freeze on activating TwinView
missing logfiles. Twinview was given up in favour of RandR. This means ful systemcompatibilty. Nvidia-settings should be used any furthers only in rare cases. System provided GUI-tools should be able to help on Dual-screen configuration in ful. ** Tags added: oneiric precise -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/920353 Title: nvidia-settings freeze on activating TwinView Status in “nvidia-settings” package in Ubuntu: Incomplete Bug description: This bug still affects me. When I try to activate my secondary display the nvidia-settings software will freeze when i choose the option TwinView. After killing the program I cant start it in this session again, so I have to logout und relogin then. My system: Notebook: Dell Latitude E6420 Videocard: NVIDIA Quadro NVS 4200M Architecture: amd64 The issues I'm experiencing are exactly the same as in bug #873375 The proposed fixes are not working. Neither in 11.10 nor in 12.04 (inculuding all current updates) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/920353/+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 723432] Re: We need a way to translate the nvidia-settings tool
As far as I'm concerned this is on the windows side translated into 52 languages. at least. Tried to open a bug-report against nVidia, already ? Try it! How is situation in OpenSuse or Fedora :-) These translations are already there they just don't get packaged, here. Let's just call this legendary league, So, Ubuntu is interested in gathering into new big markets like India and China. Wondering how their acceptance on missing localisation is? And I am not talking about left2right languages that presumably present an even higher number than native english speakers. It took some years to have localised 'search-providers' in the beloved Firefox. Put it on 100 papercuts. ** Tags added: localization propietary trusty ** Tags removed: propietary ** Tags added: proprietary ** Tags removed: localization ** Tags added: localisation ** Tags added: bitesize -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/723432 Title: We need a way to translate the nvidia-settings tool Status in “nvidia-settings” package in Ubuntu: Confirmed Bug description: Binary package hint: nvidia-settings Currently there is no way to localize the nvidia-settings tool (except for translating in source), this makes it hard for end userse to configure there monitor settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/723432/+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 822369] Re: after upgrading fro 10.10 to 11.04 i got instable and purple desktop card intel
logfiles? setting to status=incomplete ** Changed in: nvidia-settings (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/822369 Title: after upgrading fro 10.10 to 11.04 i got instable and purple desktop card intel Status in “nvidia-settings” package in Ubuntu: Incomplete Bug description: the problem is affecting even the graphic card intel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/822369/+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 1259237] Re: Hybrid graphics enablement in 12.04.4
Hello watchout for bug #1262752 nvidia_304 not blacklisted or removed when nvidia_304_updates is installed Besides I'd like to draw your attention to the fact that Kubuntu 12.04 initially was supllied without support of LightDM, thus the last update to it's greeter lightdam-kde-greeter was somewhat in April 2012. Even though it has matured in younger versions of Kubuntu. Some packages listed here get updated w/o approval already? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1259237 Title: Hybrid graphics enablement in 12.04.4 Status in “bbswitch” package in Ubuntu: Invalid Status in “lightdm” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-173” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-304” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-304-updates” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-331” package in Ubuntu: In Progress Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: In Progress Status in “nvidia-prime” package in Ubuntu: Invalid Status in “nvidia-settings” package in Ubuntu: In Progress Status in “screen-resolution-extra” package in Ubuntu: Invalid Status in “bbswitch” source package in Precise: In Progress Status in “nvidia-prime” source package in Precise: In Progress Status in “screen-resolution-extra” source package in Precise: Fix Committed Bug description: SRU request: Please accept the following packages in precise-proposed. lightdm nvidia-prime nvidia-graphics-drivers-331 nvidia-graphics-drivers-331-updates nvidia-graphics-drivers-304 nvidia-graphics-drivers-304-updates nvidia-graphics-drivers-173 nvidia-settings screen-resolution-extra bbswitch [Rationale] This is the result of the HWE effort to bring power management to systems with NVIDIA Optimus. [Impact] Without this work, we keep both GPUs on all the time, thus heavily impacting on battery life. Thanks to this work, it is now possible to easily disable the discrete card when raw power is not needed. Furthermore nvidia-prime has better hardware detection now, and won't try to enable hybrid graphics on desktop systems any more. As for the technical details: * bbswitch is a backport of the package that now lives in main in 14.04. * The actual work happened in lightdm, nvidia-331, nvidia-331-updates, nvidia-prime, screen-resolution-extra, and nvidia-settings. * nvidia-settings now replaces all the different nvidia-settings flavours, so as to reduce the maintainance effort. I patched the app so that it checks the driver version (at runtime) and doesn't expose features that older driver releases do not support. * nvidia-331 and nvidia-331-updates replace 319 and 319-updates. These are the new LTS releases by NVIDIA. * nvidia-304 and nvidia-304-updates recommend the new nvidia-settings, include a security update, and build against the upcoming Linux 3.11 (lts-saucy). * nvidia-173, in addition to being compatible with Linux 3.11 (lts-saucy), also introduces transitional packages for 173-updates, as it doesn't make sense to maintain a separate -updates flavour any more. [Test Case] After installing the update, users should be able to boot the system as usual, with no regressions of any kind. * Systems with a single NVIDIA card: nvidia-prime will detect the hardware and do nothing at all on unsupported systems (such as the one card use case, or the desktop use case) * Systems with NVIDIA Optimus: nvidia-prime will preserve its previous behaviour by leaving both GPUs on. Users can launch nvidia-settings and switch to the power profile that they need. [Regression Potential] Low. The new features are enabled only if the user manually selects them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bbswitch/+bug/1259237/+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 1214462] Re: Kernel Description doesn't explain its a PAE-Kernel _ since 3.4.0.1.1 _ Linus would not smile _.
** Changed in: linux (Ubuntu) Status: Incomplete = New -- 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/1214462 Title: Kernel Description doesn't explain its a PAE-Kernel _ since 3.4.0.1.1 _ Linus would not smile _. Status in “linux” package in Ubuntu: New Bug description: Dear Developers and maintainers, trying not to make a big fuzz about it: Let me just quote https://bugs.launchpad.net/baltix/+bug/930447/comments/97 from 2012-06-05 (referencing the release-notes on 12.04.2): The non-PAE version of the Linux kernel will be dropped completely following the 12.04 release. Pls correct me and mark as invalid, if Ubuntu doesn't have to follow naming conventions given on the Linux-Kernel. Trying to find appropiate information in the package change-log: linux-meta (3.4.0.1.1) quantal; urgency=low * Open Quantal Quetzal 12.10 * Temporarily disable LBM * Remove non-PAE i386 references -- mail adress hid...@canonical.com Wed, 02 May 2012 06:21:45 -0700 Pls clarify this and correct Ubuntus Kernel-naming on i386 package if appropriate.If the leftovers in the package are PAE, the package-names are meant to say so Clear Loud. Personally I think Linus wouldn't smile, even though if I thought the index-finger to Nvidia was a bit to rough. Personally I think this bug has security-potential. Thanks for helping to make Ubuntu better every day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214462/+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 1214462] Re: Kernel Description doesn't explain its a PAE-Kernel _ since 3.4.0.1.1 _ Linus would not smile _.
This is probably one of the very last bugs I'm reporting to Ubuntu. Release-Notes 12.04/12.04.1/12.04.2 get overwritten... One can only reconstruct it via history. AND a camouflaged PAE-Kernel ... Wonder how the other big distros handle the farewell to the 32-Bit Non- PAE Kernel. From Fedora I 've read they at least establish the live CD with a non PAE-Kernel. Can't attach log-iles since whoopsie can't handle stuff like this. ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- 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/1214462 Title: Kernel Description doesn't explain its a PAE-Kernel _ since 3.4.0.1.1 _ Linus would not smile _. Status in “linux” package in Ubuntu: Confirmed Bug description: Dear Developers and maintainers, trying not to make a big fuzz about it: Let me just quote https://bugs.launchpad.net/baltix/+bug/930447/comments/97 from 2012-06-05 (referencing the release-notes on 12.04.2): The non-PAE version of the Linux kernel will be dropped completely following the 12.04 release. Pls correct me and mark as invalid, if Ubuntu doesn't have to follow naming conventions given on the Linux-Kernel. Trying to find appropiate information in the package change-log: linux-meta (3.4.0.1.1) quantal; urgency=low * Open Quantal Quetzal 12.10 * Temporarily disable LBM * Remove non-PAE i386 references -- mail adress hid...@canonical.com Wed, 02 May 2012 06:21:45 -0700 Pls clarify this and correct Ubuntus Kernel-naming on i386 package if appropriate.If the leftovers in the package are PAE, the package-names are meant to say so Clear Loud. Personally I think Linus wouldn't smile, even though if I thought the index-finger to Nvidia was a bit to rough. Personally I think this bug has security-potential. Thanks for helping to make Ubuntu better every day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214462/+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 1214462] [NEW] Kernel Description doesn't explain its a PAE-Kernel _ since 3.4.0.1.1 _ Linus would not smile _.
Public bug reported: Dear Developers and maintainers, trying not to make a big fuzz about it: Let me just quote https://bugs.launchpad.net/baltix/+bug/930447/comments/97 from 2012-06-05: The non-PAE version of the Linux kernel will be dropped completely following the 12.04 release. Pls correct me and mark as invalid, if Ubuntu doesnt have to follow naming conventions given on Linux-Kernel. Trying to find appropiate information in the package change-log: linux-meta (3.4.0.1.1) quantal; urgency=low * Open Quantal Quetzal 12.10 * Temporarily disable LBM * Remove non-PAE i386 references -- mail adress hid...@canonical.com Wed, 02 May 2012 06:21:45 -0700 Pls clarify this and correct Ubuntus Kernel-nming on i386 package if appropriate Personally I think Linus wouldn't smile, even though if I thought the index-finger to Nvidia was a bit to rough. Personally I think this bug has security-potential. Thanks for helping to make Ubuntu better every day. ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New ** Tags: precise quantal raring saucy ** Description changed: Dear Developers and maintainers, trying not to make a big fuzz about it: Let me just quote https://bugs.launchpad.net/baltix/+bug/930447/comments/97 from 2012-06-05: The non-PAE version of the Linux kernel will be dropped completely following the 12.04 release. Pls correct me and mark as invalid, if Ubuntu doesnt have to follow naming conventions given on Linux-Kernel. - Trying to find appropiate inormation in the package change-log: + Trying to find appropiate information in the package change-log: linux-meta (3.4.0.1.1) quantal; urgency=low - * Open Quantal Quetzal 12.10 - * Temporarily disable LBM - * Remove non-PAE i386 references + * Open Quantal Quetzal 12.10 + * Temporarily disable LBM + * Remove non-PAE i386 references - -- mail adress hid...@canonical.com Wed, 02 May 2012 06:21:45 -0700 + -- mail adress hid...@canonical.com Wed, 02 May 2012 06:21:45 -0700 Pls clarify this and correct Ubuntus Kernel-nming on i386 package if appropriate Personally I think Linus wouldn't smile, even though if I thought the index-finger to Nvidia was a bit to rough. Personally I think this bug has security-potential. Thanks for helping to make Ubuntu better every day. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1214462 Title: Kernel Description doesn't explain its a PAE-Kernel _ since 3.4.0.1.1 _ Linus would not smile _. Status in “linux-meta” package in Ubuntu: New Bug description: Dear Developers and maintainers, trying not to make a big fuzz about it: Let me just quote https://bugs.launchpad.net/baltix/+bug/930447/comments/97 from 2012-06-05: The non-PAE version of the Linux kernel will be dropped completely following the 12.04 release. Pls correct me and mark as invalid, if Ubuntu doesnt have to follow naming conventions given on Linux-Kernel. Trying to find appropiate information in the package change-log: linux-meta (3.4.0.1.1) quantal; urgency=low * Open Quantal Quetzal 12.10 * Temporarily disable LBM * Remove non-PAE i386 references -- mail adress hid...@canonical.com Wed, 02 May 2012 06:21:45 -0700 Pls clarify this and correct Ubuntus Kernel-nming on i386 package if appropriate Personally I think Linus wouldn't smile, even though if I thought the index-finger to Nvidia was a bit to rough. Personally I think this bug has security-potential. Thanks for helping to make Ubuntu better every day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1214462/+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 1214462] Re: Kernel Description doesn't explain its a PAE-Kernel _ since 3.4.0.1.1 _ Linus would not smile _.
** Description changed: Dear Developers and maintainers, trying not to make a big fuzz about it: Let me just quote https://bugs.launchpad.net/baltix/+bug/930447/comments/97 from 2012-06-05: - The non-PAE version of the Linux kernel will be dropped completely - following the 12.04 release. + The non-PAE version of the Linux kernel will be dropped completely + following the 12.04 release. - Pls correct me and mark as invalid, if Ubuntu doesnt have to follow - naming conventions given on Linux-Kernel. + Pls correct me and mark as invalid, if Ubuntu doesn't have to follow + naming conventions given on the Linux-Kernel. Trying to find appropiate information in the package change-log: linux-meta (3.4.0.1.1) quantal; urgency=low * Open Quantal Quetzal 12.10 * Temporarily disable LBM * Remove non-PAE i386 references -- mail adress hid...@canonical.com Wed, 02 May 2012 06:21:45 -0700 - Pls clarify this and correct Ubuntus Kernel-nming on i386 package if - appropriate + Pls clarify this and correct Ubuntus Kernel-naming on i386 package if + appropriate. Personally I think Linus wouldn't smile, even though if I thought the index-finger to Nvidia was a bit to rough. Personally I think this bug has security-potential. Thanks for helping to make Ubuntu better every day. ** Description changed: Dear Developers and maintainers, trying not to make a big fuzz about it: Let me just quote https://bugs.launchpad.net/baltix/+bug/930447/comments/97 from - 2012-06-05: + 2012-06-05 (referencing the release-notes on 12.04.2): - The non-PAE version of the Linux kernel will be dropped completely + The non-PAE version of the Linux kernel will be dropped completely following the 12.04 release. Pls correct me and mark as invalid, if Ubuntu doesn't have to follow naming conventions given on the Linux-Kernel. Trying to find appropiate information in the package change-log: linux-meta (3.4.0.1.1) quantal; urgency=low * Open Quantal Quetzal 12.10 * Temporarily disable LBM * Remove non-PAE i386 references -- mail adress hid...@canonical.com Wed, 02 May 2012 06:21:45 -0700 Pls clarify this and correct Ubuntus Kernel-naming on i386 package if appropriate. Personally I think Linus wouldn't smile, even though if I thought the index-finger to Nvidia was a bit to rough. Personally I think this bug has security-potential. Thanks for helping to make Ubuntu better every day. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1214462 Title: Kernel Description doesn't explain its a PAE-Kernel _ since 3.4.0.1.1 _ Linus would not smile _. Status in “linux” package in Ubuntu: New Bug description: Dear Developers and maintainers, trying not to make a big fuzz about it: Let me just quote https://bugs.launchpad.net/baltix/+bug/930447/comments/97 from 2012-06-05 (referencing the release-notes on 12.04.2): The non-PAE version of the Linux kernel will be dropped completely following the 12.04 release. Pls correct me and mark as invalid, if Ubuntu doesn't have to follow naming conventions given on the Linux-Kernel. Trying to find appropiate information in the package change-log: linux-meta (3.4.0.1.1) quantal; urgency=low * Open Quantal Quetzal 12.10 * Temporarily disable LBM * Remove non-PAE i386 references -- mail adress hid...@canonical.com Wed, 02 May 2012 06:21:45 -0700 Pls clarify this and correct Ubuntus Kernel-naming on i386 package if appropriate. Personally I think Linus wouldn't smile, even though if I thought the index-finger to Nvidia was a bit to rough. Personally I think this bug has security-potential. Thanks for helping to make Ubuntu better every day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214462/+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 1214462] Re: Kernel Description doesn't explain its a PAE-Kernel _ since 3.4.0.1.1 _ Linus would not smile _.
** Description changed: Dear Developers and maintainers, trying not to make a big fuzz about it: Let me just quote https://bugs.launchpad.net/baltix/+bug/930447/comments/97 from 2012-06-05 (referencing the release-notes on 12.04.2): The non-PAE version of the Linux kernel will be dropped completely following the 12.04 release. Pls correct me and mark as invalid, if Ubuntu doesn't have to follow naming conventions given on the Linux-Kernel. Trying to find appropiate information in the package change-log: linux-meta (3.4.0.1.1) quantal; urgency=low * Open Quantal Quetzal 12.10 * Temporarily disable LBM * Remove non-PAE i386 references -- mail adress hid...@canonical.com Wed, 02 May 2012 06:21:45 -0700 Pls clarify this and correct Ubuntus Kernel-naming on i386 package if - appropriate. + appropriate.If the leftovers in the package are PAE, the package-names + are meant to say so Clear Loud. Personally I think Linus wouldn't smile, even though if I thought the index-finger to Nvidia was a bit to rough. Personally I think this bug has security-potential. Thanks for helping to make Ubuntu better every day. -- 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/1214462 Title: Kernel Description doesn't explain its a PAE-Kernel _ since 3.4.0.1.1 _ Linus would not smile _. Status in “linux” package in Ubuntu: New Bug description: Dear Developers and maintainers, trying not to make a big fuzz about it: Let me just quote https://bugs.launchpad.net/baltix/+bug/930447/comments/97 from 2012-06-05 (referencing the release-notes on 12.04.2): The non-PAE version of the Linux kernel will be dropped completely following the 12.04 release. Pls correct me and mark as invalid, if Ubuntu doesn't have to follow naming conventions given on the Linux-Kernel. Trying to find appropiate information in the package change-log: linux-meta (3.4.0.1.1) quantal; urgency=low * Open Quantal Quetzal 12.10 * Temporarily disable LBM * Remove non-PAE i386 references -- mail adress hid...@canonical.com Wed, 02 May 2012 06:21:45 -0700 Pls clarify this and correct Ubuntus Kernel-naming on i386 package if appropriate.If the leftovers in the package are PAE, the package-names are meant to say so Clear Loud. Personally I think Linus wouldn't smile, even though if I thought the index-finger to Nvidia was a bit to rough. Personally I think this bug has security-potential. Thanks for helping to make Ubuntu better every day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1214462/+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 1076414] Re: Transitioning between nvidia drivers (updates, 304, 310) results in install failure due to conflicting nvidia-settings
hi! both files seem to be stuck in proposed Since these version-numbers (exakt-hit) are not listed any longer fro Nvidia - https://devtalk.nvidia.com/default/topic/533434/linux/current-graphics- driver-releases/ This has good potential to confuse non-experts. Think they could get cleaned up. Thanks in advance. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1076414 Title: Transitioning between nvidia drivers (updates, 304, 310) results in install failure due to conflicting nvidia-settings Status in “nvidia-settings” package in Ubuntu: Invalid Status in “nvidia-settings-experimental-304” package in Ubuntu: Fix Committed Status in “nvidia-settings-experimental-310” package in Ubuntu: Fix Committed Status in “nvidia-settings-updates” package in Ubuntu: Invalid Status in “nvidia-settings” source package in Precise: New Status in “nvidia-settings-experimental-304” source package in Precise: New Status in “nvidia-settings-experimental-310” source package in Precise: New Status in “nvidia-settings-updates” source package in Precise: New Bug description: package nvidia-settings was installed. Seemed to conflict somehow. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: nvidia-settings-experimental-310 (not installed) ProcVersionSignature: Ubuntu 3.2.0-32.51-generic 3.2.30 Uname: Linux 3.2.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu14 AptOrdering: nvidia-settings-experimental-310: Install nvidia-settings-experimental-310: Configure Architecture: amd64 Date: Thu Nov 8 17:00:14 2012 DpkgTerminalLog: Unpacking nvidia-settings-experimental-310 (from .../nvidia-settings-experimental-310_310.14-0ubuntu0.1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/nvidia-settings-experimental-310_310.14-0ubuntu0.1_amd64.deb (--unpack): trying to overwrite '/usr/bin/nvidia-settings', which is also in package nvidia-settings-updates 304.43-0ubuntu0.2 DuplicateSignature: Unpacking nvidia-settings-experimental-310 (from .../nvidia-settings-experimental-310_310.14-0ubuntu0.1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/nvidia-settings-experimental-310_310.14-0ubuntu0.1_amd64.deb (--unpack): trying to overwrite '/usr/bin/nvidia-settings', which is also in package nvidia-settings-updates 304.43-0ubuntu0.2 ErrorMessage: trying to overwrite '/usr/bin/nvidia-settings', which is also in package nvidia-settings-updates 304.43-0ubuntu0.2 InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) SourcePackage: nvidia-settings-experimental-310 Title: package nvidia-settings-experimental-310 (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/nvidia-settings', which is also in package nvidia-settings-updates 304.43-0ubuntu0.2 UpgradeStatus: Upgraded to precise on 2012-05-16 (176 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1076414/+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 1100994] Re: The quantal version of nvidia-settings doesn't support legacy nvidia driver (173)
It might be worth to take a little peekaboo over the shoulder of our big sister Debian: http://packages.qa.debian.org/n/nvidia-settings-legacy-173xx.html http://packages.qa.debian.org/n/nvidia-graphics-drivers-legacy- 173xx.html Would be nice to have this fixed before 12.04.4 ** Tags added: precise ** Tags added: regression-proposed ** Summary changed: - The quantal version of nvidia-settings doesn't support legacy nvidia driver (173) + The quantal version of nvidia-settings doesn't support legacy nvidia driver (173) and tends to be backported to Precise 12.04.3 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1100994 Title: The quantal version of nvidia-settings doesn't support legacy nvidia driver (173) and tends to be backported to Precise 12.04.3 Status in “nvidia-settings” package in Ubuntu: Confirmed Bug description: When I tried to configure my display using the nvidia-settings package from Quantal repository, I meet the error message: The NVIDIA X driver on (...) is not new enough to support the nvidia-settings Display Configuration page.. It makes sense, because I'm using the legacy nvidia-173 driver. My non-elegant soluction was install the nvidia-settings from Precise repository, that solved the problem. Being more precise: $ dpkg -l |grep nvidia ii nvidia-173 173.14.36-0ubuntu0.1 i386 ii nvidia-settings 304.51-0ubuntu2 i386 DIDN'T WORKS but $ dpkg -l |grep nvidia ii nvidia-173 173.14.36-0ubuntu0.1 i386 ii nvidia-settings 295.33-0ubuntu1 i386 WORKS There is no package that the name is something like nvidia- settings-173 available in Quantal repository, but it's required to configure properly a old Nvidia device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1100994/+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
