retitle 684240 uvesafb: nouveaufb shows black screen (missing framebuffer
handoff support)
tags 684240 - moreinfo + upstream
severity 684240 normal
quit
Luis Mochan wrote:
> After update-initramfs, it seems to work fine now! Thanks!
Ok, awesome.
I'm recycling this bug to describe the main rem
After update-initramfs, it seems to work fine now! Thanks!
Best regards,
Luis
On Thu, Nov 01, 2012 at 08:19:02PM -0700, Jonathan Nieder wrote:
> Luis Mochan wrote:
>
> > I guess I made some mistake, as there are messages labeled uvesafb in
> > all the boot attempts this afternoon.
>
> Ah, I
Luis Mochan wrote:
> I guess I made some mistake, as there are messages labeled uvesafb in
> all the boot attempts this afternoon.
Ah, I know what step I left out now. :/
It's
update-initramfs -u -k all
Sorry about that.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian
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
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 th
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?
Yes, a kernel log of that boot would be useful.
Thanks,
Jonath
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?
Regards,
Luis
> Could you try nouveau again using this information? This experiment
>
On Tue, Oct 30, 2012 at 04:40:00PM -0700, Jonathan Nieder wrote:
> Luis Mochan wrote:
>
> > I guess you want this is the relevant output of grep:
> > /etc/initramfs-tools/modules:uvesafb
> > /etc/modprobe.d/uvesafb.conf:options uvesafb mode_option=1280x1024-32
> > scroll=ywrap
>
> Actual
Luis Mochan wrote:
> I guess you want this is the relevant output of grep:
> /etc/initramfs-tools/modules:uvesafb
> /etc/modprobe.d/uvesafb.conf:options uvesafb mode_option=1280x1024-32
> scroll=ywrap
Actually, the full output (as an attachment) would be helpful.
> Now that I see it, I
I guess you want this is the relevant output of grep:
/etc/initramfs-tools/modules:uvesafb
/etc/modprobe.d/uvesafb.conf:options uvesafb mode_option=1280x1024-32
scroll=ywrap
Now that I see it, I vaguely recall writing this this line following
information in someone's blog. I had started
Sven Joachim wrote:
> I think uvesafb is only loaded if you force it to (e.g. with the
> video=uvesafb kernel parameter), and it's not even included in the
> initramfs by default.
Ah. Luis: please attach the output of
grep . /etc/initramfs-tools/* /etc/modprobe.d/*
Thanks,
Jonathan
-
On 2012-10-11 02:04 +0200, Jonathan Nieder wrote:
> Luis Mochan wrote:
>
>> [ 297.964] (II) [drm] DRM interface version 1.4
>> [ 297.964] (II) [drm] DRM open master succeeded.
>> [ 297.964] (--) NOUVEAU(0): Chipset: "NVIDIA NV86"
>
> Sven has the same chipset, I think. It was supposed to wo
12 matches
Mail list logo
