Re: Blank screen at boot with kernel 3.1
On Wed, Jan 25, 2012 at 3:09 PM, Sven Joachim <svenjoac@gmx.de> wrote:
> 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.
This can't be. I installed a testing box and upgraded it to unstable
today and I have both 3.1 and 3.2 installed - and they're both still
available in the repos.
# tune2fs -l /dev/sda2 | grep created
Filesystem created: Wed Jan 25 03:35:13 2012
#
# aptitude search linux-image -F '%p %t %v %V'
linux-image
<none> <none>
linux-image-2.6-486
unstable <none> 3.2+42
linux-image-2.6-686
unstable <none> 3.2+42
linux-image-2.6-686-bigmem
unstable <none> 3.2+42
linux-image-2.6-686-pae
unstable <none> 3.2+42
linux-image-2.6-amd64
unstable <none> 3.2+42
linux-image-3.1.0-1-486
testing <none> 3.1.8-2
linux-image-3.1.0-1-686-pae
testing 3.1.8-2 3.1.8-2
linux-image-3.1.0-1-686-pae-dbg
testing <none> 3.1.8-2
linux-image-3.1.0-1-amd64
testing <none> 3.1.8-2
linux-image-3.2.0-1-486
unstable <none> 3.2.1-2
linux-image-3.2.0-1-686-pae
unstable 3.2.1-2 3.2.1-2
linux-image-3.2.0-1-686-pae-dbg
unstable <none> 3.2.1-2
linux-image-3.2.0-1-amd64
unstable <none> 3.2.1-2
linux-image-486
unstable <none> 3.2+42
linux-image-686
unstable <none> 3.2+42
linux-image-686-bigmem
unstable <none> 3.2+42
linux-image-686-pae
unstable <none> 3.2+42
linux-image-amd64
unstable <none> 3.2+42
Reply to: