[SOLVED] nvidia proprietary drivers

[calvert]

ok, i've had mageia a day and i've broke it

i like my compiz, it amuses me and my daughter - but my system is saying that compiz is not supported,
yet i have full compiz on my mandriva, even pclos and fedora,

i have an nvidia 7100 gs vid card

i had a fiddle around and found i was using the nouveau module, so updated my packages to see if the proprietary nvidia one would show up, it didn't
so i downloaded the latest driver from nvidia and tried to install, disabled x but the nouveau driver refused to play,

i then changed my tactics - after seeing a post about just re-enabling the nouveau driver and mageia informing the user about the proprietary driver being available for download,
i changed the driver to vesa, rebooted and re-enabled nouveau - sure enough i was informed about the new driver and ok'd the download, (using drakx11 through a terminal)

now x will not start, it throws an error about 'nokmsboot' being disabled and leaves me on a sort of 'verbose' screen,

i have to ctrl, alt + F1 and drakx11 to change back to nouveau, reboot and everything is back to normal (ie, working desktop but no compiz)

anyone help ?? or should i just do a clean install ?

thanks in advance

[calvert]

for info, i did a clean install and the issue is just the same,

[doktor5000]

Please show the output of

Code: Select all

grep -i driver /var/log/Xorg.0.log

and

Code: Select all

rpm -qa | grep nvidia

In general you should refrain from directly installing nvidia drivers via the installer from the nvidia page.
Normally you just need to enable nonfree repositories via software sources management in Mageia Control center
and then start drakx11, select your nvidia card, say yes to the question for the proprietary driver, let it install itself and then reboot.

[calvert]

hi, i did do that with the clean install - i still get the 'your system does not support 3d effects' through mcc,
also the effects do not work in 'system settings effects' via system settings,
if i check the enable box my system goes to black screen and throws an error, then auto reverts to normal desktop

if i enable the nvidia driver via drakx11 and reboot i get the 'nokmsboot' error,
checked in menu.lst and the option is there

i have tainted release and tainted updates enabled, fully up to date (if that makes any difference)

outputs as requested

Code: Select all

