Tiny Core Linux
Tiny Core Extensions => TCE Talk => Extension requests => Topic started by: Rabie on September 23, 2021, 05:02:20 AM
-
Hi There,
is there any driver Extension for the displaylink vga to usb Adapter ?
Something like this: https://www.otto.de/p/i-tec-display-adapter-usb-vga-advance-computer-kabel-C1263118070/#variationId=1263118093
Thank you
-
Which architecture and which version?
If I understand correctly, the oem should supply a linux driver?
Edit: If it is a usb2 device, it apparently uses the udl kernel driver already present.
-
Which architecture and which version?
If I understand correctly, the oem should supply a linux driver?
Edit: If it is a usb2 device, it apparently uses the udl kernel driver already present.
piCore V13.x/armv7
it's related to this thread: http://forum.tinycorelinux.net/index.php/topic,25183.75.html#lastPost
i want to use piCore on the RPI3 with dual Monitor to see if the Freerdp session is faster
Yes it is a usb2 Device but i am getting no graphic with it and when i connect the device with windows 10 it work's, thats why i thought there is a driver missing on picore
-
Is the udl driver loaded (if not, load it). Apparently with the driver loaded the usb to vga adapter can be configured with xrandr.
It would be useful to check the oem with lsusb.
-
Hi Rabie
udl.ko is provided by graphics-5.10.16-piCore-v7.tcz:
http://tinycorelinux.net/13.x/armv7/tcz/graphics-5.10.16-piCore-v7.tcz.list
Is that installed?
-
Hi Rabie
If you are using Xorg.tcz make sure graphics-5.10.16-piCore-v7.tcz is listed before it in your onboot.lst file.
-
Hi Juanito,
Is the udl driver loaded (if not, load it). Apparently with the driver loaded the usb to vga adapter can be configured with xrandr.
It would be useful to check the oem with lsusb.
when i use lsusb i get this:
lsusb
Protocol spec without prior Class and Subclass spec at line 23179
Bus 001 Device 004: ID 17e9:02ee DisplayLink
Bus 001 Device 003: ID 0424:ec00 Microchip Technology, Inc. (formerly SMSC) SMSC9512/9514 Fast Ethernet Adapter
Bus 001 Device 002: ID 0424:9514 Microchip Technology, Inc. (formerly SMSC) SMC9514 Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
but when i boot the RPI3 with the DisplayLink i am just getting a green Display the whole time
-
Hi Rich,
Hi Rabie
If you are using Xorg.tcz make sure graphics-5.10.16-piCore-v7.tcz is listed before it in your onboot.lst file.
yes i am using Xorg and graphics-5.10.16-piCore-v7.tcz is installed but i am getting just a green Display with the DisplayLink :-\
-
Hi Rabie
Xorg.tcz must be listed after graphics-5.10.16-piCore-v7.tcz in your onboot.lst file.
-
Does lsmod show udl is loaded?
-
Hi Rich,
Hi Rabie
Xorg.tcz must be listed after graphics-5.10.16-piCore-v7.tcz in your onboot.lst file.
it is..
openssh.tcz
getlocale.tcz
mylocale.tcz
graphics-5.10.16-piCore-v7.tcz
Xorg.tcz
openbox.tcz
-
Hi Juanito,
Does lsmod show udl is loaded?
tc@box:~$ lsmod
Module Size Used by Tainted: G
udl 20480 0
drm_kms_helper 241664 1 udl
drm 524288 2 udl,drm_kms_helper
drm_panel_orientation_quirks 16384 1 drm
backlight 20480 1 drm
brcmfmac 299008 0
brcmutil 20480 1 brcmfmac
udlfb 28672 0
fb_sys_fops 16384 2 drm_kms_helper,udlfb
sysfillrect 16384 2 drm_kms_helper,udlfb
syscopyarea 16384 2 drm_kms_helper,udlfb
sysimgblt 16384 2 drm_kms_helper,udlfb
cfg80211 798720 1 brcmfmac
snd_bcm2835 28672 0
snd_pcm 114688 1 snd_bcm2835
snd_timer 36864 1 snd_pcm
rfkill 32768 1 cfg80211
snd 77824 3 snd_bcm2835,snd_pcm,snd_timer
fixed 16384 0
squashfs 40960 235
zram 28672 1
zsmalloc 28672 1 zram
raspberrypi_hwmon 16384 0
-
Do you get any error messages when you attempt to configure the displaylink with xrandr?
-
Hi Rabie
Does /var/log/Xorg.0.log make any mention of your DisplayLink device?
Just an observation, but I see there is also a frame buffer driver (udlfb) loaded for your DisplayLink device.
-
Hi Juanito,
Do you get any error messages when you attempt to configure the displaylink with xrandr?
yes i get
tc@box:~$ xrandr
xrandr: Failed to get size of gamma for output default
Screen 0: minimum 720 x 480, current 720 x 480, maximum 720 x 480
default connected 720x480+0+0 0mm x 0mm
720x480 0.00*
i guess because of FBTURBO again ?
Xorg-3d didn't work also
-
Hi Rich,
Hi Rabie
Does /var/log/Xorg.0.log make any mention of your DisplayLink device?
Just an observation, but I see there is also a frame buffer driver (udlfb) loaded for your DisplayLink device.
i think it says that FBTURBO is loaded and can't recognize any Monitor thats why it say also:
FBTURBO(0): Virtual size is 720x480 (pitch 720)could you find anything ?
-
The piCore default is:
$ cat /mnt/mmcblk0p1/cmdline.txt
zswap.compressor=lz4 zswap.zpool=z3fold console=tty1 root=/dev/ram0 elevator=deadline rootwait quiet nortc loglevel=3 noembed
..you appear to be using: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 zswap.compressor=lz4 zswap.zpool=z3fold console=/dev/null root=/dev/ram0 elevator=deadline rootwait quiet nortc loglevel=3 noembed lang=de_DE.UTF-8 kmap=de waitusb=5 logo.nologo=1 vga=795
I would suggest using xf86-video-fbdev instead of xf86-video-fbturbo, remove bcm2708_fb.fbwidth=720, bcm2708_fb.fbheight=480, bcm2708_fb.fbswap=1, vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 and vga=795 and try again.
-
The rpi firmware is injecting that extra stuff into the command line based on what it is detecting (or not detecting)
The fbwidth and fbheight can be overridden in the config.txt using the
framebuffer_width and framebuffer_height directives.
-
Ah - so it is, I learnt something there :)
-
Hi Juanito,
The piCore default is: $ cat /mnt/mmcblk0p1/cmdline.txt
zswap.compressor=lz4 zswap.zpool=z3fold console=tty1 root=/dev/ram0 elevator=deadline rootwait quiet nortc loglevel=3 noembed
..you appear to be using: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=720 bcm2708_fb.fbheight=480 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 zswap.compressor=lz4 zswap.zpool=z3fold console=/dev/null root=/dev/ram0 elevator=deadline rootwait quiet nortc loglevel=3 noembed lang=de_DE.UTF-8 kmap=de waitusb=5 logo.nologo=1 vga=795
I would suggest using xf86-video-fbdev instead of xf86-video-fbturbo, remove bcm2708_fb.fbwidth=720, bcm2708_fb.fbheight=480, bcm2708_fb.fbswap=1, vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 and vga=795 and try again.
this is my cmdline:
cat /mnt/mmcblk0p1/cmdline.txt
zswap.compressor=lz4 zswap.zpool=z3fold console=/dev/null root=/dev/ram0 elevator=deadline rootwait quiet nortc loglevel=3 noembed lang=de_DE.UTF-8 kmap=de waitusb=5 logo.nologo=1 vga=795
so i tried switching to xf86-video-fbdev.tcz but i am getting the same "green screen"
[/code]
-
Hi Rabie
I don't think the vga= boot code is valid for Raspberry pi.
I also noticed this in your log file:
[ 47.806] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
-
Hi Rich,
Hi Rabie
I don't think the vga= boot code is valid for Raspberry pi.
ok i just removed the VGA Code
I also noticed this in your log file:
[ 47.806] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
but i haven't connect the second Monitor yet. i just connected the first one with the displaylink to get this work :-\
-
That (WW) indicates the message is a warning rather than an error.
It appears that the green screen indicates udl is loaded and the displaylink has been found - what does: $ xrandr —listproviders ..give?
See also archwiki displaylink.
-
Hi Juanito,
That (WW) indicates the message is a warning rather than an error.
It appears that the green screen indicates udl is loaded and the displaylink has been found - what does: $ xrandr —listproviders ..give?
See also archwiki displaylink.
this:
xrandr --listproviders
Providers: number : 0