Not so long ago, I posted a fix for the kdm splash screen of the Feisty Fawn release of Kubuntu. Every time there was a kernel update, it would update my grub menu and I had to go back into /boot/grub/menu.lst and update the line for the first kubuntu boot option with a vga setting (vga=792).
Please see this post for details.
This works in Gutsy, too, but for my setup (I have an agp ATI X700 graphics card connected via DVI to a 19″ Acer LCD), I had to update some more files first. I was lost until I happened upon this post in the ubuntu forums regarding framebuffer errors (thanks El Chupacabras).
Basically, I have to force the kernel to recognize my card and driver.
First, I had to edit the framebuffer blacklist for the kernel. This file is found at /etc/modprobe.d/blacklist-framebuffer and can be opened with any text editor. I like nano and vim.
$ sudo nano /etc/modprobe.d/blacklist-framebuffer
The file will look something like this:
# 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…
Locate the brand that most closely resembles the name of your graphics card, and comment it out by putting a # in front of it. In my case, I inserted # in front of “blacklist radeonfb” and “blacklist vesafb” (never hurts to allow vesafb). Once completed, remember to “save” it and close your editor.
That done, I next updated startup modules with the same framebuffers. That, too, is a file update. The file is located at /etc/initramfs-tools/modules:
$ sudo nano /etc/initramfs-tools/modules
The file will look something like this:
# List of modules that you want to include in your initramfs.
#
# Syntax: module_name [args ...]
#
# You must run update-initramfs(8) to effect this change.
#
# Examples:
#
# raid1
# sd_mod
Go to the end of the file and add your framebuffers and the controller. I added to the end of the file:
fbcon
radeonfb
vesafb
Now just update the init scripts with one simple line:
$ sudo update-initramfs -u -k all
After that, I simply updated the kernel boot line in /boot/grub/menu.lst as I did before, even using the same vga (vga=792). It has worked ever since.
As the kernel has been updated, all I’ve had to update is the kernel line just as before with Feisty.
Again, thanks to El Chupacabras of ubuntuforums for finding this solution!
I hope this works for some of you as well as it worked for me!
I’ve installed kubuntu from windows xp trough wubi installer. A virus had made a lot of damage in windows, so, I was forced to format my C: partition (primary); after wards I’ve installed windows xp on the same partition (C:). Kubuntu remained on D: (ext+logical partition). Somehow I’ve solved the dual boot, and now, I’m getting in this menu:
BusyBox v1.1.3 (Debian 1:1.1.3-2ubuntu3) Built-in shell (ash)
/bin/sh: can’t access tty; job control turned off
(initramfs)
Comment by Florin — September 16, 2008 @ 1:02 am
PLEASE HELP ME…
( BECAUSE I HAVE CONFIGURED AN ACCOUNTANCY PROGRAM WITCH CONNECTS TROUGH A SERVER ABROAD. AND I NEED KUBUNTU INTACT.
Comment by Florin — September 16, 2008 @ 1:06 am
Don’t know that this will help, but it sounds like your bootloader has bad info. What all is on your boot menu?
If you can boot into linux in any way, even if just with command line only, try running grub-install as root (or “sudo grub-install”). That might rebuild the file to correctly display the installed systems (it edits the menu.lst file in the /boot/grub/ directory).
Comment by WirelessMike — September 16, 2008 @ 7:52 am