UVesaFB - The Successor to VesaFB-TNG (Bootsplash)

Message

ronmon · Post by **ronmon** » Thu Nov 29, 2007 1:09 pm

Thanks, musv.

I checked that out and tried a few experiments. "hwinfo --vbe" showed some promising info:

Mode 0x0345: 1600x1200 (+1600), 8 bits
Mode 0x0346: 1600x1200 (+3200), 16 bits

No joy, though. Oh well.

eMxyzptlk · Post by **eMxyzptlk** » Tue Dec 04, 2007 3:21 pm

Hello,

I have the same problem as justcme, I get the same error trying to boot 2.6.23-tuxonice-r4

Code: Select all

uvesafb: Getting VBE info block failed (eax=0x4f00, err=1) 
uvesafb: vbe_init() failed with -22 
uvesafb: probe of uvesafb.0 failed with error -22

I have intel 945GM, anyway to solve this problem?
Thx

Zoboulo · Post by **Zoboulo** » Tue Dec 04, 2007 5:56 pm

@eMxyzptlk : is CONFIG_VM86 set to Y in your .config ? I had the same problem and it helped for me.

gerardo · Post by **gerardo** » Tue Dec 04, 2007 7:45 pm

wxqc11h wrote:i cannot build klibc (x86_64)

defconfig has changed, please remove or edit .config
make: *** [.config] Błąd 1
*
* ERROR: dev-libs/klibc-1.5.7-r2 failed.
* Call stack:
* ebuild.sh, line 1701: Called dyn_compile
* ebuild.sh, line 1039: Called qa_call 'src_compile'
* ebuild.sh, line 44: Called src_compile
* klibc-1.5.7-r2.ebuild, line 143: Called die
* The specific snippet of code:
* emake \
* EXTRA_KLIBCAFLAGS="-Wa,--noexecstack" \
* EXTRA_KLIBCLDFLAGS="-z,noexecstack" \
* HOSTCC="${HOSTCC}" CC="${CC}" \
* INSTALLDIR="/usr/${libdir}/klibc" \
* KLIBCARCH=${KLIBCARCH} \
* KLIBCASMARCH=${KLIBCASMARCH} \
* SHLIBDIR="/${libdir}" \
* libdir="/usr/${libdir}" \
* mandir="/usr/share/man" \
* ${myargs} || die "Compile failed!"
* The die message:
* Compile failed!
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/mnt/zbiornik/.portos/tmp/portage/dev-libs/klibc-1.5.7-r2/temp/build.log'.
*
do you have any ideas ?
defconfig has changed, please remove or edit .config ????

If you are using Reiser4 that's the problem.
Solution is in this bug

gerardo · Post by **gerardo** » Tue Dec 04, 2007 9:28 pm

I can't seem to get this working.
It always takes on a resolution of 640x480-8

What's wrong?

I find something strange in dmesg:

Code: Select all

sysctl table check failed: /kernel/fbcondecor .1.77 Unknown sysctl binary path
Pid: 1, comm: swapper Not tainted 2.6.24-rc3-zen4 #1

Call Trace:
 [<ffffffff8024ba70>] set_fail+0x3f/0x47
 [<ffffffff8024bf1e>] sysctl_check_table+0x4a6/0x4f3
 [<ffffffff8024ba22>] sysctl_check_lookup+0xc1/0xd0
 [<ffffffff8024bf34>] sysctl_check_table+0x4bc/0x4f3
 [<ffffffff805ccbc0>] sysctl_init+0x1e/0x22
 [<ffffffff805be636>] kernel_init+0x171/0x2dd
 [<ffffffff8048c11a>] _spin_unlock_irq+0x15/0x30
 [<ffffffff8022ffb3>] finish_task_switch+0x2b/0xc2
 [<ffffffff8020cde8>] child_rip+0xa/0x12
 [<ffffffff805be4c5>] kernel_init+0x0/0x2dd
 [<ffffffff8020cdde>] child_rip+0x0/0x12
...
Linux agpgart interface v0.102
uvesafb: NVIDIA Corporation, G73 Board - p501h0  , Chip Rev   , OEM: NVIDIA, VBE v3.0
uvesafb: VBIOS/hardware doesn't support DDC transfers
uvesafb: no monitor limits have been set, default refresh rate will be used
uvesafb: scrolling: redraw
Console: switching to colour frame buffer device 80x30
uvesafb: framebuffer at 0xd0000000, mapped to 0xffffc20010100000, using 10240k, total 262144k
fb0: VESA VGA frame buffer device
vga16fb: initializing
vga16fb: mapped to 0xffff8100000a0000
fb1: VGA16 VGA frame buffer device

Note: the vga16fb has nothing to do with it. It doesn't make a difference...

Here's my grub-section: (I tried with or without the initrd and with 1280x1024-16)

Code: Select all

title=Gentoo Linux (2.6.24-rc3-zen4)
root (hd0,2)
kernel /kernel-genkernel-x86_64-2.6.24-rc3-zen4 real_root=/dev/sda6 irqpoll udev video=uvesafb:1280x1024-32:mtrr:3,ywrap splash=silent,theme:gentoo-burn CONSOLE=/dev/tty1 quiet fbcon=scrollback:128K
initrd /initramfs-genkernel-x86_64-2.6.24-rc3-zen4

# cat /sys/devices/platform/uvesafb.0/vbe_modes

Code: Select all

640x400-8, 0x0100
640x480-8, 0x0101
800x600-8, 0x0103
1024x768-8, 0x0105
1280x1024-8, 0x0107
320x200-16, 0x010e
320x200-32, 0x010f
640x480-16, 0x0111
640x480-32, 0x0112
800x600-16, 0x0114
800x600-32, 0x0115
1024x768-16, 0x0117
1024x768-32, 0x0118
1280x1024-16, 0x011a
1280x1024-32, 0x011b
320x200-8, 0x0130
320x400-8, 0x0131
320x400-16, 0x0132
320x400-32, 0x0133
320x240-8, 0x0134
320x240-16, 0x0135
320x240-32, 0x0136
640x400-16, 0x013d
640x400-32, 0x013e

I recompiled kernel, splash-utils (with the fbcondecor use-flag) and klibc already several times...
I never had problems without the uvesafb (using the regular vesa-driver) in previous kernel versions

And to avoid a too long post here: here's my emerge --info (that bug has nothing to do with it)

eMxyzptlk · Post by **eMxyzptlk** » Tue Dec 04, 2007 10:44 pm

Engywuck wrote:@eMxyzptlk : is CONFIG_VM86 set to Y in your .config ? I had the same problem and it helped for me.

Yes it is set

Code: Select all

$ grep CONFIG_VM86 /usr/src/linux/.config
CONFIG_VM86=y
$ grep UVESA /usr/src/linux/.config
CONFIG_FB_UVESA=y

I haven't posted much info in the first post so I'll add more details now:

menu.lst

Code: Select all

title=Gentoo Linux (2.6.23-tuxonice-r4)
root (hd0,0)
kernel (hd0,0)/kernel-genkernel-x86-2.6.23-tuxonice-r4 dolvm crypt_root=/dev/sda2 lvm2root=/dev/mapper/root real_root=/dev/system/slash video=uvesafb:ywrap,mtrr:3,1024x768-32 splash=silent,theme:KillBillTux-Grey fbcon=scrollback:128k console=tty1 resume2=swap:/dev/system/swap quiet
initrd (hd0,0)/initramfs-genkernel-x86-2.6.23-tuxonice-r4

Code: Select all

$ grep OVERLAY /etc/genkernel.conf
CMD_INITRAMFS_OVERLAY=/usr/share/v86d

* Which is the same as running : genkernel --initramfs-overlay=/usr/share/v86d

Code: Select all

$ cat /proc/fb0/modes
1280x800-8
1280x800-16
1280x800-32
1024x768-8
1024x768-16
1024x768-32
640x480-32
800x600-16
800x600-32
640x480-8
800x600-8
640x480-16

I'm stuck with 2.6.22 kernels untill I get this fixed

Thx

ChristianK92 · Post by **ChristianK92** » Tue Dec 04, 2007 11:13 pm

I upgrade to gentoo-sources 2.6.23 (after emerge --sync).
I follow the instructions given on http://dev.gentoo.org/~spock/projects/uvesafb/
and get a kernel panic

Without initramfs : no kernel panic but i stay in 640x480

gerardo · Post by **gerardo** » Tue Dec 04, 2007 11:24 pm

