Multiple Frame buffer beta testers wanted

[procount]

@lonerider - in my post above I mentioned that this driver would not work for me in Raspbian installed by PINN.
You should do a normal Raspbian install through Etcher or win32diskimager and try again.

[epg]

Hi Jamesh

First of all, a BIG thank you for your efforts in the multiple Rpi framebuffer patch.

My setup:
Hardware: Rapberry pi 3 model B+ (latest Rpi), 7" official touchscreen, HDMI Samsung fullHD tv.
Software: latest Raspbian with framebuffer kernel & firmware.

I did some quick tests and I'm able to run Netsurf (a framebuffer browser) in /dev/fb1 while having an active console in /dev/fb0.
To achieve this goal, I had to recompile Netsurf from source (because the default framebuffer /dev/fb0 is hardcoded in the src) and launch nsfb from a console (I'm not starting X automatically) or via ssh.

Now the problems:
1) if I try to strart X from the fb0, then X runs fine in fb0 but destroy (blank screen) the Netsurf browser in fb1!! I suspect that X initialize fb0 and fb1, so fb1 goes blank;

2) booting directly with X (default Raspbian), if I try to launch on fb1 Netsurf via xterm nothing happens: again, X seems to tie fb0 and fb1..

Anyway, I've found the multiple framebuffer patch very useful: it permits to have a "control display" to show control information (i.e. via fb web browser) on a specific fb while another program runs on the other fb

Epg.

[jamesh]

Not sure what X does under these circumstances, I need to look in to X an multiple FB's today anyway, so a timely report!

[jamesh]

OK, so I am back on this now after doing some work elsewhere.

Did anyone manage to get X running over multiple displays? That's what I plan to try and get working, any hints gratefully received.

[jamesh]

I have not been succesful getting X to run over multiple FB's but have produced a xorg.confg file that makes it a bit easier to switch between different configurations, and to turn off the fbturbo driver if required. Posting it here, might be useful to someone! Simply replace the /usr/share/X11/xorg.conf.d/99-fbturbo.conf contents with the contents here. There are layouts for multihead, but they simply don't work correctly, still trying to figure out why.

You select which layout you want using the following, where layout name is one of the "ServerLayout"'s specified in the conf file here.

startx -- -layout "layoutname"

Code: Select all

# This is a minimal sample config file, which can be copied to
# /etc/X11/xorg.conf in order to make the Xorg server pick up
# and load xf86-video-fbturbo driver installed in the system.
# When troubleshooting, check /var/log/Xorg.0.log for the debugging
# output and error messages.
#
# Run "man fbturbo" to get additional information about the extra
# configuration options for tuning the driver.

#Section "Device"
#        Identifier      "Allwinner A10/A13 FBDEV"
#        Driver          "fbturbo"
#        Option          "fbdev" "/dev/fb1"

#        Option          "SwapbuffersWait" "true"
#EndSection


Section "Device"
        Identifier      "fbturbo0"
        Driver          "fbturbo"
        Option          "fbdev" "/dev/fb0"

        Option          "SwapbuffersWait" "true"
	Option		"debug" "true"
EndSection

Section "Device"
        Identifier      "fbturbo1"
        Driver          "fbturbo"
        Option          "fbdev" "/dev/fb1"

        Option          "SwapbuffersWait" "true"
	Option		"debug" "true"
EndSection

Section "Device"
        Identifier      "fbdev0"
        Driver          "fbdev"
        Option          "fbdev" "/dev/fb0"
EndSection

Section "Device"
        Identifier      "fbdev1"
        Driver          "fbdev"
        Option          "fbdev" "/dev/fb1"
EndSection

Section "Monitor"
    Identifier "Monitor0"
EndSection

Section "Monitor"
    Identifier "Monitor1"
EndSection

Section "Screen"
    Identifier "ScreenTurbo0"
    Monitor "Monitor0"
    Device "fbturbo0"
    Subsection "Display"
    EndSubSection
EndSection

Section "Screen"
    Identifier "ScreenTurbo1"
    Monitor "Monitor1"
    Device "fbturbo1"
    Subsection "Display"
    EndSubSection
EndSection

