On Sat, Nov 21, 2009 at 7:46 AM, Nicolas Chauvet
<kwizart@gmail.com> wrote:
2009/11/21 Adam Williamson <adamwill@shaw.ca>:
> On Tue, 2009-11-17 at 17:10 -0800, Conrad Meyer wrote:
>> On Tuesday 17 November 2009 04:21:40 pm Chris Nolan wrote:
>> > A few people (me included) are wondering what has happened to
>> > kmod-nvidia in F12? Did it get missed somehow or is there a problem with
>> > it?
>> >
>> > Thanks
>> > Chris
>>
>> If you read the announcement email, they are in updates-testing because some
>> sort of manual step is required.
>
> Some notes on this.
>
> So, it seems the manual steps required are a) rebuild the initramfs -
> I'm assuming the nvidia packages somehow configure things so that
> nouveau doesn't get pulled into the initramfs any more and b) change
> SELinux configuration to disable executable stack protection.
>
> on b), a clean F12 install has these relevant SELinux settings:
If you want to be on any help on b) please review the nvidia-settings
and nvidia-xconfig.
on a) that part isn't planned to be solved before the introduction of
the new packaging scheme.
Whereas it could have been safe to regenerate the initrd on install
(it's not actually as we have seen mkinitrd update that then failed to
create a valid initrd.img), it's even more probable that a dracut
plugin get installed whereas it shouldn't have, leading to a failure
in generation of a valid initramfs.
Now if some want to write a dracut module to handle that propertly,
experimentation is always open. And I wish I can hear feedback on
this.
For the record, what handle the initrd regeneration is to create a
blacklist-nouveau.conf in /etc/modprobe.d
The same is also needed for radeon and fglrx.
Nicolas (kwizart)