6 replies to this topic

[pietjepuk]

Im having issues with my front lcd display of my vusuo4kse after a migration from vuduo.

Installed openpli from usb stick and dis a restore of the config of vuduo backup from the hard disk that I moved too.

 

It just needed a bit of a tweaking afterwards to get it running the way I wanted it. 

However the front lcd display is still not ok. See attached picture.

 

Anyone has an idea if there is a config file somewhere in enigma2 that defines the resolution of the display that I can adapt for the vuduo4kse display?

 

 

Attached Files

•  IMG_9822.jpeg   55.17KB   1 downloads

[ccs]

.

Installed openpli from usb stick and dis a restore of the config of vuduo backup from the hard disk that I moved too.

 

 

Restoring the config from a different machine would almost certainly need "tweaking" as you describe it.

It should be safe to do it if you understand what you are doing (or more to the point, what you did on the old machine).

[Pr2]

Please check this thread:

 

https://forums.openp...u-uno-4kse-lcd/

 

May be the Duo4kse has the same LCD as the uno4kse

 

so may be interesting to display the LCD resolution like explained in the other thread.

[pietjepuk]

Please check this thread:

 

https://forums.openp...u-uno-4kse-lcd/

 

May be the Duo4kse has the same LCD as the uno4kse

 

so may be interesting to display the LCD resolution like explained in the other thread.

The problem I seem to have is that no images generated via skins or lcd4linux are actually written to the display. What is shown seems to be a fallback from a situation where skin images cannot be written to the screen. Is there anywhere in a setting a link to the entry in /dev to be used for the lcd display by the enigma2 process?

I've tried a few different "display" skins, no change visible on the actual display when I try different skins

 

I've been looking at the /dev directory, should there be a lcd0 device entry? when looking at box directory I see

root@vuduo4kse:/dev# ls -l dbox

lrwxrwxrwx    1 root     root             6 Jan  1  1970 fp0 -> ../fp0

-rw-r--r--    1 root     root             5 Nov  5 14:42 lcd0

lrwxrwxrwx    1 root     root             8 Jan  1  1970 oled0 -> ../oled0

 

Should lcd0 also be a symbolic link to ../lcd0? and a /dev/lcd0?

Edited by pietjepuk, 5 November 2021 - 15:44.

[pietjepuk]

Info from Enigma2 in debug mode:

ENIGMA_DEBUG_LVL=4                                                                                                                                              

[eInit] + (9) gLCD                                                                       

[eFbLCD] /dev/fb1: No such file or directory                                             

[eFbLCD] framebuffer /dev/fb1 not available                                              

[eDboxLCD] xres=480, yres=320, bpp=32 lcd_type=3                                         

[eLCD] (480x320x32) buffer 0xb5e2a008 614400 bytes, stride 1920                          

[gLCDDC] resolution: 480x320x32 stride=1920                                              

[eInit] + (9) GFBDC                                                                      

[fb] /dev/fb0: 21600k video mem 

[Jork]

No actual xml in your case here.https://github.com/O...op/data/display This should be solved for these models i think. DUO4K and DUO4KSE .

Edited by Jork, 5 November 2021 - 21:05.

[pietjepuk]

No actual xml in your case here.https://github.com/O...op/data/display This should be solved for these models i think. DUO4K and DUO4KSE .

Unfortunately not, installed the one from there already ;-(