Section "Screen"
    Identifier "ScreenDev0"
    Monitor "Monitor0"
    Device "fbdev0"
    Subsection "Display"
    EndSubSection
EndSection

Section "Screen"
    Identifier "ScreenDev1"
    Monitor "Monitor1"
    Device "fbdev1"
    Subsection "Display"
    EndSubSection
EndSection


Section "ServerLayout"
    Identifier "MultiheadTurbo"
    Screen  1 "ScreenTurbo0"  
    Screen  0 "ScreenTurbo1" rightof "ScreenTurbo0"
EndSection

Section "ServerLayout"
    Identifier "Singlehead0"
    Screen  0 "ScreenTurbo0"  
EndSection

Section "ServerLayout"
    Identifier "Singlehead1"
    Screen  0 "ScreenTurbo1"  
EndSection

Section "ServerLayout"
    Identifier "MultiheadSlow"
    Screen  0 "ScreenDev0"  
    Screen  1 "ScreenDev1" rightof "ScreenDev0"
EndSection

Section "ServerLayout"
    Identifier "SingleheadSlow0"
    Screen  0 "ScreenDev0"  
EndSection

Section "ServerLayout"
    Identifier "SingleheadSlow1"
    Screen  0 "ScreenDev1"  
EndSection

Section "ServerFlags"
    Option "BlankTime"  "0"
    Option "StandbyTime"  "0"
    Option "SuspendTime"  "0"
    Option "OffTime"  "0"
    Option "DefaultServerLayout" "Singlehead0"
EndSection

[jamesh]

Hi Jamesh

First of all, a BIG thank you for your efforts in the multiple Rpi framebuffer patch.

My setup:
Hardware: Rapberry pi 3 model B+ (latest Rpi), 7" official touchscreen, HDMI Samsung fullHD tv.
Software: latest Raspbian with framebuffer kernel & firmware.

I did some quick tests and I'm able to run Netsurf (a framebuffer browser) in /dev/fb1 while having an active console in /dev/fb0.
To achieve this goal, I had to recompile Netsurf from source (because the default framebuffer /dev/fb0 is hardcoded in the src) and launch nsfb from a console (I'm not starting X automatically) or via ssh.

Now the problems:
1) if I try to strart X from the fb0, then X runs fine in fb0 but destroy (blank screen) the Netsurf browser in fb1!! I suspect that X initialize fb0 and fb1, so fb1 goes blank;

2) booting directly with X (default Raspbian), if I try to launch on fb1 Netsurf via xterm nothing happens: again, X seems to tie fb0 and fb1..

Anyway, I've found the multiple framebuffer patch very useful: it permits to have a "control display" to show control information (i.e. via fb web browser) on a specific fb while another program runs on the other fb

Epg.

Just been trying something similar. Approximately I did something like this....Start a new login (ctrl-alt Fn), change the console (conf2b n 1) to appear on LCD. Go back to original console, startx using the Xorg.conf from pervious post. Appears on HDMI. fb1 stays with whatever I had running on it (top)- doesn't get blanked. You should be able to switch between consoles using the ctrl-alt Fn keypress. Quite funky.

Also been testing the different in the display settings in omxplayer. Table as follows, so there is clearly a slight difference between current software and the mutiFB stuff which people using dispmanx or devices that use display numbers directly may encounter. I'll see what I can do to fix that.

Display Num/Current/MultiFB
0 LCD LCD
1 LCD LCD
2 LCD HDMI <<< the difference
3 LCD LCD
4 LCD LCD
5 HDMI HDMI
6 HDMI HDMI
7 LCD LCD

[6by9]

Just been trying something similar. Approximately I did something like this....Start a new login (ctrl-alt Fn), change the console (conf2b n 1) to appear on LCD. Go back to original console, startx using the Xorg.conf from pervious post. Appears on HDMI. fb1 stays with whatever I had running on it (top)- doesn't get blanked. You should be able to switch between consoles using the ctrl-alt Fn keypress. Quite funky.

Also been testing the different in the display settings in omxplayer. Table as follows, so there is clearly a slight difference between current software and the mutiFB stuff which people using dispmanx or devices that use display numbers directly may encounter. I'll see what I can do to fix that.

Display Num/Current/MultiFB
0 LCD LCD
1 LCD LCD
2 LCD HDMI <<< the difference
3 LCD LCD
4 LCD LCD
5 HDMI HDMI
6 HDMI HDMI
7 LCD LCD

https://github.com/raspberrypi/userland ... ypes.h#L60

Code: Select all

#define DISPMANX_ID_MAIN_LCD  0
#define DISPMANX_ID_AUX_LCD   1
#define DISPMANX_ID_HDMI      2
#define DISPMANX_ID_SDTV 3

So isn't using the HDMI correct for mode 2, and actually you're fixing a bug in the current firmware?
Or am I on totally the wrong ste of defines?

[jamesh]

Just been trying something similar. Approximately I did something like this....Start a new login (ctrl-alt Fn), change the console (conf2b n 1) to appear on LCD. Go back to original console, startx using the Xorg.conf from pervious post. Appears on HDMI. fb1 stays with whatever I had running on it (top)- doesn't get blanked. You should be able to switch between consoles using the ctrl-alt Fn keypress. Quite funky.

Also been testing the different in the display settings in omxplayer. Table as follows, so there is clearly a slight difference between current software and the mutiFB stuff which people using dispmanx or devices that use display numbers directly may encounter. I'll see what I can do to fix that.

Display Num/Current/MultiFB
0 LCD LCD
1 LCD LCD
2 LCD HDMI <<< the difference
3 LCD LCD
4 LCD LCD
5 HDMI HDMI
6 HDMI HDMI
7 LCD LCD

https://github.com/raspberrypi/userland ... ypes.h#L60

Code: Select all

#define DISPMANX_ID_MAIN_LCD  0
#define DISPMANX_ID_AUX_LCD   1
#define DISPMANX_ID_HDMI      2
#define DISPMANX_ID_SDTV 3

So isn't using the HDMI correct for mode 2, and actually you're fixing a bug in the current firmware?
Or am I on totally the wrong ste of defines?

Correct - the current firmware munges the display number, depending on what is plugged in I believe. I think to ensure that everything works by default on the LCD rather than the HDMI. Not great for consistency when you move to multi framebuffers.

[AiRSpectruM]

I'm new here but this looked like it could help me finish a project I started so I figured I would download it and see if I could help uncover anything. On initial install and after getting both the startup console and desktop to display on the LCD I noticed that the splash screen loaded on my HDMI (Dell monitor) and didn't go away.

I've only just started playing around with this, i'll post if more comes up.

EDIT: Is it possible to boot the desktop to both screens?

EDIT2: After switching the console to boot on the HDMI (0) splash screen appears and goes away once booted.

[DirkS]

EDIT: Is it possible to boot the desktop to both screens?

Yes, but you will have to find the correct X configuration.
Start with having a look at James' configuration above.
Then search for something like 'linux dual monitor'

[Melticus]

hello @jamesh

I followed the instructions to the letter (very good and well written) everything you explain is as expected, except

My HDMI screen does comeout of standby on boot of raspi but does not display the coulor square. IT then goes back into powersave.

When I run FBI I get an error:

using "Liberation Mono-16", pixelsize=21.33 file=/usr/share/fonts/truetype/liberation2/LiberationMono-Regular.ttf
ioctl VT_GETSTATE: Inappropriate ioctl for device (not a linux console?)

from uname -e I get
Linux raspberrypi 4.14.50-v7+ #270 SMP Wed Jun 20 14:19:18 BST 2018 arm71 GNU/Linux

I have /ect/fb0 and /etc/fb1 in the directory

I tried FBI with a to of options but all the same.

Any Ideas?

Bet I am doing something stu pid..

[DirkS]

using "Liberation Mono-16", pixelsize=21.33 file=/usr/share/fonts/truetype/liberation2/LiberationMono-Regular.ttf
ioctl VT_GETSTATE: Inappropriate ioctl for device (not a linux console?)

Is this when logged in remotely (using SSH) or maybe using virtual terminals as with 'screen' or tmux)?
fbi does not like that...

[Melticus]

No Dirks. I have a USB kbd connected to the rpi and 7inch screen. I am using the Rasbian GUI though.

EDIT: Oh and I checked the font directory. that font is there...

[DirkS]

