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

[Bogdan Butnaru]

@captn: Strange: I tried the exact same parameters you gave, and I
receive this error:

[   14.298314] uvesafb: Unknown parameter `mttr'

Any idea why that'd be missing? I don't think I ever saw a help file
that mentioned it mightn't exist.

I tried removing that parameter and modprobeing the module myself. This
took me to 1024x768 instead of the mode I wanted. fbset doesn't seem to
know how to set the mode, either.

$ dmesg | tail
[  558.888174] CPU1 attaching sched-domain:
[  558.888178]  domain 0: span 0-1 level MC
[  558.888183]   groups: 1 0
[ 1021.792123] uvesafb: Intel Corporation, Intel(r) 82945GM Chipset Family Graphics Controller, Hardware Version 0.0, OEM: Intel(r) 82945GM Chipset Family Graphics Chip Accelerated VGA BIOS, VBE v3.0
[ 1021.805758] uvesafb: VBIOS/hardware supports DDC2 transfers
[ 1021.818305] uvesafb: monitor limits: vf = 60 Hz, hf = 49 kHz, clk = 68 MHz
[ 1021.827251] uvesafb: scrolling: redraw
[ 1022.267697] Console: switching to colour frame buffer device 128x48
[ 1022.272493] uvesafb: framebuffer at 0xd0000000, mapped to 0xf9200000, using 6144k, total 7872k
[ 1022.272497] fb0: VESA VGA frame buffer device

$ fbset -i
mode "1024x768-60"
    # D: 64.033 MHz, H: 47.714 kHz, V: 60.018 Hz
    geometry 1024 768 1024 768 32
    timings 15617 159 52 23 1 107 3
    vsync high
    rgba 8/16,8/8,8/0,8/24
endmode

Frame buffer device information:
    Name        : VESA VGA
    Address     : 0xd0000000
    Size        : 6291456
    Type        : PACKED PIXELS
    Visual      : TRUECOLOR
    XPanStep    : 0
    YPanStep    : 0
    YWrapStep   : 0
    LineLength  : 4096
    Accelerator : No

$ sudo fbset -xres 1280 -yres 800
Linux Frame Buffer Device Configuration Version 2.1 (23/06/1999)
(C) Copyright 1995-1999 by Geert Uytterhoeven

Opening frame buffer device `/dev/fb0'
Using current video mode from `/dev/fb0'
Setting video mode to `/dev/fb0'
ioctl FBIOPUT_VSCREENINFO: Invalid argument

-- 
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.