12:21 a.m.
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
1:10 a.m.
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.
--
Conrad Meyer <cemeyer(a)u.washington.edu>
11:06 p.m.
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:
allow_execheap --> off
allow_execmem --> on
allow_execmod --> off
allow_execstack --> off
so if execmem is enough, it may be OK. if execstack is needed, it isn't.
on a), is there some reason we don't just have the kmod package
re-generate the initramfs when it's first installed? Okay, it's not
particularly elegant, but probably better than making people do it
themselves.
just wanted to keep the ball rolling to see if f12 can be made as smooth
as possible from this perspective. if this discussion is happening
elsewhere, apologies, please point me there...
--
adamw
10:46 a.m.
2009/11/21 Adam Williamson <adamwill(a)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)
3:32 p.m.
Is it possible to do a workaround to use it??..Nouveau is not working too,
it have an error too(https://bugzilla.redhat.com/show_bug.cgi?id=530520).
How can I use my machine?? .. I cant' use it at all.
Thank you.
salu2...
masch...
On Sat, Nov 21, 2009 at 7:46 AM, Nicolas Chauvet <kwizart(a)gmail.com> wrote:
2009/11/21 Adam Williamson <adamwill(a)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)
3:49 p.m.
I've seen the workaround for Nvidia proprietary drivers and it works
great!!..I hope that Fedora team can fix the noveau/vesa/Xorg issue and my
video card.
thank you.
On Sat, Nov 21, 2009 at 12:32 PM, Mario Chacon <the.masch(a)gmail.com> wrote:
Is it possible to do a workaround to use it??..Nouveau is not working
too,
it have an error too(https://bugzilla.redhat.com/show_bug.cgi?id=530520).
How can I use my machine?? .. I cant' use it at all.
Thank you.
salu2...
masch...
On Sat, Nov 21, 2009 at 7:46 AM, Nicolas Chauvet <kwizart(a)gmail.com>wrote:
> 2009/11/21 Adam Williamson <adamwill(a)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)
>
5:07 p.m.
On Sat, 2009-11-21 at 11:46 +0100, Nicolas Chauvet wrote:
> 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.
I'll have a look. Thanks. My first thought was we should introduce an
selinux policy package to change the appropriate settings
(selinux-policy-nvidia ?)
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.
That's interesting, cos warren told me dracut probably didn't parse
modprobe.d blacklists. that liar =)
--
adamw
5:09 p.m.
On Sat, 2009-11-21 at 11:46 +0100, Nicolas Chauvet wrote:
> 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.
Hans has reviewed both and approved them. They look fine to me too. I
don't see what they do about selinux, though?
--
adamw
9:28 a.m.
2009/11/21 Adam Williamson <adamwill(a)shaw.ca>:
On Sat, 2009-11-21 at 11:46 +0100, Nicolas Chauvet wrote:
> > 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.
Hans has reviewed both and approved them. They look fine to me too. I
don't see what they do about selinux, though?
that was explained in a previous
message. exectstac -c doesn't work on
x86 binaries leadind to have the selinux boolean on as a mandatory
option for this arch. (works for libraries at least).
5267
days inactive
5271
days old
rpmfusion-developers@lists.rpmfusion.org
10 comments
5 participants
participants (5)
-
Adam Williamson -
Chris Nolan -
Conrad Meyer -
Mario Chacon -
Nicolas Chauvet