eMxyzptlk wrote:
Engywuck wrote:@eMxyzptlk : is CONFIG_VM86 set to Y in your .config ? I had the same problem and it helped for me.
Yes it is set

Where can I find it?
I don't have that.

CloudBolt · Post by **CloudBolt** » Thu Dec 06, 2007 9:05 pm

ChristianK92 wrote:I upgrade to gentoo-sources 2.6.23 (after emerge --sync).
I follow the instructions given on http://dev.gentoo.org/~spock/projects/uvesafb/
and get a kernel panic

Without initramfs : no kernel panic but i stay in 640x480

Yeah, same here. I followed the steps on spock's site, double checked everything, but I am still getting the kernel panic. It wouldn't be an incompatibility problem with the intel i810 would it?

tld · Post by **tld** » Thu Dec 06, 2007 9:41 pm

For my own purposes, I really didn't need anything more than a standard vesafb 1024X768, and I currently don't use initrd, so I just did without uvesafb and vesafb-tng and replaced my video line with vga=0x318. I guess if I find I need more I'll screw around with the initramfs etc.

Tom

ChristianK92 · Post by **ChristianK92** » Thu Dec 06, 2007 9:41 pm

CloudBolt wrote:
ChristianK92 wrote:I upgrade to gentoo-sources 2.6.23 (after emerge --sync).
I follow the instructions given on http://dev.gentoo.org/~spock/projects/uvesafb/
and get a kernel panic

Without initramfs : no kernel panic but i stay in 640x480
Yeah, same here. I followed the steps on spock's site, double checked everything, but I am still getting the kernel panic. It wouldn't be an incompatibility problem with the intel i810 would it?

I have not a intel i810 nut a nVidia 8800 GTS.

CloudBolt · Post by **CloudBolt** » Sat Dec 08, 2007 1:32 pm

ChristianK92 wrote:
CloudBolt wrote:
ChristianK92 wrote:I upgrade to gentoo-sources 2.6.23 (after emerge --sync).
I follow the instructions given on http://dev.gentoo.org/~spock/projects/uvesafb/
and get a kernel panic

Without initramfs : no kernel panic but i stay in 640x480
Yeah, same here. I followed the steps on spock's site, double checked everything, but I am still getting the kernel panic. It wouldn't be an incompatibility problem with the intel i810 would it?
I have not a intel i810 nut a nVidia 8800 GTS.

hmm I've tried compiling uvesafb as a module and modprobing it, but that gave the same segmentation fault. the only difference was it didn't crash my kernel because it was a module.

mijenix · Post by **mijenix** » Sat Dec 08, 2007 6:04 pm

Hi

uvesafb works but with a resolution 1400x1050-32 I've some problems.
During the boot the resolution works without any probems.
But when I switch from x.org to the console I get some display failures.
With 1280x1024 I don't get this display problems.

video=uvesafb:1400x1050-32,mtrr:3,ywrap

Any ideas what can be the problem? I've a ATI X1300 graphics card.

Neo2 · Post by **Neo2** » Sat Dec 08, 2007 7:47 pm

gerardo wrote:I can't seem to get this working.
It always takes on a resolution of 640x480-8

What's wrong?

I find something strange in dmesg:

Code: Select all

sysctl table check failed: /kernel/fbcondecor .1.77 Unknown sysctl binary path
Pid: 1, comm: swapper Not tainted 2.6.24-rc3-zen4 #1

Call Trace:
 [<ffffffff8024ba70>] set_fail+0x3f/0x47
 [<ffffffff8024bf1e>] sysctl_check_table+0x4a6/0x4f3
 [<ffffffff8024ba22>] sysctl_check_lookup+0xc1/0xd0
 [<ffffffff8024bf34>] sysctl_check_table+0x4bc/0x4f3
 [<ffffffff805ccbc0>] sysctl_init+0x1e/0x22
 [<ffffffff805be636>] kernel_init+0x171/0x2dd
 [<ffffffff8048c11a>] _spin_unlock_irq+0x15/0x30
 [<ffffffff8022ffb3>] finish_task_switch+0x2b/0xc2
 [<ffffffff8020cde8>] child_rip+0xa/0x12
 [<ffffffff805be4c5>] kernel_init+0x0/0x2dd
 [<ffffffff8020cdde>] child_rip+0x0/0x12
