DisplayLink external DVI/VGA display on SuperZaxxon firmware: Request for assistance


Xinerama is not working under superzaxxon. Without Xinerama, you have the icons on both screens and it won't let you drag the window to another screen. It's like a screen expander for X, if it's disabled, you have two independent sessions of X running in different screens.

I do wish Xfce would allow me to change the screen resolution on the DisplayLink adapter...
 
Last edited by a moderator:
Palmiga said:
but it didnt work and the Pandora wont start anymore. :wacko:
Click to expand...
Oops.. I never said anything *walks off whistling* :p

Do you have another PC around? You could try xrandr there, maybe via some linux live CD. I've needed this before, can't remember why, heh.

hmc said:
- kuru, your adapter from Pollin might not work. There are different chipsets used. We only support the DisplayLink chipset now, and I don't see any mention about what chipset is used there. My recommendation is to directly search for "DisplayLink" on Amazon or Ebay and only use adpaters that are found using that search word. Then it's quite sure that the adapter will work.


Oh, I see, in a post just a few hours later you say it works. So you did not order it from Pollin but directly bought it there? Do you live near Pfoerring? I do, so then let's meet and share experiences. :-D


- kuru, adapter not working on a hub is not a general problem. Maybe the adapter draws too much power? Is it a powered hub? I have a DL adapter working un an unpowered hub, together with an external mouse and keyboard.
Click to expand...
I've been using a powered hub, aye. It hasn't had any problems with other peripherals so far...

Geez.. yesterday the Pandora made my heart stop for a second - I was experimenting with putting voltage across the power lines of the USB OTG host cable using a battery pack. The little machine didn't take well to me connecting it. I immediately ran dmesg after connecting the battery pack and was able to read "battery temp out of range" which accelerated my hands to near-lightspeed disconnecting it again. Maybe a diode wouldn't be amiss here. Or actually knowing more about electronics than what's black and red, heh.

Edit: Aye we could organize a little get-together. Maybe there's even more central Bavarian Pandora users. Maybe even enough for a Stammtisch? Weißbier and Pandora. Both cool and full of taste to the connoisseur. Stop facepalming already :p
 
Last edited by a moderator:
Takedown said:
Xinerama is not working under superzaxxon. Without Xinerama, you have the icons on both screens and it won't let you drag the window to another screen. It's like a screen expander for X, if it's disabled, you have two independent sessions of X running in different screens.

I do wish Xfce would allow me to change the screen resolution on the DisplayLink adapter...
Click to expand...
I don't care.

It's no problem for me.

No need to rag one window to the other screen.

The too big window is the main problem.

kuru said:
Palmiga said:
but it didnt work and the Pandora wont start anymore. :wacko:
Click to expand...
Oops.. I never said anything *walks off whistling* :p

Do you have another PC around? You could try xrandr there, maybe via some linux live CD. I've needed this before, can't remember why, heh.
Click to expand...
Had the same problem.

I copied the xorg.conf posted here and forgot to press Enter after the last line.

Booting didn't finish.

You can press ALT and Right (D-Pad) during startup.

Then you see what's going on behind the boot screen.

In my case XFCE didn't start but the command line login screen appeared.

I logged in and replaced the modified xorg.conf with the original one.

Reboot and everything was fine again.

If you don't have a backup on Pandora it's no problem.

In case you made the same mistake I made simply do:

1: Login

2: sudo mousepad /etc/X11/xorg.conf

3: Go to last line and check if there's an empty kine at the end.

4: If not: press enter.

5: Save

6: Quit mousepad and shutdown.

7: Reboot and be happy.

Maybe it helps. Don't know if that's your problem.
 
Tested on a Panasonic.

EDIT:

Seems like the TV is the problem.

Tested again on an other one.

Brand: Orion

If I select "16:9" it also displays the screen to big, also if I select "automatic".

If I select "Real" it's displayed fine.

The one I used with Slackware is a Samsung one.

Can't test right now as it's 3 hours train trip away.

