Nvidia-current v. 310.19

[Harry33]

There is a new nvidia-current beta version available from xorg-edgers PPA (RR branch).
The version is 310.19.

Working fine here.

[dino99]

hm, still get the same known error:

update-initramfs: Generating /boot/initrd.img-3.7.0-030700rc5-generic
modprobe: ../tools/modprobe.c:550: print_action: Assertion `kmod_module_get_initstate(m) == KMOD_MODULE_BUILTIN' failed.
Aborted (core dumped)
WARNING: could not open /tmp/mkinitramfs_iuhZhv/lib/modules/3.7.0-030700rc5-generic/modules.builtin: No such file or directory

[zika]

hm, still get the same known error:

update-initramfs: Generating /boot/initrd.img-3.7.0-030700rc5-generic
modprobe: ../tools/modprobe.c:550: print_action: Assertion `kmod_module_get_initstate(m) == KMOD_MODULE_BUILTIN' failed.
Aborted (core dumped)
WARNING: could not open /tmp/mkinitramfs_iuhZhv/lib/modules/3.7.0-030700rc5-generic/modules.builtin: No such file or directory

It's just warning... No harm produced as far as I can tell...
Lot of bugs are filed against this and elsewhere...
http://bit.ly/TGOiWG

[dino99]

It's just warning... No harm produced as far as I can tell...
Lot of bugs are filed against this and elsewhere...
http://bit.ly/TGOiWG

I can run it but only on low graphic mode (800x600), so i switch back to nouveau again

[NikTh]

An observation here , that might help others.

I downloaded (2 days ago) 310.14 beta driver from Nvidia's site
http://www.nvidia.com/object/linux-d...14-driver.html

To test it with my Nvidia GT430. What I observed is when I installed the .run file , during installation asked me to blacklist nouveau. Installation failed due to nouveau loaded module.
I blacklisted nouveau and booted with vesa (low graphics) and then installation completed successfully and the driver working good since then.
Until this time I thought the only requirement was to stop the X , but seems a new requirement now is to have nouveau module unloaded.
So , try to install with nouveau blacklisted. (manual by you).

Thanks

[zika]

I can run it but only on low graphic mode (800x600), so i switch back to nouveau again

Then I stand corrected. My (ATI/Asus) machine does not produce any harm due to this warning...

[Harry33]

Well if one just upgrades from the previous nvidia-current version, then nouveau driver is blacklisted.
That is, installing nvidia-current will automatically blacklist nouveau driver.

[dino99]

i cant beleive what have happened:
- due to previous comment, i've purged the "nouveau" driver (installed: vesa, fbdev, modesetting)
- then did a cold reboot
- was expecting a low graphic, but got a normal definition
- then i've checked the active video driver : "nouveau"
its really purged, but still active after a reboot

- well going ahead: activate edgers ppa and install nvidia 310.19
- got the kmod error
- then i've rebooted: surprisingly i got alot of art-deco before getting lightdm
- and everything seems ok: jockey show me nvidia activated that time

[toobuntu]

Is your /tmp mounted noexec? If so, the update-initramfs issue might be related to Debian Bug #576678; at least it seems familiar.

/tmp: [exec] needs to be mounted exec at package configuration time, or there could be problems with the maintainer scripts, e.g. see Bug#576678: initramfs-tools: breaks but continues if /tmp is mounted with noexec option (fixed on 08-Jun-2010 in v0.96.1).

Does

grep \ /tmp /etc/mtab

show noexec as a mount option? If so, try remounting exec before running update-initramfs (or apt-get, which will call it when appropriate). You can do that with:

sudo mount /tmp -o remount,exec

[dino99]

hm, get no output, and /tmp is not mounted at all

oem@oem-desktop:~$ grep \ /tmp /etc/mtab
oem@oem-desktop:~$ sudo grep \ /tmp /etc/mtab
[sudo] password for oem:
oem@oem-desktop:~$ sudo mount /tmp -o remount,exec
mount: /tmp not mounted or bad option