...
Linux agpgart interface v0.102
uvesafb: NVIDIA Corporation, G73 Board - p501h0  , Chip Rev   , OEM: NVIDIA, VBE v3.0
uvesafb: VBIOS/hardware doesn't support DDC transfers
uvesafb: no monitor limits have been set, default refresh rate will be used
uvesafb: scrolling: redraw
Console: switching to colour frame buffer device 80x30
uvesafb: framebuffer at 0xd0000000, mapped to 0xffffc20010100000, using 10240k, total 262144k
fb0: VESA VGA frame buffer device
vga16fb: initializing
vga16fb: mapped to 0xffff8100000a0000
fb1: VGA16 VGA frame buffer device

Note: the vga16fb has nothing to do with it. It doesn't make a difference...

Here's my grub-section: (I tried with or without the initrd and with 1280x1024-16)

Code: Select all

...
kernel /kernel-genkernel-x86_64-2.6.24-rc3-zen4 real_root=/dev/sda6 irqpoll udev video=uvesafb:1280x1024-32:mtrr:3,ywrap splash=silent,theme:gentoo-burn CONSOLE=/dev/tty1 quiet fbcon=scrollback:128K
...

There's a typo in your kernel line. Arguments to video should look like:

Code: Select all

video=uvesafb:1280x1024-32,mtrr:4,ywrap,ypan

Note the comma between "1280x0124-32" and "mtrr:4", yours is a colon. The problem shown by your dmesg log may be related to miscompiled klibc/v86d or v86d initramfs not included in the kernel (if you compiled uvesafb in-kernel) or v86d not starting at bootup (if you compiled uvesafb as a module). Also, be sure that the two options below are enabled on your kernel and that your /usr/src/linux symlink points to the correct location (klibc should be built against a kernel that has uvesafb support, and if your symlink points to an older kernel you may get a miscompiled version of klibc).

Code: Select all

