I guess I made some mistake, as there are messages labeled uvesafb in
all the boot attempts this afternoon. Maybe I should have blacklisted
uvesafb besides commenting it out from
/etc/initramfs-tools/modules. I'll try this during the weekend later.
Regards,
Luis
On Thu, Nov 01, 2012 at 05:57:19PM -0700, Jonathan Nieder wrote:
> Luis Mochan wrote:
>
> > I followed your instructions below and again got to a black screen and
> > an unresponsive laptop. I had to use a recover disk to go back to the
> > previous configuration. Would the /var/log/messages file be useful?
>
> To avoid wasting the round-trip:
>
> 1. Yes, a kernel log from the failing boot would be very helpful,
> since then we might learn something about why it failed. :)
>
> 2. Testing 3.6.y from experimental as well using the nouveau driver
> with uvesafb disabled would be nice.
>
> Thanks,
> Jonathan
--
o
W. Luis Mochán, | tel:(52)(777)329-1734 /<(*)
Instituto de Ciencias Físicas, UNAM | fax:(52)(777)317-5388 `>/ /\
Apdo. Postal 48-3, 62251 | (*)/\/ \
Cuernavaca, Morelos, México | moc...@fis.unam.mx /\_/\__/
O< ascii ribbon campaign - stop html mail - www.asciiribbon.org
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20121102031717.gf2...@em.fis.unam.mx
