10:09 p.m.
2009/11/25 Adam Williamson <awilliam(a)redhat.com>:
On Wed, 2009-11-25 at 15:02 -0600, Michael Cronenworth wrote:
> On 11/25/2009 02:15 PM, Adam Williamson wrote:
> > and the nvidia kernel module conflicts with
> > the nouveau one.
> There is no conflict. I'm not sure why RPMFusion is recommending
> rebuilding your initramfs. It is completely unnecessary.
Uh? If the nouveau kernel module is loaded, the nvidia kernel module
refuses to load, complaining that another module is in control of the
hardware. I've seen multiple people report this. I haven't seen anyone
who's got the NVIDIA driver working if the nouveau module is loaded.
I think
it's possible, but it's random.
In some case, it works, in others not.
Once that said, I saw that it could be possible to use
nouveau.modeset=0 on the grub line.
I never tried that solution, but the perspective to have two
differents driver loaded at the same time for one hardware just scared
me.
IIRC nvidia-installer (not nvidia.ko) has detection routine to know if
nvidiafb is loaded, because it has produced well knwon
incompatiblities from the past. I wonder if they have updated it for
nouveau.
Nicolas Chauvet (kwizart)
10:16 p.m.
New subject: NVIDIA / nouveau thread branch [was Re: Fedora 12 QA retrospective - feedback needed]
On Wednesday 25 November 2009, Nicolas Chauvet wrote:
2009/11/25 Adam Williamson <awilliam(a)redhat.com>:
> On Wed, 2009-11-25 at 15:02 -0600, Michael Cronenworth wrote:
>> On 11/25/2009 02:15 PM, Adam Williamson wrote:
>> > and the nvidia kernel module conflicts with
>> > the nouveau one.
>>
>> There is no conflict. I'm not sure why RPMFusion is recommending
>> rebuilding your initramfs. It is completely unnecessary.
>
> Uh? If the nouveau kernel module is loaded, the nvidia kernel module
> refuses to load, complaining that another module is in control of the
> hardware. I've seen multiple people report this. I haven't seen anyone
> who's got the NVIDIA driver working if the nouveau module is loaded.
I think it's possible, but it's random.
In some case, it works, in others not.
Once that said, I saw that it could be possible to use
nouveau.modeset=0 on the grub line.
I never tried that solution, but the perspective to have two
differents driver loaded at the same time for one hardware just scared
me.
IIRC nvidia-installer (not nvidia.ko) has detection routine to know if
nvidiafb is loaded, because it has produced well knwon
incompatiblities from the past. I wonder if they have updated it for
nouveau.
Nicolas Chauvet (kwizart)
nouveau.modeset=0 doesn't work here, kernel says it's unknown (and
ignored).
This works:
rdblacklist=nouveau
7:56 a.m.
New subject: NVIDIA / nouveau thread branch [was Re: Fedora 12 QA retrospective - feedback needed]
On Wed, Nov 25, 2009 at 11:16 PM, Neal Becker <ndbecker2(a)gmail.com> wrote:
nouveau.modeset=0 doesn't work here, kernel says it's unknown
(and ignored).
IIRC on F11 the message was expected, but the command was correctly
parsed and used by nouveau
In F12 I am quite sure a simple "nomodeset" works; at least, that's
how a friend said he fixed his lockups starting Firefox.
--
Gianluca Sforna
http://morefedora.blogspot.com
http://www.linkedin.com/in/gianlucasforna
5:40 a.m.
New subject: NVIDIA / nouveau thread branch [was Re: Fedora 12 QA retrospective - feedback needed]
On Wed, 2009-11-25 at 17:16 -0500, Neal Becker wrote:
> IIRC nvidia-installer (not nvidia.ko) has detection routine to
know if
> nvidiafb is loaded, because it has produced well knwon
> incompatiblities from the past. I wonder if they have updated it for
> nouveau.
>
> Nicolas Chauvet (kwizart)
>
nouveau.modeset=0 doesn't work here, kernel says it's unknown (and ignored).
Yes, it does work. It disables kernel modesetting. It doesn't stop the
module loading, that's not what it's intended to do. The message from
the kernel is bogus and should be ignored. See:
http://bugzilla.kernel.org/show_bug.cgi?id=14164
This works:
rdblacklist=nouveau
That does something different; it stops the nouveau module being loaded
during initrd phase (it's a dracut parameter).
As I understand things currently, there seem to be some situations where
it's enough to simply stop the nouveau module doing kernel modesetting -
i.e. you just need 'nouveau.modeset=0'; even if it gets loaded in this
case, nvidia still works. In other cases, it seems, nvidia doesn't work
unless you stop nouveau being loaded entirely. I'm still not exactly
sure what's going on there.
I believe to ensure nouveau never gets loaded, you need both the
rdblacklist parameter and a blacklist directive in /etc/modprobe.d (as
the package currently installs).
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Fedora Talk: adamwill AT fedoraproject DOT org
http://www.happyassassin.net
--
adamw
1:07 a.m.
New subject: NVIDIA / nouveau thread branch [was Re: Fedora 12 QA retrospective - feedback needed]
I have an issue with the nvidia driver in KDE. Certain actions, such as
- clicking on the K-menu
- clicking on the clock
- using an auto hiding panel
- ...
freezes KDE for 10 exact seconds. Afterwards things continue as if
nothing happened. I also saw this reported in nvnews.net under the
evdev thread. I didn't have time to locate the source of problem,
although it's most possibly evdev. Please let me know if there is a
solution or workaround.
kmod-nvidia-2.6.31.5-127.fc12.x86_64-190.42-1.fc12.4.x86_64
I have such error messages in Xorg.0.log:
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
[mi] EQ overflowing. The server is probably stuck in an infinite loop.
Backtrace:
0: /usr/bin/X (xorg_backtrace+0x28) [0x49e8d8]
1: /usr/bin/X (mieqEnqueue+0x1f4) [0x49e2a4]
2: /usr/bin/X (xf86PostMotionEventP+0xce) [0x478f0e]
3: /usr/lib64/xorg/modules/input/evdev_drv.so (0x7fc55c359000+0x50bf)
[0x7fc55c35e0bf]
4: /usr/bin/X (0x400000+0x6be17) [0x46be17]
5: /usr/bin/X (0x400000+0x116b13) [0x516b13]
6: /lib64/libpthread.so.0 (0x3d55200000+0xefa0) [0x3d5520efa0]
7: /usr/lib64/xorg/modules/drivers/nvidia_drv.so
(0x7fc57cb7b000+0xa4a51) [0x7fc57cc1fa51]
8: /usr/lib64/xorg/modules/libwfb.so (wfbBlt+0x1045) [0x7fc57c746495]
9: /usr/lib64/xorg/modules/libwfb.so (wfbCopyNtoN+0x25e) [0x7fc57c74a1ee]
10: /usr/bin/X (miCopyRegion+0x28d) [0x54575d]
11: /usr/bin/X (miDoCopy+0x44a) [0x545c6a]
12: /usr/lib64/xorg/modules/libwfb.so (wfbCopyArea+0x4c) [0x7fc57c7494cc]
13: /usr/lib64/xorg/modules/libwfb.so (wfb_image_from_pict+0x302)
[0x7fc57c74e8f2]
14: /usr/lib64/xorg/modules/libwfb.so (wfbComposite+0xd4) [0x7fc57c74ebd4]
15: /usr/lib64/xorg/modules/drivers/nvidia_drv.so
(0x7fc57cb7b000+0x33e817) [0x7fc57ceb9817]
16: /usr/bin/X (0x400000+0xd1c80) [0x4d1c80]
17: /usr/bin/X (0x400000+0x15e459) [0x55e459]
18: /usr/bin/X (0x400000+0x15e725) [0x55e725]
19: /usr/bin/X (0x400000+0xa2366) [0x4a2366]
20: /usr/bin/X (0x400000+0x4edde) [0x44edde]
21: /usr/bin/X (MapWindow+0x179) [0x452ec9]
22: /usr/bin/X (0x400000+0x2bdc6) [0x42bdc6]
23: /usr/bin/X (0x400000+0x2c69c) [0x42c69c]
24: /usr/bin/X (0x400000+0x21cfa) [0x421cfa]
25: /lib64/libc.so.6 (__libc_start_main+0xfd) [0x3d5461eb1d]
26: /usr/bin/X (0x400000+0x218a9) [0x4218a9]
1:16 a.m.
New subject: NVIDIA / nouveau thread branch [was Re: Fedora 12 QA retrospective - feedback needed]
On 11/26/2009 06:37 AM, Orcan Ogetbil wrote:
I have an issue with the nvidia driver in KDE. Certain actions, such
as
- clicking on the K-menu
- clicking on the clock
- using an auto hiding panel
- ...
freezes KDE for 10 exact seconds. Afterwards things continue as if
nothing happened. I also saw this reported in nvnews.net under the
evdev thread. I didn't have time to locate the source of problem,
although it's most possibly evdev. Please let me know if there is a
solution or workaround.
Refer to
https://fedoraproject.org/wiki/Common_F12_bugs#Problems_when_using_the_pr...
Rahul
2:01 a.m.
New subject: NVIDIA / nouveau thread branch [was Re: Fedora 12 QA retrospective - feedback needed]
On Wed, Nov 25, 2009 at 8:16 PM, Rahul Sundaram wrote:
On 11/26/2009 06:37 AM, Orcan Ogetbil wrote:
> I have an issue with the nvidia driver in KDE. Certain actions, such as
> - clicking on the K-menu
> - clicking on the clock
> - using an auto hiding panel
> - ...
> freezes KDE for 10 exact seconds. Afterwards things continue as if
> nothing happened. I also saw this reported in nvnews.net under the
> evdev thread. I didn't have time to locate the source of problem,
> although it's most possibly evdev. Please let me know if there is a
> solution or workaround.
>
Refer to
https://fedoraproject.org/wiki/Common_F12_bugs#Problems_when_using_the_pr...
Rahul
Oh great. Thank you!
Orcan
5262
days inactive
5266
days old
rpmfusion-developers@lists.rpmfusion.org
6 comments
6 participants
participants (6)
-
Adam Williamson -
Gianluca Sforna -
Neal Becker -
Nicolas Chauvet -
Orcan Ogetbil -
Rahul Sundaram