# configure the kernel; in the "Device Drivers" section select:
Connector - unified userspace <-> kernelspace linker and
Graphics support ---> Userspace VESA VGA graphics support
(that's CONFIG_CONNECTOR=y and CONFIG_FB_UVESA=y)
# reconfigure your kernel; in the "General Setup" section select:
Initial RAM filesystem and RAM disk (initramfs/initrd) support
and use /usr/share/v86d/initramfs in Initramfs source file(s).
(that's CONFIG_INITRAMFS_SOURCE="/usr/share/v86d/initramfs")

For problems when switching from X to console or viceversa, this may be related to mtrr settings. Sometimes framebuffer devices allocate mtrr resources that later 2d/3d graphic drivers tend to allocate. I'm not an expert but from my experience I can tell that sometimes mtrrs just work fine with graphic drivers and sometimes they simply do not. I have an x1900xt with ati drivers+uvesafb that doesn't show any problems. Instead my laptop has an ATI mobility graphics card with mach3d chipset, I can't use the mtrrs both with framebuffer and graphics because I'd lose accelerated 3d rendering. Usually you can choose between enabling mtrrs for framebuffer (thus faster scrolling) and lose direct rendering in X, or pass the "nomtrr" option to the framebuffer at boot and keep a slower scrolling in console mode but keeping direct rendering in X. There can also be the much more complicated case where mtrrs with fb (framebuffer) work fine and booting up X works fine as well and you get direct rendering, whereas when shutting down the system freezes/lock/you get a blank screen. This was documented on older ATI drivers (and hopefully from what I understand it has been solved). Hope to have helped someone

gundelgauk · Post by **gundelgauk** » Sat Dec 08, 2007 7:51 pm

Well for me vesafb-tng used to work great with my Mobility Radeon X700. The native widescreen resolution of 1280x800 worked, switching from X to console and back worked. It was great.

However I have compiled gentoo-sources-2.6.23-r6 yesterday and I can't get uvesafb to work at all. I've followed the instructions on spock's devsite but regardless of what settings I try to use, I only get the default resolution.

Some information:

Code: Select all

$ dmesg | grep vesa
Kernel command line: root=/dev/sda1 rootdelay=6 video=uvesafb:1024x768-16@60,mtrr:3,ywrap
uvesafb: (C) 1988-2003, ATI Technologies Inc. M26-P01.00, M26-P01.00, 01.00, OEM: ATI ATOMBIOS(C) 1988-2003, ATI Technologies Inc. M26-P01.00, VBE v3.0
uvesafb: protected mode interface info at c000:ae6c
uvesafb: pmi: set display start = c00caefa, set palette = c00caf3a
uvesafb: VBIOS/hardware supports DDC2 transfers
uvesafb: monitor limits: vf = 60 Hz, hf = 49 kHz, clk = 68 MHz
uvesafb: scrolling: ywrap using protected mode interface, yres_virtual=1536
uvesafb: framebuffer at 0xc0000000, mapped to 0xf8880000, using 6144k, total 16384k

I don't think there's any error in there. Note that I have also tried different resolutions and color depths than in the above kernel command line but none seem to have any effect.

If I try to use the screen's native resolution (1280x800) I get some error about unsupported video clock in dmesg. I don't have the exact error message available at the moment but I can reproduce it if you think it's of any help. I guess this is why:

Code: Select all

# cat /sys/bus/platform/drivers/uvesafb/uvesafb.0/vbe_modes
640x400-8, 0x0100
640x480-8, 0x0101
800x600-8, 0x0103
1024x768-8, 0x0105
640x480-15, 0x0110
640x480-16, 0x0111
640x480-32, 0x0112
800x600-15, 0x0113
800x600-16, 0x0114
800x600-32, 0x0115
1024x768-15, 0x0116
1024x768-16, 0x0117
1024x768-32, 0x0118
320x200-15, 0x010d
320x200-16, 0x010e
320x200-32, 0x010f
320x200-32, 0x0120
320x240-8, 0x0193
320x240-15, 0x0194
320x240-16, 0x0195
320x240-32, 0x0196
512x384-8, 0x01b3
512x384-15, 0x01b4
512x384-16, 0x01b5
512x384-32, 0x01b6
640x350-8, 0x01c3
640x350-15, 0x01c4
640x350-16, 0x01c5
640x350-32, 0x01c6
640x400-8, 0x0183
640x400-15, 0x0184
640x400-16, 0x0185
640x400-32, 0x0186
720x400-8, 0x0133
720x400-15, 0x0134
720x400-16, 0x0135
720x400-32, 0x0136
640x480-32, 0x0121
800x600-32, 0x0122
1024x768-32, 0x0123
640x400-8, 0x0183
640x400-15, 0x0184
640x400-16, 0x0185
640x400-32, 0x0186

The resolution I tried above is actually in there. The sad thing however is, that the highest resolution I would be able to get is 1024x768. So, no native resolution. If it worked at all, that is.

So the way it looks now, uvesafb is a huge step back for me.

Does anyone have some ideas for me, what I could try? Unfortunately I'm out of ideas.

Neo2 · Post by **Neo2** » Sun Dec 09, 2007 9:17 am

I've read doc file /usr/src/linux/Documentation/fb/uvesafb.txt and it seems that the XxY-bit@Hz option doesn't work anymore with uvesafb. This is what documentation says:

Code: Select all

Additionally, the following parameters may be provided.  They all override the
EDID-provided values and BIOS defaults.  Refer to your monitor's specs to get
the correct values for maxhf, maxvf and maxclk for your hardware.

maxhf:n     Maximum horizontal frequency (in kHz).
maxvf:n     Maximum vertical frequency (in Hz).
maxclk:n    Maximum pixel clock (in MHz).

If you want to manually specify refresh rate you should have a line like this one:

Code: Select all

video=uvesafb:1024x768-32,mtrr:3,ywrap,maxvf:60

Anyway, specifing vertical refresh rate should be useless because the framebuffer will try to use the maximum frequency supported by your monitor by default. If I'm right it should be used only if you've got display problems when using framebuffer. If you keep getting default resolution, try to disable vesafb in kernel configuration (deselect "VESA VGA Graphics support" in Device Drivers->Graphics support). I had the very same problem when switching from vesafb to uvesafb on my amd64 machine. Followed the guide step by step, recompiled several times, kernel line in grub.conf was ok, but I kept getting default resolution. Now that I've deleted vesafb from my kernel config uvesafb works perfectly. Please make sure you have a "backup" kernel somewhere, in case uvesafb fails to work, else you'll have blank screen I guess (if you don't have a login manager starting at boot).
If none of the above does work, try to post the error message, it's always better than nothing

gundelgauk · Post by **gundelgauk** » Sun Dec 09, 2007 10:14 am

Thanks for your reply, Neo2!

Ok, vesafb was not set the whole time, I just verified this again:
CONFIG_FB_UVESA=y
# CONFIG_FB_VESA is not set

As for the XxY-bit@Hz format, I should have mentioned that initially I tried settings without the @Hz part as shown on spock's devsite; for example video=uvesafb:1024x768-16,mtrr:3,ywrap. The reason I also tried to add the frequency is that I got that "video clock" error message when setting anything above 1024x768 and I thought this might help. But it seems unconnected. In any case, I just tried again without the frequency, this is the output of dmesg:

Code: Select all

$ dmesg | grep vesa
Kernel command line: root=/dev/sda1 rootdelay=6 video=uvesafb:1024x768-16,mtrr:3,ywrap
uvesafb: (C) 1988-2003, ATI Technologies Inc. M26-P01.00, M26-P01.00, 01.00, OEM: ATI ATOMBIOS(C) 1988-2003, ATI Technologies Inc. M26-P01.00, VBE v3.0
uvesafb: protected mode interface info at c000:ae6c
uvesafb: pmi: set display start = c00caefa, set palette = c00caf3a
uvesafb: VBIOS/hardware supports DDC2 transfers
uvesafb: monitor limits: vf = 60 Hz, hf = 49 kHz, clk = 68 MHz
uvesafb: scrolling: ywrap using protected mode interface, yres_virtual=3072
uvesafb: framebuffer at 0xc0000000, mapped to 0xf8880000, using 6144k, total 16384k

I also tried different settings for mtrr (< 3), including leaving it out altogether. Same for ywrap. This is an example:

Code: Select all

$ dmesg | grep vesa
Kernel command line: root=/dev/sda1 rootdelay=6 video=uvesafb:1280x800-16
uvesafb: (C) 1988-2003, ATI Technologies Inc. M26-P01.00, M26-P01.00, 01.00, OEM: ATI ATOMBIOS(C) 1988-2003, ATI Technologies Inc. M26-P01.00, VBE v3.0
uvesafb: protected mode interface info at c000:ae6c
uvesafb: pmi: set display start = c00caefa, set palette = c00caf3a
uvesafb: VBIOS/hardware supports DDC2 transfers
uvesafb: monitor limits: vf = 60 Hz, hf = 49 kHz, clk = 68 MHz
uvesafb: scrolling: ypan using protected mode interface, yres_virtual=9830
uvesafb: framebuffer at 0xc0000000, mapped to 0xf8880000, using 6144k, total 16384k

What is extremely weird is that I'm not getting the "video clock" error any more, when I'm trying 1280x800 now. So for now I seem to be unable to reproduce it. I even get a /dev/fb0 device, but still only the default resolution.

I also tried playing around with fbset a bit, but whatever I do, the only thing it does is giving me a completely blank screen. I can get my console back if I press enter after a few seconds. However there is no indication that the resolution changes at any point.

Neo2 · Post by **Neo2** » Sun Dec 09, 2007 12:52 pm

Well, that's really weird. I get same dmesg with my uvesafb framebuffer. This is my relevant config info about Graphics support:

Code: Select all

# Graphics support
CONFIG_BACKLIGHT_LCD_SUPPORT=y
CONFIG_LCD_CLASS_DEVICE=m
CONFIG_BACKLIGHT_CLASS_DEVICE=y
CONFIG_BACKLIGHT_PROGEAR=m

# Display device support
CONFIG_DISPLAY_SUPPORT=y

# Display hardware drivers
CONFIG_VGASTATE=m
CONFIG_VIDEO_OUTPUT_CONTROL=m
CONFIG_FB=y
CONFIG_FIRMWARE_EDID=y
CONFIG_FB_DDC=m
CONFIG_FB_CFB_FILLRECT=y
CONFIG_FB_CFB_COPYAREA=y
CONFIG_FB_CFB_IMAGEBLIT=y
CONFIG_FB_SYS_FILLRECT=m
CONFIG_FB_SYS_COPYAREA=m
CONFIG_FB_SYS_IMAGEBLIT=m
CONFIG_FB_SYS_FOPS=m
CONFIG_FB_DEFERRED_IO=y
CONFIG_FB_BACKLIGHT=y
CONFIG_FB_MODE_HELPERS=y

# Frame buffer hardware drivers
CONFIG_FB_VGA16=m
CONFIG_FB_UVESA=y
CONFIG_FB_RADEON=m
CONFIG_FB_RADEON_I2C=y
CONFIG_FB_RADEON_BACKLIGHT=y

# Console display driver support
CONFIG_VGA_CONSOLE=y
CONFIG_VGACON_SOFT_SCROLLBACK=y
CONFIG_VGACON_SOFT_SCROLLBACK_SIZE=256
CONFIG_VIDEO_SELECT=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
CONFIG_FB_CON_DECOR=y
CONFIG_FONTS=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
CONFIG_FONT_6x11=y
CONFIG_FONT_7x14=y
CONFIG_FONT_PEARL_8x8=y
CONFIG_FONT_ACORN_8x8=y
CONFIG_FONT_MINI_4x6=y
CONFIG_FONT_SUN8x16=y
CONFIG_FONT_SUN12x22=y
CONFIG_FONT_10x18=y

See if you can find any help from this, either by directly importing it in your kernel config or by comparing your config to mine. All non-present options are not set.
I don't know any other way to help you except for posting my config. Hope it works

gundelgauk · Post by **gundelgauk** » Sun Dec 09, 2007 10:29 pm

Thanks again, Neo2!

I have compared your .config with mine and apart from the fonts, there were only two or three options I had not selected. Among them CONFIG_BACKLIGHT_LCD_SUPPORT. Still, I tried using the exact same settings but unfortunately with no success.

I guess I will leave it at that until the next version of gentoo-sources comes out or until I find half a day of time again to play around and try things, whichever comes first.

skijmpr · Post by **skijmpr** » Fri Dec 21, 2007 1:27 pm

I started from the Gentoo Wiki HOWTO on gensplash:

http://gentoo-wiki.com/HOWTO_fbsplash

And now I've ended up here. Numerous problems:

-The Gentoo Wiki gensplash page contains NOTHING about uvesafb, despite the fact that vesafb-tng is now defunct, and the current instructions are incorrect for people with kernel versions >=2.6.23 with regards to the framebuffer selection.
-I have followed Spock's instructions verbatim for setting up uvesafb, but run into numerous problems

Here is a description of the problems I am having:

1) When I try to boot with uvesafb, the screen freezes early in the boot process. I have tried the following boot lines to no avail:

a)

Code: Select all

kernel /boot/kernel-2.6.23-gentoo-r3 root=/dev/sda2 video=uvesafb:1024x768-32,ywrap,mtrr:3

b) (also with splash=verbose and without the initrd line)

