fbxine is causing "Video port failed"

Dmitry Katsubo <[email protected]> Sat, 09 Mar 2013 19:03:49 +0100
Newsgroups gmane.comp.video.xine.user
Message-ID <[email protected]>
Dear Xine users,

I am trying to launch Xine on FrameBuffer, and I am suffering from the
following problem:

When I am trying to start fbxine it literally shows the following:

centurion:~$ fbxine /mnt/video/film.avi
centurion:~$ iled.

After strace'ing it, I got the following result:

ioctl(4, FBIOPUT_VSCREENINFO, 0x98e04b4) = -1 EINVAL (Invalid argument)
ioctl(4, FBIOPUT_VSCREENINFO, 0x98e04b4) = -1 EINVAL (Invalid argument)
ioctl(4, FBIOPUT_VSCREENINFO, 0x98e04b4) = 0
ioctl(4, FBIOGET_VSCREENINFO, 0x98e04b4) = 0
ioctl(4, FBIOGET_FSCREENINFO, 0x98e0554) = 0
ioctl(4, FBIOPUTCMAP, 0xbfa392c8)       = -1 EINVAL (Invalid argument)
write(2, "Video port failed.\n", 19Video port failed.
)    = 19

and when I have compared this trace with video_out_fb.c sources, I come
to conclusion that set_fb_palette() is failing
(https://github.com/Raider05/enigma2pc/blob/master/xine-lib/src/video_out/video_out_fb.c#L776).

Any ideas how can I overcome this problem?

Additional information:

=== uname -a ===
Linux centurion 3.2.0-4-686-pae #1 SMP Debian 3.2.35-2 i686 GNU/Linux

=== fbset -i ===
mode "1024x768"
    geometry 1024 768 1024 768 32
    timings 0 0 0 0 0 0 0
    accel true
    rgba 8/16,8/8,8/0,8/24
endmode

Frame buffer device information:
    Name        : inteldrmfb
    Address     : 0xd0020000
    Size        : 3145728
    Type        : PACKED PIXELS
    Visual      : TRUECOLOR
    XPanStep    : 1
    YPanStep    : 1
    YWrapStep   : 0
    LineLength  : 4096
    Accelerator : No

--
With best regards,
Dmitry

------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester  
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the  
endpoint security space. For insight on selecting the right partner to 
tackle endpoint security challenges, access the full report. 
http://p.sf.net/sfu/symantec-dev2dev