Installed gnome from DVD 32 on an athlon64, nvidia340 card and ivtv. On the first boot it fails and falls back to nouveau giving the reason as "The proprietary kernel driver was not found for X.org driver 'nvidia' ". I'll attach some logs Reproducible: Steps to Reproduce:
Priority: Normal => release_blockerCC: (none) => ennael1, tmb
Created attachment 5882 [details] journal.txt
Created attachment 5883 [details] dmesg.txt
Created attachment 5884 [details] report.bug.xz
# lsmod | grep -e nv -e nou nouveau 1230529 3 mxm_wmi 12893 1 nouveau wmi 18689 2 mxm_wmi,nouveau video 19594 1 nouveau ttm 80946 1 nouveau drm_kms_helper 100414 1 nouveau drm 270591 6 ttm,drm_kms_helper,nouveau i2c_algo_bit 13190 2 ivtv,nouveau button 13654 1 nouveau sata_nv 23016 3 # rpm -qa *nvidia* nvidia340-kernel-3.19.0-desktop-1.mga5-340.76-4.mga5.nonfree x11-driver-video-nvidia340-340.76-1.mga5.nonfree nvidia340-doc-html-340.76-1.mga5.nonfree dkms-nvidia340-340.76-1.mga5.nonfree nvidia340-kernel-desktop-latest-340.76-4.mga5.nonfree # rpm -qa *kernel* nvidia340-kernel-3.19.0-desktop-1.mga5-340.76-4.mga5.nonfree kernel-desktop-latest-3.19.0-1.mga5 kernel-firmware-nonfree-20150204-1.mga5.nonfree kernel-userspace-headers-3.19.0-1.mga5 nvidia340-kernel-desktop-latest-340.76-4.mga5.nonfree kernel-firmware-20150204-1.mga5 kernel-desktop-devel-latest-3.19.0-1.mga5 kernel-desktop-3.19.0-1.mga5-1-1.mga5 kernel-desktop-devel-3.19.0-1.mga5-1-1.mga5
Created attachment 5885 [details] journalctl -e _COMM=X > journal-xorg.txt Gnome doesn't create Xorg.0.log so pulling it from the journal.
(Not to self: -e shows last 1000 lines from the end so not necessary here)
what does "modinfo nvidia" or "modinfo nvidia340" say ?
I was just about to format, is there any other info needed before I do? # modinfo nvidia modinfo: ERROR: Module nvidia not found. # modinfo nvidia340 filename: /lib/modules/3.19.0-desktop-1.mga5/dkms-binary/drivers/char/drm/nvidia340.ko.xz alias: char-major-195-* version: 340.76 supported: external license: NVIDIA alias: pci:v000010DEd00000E00sv*sd*bc04sc80i00* alias: pci:v000010DEd00000AA3sv*sd*bc0Bsc40i00* alias: pci:v000010DEd*sv*sd*bc03sc02i00* alias: pci:v000010DEd*sv*sd*bc03sc00i00* depends: drm vermagic: 3.19.0-desktop-1.mga5 SMP mod_unload modversions 686 parm: NVreg_Mobile:int parm: NVreg_ResmanDebugLevel:int parm: NVreg_RmLogonRC:int parm: NVreg_ModifyDeviceFiles:int parm: NVreg_DeviceFileUID:int parm: NVreg_DeviceFileGID:int parm: NVreg_DeviceFileMode:int parm: NVreg_RemapLimit:int parm: NVreg_UpdateMemoryTypes:int parm: NVreg_InitializeSystemMemoryAllocations:int parm: NVreg_UsePageAttributeTable:int parm: NVreg_MapRegistersEarly:int parm: NVreg_RegisterForACPIEvents:int parm: NVreg_CheckPCIConfigSpace:int parm: NVreg_EnablePCIeGen3:int parm: NVreg_EnableMSI:int parm: NVreg_MemoryPoolSize:int parm: NVreg_RegistryDwords:charp parm: NVreg_RmMsg:charp parm: NVreg_AssignGpus:charp
One thing, what happends if you "modprobe nvidia340" does it even detect your hw ?
Doesn't look like it # modprobe nvidia340 modprobe: ERROR: could not insert 'nvidia340': No such device Although it was offered in the installer and installed what looked to be all the correct packages.
Hm, well nouveau might be blocking, so switch to a console and "modprobe -r nouveau" ensure it's unloaded with lsmod then: "modprobe nvidia340"
and paste lspcidrake -v for that card
Oh, and if you boot a livecd, wich driver handles your card ?
It won't allow me to modprobe -r nouveau even in single user mode, says it's in use.
Created attachment 5886 [details] lspcidrake-v.txt
Gnome livecd (round 3 Feb 9th) in live mode # lsmod | grep -e nv -e nou nvidia 9532278 39 drm 270591 3 nvidia sata_nv 23016 0
Created attachment 5887 [details] ddh_debug.log
Above was from.. <tmb> MrsB, edit /usr/sbin/display_driver_helper <MrsB> ok <tmb> uncomment "DEBUG_DISPLAY_DRIVER_HELPER=yes" and reboot <tmb> then after boot do: cat /dev/ddh_debug >/tmp/ddh_debug_log and attach that file to the bugreport
Created attachment 5888 [details] ddh_debug2.log Set to use nvidia in MCC and rebooted. It fell back to nouveau again but this time the window which informs you contained no message, it was just a blank window with an OK button. ddh_debug2.log taken after login.
@Anssi: any thoughts why it wants to switch to nouveau? have we missed to add support for nvidia340 somewhere that I'm missing? I also noticed this in the nvidia* SPECS: $ grep "define priority" nvidia*/SPECS/*.spec nvidia304/SPECS/nvidia304.spec:%define priority 9630 nvidia340/SPECS/nvidia340.spec:%define priority 9851 nvidia-current/SPECS/nvidia-current.spec:%define priority 9700 shouldn't nvidia-current rank highest, or do I remember wrong...
CC: (none) => anssi.hannula
On real hardware, M5B3, Gnome, 32-bit, Live-DVD, install from the boot menu. On the following platform: Intel Core i7-2600K Sandy Bridge 3.4GHz GIGABYTE GA-Z68X-UD3-B3 LGA 1155 MoBo GIGABYTE GV-N440D3-1GI Nvidia GeForce GT 440 (Fermi) 1GB RTL8111/8168B PCI Express 1Gbit Ethernet DRAM 16GB (4 x 4GB) Mageia 4 64-bit, Nvidia driver virtualbox-4.3.10-1.1.mga4.x86_64 virtualbox-guest-additions-4.3.10-1.1.mga4.x86_64 Install had a couple minor issues but in reference to this bug the Nvidia driver was installed, I updated the system, rebooted, and the Nvidia driver was still active after the reboot. lspci -k is the terminal command I used to determine which driver was being used.
CC: (none) => wilcal.int
Argh, yes, service_harddrake still contains a hardcoded list (I thought we had replaced it with a regex, but seems that was just for the x.org driver). tmb, can you make the fix? :) The priority doesn't really matter since we use manual alternatives selection. Preferably the priority should be lower than mesa even, to keep mesa selected if auto mode is on.
(In reply to Anssi Hannula from comment #22) > Argh, yes, service_harddrake still contains a hardcoded list (I thought we > had replaced it with a regex, but seems that was just for the x.org driver). > tmb, can you make the fix? :) > Ah, indeed. How did I miss that one :/ I will fix (and drop some of the older nonexistant ones) thanks for pointing it out. > The priority doesn't really matter since we use manual alternatives > selection. Preferably the priority should be lower than mesa even, to keep > mesa selected if auto mode is on. Hm, that could be done yes, but I think that can wait for mga6 too
commit acf15d5f735f5a68412f55c9ec0c5ff1afcf9a5e Author: Thomas Backlund <tmb@...> Date: Tue Feb 10 21:01:03 2015 +0159 - service_harddrake: * add support for the new nvidia340 driver (mga#15255) * drop references to old unsupported nVidia drivers --- Commit Link: http://gitweb.mageia.org/software/drakx/commit/?id=acf15d5f735f5a68412f55c9ec0c5ff1afcf9a5e
Well done :)
Closing then
Status: NEW => RESOLVEDCC: (none) => thierry.vignaudResolution: (none) => FIXED
Confirmed fixed with last isos