Code: Select all

kernel /boot/kernel-2.6.23-gentoo-r3 root=/dev/sda2 video=uvesafb:1024x768-32,ywrap,mtrr:3 splash=silent,theme:livecd-2007.0 quiet CONSOLE=/dev/tty1
initrd /boot/fbsplash-livecd-2007.0-1024x768

I followed Spock's uvesafb instructions to a tee.

2) I want to use a splash theme, like livecd-2007.0, to have two things:

a) A pretty looking silent (graphical w/o scrolling text) theme at boot time
b) A nice background on my consoles during and/or after boot

At one point I managed to get (a) working with the old vesafb driver that still remains in the kernel, but I have been unable to make any progress with uvesafb due to problem (1) above.

This is a fresh install of Gentoo on a Dell D820 laptop. I can provide more info if needed. Also, someone with more understanding of this stuff please make updates to the Gentoo Wiki HOWTO gensplash page.

djdunn · Post by **djdunn** » Sun Dec 23, 2007 3:20 am

i am so blind driving myself crazy all night

till i saw that userspace vesa vga grapgics support right above vesa vga grapgics support, im thinkinh ...userspace... DOH! vesafb is not uvesafb

should not try to do this tired or after all that wine for dinner

djdunn · Post by **djdunn** » Sun Dec 23, 2007 4:46 am

