[Bug 129910] Re: Blank ttys when using vesafb (vga=xxx)

TrinitronX TrinitronX at gmail.com
Sat Feb 2 02:47:50 UTC 2008

Hello, running a Gateway C-140x convertible tablet that includes an "ATI Mobility™ Radeon® X2300 HD" card.  I initially had problems with the usplash not displaying on boot as well as the no terminal problem.
I changed around the display settings in /etc/usplash.conf to be:
Then installed the proprietary fglrx drivers (in the process of this I had need of a terminal when X would not start, only to find that those would not work either! Only booting recovery console would  get a working terminal thankfully.)

Fixed it with the following steps:
sudo apt-get install hwinfo
sudo hwinfo --framebuffer
looked through supported vga modes and found one I liked:
Mode 0x0323: 1024x768 (+4096), 32 bits

sudo vim /boot/grub/menu.lst
found my kernel line and added vga=0x0323
Add fb modules to initramfs:
sudo vim /etc/initramfs-tools/modules

sudo vim /etc/modprobe.d/blacklist-framebuffer
un-blacklist the module by commenting out line:
#blacklist radeonfb
update the initramfs:
sudo update-initramfs -u -k all -v

Fixed with acceptable resolution and working usplash :D.

Seriously though, how'd this bug even get into Gutsy?  There's no need
to break previously working framebuffer modules for the sake of power
management.  I'd think having a working set of ttys is more important.
This is most certainly a case of: "If it ain't broke, don't fix it".
I'd like to see this back to normal in Hardy.

Blank ttys when using vesafb (vga=xxx)
You received this bug notification because you are a member of Kernel
Bugs, which is a bug contact for initramfs-tools in ubuntu.

More information about the kernel-bugs mailing list