Re: Blank screen at boot with kernel 3.1
On 2012-01-25 20:38 +0100, Rémi Moyen wrote:
> Le 25 janvier 2012 18:10, Sven Joachim <svenjoac@gmx.de> a écrit :
>> On 2012-01-25 18:04 +0100, Rémi Moyen wrote:
>
>>> Kernel 3.2 seems to be still in unstable, I'd rather not install
>>> something from there if I can avoid it.
>>
>> No, 3.2 has been in testing for six days, 3.1 is not supported anymore.
>
> But linux-image-am64 still seems to be in version 3.1 and depends from
> linux-image-3.1.0-1-amd64?
The metapackage has not yet migrated, it seems. But 3.1 really is not
supported anymore, neither by Debian nor by upstream.
> I don't want to nominally install the 3.2
> kernel, I only want the latest one, so I think I'll stick to
> linux-image-amd64 and wait until that updates to 3.2. Should be quite
> soon, I guess.
As long as you don't have untrusted users on your system, a local root
exploit might not scare you much. And since you're willing to use a
proprietary kernel module for which nobody knows what nasty things it
might do, security probably does not really matter.
>>> * To blacklist nouveau, there needs to be a "blacklist nouveau" line
>>> somewhere in a file in /etc/modprobe.d. The nvidia DKMS package does
>>> this (or I did that manually), but apparently this is not enough.
>>
>> It is enough to prevent udev from loading the module, but X will still
>> try to load it if you don't specify a different driver in xorg.xonf.
>
> Good point. I guess though that now that I have added nomodeset,
> nouveau will not be available to X, so it shouldn't even try to load
> it?
X does not know about that parameter, so it will try to load nouveau
unless you specify a driver in xorg.conf. But
a) you have to specify the nvidia driver anyway if you want to use it;
b) the only ill effect would be an error message in Xorg's log.
Sven
Reply to: