DisplayLink

[Rabie]

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:

Code: [Select]

FBTURBO(0): Virtual size is 720x480 (pitch 720)could you find anything ?

[Juanito]

The piCore default is:

Code: [Select]

$ 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:

Code: [Select]

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.

[Paul_123]

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.

[Juanito]

Ah - so it is, I learnt something there 

[Rabie]

Hi Juanito,

The piCore default is:

Code: [Select]

$ 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:

Code: [Select]

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:

Code: [Select]

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]

[Rich]

Hi Rabie
I don't think the  vga=  boot code is valid for Raspberry pi.

I also noticed this in your log file:

Code: [Select]

[    47.806] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support

[Rabie]

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:

Code: [Select]

[    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 

[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:

Code: [Select]

$ xrandr —listproviders ..give?

See also archwiki displaylink.

[Rabie]

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:

Code: [Select]

$ xrandr —listproviders ..give?

See also archwiki displaylink.

this:

Code: [Select]

xrandr --listproviders
Providers: number : 0