No Dirks. I have a USB kbd connected to the rpi and 7inch screen. I am using the Rasbian GUI though.

EDIT: Oh and I checked the font directory. that font is there...

That's not the issue.
from 'man fbi'

fbi also needs access to the linux console (i.e. /dev/ttyN) for sane console switch handling. That is obviously no problem for console logins, but any kind of a pseudo tty (xterm, ssh, screen, ...) will not work.

GUI consoles are also pseudo tty...

Switching to a terminal with <ctrl+alt+F1> may work, but I'm no sure
You can check the device with 'tty' command

[Melticus]

That Does Work DirkS. I am now outputting to two screens.

But

I am so close here. Can I run one of these non virtual ttys from python3? I have an app running on X and I want to display a folder full of images in a continuous slideshow on a second screen. Do you know if this is possible?

Thanks a lot you have been very helpfull thus far!

[DirkS]

I am so close here. Can I run one of these non virtual ttys from python3? I have an app running on X and I want to display a folder full of images in a continuous slideshow on a second screen. Do you know if this is possible?

Sorry, no idea. But there must be a GUI application that can do that...

We're getting a bit off topic though. Maybe you should start a new topic for this

[Melticus]

Yea, Will Do thanks!!

[jamesh]

No Dirks. I have a USB kbd connected to the rpi and 7inch screen. I am using the Rasbian GUI though.

EDIT: Oh and I checked the font directory. that font is there...

That's not the issue.
from 'man fbi'

fbi also needs access to the linux console (i.e. /dev/ttyN) for sane console switch handling. That is obviously no problem for console logins, but any kind of a pseudo tty (xterm, ssh, screen, ...) will not work.

GUI consoles are also pseudo tty...

Switching to a terminal with <ctrl+alt+F1> may work, but I'm no sure
You can check the device with 'tty' command

DirksS is correct, and I pressume you are running the desktop? This means FBI cannot task switch the screens corectly, so I think you can use the -vt option, which might need sudo as well.

E.g.

sudo fbi -vt 1 -d /dev/fb1 /usr/share/rpd-wallpaper/islands.jpg

[Melticus]

Thanks @Jamesh I will try that to when I finish boring work today...

[EDIT] I also asked around, you can also use "openvt" to run any commandline in TTY mode.

Also wanted to give some feedback from my investigation of your patch.

I am running a Python App on X using wxpython framework.

Before I did your patch My GUI was filling the screen and my images and text was placed nicely on the screen. So I know the app works.

After I did the patch and I did not connect the HDMI interface (defaults to the 7inch screen) . When My App boots I am getting a 10 or 15 pixel boundry around the screen that is Blank and my images are all clipped. I have an image but dont know how to upload it to this forum. If you give me an email address I'll send it to you?

Could this be as a result of the patch?

Note When I connected the HDMI and the GUI was on the HDMI, I used fbi to output to the 7 inch screen, It filled the screen completely(no boundry) so its not a fb size issue.

[jamesh]

Sounds like overscan is turned on - you can turn it off in config.txt

[procount]

@Melticus - see my post above -> viewtopic.php?f=63&t=216399&start=25#p1336653 . Overscan is turned on by default in this patch (instead of being off)

[jamesh]

Think I have figured out one problem with multi X screen - now get an X display on both devices (HDMI/DSI). Bug in my Linux framebuffer changes to support multiple bcm devices. Will post a new zImage in the near future.

However, although X does appear on the two devices, it's not particular useful - most stuff just happens on the main display, you cannot move windows from one to the other etc. Not sure what that is, so if anyone has any clues. My suspicion is the the devies are different resolutions and that may be causing confusion. Any X experts out there with ideas?

[jamesh]

Think I have figured out one problem with multi X screen - now get an X display on both devices (HDMI/DSI). Bug in my Linux framebuffer changes to support multiple bcm devices. Will post a new zImage in the near future.

However, although X does appear on the two devices, it's not particular useful - most stuff just happens on the main display, you cannot move windows from one to the other etc. Not sure what that is, so if anyone has any clues. My suspicion is the the devies are different resolutions and that may be causing confusion. Any X experts out there with ideas?

Ah Ha. Got it.

Now have desktop over multiple screens! Woot! Will post more stuff later.

