[Bug 1267442] Re: Install nvidia-331 on X/K/Lubuntu results in unbootable machine
OLD stuff. Time to close this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1267442 Title: Install nvidia-331 on X/K/Lubuntu results in unbootable machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1267442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886074] Re: "please reboot" - too often
$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04 LTS Release:20.04 Codename: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886074 Title: "please reboot" - too often To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1886074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886074] [NEW] "please reboot" - too often
Public bug reported: $ uname -a Linux wkbx 5.4.0-40-generic #44-Ubuntu SMP Tue Jun 23 00:01:04 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux "5.4.0-40-generic" was installed this morning at 2020-07-02_06h14m19s CET, leaving 5.4.0-39-generic pending for removal. So... $ sudo apt-get purge linux-headers-5.4.0-39 linux- headers-5.4.0-39-generic linux-image-5.4.0-39-generic linux- modules-5.4.0-39-generic linux-modules-extra-5.4.0-39-generic linux- modules-nvidia-440-5.4.0-39-generic Just minutes after(?), I got a request to reboot, to finish the update. Really necessary for removing the unused kernel and its associated packages? ** Affects: nvidia-prime (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886074 Title: "please reboot" - too often To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1886074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785804] [NEW] package linux-image-4.15.0-30-generic (not installed) failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1
Public bug reported: Install guidelines MISSING for HWE-virtual-16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-30-generic (not installed) ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 AptOrdering: linux-image-4.15.0-30-generic: Purge NULL: ConfigurePending Architecture: amd64 Date: Tue Aug 7 13:10:07 2018 ErrorMessage: subprocess installed pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-08-12 (724 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: linux-signed-hwe Title: package linux-image-4.15.0-30-generic (not installed) failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1785804 Title: package linux-image-4.15.0-30-generic (not installed) failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1785804/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682637] Re: during recovery mode, enable network failed due to /etc/resolv.conf not being present
I can confirm "Daniel Pietrucha (texar)"'s experience. Boot into the recovery console and run # dpkg-reconfigure resolvconf ... # apt update # worked immediately afterwards. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1682637 Title: during recovery mode, enable network failed due to /etc/resolv.conf not being present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1682637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1595656] Re: modprobe ftdi_sio - nonfunctional for (some) devices
$ apport-collect 1595656
/usr/share/apport/apport-gtk:16: PyGIWarning: Wnck was imported without
specifying a version first. Use gi.require_version('Wnck', '3.0') before import
to ensure that the right version gets loaded.
from gi.repository import GLib, Wnck, GdkX11, Gdk
The authorization page:
(https://launchpad.net/+authorize-token?oauth_token=wfwD64wHlJgZ2nJxKf50_permission=DESKTOP_INTEGRATION)
should be opening in your browser. Use your browser to authorize
this program to access Launchpad on your behalf.
Waiting to hear from Launchpad about your decision...
Package linux-lts-xenial not installed and no hook available, ignoring
Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1595656
Title:
modprobe ftdi_sio - nonfunctional for (some) devices
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/1595656/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1595656] Re: modprobe ftdi_sio - nonfunctional for (some) devices
I get no entry for 4.7 in the grub boot menu. All attempts to get to 4.7 was done on 16.04. End of tries for now. I have other things to do. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1595656 Title: modprobe ftdi_sio - nonfunctional for (some) devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/1595656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1595656] Re: modprobe ftdi_sio - nonfunctional for (some) devices
$ sudo apt-get purge linux-headers-4.7.0-040700rc4 linux-headers-4.7.0-040700rc4-generic linux-image-4.7.0-040700rc4-generic ... $ cat ../inst.sh sudo dpkg -i *.deb sudo update-initramfs -u sudo update-grub2 $ . ../inst.sh Selecting previously unselected package linux-headers-4.7.0-040700rc4. (Reading database ... 203148 files and directories currently installed.) Preparing to unpack linux-headers-4.7.0-040700rc4_4.7.0-040700rc4.201606201235_all.deb ... Unpacking linux-headers-4.7.0-040700rc4 (4.7.0-040700rc4.201606201235) ... Selecting previously unselected package linux-headers-4.7.0-040700rc4-generic. Preparing to unpack linux-headers-4.7.0-040700rc4-generic_4.7.0-040700rc4.201606201235_amd64.deb ... Unpacking linux-headers-4.7.0-040700rc4-generic (4.7.0-040700rc4.201606201235) ... Selecting previously unselected package linux-image-4.7.0-040700rc4-generic. Preparing to unpack linux-image-4.7.0-040700rc4-generic_4.7.0-040700rc4.201606201235_amd64.deb ... Examining /etc/kernel/preinst.d/ run-parts: executing /etc/kernel/preinst.d/intel-microcode 4.7.0-040700rc4-generic /boot/vmlinuz-4.7.0-040700rc4-generic Done. Unpacking linux-image-4.7.0-040700rc4-generic (4.7.0-040700rc4.201606201235) ... Setting up linux-headers-4.7.0-040700rc4 (4.7.0-040700rc4.201606201235) ... Setting up linux-headers-4.7.0-040700rc4-generic (4.7.0-040700rc4.201606201235) ... Examining /etc/kernel/header_postinst.d. run-parts: executing /etc/kernel/header_postinst.d/dkms 4.7.0-040700rc4-generic /boot/vmlinuz-4.7.0-040700rc4-generic Setting up linux-image-4.7.0-040700rc4-generic (4.7.0-040700rc4.201606201235) ... Running depmod. update-initramfs: deferring update (hook will be called later) Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.7.0-040700rc4-generic /boot/vmlinuz-4.7.0-040700rc4-generic run-parts: executing /etc/kernel/postinst.d/dkms 4.7.0-040700rc4-generic /boot/vmlinuz-4.7.0-040700rc4-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.7.0-040700rc4-generic /boot/vmlinuz-4.7.0-040700rc4-generic update-initramfs: Generating /boot/initrd.img-4.7.0-040700rc4-generic W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/sw_method_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/sw_bundle_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/sw_nonctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/sw_ctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/gpccs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/gpccs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/gpccs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/gpccs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/fecs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/fecs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/fecs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm206/gr/fecs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm206/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm206/acr/ucode_load.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm206/acr/bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm204/gr/sw_method_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm204/gr/sw_bundle_init.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm204/gr/sw_nonctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm204/gr/sw_ctx.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm204/gr/gpccs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm204/gr/gpccs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm204/gr/gpccs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm204/gr/gpccs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm204/gr/fecs_sig.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm204/gr/fecs_data.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm204/gr/fecs_inst.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm204/gr/fecs_bl.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm204/acr/ucode_unload.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm204/acr/ucode_load.bin for module nouveau W: Possible missing firmware /lib/firmware/nvidia/gm204/acr/bl.bin for module nouveau W: Possible missing
[Bug 1595656] Re: modprobe ftdi_sio - nonfunctional for (some) devices
$ sudo apt-get purge nvidia-361 nvidia-opencl-icd-361 nvidia-prime nvidia-settings [sudo] password for hannu: Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: nvidia-361* nvidia-opencl-icd-361* nvidia-prime* nvidia-settings* 0 upgraded, 0 newly installed, 4 to remove and 0 not upgraded. After this operation, 339 MB disk space will be freed. Do you want to continue? [Y/n] Y (Reading database ... 237085 files and directories currently installed.) Removing nvidia-361 (361.42-0ubuntu2) ... Stopping nvidia-persistenced nvidia-persistenced: no process found Done. Removing all DKMS Modules Done. update-alternatives: using /usr/lib/nvidia-361-prime/ld.so.conf to provide /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf (x86_64-linux-gnu_gl_conf) in auto mode update-alternatives: using /usr/lib/nvidia-361-prime/ld.so.conf to provide /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf (x86_64-linux-gnu_egl_conf) in auto mode update-alternatives: using /usr/lib/nvidia-361-prime/alt_ld.so.conf to provide /etc/ld.so.conf.d/i386-linux-gnu_GL.conf (i386-linux-gnu_gl_conf) in auto mode update-alternatives: using /usr/lib/nvidia-361-prime/alt_ld.so.conf to provide /etc/ld.so.conf.d/i386-linux-gnu_EGL.conf (i386-linux-gnu_egl_conf) in auto mode update-alternatives: using /usr/lib/x86_64-linux-gnu/mesa/ld.so.conf to provide /etc/ld.so.conf.d/x86_64-linux-gnu_GL.conf (x86_64-linux-gnu_gl_conf) in auto mode update-alternatives: using /usr/lib/x86_64-linux-gnu/mesa-egl/ld.so.conf to provide /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf (x86_64-linux-gnu_egl_conf) in auto mode INFO:Disable nvidia-361 DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude update-initramfs: deferring update (trigger activated) Purging configuration files for nvidia-361 (361.42-0ubuntu2) ... update-initramfs: deferring update (trigger activated) Removing nvidia-opencl-icd-361 (361.42-0ubuntu2) ... Purging configuration files for nvidia-opencl-icd-361 (361.42-0ubuntu2) ... Removing nvidia-prime (0.8.2) ... Purging configuration files for nvidia-prime (0.8.2) ... Removing nvidia-settings (361.42-0ubuntu1) ... Purging configuration files for nvidia-settings (361.42-0ubuntu1) ... Processing triggers for libc-bin (2.23-0ubuntu3) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for initramfs-tools (0.122ubuntu8.1) ... update-initramfs: Generating /boot/initrd.img-4.7.0-040700rc4-generic Processing triggers for bamfdaemon (0.5.3~bzr0+16.04.20160523-0ubuntu1) ... Rebuilding /usr/share/applications/bamf-2.index... Processing triggers for gnome-menus (3.13.3-6ubuntu3) ... Processing triggers for desktop-file-utils (0.22-1ubuntu5) ... Processing triggers for mime-support (3.59ubuntu1) ... $ sudo reboot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1595656 Title: modprobe ftdi_sio - nonfunctional for (some) devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/1595656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1595656] Re: modprobe ftdi_sio - nonfunctional for (some) devices
$ sudo dpkg-reconfigure nvidia-361 [sudo] password for hannu: Stopping nvidia-persistenced nvidia-persistenced: no process found Done. Removing all DKMS Modules Done. update-initramfs: deferring update (trigger activated) update-initramfs: Generating /boot/initrd.img-4.4.0-22-generic INFO:Enable nvidia-361 DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude Loading new nvidia-361-361.42 DKMS files... Building for 4.4.0-22-generic and 4.7.0-040700rc4-generic Building for architecture x86_64 Building initial module for 4.4.0-22-generic Done. nvidia_361: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/4.4.0-22-generic/updates/dkms/ nvidia_361_modeset.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/4.4.0-22-generic/updates/dkms/ nvidia_361_uvm.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/4.4.0-22-generic/updates/dkms/ depmod DKMS: install completed. Building initial module for 4.7.0-040700rc4-generic ERROR (dkms apport): kernel package linux-headers-4.7.0-040700rc4-generic is not supported Error! Bad return status for module build on kernel: 4.7.0-040700rc4-generic (x86_64) Consult /var/lib/dkms/nvidia-361/361.42/build/make.log for more information. Processing triggers for initramfs-tools (0.122ubuntu8.1) ... update-initramfs: Generating /boot/initrd.img-4.7.0-040700rc4-generic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1595656 Title: modprobe ftdi_sio - nonfunctional for (some) devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/1595656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1595656] Re: modprobe ftdi_sio - nonfunctional for (some) devices
#8 is https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics- drivers-361/+bug/1573508 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1595656 Title: modprobe ftdi_sio - nonfunctional for (some) devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/1595656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1595656] Re: modprobe ftdi_sio - nonfunctional for (some) devices
$ cat /var/lib/dkms/nvidia-361/361.42/build/make.log
...
In file included from ./arch/x86/include/asm/processor.h:15:0,
from ./arch/x86/include/asm/cpufeature.h:4,
from ./arch/x86/include/asm/thread_info.h:52,
from include/linux/thread_info.h:54,
from ./arch/x86/include/asm/preempt.h:6,
from include/linux/preempt.h:59,
from include/linux/spinlock.h:50,
from include/linux/mmzone.h:7,
from include/linux/gfp.h:5,
from include/linux/mm.h:9,
from
/var/lib/dkms/nvidia-361/361.42/build/common/inc/nv-pgprot.h:17,
from
/var/lib/dkms/nvidia-361/361.42/build/common/inc/nv-linux.h:17,
from
/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:15:
/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c: In function
‘os_lock_user_pages’:
./arch/x86/include/asm/current.h:17:17: warning: passing argument 1 of
‘get_user_pages’ makes integer from pointer without a cast [-Wint-conversion]
#define current get_current()
^
/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:119:26: note: in
expansion of macro ‘current’
ret = get_user_pages(current, mm, (unsigned long)address,
^
In file included from
/var/lib/dkms/nvidia-361/361.42/build/common/inc/nv-pgprot.h:17:0,
from
/var/lib/dkms/nvidia-361/361.42/build/common/inc/nv-linux.h:17,
from
/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:15:
include/linux/mm.h:1254:6: note: expected ‘long unsigned int’ but argument is
of type ‘struct task_struct *’
long get_user_pages(unsigned long start, unsigned long nr_pages,
^
/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:119:35: warning:
passing argument 2 of ‘get_user_pages’ makes integer from pointer without a
cast [-Wint-conversion]
ret = get_user_pages(current, mm, (unsigned long)address,
^
In file included from
/var/lib/dkms/nvidia-361/361.42/build/common/inc/nv-pgprot.h:17:0,
from
/var/lib/dkms/nvidia-361/361.42/build/common/inc/nv-linux.h:17,
from
/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:15:
include/linux/mm.h:1254:6: note: expected ‘long unsigned int’ but argument is
of type ‘struct mm_struct *’
long get_user_pages(unsigned long start, unsigned long nr_pages,
^
/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:120:25: warning:
passing argument 5 of ‘get_user_pages’ makes pointer from integer without a
cast [-Wint-conversion]
page_count, write, force, user_pages, NULL);
^
In file included from
/var/lib/dkms/nvidia-361/361.42/build/common/inc/nv-pgprot.h:17:0,
from
/var/lib/dkms/nvidia-361/361.42/build/common/inc/nv-linux.h:17,
from
/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:15:
include/linux/mm.h:1254:6: note: expected ‘struct page **’ but argument is of
type ‘NvBool {aka unsigned char}’
long get_user_pages(unsigned long start, unsigned long nr_pages,
^
/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:120:32: warning:
passing argument 6 of ‘get_user_pages’ makes pointer from integer without a
cast [-Wint-conversion]
page_count, write, force, user_pages, NULL);
^
In file included from
/var/lib/dkms/nvidia-361/361.42/build/common/inc/nv-pgprot.h:17:0,
from
/var/lib/dkms/nvidia-361/361.42/build/common/inc/nv-linux.h:17,
from
/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:15:
include/linux/mm.h:1254:6: note: expected ‘struct vm_area_struct **’ but
argument is of type ‘NvBool {aka unsigned char}’
long get_user_pages(unsigned long start, unsigned long nr_pages,
^
/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:119:11: error: too many
arguments to function ‘get_user_pages’
ret = get_user_pages(current, mm, (unsigned long)address,
^
In file included from
/var/lib/dkms/nvidia-361/361.42/build/common/inc/nv-pgprot.h:17:0,
from
/var/lib/dkms/nvidia-361/361.42/build/common/inc/nv-linux.h:17,
from
/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:15:
include/linux/mm.h:1254:6: note: declared here
long get_user_pages(unsigned long start, unsigned long nr_pages,
^
/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:132:13: error: implicit
declaration of function ‘page_cache_release’
[-Werror=implicit-function-declaration]
page_cache_release(user_pages[i]);
^
cc1: some warnings being treated as errors
scripts/Makefile.build:289: recipe for target
'/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.o' failed
make[2]: *** [/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.o] Error 1
make[2]: *** Waiting for
[Bug 1595656] Re: modprobe ftdi_sio - nonfunctional for (some) devices
$ wget
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7-rc4-yakkety/{linux-headers-4.7.0-040700rc4-generic_4.7.0-040700rc4.201606201235_amd64.deb,linux-image-4.7.0-040700rc4-generic_4.7.0-040700rc4.201606201235_amd64.deb,linux-headers-4.7.0-040700rc4_4.7.0-040700rc4.201606201235_all.deb}
Downloaded: 3 files, 67M in 31s (2,19 MB/s)
$ sudo dpkg -i *.deb
[sudo] password for hannu:
Selecting previously unselected package linux-headers-4.7.0-040700rc4.
(Reading database ... 204098 files and directories currently installed.)
Preparing to unpack
linux-headers-4.7.0-040700rc4_4.7.0-040700rc4.201606201235_all.deb ...
Unpacking linux-headers-4.7.0-040700rc4 (4.7.0-040700rc4.201606201235) ...
Selecting previously unselected package linux-headers-4.7.0-040700rc4-generic.
Preparing to unpack
linux-headers-4.7.0-040700rc4-generic_4.7.0-040700rc4.201606201235_amd64.deb ...
Unpacking linux-headers-4.7.0-040700rc4-generic (4.7.0-040700rc4.201606201235)
...
Selecting previously unselected package linux-image-4.7.0-040700rc4-generic.
Preparing to unpack
linux-image-4.7.0-040700rc4-generic_4.7.0-040700rc4.201606201235_amd64.deb ...
Examining /etc/kernel/preinst.d/
run-parts: executing /etc/kernel/preinst.d/intel-microcode
4.7.0-040700rc4-generic /boot/vmlinuz-4.7.0-040700rc4-generic
Done.
Unpacking linux-image-4.7.0-040700rc4-generic (4.7.0-040700rc4.201606201235) ...
Setting up linux-headers-4.7.0-040700rc4 (4.7.0-040700rc4.201606201235) ...
Setting up linux-headers-4.7.0-040700rc4-generic (4.7.0-040700rc4.201606201235)
...
Examining /etc/kernel/header_postinst.d.
run-parts: executing /etc/kernel/header_postinst.d/dkms 4.7.0-040700rc4-generic
/boot/vmlinuz-4.7.0-040700rc4-generic
Error! Bad return status for module build on kernel: 4.7.0-040700rc4-generic
(x86_64)
Consult /var/lib/dkms/nvidia-361/361.42/build/make.log for more information.
Setting up linux-image-4.7.0-040700rc4-generic (4.7.0-040700rc4.201606201235)
...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal
4.7.0-040700rc4-generic /boot/vmlinuz-4.7.0-040700rc4-generic
run-parts: executing /etc/kernel/postinst.d/dkms 4.7.0-040700rc4-generic
/boot/vmlinuz-4.7.0-040700rc4-generic
ERROR: Cannot create report: [Errno 17] File exists:
'/var/crash/nvidia-361.0.crash'
Error! Bad return status for module build on kernel: 4.7.0-040700rc4-generic
(x86_64)
Consult /var/lib/dkms/nvidia-361/361.42/build/make.log for more information.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools
4.7.0-040700rc4-generic /boot/vmlinuz-4.7.0-040700rc4-generic
update-initramfs: Generating /boot/initrd.img-4.7.0-040700rc4-generic
run-parts: executing /etc/kernel/postinst.d/pm-utils 4.7.0-040700rc4-generic
/boot/vmlinuz-4.7.0-040700rc4-generic
run-parts: executing /etc/kernel/postinst.d/unattended-upgrades
4.7.0-040700rc4-generic /boot/vmlinuz-4.7.0-040700rc4-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier
4.7.0-040700rc4-generic /boot/vmlinuz-4.7.0-040700rc4-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub
4.7.0-040700rc4-generic /boot/vmlinuz-4.7.0-040700rc4-generic
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.7.0-040700rc4-generic
Found initrd image: /boot/initrd.img-4.7.0-040700rc4-generic
Found linux image: /boot/vmlinuz-4.4.0-22-generic
Found initrd image: /boot/initrd.img-4.4.0-22-generic
Found Ubuntu 14.04.4 LTS (14.04) on /dev/sda2
Adding boot menu entry for EFI firmware configuration
done
Comment:
Hmm... without the nvidia stuff I have less of display to read on... Well, I'll
try anyway...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1595656
Title:
modprobe ftdi_sio - nonfunctional for (some) devices
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/1595656/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1595656] Re: modprobe ftdi_sio - nonfunctional for (some) devices
May I suggest that any mention of the link in #3 (above) be presented,
like this.
QUOTE
https://wiki.ubuntu.com/KernelMainlineBuilds at "Installing upstream kernels
(manually)" ("uninstalling" is just slightly down from there)
UNQUOTE
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1595656
Title:
modprobe ftdi_sio - nonfunctional for (some) devices
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/1595656/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1595656] Re: modprobe ftdi_sio - nonfunctional for (some) devices
Is there a VERY hands on guide on how to install the very latest kernel? I know this is a question about installing .deb packages... But which ones do I need? amd64 for sure, but there are several to choose from. And how do I install them in a manner that makes then easily removable? I'm sorry, but I'm not ready to gobble through pages of text to accomplish this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1595656 Title: modprobe ftdi_sio - nonfunctional for (some) devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/1595656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1595656] Re: modprobe ftdi_sio - nonfunctional for (some) devices
linux-image-extra-3.13.0-24-generic ==> and all versions after it? Probably a few before it too. It sure exists in the current 4.4 too (current for Ubuntu 16.04) ** Package changed: linux (Ubuntu) => linux-lts-xenial (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1595656 Title: modprobe ftdi_sio - nonfunctional for (some) devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/1595656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1595656] [NEW] modprobe ftdi_sio - nonfunctional for (some) devices
Public bug reported: $ cat /proc/version_signature Ubuntu 4.2.0-27.32~14.04.1-generic 4.2.8-ckt1 --- --- Some background: I have recently acquired a Flashforge Creator Pro 2016, a FDM/FFF 3D- printer that came with the [Open source "Sailfish" firmware][1]. Now to use the advanced features of the firmware you need to use "[ReplicatorG][2]" (free software) and connect to the printer using the provided USB-cable. This relies on FTDI-based communications with it's ATMega 2560 -based controller board (Mightyboard 2560) I can currently run Windows in a virtual machine (Virtualbox) and use ReplicatorG for the full set of features, including firmware updates (did that yesterday). BUT, this is not possible using Ubuntu (14.04.4 and 16.04 installed and used in attempts) >From what I can see I should use sudo modprobe ftdi-sio sudo chmod 666 /sys/bus/usb-serial/drivers/ftdi_sio/new_id sudo echo "23c1 d314" > /sys/bus/usb-serial/drivers/ftdi_sio/new_id ... then simply connect the cable. This DOES set up /dev/ttyUSB0 and /dev/ttyUSB1 as expected, but these are nonfunctional What I see is this, in dmesg [ 2832.712115] usb 1-7: USB disconnect, device number 10 [ 2832.712430] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0 [ 2832.712457] ftdi_sio 1-7:1.0: device disconnected [ 2832.712775] ftdi_sio ttyUSB1: FTDI USB Serial Device converter now disconnected from ttyUSB1 [ 2832.712815] ftdi_sio 1-7:1.1: device disconnected [ 2840.832455] usb 1-7: new full-speed USB device number 11 using xhci_hcd [ 2840.962313] usb 1-7: New USB device found, idVendor=23c1, idProduct=d314 [ 2840.962317] usb 1-7: New USB device strings: Mfr=1, Product=2, SerialNumber=220 [ 2840.962319] usb 1-7: Product: The Replicator [ 2840.962321] usb 1-7: Manufacturer: MakerBot Industries [ 2840.962322] usb 1-7: SerialNumber: [ 2840.962443] usb 1-7: ep 0x82 - rounding interval to 1024 microframes, ep desc says 2040 microframes [ 2840.962871] ftdi_sio 1-7:1.0: FTDI USB Serial Device converter detected [ 2840.962898] usb 1-7: Detected FT2232C [ 2840.962984] ftdi_sio ttyUSB0: Unable to read latency timer: -32 [ 2840.963048] ftdi_sio ttyUSB0: Unable to write latency timer: -32 [ 2840.963119] usb 1-7: FTDI USB Serial Device converter now attached to ttyUSB0 [ 2840.963188] ftdi_sio 1-7:1.1: FTDI USB Serial Device converter detected [ 2840.963210] usb 1-7: Detected FT2232C [ 2840.963273] ftdi_sio ttyUSB1: Unable to read latency timer: -32 [ 2840.963365] ftdi_sio ttyUSB1: Unable to write latency timer: -32 [ 2840.963423] usb 1-7: FTDI USB Serial Device converter now attached to ttyUSB1 [ 2840.977742] ftdi_sio ttyUSB0: ftdi_set_termios FAILED to set databits/stopbits/parity [ 2840.977838] ftdi_sio ttyUSB0: ftdi_set_termios urb failed to set baudrate [ 2840.977932] ftdi_sio ttyUSB0: urb failed to set to xon/xoff flow control [ 2840.978117] ftdi_sio ttyUSB0: ftdi_set_termios urb failed to set baudrate [ 2840.978207] ftdi_sio ttyUSB0: urb failed to set to xon/xoff flow control [ 2840.978301] ftdi_sio ttyUSB0: Unable to write latency timer: -32 [ 2840.978393] ftdi_sio ttyUSB0: ftdi_set_termios error from disable flowcontrol urb [ 2840.978581] ftdi_sio ttyUSB0: urb failed to set to xon/xoff flow control [ 2840.978914] ftdi_sio ttyUSB1: ftdi_set_termios FAILED to set databits/stopbits/parity [ 2840.979006] ftdi_sio ttyUSB1: ftdi_set_termios urb failed to set baudrate [ 2840.979099] ftdi_sio ttyUSB1: urb failed to clear flow control [ 2840.979274] ftdi_sio ttyUSB1: ftdi_set_termios urb failed to set baudrate [ 2840.979372] ftdi_sio ttyUSB1: urb failed to set to xon/xoff flow control [ 2840.979470] ftdi_sio ttyUSB1: Unable to write latency timer: -32 [ 2840.979568] ftdi_sio ttyUSB1: ftdi_set_termios error from disable flowcontrol urb [ 2840.979763] ftdi_sio ttyUSB1: urb failed to set to xon/xoff flow control [ 2841.078912] ftdi_sio ttyUSB0: ftdi_set_termios urb failed to set baudrate [ 2841.079142] ftdi_sio ttyUSB0: urb failed to set to xon/xoff flow control [ 2841.079309] ftdi_sio ttyUSB0: Unable to write latency timer: -32 [ 2841.079437] ftdi_sio ttyUSB0: failed to get modem status: -32 [ 2841.079697] ftdi_sio ttyUSB0: ftdi_set_termios FAILED to set databits/stopbits/parity [ 2841.079761] ftdi_sio ttyUSB0: ftdi_set_termios urb failed to set baudrate [ 2841.079858] ftdi_sio ttyUSB0: urb failed to set to xon/xoff flow control [ 2841.080070] ftdi_sio ttyUSB0: urb failed to set to xon/xoff flow control [ 2841.080176] ftdi_sio ttyUSB0: Unable to write latency timer: -32 [ 2841.080279] ftdi_sio ttyUSB0: ftdi_set_termios error from disable flowcontrol urb [ 2841.080471] ftdi_sio ttyUSB0: urb failed to set to xon/xoff flow control [ 2841.080571] ftdi_sio ttyUSB1: ftdi_set_termios urb failed to set baudrate [ 2841.080768] ftdi_sio ttyUSB1: urb failed to set to xon/xoff flow control [ 2841.180973] ftdi_sio ttyUSB0: ftdi_set_termios urb failed to set baudrate [ 2841.181177] ftdi_sio ttyUSB0: urb
[Bug 1589049] Re: Desktop Background -- Cropping source for second monitor
+ Logout and the backgrounds are displayed correctly. + This is present in 16.04 too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1589049 Title: Desktop Background -- Cropping source for second monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1589049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1589049] [NEW] Desktop Background -- Cropping source for second monitor
Public bug reported: System settings > Appearance > Background With a lower resolution display (Asus/ACI VC279 1920x1080, vertical/portrait orientation) as "left" screen and a 2560x1440 (Asus/ACI PA279, horizontal/landscape) on the right I get a crop of the cropped left screen image as background on the right screen. Original image: https://www.dropbox.com/s/c5cylr23lhztboj/2016-06-04_Grass_by_Jeremy_Hill.png?dl=0 Screen background, display setup: https://www.dropbox.com/s/p9m9v990eqhb5di/2016-06-04_ScreenCapture.png?dl=0 Facts: AT LOGIN; The original image gets cropped as background for the left side display as it is tilted 90 degrees - this is OK. The right side display gets a background based on the crop for the left side display - not OK. This background should be based on the *original* image. "Fix": Note that RE-SETTING the display background from "System Settings > Appearance" will display the backgrounds correctly for the remainder of the login. It will be wrong again after logout and re-login. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-control-center 14.04.3+14.04.20150916-0ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-27.32~14.04.1-generic 4.2.8-ckt1 Uname: Linux 4.2.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jun 4 08:47:54 2016 InstallationDate: Installed on 2014-04-02 (793 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: unity-control-center UpgradeStatus: Upgraded to trusty on 2014-04-24 (771 days ago) usr_lib_unity-control-center: deja-dup 30.0-0ubuntu4 gnome-control-center 1:3.6.3-0ubuntu56.1 ** Affects: unity-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1589049 Title: Desktop Background -- Cropping source for second monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1589049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1582805] [NEW] package nvidia-361 361.42-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10
*** This bug is a duplicate of bug 1579305 *** https://bugs.launchpad.net/bugs/1579305 Public bug reported: Requesting "Third party... " packages when installing from 64bit ubuntu 16.04 image A slight delay (20/30 seconds?) and then *boom* ProblemType: Package DistroRelease: Ubuntu 16.04 Package: nvidia-361 361.42-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.376 Date: Tue May 17 16:23:09 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 10 LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: nvidia-graphics-drivers-361 Title: package nvidia-361 361.42-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-361 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1582805 Title: package nvidia-361 361.42-0ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1582805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 977337] Re: Color profile for VGA dual-monitor reverts to default after reboot
Apparent, verified temporary fix: --- $ tail -n 1 /etc/group DUMMY:x:65535: --- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/977337 Title: Color profile for VGA dual-monitor reverts to default after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-color-manager/+bug/977337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1311362] Re: Ubuntu Gnome 14.04 - NVidia 331 - OpenCL broken (using Darktable)
For what it is worth - I have been through **almost** all of v304 (nvidia-current from USC) to latest xorg-edgers - in the end, here is the only currently working option for me, pseudo-code; purge-ppa ppa:xorg-edgers # purged the mesa libraries mentioned above among other things. apt-get purge nvidia* nvidia-opencl* nvidia-libopencl* libcuda1* sh NVIDIA-Linux-x86_64-340.17.run dkms registration of modules - not necessary gcc 4.6 used for driver, gcc 4.8 on system - CC check ignored. Now: $ dpkg --list | grep -E '^ii.*(nvidia|cuda)' displays 'ii nvidia-settings 331.20-0ubuntu8' Driver from http://www.geforce.co.uk/search/search- results?search=linux%20x64%20340.17%20-freebsd%20-solaris -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311362 Title: Ubuntu Gnome 14.04 - NVidia 331 - OpenCL broken (using Darktable) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1311362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1341140] [NEW] nvidia-setting not persistent.
Public bug reported: The following has a direct relation to not being able to save changed settings: nvidia-settings and the package files have an inconsistency that makes it hard if not impossible to get any changes to keep more than for the moment (at most). The settings file: /etc/alternatives/x86_64-linux-gnu_nvidia_app_profile has a note, e.g. $ head -n 10 /etc/alternatives/x86_64-linux-gnu_nvidia_app_profile # Application profiles for the NVIDIA Linux graphics driver, version 340.24 # Last modified: Wed Jul 2 15:07:50 PDT 2014 # These profiles were provided by NVIDIA and should not be modified. If you # wish to change the defaults provided here, you can override them by creating # custom rules in /etc/nvidia/nvidia-application-profiles-rc (which will apply # system-wide) or, for a given user, $HOME/.nv/nvidia-application-profiles-rc # (which will apply to that particular user). See the APPLICATION PROFILE # SEARCH PATH section of the NVIDIA Linux Graphics Driver README for more # information. ... that refers to the folder /etc/nvidia/ - which does not exist immediately after install. The file that refers to it is in /etc/alternatives/ ... where you find a lot of *nvidia* items. Clearly it is so though, that at least TWO of the files still need to be in /etc/nvidia to allow nvidia-settings to be at least somewhat functional. -- FIX -- pre $ gksudo nvidia-settings ERROR: nvidia-settings could not find the registry key file. This file should have been installed along with this driver at either /usr/share/nvidia/nvidia-application-profiles-337.25-key-documentation or /usr/share/nvidia/nvidia-application-profiles-key-documentation. The application profiles will continue to work, but values cannot be preopulated or validated, and will not be listed in the help text. Please see the README for possible values and descriptions. /pre ... is that familiar? Then do pre sudo bash ... mkdir -p /etc/nvidia cd /etc/nvidia ln -s /etc/alternatives/x86_64-linux-gnu_nvidia_app_profile_keys nvidia-application-profiles-340.24-key-documentation ln -s /etc/alternatives/x86_64-linux-gnu_nvidia_app_profile nvidia-application-profiles-340.24-rc /pre Then check that you can see something similar to: pre $ ls -l total 0 lrwxrwxrwx 1 root 58 jul 12 14:23 nvidia-application-profiles-340.24-key-documentation - /etc/alternatives/x86_64-linux-gnu_nvidia_app_profile_keys lrwxrwxrwx 1 root 53 jul 12 14:23 nvidia-application-profiles-340.24-rc - /etc/alternatives/x86_64-linux-gnu_nvidia_app_profile /pre Note that -340.24... and maybe other parts may differ for you (depending on version of the driver), what is shown is after installing the very latest from the xorg-edgers ppa at this writing. ** Affects: coreutils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1341140 Title: nvidia-setting not persistent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1341140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1341140] Re: nvidia-setting not persistent.
the smae and more: http://askubuntu.com/questions/477553/ubuntu-14-04-cant-get-nvidia-prime-working/496873#496873 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1341140 Title: nvidia-setting not persistent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1341140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1311362] Re: Ubuntu Gnome 14.04 - NVidia 331 - OpenCL broken (using Darktable)
I think this is something that is unrelated to nvidia and/or darktable - I had updates of lib-mesa on 2014-07-10 (Thursday) and believe I didn't run darktable much yesterday (Friday). It seems as darktable at least gets a bit further, with opencl_library =libnvidia-opencl.so.1 in ~/.config/darktable/darktablerc $ darktable -d opencl [opencl_init] opencl related configuration options: [opencl_init] [opencl_init] opencl: 1 [opencl_init] opencl_library: 'libnvidia-opencl.so.1' [opencl_init] opencl_memory_requirement: 768 [opencl_init] opencl_memory_headroom: 300 [opencl_init] opencl_device_priority: '*/!0,*/*/*' [opencl_init] opencl_size_roundup: 16 [opencl_init] opencl_async_pixelpipe: 0 [opencl_init] opencl_synch_cache: 0 [opencl_init] opencl_number_event_handles: 25 [opencl_init] opencl_micro_nap: 1000 [opencl_init] opencl_use_pinned_memory: 0 [opencl_init] opencl_use_cpu_devices: 0 [opencl_init] opencl_avoid_atomics: 0 [opencl_init] opencl_omit_whitebalance: 0 [opencl_init] [opencl_init] trying to load opencl library: 'libnvidia-opencl.so.1' [opencl_init] could not load all required symbols from library [opencl_init] no working opencl library found. Continue with opencl disabled [opencl_init] FINALLY: opencl is NOT AVAILABLE on this system. [opencl_init] initial status of opencl enabled flag is OFF. ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311362 Title: Ubuntu Gnome 14.04 - NVidia 331 - OpenCL broken (using Darktable) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1311362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1311362] Re: Ubuntu Gnome 14.04 - NVidia 331 - OpenCL broken (using Darktable)
For what it is worth: I have pulled out nvidia-340 (xorg-edgers) and am now down to 331.89 and settings from -340 - makes no difference. opencl_library=libnvidia-opencl.so.331.89 in ~/.config/darktable/darktablerc $ darktable -d opencl [opencl_init] opencl related configuration options: [opencl_init] [opencl_init] opencl: 1 [opencl_init] opencl_library: 'libnvidia-opencl.so.331.89' [opencl_init] opencl_memory_requirement: 768 [opencl_init] opencl_memory_headroom: 300 [opencl_init] opencl_device_priority: '*/!0,*/*/*' [opencl_init] opencl_size_roundup: 16 [opencl_init] opencl_async_pixelpipe: 0 [opencl_init] opencl_synch_cache: 0 [opencl_init] opencl_number_event_handles: 25 [opencl_init] opencl_micro_nap: 1000 [opencl_init] opencl_use_pinned_memory: 0 [opencl_init] opencl_use_cpu_devices: 0 [opencl_init] opencl_avoid_atomics: 0 [opencl_init] opencl_omit_whitebalance: 0 [opencl_init] [opencl_init] trying to load opencl library: 'libnvidia-opencl.so.331.89' [opencl_init] could not load all required symbols from library [opencl_init] no working opencl library found. Continue with opencl disabled [opencl_init] FINALLY: opencl is NOT AVAILABLE on this system. [opencl_init] initial status of opencl enabled flag is OFF. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311362 Title: Ubuntu Gnome 14.04 - NVidia 331 - OpenCL broken (using Darktable) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1311362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1329940] Re: No keyboard nor mouse after boot, login impossible
Related: http://askubuntu.com/q/489178/289138 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1329940 Title: No keyboard nor mouse after boot, login impossible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1329940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1331100] Re: The last line in /etc/groups - inactive
Forgot one thing; this bug may well be the cause for this: https://bugs.launchpad.net/ubuntu/+source/gnome-color- manager/+bug/977337 ... and potentially more of the same. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1331100 Title: The last line in /etc/groups - inactive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1331100/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1331100] Re: The last line in /etc/groups - inactive
I took it as security related - but you're probably right, it RESTRICTS instead of enabling access. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1331100 Title: The last line in /etc/groups - inactive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1331100/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1329940] Re: No keyboard nor mouse after boot, login impossible
Related: http://askubuntu.com/a/484923/289138 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1329940 Title: No keyboard nor mouse after boot, login impossible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1329940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1329940] Re: No keyboard nor mouse after boot, login impossible
NOTE: Virtualbox has lost the ability to access USB-devices, lsusb displays them, but NOTHING is detected by Virtualbox (Virtualbox, Settings, USB). This MIGHT be caused by the above. But I'm NOT sure linux-image-3.13.0-24-generic has worked in this regard. Current state: Hunting for clues. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1329940 Title: No keyboard nor mouse after boot, login impossible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1329940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1329940] Re: No keyboard nor mouse after boot, login impossible
$ tail -n 1 /etc/group vboxusers:x:127:hannu That was not directly related, dismissed, new bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1329940 Title: No keyboard nor mouse after boot, login impossible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1329940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 977337] Re: Color profile for VGA dual-monitor reverts to default after reboot
Problem back: The last group in: $ tail -n 3 /etc/group vboxusers:x:127:hannu nvidia-persistenced:x:128: appears NOT work. If I SWAP thos lines I get either USB in Virtualbox 4.3.12 working **OR** ALL screen-profiles loaded (created with System Settings Color Calibrate) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/977337 Title: Color profile for VGA dual-monitor reverts to default after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-color-manager/+bug/977337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1329940] [NEW] No keyboard nor mouse after boot, login impossible
Public bug reported: As it reads in summary. The same with recovery console. The collected data is from booting linux-image-3.13.0-24-generic, which is fully functional. --- version.log -- Ubuntu 3.13.0-24.47-generic 3.13.9 --- sudo lspci -vnvn lspci-vnvn.log --- 00:00.0 Host bridge [0600]: Intel Corporation 4th Gen Core Processor DRAM Controller [8086:0c00] (rev 06) Subsystem: ASUSTeK Computer Inc. Device [1043:8534] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- INTx- Latency: 0 Capabilities: [e0] Vendor Specific Information: Len=0c ? 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller [8086:0c01] (rev 06) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: e000-efff Memory behind bridge: f600-f70f Prefetchable memory behind bridge: e800-f1ff Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- BridgeCtl: Parity- SERR- NoISA- VGA+ MAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [88] Subsystem: ASUSTeK Computer Inc. Device [1043:8534] Capabilities: [80] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: feeff00c Data: 4181 Capabilities: [a0] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 256 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #2, Speed 8GT/s, Width x16, ASPM L0s L1, Exit Latency L0s 256ns, L1 8us ClockPM- Surprise- LLActRep- BwNot+ LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 8GT/s, Width x16, TrErr- Train- SlotClk+ DLActive- BWMgmt+ ABWMgmt+ SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise- Slot #1, PowerLimit 75.000W; Interlock- NoCompl+ SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg- Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock- Changed: MRL- PresDet- LinkState- RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible- RootCap: CRSVisible- RootSta: PME ReqID , PMEStatus- PMEPending- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR+, OBFF Via WAKE# ARIFwd- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Via WAKE# ARIFwd- LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete+, EqualizationPhase1+ EqualizationPhase2+, EqualizationPhase3+, LinkEqualizationRequest- Capabilities: [100 v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb:Fixed- WRR32- WRR64- WRR128- Ctrl: ArbSelect=Fixed Status: InProgress- VC0:Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans- Arb:Fixed+ WRR32- WRR64- WRR128- TWRR128- WRR256- Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=ff Status: NegoPending- InProgress- Capabilities: [140 v1] Root Complex Link Desc: PortNumber=02 ComponentID=01 EltType=Config Link0: Desc: TargetPort=00 TargetComponent=01 AssocRCRB- LinkType=MemMapped LinkValid+ Addr:
[Bug 1329940] Re: No keyboard nor mouse after boot, login impossible
initramfs booted with break=top debug=vc ** Attachment added: 20140613_230108.jpg https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1329940/+attachment/4131177/+files/20140613_230108.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1329940 Title: No keyboard nor mouse after boot, login impossible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1329940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1329940] Re: No keyboard nor mouse after boot, login impossible
@Joseph, I'll have a look - but it is close to midnight here... If it is a lengthy trip, I'll save it for tomorrow. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1329940 Title: No keyboard nor mouse after boot, login impossible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1329940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1329940] Re: No keyboard nor mouse after boot, login impossible
initramfs booted with break=top debug=vc + pull out and reinsert several USB devices (USB HDD, Mouse, Card reader, Keyboard - in that order). The mouse and keyboard are not usable in this state. ** Attachment added: 20140613_230441.jpg https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1329940/+attachment/4131178/+files/20140613_230441.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1329940 Title: No keyboard nor mouse after boot, login impossible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1329940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1329940] Re: No keyboard nor mouse after boot, login impossible
wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-utopic/linux-headers-3.15.0-031500-generic_3.15.0-031500.201406131105_amd64.deb wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-utopic/linux-headers-3.15.0-031500_3.15.0-031500.201406131105_all.deb wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-utopic/linux-image-3.15.0-031500-generic_3.15.0-031500.201406131105_amd64.deb $ sudo dpkg -i *.deb [sudo] password for hannu: Selecting previously unselected package linux-headers-3.15.0-031500. (Reading database ... 236712 files and directories currently installed.) Preparing to unpack linux-headers-3.15.0-031500_3.15.0-031500.201406131105_all.deb ... Unpacking linux-headers-3.15.0-031500 (3.15.0-031500.201406131105) ... Selecting previously unselected package linux-headers-3.15.0-031500-generic. Preparing to unpack linux-headers-3.15.0-031500-generic_3.15.0-031500.201406131105_amd64.deb ... Unpacking linux-headers-3.15.0-031500-generic (3.15.0-031500.201406131105) ... Selecting previously unselected package linux-image-3.15.0-031500-generic. Preparing to unpack linux-image-3.15.0-031500-generic_3.15.0-031500.201406131105_amd64.deb ... Done. Unpacking linux-image-3.15.0-031500-generic (3.15.0-031500.201406131105) ... Setting up linux-headers-3.15.0-031500 (3.15.0-031500.201406131105) ... Setting up linux-headers-3.15.0-031500-generic (3.15.0-031500.201406131105) ... Examining /etc/kernel/header_postinst.d. run-parts: executing /etc/kernel/header_postinst.d/dkms 3.15.0-031500-generic /boot/vmlinuz-3.15.0-031500-generic Setting up linux-image-3.15.0-031500-generic (3.15.0-031500.201406131105) ... Running depmod. update-initramfs: deferring update (hook will be called later) Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.15.0-031500-generic /boot/vmlinuz-3.15.0-031500-generic run-parts: executing /etc/kernel/postinst.d/dkms 3.15.0-031500-generic /boot/vmlinuz-3.15.0-031500-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.15.0-031500-generic /boot/vmlinuz-3.15.0-031500-generic update-initramfs: Generating /boot/initrd.img-3.15.0-031500-generic run-parts: executing /etc/kernel/postinst.d/pm-utils 3.15.0-031500-generic /boot/vmlinuz-3.15.0-031500-generic run-parts: executing /etc/kernel/postinst.d/update-notifier 3.15.0-031500-generic /boot/vmlinuz-3.15.0-031500-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.15.0-031500-generic /boot/vmlinuz-3.15.0-031500-generic Generating grub configuration file ... Found linux image: /boot/vmlinuz-3.15.0-031500-generic Found initrd image: /boot/initrd.img-3.15.0-031500-generic Found linux image: /boot/vmlinuz-3.13.0-24-generic Found initrd image: /boot/initrd.img-3.13.0-24-generic No volume groups found Adding boot menu entry for EFI firmware configuration Found memdisk: /boot/memdisk done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1329940 Title: No keyboard nor mouse after boot, login impossible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1329940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1329940] Re: No keyboard nor mouse after boot, login impossible
Right, I'll keep this for a while, unless I note something wierd - when the linux-image-3.13.0-24-generic will be back real quick. ;-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1329940 Title: No keyboard nor mouse after boot, login impossible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1329940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1329940] Re: No keyboard nor mouse after boot, login impossible
$ uname -a Linux wkbox 3.15.0-031500-generic #201406131105 SMP Fri Jun 13 15:06:46 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Successful boot, Mouse and keybaord works. System fully up as it seems from a VERY quick glance. So, I'll try to add kernel-fixed-upstream now... ;-P ** Tags added: kernel-fixed-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1329940 Title: No keyboard nor mouse after boot, login impossible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1329940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 977337] Re: Color profile for VGA dual-monitor reverts to default after reboot
General cleanup: 1. Uninstall of proprietary drivers, 2. over to xorg-edgers instead. 3. Startup applications (search 'start' in dash home) had dispcalGUI present as first item, 'Nvidia X server settings' as last. Removal of dispcal and uninstalling it ( apt get remove dispcal*') 4. followed by removal of Argyll1.6.3 (which I had added by hand)from $PATH Problem - fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/977337 Title: Color profile for VGA dual-monitor reverts to default after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-color-manager/+bug/977337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1267442] Re: Install nvidia-331 on X/K/Lubuntu results in unbootable machine
Display at the end of it. ** Attachment added: 20140605_221334.jpg https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1267442/+attachment/4126698/+files/20140605_221334.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1267442 Title: Install nvidia-331 on X/K/Lubuntu results in unbootable machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1267442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1267442] Re: Install nvidia-331 on X/K/Lubuntu results in unbootable machine
I cannot say I'm sure if this information helps, but in hope it does: OS: Pure Ubuntu (*not* X or L...) 13.10 apt-get upgrade to 14.04 LTS CTRL+Alt+F1 - login - Bash - sudo bash - # blacklisting of at least noveau REQUIRED to be able to get anywhere # *** more detail not investigated! # NOTE: I do NOT se the login prompt unless this is in place! # USE recovery mode boot - 'root prompt' on fsck'ed filesystems to get it in place. # cat /etc/modprobe.d/nvidia-graphics-drivers.conf blacklist nouveau blacklist lbm-nouveau blacklist nvidia-173 blacklist nvidia-96 blacklist nvidia-current blacklist nvidia-173-updates blacklist nvidia-96-updates alias nvidia nvidia_current_updates alias nouveau off alias lbm-nouveau off -- end of file -- Commands to install the OEM-driver. --- sudo service lightdm stop sudo apt-get purge nvidia* sudo apt-get update apt-get upgrade # In this step I got bitten by nvidia-prime getting pulled in by sudo apt-get install nvidia-331-updates-dev # From memory: init says nvidia-prime does not exist, start failed - in the last screenful of text # the following doesn't matter # as ^- stops with init telling it cannot start nvidia-prime (out of memory, from tty output) sudo sh NVIDIA-Linux-*-337.25.run --- NOTE: If I replace sudo apt-get install nvidia-331-updates-dev with sudo apt-get install nvidia-settings-319 nvidia-settings-319-updates the above sequence works. Summary, getting things to work: sudo service lightdm stop sudo apt-get purge nvidia* sudo apt-get update apt-get upgrade sudo apt-get install nvidia-settings-319 nvidia-settings-319-updates sudo sh NVIDIA-Linux-*-337.25.run -- on a working installation -- $ dpkg --list | grep nvidia ii nvidia-settings 331.20-0ubuntu8 amd64 Tool for configuring the NVIDIA graphics driver ii nvidia-settings-319 331.20-0ubuntu8 amd64 Transitional package for nvidia-settings ii nvidia-settings-319-updates 331.20-0ubuntu8 amd64 Transitional package for nvidia-settings hannu@wkbox ~ bash (P)PID=(3961)3969, s=0 $ apt-get install nvidia-331TAB nvidia-331nvidia-331-dev nvidia-331-updates nvidia-331-updates-dev nvidia-331-updates-uvm nvidia-331-uvm hannu@wkbox ~ bash (P)PID=(3961)3969, s=0 $ apt-get install nvidia-priTAB nvidia-prime hannu@wkbox ~ bash (P)PID=(3961)3969, s=0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1267442 Title: Install nvidia-331 on X/K/Lubuntu results in unbootable machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1267442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1267442] Re: Install nvidia-331 on X/K/Lubuntu results in unbootable machine
Ouch what a mess, is there a lt;PREgt; - thingy here? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1267442 Title: Install nvidia-331 on X/K/Lubuntu results in unbootable machine To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1267442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 977337] Re: Color profile for VGA dual-monitor reverts to default after reboot
NOTE: If Rhythmbox is started on one of the extra displays, AND there is Artwork to display - then the profiles gets pulled in - on ALL displays. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/977337 Title: Color profile for VGA dual-monitor reverts to default after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-color-manager/+bug/977337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 977337] Re: Color profile for VGA dual-monitor reverts to default after reboot
^--- gnome-color-manager 3.8.3-1ubuntu1 CHANGE: The FIRST monitor - the one that is active as tyhe machine boots - has the profile loaded as the desktop appears. The other three has to have profiles 'activated' through double clicks on the profile in System Settings Color. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/977337 Title: Color profile for VGA dual-monitor reverts to default after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-color-manager/+bug/977337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 977337] Re: Color profile for VGA dual-monitor reverts to default after reboot
https://bugs.launchpad.net/ubuntu/+source/gnome-color-manager/+bug/977337 https://bugs.launchpad.net/ubuntu/+source/gnome-color-manager/+bug/877843 https://bugs.launchpad.net/ubuntu/+source/gnome-color-manager/+bug/782571 https://bugs.launchpad.net/ubuntu/+source/gnome-color-manager/+bug/722083 https://bugs.launchpad.net/ubuntu/+source/gnome-color-manager/+bug/533961 Looks related to each other to me. $ uname -a Linux wkbox 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 14.04 LTS, 32GB RAM, i7-4770K, 3+TB disk. MB: ASUS Maximus Hero 6, GFX: Asus GTX780 DirectCU II/3GB Got Nvidia drivers running by first installing $ sudo apt-get install nvidia-settings-319 $ sudo apt-get install nvidia-settings-319-updates then followed by: $ sudo sh NVIDIA-Linux-x86_64-331.49.run The driver asks for signing, I said NO - didn't known how to get it signed. I currently have FOUR monitors, neither of them get the profile loaded at boot. I can double click each profile in System Settings Color - to apparentlu have them applied. Profiles created with www.datacolor.com / Spyder 4 and Ubuntu Color manager (System Settings Color) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/977337 Title: Color profile for VGA dual-monitor reverts to default after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-color-manager/+bug/977337/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
