Comment 22 for bug 246269

Hi Leann,

Thanks for this post. After updating to kernel 2.6.27-1,After bootup, I'm having the following problems :

boomer@boomer-laptop:~$ dmesg | grep uvesa
[ 0.000000] Kernel command line: root=UUID=c48d6261-5fb3-45fd-9cec-ade1e3816556 ro video=uvesafb:800x600-16,mtrr:3,ywrap
[ 1.897079] uvesafb: Unknown parameter `mode'
[ 6.976027] uvesafb: Getting VBE info block failed (eax=0x4f00, err=1)
[ 6.976109] uvesafb: vbe_init() failed with -22
[ 6.976263] uvesafb: probe of uvesafb.0 failed with error -22

More weird, lsmod | grep uvesafb says the module is loaded, but
boomer@boomer-laptop:~$ less /sys/bus/platform/drivers/uvesafb/uvesafb.0/vbe_modes
/sys/bus/platform/drivers/uvesafb/uvesafb.0/vbe_modes: No such file or directory

Re-loading the uvesafb using the 'mode' parameter doesn't work neither :
root@boomer-laptop:/home/boomer# modprobe -r uvesafb
root@boomer-laptop:/home/boomer# modprobe uvesafb mode=1024x768-32 mtrr=3 scroll=ywrap
FATAL: Error inserting uvesafb (/lib/modules/2.6.27-1-generic/initrd/uvesafb.ko): Unknown symbol in module, or unknown parameter (see dmesg)

So, I wonder if anything is wrong with my uvesafb version (I don't know how to figure it) as 'mode' the parameter seems to never work when used in kernel command line bootup options, nor in modprobe reload options.

However, re-loading uvesafb without 'mode' parameter (with modprobe) seems to work fine and the supported mode can now be printed as in :
boomer@boomer-laptop:~$ cat /sys/bus/platform/drivers/uvesafb/uvesafb.0/vbe_modes
...
800x600-8, 0x0103
1024x768-8, 0x0105
320x200-16, 0x010e
320x200-32, 0x010f
640x480-16, 0x0111
640x480-32, 0x0112
800x600-16, 0x0114
800x600-32, 0x0115
1024x768-16, 0x0117
1024x768-32, 0x0118
...

Does anyone have a clue why 'mode' parameter is reported 'unknown' now?