Surely you've as much chance of doing that from lilo or blindly from the terminal as just blacklisting the module?

Yes, but I'm thinking long term here. Why let these kind of situations continue when we can fix them now for all distributions? So far kernel cmdline module blacklisting has been distro specific.

Ok fair enough, but you still need to tell modprobe what _not_ to load even if you do manage to do things in this way, which is presumably done through the blacklist. Also, if you put something random at the end of the lilo boot command won't it just refuse to boot?

As far as I know the module will be loaded by udev right at the start of rc.S. I guess you could disable udev, which then raises a new question of how to do this from lilo (and probably a whole load of separate problems booting in general).

I don't know about all other distros but there has got to be a finite number of separate places the blacklist can be surely?

Anyone please do correct me if I'm wrong about anything I'm not very experienced at handing out advice (or a load of speculation basically)

This post was buried at the end of this thread, I moved it here

Hefty, do you get this problem in Arch?

Why no.... no i don't.

Anonymo, just in case you didn't see it already an howto for nouveau on Arch is available here.

I eventually did find out the reason why at first I got a black (or blank) screen after a while during startup: there is a resources conflict between nouveau fb and other framebuffer drivers.

To avoid that you can still blacklist nouveau (which doesn't prevent to use it anyway) or avoid running another framebuffer driver at startup.

For that, just edit /etc/lilo.conf and either comment the "VGA=nnn" option or choose either "VGA=ask" ot "VGA=ext", then re-run lilo... And say good-bye to Tux

I edited the first post accordingly.

@Hefty: this is not intended to answer your question, so there's no need to state you bad opinion about me again.

@Hefty : I eventually did find an answer to your question.

Boot and at the Lilo prompt type:You'll find an explanation here.