Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replace rpmfusion Obsoletes with Conflicts, add auto-fallback to nouveau systemd service #20

Closed
wants to merge 1 commit into from

Conversation

jwrdegoede
Copy link
Contributor

No description provided.

@scaronni
Copy link
Member

scaronni commented May 9, 2017

I think this is not enough. I'm upgrading from RPMFusion, elrepo and Nvidia CUDA repositpories, this is only a bit of it.

For example, one of the latest bugs opened on Fedora's bugzilla (don't have the ticket number at hand, sorry, it's the one where Leigh helped) where the user had left overs from both RPMFusion and CUDA repositories would have not happened with the Obsoletes/Provides in place.

I guess I will just remove all Obsoletes/Provides and put everything into Conflicts.

Would it be better if I just leave the base driver and modules/tools in the repository? Being an interim solution I can leave CUDA and all the rest in the other repository (multimedia). Most of the universities use those.

%global _dracutopts nouveau.modeset=0 rdblacklist=nouveau
%global _dracutopts_rm nomodeset vga=normal
%global _dracutopts rdblacklist=nouveau
%global _dracutopts_rm nomodeset vga=normal nouveau.modeset=0
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Further down in the SPEC file I just check for the whole string of options, and the other two have been there for quite a while, so I guess all users will not have those and the nouveau.modeset=0 parameter would not get removed.

I guess I need to remove the old Dracut options and just leave that, or iterate on each of one in the SPEC file.

@scaronni
Copy link
Member

scaronni commented May 9, 2017

Looks fine for me, as written in the email I would have actually preferred to have the kernel locked into place until all modules are available.

Someone who installs the Nvidia drivers would definitely give priority to the drivers being available than updating the kernel. I think users will be pretty vocal about this just after we enable it.

@scaronni
Copy link
Member

I've added the fallback service and made sure that the nouveau.modeset=0 parameter is removed on Fedora 25+.

6b3bf32
df32483

I'm going to make some test (hopefully this evening) and write a blog post/change the docs to announce that the packages no longer upgrade ELRepo, RPMFusion and Nvidia packages. I have also a couple of pending items to explain so this is a good moment.

After that, so I guess this weekend or next week, I'll push the ones with Conflicts in place. I need to also make the same changes to the CUDA and NVENC packages to avoid errors in solving dependencies when you have/want the other packages.

@jwrdegoede
Copy link
Contributor Author

jwrdegoede commented May 12, 2017 via email

@jwrdegoede
Copy link
Contributor Author

jwrdegoede commented May 12, 2017 via email

@jwrdegoede
Copy link
Contributor Author

jwrdegoede commented May 12, 2017 via email

Add dracut.conf.d/99-nvidia.conf file enforcing that the nvidia modules never
get added to the initramfs.

This is necessary because the userspace bits and the kernel modules must
be 100% in sync, otherwise things might break. Normally we build the initrd
before building the dkms / akmod so this issue will only happen if the initrd
somehow gets re-generated afterwards, still this is something which we should
avoid.
@jwrdegoede
Copy link
Contributor Author

Hmm, my latest push was meant for a new pull-req really, since 2 of the 3 commits from this pull-req have been merged and the other one is going to get a different fix. So lets close this pull-req.

@jwrdegoede jwrdegoede closed this May 12, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants