Reply
Thread Tools
Posts: 10 | Thanked: 3 times | Joined on Jan 2011
#1
Hi Guys,

first let me say thank you to many of you. This forum often helped me to solve issues with the n900.

I searched in the forums but was unable to find informations to solve my issue...

I would like to use a displaylink usb vga with the n900 and i have big trouble compiling the kernel module for it.

I have a scratchbox setup and installed the headers for power-kernel46... i can compile the the X module but not the usb driver which can be found here: http://plugable.com/2009/11/11/udlfb-0-4-0/

The problem is: i try to compile it, no error message etc. it just says MODPOST 0 modules, that's it... no files are generated...


Any hints?

thanks,
Chris
 
Posts: 1,994 | Thanked: 3,342 times | Joined on Jun 2010 @ N900: Battery low. N950: torx 4 re-used once and fine; SIM port torn apart
#2
Originally Posted by chris102 View Post
Hi Guys,

first let me say thank you to many of you. This forum often helped me to solve issues with the n900.

I searched in the forums but was unable to find information to solve my issue...

I would like to use a displaylink usb vga with the n900 and i have big trouble compiling the kernel module for it.

I have a scratchbox setup and installed the headers for power-kernel46... i can compile the the X module but not the usb driver which can be found here: http://plugable.com/2009/11/11/udlfb-0-4-0/

The problem is: i try to compile it, no error message etc. it just says MODPOST 0 modules, that's it... no files are generated...


Any hints?

thanks,
Chris
Read here:

How to: Compile Linux kernel modules
http://www.cyberciti.biz/tips/compil...el-module.html

Disclaimer: I don't use scratchbox.
 
Posts: 243 | Thanked: 172 times | Joined on Sep 2007 @ silicon valley
#3
I just got a sisusbvga adapter and was poking for support. It's in the n900 kernel source but doesn't seem to have gotten compiled by default.

Off the top of my head having not touched compiling in a while, the only thought is to check over the makefile for 1. use of the command uname (bad) 2. if it's assuming there are directories which don't exist like some soft links to kernel source directories
 
Posts: 243 | Thanked: 172 times | Joined on Sep 2007 @ silicon valley
#4
Anyway let me know how yours goes and I'll let you know about mine.
 
Posts: 10 | Thanked: 3 times | Joined on Jan 2011
#5
my Driver works!!!!!!!!

anyway a new problem with xorg but i'm close....


here's the output....

(II) Loading extension DRI2
(II) LoadModule: "displaylink"
(II) Loading /usr/lib/xorg/modules/drivers/displaylink_drv.so
(II) Module displaylink: vendor="X.Org Foundation"
compiled for 1.6.99.1, module version = 0.0.1
ABI class: X.Org Video Driver, version 5.0
(II) DL: driver for : displaylink
(WW) Falling back to old probe method for displaylink
(II) Loading sub module "fbdevhw"
(II) LoadModule: "fbdevhw"
(II) Loading /usr/lib/xorg/modules/linux/libfbdevhw.so
(II) Module fbdevhw: vendor="X.Org Foundation"
compiled for 1.6.99.1, module version = 0.0.2
ABI class: X.Org Video Driver, version 5.0
(II) DL(0): using /dev/fb1
(II) resource ranges after probing:
(EE) DL(0): Unknown EDID version 25
(==) DL(0): Depth 24, (--) framebuffer bpp 32
(==) DL(0): RGB weight 888
(==) DL(0): Default visual is TrueColor
(==) DL(0): Using gamma correction (1.0, 1.0, 1.0)
(II) DL(0): hardware: omapfb (video memory: 0kB)
(**) DL(0): Option "fbdev" "/dev/fb1"
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib/xorg/modules/libfb.so
(II) Module fb: vendor="X.Org Foundation"
compiled for 1.6.99.1, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) DL(0): Output omapfb using monitor section DisplayLinkMonitor
(EE) DL(0): Unknown EDID version 68
 
