开机在grub中选择启动Ubuntu12.04后，出错信息大致是这样的：
FATAL: Error inserting vesafb (/lib/modules/3.2.0-39-generic/kernel/drivers/video/vesafb.ko): No such device
我在电脑里搜索到有这个文件：
/lib/modules/3.2.0-39-generic-pae/kernel/drivers/video/vesafb.ko
出错信息持续大约3秒后Ubuntu系统就正常启动，使用一切正常。
如果使用待机再启动不会提示错误，一切正常。但每次关机重启后都出错，不知道是什么原因？
貌似出错前我曾做过以下操作：
因为用tty1时不能显示中文，我就安装使用了fbterm能正常显示中文，看到开机出错后又卸载过，开机还是有错，再重装fbterm还是有错，现在电脑里安装了fbterm,在tty1下还是显示不了中文。
还請高手帮忙，不胜感激！！
Ubuntu启动时出错（FATAL: Error inserting vesafb）
版面规则
我们都知道新人的确很菜，也喜欢抱怨，并且带有浓厚的Windows习惯，但既然在这里询问，我们就应该有责任帮助他们解决问题，而不是直接泼冷水、简单的否定或发表对解决问题没有任何帮助的帖子。乐于分享，以人为本，这正是Ubuntu的精神所在。
我们都知道新人的确很菜，也喜欢抱怨，并且带有浓厚的Windows习惯，但既然在这里询问，我们就应该有责任帮助他们解决问题，而不是直接泼冷水、简单的否定或发表对解决问题没有任何帮助的帖子。乐于分享，以人为本，这正是Ubuntu的精神所在。
-
liaosen
- 帖子： 20
- 注册时间： 2011-06-08 9:43
-
liaosen
- 帖子： 20
- 注册时间： 2011-06-08 9:43
Re: Ubuntu启动时出错（FATAL: Error inserting vesafb）
自己在网上找了很久，只看到英文的回复，而且别人的问题貌似大都不能开机，我的是报错后能正常开机。
-
liaosen
- 帖子： 20
- 注册时间： 2011-06-08 9:43
Re: Ubuntu启动时出错（FATAL: Error inserting vesafb）
看英文回复有点云里雾里，这里也贴一个网上找的回复，看不懂也没有解决问题：
Instructions on how to boot Ubuntu into the rough equivalent of Windows "safe mode".
If that seems to go well, yo could try bringing the system up as close to normally as possible except for X by editing the boot params again and adding "text" to the boot params.
In any case, it makes sense to see if there are some old Xorg logs fro when it failed to come up. I'd take a peek in those to see if there is some other information that can be gleaned from those files.
Another useful approach (but kinda requires a bootable system or some knowledge of how to chroot into an exiting root filesystem or manually modifying the startup scripts, not too bad really) would be to configure the ssh server to come up and allow logging into the machine even in the case that X is off in the weeds.
Instructions on how to boot Ubuntu into the rough equivalent of Windows "safe mode".
If that seems to go well, yo could try bringing the system up as close to normally as possible except for X by editing the boot params again and adding "text" to the boot params.
In any case, it makes sense to see if there are some old Xorg logs fro when it failed to come up. I'd take a peek in those to see if there is some other information that can be gleaned from those files.
Another useful approach (but kinda requires a bootable system or some knowledge of how to chroot into an exiting root filesystem or manually modifying the startup scripts, not too bad really) would be to configure the ssh server to come up and allow logging into the machine even in the case that X is off in the weeds.