Bug#336450: linux-image-2.6.14-1-686: 2.6.14-1-686 doesn't support vga=795 o

[Sven Luther <sven.luther@wanadoo.fr>]

On Sun, Oct 30, 2005 at 10:21:39PM +0100, Jonas Smedegaard wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> On Sun, 30 Oct 2005 15:25:33 +0000
> "Richard Burton" <richardaburton@hotmail.com> wrote:
> 
> > >This could be changes to video drivers in the kernel. Please describe
> > >your graphics card used.
> > 
> > Oops, I did intened to mention that. It's an Nvidia GeForce 6600GT
> > 128MB (generic unbranded reference board).
> 
> Nvidia. Ok (or "ok" is perhaps an exageration: problems with this
> specific hardware vendor is not really a surprise to me...)
> 
> 
> > >Please try the following:
> > >1) add "ramdisk = /usr/sbin/mkinitrd.yaird" to /etc/kernel-img.conf
> > >2) make a backup of the initrd for your older working kernel
> > >3) Run "dpkg-reconfigure <old kernel package>"
> > >4) Reboot with older kernel
> > 
> > Now older kernel hits same problem. So I guess this is yaird problem
> > then?
> > 
> > >You can also try installing initramfs-tools, uninstalling yaird, run
> > >"dpkg-reconfigure <new kernel package>" and reboot with new kernel.
> > 
> > Also has no video on boot.
> 
> You did remember to uninstall yaird before regenerating the ramdisk?
> 
> Then it sounds like the nvidia driver being buggy then - not a yaird
> bug if also appearing with initramfs-tools.

Notice that the nvidiafb driver seems to be broken on powerpc too, one more
reason to never buy nvidia based laptops :)

Anyway, just to notice that anything involving vga=... command line options
doesn't involve nvidiafb but vesafb/vgafb, and we did some changes to that
recently i think.

Friendly,

Sven Luther