[Bug 246269] Re: Switched from vesafb to uvesafb, but uvesafb can't work without v86d
Fahim
f.abdun.nur at gmail.com
Fri Aug 29 10:32:16 UTC 2008
Yep, seems like it worked even better on my work PC:
before:
[ 3.668437] uvesafb: Getting VBE info block failed (eax=0x4f00, err=-3)
[ 3.668437] uvesafb: vbe_init() failed with -22
[ 3.668437] uvesafb: probe of uvesafb.0 failed with error -22
after:
[ 3.780626] uvesafb: Intel Corporation, Intel(r)Q33/Q35/G33 Graphics Controller, Hardware Version 0.0, OEM: Intel(r)Q33/Q35/G33 Gr
aphics Chip Accelerated VGA BIOS, VBE v3.0
[ 3.780627] uvesafb: VBIOS/hardware supports DDC2 transfers
[ 3.810626] uvesafb: monitor limits: vf = 75 Hz, hf = 83 kHz, clk = 150 MHz
[ 3.810626] uvesafb: scrolling: redraw
[ 3.812880] uvesafb: framebuffer at 0xd0000000, mapped to 0xf8880000, using 8128k, total 8128k
--
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.
More information about the kernel-bugs
mailing list