Re: FreeBSD - support for DisplayLink devices?
On Wed, Nov 18, 2009 at 10:47:19PM +0100, Hans Petter Selasky wrote: > On Wednesday 18 November 2009 22:44:04 Torfinn Ingolfsen wrote: > > On Wed, 18 Nov 2009 22:32:23 +0100 > > > > Torfinn Ingolfsen wrote: > > > Today I got a UM-70[5] monitor made by Lilliput, this is > > > what /var/log/messages says when I connectd it to my 7.2-stable > > > machine: > > > > Oh, I forgot to tell the age of this -stable: > > ti...@kg-v2$ uname -a > > FreeBSD kg-v2.kg4.no 7.2-STABLE FreeBSD 7.2-STABLE #1: Fri Oct 30 > > 19:46:58 CET 2009 r...@kg-v2.kg4.no:/usr/obj/usr/src/sys/V2 amd64 > > Is there are userland driver using libusb for your device? libdlo mentioned in the original email is a userland driver using libusb. It should just work. Note for FreeBSD 7 and below you will need to install the devel/libusb port. Andrew ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: FreeBSD - support for DisplayLink devices?
On Wed, 18 Nov 2009 22:47:19 +0100 Hans Petter Selasky wrote: > Is there are userland driver using libusb for your device? I don't know, really. I haven't finished googling yet. :-) So far I've got this: http://libdlo.freedesktop.org/wiki/ http://mulchman.org/blog/?tag=displaylink -- Rgds, Torfinn Ingolfsen ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: FreeBSD - support for DisplayLink devices?
On Wednesday 18 November 2009 22:44:04 Torfinn Ingolfsen wrote: > On Wed, 18 Nov 2009 22:32:23 +0100 > > Torfinn Ingolfsen wrote: > > Today I got a UM-70[5] monitor made by Lilliput, this is > > what /var/log/messages says when I connectd it to my 7.2-stable > > machine: > > Oh, I forgot to tell the age of this -stable: > ti...@kg-v2$ uname -a > FreeBSD kg-v2.kg4.no 7.2-STABLE FreeBSD 7.2-STABLE #1: Fri Oct 30 > 19:46:58 CET 2009 r...@kg-v2.kg4.no:/usr/obj/usr/src/sys/V2 amd64 Is there are userland driver using libusb for your device? --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: FreeBSD - support for DisplayLink devices?
On Wed, 18 Nov 2009 22:32:23 +0100 Torfinn Ingolfsen wrote: > Today I got a UM-70[5] monitor made by Lilliput, this is > what /var/log/messages says when I connectd it to my 7.2-stable > machine: Oh, I forgot to tell the age of this -stable: ti...@kg-v2$ uname -a FreeBSD kg-v2.kg4.no 7.2-STABLE FreeBSD 7.2-STABLE #1: Fri Oct 30 19:46:58 CET 2009 r...@kg-v2.kg4.no:/usr/obj/usr/src/sys/V2 amd64 -- Regards, Torfinn Ingolfsen ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
FreeBSD - support for DisplayLink devices?
Hi, Do we have support for DisplayLink devices in FreeBSD? Like libdlo[2,3] or udl[4]? Today I got a UM-70[5] monitor made by Lilliput, this is what /var/log/messages says when I connectd it to my 7.2-stable machine: Nov 18 22:18:13 kg-v2 root: Unknown USB device: vendor 0x17e9 product 0x02a9 bus uhub1 Nov 18 22:18:13 kg-v2 kernel: ugen2: on uhub1 Output from 'usbdevs -v': port 5 addr 4: high speed, power 500 mA, config 1, LILLIPUT USB Monitor(0x02a9), DisplayLink(0x17e9), rev 1.23 (No, I can't stop buying gadgets) Refernces: 1) http://en.wikipedia.org/wiki/Displaylink 2) http://displaylink.org/ 3) http://libdlo.freedesktop.org/ 4) http://libdlo.freedesktop.org/wiki/udl 5) http://www.lilliputlcd.com/lilliput-um70-7-usb-monitor-only-one-cable-does-all_p592.html -- Regards, Torfinn Ingolfsen ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
RE: 8.0-RC3 USB lock up on mounting two partitions from one USB drive
It looks like a system issue since it also happens to the SATA drive. The USB drive seems having more difficulty. I will back up rest partitions, Then redo the slice and partition to see if problem goes away. If so, then 8.0-R has a backward compatibility issue on the partition table or format to older FreeBSD release. -Original Message- From: Hans Petter Selasky [mailto:hsela...@c2i.net] Sent: Wednesday, November 18, 2009 3:14 AM To: freebsd-usb@freebsd.org Cc: Guojun Jin; freebsd-sta...@freebsd.org; questi...@freebsd.org Subject: Re: 8.0-RC3 USB lock up on mounting two partitions from one USB drive Hi, I'm not sure if this is an USB issue or not. If you get READ/WRITE errors and the drive simply dies then it might be the case. Else it is a system issue. There are quirks for mass storage which you can add to sys/dev/usb/storage/umass.c . --HPS On Wednesday 18 November 2009 08:33:07 Guojun Jin wrote: > Did newfs on those partition and made things worsen -- restore completely > fails: (I had experienced another similar problem on an IDE, which works > well for 6.4 and 7.2, but 8.0.) This dirve works fine under FreeBSD 6.4. > > Is something new in 8.0 making disk partition schema changed? > > g_vfs_done():da0s3d[READ(offset=98304, length=16384)]error = 6 > g_vfs_done():da0s3d[WRITE(offset=192806912, length=16384)]error = 6 > fopen: Device not configured > cannot create save file ./restoresymtable for symbol table > abort? [yn] (da0:umass-sim0:0:0:0): Synchronize cache failed, status == > 0xa, scs i status == 0x0 > (da0:umass-sim0:0:0:0): removing device entry > ugen1.2: at usbus1 > umass0: on usbus1 > umass0: SCSI over Bulk-Only; quirks = 0x > umass0:0:0:-1: Attached to scbus0 > da0 at umass-sim0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-0 device > da0: 40.000MB/s transfers > da0: 114473MB (234441648 512 byte sectors: 255H 63S/T 14593C) > Device da0s3d went missing before all of the data could be written to it; > expect data loss. > > 99 23:19 sysinstall >100 23:20 newfs /dev/da0s3d >101 23:20 newfs /dev/da0s3e >102 23:21 mount /dev/da0s3d /mnt >103 23:21 cd /mnt >104 23:21 dump -0f - /home | restore -rf - >105 23:27 history 15 > > > > -Original Message- > From: Guojun Jin > Sent: Tue 11/17/2009 11:05 PM > To: freebsd-sta...@freebsd.org > Cc: questi...@freebsd.org; freebsd-usb@freebsd.org > Subject: 8.0-RC3 USB lock up on mounting two partitions from one USB drive > > When mounting two partitions from a USB dirve, it can cause the drive > access lock up for a long time. Details: > > Terminal 1 -- > term1# mount /dev/da0s3d /mnt > term1# cd /mnt ; rm -fr * > > when rm starts, go to terminal 2 and do: > > term2# mount /dev/da0s3e /dist ### this will hanging for a long time and > USB hard drive activity light is off. After more than 1-2 minutes, mount > returns, and the drive activity light is blinking, thus removing is going > on. > > term2# ls /dist ### this will cause dUSB dirve hanging again -- no > avtivity. Similarly, ls will finish in a couple of miniutes or longer, the > rm command continues; but for a while, the drive activity will stop again. > > Reboot machine, repeat the above steps, and result will be the same. Reboot > machine again, and just mount one partition, then doing "rm -rf *" without > involve the second partition, rm will finish quickly. > > Has anyone obseved this behave on 8.0-RC? > > -Jin ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: [keyboard] ukbd stops working after filesystems mount at boot time
on 18/11/2009 14:25 Travelling Particle said the following: > Hello, > > I am not sure if the problem is with USB, because the same hardware works > fine with LiveCD. I will seek help here first, please feel free to redirect > me to a better place for advice. > > The system is 8.0-RC3. > > I am booting off USB stick because I have to attach root partition on HDD > with GELI. It all works fine, I am able to enter passphrase on the keyboard > (there's only ukbd keyboard in the kernel at this moment, but I had tried > with atkbd as well; I have also experimented with or without TEKEN with no > difference). After root partition is mounted, system mounts other geli > partitions on the same hard disk. It is right after the filesystems were > mounted that the problem starts. The output on console at that moment starts > to be interleaved with new lines symbols. After late boot stage completes, I > see login prompt on console, but system acts *as if* I had just pressed > Enter and presents login prompt again and again. The keyboard itself appears > to be dead. If I choose to boot single-mode, behavior is the same -- I see > multiple shell prompts as if I were hitting Enter repeatedly. I had been > trying various configurations in the kernel for over 5 days now, and still > couldn't make the console work on the system (I can login via network > though). > > The hardware is Nvidea ION-based Acer nettop. It does not come with PS/2 > keyboard connector and I cannot test it with any keyboard but USB. The > keyboard itself I am using is Acer's standard one, and it works fine with > LiveCD. I wonder if GELI might mess the things up, but the geli attachment > process goes well, and all filesystems are attached just fine. LiveCD is also 8.0-RC3? -- Andriy Gapon ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
[keyboard] ukbd stops working after filesystems mount at boot time
Hello, I am not sure if the problem is with USB, because the same hardware works fine with LiveCD. I will seek help here first, please feel free to redirect me to a better place for advice. The system is 8.0-RC3. I am booting off USB stick because I have to attach root partition on HDD with GELI. It all works fine, I am able to enter passphrase on the keyboard (there's only ukbd keyboard in the kernel at this moment, but I had tried with atkbd as well; I have also experimented with or without TEKEN with no difference). After root partition is mounted, system mounts other geli partitions on the same hard disk. It is right after the filesystems were mounted that the problem starts. The output on console at that moment starts to be interleaved with new lines symbols. After late boot stage completes, I see login prompt on console, but system acts *as if* I had just pressed Enter and presents login prompt again and again. The keyboard itself appears to be dead. If I choose to boot single-mode, behavior is the same -- I see multiple shell prompts as if I were hitting Enter repeatedly. I had been trying various configurations in the kernel for over 5 days now, and still couldn't make the console work on the system (I can login via network though). The hardware is Nvidea ION-based Acer nettop. It does not come with PS/2 keyboard connector and I cannot test it with any keyboard but USB. The keyboard itself I am using is Acer's standard one, and it works fine with LiveCD. I wonder if GELI might mess the things up, but the geli attachment process goes well, and all filesystems are attached just fine. Thanks a lot for help, Vassiliy ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: 8.0-RC3 USB lock up on mounting two partitions from one USB drive
Hi, I'm not sure if this is an USB issue or not. If you get READ/WRITE errors and the drive simply dies then it might be the case. Else it is a system issue. There are quirks for mass storage which you can add to sys/dev/usb/storage/umass.c . --HPS On Wednesday 18 November 2009 08:33:07 Guojun Jin wrote: > Did newfs on those partition and made things worsen -- restore completely > fails: (I had experienced another similar problem on an IDE, which works > well for 6.4 and 7.2, but 8.0.) This dirve works fine under FreeBSD 6.4. > > Is something new in 8.0 making disk partition schema changed? > > g_vfs_done():da0s3d[READ(offset=98304, length=16384)]error = 6 > g_vfs_done():da0s3d[WRITE(offset=192806912, length=16384)]error = 6 > fopen: Device not configured > cannot create save file ./restoresymtable for symbol table > abort? [yn] (da0:umass-sim0:0:0:0): Synchronize cache failed, status == > 0xa, scs i status == 0x0 > (da0:umass-sim0:0:0:0): removing device entry > ugen1.2: at usbus1 > umass0: on usbus1 > umass0: SCSI over Bulk-Only; quirks = 0x > umass0:0:0:-1: Attached to scbus0 > da0 at umass-sim0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-0 device > da0: 40.000MB/s transfers > da0: 114473MB (234441648 512 byte sectors: 255H 63S/T 14593C) > Device da0s3d went missing before all of the data could be written to it; > expect data loss. > > 99 23:19 sysinstall >100 23:20 newfs /dev/da0s3d >101 23:20 newfs /dev/da0s3e >102 23:21 mount /dev/da0s3d /mnt >103 23:21 cd /mnt >104 23:21 dump -0f - /home | restore -rf - >105 23:27 history 15 > > > > -Original Message- > From: Guojun Jin > Sent: Tue 11/17/2009 11:05 PM > To: freebsd-sta...@freebsd.org > Cc: questi...@freebsd.org; freebsd-usb@freebsd.org > Subject: 8.0-RC3 USB lock up on mounting two partitions from one USB drive > > When mounting two partitions from a USB dirve, it can cause the drive > access lock up for a long time. Details: > > Terminal 1 -- > term1# mount /dev/da0s3d /mnt > term1# cd /mnt ; rm -fr * > > when rm starts, go to terminal 2 and do: > > term2# mount /dev/da0s3e /dist ### this will hanging for a long time and > USB hard drive activity light is off. After more than 1-2 minutes, mount > returns, and the drive activity light is blinking, thus removing is going > on. > > term2# ls /dist ### this will cause dUSB dirve hanging again -- no > avtivity. Similarly, ls will finish in a couple of miniutes or longer, the > rm command continues; but for a while, the drive activity will stop again. > > Reboot machine, repeat the above steps, and result will be the same. Reboot > machine again, and just mount one partition, then doing "rm -rf *" without > involve the second partition, rm will finish quickly. > > Has anyone obseved this behave on 8.0-RC? > > -Jin ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
Re: usb printer rejects incoming data [SOLVED]
On Tuesday 17 November 2009 18:23:10 Alex Troussov wrote: > On Tue, Nov 17, 2009 at 09:16:03AM +0100, Hans Petter Selasky wrote: > > > Recently I upgraded to the latest RELENG_8 and rebuilt world. > > > Now I'm having strange problems with my USB printer (Samsung CLP 315). > > > Digging into it these last days, I found that it seems to refuse > > > incoming data via USB port. > > > > > > >sudo cat tiger.qpdl > /dev/usb/4.3.0 > > > > > > cat: stdout: Input/output error > > > > > > I'm sure this file tiger.qpdl contains the data needed, I created it > > > from /usr/local/share/ghostscript/8.64/examples/tiger.eps using gs + > > > foo2qpdl and tested on another PC. > > > > .0 is the control endpoint. You won't get any data through there :-) > > > > See: > > > > usbconfig -u 4 -a 3 dump_curr_config_desc > > > > for the correct OUT endpoint. > > OK, here is what it gives: > >sudo usbconfig -u 4 -a 3 dump_curr_config_desc > > ugen4.3: at usbus4, cfg=0 > md=HOST spd=HIGH (480Mbps) pwr=ON > > Configuration index 0 > > bLength = 0x0009 > bDescriptorType = 0x0002 > wTotalLength = 0x0020 > bNumInterfaces = 0x0001 > bConfigurationValue = 0x0001 > iConfiguration = 0x > bmAttributes = 0x00c0 > bMaxPower = 0x0001 > > Interface 0 > bLength = 0x0009 > bDescriptorType = 0x0004 > bInterfaceNumber = 0x > bAlternateSetting = 0x > bNumEndpoints = 0x0002 > bInterfaceClass = 0x0007 > bInterfaceSubClass = 0x0001 > bInterfaceProtocol = 0x0002 > iInterface = 0x > > Endpoint 0 > bLength = 0x0007 > bDescriptorType = 0x0005 > bEndpointAddress = 0x0002 > bmAttributes = 0x0002 > wMaxPacketSize = 0x0200 > bInterval = 0x000a > bRefresh = 0x > bSynchAddress = 0x > > Endpoint 1 > bLength = 0x0007 > bDescriptorType = 0x0005 > bEndpointAddress = 0x0081 > bmAttributes = 0x0002 > wMaxPacketSize = 0x0200 > bInterval = 0x000a > bRefresh = 0x > bSynchAddress = 0x > > I don't know where to look for the right endpoint here... > > But I tried every endpoint - /dev/usb/4.3.0, /dev/usb/4.3.1 and > /dev/usb/4.3.2 - and the last one worked. > So, the problem is solved for me. > > Just for my curiosity, where can I read more about USB endpoints? Try google. I don't have any links at hand. --HPS ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
8.0-RC3 USB lock up on mounting two partitions from one USB drive
When mounting two partitions from a USB dirve, it can cause the drive access lock up for a long time. Details: Terminal 1 -- term1# mount /dev/da0s3d /mnt term1# cd /mnt ; rm -fr * when rm starts, go to terminal 2 and do: term2# mount /dev/da0s3e /dist ### this will hanging for a long time and USB hard drive activity light is off. After more than 1-2 minutes, mount returns, and the drive activity light is blinking, thus removing is going on. term2# ls /dist ### this will cause dUSB dirve hanging again -- no avtivity. Similarly, ls will finish in a couple of miniutes or longer, the rm command continues; but for a while, the drive activity will stop again. Reboot machine, repeat the above steps, and result will be the same. Reboot machine again, and just mount one partition, then doing "rm -rf *" without involve the second partition, rm will finish quickly. Has anyone obseved this behave on 8.0-RC? -Jin ___ freebsd-usb@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-usb To unsubscribe, send any mail to "freebsd-usb-unsubscr...@freebsd.org"