As it's not a Pandora problem I'm happy with it.

Don't know what those TVs do.

:)

EDIT 2:

Maybe it's interesting for you:

If I change Orion TV to 4:3 before I connect DisplayLink it's displayed as 600:800.

So there seems to be some resolution detection.

for sure I can tell it if I'm in University and connect it to a VGA projector.

This won't happen until 15th April. Have to look for an empty room and do some secret test ;) .

No VGA here.
 
Last edited by a moderator:
Will report how it works on the Samsung in two weeks.


Now I can finally make my presentations on the Pandora and show them on Pandora.


Awesome.
 
And DisplayLink working on SZ1.54. I wonder if it would be possible to make it detect 1680x1050 and other, maybe weird, resolutions. I could get full res on my screen before. I ofc am only guessing it's software and not the adapter, because it looked right, as in 1680x1050, when I tried it on 1.53. Crappy youtube video at watch?v=msRtdyFkMvU or in the spoiler

https://www.youtube.com/embed/msRtdyFkMvU?feature=oembed

Notes

- udlfb.h detects possible DL resolutions, some seem to be missing

- xrandr reports max 1680x1050@60 for the screen
 
Last edited by a moderator:
Allright, let me make a call here - If there's anyone willing to write a clear tutorial on PandoraLive for everyone interested in the DisplayLink capabilities, I will publish them :)  Please PM me. 
 
Update, just tried again and now the adapter reports 1680x1050.

- connect DVI to DL

- connect DL to Pandora's USB-A

- activate USB host

dmesg should now report the modes found by udlfb and select the highest... will edit in post from pandora

Edit: 

Code: 
[52568.832580] ehci-omap ehci-omap.0: USB 2.0 started, EHCI 1.00
[52568.832672] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[52568.832702] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[52568.832702] usb usb2: Product: OMAP-EHCI Host Controller
[52568.832702] usb usb2: Manufacturer: Linux 3.2.39 ehci_hcd
[52568.832733] usb usb2: SerialNumber: ehci-omap.0
[52568.835205] hub 2-0:1.0: USB hub found
[52568.835266] hub 2-0:1.0: 3 ports detected
[52569.160827] usb 2-2: new high-speed USB device number 2 using ehci-omap
[52569.319610] usb 2-2: New USB device found, idVendor=17e9, idProduct=0290
[52569.319610] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[52569.319610] usb 2-2: Product: DL-165 Adapter
[52569.319641] usb 2-2: Manufacturer: DisplayLink
[52569.319641] usb 2-2: SerialNumber: 106717
[52569.546966] udlfb: DisplayLink DL-165 Adapter - serial #106717
[52569.546997] udlfb: vid_17e9&pid_0290&rev_0001 drivers dlfb_data struct at cd725000
[52569.546997] udlfb: console enable=1
[52569.547027] udlfb: fb_defio enable=1
[52569.547027] udlfb: shadow enable=1
[52569.547210] udlfb: vendor descriptor length:22 data:22 5f 01 0020 05 00 01 03 04 02
[52569.547241] udlfb: DL chip limited to 2080000 pixel modes
[52569.549163] udlfb: allocated 4 65024 byte urbs
[52569.659484] udlfb: 1680x1050 valid mode
[52569.659484] udlfb: 720x400 valid mode
[52569.659484] udlfb: 640x480 valid mode
[52569.659515] udlfb: 640x480 valid mode
[52569.659515] udlfb: 640x480 valid mode
[52569.659515] udlfb: 640x480 valid mode
[52569.659515] udlfb: 800x600 valid mode
[52569.659545] udlfb: 800x600 valid mode
[52569.659545] udlfb: 800x600 valid mode
[52569.659545] udlfb: 800x600 valid mode
[52569.659545] udlfb: 832x624 valid mode
[52569.659576] udlfb: 1024x768 valid mode
[52569.659576] udlfb: 1024x768 valid mode
[52569.659576] udlfb: 1024x768 valid mode
[52569.659576] udlfb: 1280x1024 valid mode
[52569.659606] udlfb: 1152x864 valid mode
[52569.659606] udlfb: 1152x864 valid mode
[52569.659606] udlfb: 1280x1024 valid mode
[52569.659606] udlfb: 1280x960 valid mode
[52569.659637] udlfb: 1280x960 valid mode
[52569.659637] udlfb: 1280x720 valid mode
[52569.659637] udlfb: 1440x900 valid mode
[52569.659637] udlfb: 1400x1050 valid mode
[52569.659667] udlfb: 1680x1050 valid mode
[52569.659667] udlfb: Reallocating framebuffer. Addresses will change!
[52569.666870] udlfb: 1680x1050 valid mode
[52569.666900] udlfb: set_par mode 1680x1050
[52569.708099] udlfb: DisplayLink USB device /dev/fb3 attached. 1680x1050 resolution. Using 6896K framebuffer memory
[52569.709472] usbcore: registered new interface driver udlfb
 