[dave@localhost ~]$ grep -i driver /var/log/Xorg.0.log
[    16.263]    X.Org Video Driver: 10.0
[    16.263]    X.Org XInput driver : 12.2
[    16.271] (II) Loading /usr/lib/xorg/modules/drivers/v4l_drv.so
[    16.271]    ABI class: X.Org Video Driver, version 10.0
[    16.302] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
[    16.323]    Module class: X.Org Video Driver
[    16.323]    ABI class: X.Org Video Driver, version 10.0
[    16.323] (II) v4l driver for Video4Linux
[    16.323] (II) NOUVEAU driver
[    16.323] (II) NOUVEAU driver for NVIDIA chipset families :
[    16.327] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
[    16.677] (**) NOUVEAU(0):  Driver mode "1280x1024": 157.5 MHz (scaled from 0.0 MHz), 91.1 kHz, 85.0 Hz
[    16.677] (**) NOUVEAU(0):  Driver mode "1920x1440": 234.0 MHz (scaled from 0.0 MHz), 90.0 kHz, 60.0 Hz
[    16.677] (**) NOUVEAU(0):  Driver mode "1856x1392": 218.2 MHz (scaled from 0.0 MHz), 86.3 kHz, 60.0 Hz
[    16.677] (**) NOUVEAU(0):  Driver mode "1792x1344": 204.8 MHz (scaled from 0.0 MHz), 83.6 kHz, 60.0 Hz
[    16.677] (**) NOUVEAU(0):  Driver mode "1600x1200": 202.5 MHz (scaled from 0.0 MHz), 93.8 kHz, 75.0 Hz
[    16.677] (**) NOUVEAU(0):  Driver mode "1280x1024": 135.0 MHz (scaled from 0.0 MHz), 80.0 kHz, 75.0 Hz
[    16.677] (**) NOUVEAU(0):  Driver mode "1280x960": 148.5 MHz (scaled from 0.0 MHz), 85.9 kHz, 85.0 Hz
[    16.677] (**) NOUVEAU(0):  Driver mode "1152x864": 108.0 MHz (scaled from 0.0 MHz), 67.5 kHz, 75.0 Hz
[    16.677] (**) NOUVEAU(0):  Driver mode "1024x768": 94.5 MHz (scaled from 0.0 MHz), 68.7 kHz, 85.0 Hz
[    16.677] (**) NOUVEAU(0):  Driver mode "1024x768": 78.8 MHz (scaled from 0.0 MHz), 60.1 kHz, 75.1 Hz
[    16.677] (**) NOUVEAU(0):  Driver mode "1024x768": 75.0 MHz (scaled from 0.0 MHz), 56.5 kHz, 70.1 Hz
[    16.677] (**) NOUVEAU(0):  Driver mode "1024x768": 65.0 MHz (scaled from 0.0 MHz), 48.4 kHz, 60.0 Hz
[    16.677] (**) NOUVEAU(0):  Driver mode "1024x768": 44.9 MHz (scaled from 0.0 MHz), 35.5 kHz, 87.0 Hz (I)
[    16.677] (**) NOUVEAU(0):  Driver mode "832x624": 57.3 MHz (scaled from 0.0 MHz), 49.7 kHz, 74.6 Hz
[    16.677] (**) NOUVEAU(0):  Driver mode "800x600": 50.0 MHz (scaled from 0.0 MHz), 48.1 kHz, 72.2 Hz
[    16.677] (**) NOUVEAU(0):  Driver mode "800x600": 49.5 MHz (scaled from 0.0 MHz), 46.9 kHz, 75.0 Hz
[    16.677] (**) NOUVEAU(0):  Driver mode "800x600": 40.0 MHz (scaled from 0.0 MHz), 37.9 kHz, 60.3 Hz
[    16.678] (**) NOUVEAU(0):  Driver mode "800x600": 36.0 MHz (scaled from 0.0 MHz), 35.2 kHz, 56.2 Hz
[    16.678] (**) NOUVEAU(0):  Driver mode "640x480": 31.5 MHz (scaled from 0.0 MHz), 37.9 kHz, 72.8 Hz
[    16.678] (**) NOUVEAU(0):  Driver mode "640x480": 31.5 MHz (scaled from 0.0 MHz), 37.5 kHz, 75.0 Hz
[    16.678] (**) NOUVEAU(0):  Driver mode "640x480": 30.2 MHz (scaled from 0.0 MHz), 35.0 kHz, 66.7 Hz
[    16.678] (**) NOUVEAU(0):  Driver mode "640x480": 25.2 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz
[    16.678] (**) NOUVEAU(0):  Driver mode "720x400": 35.5 MHz (scaled from 0.0 MHz), 39.4 kHz, 87.8 Hz
[    16.678] (**) NOUVEAU(0):  Driver mode "720x400": 28.3 MHz (scaled from 0.0 MHz), 31.5 kHz, 70.1 Hz
[    16.687]    ABI class: X.Org Video Driver, version 10.0
[    16.693] (II) NOUVEAU(0): [DRI2]   DRI driver: nouveau
[    16.696] (II) EXA(0): Driver allocated offscreen pixmaps
[    16.696] (II) EXA(0): Driver registered support for the following operations:
[    17.008]    Module class: X.Org XInput Driver
[    17.008]    ABI class: X.Org XInput driver, version 12.2
[    17.008] (II) Using input driver 'evdev' for 'Power Button'
[    17.054] (II) Using input driver 'evdev' for 'Power Button'
[    17.091] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[    17.096] (II) Using input driver 'evdev' for 'ImPS/2 Generic Wheel Mouse'
[    17.102] (II) No input driver/identifier specified (ignoring)
[    17.995] (II) Using input driver 'evdev' for 'UVC Camera (046d:08ce)'
[dave@localhost ~]$


