Re: nouveau vs nvidia - fresh install, nouveau wins

On Wed, May 4, 2011 at 9:19 AM, Axel Thimm <[email protected]> wrote:
> On Wed, 2011-05-04 at 08:05 -0700, Fedor Pikus wrote:
>> >> > Have you tried nouveau.modeset=0?
>> >>
>> >> Yes, tried that and rdblacklist=nouveau. I think the problem is that
>> >> initrd is built during the install and is configured for
>> >> high-resolution text modes, and all modules in initrd are loaded even
>> >> if they are later not used.
>> >
>> > I thought these commands would prevent the loading of nouveau from
>> > initrd/initram.
>> >
>> > Try booting into mode 3 or mode 1 and see if the nouveau driver has been
>> > loaded (lsmod | grep nouveau). BTW you need both the nouveau.modeset=0
>>
>> That's how I tracked it to initrd, I booted "single" and nouveau was
>> there, that's before most things are loaded. Well, that, and removing
>> nouveau.ko.
>>
>> > setting *and* the blacklisting at modprobe level, e.g. nouveau needs
>> > blacklisting at two levels.
>>
>> When it's not in initrd, blacklist in modprobe.conf is sufficient.
>> When it's in initrd, it just gets force-loaded on boot.
>
> So you mean that if you use the rdblacklist or modeset args you still
> get nouveau from the initramfs?
>
> Maybe the circumstances have changed, but at least until about 3/4 year
> ago I was maintaining a 20 node nvidia driven pool that autoinstalled
> and (IIRC) all I did was to shove the modeline into the grub.conf.

On F12 I never had this problem, but I just did 3 installs of F14, and
2 of them had that problem, nouveau was in initrd and I could not keep
it from loading until I ran mkinitrd. The 3rd system did not pick up
updated kernel during install, but got new kernel on the first run of
yum update, and did not have the same problem.

>
> If it has changed, and a new initramfs is needed, then maybe I'm fooled
> by the fact that the second kernel you install already has a "fixed"
> initramfs or maybe already the first, if the kickstart place the
> modprobe snippet onto the fs before the kernel was installed.

Anaconda does something special with the first initrd it creates,
subsequent "yum update" does not add nouveau to initrd. May be
kickstart creates normal initrd?

> --
> http://thimm.gr/ - http://ATrpms.net/
>
> _______________________________________________
> atrpms-devel mailing list
> [email protected]
> http://lists.atrpms.net/mailman/listinfo/atrpms-devel
>



-- 
Fedor G Pikus ([email protected])
http://www.pikus.net
http://wild-light.com