[Bug 246269] Re: Switched from vesafb to uvesafb, but uvesafb can't work without v86d

[excogitation]

on an Acer Travelmate TM8106wlmi

~# lsb_release -rd
Description:	Ubuntu intrepid (development branch)
Release:	8.10

~# uname -a
Linux bored 2.6.27-2-generic #1 SMP Thu Aug 28 17:20:02 UTC 2008 i686 GNU/Linux

~# lsmod | grep uvesafb
uvesafb                34788  0 
cn                     15776  1 uvesafb

~# dmesg | grep vesa
[    2.472002] uvesafb: Getting VBE info block failed (eax=0x4f00, err=-3)
[    2.472002] uvesafb: vbe_init() failed with -22
[    2.472002] uvesafb: probe of uvesafb.0 failed with error -22

~# whereis v86d
v86d: /sbin/v86d /usr/share/man/man8/v86d.8.gz

~# ls /sys/bus/platform/drivers/uvesafb/
bind  uevent  unbind  v86d

~# sudo modprobe -r uvesafb
~# sudo modprobe uvesafb mode=1280x800-32
FATAL: Error inserting uvesafb (/lib/modules/2.6.27-2-generic/initrd/uvesafb.ko): Unknown symbol in module, or unknown parameter (see dmesg)
~# cat /sys/bus/platform/drivers/uvesafb/uvesafb.0/vbe_modes
cat: /sys/bus/platform/drivers/uvesafb/uvesafb.0/vbe_modes: No such file or directory
[ 1706.062122] uvesafb: Unknown parameter `mode'

~# sudo modprobe uvesafb 
root at bored:~# cat /sys/bus/platform/drivers/uvesafb/uvesafb.0/vbe_modes
640x400-8, 0x0100
640x480-8, 0x0101
800x600-8, 0x0103
1024x768-8, 0x0105
1280x1024-8, 0x0107
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
1280x1024-15, 0x0119
1280x1024-16, 0x011a
1280x1024-32, 0x011b
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
1152x864-8, 0x0153
1152x864-15, 0x0154
1152x864-16, 0x0155
1152x864-32, 0x0156
1280x1024-8, 0x0163
1280x1024-15, 0x0164
1280x1024-16, 0x0165
1280x1024-32, 0x0166
640x480-32, 0x0121
800x600-32, 0x0122
1024x768-32, 0x0123
1280x1024-32, 0x0124
1400x1050-8, 0x0143
1400x1050-15, 0x0144
1400x1050-16, 0x0145
1400x1050-32, 0x0146
640x400-8, 0x0183
640x400-15, 0x0184
640x400-16, 0x0185
640x400-32, 0x0186

[ 1845.056513] uvesafb: (C) 1988-2005, ATI Technologies Inc. M26-P01.00, M26-P01.00, 01.00, OEM: ATI ATOMBIOS(C) 1988-2005, ATI Technologies Inc. M26-P01.00, VBE v3.0
[ 1845.074888] uvesafb: protected mode interface info at c000:adce
[ 1845.074894] uvesafb: pmi: set display start = c00cae5c, set palette = c00cae9c
[ 1845.261580] uvesafb: VBIOS/hardware supports DDC2 transfers
[ 1845.394236] uvesafb: monitor limits: vf = 61 Hz, hf = 65 kHz, clk = 121 MHz
[ 1845.394674] uvesafb: scrolling: ypan using protected mode interface, yres_virtual=9187
[ 1845.399671] uvesafb: framebuffer at 0xd0000000, mapped to 0xf9000000, using 11484k, total 16384k

-- 
Switched from vesafb to uvesafb, but uvesafb can't work without v86d
https://bugs.launchpad.net/bugs/246269
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux-meta in ubuntu.