On 14.08.2012 23:57, Matthieu Herrb wrote:
On Tue, Aug 14, 2012 at 10:35:40PM +0200, Alexis de BRUYN wrote:
On 14.08.2012 17:58, Matthieu Herrb wrote:
On Tue, Aug 14, 2012 at 04:39:57PM +0200, Matthieu Herrb wrote:
On Tue, Aug 14, 2012 at 10:31:24AM +0200, Alexis de BRUYN wrote:
On 13.08.2012
On 13.08.2012 23:34, Matthieu Herrb wrote:
On Sun, Aug 12, 2012 at 10:04:17PM +0200, Alexis de BRUYN wrote:
On 11.08.2012 23:33, Alexis de BRUYN wrote:
I still have my previous issue, but I have another one : while the
in-board display device is actived through my xorg.conf, the udl devices
On Tue, Aug 14, 2012 at 10:31:24AM +0200, Alexis de BRUYN wrote:
On 13.08.2012 23:34, Matthieu Herrb wrote:
On Sun, Aug 12, 2012 at 10:04:17PM +0200, Alexis de BRUYN wrote:
On 11.08.2012 23:33, Alexis de BRUYN wrote:
I still have my previous issue, but I have another one : while the
On Tue, Aug 14, 2012 at 04:39:57PM +0200, Matthieu Herrb wrote:
On Tue, Aug 14, 2012 at 10:31:24AM +0200, Alexis de BRUYN wrote:
On 13.08.2012 23:34, Matthieu Herrb wrote:
On Sun, Aug 12, 2012 at 10:04:17PM +0200, Alexis de BRUYN wrote:
On 11.08.2012 23:33, Alexis de BRUYN wrote:
I
On 14.08.2012 17:58, Matthieu Herrb wrote:
On Tue, Aug 14, 2012 at 04:39:57PM +0200, Matthieu Herrb wrote:
On Tue, Aug 14, 2012 at 10:31:24AM +0200, Alexis de BRUYN wrote:
On 13.08.2012 23:34, Matthieu Herrb wrote:
On Sun, Aug 12, 2012 at 10:04:17PM +0200, Alexis de BRUYN wrote:
On 11.08.2012
On Tue, Aug 14, 2012 at 10:35:40PM +0200, Alexis de BRUYN wrote:
On 14.08.2012 17:58, Matthieu Herrb wrote:
On Tue, Aug 14, 2012 at 04:39:57PM +0200, Matthieu Herrb wrote:
On Tue, Aug 14, 2012 at 10:31:24AM +0200, Alexis de BRUYN wrote:
On 13.08.2012 23:34, Matthieu Herrb wrote:
On Sun,
On Sun, Aug 12, 2012 at 10:04:17PM +0200, Alexis de BRUYN wrote:
On 11.08.2012 23:33, Alexis de BRUYN wrote:
# wsconsctl -f /dev/ttyC0 display.type
display.type=vga-pci
# wsconsctl -f /dev/ttyD0 display.type
display.type=displaylink
# wsconsctl -f /dev/ttyE0 display.type
On 11.08.2012 23:33, Alexis de BRUYN wrote:
# wsconsctl -f /dev/ttyC0 display.type
display.type=vga-pci
# wsconsctl -f /dev/ttyD0 display.type
display.type=displaylink
# wsconsctl -f /dev/ttyE0 display.type
display.type=displaylink
I still have my previous issue, but I have another one :
On 02.08.2012 22:31, Alexis de BRUYN wrote:
On 02.08.2012 21:48, Matthieu Herrb wrote:
This is the xorg.conf I use to test wsudl:
Section Devicë
Identifier Card0
Driver wsudl
Option Devicë /dev/ttyD0
EndSection
(Yes that's it. Modern X can figure out
On Sat, 11 Aug 2012, Alexis de BRUYN wrote:
On 02.08.2012 22:31, Alexis de BRUYN wrote:
On 02.08.2012 21:48, Matthieu Herrb wrote:
This is the xorg.conf I use to test wsudl:
Section Devicë
Identifier Card0
Driver wsudl
Option Devicë /dev/ttyD0
On 11.08.2012 20:22, Mats O Jansson wrote:
So I did sh MAKEDEV ttyD1, and modify my xorg.conf like,
Where did you get ttyD1 from? Try to add ttyE0.
I have chosen ttyD1 because I think I had to choose the next ttyD* after
ttyD0.
Unfortunately, I have the same error with ttyE0.
Thanks for your
On Sat, 11 Aug 2012, Alexis de BRUYN wrote:
On 11.08.2012 20:22, Mats O Jansson wrote:
So I did sh MAKEDEV ttyD1, and modify my xorg.conf like,
Where did you get ttyD1 from? Try to add ttyE0.
I have chosen ttyD1 because I think I had to choose the next ttyD* after
ttyD0.
Since I havn't seen a dmesg i guess that wsdisplay0 is your graphics card
on your pc (/dev/ttyC0). udl0 is wsdisplay1 (/dev/ttyD0). So udl1 is
wsdisplay2 (/dev/ttyE0).
You can use wsconsctl to verify which device it should be.
You're right (my dmesg is at the end of my reply) :
# wsconsctl
On 03.08.2012 23:02, Mats O Jansson wrote:
Hmm, looking at the message you get about modes it seems that they are
generated by dev/videomode/edid.c. Recompile it with EDIDVERBOSE defined.
That might give us more information on whats going on...
What kind of display is connected to the udl
On Thu, 2 Aug 2012, Alexis de BRUYN [Mailinglists] wrote:
The chip is a DL-165. Maybe it is my problem. UDL(4) mentions that :
DESCRIPTION
The udl driver supports USB display devices based on the DisplayLink
DL-120 / DL-160 graphic chip.
Regards,
Nope, DL-165 is supported. But
Thanks Mats for your answer.
The chip is a DL-165. Maybe it is my problem. UDL(4) mentions that :
DESCRIPTION
The udl driver supports USB display devices based on the DisplayLink
DL-120 / DL-160 graphic chip.
Nope, DL-165 is supported. But looking at udl.c i see that is seems to
On Fri, 3 Aug 2012, Alexis de BRUYN wrote:
Thanks Mats for your answer.
The chip is a DL-165. Maybe it is my problem. UDL(4) mentions that :
DESCRIPTION
The udl driver supports USB display devices based on the DisplayLink
DL-120 / DL-160 graphic chip.
Nope, DL-165 is
Hi List,
I have an issue with DisplayLink CONV-USB2DVI and OpenBSD 5.1/amd64 (and
snapshot/amd64). X cannot be launched, I have got the following error :
wsudl(0): We are not attached to the udl driver
The device is detected, dmesg :
-
udl0 at uhub6 port 2 DisplayLink CONV-USB2DVI rev
Could this be related to the space preceding in the device declaration?
Option device / dev/wsdisplay1 -- Option device /dev/wsdisplay1
Thanks for your reply, Вовочка, but this is a typo mistake I have made
while I write my mail.
--
Alexis de BRUYN
On Thu, Aug 02, 2012 at 03:15:04PM +0200, Alexis de BRUYN [Mailinglists] wrote:
Hi List,
I have an issue with DisplayLink CONV-USB2DVI and OpenBSD 5.1/amd64 (and
snapshot/amd64). X cannot be launched, I have got the following error :
wsudl(0): We are not attached to the udl driver
The
On 02.08.2012 21:48, Matthieu Herrb wrote:
This is the xorg.conf I use to test wsudl:
Section Devicë
Identifier Card0
Driver wsudl
Option Devicë /dev/ttyD0
EndSection
(Yes that's it. Modern X can figure out everything else).
Thanks for your help Matthieu,
21 matches
Mail list logo
