Tiny Core Linux
Tiny Core Base => Raspberry Pi => Topic started by: Rabie on August 05, 2021, 03:21:51 AM
-
Hello there,
i have installed piCore 13.x armv7l on pi 4 and i want to use 2 Monitors.
Anyway i have used on TinyCore pure64 xrandr for that
so i installed xrandr on piCore but i am getting the following:
$xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 1920 x 1080, current 1920x1080, maximum 1920x1080
default connected 1920x1080+0+0 0mm x 0mm
1920x1080 0.00*
i already tried to add a new Mode like:
$cvt 1920 1080 60
# 1920x1080 59.96 Hz (CVT 2.07M9) hsync: 67.16 kHz; pclk: 173.00 MHz
Modeline "1920x1080_60.00" 173.00 1920 2048 2248 2576 1080 1083 1088 1120 -hsync +vsync
$xrandr --newmode "1920x1080_60.00" 173.00 1920 2048 2248 2576 1080 1083 1088 1120 -hsync +vsync
xrandr: Failed to get size of gamma for output default
How can i get this to work with xrandr ?
Thank you
-
Hi,
i found out that there is just one Framebuffer in PiCore:
$ls /dev/fb*
/dev/fb0
i don't know if this possible to make piCore work with 2 Monitors
-
Have you tried using Xorg-3d and dtoverlay=vc4-kms-v3d-pi4?
Are both of the monitors hdmi?
Do you see both monitors mentioned in Xorg.0.log?
-
Hi Juanito,
Have you tried using Xorg-3d and dtoverlay=vc4-kms-v3d-pi4?
i just tried that and the second Monitor stucks on the rainbow screen while booting.
Are both of the monitors hdmi?
the first one is direkt from HDMI to HDMI
the second is from HDMI to DVI (because my second Monitor doesn't has HDMI) But it work's when its the only Monitor connected
Do you see both monitors mentioned in Xorg.0.log?
i dont think so, it just says that the system use some Default Screen
Here ist the Log File (See Attachtment)
-
I see a couple of problems:
* the expat2 extension does not seem to be loaded?
* the xf86-video-fbturbo extension prevents 3d acceleration from working
You could try deleting /usr/local/share/X11/xorg.conf.d/fbturbo.conf and re-starting X
-
Hi Juanito,
* the expat2 extension does not seem to be loaded?
its already installed if this what you mean
$ tce-load -wi expat2
expat2 is already installed!
You could try deleting /usr/local/share/X11/xorg.conf.d/fbturbo.conf and re-starting X
nothing happens, the second Monitor still stuck on the rainbow screen
-
Could you attach the latest Xorg.0.log
-
Could you attach the latest Xorg.0.log
yes of course!
i hope, i am not doing it wrong
i did it like that:
sudo rm /usr/local/share/X11/xorg.conf.d/fbturbo.conf
startx
-
The fbturbo driver is still being loaded, could you delete /usr/local/lib/xorg/modules/drivers/fbturbo_drv.so, exit the gui and re-start X
-
The fbturbo driver is still being loaded, could you delete /usr/local/lib/xorg/modules/drivers/fbturbo_drv.so, exit the gui and re-start X
so i deleted the driver
sudo rm /usr/local/share/X11/xorg.conf.d/fbturbo.conf
sudo rm /usr/local/lib/xorg/modules/drivers/fbturbo_drv.so
i saw in the log that it loaded some lib:
/usr/local/lib/xorg/modules/libfbdevhw.so
so i deleted it too
sudo rm /usr/local/lib/xorg/modules/libfbdevhw.so
this is the new Log
do i have to kill some process bevor i start X again ?
-
You should not delete /usr/local/lib/xorg/modules/libfbdevhw.so, this has nothing to do with the fbturbo driver.
Xorg is still using the fbturbo driver, which must mean that you have either not deleted it or are rebooting after having deleted it.
Do you see at least one of the screens blank when you load Xorg-3d (which loads graphics-KERNEL) and it enters kms mode?
-
Hi Juanito,
Xorg is still using the fbturbo driver, which must mean that you have either not deleted it or are rebooting after having deleted it.
no i deleted both Files and did not reboot
i think i was doing the restart from X wrong :o
i deleted both Files:
sudo rm /usr/local/share/X11/xorg.conf.d/fbturbo.conf
sudo rm /usr/local/lib/xorg/modules/drivers/fbturbo_drv.so
and then i killed the x server:
sudo pkill -f "/usr/local/lib/xorg/Xorg -logfile /tmp/xorg.log -nolisten tcp"
and now when i do:
$sudo Xorg -configurethis what i get: (See Log)
and if i run:
$startxfailed in waitforX
-
To exit to the console prompt you can use the exittc icon.
There is no need to use “Xorg -configure”, the automatic configuration should work.
First we need to check that you are in kms mode - if you reboot to the console prompt and then load Xorg-3d, do you see the screen blank and then come back again?
Does “dmesg | tail -20” show vc4 and v3d being initialised?
-
First we need to check that you are in kms mode - if you reboot to the console prompt and then load Xorg-3d, do you see the screen blank and then come back again?
i am sorry but I don't even know how do i enter the kms mode i just did like you said " with exittc => exit to prompt " is this the same as reboot to console prompt ?
First we need to check that you are in kms mode - if you reboot to the console prompt and then load Xorg-3d, do you see the screen blank and then come back again?
what do you mean with load Xorg-3d and the screen blanck ?
Does “dmesg | tail -20” show vc4 and v3d being initialised?
-
Reboot means power-off and power-on again.
Once you have rebooted to the console prompt, issue the command “tce-load -i Xorg-3d”. This will have the effect of loading the graphics-KERNEL module , which, if you entered the dtoverlay line mentioned previously into config.txt, will blank the screen briefly.
-
Hi Juanito
The last dmesg he posted shows vc4 can't find kernel/drivers/media/cec/cec.ko.
-
Reboot means power-off and power-on again.
Once you have rebooted to the console prompt, issue the command “tce-load -i Xorg-3d”. This will have the effect of loading the graphics-KERNEL module , which, if you entered the dtoverlay line mentioned previously into config.txt, will blank the screen briefly.
$ tce-load -i Xorg-3d
Xorg-3d.tcz: OK
its just says that the extension was loaded and the Screen didn't blank. Maybe because the extension "graphics-5.10.16-piCore-v7l.tcz" is listed in onboot.lst ?
-
graphics-5.10.16-piCore-v7l was missing a driver - I added it.
Please update graphics-5.10.16-piCore-v7l, reboot and check "dmesg | tail -20" to verfiy that the vc4 driver loads.
-
Hi Juanito,
graphics-5.10.16-piCore-v7l was missing a driver - I added it.
Please update graphics-5.10.16-piCore-v7l, reboot and check "dmesg | tail -20" to verfiy that the vc4 driver loads.
wow that driver did it, now both Screens works (See Attachments)
so now i need to let both Screens work with xrandr:
$ xrandr
xrandr : Failed to get size of gamma for output "default"
Screen 0: minimum 1280 x 1024, current 1280 x 1024, maximum 1280 x 1024
default connected 1280x1024+0+0 0mm x 0mm
1280x1024 0.00*
could you show me the way ?
Edit: while booting the second Screen stucks like i said before on the rainbow Screen and then after it finished booting the second Screen works fine!
can i let the second Screen shows what the first Screen shows while booting ?
-
As per your Xorg.0.log, you are still using the fbturbo driver - I don't know if that effects xrandr, but it is blocking 3d acceleration.
-
As per your Xorg.0.log, you are still using the fbturbo driver - I don't know if that effects xrandr, but it is blocking 3d acceleration.
how do i uninstall it ?
-
You could delete it from Xorg.tcz.dep - check also that you don't have it in onboot.lst
-
As per your Xorg.0.log, you are still using the fbturbo driver - I don't know if that effects xrandr, but it is blocking 3d acceleration.
oh yes you are right!
After i remove the Driver and restarted X server i am getting with xrandr the right information.
sudo rm /usr/local/share/X11/xorg.conf.d/fbturbo.conf
sudo rm /usr/local/lib/xorg/modules/drivers/fbturbo_drv.so
-
You could delete it from Xorg.tcz.dep - check also that you don't have it in onboot.lst
OMG it works:
$ xrandr
Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 7680 x 7680
HDMI-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 527mm x 296mm
1920x1080 60.00*+ 50.00 59.94
1920x1080i 60.00 50.00 59.94
1680x1050 59.88
1600x900 60.00
1280x1024 75.02 60.02
1280x800 59.91
1152x864 75.00
1280x720 60.00 50.00 59.94
1024x768 75.03 60.00
832x624 74.55
800x600 75.00 60.32
720x576 50.00
720x480 60.00 59.94
640x480 75.00 60.00 59.94
720x400 70.08
HDMI-2 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 527mm x 296mm
1920x1080 60.00*+ 50.00 59.94
1920x1080i 60.00 50.00 59.94
1680x1050 59.88
1600x900 60.00
1280x1024 75.02 60.02
1280x800 59.91
1152x864 75.00
1280x720 60.00 50.00 59.94
1024x768 75.03 60.00
832x624 74.55
800x600 75.00 60.32
720x576 50.00
720x480 60.00 59.94
640x480 75.00 60.00 59.94
720x400 70.08
Thank you very very much for your help! :D :D
there is only on thing left:
while booting the second Screen stucks like i said before on the rainbow Screen and then after it finished booting the second Screen works fine!
can i let the second Screen shows what the first Screen shows while booting ?
-
I suspect that you will only see data on one screen during boot - I don't know this for sure, you'll have to google or search/post a question on the raspberrypi forums to find out..
-
I suspect that you will only see data on one screen during boot - I don't know this for sure, you'll have to google or search/post a question on the raspberrypi forums to find out..
Okay, Thanx
-
Hi Juanito,
after all the freerdp didn't work with the "/Multimon:force" option
xfreerdp /sec:rdp /drive:USB-Stick,/mnt/ /multimon:force +multitransport +auto-reconnect -themes -wallpaper /cert-ignore /bpp:15 /kbd:0x00000407 /d:domain /v:server:port /f
[10:31:04:365] [5420:5421] [INFO][com.freerdp.core] - freerdp_connect:freerdp_set_last_error_ex resetting error state
[10:31:04:365] [5420:5421] [INFO][com.freerdp.client.common.cmdline] - loading channelEx rdpdr
[10:31:04:365] [5420:5421] [INFO][com.freerdp.client.common.cmdline] - loading channelEx rdpsnd
[10:31:04:365] [5420:5421] [INFO][com.freerdp.client.common.cmdline] - loading channelEx cliprdr
[10:31:04:787] [5420:5421] [INFO][com.freerdp.primitives] - primitives autodetect, using optimized
[10:31:04:795] [5420:5421] [INFO][com.freerdp.core] - freerdp_tcp_is_hostname_resolvable:freerdp_set_last_error_ex resetting error state
[10:31:04:796] [5420:5421] [INFO][com.freerdp.core] - freerdp_tcp_connect:freerdp_set_last_error_ex resetting error state
[10:31:04:807] [5420:5421] [ERROR][com.freerdp.core.gcc] - WARNING: true multi monitor support was not advertised by server!
[10:31:04:807] [5420:5421] [ERROR][com.freerdp.core.gcc] - Sending multi monitor information anyway (may break connectivity!)
[10:31:05:912] [5420:5421] [INFO][com.freerdp.gdi] - Local framebuffer format PIXEL_FORMAT_BGRX32
[10:31:05:912] [5420:5421] [INFO][com.freerdp.gdi] - Remote framebuffer format PIXEL_FORMAT_RGB16
[10:31:05:048] [5420:5421] [INFO][com.winpr.clipboard] - initialized POSIX local file subsystem
[10:31:05:146] [5420:5442] [INFO][com.freerdp.channels.rdpdr.client] - Loading device service drive [USB-Stick] (static)
[10:31:05:147] [5420:5421] [INFO][com.freerdp.channels.rdpsnd.client] - [static] Loaded fake backend for rdpsnd
it says that the multi monitor support was not advertised by server, but it actually works with TinyCore with the same freerdp version.
-
there is a thing i found out maybe effect this option /multimon
when i install freerdp.tcz and try to start it, it asks for the libnettle.so.7
xfreerdp: error while loading shared libraries: libnettle.so.7: cannot open shared object file: No such file or directory
and when installing nettle.tcz
i get the latest version:
/usr/local/lib/libnettle.a
/usr/local/lib/libnettle.so.8.1
/usr/local/lib/libnettle.so.8
/usr/local/lib/libnettle.so
so i downloaded the old one from V11.x/armv7
is that why the freerdp isn't working with /multimon ?
-
so i downloaded the old one from V11.x/armv7
is that why the freerdp isn't working with /multimon ?
Did you try it (use the "sudo ldconfig" command first)?
-
so i downloaded the old one from V11.x/armv7
is that why the freerdp isn't working with /multimon ?
Did you try it (use the "sudo ldconfig" command first)?
yes now i did but freerdp still asking for "libnettle.so.7"
-
Hi Rabie
... but freerdp still asking for "libnettle.so.7"
sudo ldconfig will not effect which libraries freerdp will look for.
... so i downloaded the old one from V11.x/armv7 ...
You also need to load the extension.
If you overwrite your existing nettle extension with the the old version, you need to reboot to load it.
-
... but freerdp still asking for "libnettle.so.7"
sudo ldconfig will not effect which libraries freerdp will look for.
I thought the old nettle extension had been mounted somewhere and the libs copied into the root filesystem.
-
Hi Juanito
tce-load runs ldconfig in the update_system() function which gets called by the install() function.
-
Yes, but when you manually mount an extension in, say, /tmp and copy the files to / ldconfig is needed 🙂
-
Hi Juanito
You are correct sir. I missed this part when I read your reply:
... and the libs copied into the root filesystem.
I really should pay closer attention. :-[
-
Hi Rich,
You also need to load the extension.
If you overwrite your existing nettle extension with the the old version, you need to reboot to load it.
i already did all of that and the freerdp is working fine with one Monitor but the Problem what i am facing is like i mentioned before:
after all the freerdp didn't work with the "/Multimon:force" option
Code: [Select]
xfreerdp /sec:rdp /drive:USB-Stick,/mnt/ /multimon:force +multitransport +auto-reconnect -themes -wallpaper /cert-ignore /bpp:15 /kbd:0x00000407 /d:domain /v:server:port /f
Code: [Select]
[10:31:04:365] [5420:5421] [INFO][com.freerdp.core] - freerdp_connect:freerdp_set_last_error_ex resetting error state
[10:31:04:365] [5420:5421] [INFO][com.freerdp.client.common.cmdline] - loading channelEx rdpdr
[10:31:04:365] [5420:5421] [INFO][com.freerdp.client.common.cmdline] - loading channelEx rdpsnd
[10:31:04:365] [5420:5421] [INFO][com.freerdp.client.common.cmdline] - loading channelEx cliprdr
[10:31:04:787] [5420:5421] [INFO][com.freerdp.primitives] - primitives autodetect, using optimized
[10:31:04:795] [5420:5421] [INFO][com.freerdp.core] - freerdp_tcp_is_hostname_resolvable:freerdp_set_last_error_ex resetting error state
[10:31:04:796] [5420:5421] [INFO][com.freerdp.core] - freerdp_tcp_connect:freerdp_set_last_error_ex resetting error state
[10:31:04:807] [5420:5421] [ERROR][com.freerdp.core.gcc] - WARNING: true multi monitor support was not advertised by server!
[10:31:04:807] [5420:5421] [ERROR][com.freerdp.core.gcc] - Sending multi monitor information anyway (may break connectivity!)
[10:31:05:912] [5420:5421] [INFO][com.freerdp.gdi] - Local framebuffer format PIXEL_FORMAT_BGRX32
[10:31:05:912] [5420:5421] [INFO][com.freerdp.gdi] - Remote framebuffer format PIXEL_FORMAT_RGB16
[10:31:05:048] [5420:5421] [INFO][com.winpr.clipboard] - initialized POSIX local file subsystem
[10:31:05:146] [5420:5442] [INFO][com.freerdp.channels.rdpdr.client] - Loading device service drive [USB-Stick] (static)
[10:31:05:147] [5420:5421] [INFO][com.freerdp.channels.rdpsnd.client] - [static] Loaded fake backend for rdpsnd
it says that the multi monitor support was not advertised by server, but it actually works with TinyCore with the same freerdp version.
that is why i thought that the old nettle extension is the Problem.
And maybe its because the piCore take the two Monitors as one Large Screen ? (See Attachment)
-
The problem with the unmet dep on libnettle.so.7 seems to have been caused by the gnutls dep file.
The gnutls extension is the same in piCore-12.x and piCore-13.x, but the dep file in piCore-13.x was missing p11-kit and nettle.
The update to nettle in piCore-13.x (libnettle.so.7 -> libnettle.so.8 ) then broke gnutls and perhaps other extensions.
I created a nettle7 extension for backwards compatibility and adjusted the gnutls dep file accordingly - you will need to update your local copy.
-
Hi Juanito,
i just installed the new nettle7 extension and this got the freerdp to work with both Monitors!
the next problem what i have is:
the rdp image structure is loading Lines / blockwise screen layout (Realy slow)
even when i use the the "/gdi:hw" Option.
So i tried to reload the fbturbo driver again to see if it's better and indeed it is! (See this topic: https://www.raspberrypi.org/forums/viewtopic.php?t=249628)
do you have any ideas how do i get a faster redering oder get the two Monitors to work with the fbturbo ?
Thx
-
In the link you posted they give an Xorg conf snippet to get two monitors with fbturbo - did you try it?
-
In the link you posted they give an Xorg conf snippet to get two monitors with fbturbo - did you try it?
yes i tried it but before the new nettle7 extension without success
now i tried it again after and i am getting 2 Monitors Buffering but they buffer the same like a Mirror!
Hier ist my xorg.conf:
Section "Device"
Identifier "HDMI-1"
Driver "fbturbo"
Option "fbdev" "/dev/fb0"
Option "SwapbuffersWait" "true"
EndSection
Section "Device"
Identifier "HDMI-2"
Driver "fbturbo"
Option "fbdev" "/dev/fb1"
Option "SwapbuffersWait" "true"
EndSection
Section "Monitor"
Identifier "HDMI-1"
Option "PreferredMode" "1920x1080"
Option "Primary" "true"
Option "DPMS" "false"
# Option "Position" "0 0"
EndSection
Section "Monitor"
Identifier "HDMI-2"
Option "PreferredMode" "1280x1024"
Option "DPMS" "false"
Option "LeftOf" "HDMI1"
# Option "Position" "1280 1024"
EndSection
Section "Screen"
Identifier "screen0"
Device "HDMI-1"
Monitor "HDMI-1"
EndSection
Section "Screen"
Identifier "screen1"
Device "HDMI-2"
Monitor "HDMI-2"
EndSection
Section "ServerLayout"
Identifier "default"
Option "Xinerama" "off"
# Option "Clone" "off" ===> this option is not to find in Xorg.conf website ( https://www.x.org/releases/current/doc/man/man5/xorg.conf.5.xhtml#heading16 )
Screen 0 "screen0"
Screen 1 "screen1" RightOf "screen0"
EndSection
i can't find the option that makes the socond Monitor not as clone to the first one but as an extension Monitor
-
You say hdmi 2 is left of hdmi 1, but you also say screen 1 is right of screen 0?
-
You say hdmi 2 is left of hdmi 1, but you also say screen 1 is right of screen 0?
yes is't that the same ? even tho i tried to delete one of them, i am still getting a the same on both Screens
usually i would do that with xrandr but it's not working when fbturbo is loaded, is there someway to get xrandr work ?
Section "Device"
Identifier "HDMI-1"
Driver "fbturbo"
Option "fbdev" "/dev/fb0"
Option "SwapbuffersWait" "true"
EndSection
Section "Device"
Identifier "HDMI-2"
Driver "fbturbo"
Option "fbdev" "/dev/fb1"
Option "SwapbuffersWait" "true"
EndSection
Section "Monitor"
Identifier "HDMI-1"
Option "PreferredMode" "1920x1080"
Option "Primary" "true"
Option "Enable" "true"
Option "DPMS" "false"
# Option "Position" "0 0"
EndSection
Section "Monitor"
Identifier "HDMI-2"
Option "PreferredMode" "1280x1024"
Option "DPMS" "false"
Option "Enable" "true"
# Option "LeftOf" "HDMI1"
# Option "Position" "1280 1024"
EndSection
Section "Screen"
Identifier "screen0"
Device "HDMI-1"
Monitor "HDMI-1"
EndSection
Section "Screen"
Identifier "screen1"
Device "HDMI-2"
Monitor "HDMI-2"
EndSection
Section "ServerLayout"
Identifier "default"
Screen "screen0"
Screen "screen1" RightOf "screen0"
EndSection
-
I think the problem is that fbturbo is old and not maintained..
-
It's perhaps a long shot, but maybe wayland/weston might work better than x11?
A few hints here: http://forum.tinycorelinux.net/index.php/topic,23269.msg150229.html
-
Hi Rabie
... Hier ist my xorg.conf:
----- Snip -----
Section "Monitor"
Identifier "HDMI-2"
Option "PreferredMode" "1280x1024"
Option "DPMS" "false"
Option "LeftOf" "HDMI1"
# Option "Position" "1280 1024"
EndSection
----- Snip -----
I think HDMI1 is missing a dash, HDMI-1.
-
Hi Rich,
Hi Rabie
... Hier ist my xorg.conf:
----- Snip -----
Section "Monitor"
Identifier "HDMI-2"
Option "PreferredMode" "1280x1024"
Option "DPMS" "false"
Option "LeftOf" "HDMI1"
# Option "Position" "1280 1024"
EndSection
----- Snip -----
I think HDMI1 is missing a dash, HDMI-1.
You are absolutely right, i correct it but still not working
-
It's perhaps a long shot, but maybe wayland/weston might work better than x11?
A few hints here: http://forum.tinycorelinux.net/index.php/topic,23269.msg150229.html
i will have a look at that.
I think the problem is that fbturbo is old and not maintained..
is there any way to update the fbturbo driver? because i am using it on TinyCore 12.x/x86_64 and it just working fine with xrandr and without an xorg.conf
-
Hi Rabie
Xinerama is an extension to the X Window System that enables X applications and window managers to use two or more physical displays as one large virtual ...
Shouldn't Option "Xinerama" "off" be "on" ?
-
Hi Rabie
Xinerama is an extension to the X Window System that enables X applications and window managers to use two or more physical displays as one large virtual ...
Shouldn't Option "Xinerama" "off" be "on" ?
"Xinerama" is disabled by Default https://www.x.org/releases/current/doc/man/man5/xorg.conf.5.xhtml#heading16
and when i active it nothing happens :-\
Section "ServerLayout"
Identifier "default"
Screen "screen0"
Screen "screen1" RightOf "screen0"
Option "Xinerama" "on"
EndSection
-
I think the problem is that fbturbo is old and not maintained..
would the fbturbo actually with an old kernel work ? Like piCore V8x or V9x or will those Kernel not work with pi4 ?
-
I think it would be better to use the latest kernel with RPi4.
If Xorg-3d is too slow in the freerdp window, you could try replacing dtoverlay=vc4-kms-v3d-pi4 with dtoverlay=vc4-fkms-v3d in config.txt
Is/can freerdp be set to use h264 hw acceleration?
-
If Xorg-3d is too slow in the freerdp window, you could try replacing dtoverlay=vc4-kms-v3d-pi4 with dtoverlay=vc4-fkms-v3d in config.txt
i just tried that, the freerdp is soo slow :(
Is/can freerdp be set to use h264 hw acceleration?
i actually don't know what does that mean, but i am gonna definitly read about it 😅
-
i just tried that, the freerdp is soo slow
Did you reboot after charging the overlay to fkms?
-
i just tried that, the freerdp is soo slow
Did you reboot after charging the overlay to fkms?
yes of course
-
Hi Juanito,
It's perhaps a long shot, but maybe wayland/weston might work better than x11?
A few hints here: http://forum.tinycorelinux.net/index.php/topic,23269.msg150229.html
sorry but this will not be the solution for me.
i realy need to get it work with fbturbo, could we get another version of it maybe ? :(
Here is my Xorg.log maybe you will see something i didn't see :-\
-
Did you try weston?
As explained earlier, there has not been an update to the fbturbo source code for a long time - as far as I know, the piCore fbturbo extension uses the latest code.
-
Did you try weston?
As explained earlier, there has not been an update to the fbturbo source code for a long time - as far as I know, the piCore fbturbo extension uses the latest code.
yes i tried weston but not with xfreerdp, but i already had some automatism in Xorg and if i used weston, i have do do everything over again. That is why i want to find an solution that works with Xorg :-\
-
xf86-video-fbdev added to the repo - you could try that instead of xf86-video-fbturbo.
-
Hi Juanito,
xf86-video-fbdev added to the repo - you could try that instead of xf86-video-fbturbo.
so with this step i am realy moving forward :)
The xf86-video-fbdev did help a little bit, i mean now i can use Xrandr to set my Monitors like i want and that is cool
the second thing is, that xfreerdp is a little bit faster but i don't think that somebody would like to work on the session, because every window need some seconds to load.
any other tips? ;D
-
Hi Rabie
If you run:
xfreerdp --helpIt should list available options, for example:
-x: performance flags (m[odem], b[roadband] or l[an])Try setting it to modem.
Maybe track down the documentation to see how various other flags affect performance.
-
You could also try using the client with options "/gfx:AVC420" or "/gfx:AVC444" to try to force freerdp to use the RPi h264 hardware acceleration.
-
so here are the options i tried until yet:
gdi:hw
/network:[modem|broadband|broadband-low|broadband-high|wan|lan|auto] (Best one was the /network:auto)
+gfx-thin-client
+gfx-small-cache
+gfx-progressive
i tried them together and separated
You could also try using the client with options "/gfx:AVC420" or "/gfx:AVC444" to try to force freerdp to use the RPi h264 hardware acceleration.
with those two freerdp says that some parameter is wrong
after all it is so slow (look at the Video)
https://www.file2send.eu/de/download/ALHlha4a5ucfTqfvbZDdXOGwahrUMfA4mPGVVXDpDrXy7XKkFDqHCq11SoW2oTMf
-
with those two freerdp says that some parameter is wrong
Please post the exact error message - maybe you need /gfx-h264:AVC444?
What does /buildconfig show about h264 on the freerdp client and server?
-
Ah - I see:
$ xfreerdp /buildconfig
..WITH_FFMPEG=OFF WITH_GFX_H264=OFF WITH_X264=OFF
-
freerdp updated:
$ xfreerdp /buildconfig
This is FreeRDP version 2.4.0 (2.4.0)
Build configuration:
...
WITH_FFMPEG=TRUE WITH_GFX_H264=ON
-
After realising I could set a windows machine as an rdp server, I did a test using freerdp in piCore64 - there was a noticeable speed up with /gfx-h264:AVC444
-
Hi Juanito,
After realising I could set a windows machine as an rdp server, I did a test using freerdp in piCore64 - there was a noticeable speed up with /gfx-h264:AVC444
now i updated freerdp and tried this options:
/gfx-h264:AVC444
/gfx:AVC444
/gfx:AVC420
i noticed that freerdp is much faster with /gfx-h264:AVC444 but just on one Monitor, when i connect the second Monitor it goes again to be so slow :-\
-
Are you using /multimon?
-
Are you using /multimon?
yes, this is what i am using:
xfreerdp /sec:rdp /drive:USB-Stick,/mnt/ /gfx-h264:AVC444 /multimon:force +multitransport +auto-reconnect -themes -wallpaper /cert-ignore /bpp:15 /kbd:0x00000407 /d:domain /v:server:3389 /f
-
Maybe you can ask on the freerdp github site why multi-mon is slow compared to single?
-
Hi Juanito,
Maybe you can ask on the freerdp github site why multi-mon is slow compared to single?
i will try that but to be honest i do not think that the freerdp is the problem.
Because i use the same thing on tinycore with fbturbo and there is no problem.
i think that xf86-video-fbdev is not enough :'( :'(
-
Neither xf86-video-fbdev nor xf86-video-fbturbo exist in Tinycore, so unless you compiled them yourself, you must be using something else.
When testing freerdp with Xorg-3d and one screen, I found using /gfx-h264:AVC444 increased the speed - since xf86-video-fbturbo stops Xorg-3d acceleration from working, I suspect you would be better off without it.
-
i am sorry i am using xf86-video-intel.tcz on tinycore
but i will try your idea to use /gfx-h264:AVC444 with Xorg-3d
-
Neither xf86-video-fbdev nor xf86-video-fbturbo exist in Tinycore, so unless you compiled them yourself, you must be using something else.
When testing freerdp with Xorg-3d and one screen, I found using /gfx-h264:AVC444 increased the speed - since xf86-video-fbturbo stops Xorg-3d acceleration from working, I suspect you would be better off without it.
so i tried that but it didn't help (Look at the videos )
https://www.file2send.eu/de/download/qnrqHkpQFQvWl55zZ51pWvbnsYss4tUH5TQpe6J7afVqtdNUSfQswhaqOGWDlNsn
that is why i think that isn't a problem from freerdp but it's from the driver because it's just so fast with fbturbo
-
Do you have the latest v4l-dvb-5.10.16-piCore-v7 extension?
Are you sure Xorg is running with 3d hardware acceleration?
$ glxinfo | grep Acc
Accelerated: yes
-
Hi Juanito,
Do you have the latest v4l-dvb-5.10.16-piCore-v7 extension?
i didn't had this one but i installed it and no difference
Are you sure Xorg is running with 3d hardware acceleration?
yes i am sure
here tc@box:~$ glxinfo |grep Acc
Accelerated: yes
now im trying since days to get this work out, there must be an solution :( :(
-
Is the h264 hardware decoder present - /dev/video10?
edit: if it is present, maybe you need to increase gpu memory in config.txt
-
Hi Juanito,
Is the h264 hardware decoder present - /dev/video10?
edit: if it is present, maybe you need to increase gpu memory in config.txt
yes this is what i found
ls /dev/video1
video10 video11 video12 video13 video14 video15 video16
do you mean i have to increase the arm here ? How much ?
#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800
edit: i tried with arm_freq=1000, didn't help
-
Try gpu_mem=128 with Xorg-3d and, if that doesn’t work, 256.
-
Hi Juanito,
Try gpu_mem=128 with Xorg-3d and, if that doesn’t work, 256.
unfortunately both options did not work, gpu_mem=128 or 256 didn't exist in config.txt but i placed it there my self
it didn't help not even a little bit
-
Did you place it on the right line ?
You have to place it under [ALL] section or under [PI4] section.
-
After reboot, you can check using the rpi-vc extension:
$ sudo vcgencmd get_mem gpu
gpu=256M
-
Did you place it on the right line ?
You have to place it under [ALL] section or under [PI4] section.
yes i did
After reboot, you can check using the rpi-vc extension:
Code: [Select]
$ sudo vcgencmd get_mem gpu
gpu=256M
and now i checked for it and tried it again but there is no difference
tc@box:~$ sudo vcgencmd get_mem gpu
gpu=256M
-
Have you tried the freerdp switch /gdi:hw?
-
Hi Juanito,
Have you tried the freerdp switch /gdi:hw?
yes like i said before this ist what i untill now have tried
gdi:hw
/network:[modem|broadband|broadband-low|broadband-high|wan|lan|auto] (Best one was the /network:auto)
+gfx-thin-client
+gfx-small-cache
+gfx-progressive
/gfx-h264:AVC444
/gfx:AVC444
/gfx:AVC420
in config.txt:
gpu_mem=256
dtoverlay=vc4-kms-v3d-pi4
max_framebuffers=2
arm_freq=1000
config_hdmi_boost=4
and like i said before, i don't think that the Hardware or freerdp are causing the problem, because when i switch to fbturbo and run freerdp without any performance parameter like "gdi:hw", it's just running like a rocket
so i think it's just the Graphic driver who's cousing the slow freerdp performance
-
On RPi4, h264 hw acceleration is available via the ffmpeg h264_v4l2m2m decoder - I'd guess that freerdp is not using it. Alternatively, the v3d graphics driver on the RPi4 might be too slow.
Searching the internet reveals several comments stating that freerdp is faster on RPi3 than RPi4, which would tend to support the above.
-
On RPi4, h264 hw acceleration is available via the ffmpeg h264_v4l2m2m decoder - I'd guess that freerdp is not using it. Alternatively, the v3d graphics driver on the RPi4 might be too slow.
Searching the internet reveals several comments stating that freerdp is faster on RPi3 than RPi4, which would tend to support the above.
do you know if there is a way to use dual Monitor on RPi3 ?
-
Hi Juanito,
It's perhaps a long shot, but maybe wayland/weston might work better than x11?
A few hints here: http://forum.tinycorelinux.net/index.php/topic,23269.msg150229.html
so i decided to try wayland as an compromise.
could you please tell me how to configure the Dual Monitors in the extended Mode on weston ?
Thank you
-
Did you check the linux man page for weston.ini?
(It's my understanding that weston will run two monitors in extended mode by default)
-
Did you check the linux man page for weston.ini?
(It's my understanding that weston will run two monitors in extended mode by default)
yes you are right, i made a mistake
so i wanted to try wlfreerdp to see if it is faster than Xorg, but wlfreerdp is starting just on one Monitor and just on the one where i start the following from Terminal
wlfreerdp /sec:rdp /multimon:force +multitransport -mouse-motion +auto-reconnect /cert-ignore /bpp:15 /kbd:0x00000407 /d:domain /v:server:3389 /f
How to get wlfreerdp on both Monitors ? ;D
-
I don't know - you could try asking on the weston/freerdp git sites "issues"?