Code: Select all

[dave@localhost ~]$ rpm -qa | grep nvidia
x11-driver-video-nvidia-current-275.09.07-0.1.mga1.nonfree
nvidia-current-doc-html-275.09.07-0.1.mga1.nonfree
dkms-nvidia-current-275.09.07-0.1.mga1.nonfree
[dave@localhost ~]$


[doktor5000]

if i enable the nvidia driver via drakx11 and reboot i get the 'nokmsboot' error,
checked in menu.lst and the option is there

What is the exact message?
And what happens if you remove this option for the next boot? Can be done via
F3 in grub bootscreen, selecting "Default" and removing "nokmsboot" and pressing enter.

[calvert]

i tried editing menu.lst to remove the option on both kernels, but a reboot later and the options were back,

i edited menu.lst from mandriva

i don't think i can F3 at grub as i've added mageia to my mandriva grub, they are on separate hdd's,
but i'll give it a go, something new to try and break

[calvert]

ok, changed to the nvidia driver via drakx11, rebooted and presented with this error.

The display driver currently configured requires you to use the 'nokmsboot' boot option to prevent the kms driver of the kernel from being loaded in the boot process. Starting of the X server may now fail as that option was not specified

using Ctrl, Alt + F1 allows me to login as user or root,
using startx tells me there are no screens and fails on either account,

Ctrl, Alt + Delete to reboot

i have left it as it is and booted into mandriva, just in case you need me to do anything while its in that state

[doktor5000]

Well, that option should be there by default. Please show your /boot/grub/menu.lst

[calvert]

mageia menu.lst

Code: Select all

timeout 10
color black/cyan yellow/cyan
gfxmenu (hd0,0)/boot/gfxmenu
default 0

title linux
kernel (hd0,0)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=cf115603-cd54-4ec6-b822-8bd6f053c5d8 nokmsboot resume=UUID=3425bfa1-9091-4089-a666-09e3df213403 splash=silent vga=788
initrd (hd0,0)/boot/initrd.img

title linux-nonfb
kernel (hd0,0)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=cf115603-cd54-4ec6-b822-8bd6f053c5d8 nokmsboot resume=UUID=3425bfa1-9091-4089-a666-09e3df213403
initrd (hd0,0)/boot/initrd.img

title failsafe
kernel (hd0,0)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=cf115603-cd54-4ec6-b822-8bd6f053c5d8 failsafe
initrd (hd0,0)/boot/initrd.img

title 2.6.38.7-desktop586-1.mga
kernel (hd0,0)/boot/vmlinuz-2.6.38.7-desktop586-1.mga BOOT_IMAGE=2.6.38.7-desktop586-1.mga root=UUID=cf115603-cd54-4ec6-b822-8bd6f053c5d8 nokmsboot resume=UUID=3425bfa1-9091-4089-a666-09e3df213403 splash=silent vga=788
initrd (hd0,0)/boot/initrd-2.6.38.7-desktop586-1.mga.img

title 2.6.38.8-desktop586-8.mga
kernel (hd0,0)/boot/vmlinuz-2.6.38.8-desktop586-8.mga BOOT_IMAGE=2.6.38.8-desktop586-8.mga root=UUID=cf115603-cd54-4ec6-b822-8bd6f053c5d8 nokmsboot resume=UUID=3425bfa1-9091-4089-a666-09e3df213403 splash=silent vga=788
initrd (hd0,0)/boot/initrd-2.6.38.8-desktop586-8.mga.img

mandriva menu.lst

Code: Select all

timeout 5
color black/cyan yellow/cyan
gfxmenu (hd0,4)/boot/gfxmenu
default 2

title linux-nonfb
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=abb73474-2e06-4eb2-8512-ac4dd62f95a1 resume=UUID=fd1a4647-e75f-49b6-9dec-716187076e9d
initrd (hd0,4)/boot/initrd.img

title failsafe
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=abb73474-2e06-4eb2-8512-ac4dd62f95a1 failsafe
initrd (hd0,4)/boot/initrd.img

