Comment 13 for bug 246269

Revision history for this message
Michael Sotnikov (stari4ek) wrote :

one more experiment:

after clean boot I see uvesafb as loaded module (lsmod), but it doesn't work: I have no /sys/bus/platform/drivers/uvesafb/uvesafb.0 and /sys/class/graphics/fb0, and all terminals have usual text mode (40x25 or like that)

I can reload uvesafb:
$ sudo modprobe -r uvesafb
$ sudo modprobe uvesafb mode=1280x800-32

got it:
$ dmesg | tail
[ 225.876067] uvesafb: NVIDIA Corporation, G86 Board - e415h01 , Chip Rev , OEM: NVIDIA, VBE v3.0
[ 225.930869] uvesafb: protected mode interface info at c000:b7e0
[ 225.930869] uvesafb: pmi: set display start = c00cb843, set palette = c00cb89e
[ 225.930869] uvesafb: pmi: ports = 3b4 3b5 3ba 3c0 3c1 3c4 3c5 3c6 3c7 3c8 3c9 3cc 3ce 3cf 3d0 3d1 3d2 3d3 3d4 3d5 3da
[ 225.999969] uvesafb: VBIOS/hardware doesn't support DDC transfers
[ 225.999969] uvesafb: no monitor limits have been set, default refresh rate will be used
[ 225.999980] uvesafb: scrolling: ypan using protected mode interface, yres_virtual=1600
[ 226.003950] Console: switching to colour frame buffer device 160x50
[ 226.003950] uvesafb: framebuffer at 0xcd000000, mapped to 0xfba00000, using 8000k, total 14336k
[ 226.003950] fb0: VESA VGA frame buffer device

and it looks like module start working (stuff in /sys/bus, /sys/class mentioned before) but terminals become totally blank (no login prompt, no blinking cursor. no reaction on keyboard input)