nvidia-304 - module doesn't install to (or load from) kernal)

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@0000:00:0d.0
       version: a2
       width: 64 bits
       clock: 66MHz
       capabilities: pm msi vga_controller bus_master cap_list
       configuration: latency=0
       resources: memory:de000000-deffffff memory:c0000000-cfffffff memory:dd000000-ddffffff memory:c0000-dffff

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...

----------------------------------------------------
scott@scott-ASUS-M2N68-AM-PLUS:~$ uname -a
Linux scott-ASUS-M2N68-AM-PLUS 4.8.0-26-generic #28-Ubuntu SMP Tue Oct 18 14:39:52 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-304 version:
 nvidia-current_304.132-0ubuntu1_amd64.deb
 nvidia-304_304.132-0ubuntu1_amd64.deb

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: nvidia-304 (not installed)
ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
Uname: Linux 4.8.0-26-generic x86_64
ApportVersion: 2.20.3-0ubuntu8
Architecture: amd64
CurrentDesktop: LXDE
Date: Tue Oct 25 13:07:39 2016
InstallationDate: Installed on 2016-10-20 (5 days ago)
InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
SourcePackage: nvidia-graphics-drivers-304
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.modprobe.d.nvidia-304_hybrid.conf: [deleted]