title linux
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=abb73474-2e06-4eb2-8512-ac4dd62f95a1 resume=UUID=fd1a4647-e75f-49b6-9dec-716187076e9d splash=silent vga=788
initrd (hd0,4)/boot/initrd.img

title pclinuxos
kernel (hd1,0)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=612f6baa-2daa-47b5-8849-1fa6d27367dc  quiet nokmsboot vmalloc=256M acpi=on resume=UUID=2a44f2ce-43c9-4727-89c6-165821423df2 splash=silent vga=788
initrd (hd1,0)/boot/initrd.img

title Mageia
kernel (hd1,0)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=cf115603-cd54-4ec6-b822-8bd6f053c5d8  resume=UUID=3425bfa1-9091-4089-a666-09e3df213403 splash=silent vga=788
initrd (hd1,0)/boot/initrd.img


title Windoze
rootnoverify (hd1,2)
map (hd0) (hd1)
map (hd1) (hd0)
makeactive
chainloader +1

wrapped in code for ease, the windows and pclinux hdd is not currently connected

[calvert]

ok, i have found the problem,

as i was booting via mandriva's grub and not mageia's grub then it boots direct,

i manually added the entry to mandriva's grub, but missed out one word - nokmsboot

i realised this by reading through this thread again and checking the 2 menu.lst's,
it doesn't matter how i edit mageia's, its not used - its mandriva's thats used

i have changed this

Code: Select all

title Mageia
kernel (hd1,0)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=cf115603-cd54-4ec6-b822-8bd6f053c5d8  resume=UUID=3425bfa1-9091-4089-a666-09e3df213403 splash=silent vga=788
initrd (hd1,0)/boot/initrd.img

to this

Code: Select all

title Mageia
kernel (hd1,0)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=cf115603-cd54-4ec6-b822-8bd6f053c5d8  nokmsboot resume=UUID=3425bfa1-9091-4089-a666-09e3df213403 splash=silent vga=788
initrd (hd1,0)/boot/initrd.img

booted into mageia and all is ok, no errors and full compiz

my thanks to doktor5000 (you can kick me later ) for his time and wish you all a happy new year

topic is solved

[doktor5000]

You're still doing it wrong, you should add a chainloader entry to Mandriva's grub instead of a direct entry for a Mageia kernel.
Supposed already you were doing something like that, because in a default install you wouldn't have that problem.

In the end the mandriva grub menu.lst should look like this for the Mageia part:

Code: Select all

title Mageia
root (hd1,0)
chainloader (hd1,0)+1

[calvert]

just out of interest, is there a reason why i should chainload ?

i've always done it the way i do it

ah, is the kernel upgrade the only reason ?

[doktor5000]

Well, if sometime Mageia boot options will change, you will never know, because you still use your hardcoded entry to boot Mageia,
like with the nokmsboot problem which you've just encountered. Also there are no advantages when you do it your way, IMHO.

[calvert]

ok, i understand,

i've installed mageia looking for an upgrade to mandriva, i'm currently using mdv2010.0 and i prefer to use something i am familiar with certain commands with (mandriva, pclos, mageia),

the latest mandriva is not to my liking, or pclos - so mageia is being tested on my machine,

the best of the 3 (imo) will become number one - or i may just stick with mdv2010.0

i have to be comfortable with my machine, its used as a media server as well - and i'm a bit piccy,

thanks again for your help and time

[wobo]

As for Mandriva 2010.0 you should be aware of the fact that this version is not officially supported anymore (no security updates).
At least I'd upgrade to Mandriva 2010.2 (which will still be supported for a couple of months).
From there you can upgrade to Mageia 1 (if you want) or you keep exploring Mageia 1 in it's own installation.

As for the chainloader approach: it's the most userfriendly and maintenance-friendly way to manage several installations on one machine.

[calvert]

hi,
yes i am aware of the lifecycle of mandriva and i also understand the security and support concerns,