Posts: 10 | Thanked: 3 times | Joined on Jan 2011
#6
my dmesg...


usb 1-1.3: New USB device found, idVendor=17e9, idProduct=01ae
[117126.784820] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[117126.784851] usb 1-1.3: Product: UV PLUS
[117126.784881] usb 1-1.3: Manufacturer: DisplayLink
[117126.784881] usb 1-1.3: SerialNumber: something
[117153.223449] udlfb 1-1.3:1.0: usb_probe_interface
[117153.223510] udlfb 1-1.3:1.0: usb_probe_interface - got id
[117153.223571] udlfb: DisplayLink UV PLUS - serial #01AE-005861
[117153.223602] udlfb: vid_17e9&pid_01ae&rev_0002 driver's dlfb_data struct at cd2da000
[117153.223632] udlfb: console enable=0
[117153.223663] udlfb: fb_defio enable=0
[117153.224060] udlfb: vendor descriptor length:e0 data:00 1e e4 c800 00 00 00 00 00 00
[117153.224090] udlfb: Unrecognized vendor firmware descriptor
[117153.227142] udlfb: allocated 4 65024 byte urbs
[117153.514892] udlfb: Unable to get valid EDID from device/display
[117153.514953] udlfb: unable to find common mode for display and adapter
[117153.515014] udlfb: Waiting for completes and freeing all render urbs
[117153.515319] udlfb: freeing dlfb_data cd2da000
 
Posts: 243 | Thanked: 172 times | Joined on Sep 2007 @ silicon valley
#7
My USB connector broke AGAIN. I am so sick of this crap. Frankly I hope whoever was responsible for the mechanical design of the n900 either "learned their lesson" or got shown the door. I bought an aftermarket warranty; will see how that goes.

What was wrong with compiling?

No clue about the driver. I would try the driver on a desktop system first with first whatever is convenient and probably 2.6.28 there too.
 
Posts: 243 | Thanked: 172 times | Joined on Sep 2007 @ silicon valley
#8
Just to confirm, you are using a powered hub? Does it require 2 USB inputs?
 
Posts: 10 | Thanked: 3 times | Joined on Jan 2011
#9
No it uses only one port... I'm using a powered hub but it is possible to have the n900 poer the device (i tried it).

Compiling... i needed to patch an older version of udlfb... anyway it was not working. For the newer Version i needed to change the Makefile afterwards it was up and running but showing nothing on X (wrong EDID). EDID in fact is a bad thing...

I'm now on the displaylink-mod driver where i needed to change the Makefile as well but it compiles and is loadable...

I tried nearly all displaylink drivers now... and all version combinations.
When the module loads, i get the green screen (for displaylink this means it is working). However Xorg from within maemo starts up but the screen remains green... i get an ioctl eror from omapfb module...

anyway as the kernel module runs now i will install the whole X thing inside of debian to give it a go.

And perhaps i can help you beause i bought a 'docking-station' on ebay - i'm unsure but i think it uses the sisusb....

cheers,
chris
 
Posts: 540 | Thanked: 288 times | Joined on Sep 2009
#10
Hi there, resurrecting the thread, I just got a displaylink chipset using USB-display driver from DX and loads correctly on my ubuntu VM (didn't actually test it since I didn't have a spare monitor at hand then), very eager to try it with N900 and now downloading the kernel sources and cloning the repos.

I'll see what happens, if you have good pointers please throw them my way.
__________________
  • Live near Helsinki, Finland & interested in electronics ? Check this out.
  • Want anti-virus/firewall ? Read this (and follow the links, also: use the search, there are way too many threads asking the same questions over and over and over again).
  • I'm experimenting with BitCoins, if you want to tip me send some to: 1CAEy7PYptSasN67TiMYM74ELDVGZS6cCB
 
Reply


 
Forum Jump


All times are GMT. The time now is 11:40.