Go Back   DisplayLink Forum > DisplayLink Graphics Technology > Linux and Open Source

Reply
 
Thread Tools Search this Thread Display Modes
Old 01-16-2017, 02:07 PM   #1
lars22
Junior Member
 
Join Date: Jan 2017
Posts: 1
Default Purple highlights / messed up colors with rasbperry pi

Hi

I'm using latest raspbian. I've pasted my configs below.

Output to primary screen works fine (I've also switched the screens around).

Output to secondary screen (which is via DisplayLink adapter) has weird colors. All hightlights (white and very bright colors) are purple. See attached imgs.

I've tested with B/W images, gifs (less colors). I've taken a screen shot to make sure the image sent to the framebuffer is ok.

$ lsusb
Code:
Bus 001 Device 014: ID 17e9:01e2 DisplayLink
dmesg:
Code:
pi:~ $ dmesg |grep udlfb                                                                                                      
[    6.920686] usbcore: registered new interface driver udlfb
[    7.057700] udlfb: DisplayLink M01061 - serial #000000000000052
[    7.057727] udlfb: vid_17e9&pid_01e2&rev_0001 driver's dlfb_data struct at b5aaf000
[    7.057736] udlfb: console enable=1
[    7.057743] udlfb: fb_defio enable=1
[    7.057751] udlfb: shadow enable=1
[    7.057946] udlfb: vendor descriptor length:22 data:22 5f 01 00 20 05 00 01 03 00 04
[    7.057961] udlfb: DL chip limited to 2360000 pixel modes
[    7.059056] udlfb: allocated 4 65024 byte urbs
[    7.138212] udlfb: 800x480 @ 65 Hz valid mode
[    7.138244] udlfb: Reallocating framebuffer. Addresses will change!
[    7.139845] udlfb: 800x480 @ 65 Hz valid mode
[    7.139873] udlfb: set_par mode 800x480
[    7.147155] udlfb: DisplayLink USB device /dev/fb1 attached. 800x480 resolution. Using 1504K framebuffer memory
[  125.700211] udlfb: open /dev/fb1 user=1 fb_info=b2444400 count=1
[  125.700266] udlfb: released /dev/fb1 user=1 count=0
[  125.703910] udlfb: open /dev/fb1 user=1 fb_info=b2444400 count=1
[  125.719903] udlfb: /dev/fb1 FB_BLANK mode 0 --> 1
[  125.729756] udlfb: open /dev/fb1 user=1 fb_info=b2444400 count=2
[  125.729837] udlfb: released /dev/fb1 user=1 count=1
[  126.484218] udlfb: /dev/fb1 FB_BLANK mode 1 --> 0
/usr/share/X11/xorg.conf.d/99-fb.conf:
Code:
Section "Device"
# RPi builtin video, framebuffer 0
  Identifier "rpi"
  driver "fbturbo"
  Option "fbdev" "/dev/fb0"
EndSection

Section "Device"
# USB DisplayLink video, framebuffer 1
  Identifier "uga"
  driver "fbturbo"
  Option "fbdev" "/dev/fb1"
EndSection

Section "Monitor"
  Identifier "touch"
EndSection

Section "Monitor"
  Identifier "nontouch"
EndSection

Section "Screen"
  Identifier "primary"
  Device "rpi"
  Monitor "touch"
  SubSection "Display"
    Depth   16
    Modes   "800x480"
  EndSubSection
EndSection

Section "Screen"
  Identifier "secondary"
  Device "uga"
  Monitor "nontouch"
  SubSection "Display"
    Depth   16
    Modes   "800x480"
  EndSubSection
EndSection

Section "ServerLayout"
  Identifier "default"
  Screen 0 "primary" 0 0
# The HP is 26 pixels higher than the Dell. Align the screens along the monitors bottom edges,
# so the status bar is visible on both monitors.
 Screen 1 "secondary" 800 0
# If both monitors are the same height, you can just do:
# Screen 1 "secondary" RightOf "primary"
# Option   "Xinerama" "1"  # enable XINERAMA extension.  Default is disabled.
EndSection
Edit:
I've tried changing Depth in framebuffer config to 24 for both. No difference.
Attached Images
File Type: jpg IMG_20170116_150402.jpg (96.1 KB, 1 views)
File Type: jpg IMG_20170116_150356.jpg (91.3 KB, 1 views)

Last edited by lars22; 01-16-2017 at 02:08 PM. Reason: Depth in framebuffer config
lars22 is offline   Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT. The time now is 05:39 PM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2024, vBulletin Solutions, Inc.