Automatic migration from nvidia to nvidia-390xx


#6

It already does that. And what problem your computer have at this moment that needs to be fixed?


#7

WRONG, I tested it with a bumblebee, and it updates to 396.X series… requires manual invervention to uninstall nvidia bumblebee and install nvidia-390.XX bumblebee


#8

muahahahahahahaha … When did a package installed by itself just because you where thinking about it? Seriously?


#9

It’s simple, just detecting the hardware id and switching to the correct nvidia driver… not funny at all


#10

I see you are insisting. Bravo.
User X, user Y and user Z have the same GPU model. Y wants to use the nouveau driver (free driver) on his/her system because that is what wants to use. User Y wants to use the latest Nvidia Driver because prefers to have the latest thing installed. User Z prefers stability so it will use the lagacy driver. Tell me how MHWD will know that ?
Please, enlighten me!

If you prefer to Auto Install … it will do just that, as it did previously.


#11

I think you dont understand it. The point is that you have to install something first manually. So, then you have very clear auto update path - if you have installed nouveau, then updater just updates it. If you have new and supported nvidia gpu, then updater updates to newest 396.xxx driver version. But if you have old and unsupported gpu and have installed nvidia drivers, then update to legacy drivers 390.xxx. All the other paths are easily covered too - only nvidia driver works with mobile gpu, and nouveau is ■■■■ in general, so nvidia driver for desktop gpus, too, unless you want to change it yourself. The hardest part is to get all hardware ids of supported and unsupported nvidia gpus, grouped by driver version. After that it is like 5 minutes job.


#12

I have a GPU that can use all of the 3 drivers mentioned. In what case is not my intervention necessary?
And guys, this is a linux forum, please don’t straw man.


#13

that require to have the list all PCI ID videos cards for that ,
and added to mwhd and this do not tells that this will always work in the future for 390.x series and Fermi , any Mesa , OpenGL , Vulkan or bumblebee or prisme update


#14

That’s right and if a non IT user see there is a black screen after update. It just says: Manjaro is unstable and ■■■■■■■■ and return to Windows


#15

That’s ok because the Windows users who’s computers started rebooting by itself after updating nvidia switched over to Manjaro.


#16

I(ve solved many issues by our discord channel, I’m the fondator and the respinner of Manjaro TuxnVape version (Baba Orhum) www.tuxnvape.fr.

It’s hard to have the trust of many users about Linux and harder with a lots of linux fixed desktop release users bashing Manjaro and desktop rolling release. If a driver can be switch more easily it’s just a better point for Manjaro


#19

A driver should never be “switched” automatically. This sort of thing will cause many more issues than it will solve.

Linux is not Windows.

This will happen from time to time on a rolling release distro, particularly with nvidia drivers.

People that have absolutely no interest in how their system works should not use a rolling release distro, instead a version release distro like Mint may be more appropriate.

Ironically, since Microborg has moved to a W10 rolling release model they are having all sorts of update issues also.


[Stable Update] 2018-05-07 - Kernels, Mesa, Glibc, PHP, Nvidia, Plasma5, Firefox
#20

This is hard for Artificial Intelligence but fairly easy for Human Intelligence.
Until now, I never had any impression than Manjaro claims that it is a NO USER INTERVENTION distribution.
For the record, I have a similar setup and the auto flag for mhwd non-free installation did not install 390xx but plain video-nvidia.
I followed the advice given in the Announcemente Topic. THIS is trivial for Manjaro/Archlinux distros.
Manual intervention is needed from time to time. That’s life! :grin:


#21

Normally it should install 390xx if supported. What is the output of mhwd on your end?

On my end it runs correct:

$ sudo mhwd -a pci nonfree 0300
> Skipping already installed config 'video-nvidia' for device: 0000:1c:00.0 (0300:10de:0fc6) Display controller nVidia Corporation GK107 [GeForce GTX 650]

#22

Right now it seems to see it OK.

$ mhwd
> 0000:02:00.0 (0200:10ec:8168) Network controller Realtek Semiconductor Co., Ltd.:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
         network-r8168            2016.04.20                true            PCI


> 0000:01:00.0 (0300:10de:1244) Display controller nVidia Corporation:
--------------------------------------------------------------------------------
                  NAME               VERSION          FREEDRIVER           TYPE
--------------------------------------------------------------------------------
    video-nvidia-390xx            2018.05.04               false            PCI
    video-nvidia-340xx            2018.05.04               false            PCI
    video-nvidia-304xx            2018.05.04               false            PCI
           video-linux            2018.05.04                true            PCI
            video-vesa            2017.03.12                true            PCI

But I just upgraded mhwd-nvidia-1:396.24-1-any


#23

This is logical as this is part of mhwd. The package only included IDs and not any driver. People get always anxious when some driver drops support of their card …


#24

inxi -G returns this:

Graphics: Card-1: NVIDIA GF108 [GeForce GT 430] driver: nvidia v: 340.106
Display: x11 server: X.Org 1.19.6 driver: nvidia resolution: 1680x1050~60Hz
OpenGL: renderer: GeForce GT 430/PCIe/SSE2 v: 4.4.0 NVIDIA 340.106

So I know I have the 340 series drivers. Do I need to upgrade to the 390 series?


#25

Need to? No. If what you have works and you’re happy with it you can stick with it.

Otherwise if you want the “latest and greatest” then according to http://www.nvidia.com/Download/driverResults.aspx/132530/en-us

your GPU is supported by the 390-series driver so you should be able to switch without issue.


#26

I found some old script we used for the nvidia 340xx transition:

	# nvidia legacy changes (sept-oct 2014 - kernels 3.10-3.17)
	pacman -Qq nvidia-utils &> /tmp/cmd1
	pacman -Qq mhwd-nvidia-340xx &> /tmp/cmd2
	if [ "$(grep 'nvidia-utils' /tmp/cmd1)" == "nvidia-utils" ]; then
		if [ "$(grep 'mhwd-nvidia-340xx' /tmp/cmd2)" != "mhwd-nvidia-340xx" ]; then
			msg "Updating mhwd database"
			rm /var/lib/pacman/db.lck &> /dev/null
			pacman --noconfirm -S mhwd-db
		fi
		mhwd | grep " video-nvidia " &> /tmp/cmd3
		mhwd-gpu | grep nvidia &> /tmp/cmd4
		pacman -Qq | grep nvidia | grep -v mhwd | grep -v toolkit &> /tmp/cmd5
		if [[ -z "$(cat /tmp/cmd3)" && -n "$(cat /tmp/cmd4)" ]]; then
			msg "Maintaining video driver at version nvidia-340xx"
			rm /var/lib/pacman/db.lck &> /dev/null
			pacman --noconfirm -Rdd $(cat /tmp/cmd5)
			pacman --noconfirm -S $(cat /tmp/cmd5 | sed 's|nvidia|nvidia-340xx|g')
			rm -r /var/lib/mhwd/local/pci/video-nvidia/
			cp -a /var/lib/mhwd/db/pci/graphic_drivers/nvidia-340xx/ /var/lib/mhwd/local/pci/
		fi
	fi

It may be reused for nvidia 390xx series.


#27

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.