im not sure i got this working right any insight would be appriciated

when the computer boots i see grub i make my selection then uvesfb boots i see just a black screen while the kernel innitializes then it switches to my silent splash or whatever you want to call it as soon as it starts moving from 0% to 100% . it aways displayed the silent splash screen as the kernel was innitializing before

on a side note i get this message whn i shutdown -r or reboot

/lib/splash/sys not mounted

then it prompts me for root password to enter maintainence mode

that was strange because it buped me out of silent mode to do it

skypjack · Post by **skypjack** » Thu Dec 27, 2007 11:54 pm

Hi, this is the discussion I'm looking for!
I have an intel 945gm and now I'm using uvesafb with 1024x768 resolution.
Of course, I'd like to use my native 1280x800 but using uvesafb:1280x800-32@60 into my grub.conf drives me to a 640x480 at boot ... I don't know why but it's horrible!! So, 1024x768 it's good, but I'd like to know if it's possible to use my native resolution.
Someone has an idea?

Thanks in advance ...

digitized · Post by **digitized** » Fri Dec 28, 2007 6:53 pm

Hi everyone!
Can you guys which have problems with uvesafb (no mode switch/lockup/black screen) extend your dmesg grep?
for example:

Code: Select all

grep -A2 -B2 vesa /var/log/dmesg