[jamesh]

OK, here is a link to a new kernel image, goes in boot folder as usual

https://drive.google.com/open?id=1f-f5c ... cOI4FbGgxL

You will also need the following xorg (note this still has some extraneous stuff in, still winnowing it down)

Code: Select all

# This is a minimal sample config file, which can be copied to
# /etc/X11/xorg.conf in order to make the Xorg server pick up
# and load xf86-video-fbturbo driver installed in the system.
# When troubleshooting, check /var/log/Xorg.0.log for the debugging
# output and error messages.
#
# Run "man fbturbo" to get additional information about the extra
# configuration options for tuning the driver.

#Section "Device"
#        Identifier      "Allwinner A10/A13 FBDEV"
#        Driver          "fbturbo"
#        Option          "fbdev" "/dev/fb1"
#        Option          "SwapbuffersWait" "true"
#EndSection


Section "Device"
        Identifier      "fbturbo0"
        Driver          "fbturbo"
        Option          "fbdev" "/dev/fb0"

        Option          "SwapbuffersWait" "true"
        Option          "debug" "true"
EndSection

Section "Device"
        Identifier      "fbturbo1"
        Driver          "fbturbo"
        Option          "fbdev" "/dev/fb1"

        Option          "SwapbuffersWait" "true"
        Option          "debug" "true"
EndSection

Section "Device"
        Identifier      "fbdev0"
        Driver          "fbdev"
        Option          "fbdev" "/dev/fb0"
EndSection

Section "Device"
        Identifier      "fbdev1"
        Driver          "fbdev"
        Option          "fbdev" "/dev/fb1"
EndSection

Section "Monitor"
    Identifier "Monitor0"
    Option "Primary" "False"
EndSection

Section "Monitor"
    Identifier "Monitor1"
    Option "RightOf" "Monitor0"
    Option "Primary" "False"
EndSection

Section "Screen"
    Identifier "ScreenTurbo0"
    Monitor "Monitor0"
    Device "fbturbo0"
    Subsection "Display"
    EndSubSection
EndSection

Section "Screen"
    Identifier "ScreenTurbo1"
    Monitor "Monitor1"
    Device "fbturbo1"
    Subsection "Display"
    EndSubSection
EndSection

Section "Screen"
    Identifier "ScreenDev0"
    Monitor "Monitor0"
    Device "fbdev0"
    Subsection "Display"
    EndSubSection
EndSection

Section "Screen"
    Identifier "ScreenDev1"
    Monitor "Monitor1"
    Device "fbdev1"
    Subsection "Display"
    EndSubSection
EndSection

Section "ServerLayout"
    Identifier "Multihead"
    Screen  0 "ScreenTurbo0"
    Screen  1 "ScreenTurbo1" rightof "ScreenTurbo0"
    Option  "Xinerama" "true"
EndSection

Section "ServerLayout"
    Identifier "Singlehead0"
    Screen  0 "ScreenTurbo0"
EndSection

Section "ServerLayout"
    Identifier "Singlehead1"
    Screen  0 "ScreenTurbo1"
EndSection

Section "ServerFlags"
    Option "BlankTime"  "0"
    Option "StandbyTime"  "0"
    Option "SuspendTime"  "0"
    Option "OffTime"  "0"
    Option "DefaultServerLayout" "Singlehead0"
EndSection

Startx line is

startx -- -layout Multihead

You can play with the desktop configurations using the following files

~/.config/pcmanfm/LXDE-pi/desktop-items-[x].conf

[epg]

OK, here is a link to a new kernel image, goes in boot folder as usual

https://drive.google.com/open?id=1f-f5c ... cOI4FbGgxL

Hi Jamesh,
latest kernel image breaks something in the network area.
I can't ping the raspy anymore (I use the integrated wifi) and, moreover, my wireless Logitech K400r keyboard stopped working (it connects to the Raspi via a proprietary Logitech USB dongle, so doesn't use the wifi channels).

I have seen an error in the console when booting, but I'm not able to log in to do further analysis because I don't have a USB keyboard.

Replacing the latest kernel7.img with the previous one, network and keyboard work as expected.

Maybe there's something wrong with the latest image?

Bye, Epg.