Citat:
GOTCHA: A common bug report is enabling the framebuffer without enabling the
framebuffer console. Depending on the driver, you may get a blanked or
garbled display, but the system still boots to completion. If you are
fortunate to have a driver that does not alter the graphics chip, then you
will still get a VGA console.
srdjan@Zverko:~$ gedit /usr/src/linux-2.6.30/Documentation/fb/fbcon.txt
srdjan@Zverko:~$ tree /lib/modules/2.6.30-10-generic/kernel/drivers/video/ | grep fbdev
srdjan@Zverko:~$ tree /lib/modules/2.6.30-10-generic/kernel/drivers/video/ | grep uvesafb
|-- uvesafb.ko
srdjan@Zverko:~$ tree /lib/modules/2.6.30-10-generic/kernel/drivers/video/ | grep nvidiafb
| `-- nvidiafb.ko
srdjan@Zverko:~$
srdjan@Zverko:/etc/modprobe.d$ sudo gedit blacklist-framebuffer.conf
# Framebuffer drivers are generally buggy and poorly-supported, and cause
# suspend failures, kernel panics and general mayhem. For this reason we
# never load them automatically.
blacklist aty128fb
blacklist atyfb
blacklist radeonfb
blacklist cirrusfb
blacklist cyber2000fb
blacklist cyblafb
blacklist gx1fb
blacklist hgafb
blacklist i810fb
blacklist intelfb
blacklist kyrofb
blacklist lxfb
blacklist matroxfb_base
blacklist neofb
#blacklist nvidiafb
blacklist pm2fb
blacklist rivafb
blacklist s1d13xxxfb
blacklist savagefb
blacklist sisfb
blacklist sstfb
blacklist tdfxfb
blacklist tridentfb
blacklist vesafb
blacklist vfb
blacklist vga16fb
blacklist vt8623fb
Zatarabio sam nvidijin, pa sta mu bog da...