| View previous topic :: View next topic |
| Author |
Message |
gw
Apprentice
Joined: 03 Dec 2006
Posts: 215
|
 Posted: Wed May 27, 2009 10:57 am Post subject: SOLVED: Lost my framebuffer console |
 |
|
Through some recent update of I don't know what, I no longer have a working framebuffer console, -- if framebuffer actually is the problem.
Symptoms are, that when I boot my machine, I no longer have those neat small fonts and huge display of information, but only a very large font, and very large tux splashimage.
Where can I check what went wrong, and how to regain the framebuffer display?
Thanks
gw
Last edited by gw on Thu May 28, 2009 7:49 pm; edited 1 time in total |
|
| Back to top |
|
 |
szczerb
Veteran
Joined: 24 Feb 2007
Posts: 1709
Location: Poland => Lodz
|
| Posted: Wed May 27, 2009 11:18 am Post subject: |
|
|
| You updated your kernel, right? What version? And show as your grub config and .config (it's huge so put in pastebin or something). |
|
| Back to top |
|
|
d2_racing
Bodhisattva
Joined: 25 Apr 2005
Posts: 13047
Location: Ste-Foy,Canada
|
| Posted: Wed May 27, 2009 11:57 am Post subject: |
|
|
| Also, are you sure that your console font wasn't change ? |
|
| Back to top |
|
|
gw
Apprentice
Joined: 03 Dec 2006
Posts: 215
|
| Posted: Wed May 27, 2009 1:54 pm Post subject: |
|
|
| d2_racing wrote: | | Also, are you sure that your console font wasn't change ? |
Thanks szczerb and d2_racing.
Here's some more info: | Code: | | uname -a Linux linux 2.6.28-gentoo-r5 |
| Code: | /boot/grub/grub.conf:
kernel /boot/kernel-2.6.28-gentoo-r5 root=/dev/sda5 console=tty1 video=uvesafb:mtrr:3,ywrap,1280x1024-32@60 |
| Code: | zcat /proc/config.gz | grep -i fb
CONFIG_FB=y
# CONFIG_FB_DDC is not set
CONFIG_FB_BOOT_VESA_SUPPORT=y
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
# CONFIG_FB_CFB_REV_PIXELS_IN_BYTE is not set
# CONFIG_FB_SYS_FILLRECT is not set
# CONFIG_FB_SYS_COPYAREA is not set
# CONFIG_FB_SYS_IMAGEBLIT is not set
# CONFIG_FB_FOREIGN_ENDIAN is not set
# CONFIG_FB_SYS_FOPS is not set
# CONFIG_FB_SVGALIB is not set
# CONFIG_FB_MACMODES is not set
# CONFIG_FB_BACKLIGHT is not set
CONFIG_FB_MODE_HELPERS=y
# CONFIG_FB_TILEBLITTING is not set
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ARC is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
CONFIG_FB_UVESA=y
CONFIG_FB_VESA=y
# CONFIG_FB_N411 is not set
# CONFIG_FB_HGA is not set
# CONFIG_FB_S1D13XXX is not set
# CONFIG_FB_NVIDIA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_I810 is not set
# CONFIG_FB_LE80578 is not set
# CONFIG_FB_INTEL is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_S3 is not set
# CONFIG_FB_SAVAGE is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_VIA is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_VT8623 is not set
# CONFIG_FB_CYBLA is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_ARK is not set
# CONFIG_FB_PM3 is not set
# CONFIG_FB_CARMINE is not set
# CONFIG_FB_GEODE is not set
# CONFIG_FB_VIRTUAL is not set
# CONFIG_FB_METRONOME is not set
# CONFIG_FB_MB862XX is not set
CONFIG_FB_CON_DECOR=y
|
And finally and probably most important: the v86d helper application -- although recompiled after my kernel update -- segfaults: | Code: | 0.279284] v86d[1082]: segfault at fffffffc ip 0804899b sp bfd483e0 error 6 in v86d[8048000+4000]
[ 5.278119] uvesafb: Getting VBE info block failed (eax=0x4f00, err=1)
[ 5.278255] uvesafb: vbe_init() failed with -22
[ 5.278395] uvesafb: probe of uvesafb.0 failed with error -22
|
What could that be?
Thanks
gw |
|
| Back to top |
|
|
szczerb
Veteran
Joined: 24 Feb 2007
Posts: 1709
Location: Poland => Lodz
|
| Posted: Wed May 27, 2009 2:12 pm Post subject: |
|
|
| Why do you have to use the v86d? What gfx card? Why do you have both vesa and uvesa built? |
|
| Back to top |
|
|
pigeon768
l33t
Joined: 02 Jan 2006
Posts: 683
|
| Posted: Wed May 27, 2009 4:28 pm Post subject: |
|
|
| szczerb wrote: | | Why do you have to use the v86d? |
v86d is required for uvesafb.
gw: I'd recommend disabling vesafb and reinstalling v86d and klibc, then re-compiling your kernel. |
|
| Back to top |
|
|
szczerb
Veteran
Joined: 24 Feb 2007
Posts: 1709
Location: Poland => Lodz
|
| Posted: Wed May 27, 2009 5:55 pm Post subject: |
|
|
| pigeon768 wrote: | | szczerb wrote: | | Why do you have to use the v86d? |
v86d is required for uvesafb. |
No it's not. I was using uvesa with a couple video cards without it. Didn't have any problems - or the need for an initrd. |
|
| Back to top |
|
|
pigeon768
l33t
Joined: 02 Jan 2006
Posts: 683
|
| Posted: Wed May 27, 2009 6:35 pm Post subject: |
|
|
IIRC, v86d was, at one time, built into the kernel. Now it's been moved to userspace. | Code: | ~ # head -n 26 /usr/src/linux/Documentation/fb/uvesafb.txt
uvesafb - A Generic Driver for VBE2+ compliant video cards
==========================================================
1. Requirements
---------------
uvesafb should work with any video card that has a Video BIOS compliant
with the VBE 2.0 standard.
Unlike other drivers, uvesafb makes use of a userspace helper called
v86d. v86d is used to run the x86 Video BIOS code in a simulated and
controlled environment. This allows uvesafb to function on arches other
than x86. Check the v86d documentation for a list of currently supported
arches.
v86d source code can be downloaded from the following website:
http://dev.gentoo.org/~spock/projects/uvesafb
Please refer to the v86d documentation for detailed configuration and
installation instructions.
Note that the v86d userspace helper has to be available at all times in
order for uvesafb to work properly. If you want to use uvesafb during
early boot, you will have to include v86d into an initramfs image, and
either compile it into the kernel or use it as an initrd. |
|
|
| Back to top |
|
|
gw
Apprentice
Joined: 03 Dec 2006
Posts: 215
|
| Posted: Thu May 28, 2009 7:48 pm Post subject: |
|
|
Thanks to all, especially pigeon768, I wasn't aware of the klibc thing!
One thing though which took me another two hours or so of wasted time: you certainly want to disable distcc when trying to compile klibc; compile fails invariably with distcc enabled!
Thanks
gw |
|
| Back to top |
|
|
|
Kernel & Hardware
