When trying to compile displaylink-mod-0.3 on kernel 2.6.32.2 with UDLFB compiled into the kernel I get the following error message.... Sorry if this has been covered before :-) root@workstation:/home/shotsy# tar xzvf displaylink-mod-0.3.tar.gz displaylink/ displaylink/displaylink.h displaylink/displaylink-usb.c displaylink/modules.order displaylink/displaylink-fb.c displaylink/Makefile displaylink/drm_edid.h displaylink/displaylink-main.c displaylink/displaylink-blit.c displaylink/displaylink-ioctl.c displaylink/Module.markers root@workstation:/home/shotsy# cd displaylink root@workstation:/home/shotsy/displaylink# ls Makefile displaylink-blit.c displaylink-fb.c displaylink-main.c displaylink-usb.c drm_edid.h Module.markers displaylink-blit.o displaylink-ioctl.c displaylink-main.o displaylink.h modules.order root@workstation:/home/shotsy/displaylink# make make -C /lib/modules/`uname -r`/build SUBDIRS=/home/shotsy/displaylink modules make[1]: Entering directory `/usr/src/linux-2.6.32.2' CC [M] /home/shotsy/displaylink/displaylink-main.o CC [M] /home/shotsy/displaylink/displaylink-usb.o /home/shotsy/displaylink/displaylink-usb.c: In function 'displaylink_edid_to_reg': /home/shotsy/displaylink/displaylink-usb.c:85: error: 'struct detailed_pixel_timing' has no member named 'hactive_hi' /home/shotsy/displaylink/displaylink-usb.c:91: error: 'struct detailed_pixel_timing' has no member named 'vactive_hi' /home/shotsy/displaylink/displaylink-usb.c:97: error: 'struct detailed_pixel_timing' has no member named 'hblank_hi' /home/shotsy/displaylink/displaylink-usb.c:97: error: 'struct detailed_pixel_timing' has no member named 'hsync_offset_hi' /home/shotsy/displaylink/displaylink-usb.c:101: error: 'struct detailed_pixel_timing' has no member named 'vblank_hi' /home/shotsy/displaylink/displaylink-usb.c:101: error: 'struct detailed_pixel_timing' has no member named 'vsync_offset_hi' /home/shotsy/displaylink/displaylink-usb.c:101: error: 'struct detailed_pixel_timing' has no member named 'vsync_offset_lo' /home/shotsy/displaylink/displaylink-usb.c:105: error: 'struct detailed_pixel_timing' has no member named 'hblank_hi' /home/shotsy/displaylink/displaylink-usb.c:106: error: 'struct detailed_pixel_timing' has no member named 'hsync_pulse_width_hi' /home/shotsy/displaylink/displaylink-usb.c:109: error: 'struct detailed_pixel_timing' has no member named 'vblank_hi' /home/shotsy/displaylink/displaylink-usb.c:110: error: 'struct detailed_pixel_timing' has no member named 'vsync_pulse_width_hi' /home/shotsy/displaylink/displaylink-usb.c:110: error: 'struct detailed_pixel_timing' has no member named 'vsync_pulse_width_lo' /home/shotsy/displaylink/displaylink-usb.c: In function 'displaylink_set_video_mode': /home/shotsy/displaylink/displaylink-usb.c:242: warning: format '%d' expects type 'int', but argument 3 has type 'long int' /home/shotsy/displaylink/displaylink-usb.c:249: error: 'struct detailed_pixel_timing' has no member named 'hactive_hi' /home/shotsy/displaylink/displaylink-usb.c: In function 'displaylink_setup': /home/shotsy/displaylink/displaylink-usb.c:308: error: 'struct detailed_pixel_timing' has no member named 'hactive_hi' /home/shotsy/displaylink/displaylink-usb.c:311: error: 'struct detailed_pixel_timing' has no member named 'hactive_hi' /home/shotsy/displaylink/displaylink-usb.c:312: error: 'struct detailed_pixel_timing' has no member named 'vactive_hi' make[2]: *** [/home/shotsy/displaylink/displaylink-usb.o] Error 1 make[1]: *** [_module_/home/shotsy/displaylink] Error 2 make[1]: Leaving directory `/usr/src/linux-2.6.32.2' make: *** [all] Error 2 root@workstation:/home/shotsy/displaylink# Also are we any closer to getting 24bit color working on the MIMO UM-710? Thanks, Ken <div class="gmail_quote">On Sat, Dec 19, 2009 at 2:00 PM, <<a href="mailto:libdlo-request@lists.freedesktop.org">libdlo-request@lists.freedesktop.org</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Send Libdlo mailing list submissions to <a href="mailto:libdlo@lists.freedesktop.org">libdlo@lists.freedesktop.org</a> To subscribe or unsubscribe via the World Wide Web, visit <a href="http://lists.freedesktop.org/mailman/listinfo/libdlo" target="_blank">http://lists.freedesktop.org/mailman/listinfo/libdlo</a> or, via email, send a message with subject or body 'help' to <a href="mailto:libdlo-request@lists.freedesktop.org">libdlo-request@lists.freedesktop.org</a> You can reach the person managing the list at <a href="mailto:libdlo-owner@lists.freedesktop.org">libdlo-owner@lists.freedesktop.org</a> When replying, please edit your Subject line so it is more specific than "Re: Contents of Libdlo digest..." Today's Topics: 1. (no subject) (James) 2. GOT THE GREEN SCREEN!!! (James) 3. My xorg.conf file... (<a href="mailto:sammy@sammyjames.com">sammy@sammyjames.com</a>) 4. Re: My xorg.conf file... (Bernie Thompson) 5. How do I get xorg to recognize the Displaylink device...? (James) 6. Re: How do I get xorg to recognize the Displaylink device...? (Bernie Thompson) ---------------------------------------------------------------------- Message: 1 Date: Fri, 18 Dec 2009 23:14:21 -0600 From: "James" <<a href="mailto:sammy@sammyjames.com">sammy@sammyjames.com</a>> Subject: [Libdlo] (no subject) To: <<a href="mailto:libdlo@lists.freedesktop.org">libdlo@lists.freedesktop.org</a>> Message-ID: <5866B02A8CE74E0EA5583ACECB6B6755@SammyPC> Content-Type: text/plain; charset="iso-8859-1" I finally got the mod 0.3 patch to compile properly. Replaced the drm_edid.h, and it worked! I just used the one that came with the displaylink-mod folder. I still haven't gotten the display to work, but at least I didn't get errors when firing off make. :) -------------- next part -------------- An HTML attachment was scrubbed... URL: <a href="http://lists.freedesktop.org/archives/libdlo/attachments/20091218/dc38eb7e/attachment-0001.html" target="_blank">http://lists.freedesktop.org/archives/libdlo/attachments/20091218/dc38eb7e/attachment-0001.html</a> ------------------------------ Message: 2 Date: Sat, 19 Dec 2009 00:27:52 -0600 From: "James" <<a href="mailto:sammy@sammyjames.com">sammy@sammyjames.com</a>> Subject: [Libdlo] GOT THE GREEN SCREEN!!! To: <<a href="mailto:libdlo@lists.freedesktop.org">libdlo@lists.freedesktop.org</a>> Message-ID: <1E3FF7E0BB9A465983DA203A47FEA707@SammyPC> Content-Type: text/plain; charset="iso-8859-1" Woo-hoo!!! I KNOW that I'm getting close. I just need one final push to get me over the edge. Just tell me one thing -- do I need to make any changes to the xorg.conf file? Does the computer USE that file to set things up, or does it simply reflect the status of what is on your system? By the way -- I had already downloaded and compiled the mod 0.3 stuff, but I went back and recompiled and installed the older udlfb drivers. That is when I got the green screen. If anyone can tell me where to go from here, I would appreciate it SO much. And if I get this thing to work, then I will definitely publish here a dissertation on the steps that I took in an effort to help others to do the same thing. Thanks. - Sammy -------------- next part -------------- An HTML attachment was scrubbed... URL: <a href="http://lists.freedesktop.org/archives/libdlo/attachments/20091219/6e293259/attachment.htm" target="_blank">http://lists.freedesktop.org/archives/libdlo/attachments/20091219/6e293259/attachment.htm</a> ------------------------------ Message: 3 Date: Sat, 19 Dec 2009 00:57:18 -0500 From: <a href="mailto:sammy@sammyjames.com">sammy@sammyjames.com</a> Subject: [Libdlo] My xorg.conf file... To: <a href="mailto:libdlo@lists.freedesktop.org">libdlo@lists.freedesktop.org</a> Message-ID: <<a href="mailto:391211dc219021f967bf8308a5776a2b.squirrel@email.fatcow.com">391211dc219021f967bf8308a5776a2b.squirrel@email.fatcow.com</a>> Content-Type: text/plain;charset=iso-8859-1 Okay -- now that I finally got both the mod 0.3 drivers installed (I guess) and the xorg.conf file automatically generated, I took a gander at said file. I have no idea whether this means anything -- maybe someone here can explain what all of this means... - Sammy Below is the entire text from my xorg.conf: Section "ServerLayout" Identifier "X.org Configured" Screen 0 "Screen0" 0 0 InputDevice "Mouse0" "CorePointer" InputDevice "Keyboard0" "CoreKeyboard" EndSection Section "Files" ModulePath "/usr/lib/xorg/modules" FontPath "/usr/share/fonts/X11/misc" FontPath "/usr/share/fonts/X11/cyrillic" FontPath "/usr/share/fonts/X11/100dpi/:unscaled" FontPath "/usr/share/fonts/X11/75dpi/:unscaled" FontPath "/usr/share/fonts/X11/Type1" FontPath "/usr/share/fonts/X11/100dpi" FontPath "/usr/share/fonts/X11/75dpi" FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType" FontPath "built-ins" EndSection Section "Module" Load "glx" Load "record" Load "dri2" Load "extmod" Load "dbe" Load "dri" EndSection Section "InputDevice" Identifier "Keyboard0" Driver "kbd" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/input/mice" Option "ZAxisMapping" "4 5 6 7" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Monitor Vendor" ModelName "Monitor Model" EndSection Section "Device" ### Available Driver options are:- ### Values: : integer, <f>: float, <bool>: "True"/"False", ### <string>: "String", <freq>: "<f> Hz/kHz/MHz" ### [arg]: arg optional #Option "NoAccel" # [<bool>] #Option "SWcursor" # [<bool>] #Option "ColorKey" # #Option "CacheLines" # #Option "Dac6Bit" # [<bool>] #Option "DRI" # [<bool>] #Option "NoDDC" # [<bool>] #Option "ShowCache" # [<bool>] #Option "XvMCSurfaces" # #Option "PageFlip" # [<bool>] Identifier "Card0" Driver "intel" VendorName "Intel Corporation" BoardName "4 Series Chipset Integrated Graphics Controller" BusID "PCI:0:2:0" EndSection Section "Screen" Identifier "Screen0" Device "Card0" Monitor "Monitor0" SubSection "Display" Viewport 0 0 Depth 1 EndSubSection SubSection "Display" Viewport 0 0 Depth 4 EndSubSection SubSection "Display" Viewport 0 0 Depth 8 EndSubSection SubSection "Display" Viewport 0 0 Depth 15 EndSubSection SubSection "Display" Viewport 0 0 Depth 16 EndSubSection SubSection "Display" Viewport 0 0 Depth 24 EndSubSection EndSection ------------------------------ Message: 4 Date: Sat, 19 Dec 2009 08:38:39 -0800 From: Bernie Thompson <<a href="mailto:bernie@berniethompson.com">bernie@berniethompson.com</a>> Subject: Re: [Libdlo] My xorg.conf file... To: <a href="mailto:sammy@sammyjames.com">sammy@sammyjames.com</a> Cc: <a href="mailto:libdlo@lists.freedesktop.org">libdlo@lists.freedesktop.org</a> Message-ID: <<a href="mailto:480988180912190838w2dd1e572r159a70c521b3c9a4@mail.gmail.com">480988180912190838w2dd1e572r159a70c521b3c9a4@mail.gmail.com</a>> Content-Type: text/plain; charset=ISO-8859-1 Hi Sammy, Roberto made a cute and wise choice of that green screen. It's always nice to see when you've struggled to get it. :) Any write-ups are valuable at this point, so thanks for anything you come up with, no matter how simple (including "just don't do this"). Adding anything for mere mortal users to <a href="http://libdlo.freedesktop.org/wiki/HowTo" target="_blank">http://libdlo.freedesktop.org/wiki/HowTo</a> is particularly valuable. Luke did a great job last month exploring a bunch of these issues. He wrote up his experiences at <a href="http://lists.freedesktop.org/archives/libdlo/2009-November/000446.html" target="_blank">http://lists.freedesktop.org/archives/libdlo/2009-November/000446.html</a> Bernie ------------------------------ Message: 5 Date: Sat, 19 Dec 2009 13:00:04 -0600 From: "James" <<a href="mailto:sammy@sammyjames.com">sammy@sammyjames.com</a>> Subject: [Libdlo] How do I get xorg to recognize the Displaylink device...? To: <<a href="mailto:libdlo@lists.freedesktop.org">libdlo@lists.freedesktop.org</a>> Message-ID: <667ECC6490D842FEBA7CD06113B59B68@SammyPC> Content-Type: text/plain; charset="iso-8859-1" 1. It would be great if xorg could pick up my Displaylink device automatically, the way that it does with all of the other connected components on my computer... 2. It would be EXTREMELY great if I could figure out how to switch the "main" display, which is obviously the VGA one, with the Displaylink one. When this happens, then I'll be jumping up and down. I'm SO CLOSE. I just need to isolate the drivers and figure out how to get xorg to recognize them. Then I can probably just tell xorg which screen to put where, and then things will be good. -------------- next part -------------- An HTML attachment was scrubbed... URL: <a href="http://lists.freedesktop.org/archives/libdlo/attachments/20091219/ccc9ea05/attachment.htm" target="_blank">http://lists.freedesktop.org/archives/libdlo/attachments/20091219/ccc9ea05/attachment.htm</a> ------------------------------ Message: 6 Date: Sat, 19 Dec 2009 11:12:24 -0800 From: Bernie Thompson <<a href="mailto:bernie@berniethompson.com">bernie@berniethompson.com</a>> Subject: Re: [Libdlo] How do I get xorg to recognize the Displaylink device...? To: James <<a href="mailto:sammy@sammyjames.com">sammy@sammyjames.com</a>> Cc: <a href="mailto:libdlo@lists.freedesktop.org">libdlo@lists.freedesktop.org</a> Message-ID: <<a href="mailto:480988180912191112g25728b1fo2834e7eeb01045d6@mail.gmail.com">480988180912191112g25728b1fo2834e7eeb01045d6@mail.gmail.com</a>> Content-Type: text/plain; charset=ISO-8859-1 Hi Sammy, I assume you've already seen this, but the multiseat setup I use on my machines here switches from xorg default (accelerated Intel) to DisplayLink at GDM start time, based on whether a USB display/terminal is present: <a href="http://plugable.com/2009/11/16/setting-up-usb-multiseat-with-displaylink-on-linux-gdm-up-to-2-20/" target="_blank">http://plugable.com/2009/11/16/setting-up-usb-multiseat-with-displaylink-on-linux-gdm-up-to-2-20/</a> Now, this stuff won't work on Ubuntu 9.10 unless you downgrade GDM version (but that can be done: <a href="http://www.ubuntugeek.com/how-to-downgrade-gnome-display-manager-2-28-to-2-20-in-ubuntu-9-10-karmic.html" target="_blank">http://www.ubuntugeek.com/how-to-downgrade-gnome-display-manager-2-28-to-2-20-in-ubuntu-9-10-karmic.html</a> ) Bernie On Sat, Dec 19, 2009 at 11:00 AM, James <<a href="mailto:sammy@sammyjames.com">sammy@sammyjames.com</a>> wrote: > 1. It would be great if xorg could pick up my Displaylink device > automatically, the way that it does with all of the other connected > components on my computer... > > 2. It would be EXTREMELY great if I could figure out how to switch the > "main" display, which is obviously the VGA one, with the Displaylink one. > When this happens, then I'll be jumping up and down. > > I'm SO CLOSE. I just need to isolate the drivers and figure out how to get > xorg to recognize them. Then I can probably just tell xorg which screen to > put where, and then things will be good. > _______________________________________________ > Libdlo mailing list > <a href="mailto:Libdlo@lists.freedesktop.org">Libdlo@lists.freedesktop.org</a> > <a href="http://lists.freedesktop.org/mailman/listinfo/libdlo" target="_blank">http://lists.freedesktop.org/mailman/listinfo/libdlo</a> > > ------------------------------ _______________________________________________ Libdlo mailing list <a href="mailto:Libdlo@lists.freedesktop.org">Libdlo@lists.freedesktop.org</a> <a href="http://lists.freedesktop.org/mailman/listinfo/libdlo" target="_blank">http://lists.freedesktop.org/mailman/listinfo/libdlo</a> End of Libdlo Digest, Vol 8, Issue 11 ************************************* </blockquote></div>