On Sun, 01 Jan 2012 17:57:09 +0100, Sven Joachim wrote: > On 2012-01-01 17:46 +0100, Camaleón wrote: > >> On Sun, 01 Jan 2012 17:20:25 +0100, Sven Joachim wrote: >> >>> On 2012-01-01 15:33 +0100, Camaleón wrote: >>> >>>> On Sun, 01 Jan 2012 11:29:51 +0100, Sven Joachim wrote: >>>> >>>>> On 2011-12-31 21:41 +0100, Dean Allen Provins, P. Geoph. wrote: >>>>> >>>>> That's why I suggested to log in from a second computer via ssh. >>>>> It's hard to do anything with a blank screen. >>>> >>>> I guess blacklisting nouveau module should have be done from "init 1" >>>> with no running X session at all. >>> >>> Booting with "init 1" does not prevent the module from being loaded. >> >> (...) >> >> I haven't expressed myself right. I didn't want to say "booting at init >> 1 to prevent the nuvó module from being loaded" but once the system has >> booted (with KMS disabled) jump to "init 1" and blacklist the module >> from there. > > There is no reason why you would need to switch to runlevel 1 for that.
Neither to avoid losing X and preventing Xorg from going nuts? :-) > Besides, changing the bootloader configuration to permanently add the > "nomodeset" kernel parameter might be better than blacklisting the > module. Why do you think "nvidia" nor "nuvó" are not going to work? Because working with VESA does not look like a sane option nowadays :-( Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2012.01.01.17.11...@gmail.com