[ 91.131804] Hangcheck: Using get_cycles().
[ 91.132235] v86d[428]: segfault at 0000000000000000 rip 0000000000400da6 rsp 00007fff58f374d0 error 6
[ 91.132420] uvesafb: Getting VBE info block failed (eax=0x4f00, err=-3)
[ 91.132509] uvesafb: vbe_init() failed with -22
[ 91.132597] uvesafb: probe of uvesafb.0 failed with error -22
[ 91.132772] input: Power Button (FF) as /class/input/input0
[ 91.132861] ACPI: Power Button (FF) [PWRF]

I haven't got it to work on my new machines. On my main desktop with 2.6.22-suspend2-r2 and an older version of v86d everything works fine.

gundelgauk · Post by **gundelgauk** » Sat Dec 29, 2007 3:03 pm

Sure, here it is:

Code: Select all

Allocating PCI resources starting at 50000000 (gap: 40000000:a0000000)
Built 1 zonelists in Zone order.  Total pages: 259715
Kernel command line: root=/dev/sda1 rootdelay=6 video=uvesafb:1280x800-16,mtrr:3,ywrap
mapped APIC to ffffb000 (fee00000)
mapped IOAPIC to ffffa000 (fec00000)
--
Hangcheck: starting hangcheck timer 0.9.0 (tick is 180 seconds, margin is 60 seconds).
Hangcheck: Using get_cycles().
uvesafb: (C) 1988-2003, ATI Technologies Inc. M26-P01.00, M26-P01.00, 01.00, OEM: ATI ATOMBIOS(C) 1988-2003, ATI Technologies Inc. M26-P01.00, VBE v3.0
uvesafb: protected mode interface info at c000:ae6c
uvesafb: pmi: set display start = c00caefa, set palette = c00caf3a
uvesafb: VBIOS/hardware supports DDC2 transfers
uvesafb: monitor limits: vf = 60 Hz, hf = 49 kHz, clk = 68 MHz
uvesafb: scrolling: ywrap using protected mode interface, yres_virtual=9830
uvesafb: mode switch failed (eax=0x34f, err=0). Trying again with default timings.
uvesafb: mode switch failed (eax=0x34f, err=0). Trying again with default timings.
Switched to high resolution mode on CPU 0
Console: switching to colour frame buffer device 80x30
uvesafb: mode switch failed (eax=0x34f, err=0). Trying again with default timings.
uvesafb: framebuffer at 0xc0000000, mapped to 0xf8880000, using 6144k, total 16384k
fb0: VESA VGA frame buffer device
ACPI: AC Adapter [ACAD] (on-line)

(1280x800 is the screen's native resolution)

What is very strange, now resolutions up to 1024x768 seem to be working for me, I can even change to 800x600 and back again using fbset. I also get the two mode switch failed lines in dmesg but despite that, the mode gets changed. I have not been fiddling with uvesafb since my last post in this thread and I can't even guess what might have changed. The kernel version is still the same, only some kernel headers got pulled in by emerge -uD world some time ago.

I'm quite puzzled.

UVesaFB - The Successor to VesaFB-TNG (Bootsplash)

Re: [Fixed but not Solved] UVesaFB woes :(

Kernel panic with uvesafb

Re: Kernel panic with uvesafb

Re: Kernel panic with uvesafb

Re: Kernel panic with uvesafb

uvesafb not working