USB monitor

[gomw]

Recently, i want to use my USB monitor (samsung 800x480) .

I compiled whole kernel with < Displaylink USB Framebuffer support - ON>

-> is is much bigger than original (2633K vs 4177k)

When i power on , pi reboots spontaneously. ever and ever.. ;-(

But switch off USB monitor, Pi boots normally.

this is the kernel message i dmesged.

what is the matter?? (current limit? )
I guess pi detect the USB monitor(udlfb: DisplayLink Samsung UbiSync Monitor - serial ) but would't use it.
I have no idea at all.

--------------------------------------------------------------------------------------------------------------------------------------
usb 1-1: new high-speed USB device number 2 using dwc_otg
Indeed it is in host mode hprt0 = 00001101
usb 1-1: New USB device found, idVendor=0424, idProduct=9512
usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 3 ports detected
usb 1-1.1: new high-speed USB device number 3 using dwc_otg
usb 1-1.1: New USB device found, idVendor=0424, idProduct=ec00
usb 1-1.1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
smsc95xx v1.0.4
smsc95xx 1-1.1:1.0: eth0: register 'smsc95xx' at usb-bcm2708_usb-1.1, smsc95xx USB 2.0 Ethernet, b8:27:eb:c8:e6:f0
usb 1-1.2: new high-speed USB device number 4 using dwc_otg
usb 1-1.2: New USB device found, idVendor=17e9, idProduct=0103
usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-1.2: Product: Samsung UbiSync Monitor
usb 1-1.2: Manufacturer: DisplayLink
usb 1-1.2: SerialNumber: 0103-000000\xffffffc3\xffffffbf\xffffffbf\xffffffc3\xffffffbf\xffffffbf\xffffffc3\xffffffbf\xffffffbf\xffffffc3\xffffffbf\xffffffbf\xffffffc3\xffffffbf\xffffffbf\xffffffc3\xffffffbf\xffffffbf\xffffffc3\xffffffbf\xffffffbf\xffffffc3\xffffffbf\xffffffbf\xffffffc3\xffffffbf\xffffffbf\xffffffc3\xffffffbf\xffffffbf
udlfb: DisplayLink Samsung UbiSync Monitor - serial #0103-000000\xffffffc3\xffffffbf\xffffffbf\xffffffc3\xffffffbf\xffffffbf\xffffffc3\xffffffbf\xffffffbf\xffffffc3\xffffffbf\xffffffbf\xffffffc3\xffffffbf\xffffffbf\xffffffc3\xffffffbf\xffffffbf\xffffffc3\xffffffbf\xffffffbf\xffffffc3\xffffffbf\xffffffbf\xffffffc3\xffffffbf\xffffffbf\xffffffc3\xffffffbf\xffffffbf
udlfb: vid_17e9&pid_0103&rev_0009 driver's dlfb_data struct at db9db000
udlfb: console enable=1
udlfb: fb_defio enable=1
udlfb: shadow enable=1
udlfb: vendor descriptor not available (-32)
udlfb: allocated 4 65024 byte urbs
udlfb: 800x480 valid mode
udlfb: Reallocating framebuffer. Addresses will change!
udlfb: 800x480 valid mode
udlfb: set_par mode 800x480
udlfb: DisplayLink USB device /dev/fb1 attached. 800x480 resolution. Using 1504K framebuffer memory
usb 1-1.3: new high-speed USB device number 5 using dwc_otg
usb 1-1.3: New USB device found, idVendor=05e3, idProduct=0608
usb 1-1.3: New USB device strings: Mfr=0, Product=1, SerialNumber=0
usb 1-1.3: Product: USB2.0 Hub
hub 1-1.3:1.0: USB hub found

[Vindicator]

Are you using a powered USB hub to fire up this monitor as the Raspi itself could never power that much draw of current even in a newer 2.0 board.
Hopefully you are and if not that is the reason for the continuous reboots, that is what seems to be happening.
The newer 2.0 board has no polyfuses on the ports but stills has a 750ma (I think) polyfuse for the incoming power so there would not be enough power left to power a USB monitor.