Edited again for LFs... still hating this editor

 

More editing: My FullHD will only go to 1280x1024. Another TV problem I guess. Would there be a way to trick udlfb into setting a resolution I know  my screen supports?
 
Last edited by a moderator:
Maybe I'm slow, what would that change? I know my TV supports fullHD, I guess I need a way to have udlfb set this resolution, can't force the TV to it.

I now get proper 1680x1050 output on my other screen. Looks abolutely lovely, so much space .-)

Did what I wrote above and then Palmigas procedure with logging out.

To stop using DL goto logout, have log out highlighted, disconnect DL and hit enter
 
Xrandr is the tool to configure screens. You can change parameters on the fly without having to restart X or edit xorg.conf.
 
Ah, I was under the impression it would only read values, thanks! Too bad we don't have a PND for this, I wonder if it's hard to do...

I've been trying to install SZ to an SD card lately and failed several times, always with problems unpacking, I will try that with sl4p, maybe I've got more luck there.
 
My VGA-monitor has a resolution of 1280x1024.

dmesg shows:

[xxx.yyy] udlfb: 1280x1024 valid mode
[xxx.yyy] udlfb: Reallocating framebuffer. Addresses will change!
[xxx.yyy] udlfb: 1024x768 valid mode
[xxx.yyy] udlfb: set_par mode 1024x768

I try the tip from kuru, but it wont work. Still 1024x768. :(
 
kuru said:
kuru, on 29 Mar 2013 - 15:10, said:


Ah, I was under the impression it would only read values, thanks! Too bad we don't have a PND for this, I wonder if it's hard to do...


I've been trying to install SZ to an SD card lately and failed several times, always with problems unpacking, I will try that with sl4p, maybe I've got more luck there.
Click to expand...
No need for a PND.


There is a package in the repo.


On SuperZaxxon, do this to install xrandr:

Code: 
sudo opkg update
sudo opkg install xrandr
seems to work fine here. No deep testing done yet, though.
 
If this package is small (should be), maybe we can ask it's inclusion in Zaxxon ?
 
I didn't look deeply into xrandr and its purpose and function yet.

Does it make sense for every (DL) user? Or is it just necessary for the development phase now to tweak the settings so that the result will be useable for as many users as possible?

If it's not interesting for the average (DL) user, I usspect inclusion into SZ firmware is not wanted.
 
It goes on par with udlfb module, e.g. doesn't make sense for every user.
 
What I meant was: Does every DL user need xrandr to use DL? Or do we only need xrandr to set up DL in a universal manner now, and once DL is set up in such a universal manner, every user can use DL without needing xrandr?
 
You must log in or register to reply here.

Similar threads

hmc
DisplayLink external DVI/VGA display WORKS! Now on to fine tuning it.
3 4 5
Replies
90
Views
27K
Palmiga
Palmiga
notaz
  • Sticky
SuperZaxxon incremental update changelog
2 3
Replies
57
Views
31K
notaz
notaz
Back
Top