[Ubuntu-x-swat] [Bug 1634802] Re: Could not insert module
A week or two ago, Software Updater started offering me version 304.134-0ubuntu0.16.10.1 It had never offered me the "fixed" version 304.132-0ubuntu2, but only the original version 304.132-0ubuntu1, which did not load into the kernel (with the mtrr_add and mtrr_del errors). I tried the 304.134-0ubuntu0.16.10.1 version offered, and it fails just like 304.132-0ubuntu1. Somehow, the fix never made it into my distribution repositories, and was not incorporated into the new 304.134-0ubuntu0.16.10.1 version. I still am forced to use an older version ( 304.131-0ubuntu5 ) in order to have an nvidia driver that both loads into the kernel, and allows Hugin to run correctly... scott@scott-ASUS-M2N68-AM-PLUS:~$ uname -a Linux scott-ASUS-M2N68-AM-PLUS 4.8.0-37-generic #39-Ubuntu SMP Thu Jan 26 02:27:07 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux scott@scott-ASUS-M2N68-AM-PLUS:~$ lsb_release -dsc Ubuntu 16.10 yakkety scott@scott-ASUS-M2N68-AM-PLUS:~$ echo $DESKTOP_SESSION Lubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1634802 Title: Could not insert module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1634802/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1634802] Re: Could not insert module
Well, I ended up with the nvidia-304 304.131-0ubuntu5 version, which loads into the kernel just fine, and also allows Hugin to function... I am curious - since the fixed 304.132-0ubuntu2 version loads into the kernel, why has it not yet made it into Yakkety? Since I cannot use it (see comment #22), it doesn't make much difference to me, but it probably would help other people. I see it is not yet available, because every day, I have to dismiss the Software Updater, which is constantly offering me the 304.132-0ubuntu1 version, with which it wants to replace my 304.131-0ubuntu5... -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1634802 Title: Could not insert module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1634802/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1641233] Re: nvidia-304 (not installed): nvidia-304 kernel module failed to build
Lubuntu noticed that I had 304.131-0ubuntu3, and Software Updates offered to install the (non-fixed) 304.132-0ubuntu1. In the changelog displayed, I noted that there was a 304.131-0ubuntu4 and 304.131-0ubuntu5. but the latest I found at the above website was 304.131-0ubuntu3. I see from the changelog: "Version 304.131-0ubuntu5: * debian/templates/control.in: - Add transitional packages to deprecate the -updates flavour. Version 304.131-0ubuntu4: * debian/templates/dkms.conf.in, debian/dkms/patches/buildfix_kernel_4.6.patch: - Add support for Linux 4.6." Since Lubuntu 16.04 used Linux 4.4.xxx, I am guessing that whatever changed in 4.6 that made 304.131-0ubuntu4 necessary is still present in 4.8, and thus possibly that is why 304.131-0ubuntu3 did not work. Why is there no version higher than 304.131-0ubuntu3 in the official (?) nvidia-graphics-drivers-304 site above? Where can I find 304.131-0ubuntu5 (at least 304.131-0ubuntu4, but I assume what bug(s) 304.131-0ubuntu5 fixed might somehow be important...)? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1641233 Title: nvidia-304 (not installed): nvidia-304 kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1641233/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1641233] [NEW] nvidia-304 (not installed): nvidia-304 kernel module failed to build
Public bug reported:
I had used nvidia-304 successfully in Lubuntu 16.04.
With Lubuntu 16.10, it would not load into the kernel.
I just recently downloaded a fixed 304.132 version, which loaded into the
kernel, and was
usable, but a program (Hugin) which had started up fine under nouveau (but
during the use of which nouveau had screen-crashed, forcing hard-shutdown),
failed to start, with the following terminal output:
"
The program 'hugin' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
(Details: serial 541 error_code 2 request_code 154 minor_code 24)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
"
Since Hugin had worked fine in Lubuntu 16.04 with nvidia-304 - 304.131,
I found a version of that for Xenial Xerus (304.131-0ubuntu3) at
https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304, and tried to
install that.
It failed to install, however...
"Building initial module for 4.8.0-27-generic
Error! Bad return status for module build on kernel: 4.8.0-27-generic (x86_64)
Consult /var/lib/dkms/nvidia-304/304.131/build/make.log for more information."
I will (try to) attach the log file for the install
("/var/lib/dkms/nvidia-304/304.131/build/make.log"), but here are the lines
containing the word "error":
"echo >&2 " ERROR: Kernel configuration is invalid."; \
echo >&2 " include/generated/autoconf.h or include/config/auto.conf are
missing.";\
echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix
it."; \
...
/var/lib/dkms/nvidia-304/304.131/build/nv-mlock.c:52: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-304/304.131/build/nv-linux.h:82:0,
from /var/lib/dkms/nvidia-304/304.131/build/nv-mlock.c:15:
./include/linux/mm.h:1315:6: note: declared here
long get_user_pages(unsigned long start, unsigned long nr_pages,
^~
/var/lib/dkms/nvidia-304/304.131/build/nv-mlock.c:65: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-304/304.131/build/nv-mlock.o' failed
make[3]: *** [/var/lib/dkms/nvidia-304/304.131/build/nv-mlock.o] Error 1
Makefile:1489: recipe for target
'_module_/var/lib/dkms/nvidia-304/304.131/build' failed
make[2]: *** [_module_/var/lib/dkms/nvidia-304/304.131/build] Error 2
NVIDIA: left KBUILD.
nvidia.ko failed to build!
Makefile:255: recipe for target 'module' failed
make[1]: *** [module] Error 1
makefile:59: recipe for target 'module' failed
make: *** [module] Error 2
"
I am hoping that there is some simple way to get this older version to
load/work,
as I am running out of options for being able to run Hugin:
1: nouveau screen-crashes in Hugin (which starts up fine) when I try to open
the images from which to make the panorama
2: the fixed nvidia-304.132 loads in the kernal, but Hugin crashes upon
starting up
3: the older nvidia-304.131 fails to install
4: I would consider going back to 16.04 (which is in one of 5 partitions which
I reserve for different Lubuntu versions as they come along), but grub, in
installing 16.10, somehow made booting 16.04 impossible (some sort of Emergency
terminal starts up, and I don't know enough of what's happening to know what to
do... The partition is fine - I can traverse the directory tree and look at
files, etc. but I cannot boot it...)
If anyone knows what is going on when I attempt to install 304.131 here in
Lubuntu 16.10,
and can advise me what to do. I would be very grateful.
--
scott@scott-ASUS-M2N68-AM-PLUS:~$ uname -a
Linux scott-ASUS-M2N68-AM-PLUS 4.8.0-27-generic #29-Ubuntu SMP Thu Oct 20
21:03:13 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
scott@scott-ASUS-M2N68-AM-PLUS:~$ lsb_release -dsc
Ubuntu 16.10
yakkety
scott@scott-ASUS-M2N68-AM-PLUS:~$ echo $DESKTOP_SESSION
Lubuntu
nvidia-graphics-drivers-304 (304.131-0ubuntu3) xenial;
--
ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: nvidia-304 304.131-0ubuntu3
ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
Uname: Linux 4.8.0-27-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
DKMSKernelVersion: 4.8.0-27-generic
Date: Fri Nov 11 15:48:41 2016
DuplicateSignature: dkms:
[Ubuntu-x-swat] [Bug 1634802] Re: Could not insert module
I installed the fix from zesty, and it loads into the kernal fine, and I can set the resolution that I want. However... Since before now I could not get nvidia-304 to work, I had been using nouveau. I had been able to start the panorama program Hugin, but when I tried to open the images to stitch together, the graphics driver nouveau crashed and I had to do a hard-shutdown. Now that I have a working nvidia-304, Hugin crashes with some sort of a x-window error when it tries to start up. " The program 'hugin' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 541 error_code 2 request_code 154 minor_code 24) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) " I don't know if it is the mere presence of nvidia-304, or THIS PARTICULAR nvidia-304. I don't know if it is the FIX that caused it, or something else. I can see that the version of nvidia-304 that I had been using under Lubuntu 16.04 (and which I used with Hugin with no problem) was 304.131xxx instead of .132. >From this output, can anyone say if it is a bug in nvidia-304, or Hugin that >is the problem? Say... I see that there is a .131 for Xenial Xerus. at the same site I got the fixed .132 ... Does anyone think there is likely to be a problem if I try to load that version of nvidia-304? I am inclined to try it... -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-304 in Ubuntu. https://bugs.launchpad.net/bugs/1634802 Title: Could not insert module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1634802/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1638431] [NEW] Screen "crash" (diagonal screen gibberish)
Public bug reported: This is a recurrent problem. For the last few Lubuntu installs, eventually, something that I invoke (one install, it was AbiWord, at least one it was Firefox, this time it is Hugin. [You may wonder - If this happens, why not install the proprietary driver nvidia-xxx? I have done so before, but this time for some reason it never gets into the kernel, and the largest screen resolution I have is 1024x768, which is much too small, especially for photo-editing... So I have to use nouveau, but as I say, I cannot now use Hugin.] Everything seems fine, I do something, and there is a pause... then the screen goes all diagonal gibberish, and the only thing I can do is hard- shutdown. I paid more attention this time, and can reproduce it on demand (not that I WANT to, but I need Hugin to stitch together some panoramas that I took on my trip, and since installing Lubuntu 16.10, when I go to load in the photos, there is a pause... then the screen crashes and I must hard-shutdown.) I have tried to simplify the debugging, and I booted from a Live-USB, the same .iso from which I installed Lubuntu 16.10 64-bit. I did nothing but install the hugin package (that, however, pulls in umpty ump other packages...) and mount my /data partition so I could point Hugin at my photos. I told Hugin which Images to Load, pressed Open, there was a pause... and it loaded them...! However, the upper half of the third image (sky?) was all gibberish, and not the image data. The globe thingy at the left seemed to have the full picture, so I went ahead and made the panorama, which was just fine - only that which was displayed on the screen was messed up. The garbage on the picture replaced itself if I went to a different tab, and then came back (although I don't guarantee it was the exact same garbage...). Today, when I reproduced the crash (so I could report the bug), I went to Syslog after hard-shutdown/boot, and copied down the info for the time it crashed...: Nov 1 21:13:00 scott-ASUS-M2N68-AM-PLUS dbus[680]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Nov 1 21:13:00 scott-ASUS-M2N68-AM-PLUS systemd[1]: Started Network Manager Script Dispatcher Service. Nov 1 21:13:00 scott-ASUS-M2N68-AM-PLUS nm-dispatcher: req:1 'dhcp4-change' [wlx001f1fd8314a]: new request (1 scripts) Nov 1 21:13:00 scott-ASUS-M2N68-AM-PLUS nm-dispatcher: req:1 'dhcp4-change' [wlx001f1fd8314a]: start running ordered scripts... Nov 1 21:17:01 scott-ASUS-M2N68-AM-PLUS CRON[2818]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Nov 1 21:22:34 scott-ASUS-M2N68-AM-PLUS kernel: [14975.927029] nouveau :00:0d.0: bus: MMIO write of 01620001 FAULT at 00b000 Nov 1 21:22:34 scott-ASUS-M2N68-AM-PLUS kernel: [14976.243884] nouveau :00:0d.0: bus: MMIO write of 01680001 FAULT at 00b020 Nov 1 21:22:42 scott-ASUS-M2N68-AM-PLUS kernel: [14983.698742] nouveau :00:0d.0: bus: MMIO write of 091f0001 FAULT at 00b030 Nov 1 21:22:42 scott-ASUS-M2N68-AM-PLUS kernel: [14983.704355] nouveau :00:0d.0: bus: MMIO write of 01730001 FAULT at 00b000 Nov 1 21:22:42 scott-ASUS-M2N68-AM-PLUS kernel: [14983.741432] nouveau :00:0d.0: bus: MMIO write of FAULT at 00b020 Nov 1 21:26:35 scott-ASUS-M2N68-AM-PLUS rsyslogd: [origin software="rsyslogd" swVersion="8.16.0" x-pid="720" x-info="http://www.rsyslog.com";] start Nov 1 21:26:35 scott-ASUS-M2N68-AM-PLUS rsyslogd: rsyslogd's groupid changed to 108 Nov 1 21:26:35 scott-ASUS-M2N68-AM-PLUS rsyslogd: rsyslogd's userid changed to 104 Nov 1 21:26:35 scott-ASUS-M2N68-AM-PLUS rsyslogd-2039: Could not open output pipe '/dev/xconsole':: No such file or directory [v8.16.0 try http://www.rsyslog.com/e/2039 ] Nov 1 21:26:35 scott-ASUS-M2N68-AM-PLUS rsyslogd-2007: action 'action 10' suspended, next retry is Tue Nov 1 21:27:05 2016 [v8.16.0 try http://www.rsyslog.com/e/2007 ] Nov 1 21:26:35 scott-ASUS-M2N68-AM-PLUS kernel: [0.00] Linux version 4.8.0-26-generic (buildd@lgw01-58) (gcc version 6.2.0 20161005 (Ubuntu 6.2.0-5ubuntu12) ) #28-Ubuntu SMP Tue Oct 18 14:39:52 UTC 2016 (Ubuntu 4.8.0-26.28-generic 4.8.0) Nov 1 21:26:35 scott-ASUS-M2N68-AM-PLUS kernel: [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic root=UUID=5a40c58b-cb06-4221-8625-ef04379be2be ro quiet splash vt.handoff=7 Nov 1 21:26:35 scott-ASUS-M2N68-AM-PLUS kernel: [0.00] KERNEL supported cpus: Nov 1 21:26:35 scott-ASUS-M2N68-AM-PLUS kernel: [0.00] Intel GenuineIntel Nov 1 21:26:35 scott-ASUS-M2N68-AM-PLUS kernel: [0.00] AMD AuthenticAMD Nov 1 21:26:35 scott-ASUS-M2N68-AM-PLUS kernel: [0.00] Centaur CentaurHauls Nov 1 21:26:35 scott-ASUS-M2N68-AM-PLUS kernel: [0.00] x86/fpu: Legacy x87 FPU detected. Nov 1 21:26:35 scott-ASUS-M2N68-AM-PLUS kernel: [0.00] x86/fpu: Using 'eager' FPU context switches. Nov 1 21:26:35 scott-ASUS-M2N68-AM-PLUS kernel: [0.00] e820: BIOS-p
[Ubuntu-x-swat] [Bug 1636582] [NEW] nvidia-304 - module doesn't install to (or load from) kernal)
Public bug reported: I have used nvidia-304 successfully with Lubuntu up through 16.04. (With nouveau, at some time or other, the screen "crashes" and I have to hard- shutdown) This time, with 16.10, I first noticed only 3 screen resolutions possible - max being 1024x768. Further research showed: Monitor Settings: "The following monitor is detected... Default Monitor" scott@scott-ASUS-M2N68-AM-PLUS:~$ sudo lshw -c video [sudo] password for scott: *-display UNCLAIMED description: VGA compatible controller product: C61 [GeForce 7025 / nForce 630a] vendor: NVIDIA Corporation physical id: d bus info: pci@:00:0d.0 version: a2 width: 64 bits clock: 66MHz capabilities: pm msi vga_controller bus_master cap_list configuration: latency=0 resources: memory:de00-deff memory:c000-cfff memory:dd00-ddff memory:c-d scott@scott-ASUS-M2N68-AM-PLUS:~$ xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 640 x 480, current 1024 x 768, maximum 1024 x 768 default connected 1024x768+0+0 0mm x 0mm 1024x768 61.00* 800x600 61.00 640x480 60.00 The install from Synaptic had appeared to go just fine: Gtk-WARNING **: Theme directory imported-Humanity/192 of theme Lubuntu has no size field Selecting previously unselected package nvidia-304. (Reading database ... 171834 files and directories currently installed.) Preparing to unpack .../0-nvidia-304_304.132-0ubuntu1_amd64.deb ... Unpacking nvidia-304 (304.132-0ubuntu1) ... Selecting previously unselected package nvidia-current. Preparing to unpack .../1-nvidia-current_304.132-0ubuntu1_amd64.deb ... Unpacking nvidia-current (304.132-0ubuntu1) ... Processing triggers for libc-bin (2.24-3ubuntu1) ... Processing triggers for man-db (2.7.5-1) ... Setting up nvidia-304 (304.132-0ubuntu1) ... update-alternatives: using /usr/lib/nvidia-304/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-304/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/share/nvidia-304/glamor.conf to provide /usr/share/X11/xorg.conf.d/glamoregl.conf (glamor_conf) in auto mode update-initramfs: deferring update (trigger activated) INFO:Enable nvidia-304 DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here Loading new nvidia-304-304.132 DKMS files... Building only for 4.8.0-26-generic Building for architecture x86_64 Building initial module for 4.8.0-26-generic Done. nvidia_304: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/4.8.0-26-generic/updates/dkms/ depmod... DKMS: install completed. Setting up nvidia-current (304.132-0ubuntu1) ... Processing triggers for libc-bin (2.24-3ubuntu1) ... Processing triggers for initramfs-tools (0.125ubuntu5) ... update-initramfs: Generating /boot/initrd.img-4.8.0-26-generic However, running lsmod showed no nvidia-304 module, nor did it show one for nouveau. So it had correctly removed nouveau, but did not add nvidia-304. Un-installing nvidia-304 gets me nouveau in lsmod, it finds the VGA monitor for xrandr and Monitor Settings, lshw just shows "*-display", and I can use up to 1600x1200 - but sooner or later I have to do a hard- shutdown because of the vidio-"crash". I just tried using "Additional Drivers" to switch to nvidia-304, but with exactly the same result. Before I removed the package, I looked through the system logs, and copied out that which looked relevant. (I will attach the full file of log-excerpts that I created.) What seemed most important were: "nvidia: module verification failed: signature and/or required key missing - tainting kernel" "(EE) NVIDIA: Failed to load the NVIDIA kernel module." "(EE) Failed to load module "nvidia" (module-specific error, 0)" Can anyone say why nvidia-304 appears to install, but never makes it into the kernel, and how I can fix this situation? [Also, I know that it may not be nvidia-304's fault that it cannot be saved/loaded, that some other package for some reason could cause a perfectly-good-nvidia-304 package not to be installed/loaded in the kernal, but I don't know enough how things work to know against what other package this bug should be filed...] I'm grasping at straws here - I actually considered booting from my 16.04 Lubuntu install to try and grab its nvidia-304 package, but since I have for the first time installed 16.10 as a 64-bit OS, I don't suppose the 32-bit pkg. I could come up with would be compatible with it... s
