New IT forum
25 February 2018, 01:37:38 am *
Welcome, %1$s. Please login or register.

: CubieBoard 2 and Cubietruck both now in stock.
 
Pages: [1]

Author Topic: Mimo Monitor problem  (Read 5585 times)

bkceaf

  • Newbie
  • *
  • Posts: 2
Mimo Monitor problem
« on: 06 March 2014, 06:12:19 pm »

I am having some trouble keeping a mimo magic monster monitor connected to my dreamplug running guiplug 2.6 on an external sd card.  The green screen will appear, but only stays a second before blacking out for 2-3 seconds and then coming back.  The dmesg log is a big loop of the following:

Code: [Select]
usb 1-1.2: new high speed USB device using orion-ehci and address 16
hub 1-1.2:1.0: USB hub found
hub 1-1.2:1.0: 2 ports detected
usb 1-1.2.1: new high speed USB device using orion-ehci and address 17
udlfb: DisplayLink Mimo Magic Monster - serial #MM1312300003
udlfb: vid_17e9&pid_016b&rev_0507 driver's dlfb_data struct at de2d0800
udlfb: console enable=0
udlfb: fb_defio enable=1
udlfb: vendor descriptor length:17 data:17 5f 01 0015 05 00 01 03 00 04
udlfb: DL chip limited to 700000 pixel modes
udlfb: allocated 4 65024 byte urbs
udlfb: 1024x600 valid mode
udlfb: Reallocating framebuffer. Addresses will change!
udlfb: 1024x600 valid mode
udlfb: set_par mode 1024x600
udlfb: DisplayLink USB device /dev/fb0 attached. 1024x600 resolution. Using 2400K framebuffer memory
usb 1-1.2.2: new full speed USB device using orion-ehci and address 18
input: eGalax Inc. USB TouchController as /devices/platform/orion-ehci.0/usb1/1-1/1-1.2/1-1.2.2/1-1.2.2:1.0/input/input7
input: eGalax Inc. USB TouchController as /devices/platform/orion-ehci.0/usb1/1-1/1-1.2/1-1.2.2/1-1.2.2:1.0/input/input8
generic-usb 0003:0EEF:0001.0005: input: USB HID v2.10 Pointer [eGalax Inc. USB TouchController] on usb-orion-ehci.0-1.2.2/input0
usb 1-1.2: USB disconnect, address 16
usb 1-1.2.1: USB disconnect, address 17
udlfb: USB disconnect starting
udlfb: fb_info for /dev/fb0 has been freed
udlfb: Waiting for completes and freeing all render urbs
udlfb: freeing dlfb_data de2d0800
usb 1-1.2.2: USB disconnect, address 18
usb 1-1.2: new high speed USB device using orion-ehci and address 19
hub 1-1.2:1.0: USB hub found
hub 1-1.2:1.0: 2 ports detected
usb 1-1.2.1: new high speed USB device using orion-ehci and address 20
udlfb: DisplayLink Mimo Magic Monster - serial #MM1312300003
udlfb: vid_17e9&pid_016b&rev_0507 driver's dlfb_data struct at de2d1800
udlfb: console enable=0
udlfb: fb_defio enable=1
udlfb: vendor descriptor length:17 data:17 5f 01 0015 05 00 01 03 00 04
udlfb: DL chip limited to 700000 pixel modes
udlfb: allocated 4 65024 byte urbs
udlfb: 1024x600 valid mode
udlfb: Reallocating framebuffer. Addresses will change!
udlfb: 1024x600 valid mode
udlfb: set_par mode 1024x600
udlfb: DisplayLink USB device /dev/fb0 attached. 1024x600 resolution. Using 2400K framebuffer memory
usb 1-1.2.2: new full speed USB device using orion-ehci and address 21
input: eGalax Inc. USB TouchController as /devices/platform/orion-ehci.0/usb1/1-1/1-1.2/1-1.2.2/1-1.2.2:1.0/input/input9
input: eGalax Inc. USB TouchController as /devices/platform/orion-ehci.0/usb1/1-1/1-1.2/1-1.2.2/1-1.2.2:1.0/input/input10
generic-usb 0003:0EEF:0001.0006: input: USB HID v2.10 Pointer [eGalax Inc. USB TouchController] on usb-orion-ehci.0-1.2.2/input0
usb 1-1.2: USB disconnect, address 19
usb 1-1.2.1: USB disconnect, address 20
udlfb: USB disconnect starting
udlfb: fb_info for /dev/fb0 has been freed
udlfb: Waiting for completes and freeing all render urbs
udlfb: freeing dlfb_data de2d1800
usb 1-1.2.2: USB disconnect, address 21

My first instinct was that the monitor wasn't getting enough power, but even after plugging the power usb cable into a port on another system, the problem remains the same.  If I reverse which ports on the dreamplug the mimo is pluged into, it cycle so fast I never see the green screen, it sometimes doesn't get past initializing the hub within the mimo.  The reversed USB state will have the same problem even running the default install without udlfb, but the slow connect/disconnect cycle only comes up in guiplug when the display actually starts working.

Any feedback would be welcome.  While it feels like a power issue, the quick tests so far are making that seem less likely, and I am hoping someone else out there has seen something like this before.

Additional information
2 different Mimo Monsters display the same behaviour, and both work fine when used on a windows machine.
VNC connections also work fine.
If you are curious why 2.6 not 2.7, 2.7 would not fit on the SD card I had handy.
Logged

Confusticated

  • New IT customer
  • Hero Member
  • *
  • Posts: 662
Re: Mimo Monitor problem
« Reply #1 on: 06 March 2014, 06:52:41 pm »

Quote
My first instinct was that the monitor wasn't getting enough power
I would agree.

Quote
plugging the power usb cable into a port on another system
I would not regard this as a good test strategy in this case.

Quote
If I reverse which ports on the dreamplug... it cycle so fast
This is curious, it should make no difference.

Have you tried another USB to Mimo lead to confirm it is not faulty (you don't say if you used the same lead in your tests) ?

I would also try powering the Dreamplug itself from an alternative source to it's purpose built power supply.
Logged
Advocatus Diaboli - My agenda is not to give you the answer, but to guide your thoughts so you derive it for yourself!

bkceaf

  • Newbie
  • *
  • Posts: 2
Re: Mimo Monitor problem
« Reply #2 on: 06 March 2014, 07:25:24 pm »

Thanks Confusticated, good line of thought. 
It seems like the problem is with the mimo monster's base.  If I plug the cable directly into the screen, it is working fine.  If I connect the Monster to the weighted base, and the cable to the base as well, I get the flickering. 
Logged
Pages: [1]
 
 

Powered by MySQL Powered by PHP SMF 2.0.10 | SMF © 2015, Simple Machines Valid XHTML 1.0! Valid CSS!