Description of problem:Mageia-prime no works Version-Release number of selected component (if applicable): Mageia 7 How reproducible: Install Mageia-Prime Steps to Reproduce: 1. Install Mageia-Prime 2. Appears errors during the instalation 3. The instalation no terminate correctly.
This is the log of konsole instalation of Mageia-Prime: [root@localhost ~]# urpmi mageia-prime $MIRRORLIST: media/nonfree/release/mageia-prime-0.4-4.mga7.nonfree.x86_64.rpm instalando mageia-prime-0.4-4.mga7.nonfree.x86_64.rpm desde /var/cache/urpmi/rpms Preparando... ##################################################### 1/1: mageia-prime ##################################################### [root@localhost ~]# usr/sbin/mageia-prime-install -z -bash: usr/sbin/mageia-prime-install: No existe el fichero o el directorio [root@localhost ~]# /usr/sbin/mageia-prime-install -z Found Intel card: 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b) Found Nvidia card: 04:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] (rev a1) Blacklisting nouveau kernel module in /etc/modprobe.d/00_mageia-prime.conf (shouldn't be enough, try toadd 'nouveau.modeset=0', e.g. with option -g here, to your booting command line) Regenerating kernel initrd images...done. Checking package dkms-nvidia-current...installing...Para satisfacer las dependencias, se instalarán los paquetes siguientes: Paquete Versión Revisión Arq. (soporte «Core Release») binutils 2.32 9.mga7 x86_64 dkms 2.0.19 40.mga7 noarch gcc 8.3.1 0.20190524.1> x86_64 gcc-cpp 8.3.1 0.20190524.1> x86_64 glibc-devel 2.29 13.mga7 x86_64 isl 0.18 1.mga7 x86_64 kernel-desktop-devel-5.1.9-1.> 1 1.mga7 x86_64 kernel-desktop-devel-latest 5.1.9 1.mga7 x86_64 (Recomendado) kernel-userspace-headers 5.1.9 1.mga7 x86_64 lib64bz2-devel 1.0.6 13.mga7 x86_64 lib64elfutils-devel 0.176 1.mga7 x86_64 lib64isl15 0.18 1.mga7 x86_64 lib64lzma-devel 5.2.4 2.mga7 x86_64 lib64mpc3 1.1.0 3.mga7 x86_64 lib64ncurses-devel 6.1 20181117.3.m> x86_64 lib64xcrypt-devel 4.4.6 1.mga7 x86_64 lib64zlib-devel 1.2.11 7.mga7 x86_64 libstdc++-devel 8.3.1 0.20190524.1> x86_64 multiarch-utils 1.0.14 2.mga7 noarch (soporte «Nonfree Release») dkms-nvidia-current 430.26 1.mga7.nonfr> x86_64 se utilizarán 218MB de espacio de disco adicional. se descargarán 57MB de paquetes. ¿Efectuar la instalación de los 20 paquetes? (S/n) s $MIRRORLIST: media/core/release/gcc-cpp-8.3.1-0.20190524.1.mga7.x86_64.rpm $MIRRORLIST: media/core/release/glibc-devel-2.29-13.mga7.x86_64.rpm $MIRRORLIST: media/core/release/kernel-desktop-devel-5.1.9-1.mga7-1-1.mga7.x86_64.rpm $MIRRORLIST: media/core/release/lib64isl15-0.18-1.mga7.x86_64.rpm $MIRRORLIST: media/core/release/lib64zlib-devel-1.2.11-7.mga7.x86_64.rpm $MIRRORLIST: media/core/release/libstdc++-devel-8.3.1-0.20190524.1.mga7.x86_64.rpm $MIRRORLIST: media/core/release/multiarch-utils-1.0.14-2.mga7.noarch.rpm $MIRRORLIST: media/core/release/lib64elfutils-devel-0.176-1.mga7.x86_64.rpm $MIRRORLIST: media/core/release/dkms-2.0.19-40.mga7.noarch.rpm $MIRRORLIST: media/core/release/lib64mpc3-1.1.0-3.mga7.x86_64.rpm $MIRRORLIST: media/core/release/lib64bz2-devel-1.0.6-13.mga7.x86_64.rpm $MIRRORLIST: media/core/release/binutils-2.32-9.mga7.x86_64.rpm $MIRRORLIST: media/core/release/lib64lzma-devel-5.2.4-2.mga7.x86_64.rpm $MIRRORLIST: media/core/release/kernel-userspace-headers-5.1.9-1.mga7.x86_64.rpm $MIRRORLIST: media/core/release/lib64ncurses-devel-6.1-20181117.3.mga7.x86_64.rpm $MIRRORLIST: media/core/release/gcc-8.3.1-0.20190524.1.mga7.x86_64.rpm $MIRRORLIST: media/core/release/isl-0.18-1.mga7.x86_64.rpm $MIRRORLIST: media/core/release/lib64xcrypt-devel-4.4.6-1.mga7.x86_64.rpm $MIRRORLIST: media/core/release/kernel-desktop-devel-latest-5.1.9-1.mga7.x86_64.rpm $MIRRORLIST: media/nonfree/release/dkms-nvidia-current-430.26-1.mga7.nonfree.x86_64.rpm instalando lib64mpc3-1.1.0-3.mga7.x86_64.rpm lib64bz2-devel-1.0.6-13.mga7.x86_64.rpm kernel-userspace-headers-5.1.9-1.mga7.x86_64.rpm binutils-2.32-9.mga7.x86_64.rpm lib64lzma-devel-5.2.4-2.mga7.x86_64.rpm lib64ncurses-devel-6.1-20181117.3.mga7.x86_64.rpm isl-0.18-1.mga7.x86_64.rpm lib64xcrypt-devel-4.4.6-1.mga7.x86_64.rpm gcc-8.3.1-0.20190524.1.mga7.x86_64.rpm kernel-desktop-devel-latest-5.1.9-1.mga7.x86_64.rpm gcc-cpp-8.3.1-0.20190524.1.mga7.x86_64.rpm kernel-desktop-devel-5.1.9-1.mga7-1-1.mga7.x86_64.rpm glibc-devel-2.29-13.mga7.x86_64.rpm libstdc++-devel-8.3.1-0.20190524.1.mga7.x86_64.rpm lib64zlib-devel-1.2.11-7.mga7.x86_64.rpm lib64isl15-0.18-1.mga7.x86_64.rpm dkms-nvidia-current-430.26-1.mga7.nonfree.x86_64.rpm lib64elfutils-devel-0.176-1.mga7.x86_64.rpm multiarch-utils-1.0.14-2.mga7.noarch.rpm dkms-2.0.19-40.mga7.noarch.rpm desde /var/cache/urpmi/rpms Preparando... ##################################################### 1/20: libstdc++-devel ##################################################### 2/20: lib64mpc3 ##################################################### 3/20: multiarch-utils ##################################################### 4/20: lib64zlib-devel ##################################################### 5/20: lib64xcrypt-devel ##################################################### 6/20: isl ##################################################### 7/20: lib64isl15 ##################################################### 8/20: gcc-cpp ##################################################### 9/20: lib64lzma-devel ##################################################### 10/20: binutils ##################################################### 11/20: kernel-userspace-headers ##################################################### 12/20: glibc-devel ##################################################### 13/20: gcc ##################################################### 14/20: lib64ncurses-devel ##################################################### 15/20: lib64bz2-devel ##################################################### 16/20: lib64elfutils-devel ##################################################### 17/20: kernel-desktop-devel-latest ##################################################### 18/20: kernel-desktop-devel-5.1.9-1.mga7 ##################################################### 19/20: dkms ##################################################### 20/20: dkms-nvidia-current ##################################################### Creating symlink /var/lib/dkms/nvidia-current/430.26-1.mga7.nonfree/source -> /usr/src/nvidia-current-430.26-1.mga7.nonfree DKMS: add Completed. Preparing kernel 5.1.9-desktop-1.mga7 for module build: (This is not compiling a kernel, just preparing kernel symbols) Storing current .config to be restored when complete Running Generic preparation routine make mrproper....(bad exit status: 2) using /proc/config.gz make oldconfig....(bad exit status: 2) make prepare....(bad exit status: 2) Building module: cleaning build area.... 'make' -j4 SYSSRC=/lib/modules/5.1.9-desktop-1.mga7/build modules................... cleaning build area.... cleaning kernel tree (make mrproper)....(bad exit status: 2) DKMS: build Completed. nvidia-current.ko.xz: - Installation - Installing to /lib/modules/5.1.9-desktop-1.mga7/dkms/drivers/char/drm/ nvidia-modeset.ko.xz: - Installation - Installing to /lib/modules/5.1.9-desktop-1.mga7/dkms/drivers/char/drm/ nvidia-drm.ko.xz: - Installation - Installing to /lib/modules/5.1.9-desktop-1.mga7/dkms/drivers/char/drm/ nvidia-uvm.ko.xz: - Installation - Installing to /lib/modules/5.1.9-desktop-1.mga7/dkms/drivers/char/drm/ depmod...... DKMS: install Completed. dracut: Executing: /usr/bin/dracut -f dracut: dracut module 'bootchart' will not be installed, because command '/sbin/bootchartd' could not be found! dracut: dracut module 'systemd' will not be installed, because it's in the list to be omitted! dracut: dracut module 'systemd-bootchart' will not be installed, because command '/usr/lib/systemd/systemd-bootchart' could not be found! dracut: systemd-initrd needs systemd in the initramfs dracut: dracut module 'caps' will not be installed, because command 'capsh' could not be found! dracut: systemd-networkd needs systemd in the initramfs dracut: dracut module 'busybox' will not be installed, because command 'busybox' could not be found! dracut: dracut module 'network' will not be installed, because it's in the list to be omitted! dracut: dracut module 'network' will not be installed, because it's in the list to be omitted! dracut: dracut module 'ifcfg' depends on 'network', which can't be installed dracut: dracut module 'lvmmerge' will not be installed, because command 'lvm' could not be found! dracut: dracut module 'lvm' will not be installed, because command 'lvm' could not be found! dracut: dracut module 'cifs' will not be installed, because command 'mount.cifs' could not be found! dracut: dracut module 'iscsi' will not be installed, because command 'iscsistart' could not be found! dracut: dracut module 'iscsi' will not be installed, because command 'iscsi-iname' could not be found! dracut: dracut module 'biosdevname' will not be installed, because command 'biosdevname' could not be found! dracut: dracut-systemd needs systemd-initrd in the initramfs dracut: dracut module 'caps' will not be installed, because command 'capsh' could not be found! dracut: dracut module 'busybox' will not be installed, because command 'busybox' could not be found! dracut: dracut module 'ifcfg' depends on 'network', which can't be installed dracut: dracut module 'lvmmerge' will not be installed, because command 'lvm' could not be found! dracut: dracut module 'lvm' will not be installed, because command 'lvm' could not be found! dracut: dracut module 'cifs' will not be installed, because command 'mount.cifs' could not be found! dracut: dracut module 'iscsi' will not be installed, because command 'iscsistart' could not be found! dracut: dracut module 'iscsi' will not be installed, because command 'iscsi-iname' could not be found! dracut: *** Including module: bash *** dracut: *** Including module: dash *** dracut: *** Including module: i18n *** dracut: *** Including module: drm *** dracut: *** Including module: plymouth *** dracut: *** Including module: kernel-modules *** dracut: *** Including module: resume *** dracut: *** Including module: rootfs-block *** dracut: *** Including module: terminfo *** dracut: *** Including module: udev-rules *** dracut: Skipping udev rule: 40-redhat.rules dracut: Skipping udev rule: 50-firmware.rules dracut: Skipping udev rule: 50-udev.rules dracut: Skipping udev rule: 91-permissions.rules dracut: Skipping udev rule: 80-drivers-modprobe.rules dracut: *** Including module: usrmount *** dracut: *** Including module: base *** dracut: *** Including module: fs-lib *** dracut: *** Including module: shutdown *** dracut: *** Including modules done *** dracut: *** Installing kernel module dependencies *** dracut: *** Installing kernel module dependencies done *** dracut: *** Resolving executable dependencies *** dracut: *** Resolving executable dependencies done*** dracut: *** Stripping files *** dracut: *** Stripping files done *** dracut: *** Generating early-microcode cpio image *** dracut: *** Constructing GenuineIntel.bin **** dracut: *** Store current command line parameters *** dracut: Stored kernel commandline: dracut: resume=UUID=b036eda9-32dc-4c7c-ba2b-dde637094751 resume=UUID=b036eda9-32dc-4c7c-ba2b-dde637094751 dracut: root=UUID=a59b5615-1f71-46bb-9165-e0d91269ef33 rootfstype=ext4 rootflags=rw,relatime dracut: *** Creating image file '/boot/initrd-5.1.9-desktop-1.mga7.img' *** dracut: *** Creating initramfs image file '/boot/initrd-5.1.9-desktop-1.mga7.img' done *** ok. Checking package nvidia-current-cuda-opencl...installing...Para satisfacer las dependencias, se instalarán los paquetes siguientes: Paquete Versión Revisión Arq. (soporte «Nonfree Release») nvidia-current-cuda-opencl 430.26 1.mga7.nonfr> x86_64 nvidia-current-utils 430.26 1.mga7.nonfr> x86_64 se utilizarán 204MB de espacio de disco adicional. se descargarán 40MB de paquetes. ¿Efectuar la instalación de los 2 paquetes? (S/n) s $MIRRORLIST: media/nonfree/release/nvidia-current-cuda-opencl-430.26-1.mga7.nonfree.x86_64.rpm $MIRRORLIST: media/nonfree/release/nvidia-current-utils-430.26-1.mga7.nonfree.x86_64.rpm instalando nvidia-current-cuda-opencl-430.26-1.mga7.nonfree.x86_64.rpm nvidia-current-utils-430.26-1.mga7.nonfree.x86_64.rpm desde /var/cache/urpmi/rpms Preparando... ##################################################### 1/2: nvidia-current-utils ##################################################### 2/2: nvidia-current-cuda-opencl ##################################################### ok. Checking package x11-driver-video-nvidia-current...installing...Para satisfacer las dependencias, se instalarán los paquetes siguientes: Paquete Versión Revisión Arq. (soporte «Nonfree Release») nvidia-current-doc-html 430.26 1.mga7.nonfr> x86_64 (Recomendado) x11-driver-video-nvidia-curre> 430.26 1.mga7.nonfr> x86_64 se utilizarán 247MB de espacio de disco adicional. se descargarán 51MB de paquetes. ¿Efectuar la instalación de los 2 paquetes? (S/n) s $MIRRORLIST: media/nonfree/release/x11-driver-video-nvidia-current-430.26-1.mga7.nonfree.x86_64.rpm $MIRRORLIST: media/nonfree/release/nvidia-current-doc-html-430.26-1.mga7.nonfree.x86_64.rpm instalando nvidia-current-doc-html-430.26-1.mga7.nonfree.x86_64.rpm x11-driver-video-nvidia-current-430.26-1.mga7.nonfree.x86_64.rpm desde /var/cache/urpmi/rpms Preparando... ##################################################### 1/2: nvidia-current-doc-html ##################################################### 2/2: x11-driver-video-nvidia-current ##################################################### ---------------------------------------------------------------------- Más información sobre el paquete x11-driver-video-nvidia-current-430.26-1.mga7.nonfree.x86_64 This driver is for GeForce 635 and later cards. Use XFdrake to configure X to use the correct NVIDIA driver. Any needed packages will be automatically installed if not already present. 1. Run XFdrake as root. 2. Go to the Graphics Card list. 3. Select your card (it is usually already autoselected). 4. Answer any questions asked and then quit. If you do not want to use XFdrake, see README.manual-setup. ---------------------------------------------------------------------- ok. Switching to NVidia GL libraries...ok. modprobe: ERROR: could not insert 'nvidia_current': No such device modprobe: ERROR: Error running install command for nvidia modprobe: ERROR: could not insert 'nvidia': Operation not permitted Warning: failed to modprobe nvidia kernel module modprobe: ERROR: could not insert 'nvidia_uvm': No such device Warning: failed to modprobe nvidia-uvm kernel module modprobe: ERROR: could not insert 'nvidia_drm': No such device Warning: failed to modprobe nvidia-drm kernel module Mageia-Prime for NVidia configured (with 3 warnings) Zapping X11. Failed to restart prefdm.service: Unit prefdm.service not found. Warning: Can't restart prefdm.service: No such file or directory (error 2)
It seems that the driver 430.26, does not support my nvidia GForce 820M card, although on the official page of Nvidia if that is indicated as compatible. https://www.nvidia.com/Download/driverResults.aspx/148435/en-us
Hi, If your nvidia GForce 820M card is based on a Fermi chipset, then it is exact that the driver 430.26 does not support your card. In that case, you need nvidia390. Best regards, Nico.
CC: (none) => nicolas.salguero
I have tried to install the 390 driver, but when I reinstall mageia-prime, it reinstalls the 430.26 driver and it generates the same errors. I run out of graphical server. Best regards,
(In reply to Nicolas Salguero from comment #3) > Hi, > > If your nvidia GForce 820M card is based on a Fermi chipset, then it is > exact that the driver 430.26 does not support your card. In that case, you > need nvidia390. > > Best regards, > > Nico. (In reply to Jose Manuel López Díaz from comment #4) > I have tried to install the 390 driver, but when I reinstall mageia-prime, > it reinstalls the 430.26 driver and it generates the same errors. I run out > of graphical server. > José, please give the output of (in a konsole or terminal): lspcidrake -v | grep Card Assigning to our mageia-prime maintainer.
Source RPM: Mageia-Prime => mageia-primeAssignee: bugsquad => ghibomgxCC: (none) => marja11Keywords: (none) => NEEDINFOSummary: Mageia-prime no works => Mageia-prime doesn't work. It pulls in the 430.26 NVidia driver, maybe the 390 is needed?
Here is: [jose@localhost ~]$ lspcidrake -v | grep Card Card:Intel 810 and later: Intel Corporation|Haswell-ULT Integrated Graphics Controller [DISPLAY_VGA] (vendor:8086 device:0a16 subv:1043 subd:228a) (rev: 0b) Card:NVIDIA GeForce 420 to GeForce 630: NVIDIA Corporation|GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] [DISPLAY_3D] (vendor:10de device:1140 subv:1043 subd:228a) (rev: a1) rtsx_pci : Realtek Semiconductor Co., Ltd.|RTL8411B PCI Express Card Reader (vendor:10ec device:5287 subv:1043 subd:202f) (rev: 01) [jose@localhost ~]$
Hi, Any new news on the subject? Is there any evolution or planing so that the 390 driver can be applied? Regards!!
Hi, I created a pull request for letting mageia-prime choose between nvidia390 and nvidia-current (based upon lspcidrake output) here: https://github.com/ghibo/mageia-prime/pull/2. I hope this will help. Best regards, Nico.
Hi, Any new news on the subject? I need to use the nvidia card for graphic design and I can't with Mageia. Regards!!
I'm on it.
Hi, Any new news on the subject? Greetings.
Hi, Any news on this? Greetings!!
CC: (none) => nicolas.robaux
CC: (none) => fri
This bug_24967 esp comment 3 is like bug 25878 in that driver nvidia 430 chosen by us does not work, and needs nvidia 390 to work. Tempted to mark them as duplicates, but not sure about the details. and in the same vein: bug 25826 see https://bugs.mageia.org/show_bug.cgi?id=25826#c1 except there nvidia 390 is chosen but it really needs nvidia 340. It seems there was a change re M7. Is there any way to wrap this lot up together?
Keywords: NEEDINFO => (none)CC: (none) => lewyssmith
I cannot say that these bugs are related. My opinion is that a problem exists in the choice of the good driver. I have also seen once that two drivers were installed together. I cannot reproduce because I have repaired without analysing. Sorry.
CC: (none) => jarillon
I think the error comes from mageia-prime not selecting the correct driver for the graphics card. In my case, the Gt820M graphics can update to the latest Nvidia driver, but only if I don't have the Fermi chipset (which is unfortunately my case). Then you can only upgrade to the 390 controller. How can you do mageia-prime to differentiate this?
(In reply to Pierre Jarillon from comment #14) (In reply to Jose Manuel López from comment #15) > I cannot say that these bugs are related. My opinion is that a problem > exists in the choice of the good driver. > I think the error comes from mageia-prime not selecting the correct driver > for the graphics card. Exactly what I think - and the same for the other bugs.
A time ago I tried a version virtualbox Kdeneon for check de driver nvidia state. In this distro, the Nvidia's private driver is in charge of making the step Mageia-prime makes in Magiea, and I wonder if it wouldn't be possible for the 390 nvidia driver and later to make the same function. In this way the system will install the correct driver and it will be in charge of making the transition for games and other more demanding graphic applications. It's a suggestion, another point of view, but I don't know if it's possible. Or maybe you should tell Mageia-Prime to leave the driver that you selected for the Nvidia graphics system. On my computer Mageia 7 installs the correct driver, but Mageia-Prime tries to update to the latest version and this causes the system not to reboot again. Greetings!!
CC: lewyssmith => (none)
Any news on this? Is there a development plan about it? Greetings
Is it possible to implement somehow the solution of https://bugs.mageia.org/show_bug.cgi?id=24967#c8 in Mageia-Prime? I will try to make modifications and test with the help of Blogdrake. See if I can report something satisfactory. Greetings
Hi, I tried to apply the solution in comment 8. I had to pack Mageia-Prime with the correction provided in Github. The resulting package: https://drive.google.com/open?id=1iniAQ53Ku5am8KZKyGjQSp8_SG3tz2hX It works for my Nvidia graphics, I have installed the correct driver according to the lspci output. However, a problem appears when applying Mageia-Prime. In Konsole I get this: [root@localhost ~]# /usr/sbin/mageia-prime-install -z Found Intel card: 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 0b) Found Nvidia card: 04:00.0 3D controller: NVIDIA Corporation GF117M [GeForce 610M/710M/810M/820M / GT 620M/625M/630M/720M] (rev a1) Blacklisting nouveau kernel module in /etc/modprobe.d/00_mageia-prime.conf (shouldn't be enough, try toadd 'nouveau.modeset=0', e.g. with option -g here, to your booting command line) Regenerating kernel initrd images...done. Driver that have to be used: nvidia390Checking package dkms-nvidia390...already installed. Checking package nvidia390-cuda-opencl...already installed. Checking package x11-driver-video-nvidia390...already installed. Found previous mageia-prime configuration. Restoring previous mageia-prime configuration Switching to NVidia GL libraries...ok. Mageia-Prime for NVidia reinstalled. Zapping X11. Failed to restart prefdm.service: Unit prefdm.service not found. Warning: Can't restart prefdm.service: No such file or directory (error 2) According to what I read on the wiki, the prefdm.service has been removed from Mageia 7 to be integrated into Systemd.This causes Mageia-Prime not to automatically restart the session. Unless I fix this, the new package works, but I have to restart the session manually. I am planning to try to package a graphical application in the near future to make the change of intel-nvidia easier in Mageia. What do you think about this advance? Greetings!!
Hi! With the help of Katnatek from Blogdrake, we have managed to package this tool with some improvements. - Now mageia-prime installs the appropriate driver thanks to Nicolas Salguero's patch in comment 8. - Now mageia-prime creates during the installation two icons to enable and disable the Nvidia card located under "Tools". - Now mageia-prime restarts the session to apply the changes, displaying a warning in English or Spanish, thanks to the insertion of systemctl restart display-manager.service (prefdm.service is no longer in Mageia 7). The new package has been uploaded to the Blogdrake repositories, where you can review the changes. You can also contact Katnatek or here at the bug to have the updated package included in the official repo. I'm leaving the bug pending to be committed.
Ever confirmed: 1 => 0Status: NEW => UNCONFIRMED
From what is written, it sounds good to me. Unfortunately i have no hw available to test it.
Hi, I installed Mageia 8 Beta 1. Also the mageia-prime 0.4.5 package of Mageia repositories. Keep up the same mistake. For my Nvidia graphics card does not select the correct driver, simply select the last available one. Is it possible for cards with 340 controller? We need to fix this error, it can be a problem for users like me who use Mageia also for games with the own driver of Nvidia. The solution provided in Blogdrake's mageia-prime review works well for Mageia 7, but not for Mageia 8. If the developer assigned to maintain this has time to review, I know my hardware with Mageia 8 is available for testing.
Ever confirmed: 0 => 1Status: UNCONFIRMED => NEWSource RPM: mageia-prime => mageia-prime mga 7 y 8 beta 1Version: 7 => Cauldron
Priority: Normal => HighSeverity: normal => critical
Target Milestone: --- => Mageia 8Whiteboard: (none) => MGA7TOOSource RPM: mageia-prime mga 7 y 8 beta 1 => mageia-prime-0.4-5.mga8.nonfree
Hello! Thanks to the new kernel update 5.8.5.2 on Mageia 8 Beta, I can now install Nvidia 390 well. But mageia-prime still doesn't work properly for my chart. In Blogdrake we have packed for Mageia 8 a new version of this tool that works well, and installs the correct driver, checking the graphics card. You can find the source package as the resulting ones updated here: https://mega.nz/folder/7kt2XKTS#HR7BOg6zDLQ_K7pXx1qWIQ Tested on Mageia 8 Beta 1 X86_64 with kernel 5.8.5.2, works well, installs the correct driver and I can activate and deactivate the dedicated card, please assign the maintainer of this package for review.
Hi, This is High priority bug for a good reason. Making Mageia even better than ever is best direction. In order to do right thing, this bug should be examined and fixed as soon as possible. Packagers, please make the status to Assigned when you are working on this. Feel free to reassign the bug if bad-triaged. Also, if bug is old, please close it. On October 1st 2020, we will drop priority to normal.
Note that updated mageia-prime has landed M8 in RC1 iso, and also in M8 online repository. mageia-prime-0.4-12.mga8.nonfree.src.rpm Can this land in M7? Hum, too late. Guiseppe? an advice on this?
Source RPM: mageia-prime-0.4-5.mga8.nonfree => mageia-prime-0.4-12.mga8.nonfree.src.rpmCC: (none) => ouaurelien
Today, I will test this packages in a computer with Optimus and Nvidia GT820M that need the 390 driver.
Hi! I tested the latest mageia-prime update on a laptop with Intel-Nvidia Optimus system and Nvidia driver required 390. Mageia-prime has been installed well, I have ejecuted /usr/sbin/mageia-prime-install, the restart have been successfully, without failures. It works well for me. Could we shut down this bug?
(In reply to Jose Manuel López from comment #29) > Hi! > > I tested the latest mageia-prime update on a laptop with Intel-Nvidia > Optimus system and Nvidia driver required 390. > > Mageia-prime has been installed well, I have ejecuted > /usr/sbin/mageia-prime-install, the restart have been successfully, without > failures. > > It works well for me. Could we shut down this bug? Yeah.
Resolution: (none) => FIXEDStatus: NEW => RESOLVED
(In reply to Aurelien Oudelet from comment #27) > Can this land in M7? Hum, too late. Why too late?
(In reply to Morgan Leijström from comment #31) > (In reply to Aurelien Oudelet from comment #27) > > Can this land in M7? Hum, too late. > > Why too late? Why not? ;) No, because I don't know if new scripts handle nvidia340, and I don't check it out. But let's Guiseppe answer it.
Status: RESOLVED => REOPENEDResolution: FIXED => (none)
Current mageia-prime 0-4-12.mga(8) doesn't handle nvidia340. Indeed I'm not even sure nvidia340 would work with prime (or let's say reverse prime). First driver I tested was 367.xx. AFAIK nvidia340 would work on cards where you might disable the internal video card from BIOS (in that case you don't need mageia-prime, as you can handle as a plain nvidia card). Indeed there is still the case of render offloading (https://download.nvidia.com/XFree86/Linux-x86_64/340.108/README/optimus.html) that could be handled by 340.xx. Anyone has a card in the set of those handled only by drivers 340.108 (i.e. not supported by 390.xx) that has Optimus?
(In reply to Giuseppe Ghibò from comment #33) > Current mageia-prime 0-4-12.mga(8) doesn't handle nvidia340. Indeed I'm not > even sure nvidia340 would work with prime (or let's say reverse prime). > First driver I tested was 367.xx. AFAIK nvidia340 would work on cards > where you might disable the internal video card from BIOS (in that case you > don't need mageia-prime, as you can handle as a plain nvidia card). Indeed > there is still the case of render offloading > (https://download.nvidia.com/XFree86/Linux-x86_64/340.108/README/optimus. > html) that could be handled by 340.xx. > > Anyone has a card in the set of those handled only by drivers 340.108 (i.e. > not supported by 390.xx) that has Optimus? Yeah, I don't know about nvidia340. What about landing mga8 mageia-prime into a mageia 7 update?
If someone prepare the required doc, I can backport to 7 and upload to 7/updates_testing.
Please do. There is this wiki page in draft state: https://wiki.mageia.org/en/Mageia-prime_for_Optimus Feel free to review it and if correct, we should release this wiki page.
Version: Cauldron => 7Source RPM: mageia-prime-0.4-12.mga8.nonfree.src.rpm => mageia-prime-0.4-4.mga7.nonfree.src.rpmTarget Milestone: Mageia 8 => ---Whiteboard: MGA7TOO => (none)
Assigned to the package maintainer. (Please set the status to 'assigned' if you are working on it)
Summary: Mageia-prime doesn't work. It pulls in the 430.26 NVidia driver, maybe the 390 is needed? => Update request for mageia-primeStatus: REOPENED => NEW
I meant the doc related to accompany the bug fixing release for mga7.
Uploaded in 7/nonfree/updates_testing.
Before installing the update ... In Mageia 7 ... # rpm -q mageia-prime mageia-prime-0.4-4.mga7.nonfree (I'd previously run mageia-prime-install with no issues) In Mageia 7 I get what appears to be a xdialog text box with the msg "Detected a loaded display driver kernel module which conflicts with the diver the X server is configured to use> Startup of the X server may now fail. Then there is an Ok button. The dialog box is shown for about 30 seconds (or until I press enter) and then X starts normally. I do not have a /etc/X11/xorg.conf file, so it should be using defaults. The display of the above dialog does not happen if I add a line with HARDDRAKE_ONBOOT=no to /etc/sysconfig/system after which mageia-prime is working with no errors. After installing mageia-prime-0.4-12.mga7.nonfree.x86_64, no change. System continues to work though harddrake on boot still must be disabled. lspcidrake -v|grep Card Card:ATI Volcanic Islands and later (amdgpu/fglrx): Advanced Micro Devices, Inc. [AMD/ATI]|Renoir [DISPLAY_VGA] (vendor:1002 device:1636 subv:1043 subd:1e21) (rev: c6) Card:NVIDIA GeForce 635 series and later: NVIDIA Corporation|TU106M [GeForce RTX 2060 Mobile] [DISPLAY_VGA] (vendor:10de device:1f15 subv:1043 subd:1e21) (rev: a1) # rpm -qa|grep nvid|sort dkms-nvidia-current-460.67-1.mga7.nonfree nvidia-current-cuda-opencl-460.67-1.mga7.nonfree nvidia-current-doc-html-460.67-1.mga7.nonfree nvidia-current-utils-460.67-1.mga7.nonfree x11-driver-video-nvidia-current-460.67-1.mga7.nonfree # grep -Ir blacklist /etc/*|grep nou /etc/modprobe.d/00_mageia-prime.conf:blacklist nouveau So mageia-prime is working with nvidia-current both before and after installing the update. This is a problem in harddrake, but that is a separate issue. I can't run m7 or m8 i586 on this uefi laptop. I just reviewed all of the above. Adding the -z option to switch between the video cards is not working, but normal usage (without -z) is working. Jose, if you use mageia-prime-install without the -z option and then reboot, is it working properly on your system?
CC: (none) => davidwhodgins
Hello! The last time I ran Mageia-Prime on Mageia 8, it worked well, as I noted in comment 29. I don't currently have a computer with Nvidia, because I've purchased a new one with AMD, both processor and graphics. If more tests are needed, I could order the old equipment to verify it, but as I said before, the last time I did the tests, it worked ok. Best regards!
Just fyi, magiea-prime isn't just for Nvidia/Intel systems. # lspcidrake -v|grep Card Card:ATI Volcanic Islands and later (amdgpu/fglrx): Advanced Micro Devices, Inc. [AMD/ATI]|Renoir [DISPLAY_VGA] (vendor:1002 device:1636 subv:1043 subd:1e21) (rev: c6) Card:NVIDIA GeForce 635 series and later: NVIDIA Corporation|TU106M [GeForce RTX 2060 Mobile] [DISPLAY_VGA] (vendor:10de device:1f15 subv:1043 subd:1e21) (rev: a1) # rpm -qa|grep -e nvidia -e prime -e amd|sort dkms-nvidia-current-460.67-1.mga7.nonfree lib64drm_amdgpu1-2.4.102-1.mga7 lib64teamdctl0-1.28-1.mga7 mageia-prime-0.4-12.mga7.nonfree nvidia-current-cuda-opencl-460.67-1.mga7.nonfree nvidia-current-doc-html-460.67-1.mga7.nonfree nvidia-current-utils-460.67-1.mga7.nonfree x11-driver-video-amdgpu-19.1.0-3.mga7 x11-driver-video-nvidia-current-460.67-1.mga7.nonfree # rpm -qa|grep grub grub2-common-2.02.0-15.mga7 grub2-efi-2.02.0-15.mga7 # lscpu|grep ^Model Model: 96 Model name: AMD Ryzen 7 4800H with Radeon Graphics
Hi, I tried Mageia-Prime in laptop Asus with Nvidia-optimus GTX960. It don't works fine after upgrade from Mageia 7. I have uninstalled mageia-prime, all Nvidia packages, and I have reinstalled all. After the installation, mageia-prime works fine. The change of x11 is correct. Greetings!!
Thanks for reporting. @Dave, Guiseppe, Aurelien: Per comment 43, I think think we should add errata note that if optimus stop working, try to uninstall mageia-prime and all nvidia packages, then reboot and install them again?
Likely just running mageia-prime-uninstall followed by mageia-prime-install would have fixed the issue, or possibly just running mageia-prime-install again, but I can't confirm that. Still need an advisory for mageia-prime-0.4-12.mga7.nonfree and the bug assigned to qa if there are no further changes intended.
Hi all, I think that the last version of mageia-prime works fine for new installations in Mageia 7 y 8. I think that we can close this bug and put advisory in erratas web of the solution for updates issue bug, and that the user reinstall the package after update. This bug is two years old... Greetings!
Noted the upgrade issue top under https://wiki.mageia.org/en/Mageia_8_Errata#Various_upgrade_issues
Keywords: (none) => FOR_ERRATA8
Keywords: FOR_ERRATA8 => IN_ERRATA8
Still need an advisory for mageia-prime-0.4-12.mga7.nonfree and the bug assigned to qa if there are no further changes intended before this can be validated and closed.
Last chance Giuseppe. If you want to push this update, write an advisory and assign to QA.
Mageia 7 is EOL since July 1st 2021. There will not have any further bugfix for this release. You are encouraged to upgrade to Mageia 8 as soon as possible. @reporter, if this bug still apply with Mageia 8, please let us know it. @packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead. This bug report will be closed OLD if there is no further notice within 1st September 2021.
Hi bug reporter and hi assignee and others involved, Please reopen this bug report if it is still valid for Mageia 8 or 9(cauldron), and change "Version:" in the upper left of this report accordingly. This report is being closed as OLD because it was filed against Mageia 7, for which support ended on June 30th 2021. Thanks, Marja
Status: NEW => RESOLVEDResolution: (none) => OLD