From owner-freebsd-usb@FreeBSD.ORG Sun Mar 18 15:46:09 2012 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4B0871065679 for ; Sun, 18 Mar 2012 15:46:09 +0000 (UTC) (envelope-from denverh@comcast.net) Received: from qmta04.westchester.pa.mail.comcast.net (qmta04.westchester.pa.mail.comcast.net [76.96.62.40]) by mx1.freebsd.org (Postfix) with ESMTP id F12F38FC17 for ; Sun, 18 Mar 2012 15:46:08 +0000 (UTC) Received: from omta13.westchester.pa.mail.comcast.net ([76.96.62.52]) by qmta04.westchester.pa.mail.comcast.net with comcast id n3lN1i00217dt5G543m3d8; Sun, 18 Mar 2012 15:46:03 +0000 Received: from [192.168.0.30] ([66.41.84.80]) by omta13.westchester.pa.mail.comcast.net with comcast id n3m21i02C1jzK7m3Z3m3Ag; Sun, 18 Mar 2012 15:46:03 +0000 Message-ID: <4F660339.7000205@comcast.net> Date: Sun, 18 Mar 2012 10:46:01 -0500 From: Denver Hull User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.19) Gecko/20110521 SeaMonkey/2.0.14 MIME-Version: 1.0 To: freebsd-usb@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: webcamd and wacom X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Mar 2012 15:46:09 -0000 Hello, I see that freshports has posted an update to x11-driver/input-wacom. I've been trying to work on that myself, but it's been slow going, and I haven't made much progress. So I was happily surprised to see the update, and wanted to try it as soon as I could. I think I have everything installed and configured properly. I can see the /dev/input/event0 device, but when I start X it logs the following entries: # grep -i wacom /var/log/Xorg.0.log (II) LoadModule: "wacom" (II) Loading /usr/local/lib/xorg/modules/input/wacom_drv.so (II) Module wacom: vendor="X.Org Foundation" (--) stylus: Wacom USB Bamboo tablet maxX=14720 maxY=9200 maxZ=1023 resX=100000 resY=100000 tilt=disabled (EE) stylus: Wacom X driver can't grab event device (Bad address) (--) eraser: Wacom USB Bamboo tablet maxX=14720 maxY=9200 maxZ=1023 resX=100000 resY=100000 tilt=disabled (EE) eraser: Wacom X driver can't grab event device (Bad address) (--) cursor: Wacom USB Bamboo tablet maxX=14720 maxY=9200 maxZ=1023 resX=100000 resY=100000 tilt=disabled (EE) cursor: Wacom X driver can't grab event device (Bad address) (--) pad: Wacom USB Bamboo tablet maxX=14720 maxY=9200 maxZ=1023 resX=100000 resY=100000 tilt=disabled (EE) pad: Wacom X driver can't grab event device (Bad address) (--) touch: Wacom USB Bamboo tablet maxX=14720 maxY=9200 maxZ=1023 resX=100000 resY=100000 tilt=disabled (EE) touch: Wacom X driver can't grab event device (Bad address) (II) UnloadModule: "wacom" (II) UnloadModule: "wacom" (II) UnloadModule: "wacom" (II) UnloadModule: "wacom" (II) UnloadModule: "wacom" # Does anyone have any idea what I'm missing here? cuse4bsd.ko is loaded, and webcamd is running. I'm not sure what else I can include that will be helpful, but if there is something else, let me know and I will supply it. Hopefully this will turn out to be something simple. Thanks, Denver From owner-freebsd-usb@FreeBSD.ORG Sun Mar 18 18:32:12 2012 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 00A22106564A for ; Sun, 18 Mar 2012 18:32:12 +0000 (UTC) (envelope-from fabiodive@gmail.com) Received: from mail-qc0-f182.google.com (mail-qc0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id B388E8FC12 for ; Sun, 18 Mar 2012 18:32:11 +0000 (UTC) Received: by qcsg15 with SMTP id g15so1055940qcs.13 for ; Sun, 18 Mar 2012 11:32:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=uU0Xs7Dnia6sdiTjacZZxV0ICQCmLTI8bpYCeSXg3dI=; b=0Y0uqBmuklwv5/lpnPRf6N3jv9hbqO0sWQudKFi5oc/YWvcuZzcRbGd2yvWLZUvqiY I/UjFLF46hMpwshVazBsiw23lYcVAsP6LUUY3r21Ih2GMapj1MyBn4qZTLU7+3H9XJcG gIKLQYOVemCWf9mgespLlu53qAetdOwHFSf+bjtyrl0eAKOCO3BINeyWndMemf5RUE2I I0XWGkA4PeaMc4w2xguqBnkYBk2oJDXALmIzKN1uqqYrfjmSDjf4Zu9OATlR4Y2O/DUJ s9YZVcMM5cvuGTOShT9YArWHMkT8RigtNeJeyufz0dpG1QGvxNtEHbCUcT84JrBXFOF5 cJzA== MIME-Version: 1.0 Received: by 10.224.32.12 with SMTP id a12mr11973406qad.66.1332095525287; Sun, 18 Mar 2012 11:32:05 -0700 (PDT) Received: by 10.229.163.204 with HTTP; Sun, 18 Mar 2012 11:32:05 -0700 (PDT) Date: Sun, 18 Mar 2012 18:32:05 +0000 Message-ID: From: Fabio Dive To: freebsd-usb@freebsd.org Content-Type: text/plain; charset=UTF-8 Subject: USB serial adapter, cu write: Device not configured X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Mar 2012 18:32:12 -0000 Hello people! I write you because I have got a problem with the uplcom driver on FreeBSD 9.0, I tried a lot of different things, read all I found, manpages, forums, irc, google but still not able to solve my problem. I need to connect to my remote Alix board, the remote console setup is 19200 8N1. I am using a short USB Prolific Tec.. serial cable adapter with a NULL modem cable, the last one plugged one side to the Alix board, the other side to the adapter cable. Under Linux Debian everything is fine, so the hardware and cables should be ok, under Linux I used minicom and cu and tip without problems. With FreeBSD and NetBSD, big problems..the result is always the same, I can receive but I cannot transmit. (working as root) *cu -t -s 19200 -l /dev/cuaU0 write: Device not configured (I can't transmit but I can receive the output if I reboot the remote alix board) *minicom test1 ----> Cannot open /dev/ttyU0! test2 ----> Cannot open /dev/cuaU0! (in a popup box) #---- A bit of my enviroment and some command output (commands by root): I am using FreeBSD 9.0 with kernel and world compiled today with the last source updated with csup. The laptop is a Lenovo IBM Thinkpad T61. 4Gbyte of RAM, HD 40% used. Shell bash, X graphical enviroment with Fluxbox, the problem exist even within the shell without load Xorg. * usbconfig -d ugen1.2 show_ifdrv ugen1.2: at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen1.2.0: uplcom0: * usbconfig -d ugen1.2 dump_device_desc ugen1.2: at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0110 bDeviceClass = 0x0000 bDeviceSubClass = 0x0000 bDeviceProtocol = 0x0000 bMaxPacketSize0 = 0x0040 idVendor = 0x067b idProduct = 0x2303 bcdDevice = 0x0300 iManufacturer = 0x0001 iProduct = 0x0002 iSerialNumber = 0x0000 bNumConfigurations = 0x0001 * dmesg when I connect the cable: ugen1.2: at usbus1 uplcom0: on usbus1 * KLDSTAT Id Refs Address Size Name 1 36 0xffffffff80200000 d58c20 kernel 3 1 0xffffffff80f6c000 104ab40 nvidia.ko 4 4 0xffffffff81fb7000 45218 linux.ko 5 1 0xffffffff82212000 13300f zfs.ko 6 1 0xffffffff82346000 2fb5 opensolaris.ko 7 1 0xffffffff82349000 3d5d linprocfs.ko 8 1 0xffffffff8234d000 24c19 wpifw.ko 10 1 0xffffffff82374000 2a4c1 pf.ko 11 1 0xffffffff8239f000 762 rtc.ko 12 1 0xffffffff82372000 1fd5 uplcom.ko * stty -a -f /dev/cuaU0 speed 9600 baud; 0 rows; 0 columns; lflags: icanon isig iexten echo echoe -echok echoke -echonl echoctl -echoprt -altwerase -noflsh -tostop -flusho -pendin -nokerninfo -extproc iflags: -istrip icrnl -inlcr -igncr ixon -ixoff ixany imaxbel -ignbrk brkint -inpck -ignpar -parmrk oflags: opost onlcr -ocrnl tab0 -onocr -onlret cflags: cread cs8 -parenb -parodd hupcl -clocal -cstopb -crtscts -dsrflow -dtrflow -mdmbuf cchars: discard = ^O; dsusp = ^Y; eof = ^D; eol = ; eol2 = ; erase = ^?; erase2 = ^H; intr = ^C; kill = ^U; lnext = ^V; min = 1; quit = ^\; reprint = ^R; start = ^Q; status = ^T; stop = ^S; susp = ^Z; time = 0; werase = ^W; I tried to change the above parameters with "stty" by hand using cuaU0, cuaU0.init and cuaU0.lock before using cu, tip and minicom. I tried different combinations to the parameters of the connections but still the problem persist. My problem is exactly the same to that reported here: http://lists.freebsd.org/pipermail/freebsd-usb/2011-July/010443.html If I try to do: sysctl hw.usb.ucom.debug=15 I see in dmesg after "cu -t -s 19200 -l /dev/cuaU0": ucom_attach_tty: ttycreate: U0 ucom_attach: tp = 0xfffffe0005e08800, unit = 0, subunits = 1 ucom_open: tp = 0xfffffe0005e08800 ucom_dtr: onoff = 1 ucom_line_state: on=0x01, off=0x00 ucom_rts: onoff = 1 ucom_line_state: on=0x02, off=0x00 ucom_ring: onoff = 0 ucom_line_state: on=0x00, off=0x08 ucom_break: onoff = 0 ucom_line_state: on=0x00, off=0x04 ucom_status_change: ucom_param: sc = 0xfffffe0005106880 ucom_dtr: onoff = 1 ucom_line_state: on=0x01, off=0x00 ucom_rts: onoff = 1 ucom_line_state: on=0x02, off=0x00 ucom_cfg_open: ucom_ioctl: cmd = 0x402c7413 ucom_ioctl: cmd = 0x802c7416 ucom_ioctl: cmd = 0x2000740d ucom_ioctl: cmd = 0x402c7413 ucom_ioctl: cmd = 0x802c7416 ucom_param: sc = 0xfffffe0005106880 ucom_ioctl: cmd = 0x8004667e ucom_ioctl: cmd = 0x8004667d ucom_status_change: ucom_status_change: ucom_get_data: cnt=0 ucom_outwakeup: sc = 0xfffffe0005106880 ucom_get_data: cnt=1 ucom_outwakeup: sc = 0xfffffe0005106880 ucom_outwakeup: sc = 0xfffffe0005106880 uplcom0: at uhub1, port 1, addr 2 (disconnected) ucom_detach_tty: sc = 0xfffffe0005106880, tp = 0xfffffe0005e08800 ucom_close: tp=0xfffffe0005e08800 ucom_close: tp=0xfffffe0005e08800 already closed uplcom0: on usbus1 ucom_attach_tty: ttycreate: U0 ucom_attach: tp = 0xfffffe0007953400, unit = 0, subunits = 1 Do you have any idea where to give a look to fix my problem? Do you need other information? I suspect that the device is continuously disconnecting and reconnecting in background...but it is just a suspect. I run out of resources and brain but I still need to solve my problem and connect with my remote Alix board using FreeBSD or NetBSD. Thank you, best regards Fabio Balzano From owner-freebsd-usb@FreeBSD.ORG Sun Mar 18 18:57:57 2012 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 17A6C106566B for ; Sun, 18 Mar 2012 18:57:57 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id C85AA8FC08 for ; Sun, 18 Mar 2012 18:57:56 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.5/8.14.5) with ESMTP id q2IIvtHN085828; Sun, 18 Mar 2012 12:57:55 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.5/8.14.5/Submit) with ESMTP id q2IIvtUw085825; Sun, 18 Mar 2012 12:57:55 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Sun, 18 Mar 2012 12:57:55 -0600 (MDT) From: Warren Block To: Fabio Dive In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Sun, 18 Mar 2012 12:57:55 -0600 (MDT) Cc: freebsd-usb@freebsd.org Subject: Re: USB serial adapter, cu write: Device not configured X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Mar 2012 18:57:57 -0000 On Sun, 18 Mar 2012, Fabio Dive wrote: > Hello people! > > I write you because I have got a problem with the uplcom driver > on FreeBSD 9.0, I tried a lot of different things, read all I found, > manpages, forums, irc, google but still not able to solve my problem. > > I need to connect to my remote Alix board, > the remote console setup is 19200 8N1. > I am using a short USB Prolific Tec.. serial cable adapter with a > NULL modem cable, the last one plugged one side to the Alix board, > the other side to the adapter cable. > > Under Linux Debian everything is fine, so the hardware and cables > should be ok, under Linux I used minicom and cu and tip without problems. > With FreeBSD and NetBSD, big problems..the result is always > the same, I can receive but I cannot transmit. > > (working as root) > *cu -t -s 19200 -l /dev/cuaU0 > write: Device not configured > (I can't transmit but I can receive the output if I reboot the remote > alix board) Add the user to the dialer group. If that doesn't do it, make sure the user has write permission to the USB device and /dev/cuaU0. From owner-freebsd-usb@FreeBSD.ORG Sun Mar 18 19:25:39 2012 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2ACBB106564A for ; Sun, 18 Mar 2012 19:25:39 +0000 (UTC) (envelope-from fabiodive@gmail.com) Received: from mail-qa0-f54.google.com (mail-qa0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id D48348FC24 for ; Sun, 18 Mar 2012 19:25:38 +0000 (UTC) Received: by qao25 with SMTP id 25so500982qao.13 for ; Sun, 18 Mar 2012 12:25:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=pGQKf45CT1bahj8B4VewUchwrmk+cQ98WLSeZM5IG2E=; b=dw53M9KX6lbSySITTZK7wa3+Ayn89NiPwJ2dZkERFMd8sqa9Lv3DQMLiEKjUlYijHy OJgjuRLncqBBVCv4Hv8pUfRMUzTMi3lT3sszbL+Tvgaf9R/Wdv8Hj5/2/XPmQsWgS7xF fdcc0OrZ5HrqT9KGFsiZPRxuw4LjCWlwk+mDpPUPYPuReR+5BdW7rE5HA0dOMS92EPAG 5N2H9GIPdJaqkUNlO+tnysrKrxaaJd1hN/dH33eqggvHiQounzatHw57IIwt9iBelFKG oicPTLXUo51z/6ozJpoxGecvcTkioKnb8pqATVdMa/iXX7eMCTCsqVozpxTlyqea4foU RCAQ== MIME-Version: 1.0 Received: by 10.229.114.220 with SMTP id f28mr3563420qcq.151.1332098738093; Sun, 18 Mar 2012 12:25:38 -0700 (PDT) Received: by 10.229.163.204 with HTTP; Sun, 18 Mar 2012 12:25:38 -0700 (PDT) In-Reply-To: References: Date: Sun, 18 Mar 2012 19:25:38 +0000 Message-ID: From: Fabio Dive To: freebsd-usb@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: USB serial adapter, cu write: Device not configured X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Mar 2012 19:25:39 -0000 dear Warren, I did everything you write me but even using devfs.rules or by hand modify the ownership or write permission, or using the root user, it doesn't work. These are the rules activated by rc.conf with: devfs_system_ruleset=3D"usb_devices" cat /etc/devfs.rules [usb_devices=3D10] add path 'ugen*' mode 0777 user seaman group dialer add path 'ttyU*' mode 0777 user seaman group dialer add path 'usb/*' mode 0777 user seaman group dialer add path 'ums*' mode 0777 user seaman group usb add path 'cuaU*' mode 0777 user seaman group dialer add path 'da*s*' mode 0660 group usb I put 7 just to be sure to try everything.. normally I just need "rw" permissions. Thank you FabioDive On Sun, Mar 18, 2012 at 18:32, Fabio Dive wrote: > Hello people! > > I write you because I have got a problem with the uplcom driver > on FreeBSD 9.0, I tried a lot of different things, read all I found, > manpages, forums, irc, google but still not able to solve my problem. > > I need to connect to my remote Alix board, > the remote console setup is 19200 8N1. > I am using a short USB Prolific Tec.. serial cable adapter with a > NULL modem cable, the last one plugged one side to the Alix board, > the other side to the adapter cable. > > Under Linux Debian everything is fine, so the hardware and cables > should be ok, under Linux I used minicom and cu and tip without problems. > With FreeBSD and NetBSD, big problems..the result is always > the same, I can receive but I cannot transmit. > > (working as root) > *cu -t -s 19200 -l /dev/cuaU0 > write: Device not configured > (I can't transmit but I can receive the output if I reboot the remote > alix board) > *minicom > test1 ----> Cannot open /dev/ttyU0! > test2 ----> Cannot open /dev/cuaU0! > (in a popup box) > > #---- > > A bit of my enviroment and some command output (commands by root): > I am using FreeBSD 9.0 with kernel and world compiled today with the last= source > updated with csup. The laptop is a Lenovo IBM Thinkpad T61. 4Gbyte of RAM= , > HD 40% used. Shell bash, X graphical enviroment with Fluxbox, the problem > exist even within the shell without load Xorg. > > > * usbconfig -d ugen1.2 show_ifdrv > ugen1.2: at usbus1, > cfg=3D0 md=3DHOST spd=3DFULL (12Mbps) pwr=3DON > ugen1.2.0: uplcom0: class 0/0, rev 1.10/3.00, addr 2> > > > * usbconfig -d ugen1.2 dump_device_desc > ugen1.2: at usbus1, > cfg=3D0 md=3DHOST spd=3DFULL (12Mbps) pwr=3DON > > =C2=A0bLength =3D 0x0012 > =C2=A0bDescriptorType =3D 0x0001 > =C2=A0bcdUSB =3D 0x0110 > =C2=A0bDeviceClass =3D 0x0000 > =C2=A0bDeviceSubClass =3D 0x0000 > =C2=A0bDeviceProtocol =3D 0x0000 > =C2=A0bMaxPacketSize0 =3D 0x0040 > =C2=A0idVendor =3D 0x067b > =C2=A0idProduct =3D 0x2303 > =C2=A0bcdDevice =3D 0x0300 > =C2=A0iManufacturer =3D 0x0001 =C2=A0 > =C2=A0iProduct =3D 0x0002 =C2=A0 > =C2=A0iSerialNumber =3D 0x0000 =C2=A0 > =C2=A0bNumConfigurations =3D 0x0001 > > > * dmesg when I connect the cable: > ugen1.2: at usbus1 > uplcom0: rev 1.10/3.00, addr 2> on usbus1 > > * KLDSTAT > Id Refs Address =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Size =C2=A0 =C2= =A0 Name > =C2=A01 =C2=A0 36 0xffffffff80200000 d58c20 =C2=A0 kernel > =C2=A03 =C2=A0 =C2=A01 0xffffffff80f6c000 104ab40 =C2=A0nvidia.ko > =C2=A04 =C2=A0 =C2=A04 0xffffffff81fb7000 45218 =C2=A0 =C2=A0linux.ko > =C2=A05 =C2=A0 =C2=A01 0xffffffff82212000 13300f =C2=A0 zfs.ko > =C2=A06 =C2=A0 =C2=A01 0xffffffff82346000 2fb5 =C2=A0 =C2=A0 opensolaris.= ko > =C2=A07 =C2=A0 =C2=A01 0xffffffff82349000 3d5d =C2=A0 =C2=A0 linprocfs.ko > =C2=A08 =C2=A0 =C2=A01 0xffffffff8234d000 24c19 =C2=A0 =C2=A0wpifw.ko > 10 =C2=A0 =C2=A01 0xffffffff82374000 2a4c1 =C2=A0 =C2=A0pf.ko > 11 =C2=A0 =C2=A01 0xffffffff8239f000 762 =C2=A0 =C2=A0 =C2=A0rtc.ko > 12 =C2=A0 =C2=A01 0xffffffff82372000 1fd5 =C2=A0 =C2=A0 uplcom.ko > > * stty -a -f /dev/cuaU0 > speed 9600 baud; 0 rows; 0 columns; > lflags: icanon isig iexten echo echoe -echok echoke -echonl echoctl > =C2=A0 =C2=A0 =C2=A0 -echoprt -altwerase -noflsh -tostop -flusho -pendin = -nokerninfo > =C2=A0 =C2=A0 =C2=A0 -extproc > iflags: -istrip icrnl -inlcr -igncr ixon -ixoff ixany imaxbel -ignbrk > =C2=A0 =C2=A0 =C2=A0 brkint -inpck -ignpar -parmrk > oflags: opost onlcr -ocrnl tab0 -onocr -onlret > cflags: cread cs8 -parenb -parodd hupcl -clocal -cstopb -crtscts -dsrflow > =C2=A0 =C2=A0 =C2=A0 -dtrflow -mdmbuf > cchars: discard =3D ^O; dsusp =3D ^Y; eof =3D ^D; eol =3D ; > =C2=A0 =C2=A0 =C2=A0 eol2 =3D ; erase =3D ^?; erase2 =3D ^H; intr = =3D ^C; kill =3D ^U; > =C2=A0 =C2=A0 =C2=A0 lnext =3D ^V; min =3D 1; quit =3D ^\; reprint =3D ^R= ; start =3D ^Q; > =C2=A0 =C2=A0 =C2=A0 status =3D ^T; stop =3D ^S; susp =3D ^Z; time =3D 0;= werase =3D ^W; > > I tried to change the above parameters with "stty" by > hand using cuaU0, cuaU0.init and cuaU0.lock before using cu, tip > and minicom. I tried different combinations to the parameters of > the connections but still the problem persist. > > My problem is exactly the same to that reported here: > http://lists.freebsd.org/pipermail/freebsd-usb/2011-July/010443.html > > If I try to do: > sysctl hw.usb.ucom.debug=3D15 > > I see in dmesg after "cu -t -s 19200 -l /dev/cuaU0": > > ucom_attach_tty: ttycreate: U0 > ucom_attach: tp =3D 0xfffffe0005e08800, unit =3D 0, subunits =3D 1 > ucom_open: tp =3D 0xfffffe0005e08800 > ucom_dtr: onoff =3D 1 > ucom_line_state: on=3D0x01, off=3D0x00 > ucom_rts: onoff =3D 1 > ucom_line_state: on=3D0x02, off=3D0x00 > ucom_ring: onoff =3D 0 > ucom_line_state: on=3D0x00, off=3D0x08 > ucom_break: onoff =3D 0 > ucom_line_state: on=3D0x00, off=3D0x04 > ucom_status_change: > ucom_param: sc =3D 0xfffffe0005106880 > ucom_dtr: onoff =3D 1 > ucom_line_state: on=3D0x01, off=3D0x00 > ucom_rts: onoff =3D 1 > ucom_line_state: on=3D0x02, off=3D0x00 > ucom_cfg_open: > ucom_ioctl: cmd =3D 0x402c7413 > ucom_ioctl: cmd =3D 0x802c7416 > ucom_ioctl: cmd =3D 0x2000740d > ucom_ioctl: cmd =3D 0x402c7413 > ucom_ioctl: cmd =3D 0x802c7416 > ucom_param: sc =3D 0xfffffe0005106880 > ucom_ioctl: cmd =3D 0x8004667e > ucom_ioctl: cmd =3D 0x8004667d > ucom_status_change: > ucom_status_change: > ucom_get_data: cnt=3D0 > ucom_outwakeup: sc =3D 0xfffffe0005106880 > ucom_get_data: cnt=3D1 > ucom_outwakeup: sc =3D 0xfffffe0005106880 > ucom_outwakeup: sc =3D 0xfffffe0005106880 > uplcom0: at uhub1, port 1, addr 2 (disconnected) > ucom_detach_tty: sc =3D 0xfffffe0005106880, tp =3D 0xfffffe0005e08800 > ucom_close: tp=3D0xfffffe0005e08800 > ucom_close: tp=3D0xfffffe0005e08800 already closed > uplcom0: rev 1.10/3.00, addr 2> on usbus1 > ucom_attach_tty: ttycreate: U0 > ucom_attach: tp =3D 0xfffffe0007953400, unit =3D 0, subunits =3D 1 > > > Do you have any idea where to give a look to fix my problem? > Do you need other information? > I suspect that the device is continuously disconnecting and reconnecting > in background...but it is just a suspect. > I run out of resources and brain but I still need to solve my problem > and connect with my remote Alix board using FreeBSD or NetBSD. > > Thank you, > best regards > > Fabio Balzano From owner-freebsd-usb@FreeBSD.ORG Mon Mar 19 11:07:24 2012 Return-Path: Delivered-To: freebsd-usb@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A0D541065673 for ; Mon, 19 Mar 2012 11:07:24 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 8A8718FC1F for ; Mon, 19 Mar 2012 11:07:24 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q2JB7O0B033744 for ; Mon, 19 Mar 2012 11:07:24 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q2JB7NAm033742 for freebsd-usb@FreeBSD.org; Mon, 19 Mar 2012 11:07:23 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 19 Mar 2012 11:07:23 GMT Message-Id: <201203191107.q2JB7NAm033742@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-usb@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-usb@FreeBSD.org X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Mar 2012 11:07:24 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o usb/165815 usb add k3772z 3g modem support o usb/165163 usb [keyboard] The USB RF keyboard and mouse become non-re o usb/164058 usb Lexar 8GB USB flash drive doesn't work by default o usb/163328 usb [usb] Support for Atheros USB abgn devices o kern/163091 usb [panic] Fatal trap 12: page fault while in kernel mode o usb/162306 usb usb devices cant get address asignation, no memories, o usb/162054 usb usbdump just hangs on 9.0-RC1 f usb/161793 usb poor EHCI usb2 i/o performance o usb/160436 usb ucom wedges machine on parity error ? o usb/160299 usb MicroSDHC-to-USB adapters do not work in FreeBSD 8.x o usb/160192 usb [install] Installation from USB-Stick doesn't find the o usb/159274 usb USB 3.0 Etron EJ168A does not work. f usb/159191 usb [fusefs-ntfs] write on fusefs-ntfs mounted partition r o usb/157376 usb LaCie USB disk not recognized o usb/157074 usb [boot] [usb8] vfs_mountroot_ask is called when no usb o usb/156898 usb [keyboard] usb keyboard does not work while boot (ps2 f usb/156735 usb Need Quirk for Goflex USB Disk Drives o usb/156725 usb USB stack stall cause complete system input loss o usb/156596 usb [ehci] Extremely high interrupt rate on ehci/uhci IRQ1 o usb/156000 usb rum(4) Fatal trap 18: integer divide fault while in ke f usb/155996 usb NanoBSD not booted as Disk o usb/155784 usb Problem with Transcend StoreJet 25M3 (2AJ1) on Asus M2 o usb/154506 usb [umass] Copying dir with large files makes FreeBSD loa o usb/154192 usb [umass] In Garmin Oregon GPS, only the first umass dev o i386/153851 usb [keyboard] keyboard issues on new Intel Mother boards. o usb/153703 usb [keyboard] My USB keyboard can not be used in 8-STABLE o usb/153609 usb [zyd] [panic] kernel: Fatal trap 12: page fault while o usb/153149 usb [umass] USB stick quirk regression [regression] o usb/152075 usb [usb8] [ehci] [request] Add quirk for CS5536 USB o usb/150892 usb [zyd] Whenever network contacted in any shape, way or o usb/150189 usb [run] [usb8] [patch] if_run appears to corrupt IP traf p usb/149764 usb [u3g] [patch] usbdevs update: Huawei K3765 3G modem o usb/149283 usb [uftdi] avrdude unable to talk to Arduino board (via u o usb/149162 usb [ural] ASUS WL-167g doesn't work in 8.1 (continue of 1 s usb/148702 usb [usb8] [request] IO DATA USB-RSAQ5 support on FreeBSD- o usb/148080 usb usbconfig(8) sometimes does not turn off the device o usb/147516 usb [umass] [usb67] kernel unable to deal with Olympus USB o i386/147475 usb [install] FreeBSD 8.x does not install on ASUS K8N4-E o usb/146840 usb [hang] FreeBSD 7.2 / 7.3 / 8.0 hang at startup after e o usb/146153 usb [axe] [usb8] Hosts in network doesn't receive any pack f usb/146054 usb [urtw] [usb8] urtw driver potentially out of date f usb/145513 usb [usb8] New USB stack: no new devices after forced usb p usb/145455 usb [usb8] [patch] USB debug support cannot be disabled o usb/145415 usb [umass] [usb8] USB card reader does not create slices a usb/145184 usb GENERIC can't mount root from USB on Asus EEE o usb/145165 usb [keyboard] [usb8] ukbd_set_leds_callback: error=USB_ER f kern/144938 usb [keyboard] [boot] Boot Failure with Apple (MB869LL/A) o usb/144387 usb [run] [panic] if_run panic o usb/144043 usb [umass] [usb8] USB DLT tape drive throws random errors a usb/143790 usb [boot] [cam] can not boot from usb hdd f usb/143620 usb [cdce] [usb8] the module if_cdce doesn't support my Op f usb/143294 usb [usb8] copying process stops at some time (10 - 50 sec o usb/143286 usb [ukbd] [usb8] [boot] boot failures on RELENG_8 system p usb/143186 usb [usbdevs] [usb8] [patch] add USB device IDs for Google a usb/143139 usb [umass] [usb8] [patch] Quirk for Century EX35SW4_SB4 J p usb/143045 usb [umass] [usb8] [patch] mounting Fujitsu 2600Z camera d o usb/142991 usb [uftdi] [usb67] [patch] Patch to add Crystalfontz 533 f usb/142989 usb [usb8] canon eos 50D attaches but detaches after few s f usb/142957 usb [umass] [usb8] [patch] patch for USB disk SYNCHRONIZE o usb/142719 usb [urtw] [usb8] AirLive WL-1600USB (RTL8187L chipset) fa o usb/142713 usb [usb67] [panic] Kernel Panik when connecting an IPhone f usb/142276 usb [umass] [usb8] Cache Synchronization Error with Olympu o usb/142229 usb [ums] [usb8] [hang] connecting a USB mouse to a Dell P f usb/141680 usb [uath] [usb8] Netgear WG111T not working with uath dri o usb/141664 usb [pcm] [usb8] Logitech USB microphone failure [regressi o usb/141474 usb [boot] [usb8] FreeBSD 8.0 can not install from USB CDR o usb/141327 usb [ukbd] [usb67] USB kbd not working with 7.1+PAE on IBM o usb/141212 usb [ukbd] [usb8] ukbd_set_leds_callback:700: error=USB_ER o kern/141011 usb [usb8] Encrypted root, geli password at boot; enter ke o usb/140920 usb [install] [usb8] USB based install fails on 8.0-RELEAS o usb/140893 usb [urtw] [usb8] WPA2 not working on rtl8187b o kern/140849 usb [ums] [usb8] USB mouse doesn't work under FreeBSD 8.0- a usb/140810 usb [uftdi] [usb8] 8.X copy and paste problem / tty overfl o usb/140477 usb [umass] [usb8] [patch] allow boot-time attachment of d o usb/140236 usb [msdosfs] [usb8] Labels wiped on external Journaled US o usb/140160 usb [usb8] [acpi] USB ports are no longer "active" after A s usb/139990 usb [panic] [patch] [usb67] Kernel frequently panics after o usb/139243 usb [uhci] [usb67] unplug prolific USB serial -> uhci_abor f usb/138882 usb [ohci] [panic] [usb67] Can't install FreeBSD 7.2 due t o usb/138798 usb [boot] [usb8] 8.0-BETA4 can't boot from USB flash driv o usb/138659 usb [usb8][uftdi] driver broken in RELENG_8/CURRENT o usb/138175 usb [usb67] [boot] System cannot boot, when USB reader wit o usb/138124 usb [snd_uaudio] [usb8] Axed uaudio functionality in the u o usb/138119 usb [usb67] [usb8] MultiBay CDROM (probably on USB bus) is f usb/137872 usb [usb67] [boot] slow booting on usb flash drive o usb/137806 usb [ukbd] [usb67] USB keyboard doesn't work until it's un o usb/137763 usb [usb67][ukbd] Logitech wireless keyboard media keys no o usb/137377 usb [usb8] request support for Huawei E180 o usb/137341 usb [usb8][rum] driver if_rum doesn't work at all and thro f usb/137190 usb [usb8][patch] inhibit spurious button releases for som o usb/137189 usb [usb8][patch] create and use sysctl nodes for HID repo p usb/137188 usb [usb8][patch] correctly handle USB report descriptors o usb/137129 usb [ums] [usb8] SteelSeries Ikari USB laser mouse not att o usb/135938 usb [aue] [usb67] aue driver only passes traffic in promis o usb/135542 usb [keyboard] boot loader does not work with a usb keyboa o usb/135206 usb machine reboots when inserted USB device f usb/135200 usb SAMSUNG i740 usb mass: Synchronize cache failed, statu o usb/134950 usb Lowering DTR for USB-modem via ubsa is not possible o usb/134299 usb Kernel Panic plugging in MF626 USB UMTS Stick u3g o usb/134193 usb System freeze on usb MP3 player insertion o usb/134085 usb [umass] Adding usb quirk for Sony USB flash drive o usb/133989 usb [usb8] [ukbd] USB keyboard dead at mountroot> prompt o usb/133712 usb [ural] [patch] RE: Fixed an issue with ural(4) that wa o usb/133390 usb umass crashes system in 7.1 when Olympus D-540 attache o usb/133296 usb [rum] driver not working properly in hostap mode o usb/132594 usb USB subsystem causes page fault and crashes o usb/132080 usb [patch] [usb] [rum] [panic] Kernel panic after NOMEM c o usb/132066 usb [ukbd] Keyboard failure USB keyboard DELL 760 o usb/132036 usb [panic] page fault when connecting Olympus C740 camera o usb/131583 usb [umass] Failure when detaching umass Device o usb/131576 usb [aue] ADMtek USB To LAN Converter can't send data o usb/131521 usb Registering Belkin UPS to usb_quirks.c o usb/131074 usb no run-time detection of usb devices plugged into exte o usb/130736 usb Page fault unplugging USB stick o usb/130230 usb [patch] [quirk] [usb67] [usb] [cam] [umass] Samsung El o usb/130208 usb Boot process severely hampered by umass0 error o usb/130122 usb [usb8] DVD drive detects as 'da' device f usb/129766 usb [usb] [panic] plugging in usb modem HUAWEI E226 panics o usb/129500 usb [umass] [panic] FreeBSD Crashes when connecting SanDis o usb/129311 usb [usb] [panic] Instant crash with an USB card reader s usb/128990 usb [usb] u3g does not handle RTS/CTS available on for exa o usb/128977 usb [usb67] [patch] uaudio is not full duplex p usb/128803 usb [usbdevs] [patch] Quirk for I-Tuner Networks USBLCD4X2 o usb/128485 usb [umodem] [patch] Nokia N80 modem support o usb/128425 usb [umass] Cannot Connect Maxtor Onetouch 4 USB drive o usb/128418 usb [panic] [rum] loading if_rum causes panic, looks like o usb/127926 usb [boot] USB Timeout during bootup s usb/127453 usb [request] ubsa, uark, ubser, uftdi, and friends should o usb/127342 usb [boot] [panic] enabling usb keyboard and mouse support o usb/127248 usb [ucom] panic while uplcom devices attach and detach o usb/126884 usb [ugen] [patch] Bug in buffer handling in ugen.c o usb/126848 usb [usb]: USB Keyboard hangs during Installation o usb/126740 usb [ulpt] doesn't work on 7.0-RELEASE, 10 second stall be o usb/126519 usb [usb] [panic] panic when plugging in an iphone o kern/126396 usb [panic] kernel panic after unplug USB Bluetooth device o usb/125631 usb [ums] [panic] kernel panic during bootup while 'Logite o usb/125510 usb [panic] repeated plug and unplug of USB mass storage d f usb/125450 usb [panic] Removing USB flash card while being accessed c o usb/125088 usb [keyboard] Touchpad not detected on Adesso AKB-430UG U o usb/124980 usb [panic] kernel panic on detaching unmounted umass devi o kern/124777 usb [ucom] USB cua devices don't revert to tty devices whe o usb/124758 usb [rum] [panic] rum panics SMP kernel o usb/124708 usb [panic] Kernel panic on USB KVM reattach o kern/124130 usb [usb] gmirror fails to start usb devices that were pre o usb/123969 usb [usb] Supermicro H8SMi-2 usb problem: port reset faile o usb/123714 usb [usb] [panic] Panic when hald-storage-probe runs with o usb/123691 usb usbd(8): usbd hangs o usb/123690 usb [usb] [panic] Panic on USB device insertion when usb l o usb/123611 usb [usb] BBB reset failed, STALLED from Imation/Mitsumi U o usb/122992 usb [umass] [patch] MotoROKR Z6 Phone not recognised by um o usb/122936 usb [ucom] [ubsa] Device does not receive interrupt o usb/122905 usb [ubsa] [patch] add Huawei E220 to ubsa s usb/122819 usb [usb67] [patch] Patch to provide dynamic additions to o usb/122813 usb [udbp] [request] udbp driver should be removed in favo o usb/122547 usb [ehci] USB Printer not being recognized after reboot o usb/122539 usb [ohci] [panic] AnyDATA ADU-E1000D - kernel panic: ohci o usb/122483 usb [panic] [ulpt] Repeatable panic in 7.0-STABLE o usb/122119 usb [umass] umass device causes creation of daX but not da o usb/121734 usb [ugen] ugen HP1022 printer device not working since up o usb/121708 usb [keyboard] nforce 650i mobo w/ usb keyboard infinite k o usb/121474 usb [cam] [patch] QUIRK: SAMSUNG HM250JI in LaCie usb hard o usb/121275 usb [boot] [panic] FreeBSD fails to boot with usb legacy s o usb/121169 usb [umass] Issues with usb mp3 player o usb/121045 usb [uftdi] [patch] Add support for PC-OP-RS1 and KURO-RS f usb/120786 usb [usb] [panic] Kernel panic when forced umount of a det o usb/120729 usb [panic] fault while in kernel mode with connecting USB o usb/120321 usb [hang] System hangs when transferring data to WD MyBoo o usb/120283 usb [panic] Automation reboot with wireless keyboard & mou o usb/120034 usb [hang] 6.2 & 6.3 hangs on boot at usb0: OHCI with 1.5 o usb/119977 usb [ums] Mouse does not work in a Cherry-USB keyboard/mou o usb/119653 usb [cam] [patch] iriver s7 player sync cache error patch o usb/119633 usb [umass] umass0: BBB reset failed, IOERROR [regression] o usb/119509 usb [usb] USB flaky on Dell Optiplex 755 o usb/119389 usb [umass] Sony DSC-W1 CBI reset failed, STALLED [regress o usb/119227 usb [ubsa] [patch] ubsa buffer is too small; should be tun o usb/119201 usb [cam] [patch] Quirks for Olympus FE-210 camera, LG and o usb/118480 usb [umass] Timeout in USB mass storage freezes vfs layer o usb/118353 usb [panic] [ppp] repeatable kernel panic during ppp(4) se o usb/118141 usb [ucom] usb serial and nokia phones ucomreadcb ucomread o usb/118140 usb [ucom] [patch] quick hack for ucom to get it behave wi o usb/118098 usb [umass] 6th gen iPod causes problems when disconnectin o usb/117955 usb [umass] [panic] inserting minolta dimage a2 crashes OS o usb/117946 usb [panic] D-Link DUB-E100 rev. B1 crashes FreeBSD 7.0-BE o usb/117938 usb [ums] [patch] Adding support for MS WL Natural and MS o usb/117911 usb [ums] [request] Mouse Gembird MUSWC not work o usb/117893 usb [umass] Lacie USB DVD writing failing o usb/117613 usb [uhci] [irq] uhci interrupt storm & USB leaked memory o usb/117598 usb [snd_uaudio] [patch] Not possible to record with Plant o usb/117313 usb [umass] [panic] panic on usb camera insertion o usb/117200 usb [ugen] ugen0 prints strange string on attach if detach o usb/117183 usb [panic] USB/fusefs -- panic while transferring large a p usb/116947 usb [ukbd] [patch] [regression] enable boot protocol on th o usb/116561 usb [umodem] [panic] RELENG_6 umodem panic "trying to slee o usb/116282 usb [ulpt] Cannot print on USB HP LJ1018 or LJ1300 o usb/115935 usb [usbdevs] [patch] kernel counterproductively attaches o usb/115933 usb [uftdi] [patch] RATOC REX-USB60F (usb serial converter o usb/115400 usb [ehci] Problem with EHCI on ASUS M2N4-SLI o usb/115298 usb [ulpt] [panic] Turning off USB printer panics kernel o usb/114916 usb [umass] [patch] USB Maxtor drive (L300RO) requires qui o kern/114780 usb [uplcom] [panic] Panics while stress testing the uplco o usb/114682 usb [umass] generic USB media-card reader unusable o usb/114310 usb [libusb] [patch] [panic] USB hub attachment panics ker o usb/114068 usb [usb67] [usb8] [umass] [patch] Problem with connection o conf/114013 usb [patch] WITHOUT_USB allow to compil a lot of USB stuff s usb/113060 usb [usb67] [ulpt] [patch] Samsung printer not working in o usb/110856 usb [usb67] [ugen] [patch] interrupt in msgs are truncated o usb/107827 usb [usb67] [ohci] [panic] ohci_add_done addr not found o usb/107388 usb [usb67] [usb8] [new driver] [patch] add utoppy device o usb/106041 usb [usb67] [usb8] [request] FreeBSD does not recognise Mu s usb/103917 usb [usb67] [uhub] USB driver reports "Addr 0 should never o usb/103418 usb [usb67] [usb8] [patch] [request] usbhidctl(8) add abil o usb/103046 usb [usb67] [ulpt] [patch] ulpt event driven I/O with sele o usb/100746 usb [usb67] [ukbd] system does not boot due to USB keyboar o usb/99431 usb [keyboard] FreeBSD on MSI 6566E (Intel 845E motherboar o kern/99200 usb [usb67] SMP-Kernel crashes reliably when Bluetooth con o usb/98343 usb [boot] BBB reset failed errors with Creative Muvo MP3 o usb/97472 usb [cam] [patch] add support for Olympus C150,D390 s usb/97286 usb [mouse] [request] MS Wireless Intellimouse Explorer 2. o usb/97175 usb [umass] [hang] USB cardreader hangs system o usb/96457 usb [umass] [panic] fatback on umass = reboot o usb/96381 usb [cam] [patch] add a quirk table entry for a flash ram o usb/96224 usb [usb] [msdosfs] mount_msdosfs cause page fault in sync s usb/96120 usb [ums] [request] USB mouse not always detected s usb/95636 usb [umass] [boot] 5 minute delay at boot when using VT620 o usb/95562 usb [umass] Write Stress in USB Mass drive causes "vinvalb o usb/95037 usb [umass] USB disk not recognized on hot-plug. o usb/94897 usb [panic] Kernel Panic when cleanly unmounting USB disk o usb/94717 usb [ulpt] Reading from /dev/ulpt can break work of a UHCI o usb/94384 usb [panic] kernel panic with usb2 hardware o usb/93872 usb [cam] [patch] SCSI quirk required for ELTA 8061 OL USB o usb/93828 usb [ohci] [panic] ohci causes panic on boot (HP Pavillion o usb/93389 usb [umass] [patch] Digital Camera Pentax S60 don't work o usb/92852 usb [ums] [patch] Vertical scroll not working properly on o usb/92171 usb [panic] panic unplugging Vodafone Mobile Connect (UMTS o usb/92142 usb [uhub] SET_ADDR_FAILED and SHORT_XFER errors from usb o usb/92083 usb [ural] [panic] panic using WPA on ural NIC in 6.0-RELE o usb/92052 usb [ulpt] usbd causes defunct process with busy file-hand o usb/91906 usb [ehci] [hang] FreeBSD hangs while booting with USB leg f usb/91896 usb camcontrol(8): Serial Number of USB Memory Sticks is n o usb/91811 usb [umass] Compact Flash in HP Photosmart 2610 return " o usb/91546 usb [umodem] [patch] Nokia 6630 mobile phone does not work o usb/91538 usb [ulpt] [patch] Unable to print to EPSON CX3500 o usb/91283 usb [boot] [regression] booting very slow with usb devices o usb/91238 usb [umass] USB tape unit fails to write a second tape fil o usb/90700 usb [umass] [panic] Kernel panic on connect/mount/use umas o usb/89954 usb [umass] [panic] USB Disk driver race condition? s usb/89003 usb [request] LaCie Firewire drive not properly supported o usb/88743 usb [hang] [regression] USB makes kernel hang at boot (reg o usb/88408 usb [axe] axe0 read PHY failed o usb/87648 usb [mouse] Logitech USB-optical mouse problem. f usb/87224 usb [usb] Cannot mount USB Zip750 o usb/86767 usb [umass] [patch] bogus "slice starts beyond end of the o usb/86298 usb [mouse] Known good USB mouse won't work with correct s s usb/85067 usb [uscanner] Cannot attach ScanJet 4300C to usb device o usb/83977 usb [ucom] [panic] ucom1: open bulk out error (addr 2): IN o usb/83863 usb [ugen] Communication problem between opensc/openct via o usb/83756 usb [ums] [patch] Microsoft Intellimouse Explorer 4.0A doe o usb/83504 usb [kernel] [patch] SpeedTouch USB stop working on recent o usb/82520 usb [udbp] [reboot] Reboot when USL101 connected o usb/82350 usb [ucom] [panic] null pointer dereference in USB stack o usb/81621 usb [ehci] [hang] external hd hangs under load on ehci o usb/80935 usb [uvisor] [patch] uvisor.c is not work with CLIE TH55. s usb/80777 usb [request] usb_rem_task() should wait for callback to c s usb/80776 usb [udav] [request] UDAV device driver shouldn't use usb_ o usb/80774 usb [patch] have "usbd_find_desc" in line with the other " o usb/80361 usb [umass] [patch] mounting of Dell usb-stick fails f usb/80040 usb [sound] [hang] Use of sound mixer causes system freeze o usb/79723 usb [usb] [request] prepare for high speed isochronous tra o usb/78984 usb [umass] [patch] Creative MUVO umass failure f usb/77294 usb [ucom] [panic] ucom + ulpcom panic o usb/76653 usb [umass] [patch] Problem with Asahi Optical usb device f usb/76395 usb [uhci] USB printer does not work, usbdevs says "addr 0 s usb/75928 usb [umass] [request] Cytronix SmartMedia card (SMC) reade o usb/75800 usb [ucom] ucom1: init failed STALLED error in time of syn o usb/75764 usb [umass] [patch] "umass0: Phase Error" - no device for f usb/75705 usb [umass] [panic] da0 attach / Optio S4 (with backtrace) f usb/74771 usb [umass] [hang] mounting write-protected umass device a s usb/74453 usb [umass] [patch] Q-lity CD-RW USB ECW-043 (ScanLogic SL o usb/74211 usb [umass] USB flash drive causes CAM status 0x4 on 4.10R o usb/71417 usb [ugen] Cryptoflex e-gate USB token (ugen0) communicati o usb/71416 usb [ugen] Cryptoflex e-gate USB token (ugen0) detach is n o usb/71280 usb [aue] aue0 device (linksys usb100tx) doesn't work in 1 o usb/71155 usb [ulpt] misbehaving usb-printer hangs processes, causes o usb/69006 usb [usbdevs] [patch] Apple Cinema Display hangs USB ports o usb/67301 usb [uftdi] [panic] RTS and system panic o usb/66547 usb [ucom] Palm Tungsten T USB does not initialize correct o usb/63621 usb [umass] [panic] USB MemoryStick Reader stalls/crashes s usb/62257 usb [umass] [request] card reader UCR-61S2B is only half-s s bin/57255 usb [patch] usbd(8) and multi-function devices s usb/52026 usb [usb] [request] umass driver support for InSystem ISD2 s usb/51958 usb [urio] [patch] update for urio driver o usb/40948 usb [umass] [request] USB HP CDW8200 does not work o usb/30929 usb [usb] [patch] use usbd to initialize USB ADSL modem 293 problems total. From owner-freebsd-usb@FreeBSD.ORG Tue Mar 20 06:32:37 2012 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 14FF21065673 for ; Tue, 20 Mar 2012 06:32:37 +0000 (UTC) (envelope-from bounce@vikingpchealth.com) Received: from vdc.vikingpc.org (unknown [IPv6:2604:7800:0:1:2063:daff:fe01:f2e3]) by mx1.freebsd.org (Postfix) with ESMTP id 917F28FC0C for ; Tue, 20 Mar 2012 06:32:36 +0000 (UTC) Received: from centos ([127.0.0.1] helo=pccleanuppro.com) by vdc.vikingpc.org with esmtp (Exim 4.69) (envelope-from ) id 1S8oS7-0003bk-RS for freebsd-usb@freebsd.org; Sat, 17 Mar 2012 03:53:27 -0400 To: freebsd-usb@freebsd.org Message-ID: <8f4ae571dfbf87770bf8e0d23ee485b9@pccleanuppro.com> Date: Fri, 16 Mar 2012 12:16:57 -0400 From: "DigitalTV" MIME-Version: 1.0 X-Mailer-LID: 7 X-Mailer-RecptId: 672422 X-Mailer-SID: 27 X-Mailer-Sent-By: 1 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - vdc.vikingpc.org X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - vikingpchealth.com Content-Type: text/plain; format=flowed; charset="UTF-8" Content-Transfer-Encoding: 8bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Watch tv on your pc X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: noreply@vikingpchealth.com List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Mar 2012 06:32:37 -0000 DigitalTVforPC Stop paying monthly subscription fees. DigitalTVforPC 2 delivers more channels than satellite TV & cable combined without all the hardware charges, pay-per view costs, and monthly fees. Start Watching Instantly! Get Worldwide news, sports, feature-lenght movies, full TV episodes, and more on your PC from anywhere in the world! Stop paying monthly fees. Learn how. " A lot easier to install than I thought. I was watching live TV on my PC in minutes. Impressive." Louis M. - Sacramento, Ca With DigitalTVforPC you get many advantages: Over 2,318 LIVE TV Channels! Unlimited Viewing No Hardware No Monthly Fees No Subscription No Contract Get MORE with DigitalTVforPC Our software technology leverages the power of our playback engine and proprietary entertainment database to connect you directly to hundreds of live digital channels from across the world. Viewing these channels is simple , allowing you to watch all you want, wherever you want whenever your PC is connected to the Internet. All at no extra cost! Imagine watching 2,318 live channels whenever you want, wherever you want all at the convenience and comfort of your desktop or laptop computer! This message was intended for: %freebsd-usb@freebsd.org% Unsubscribe me from this list Click this link to unsubscribe: http://pccleanuppro.com/vem/unsubscribe.php?M=672422&C=67ad192aa53dfcf0c5cd2bb752f630f4&L=7&N=27 From owner-freebsd-usb@FreeBSD.ORG Tue Mar 20 15:23:20 2012 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ECC151065670 for ; Tue, 20 Mar 2012 15:23:20 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 8EBEC8FC17 for ; Tue, 20 Mar 2012 15:23:20 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.5/8.14.5) with ESMTP id q2KFNJ8O096647; Tue, 20 Mar 2012 09:23:19 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.5/8.14.5/Submit) with ESMTP id q2KFNJsn096644; Tue, 20 Mar 2012 09:23:19 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Tue, 20 Mar 2012 09:23:19 -0600 (MDT) From: Warren Block To: Fabio Dive In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Tue, 20 Mar 2012 09:23:19 -0600 (MDT) Cc: freebsd-usb@freebsd.org Subject: Re: USB serial adapter, cu write: Device not configured X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Mar 2012 15:23:21 -0000 On Sun, 18 Mar 2012, Warren Block wrote: > On Sun, 18 Mar 2012, Fabio Dive wrote: > >> Hello people! >> >> I write you because I have got a problem with the uplcom driver >> on FreeBSD 9.0, I tried a lot of different things, read all I found, >> manpages, forums, irc, google but still not able to solve my problem. >> >> I need to connect to my remote Alix board, >> the remote console setup is 19200 8N1. >> I am using a short USB Prolific Tec.. serial cable adapter with a >> NULL modem cable, the last one plugged one side to the Alix board, >> the other side to the adapter cable. >> >> Under Linux Debian everything is fine, so the hardware and cables >> should be ok, under Linux I used minicom and cu and tip without problems. >> With FreeBSD and NetBSD, big problems..the result is always >> the same, I can receive but I cannot transmit. >> >> (working as root) >> *cu -t -s 19200 -l /dev/cuaU0 >> write: Device not configured >> (I can't transmit but I can receive the output if I reboot the remote >> alix board) > > Add the user to the dialer group. If that doesn't do it, make sure the user > has write permission to the USB device and /dev/cuaU0. Managed to locate my PL2303 cable, and it works on 9-stable amd64 built yesterday: % cu -l /dev/cuaU0 -s 19200 can't open log file /var/log/aculog. Connected AT OK ~ [EOT] I typed the "AT". If the USB cable is disconnected and reconnected while cu still has it open, typing a character produces write: Device not configured because the device disappeared when the USB cable was unplugged. The send and receive LEDs on this modem also both go on, meaning some data is being continuously sent and echoed. /etc/devfs.rules (just the USB ones) [localrules=10] add path 'ugen*' mode 0660 group operator add path 'usb/*' mode 0660 group operator The user is a member of both dialer and operator groups. If it still does not work for you, check loader.conf and rc.conf for nonstandard settings. From owner-freebsd-usb@FreeBSD.ORG Tue Mar 20 15:45:28 2012 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C50EE106566B for ; Tue, 20 Mar 2012 15:45:28 +0000 (UTC) (envelope-from fabiodive@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id 7C66F8FC0C for ; Tue, 20 Mar 2012 15:45:28 +0000 (UTC) Received: by yenl9 with SMTP id l9so223588yen.13 for ; Tue, 20 Mar 2012 08:45:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=MyGKAVu0c/YtqlIrBoMStDCYoLHImXWhwdkH7Gdqmq0=; b=jJY5Y8CDVN5lWsLnLvFMotFlxfOh71Z8m5bxqCcJzvvf3N/oWE+ETas6UFYKuw91Tn TlSJfVQyxTnTGOsGYb6+aecoCP+PFsFn/pc/NcQNe8SmWtRlpMYCBVxFLwobfAXDehp1 hvI4NxftIxe1U/tzzxuV1KtFox4pSRsS9M1/3TRpZGJReemFmBaQfSb0tzNpYCThom0I z1xpIjpKsuLodY0FCuqGUtXKvOc2Jq7wanwQ9rdL8meJ3WCdDGoXBFkrbBhyo/uSJ4lT hYdkqJR49YQ9yuvyZkWHPYX5itIp8tNQHe4jThLP3Y0TDklJOt1bPVuLEO9UmIxIj2DB jD4A== MIME-Version: 1.0 Received: by 10.224.182.201 with SMTP id cd9mr1283701qab.92.1332258327912; Tue, 20 Mar 2012 08:45:27 -0700 (PDT) Received: by 10.229.163.204 with HTTP; Tue, 20 Mar 2012 08:45:27 -0700 (PDT) In-Reply-To: References: Date: Tue, 20 Mar 2012 15:45:27 +0000 Message-ID: From: Fabio Dive To: Warren Block Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-usb@freebsd.org Subject: Re: USB serial adapter, cu write: Device not configured X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Mar 2012 15:45:28 -0000 Dear Warren thank you for your help, following your mail I found an additional strange behavior of my system, when I use cu, two processes are spawned at the same time: (ps aux output) seaman 80719 0.0 0.0 10048 1372 4 S+ 3:35PM 0:00.00 cu -t -eo -l /dev/cuaU0 -s 19200 seaman 80720 0.0 0.0 10048 1360 4 S+ 3:35PM 0:00.00 cu -t -eo -l /dev/cuaU0 -s 19200 on the console shell where cu lives I see: seaman@bluehouse:~$ cu -t -eo -l /dev/cuaU0 -s 19200 can't open log file /var/log/aculog. Connected [Now I Hit ENTER] write: Device not configured Now the communication hold and I can't do nothing anymore, hitting Enter or rebooting the remote device to see the bootstrap output doesn't work. I need to get out with ENTER~. And I get [EOT] about my environment: * cat /etc/devfs.rules [localrules=3D10] add path 'ugen*' mode 0660 group operator add path 'usb/*' mode 0660 group operator * cat /etc/rc.conf hostname=3D"bluehouse" ifconfig_em0=3D"DHCP" powerd_enable=3D"YES" # Set dumpdev to "AUTO" to enable crash dumps, "NO" to disable dumpdev=3D"NO" wlans_wpi0=3D"wlan0" ifconfig_wlan0=3D"WPA DHCP" background_dhclient=3D"YES" moused_enable=3D"NO" moused_nondefault_enable=3D"NO" hald_enable=3D"NO" linux_enable=3D"YES" dbus_enable=3D"YES" zfs_enable=3D"YES" ntpd_enable=3D"YES" #bitlbee_enable=3D"YES" gateway_enable=3D"YES" pf_enable=3D"YES" pf_rules=3D"/etc/pf.conf" pf_program=3D"/sbin/pfctl" pflog_enable=3D"NO" pflog_logfile=3D"/var/log/pflog" pflog_program=3D"/sbin/pflogd" fusefs_enable=3D"NO" devd_enable=3D"YES" devfs_system_ruleset=3D"localrules" * cat /boot/loader.conf if_wpi_load=3D"YES" nvidia_load=3D"YES" wlan_wep_load=3D"YES" wlan_ccmp_load=3D"YES" wlan_tkip_load=3D"YES" Thank you for your help f. On Tue, Mar 20, 2012 at 15:23, Warren Block wrote: > On Sun, 18 Mar 2012, Warren Block wrote: > >> On Sun, 18 Mar 2012, Fabio Dive wrote: >> >>> Hello people! >>> >>> I write you because I have got a problem with the uplcom driver >>> on FreeBSD 9.0, I tried a lot of different things, read all I found, >>> manpages, forums, irc, google but still not able to solve my problem. >>> >>> I need to connect to my remote Alix board, >>> the remote console setup is 19200 8N1. >>> I am using a short USB Prolific Tec.. serial cable adapter with a >>> NULL modem cable, the last one plugged one side to the Alix board, >>> the other side to the adapter cable. >>> >>> Under Linux Debian everything is fine, so the hardware and cables >>> should be ok, under Linux I used minicom and cu and tip without problem= s. >>> With FreeBSD and NetBSD, big problems..the result is always >>> the same, I can receive but I cannot transmit. >>> >>> (working as root) >>> *cu -t -s 19200 -l /dev/cuaU0 >>> write: Device not configured >>> (I can't transmit but I can receive the output if I reboot the remote >>> alix board) >> >> >> Add the user to the dialer group. =C2=A0If that doesn't do it, make sure= the >> user has write permission to the USB device and /dev/cuaU0. > > > Managed to locate my PL2303 cable, and it works on 9-stable amd64 built > yesterday: > > =C2=A0% cu -l /dev/cuaU0 -s 19200 > =C2=A0can't open log file /var/log/aculog. > =C2=A0Connected > =C2=A0AT > =C2=A0OK > =C2=A0~ > =C2=A0[EOT] > > I typed the "AT". =C2=A0If the USB cable is disconnected and reconnected = while cu > still has it open, typing a character produces > > =C2=A0write: Device not configured > > because the device disappeared when the USB cable was unplugged. =C2=A0Th= e send > and receive LEDs on this modem also both go on, meaning some data is bein= g > continuously sent and echoed. > > /etc/devfs.rules (just the USB ones) > > =C2=A0[localrules=3D10] > =C2=A0add path 'ugen*' mode 0660 group operator > =C2=A0add path 'usb/*' mode 0660 group operator > > The user is a member of both dialer and operator groups. > > If it still does not work for you, check loader.conf and rc.conf for > nonstandard settings. From owner-freebsd-usb@FreeBSD.ORG Tue Mar 20 15:49:54 2012 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 105CD106566C for ; Tue, 20 Mar 2012 15:49:54 +0000 (UTC) (envelope-from fabiodive@gmail.com) Received: from mail-qc0-f182.google.com (mail-qc0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id BA2378FC0C for ; Tue, 20 Mar 2012 15:49:53 +0000 (UTC) Received: by qcsg15 with SMTP id g15so99333qcs.13 for ; Tue, 20 Mar 2012 08:49:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=GLl7zUIO3BRWuLM6YfXh1a3XbrC1xxBxLFkiGAxO7Q4=; b=Zgfeu8b5APC9Mv43LVYpBmo60F7rAxqNVmEMAEjdBOiy+4Me5OgdoAjRGzwqj9gKrm euk2wNlK4Yj0xbSD6r1q0k5ZYG/R+ZKCkxCHY60TGOtlaoR3TY1+8ZdheS0Gn3TaGfMw kw0q+hfPC5r/jKBUN4sAmcEV96D9NDYKlBTgd/LPxv4LLmYiE/1eNibGONkEzYhaVmDa TR2hZotzlJqx7FrQVx7qyxzmehRjReNC4Vfko6wChoxgRB+TdRVdzCFNPX/FgU7NWf6Q VRdudU36/aFwyqdS3UqRa8iFtEpB0hgfs7aftKQ3SDUiqyLgi4YD/Bi6iSAfKIzW8R26 8Mgg== MIME-Version: 1.0 Received: by 10.224.205.130 with SMTP id fq2mr1382608qab.53.1332258593082; Tue, 20 Mar 2012 08:49:53 -0700 (PDT) Received: by 10.229.163.204 with HTTP; Tue, 20 Mar 2012 08:49:53 -0700 (PDT) In-Reply-To: References: Date: Tue, 20 Mar 2012 15:49:53 +0000 Message-ID: From: Fabio Dive To: Warren Block Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-usb@freebsd.org Subject: Re: USB serial adapter, cu write: Device not configured X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Mar 2012 15:49:54 -0000 I forget to remember that I am receiving the output of the remote device if I bootstrap it, I even receive the login prompt, but I am not able to transmit, hitting a key produce: write: Device not configured thank you f. On Tue, Mar 20, 2012 at 15:23, Warren Block wrote: > On Sun, 18 Mar 2012, Warren Block wrote: > >> On Sun, 18 Mar 2012, Fabio Dive wrote: >> >>> Hello people! >>> >>> I write you because I have got a problem with the uplcom driver >>> on FreeBSD 9.0, I tried a lot of different things, read all I found, >>> manpages, forums, irc, google but still not able to solve my problem. >>> >>> I need to connect to my remote Alix board, >>> the remote console setup is 19200 8N1. >>> I am using a short USB Prolific Tec.. serial cable adapter with a >>> NULL modem cable, the last one plugged one side to the Alix board, >>> the other side to the adapter cable. >>> >>> Under Linux Debian everything is fine, so the hardware and cables >>> should be ok, under Linux I used minicom and cu and tip without problem= s. >>> With FreeBSD and NetBSD, big problems..the result is always >>> the same, I can receive but I cannot transmit. >>> >>> (working as root) >>> *cu -t -s 19200 -l /dev/cuaU0 >>> write: Device not configured >>> (I can't transmit but I can receive the output if I reboot the remote >>> alix board) >> >> >> Add the user to the dialer group. =C2=A0If that doesn't do it, make sure= the >> user has write permission to the USB device and /dev/cuaU0. > > > Managed to locate my PL2303 cable, and it works on 9-stable amd64 built > yesterday: > > =C2=A0% cu -l /dev/cuaU0 -s 19200 > =C2=A0can't open log file /var/log/aculog. > =C2=A0Connected > =C2=A0AT > =C2=A0OK > =C2=A0~ > =C2=A0[EOT] > > I typed the "AT". =C2=A0If the USB cable is disconnected and reconnected = while cu > still has it open, typing a character produces > > =C2=A0write: Device not configured > > because the device disappeared when the USB cable was unplugged. =C2=A0Th= e send > and receive LEDs on this modem also both go on, meaning some data is bein= g > continuously sent and echoed. > > /etc/devfs.rules (just the USB ones) > > =C2=A0[localrules=3D10] > =C2=A0add path 'ugen*' mode 0660 group operator > =C2=A0add path 'usb/*' mode 0660 group operator > > The user is a member of both dialer and operator groups. > > If it still does not work for you, check loader.conf and rc.conf for > nonstandard settings. From owner-freebsd-usb@FreeBSD.ORG Tue Mar 20 15:59:56 2012 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 478BA106564A for ; Tue, 20 Mar 2012 15:59:56 +0000 (UTC) (envelope-from fabiodive@gmail.com) Received: from mail-qa0-f47.google.com (mail-qa0-f47.google.com [209.85.216.47]) by mx1.freebsd.org (Postfix) with ESMTP id EF2828FC15 for ; Tue, 20 Mar 2012 15:59:55 +0000 (UTC) Received: by qatm19 with SMTP id m19so1360404qat.13 for ; Tue, 20 Mar 2012 08:59:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=b0dsNz6DAcU5WynHzGPRCFUxbwcaI/Dm7TUsoUDjElU=; b=0+UMNiukvj9aZejW09v/V0O/fBxxFnn8XwhM84aL33gFNi6xQF3uSS75e5UqdPILwY sUADd4li/cio002WD1lNPcZO6nIMUSRxFtO17cDEm/3cQ4vMihOK9+vzsesS9x1jDyku C9sKLTP2vbDDg6Awt4JDVvRPuo1uEBoS6b+fASXOZjk0FUhe9k51RW4fs6ZPD8Zq0ak4 PdnkHtAXMok/VllNAR2UN+yvlpoziCPYtMC2YNVtmC04+D2omgkx0ztha06N+g/3i/dc JMLmQyrFOI+35ShqRItQekhI+Xro5pXyYg3aISBpz9XtKEQ3SzH6yXnmKEOOQqNlNXiz Ikbw== MIME-Version: 1.0 Received: by 10.229.77.76 with SMTP id f12mr153722qck.91.1332258697844; Tue, 20 Mar 2012 08:51:37 -0700 (PDT) Received: by 10.229.163.204 with HTTP; Tue, 20 Mar 2012 08:51:37 -0700 (PDT) In-Reply-To: References: Date: Tue, 20 Mar 2012 15:51:37 +0000 Message-ID: From: Fabio Dive To: Warren Block Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-usb@freebsd.org Subject: Re: USB serial adapter, cu write: Device not configured X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Mar 2012 15:59:56 -0000 the groups of the user seaman are: seaman@bluehouse:~$ groups seaman wheel kmem operator dialer vboxusers usb thank you f. On Tue, Mar 20, 2012 at 15:49, Fabio Dive wrote: > I forget to remember that I am receiving the output of the remote device > if I bootstrap it, I even receive the login prompt, but I am not able > to transmit, > hitting a key produce: > > write: Device not configured > > thank you > f. > > > > On Tue, Mar 20, 2012 at 15:23, Warren Block wrote: >> On Sun, 18 Mar 2012, Warren Block wrote: >> >>> On Sun, 18 Mar 2012, Fabio Dive wrote: >>> >>>> Hello people! >>>> >>>> I write you because I have got a problem with the uplcom driver >>>> on FreeBSD 9.0, I tried a lot of different things, read all I found, >>>> manpages, forums, irc, google but still not able to solve my problem. >>>> >>>> I need to connect to my remote Alix board, >>>> the remote console setup is 19200 8N1. >>>> I am using a short USB Prolific Tec.. serial cable adapter with a >>>> NULL modem cable, the last one plugged one side to the Alix board, >>>> the other side to the adapter cable. >>>> >>>> Under Linux Debian everything is fine, so the hardware and cables >>>> should be ok, under Linux I used minicom and cu and tip without proble= ms. >>>> With FreeBSD and NetBSD, big problems..the result is always >>>> the same, I can receive but I cannot transmit. >>>> >>>> (working as root) >>>> *cu -t -s 19200 -l /dev/cuaU0 >>>> write: Device not configured >>>> (I can't transmit but I can receive the output if I reboot the remote >>>> alix board) >>> >>> >>> Add the user to the dialer group. =C2=A0If that doesn't do it, make sur= e the >>> user has write permission to the USB device and /dev/cuaU0. >> >> >> Managed to locate my PL2303 cable, and it works on 9-stable amd64 built >> yesterday: >> >> =C2=A0% cu -l /dev/cuaU0 -s 19200 >> =C2=A0can't open log file /var/log/aculog. >> =C2=A0Connected >> =C2=A0AT >> =C2=A0OK >> =C2=A0~ >> =C2=A0[EOT] >> >> I typed the "AT". =C2=A0If the USB cable is disconnected and reconnected= while cu >> still has it open, typing a character produces >> >> =C2=A0write: Device not configured >> >> because the device disappeared when the USB cable was unplugged. =C2=A0T= he send >> and receive LEDs on this modem also both go on, meaning some data is bei= ng >> continuously sent and echoed. >> >> /etc/devfs.rules (just the USB ones) >> >> =C2=A0[localrules=3D10] >> =C2=A0add path 'ugen*' mode 0660 group operator >> =C2=A0add path 'usb/*' mode 0660 group operator >> >> The user is a member of both dialer and operator groups. >> >> If it still does not work for you, check loader.conf and rc.conf for >> nonstandard settings. From owner-freebsd-usb@FreeBSD.ORG Fri Mar 23 05:14:16 2012 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 413551065673 for ; Fri, 23 Mar 2012 05:14:16 +0000 (UTC) (envelope-from day1234@hotmail.com) Received: from col0-omc1-s1.col0.hotmail.com (col0-omc1-s1.col0.hotmail.com [65.55.34.11]) by mx1.freebsd.org (Postfix) with ESMTP id 1FA1A8FC14 for ; Fri, 23 Mar 2012 05:14:15 +0000 (UTC) Received: from COL112-W35 ([65.55.34.9]) by col0-omc1-s1.col0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Thu, 22 Mar 2012 22:14:09 -0700 Message-ID: X-Originating-IP: [70.56.215.44] From: "J.J. Day" To: Date: Fri, 23 Mar 2012 05:14:08 +0000 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 23 Mar 2012 05:14:09.0041 (UTC) FILETIME=[C6C26810:01CD08B3] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: USB Flash drive problem with 9.0 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2012 05:14:16 -0000 I am upgrading a FreeBSD server and have encountered a problem with=20 mounting a USB flash drive. The system was on 6.3 and I upgraded to 9.0=20 using CVS repositories. The flash drive worked properly at all steps=20 throughout the upgrade. However=2C after the OS upgrade was complete=2C I=20 made a mistake and destroyed some of the server application. So=2C I set the=20 upgraded drive aside=2C copied the original source drive to a different spa= re=2C and=20 repeated the upgrade process taking care to verify the functioning of=20 the applications during the process. When I finished the second time=2C eve= rything worked properly except for mounting the flash drive. it appears that something changed with the OS code that reads the drive fir= mware between the first time I ran cvsup on (about) the 9th and the second = time I ran it about the 18th. This is the output from the first upgrade (3/11/2012) when the drive is ins= erted: =09 ugen4.2: at usbus4 umass0: on usbus4 umass0: SCSI over Bulk-Only=3B quirks =3D 0x0100 umass0:2:0:-1: Attached to scbus2 da0 at umass-sim0 bus 0 scbus2 target 0 lun 0 da0: Removable Direct Access SCSI-4 device=20 da0: 40.000MB/s transfers da0: 30960MB (63406080 512 byte sectors: 255H 63S/T 3946C) And diskinfo output: =09 da0 512 # sectorsize 32463912960 # mediasize in bytes (30G) 63406080 # mediasize in sectors 0 # stripesize 0 # stripeoffset 3946 # Cylinders according to firmware. 255 # Heads according to firmware. 63 # Sectors according to firmware. AA22064F00000035 # Disk ident. This is the output from the second upgrade (3/18/2012) when the drive is in= serted: =09 ugen4.2: at usbus4 umass0: on usbus4 umass0: SCSI over Bulk-Only=3B quirks =3D 0x0100 umass0:2:0:-1: Attached to scbus2 da0 at umass-sim0 bus 0 scbus2 target 0 lun 0 da0: Removable Direct Access SCSI-4 device=20 da0: 40.000MB/s transfers da0: 17454747090944MB (71776119061217281 512 byte sectors: 64H 32S/T 0C) And diskinfo shows: =09 da0 512 # sectorsize -144115188075855360 # mediasize in bytes () -281474976710655 # mediasize in sectors 0 # stripesize 0 # stripeoffset -137438953471 # Cylinders according to firmware. 64 # Heads according to firmware. 32 # Sectors according to firmware. AA22064F00000035 # Disk ident. Since the size information is incorrect=2C the /dev/da0s1 device is not cre= ated and the drive cannot be mounted. The problem only happens with a large= drive. When I use a 4GB or 8GB drive=2C everything works correctly. If there is any information that I can submit that can assist in solving th= e problem please let me know. Thanks=2C JJ = From owner-freebsd-usb@FreeBSD.ORG Fri Mar 23 07:45:08 2012 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 671FD106566B; Fri, 23 Mar 2012 07:45:08 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe06.c2i.net [212.247.154.162]) by mx1.freebsd.org (Postfix) with ESMTP id 487C48FC0A; Fri, 23 Mar 2012 07:45:06 +0000 (UTC) X-T2-Spam-Status: No, hits=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 Received: from [176.74.212.201] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe06.swip.net (CommuniGate Pro SMTP 5.4.2) with ESMTPA id 253157326; Fri, 23 Mar 2012 08:27:03 +0100 From: Hans Petter Selasky To: freebsd-usb@freebsd.org Date: Fri, 23 Mar 2012 08:25:32 +0100 User-Agent: KMail/1.13.5 (FreeBSD/8.3-PRERELEASE; KDE/4.4.5; amd64; ; ) References: In-Reply-To: X-Face: 'mmZ:T{)),Oru^0c+/}w'`gU1$ubmG?lp!=R4Wy\ELYo2)@'UZ24N@d2+AyewRX}mAm; Yp |U[@, _z/([?1bCfM{_"B<.J>mICJCHAzzGHI{y7{%JVz%R~yJHIji`y>Y}k1C4TfysrsUI -%GU9V5]iUZF&nRn9mJ'?&>O MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201203230825.32954.hselasky@c2i.net> Cc: Alexander Motin , freebsd-current@freebsd.org, "J.J. Day" Subject: Re: USB Flash drive problem with 9.0 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2012 07:45:08 -0000 On Friday 23 March 2012 06:14:08 J.J. Day wrote: > I am upgrading a FreeBSD server and have encountered a problem with > mounting a USB flash drive. The system was on 6.3 and I upgraded to 9.0 > using CVS repositories. The flash drive worked properly at all steps > throughout the upgrade. However, after the OS upgrade was complete, I > made a mistake and destroyed some of the server application. > > So, I set the > upgraded drive aside, copied the original source drive to a different > spare, and repeated the upgrade process taking care to verify the > functioning of the applications during the process. When I finished the > second time, everything worked properly except for mounting the flash > drive. > > it appears that something changed with the OS code that reads the drive > firmware between the first time I ran cvsup on (about) the 9th and the > second time I ran it about the 18th. > > > > This is the output from the first upgrade (3/11/2012) when the drive is > inserted: > > > > ugen4.2: at usbus4 > umass0: on usbus4 > umass0: SCSI over Bulk-Only; quirks = 0x0100 > umass0:2:0:-1: Attached to scbus2 > da0 at umass-sim0 bus 0 scbus2 target 0 lun 0 > da0: Removable Direct Access SCSI-4 device > da0: 40.000MB/s transfers > da0: 30960MB (63406080 512 byte sectors: 255H 63S/T 3946C) > And diskinfo output: > > > > da0 > 512 # sectorsize > 32463912960 # mediasize in bytes (30G) > 63406080 # mediasize in sectors > 0 # stripesize > 0 # stripeoffset > 3946 # Cylinders according to firmware. > 255 # Heads according to firmware. > 63 # Sectors according to firmware. > AA22064F00000035 # Disk ident. > This is the output from the second upgrade (3/18/2012) when the drive is > inserted: > > > > ugen4.2: at usbus4 > umass0: on usbus4 > umass0: SCSI over Bulk-Only; quirks = 0x0100 > umass0:2:0:-1: Attached to scbus2 > da0 at umass-sim0 bus 0 scbus2 target 0 lun 0 > da0: Removable Direct Access SCSI-4 device > da0: 40.000MB/s transfers > da0: 17454747090944MB (71776119061217281 512 byte sectors: 64H 32S/T 0C) > And diskinfo shows: > Hi, > > da0 > 512 # sectorsize > -144115188075855360 # mediasize in bytes () > -281474976710655 # mediasize in sectors > 0 # stripesize > 0 # stripeoffset > -137438953471 # Cylinders according to firmware. > 64 # Heads according to firmware. > 32 # Sectors according to firmware. > AA22064F00000035 # Disk ident. > Since the size information is incorrect, the /dev/da0s1 device is not > created and the drive cannot be mounted. The problem only happens with a > large drive. When I use a 4GB or 8GB drive, everything works correctly. > > If there is any information that I can submit that can assist in solving > the problem please let me know. > This does not look like a USB problem. It is the SCSI/CAM layer which queries over SCSI USB how big the disk is. BTW: dec2hex(17454747090944) ans = FE000000000 So it looks like some additional bits have sneaked in there? dec2hex(32463912960) ans = 78F000000 0xFE000000000 / 0x78F000000 ans = 537.67 So it looks like the mediasize was multiplied by 512 when it shouldn't. --HPS From owner-freebsd-usb@FreeBSD.ORG Fri Mar 23 21:27:45 2012 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A5D42106566B for ; Fri, 23 Mar 2012 21:27:45 +0000 (UTC) (envelope-from day1234@hotmail.com) Received: from col0-omc1-s8.col0.hotmail.com (col0-omc1-s8.col0.hotmail.com [65.55.34.18]) by mx1.freebsd.org (Postfix) with ESMTP id 8394F8FC14 for ; Fri, 23 Mar 2012 21:27:45 +0000 (UTC) Received: from COL112-W31 ([65.55.34.8]) by col0-omc1-s8.col0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 23 Mar 2012 14:26:39 -0700 Message-ID: X-Originating-IP: [70.56.215.44] From: "J.J. Day" To: Date: Fri, 23 Mar 2012 21:26:39 +0000 Importance: Normal MIME-Version: 1.0 X-OriginalArrivalTime: 23 Mar 2012 21:26:39.0884 (UTC) FILETIME=[A29274C0:01CD093B] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: USB Flash drive problem with 9.0 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2012 21:27:45 -0000 >> I am upgrading a FreeBSD server and have encountered a problem with >> mounting a USB flash drive. The system was on 6.3 and I upgraded to 9.0 >> using CVS repositories. The flash drive worked properly at all steps >> throughout the upgrade. However=2C after the OS upgrade was complete=2C = I >> made a mistake and destroyed some of the server application. >>=20 >> So=2C I set the >> upgraded drive aside=2C copied the original source drive to a different >> spare=2C and repeated the upgrade process taking care to verify the >> functioning of the applications during the process. When I finished the >> second time=2C everything worked properly except for mounting the flash >> drive. >>=20 >> it appears that something changed with the OS code that reads the drive >> firmware between the first time I ran cvsup on (about) the 9th and the >> second time I ran it about the 18th. >>=20 >>=20 >>=20 >> This is the output from the first upgrade (3/11/2012) when the drive is >> inserted: >>=20 >>=20 >>=20 >> ugen4.2: at usbus4 >> umass0: on usbus4 >> umass0: SCSI over Bulk-Only=3B quirks =3D 0x0100 >> umass0:2:0:-1: Attached to scbus2 >> da0 at umass-sim0 bus 0 scbus2 target 0 lun 0 >> da0: Removable Direct Access SCSI-4 device >> da0: 40.000MB/s transfers >> da0: 30960MB (63406080 512 byte sectors: 255H 63S/T 3946C) >> And diskinfo output: >>=20 >>=20 >>=20 >> da0 >> 512 # sectorsize >> 32463912960 # mediasize in bytes (30G) >> 63406080 # mediasize in sectors >> 0 # stripesize >> 0 # stripeoffset >> 3946 # Cylinders according to firmware. >> 255 # Heads according to firmware. >> 63 # Sectors according to firmware. >> AA22064F00000035 # Disk ident. >> This is the output from the second upgrade (3/18/2012) when the drive is >> inserted: >>=20 >>=20 >>=20 >> ugen4.2: at usbus4 >> umass0: on usbus4 >> umass0: SCSI over Bulk-Only=3B quirks =3D 0x0100 >> umass0:2:0:-1: Attached to scbus2 >> da0 at umass-sim0 bus 0 scbus2 target 0 lun 0 >> da0: Removable Direct Access SCSI-4 device >> da0: 40.000MB/s transfers >> da0: 17454747090944MB (71776119061217281 512 byte sectors: 64H 32S/T 0C) >> And diskinfo shows: >> > >Hi=2C > >>=20 >> da0 >> 512 # sectorsize >> -144115188075855360 # mediasize in bytes () >> -281474976710655 # mediasize in sectors >> 0 # stripesize >> 0 # stripeoffset >> -137438953471 # Cylinders according to firmware. >> 64 # Heads according to firmware. >> 32 # Sectors according to firmware. >> AA22064F00000035 # Disk ident. >> Since the size information is incorrect=2C the /dev/da0s1 device is not >> created and the drive cannot be mounted. The problem only happens with a >> large drive. When I use a 4GB or 8GB drive=2C everything works correctly= . >>=20 >> If there is any information that I can submit that can assist in solving >> the problem please let me know. >>=20 > >This does not look like a USB problem. It is the SCSI/CAM layer which quer= ies=20 >over SCSI USB how big the disk is. > >BTW: > >dec2hex(17454747090944) >ans =3D FE000000000 > >So it looks like some additional bits have sneaked in there? > >dec2hex(32463912960) >ans =3D 78F000000 > > 0xFE000000000 / 0x78F000000 >ans =3D 537.67 > >So it looks like the mediasize was multiplied by 512 when it shouldn't. > >--HPS So the problem could be that the header is shifted two bytes? I don't know where to look=2C but is there any way I can see what the heade= r is that=20 is presented from the drive or how the system processes it? JJ = From owner-freebsd-usb@FreeBSD.ORG Sat Mar 24 02:36:28 2012 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C9D2A106564A; Sat, 24 Mar 2012 02:36:28 +0000 (UTC) (envelope-from kaho@ed.niigata-u.ac.jp) Received: from caav01.cais.niigata-u.ac.jp (caav01.cais.niigata-u.ac.jp [133.35.17.133]) by mx1.freebsd.org (Postfix) with ESMTP id 64D148FC0A; Sat, 24 Mar 2012 02:36:28 +0000 (UTC) Received: from caav01.cais.niigata-u.ac.jp (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id F40A4A2638; Sat, 24 Mar 2012 11:18:02 +0900 (JST) Received: from pf2.ed.niigata-u.ac.jp (pf2.ed.niigata-u.ac.jp [133.35.172.22]) by caav01.cais.niigata-u.ac.jp (Postfix) with ESMTPS id D0020A261A; Sat, 24 Mar 2012 11:18:02 +0900 (JST) Received: from pf2.ed.niigata-u.ac.jp (localhost [127.0.0.1]) by pf2.ed.niigata-u.ac.jp (8.14.5/8.14.5) with ESMTP id q2O2HnWk017629; Sat, 24 Mar 2012 11:18:02 +0900 (JST) (envelope-from kaho@pf2.ed.niigata-u.ac.jp) To: freebsd-current@freebsd.org From: Kaho Toshikazu X-Mailer: MH-E 8.2; MH 6.8.4.JP-3.05; GNU Emacs 23.4.1 References: <201203230825.32954.hselasky@c2i.net> User-Agent: EMH/1.14.1 SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?ISO-2022-JP-2?B?R29qGyQoRCtXGyhC?=) APEL/10.8 Emacs/23.4 (amd64-portbld-freebsd10.0) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Date: Sat, 24 Mar 2012 11:17:49 +0900 Message-ID: <17628.1332555469@pf2.ed.niigata-u.ac.jp> Sender: kaho@ed.niigata-u.ac.jp Cc: , freebsd-usb@freebsd.org Subject: Re: USB Flash drive problem with 9.0 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Mar 2012 02:36:28 -0000 Hello, I have a similar problem with Transcend 16GB USB flash. When the flash is plugged, FreeBSD attache it, but reports very big capacity and can not read/write it. UQ_MSC_NO_INQUIRY makes jobs in my machines. 10-current and 8-stable have same problem, and 9-stable is not tested. -- Kaho Toshikazu -- To: freebsd-usb@freebsd.org Subject: Re: USB Flash drive problem with 9.0 From: Hans Petter Selasky Date: Fri, 23 Mar 2012 08:25:32 +0100 Cc: Alexander Motin , freebsd-current@freebsd.org, "J.J. Day" On Friday 23 March 2012 06:14:08 J.J. Day wrote: > I am upgrading a FreeBSD server and have encountered a problem with > mounting a USB flash drive. The system was on 6.3 and I upgraded to 9.0 > using CVS repositories. The flash drive worked properly at all steps > throughout the upgrade. However, after the OS upgrade was complete, I > made a mistake and destroyed some of the server application. > > So, I set the > upgraded drive aside, copied the original source drive to a different > spare, and repeated the upgrade process taking care to verify the > functioning of the applications during the process. When I finished the > second time, everything worked properly except for mounting the flash > drive. > > it appears that something changed with the OS code that reads the drive > firmware between the first time I ran cvsup on (about) the 9th and the > second time I ran it about the 18th. > > > > This is the output from the first upgrade (3/11/2012) when the drive is > inserted: > > > > ugen4.2: at usbus4 > umass0: on usbus4 > umass0: SCSI over Bulk-Only; quirks = 0x0100 > umass0:2:0:-1: Attached to scbus2 > da0 at umass-sim0 bus 0 scbus2 target 0 lun 0 > da0: Removable Direct Access SCSI-4 device > da0: 40.000MB/s transfers > da0: 30960MB (63406080 512 byte sectors: 255H 63S/T 3946C) > And diskinfo output: > > > > da0 > 512 # sectorsize > 32463912960 # mediasize in bytes (30G) > 63406080 # mediasize in sectors > 0 # stripesize > 0 # stripeoffset > 3946 # Cylinders according to firmware. > 255 # Heads according to firmware. > 63 # Sectors according to firmware. > AA22064F00000035 # Disk ident. > This is the output from the second upgrade (3/18/2012) when the drive is > inserted: > > > > ugen4.2: at usbus4 > umass0: on usbus4 > umass0: SCSI over Bulk-Only; quirks = 0x0100 > umass0:2:0:-1: Attached to scbus2 > da0 at umass-sim0 bus 0 scbus2 target 0 lun 0 > da0: Removable Direct Access SCSI-4 device > da0: 40.000MB/s transfers > da0: 17454747090944MB (71776119061217281 512 byte sectors: 64H 32S/T 0C) > And diskinfo shows: > Hi, > > da0 > 512 # sectorsize > -144115188075855360 # mediasize in bytes () > -281474976710655 # mediasize in sectors > 0 # stripesize > 0 # stripeoffset > -137438953471 # Cylinders according to firmware. > 64 # Heads according to firmware. > 32 # Sectors according to firmware. > AA22064F00000035 # Disk ident. > Since the size information is incorrect, the /dev/da0s1 device is not > created and the drive cannot be mounted. The problem only happens with a > large drive. When I use a 4GB or 8GB drive, everything works correctly. > > If there is any information that I can submit that can assist in solving > the problem please let me know. > This does not look like a USB problem. It is the SCSI/CAM layer which queries over SCSI USB how big the disk is. BTW: dec2hex(17454747090944) ans = FE000000000 So it looks like some additional bits have sneaked in there? dec2hex(32463912960) ans = 78F000000 0xFE000000000 / 0x78F000000 ans = 537.67 So it looks like the mediasize was multiplied by 512 when it shouldn't. --HPS From owner-freebsd-usb@FreeBSD.ORG Sat Mar 24 04:54:53 2012 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 56A17106566C for ; Sat, 24 Mar 2012 04:54:53 +0000 (UTC) (envelope-from day1234@hotmail.com) Received: from col0-omc1-s15.col0.hotmail.com (col0-omc1-s15.col0.hotmail.com [65.55.34.25]) by mx1.freebsd.org (Postfix) with ESMTP id 2C1248FC14 for ; Sat, 24 Mar 2012 04:54:52 +0000 (UTC) Received: from COL112-W46 ([65.55.34.9]) by col0-omc1-s15.col0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Fri, 23 Mar 2012 21:53:46 -0700 Message-ID: X-Originating-IP: [70.56.215.44] From: "J.J. Day" To: Date: Sat, 24 Mar 2012 04:53:46 +0000 Importance: Normal In-Reply-To: <201203230825.32954.hselasky@c2i.net> References: , <201203230825.32954.hselasky@c2i.net> MIME-Version: 1.0 X-OriginalArrivalTime: 24 Mar 2012 04:53:46.0937 (UTC) FILETIME=[18BDE290:01CD097A] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: RE: USB Flash drive problem with 9.0 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Mar 2012 04:54:53 -0000 > From: hselasky@c2i.net > To: freebsd-usb@freebsd.org > Subject: Re: USB Flash drive problem with 9.0 > Date: Fri=2C 23 Mar 2012 08:25:32 +0100 > CC: day1234@hotmail.com=3B freebsd-current@freebsd.org=3B mav@freebsd.org >=20 > On Friday 23 March 2012 06:14:08 J.J. Day wrote: > > I am upgrading a FreeBSD server and have encountered a problem with > > mounting a USB flash drive. The system was on 6.3 and I upgraded to 9.0 > > using CVS repositories. The flash drive worked properly at all steps > > throughout the upgrade. However=2C after the OS upgrade was complete=2C= I > > made a mistake and destroyed some of the server application. > >=20 > > So=2C I set the > > upgraded drive aside=2C copied the original source drive to a different > > spare=2C and repeated the upgrade process taking care to verify the > > functioning of the applications during the process. When I finished the > > second time=2C everything worked properly except for mounting the flash > > drive. > >=20 > > it appears that something changed with the OS code that reads the drive > > firmware between the first time I ran cvsup on (about) the 9th and the > > second time I ran it about the 18th. > >=20 > >=20 > >=20 > > This is the output from the first upgrade (3/11/2012) when the drive is > > inserted: > >=20 > >=20 > >=20 > > ugen4.2: at usbus4 > > umass0: on usbus4 > > umass0: SCSI over Bulk-Only=3B quirks =3D 0x0100 > > umass0:2:0:-1: Attached to scbus2 > > da0 at umass-sim0 bus 0 scbus2 target 0 lun 0 > > da0: Removable Direct Access SCSI-4 device > > da0: 40.000MB/s transfers > > da0: 30960MB (63406080 512 byte sectors: 255H 63S/T 3946C) > > And diskinfo output: > >=20 > >=20 > >=20 > > da0 > > 512 # sectorsize > > 32463912960 # mediasize in bytes (30G) > > 63406080 # mediasize in sectors > > 0 # stripesize > > 0 # stripeoffset > > 3946 # Cylinders according to firmware. > > 255 # Heads according to firmware. > > 63 # Sectors according to firmware. > > AA22064F00000035 # Disk ident. > > This is the output from the second upgrade (3/18/2012) when the drive i= s > > inserted: > >=20 > >=20 > >=20 > > ugen4.2: at usbus4 > > umass0: on usbus4 > > umass0: SCSI over Bulk-Only=3B quirks =3D 0x0100 > > umass0:2:0:-1: Attached to scbus2 > > da0 at umass-sim0 bus 0 scbus2 target 0 lun 0 > > da0: Removable Direct Access SCSI-4 device > > da0: 40.000MB/s transfers > > da0: 17454747090944MB (71776119061217281 512 byte sectors: 64H 32S/T 0C= ) > > And diskinfo shows: > >=20 >=20 > Hi=2C >=20 > >=20 > > da0 > > 512 # sectorsize > > -144115188075855360 # mediasize in bytes () > > -281474976710655 # mediasize in sectors > > 0 # stripesize > > 0 # stripeoffset > > -137438953471 # Cylinders according to firmware. > > 64 # Heads according to firmware. > > 32 # Sectors according to firmware. > > AA22064F00000035 # Disk ident. > > Since the size information is incorrect=2C the /dev/da0s1 device is not > > created and the drive cannot be mounted. The problem only happens with = a > > large drive. When I use a 4GB or 8GB drive=2C everything works correctl= y. > >=20 > > If there is any information that I can submit that can assist in solvin= g > > the problem please let me know. > >=20 >=20 > This does not look like a USB problem. It is the SCSI/CAM layer which que= ries=20 > over SCSI USB how big the disk is. >=20 > BTW: >=20 > dec2hex(17454747090944) > ans =3D FE000000000 >=20 > So it looks like some additional bits have sneaked in there? >=20 > dec2hex(32463912960) > ans =3D 78F000000 >=20 > 0xFE000000000 / 0x78F000000 > ans =3D 537.67 >=20 > So it looks like the mediasize was multiplied by 512 when it shouldn't. >=20 > --HPS Kaho Toshikazu found a solution (a work-around) for the problem. Since the drive mounted as: "ugen4.2: at usbus4" The commands: # usbconfig -d 4.2 add_quirk UQ_MSC_NO_INQUIRY # usbconfig -d 4.2 reset resets the attach and appears to bypass some of the SCSI/CAM process. The /dev/da0s1 device is created and the drive functions normally although the drive ident information is no longer available. JJ = From owner-freebsd-usb@FreeBSD.ORG Sat Mar 24 09:40:13 2012 Return-Path: Delivered-To: freebsd-usb@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E33B0106566B; Sat, 24 Mar 2012 09:40:13 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id DD53A8FC15; Sat, 24 Mar 2012 09:40:12 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id LAA01825; Sat, 24 Mar 2012 11:40:04 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1SBNS8-000DQJ-Fv; Sat, 24 Mar 2012 11:40:04 +0200 Message-ID: <4F6D9672.4050201@FreeBSD.org> Date: Sat, 24 Mar 2012 11:40:02 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:10.0.2) Gecko/20120218 Thunderbird/10.0.2 MIME-Version: 1.0 To: Kaho Toshikazu , Alexander Motin References: <201203230825.32954.hselasky@c2i.net> <17628.1332555469@pf2.ed.niigata-u.ac.jp> In-Reply-To: <17628.1332555469@pf2.ed.niigata-u.ac.jp> X-Enigmail-Version: 1.4 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org, freebsd-usb@FreeBSD.org Subject: Re: USB Flash drive problem with 9.0 X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Mar 2012 09:40:14 -0000 on 24/03/2012 04:17 Kaho Toshikazu said the following: > Hello, > > I have a similar problem with Transcend 16GB USB flash. When the flash > is plugged, FreeBSD attache it, but reports very big capacity and can > not read/write it. UQ_MSC_NO_INQUIRY makes jobs in my machines. > 10-current and 8-stable have same problem, and 9-stable is not tested. Could the problem be related to r229288 (r232943 in stable/9)? The dates below match the MFC date 2012-03-13. > To: freebsd-usb@freebsd.org > Subject: Re: USB Flash drive problem with 9.0 > From: Hans Petter Selasky > Date: Fri, 23 Mar 2012 08:25:32 +0100 > Cc: Alexander Motin , freebsd-current@freebsd.org, "J.J. Day" > > On Friday 23 March 2012 06:14:08 J.J. Day wrote: >> I am upgrading a FreeBSD server and have encountered a problem with >> mounting a USB flash drive. The system was on 6.3 and I upgraded to 9.0 >> using CVS repositories. The flash drive worked properly at all steps >> throughout the upgrade. However, after the OS upgrade was complete, I >> made a mistake and destroyed some of the server application. >> >> So, I set the >> upgraded drive aside, copied the original source drive to a different >> spare, and repeated the upgrade process taking care to verify the >> functioning of the applications during the process. When I finished the >> second time, everything worked properly except for mounting the flash >> drive. >> >> it appears that something changed with the OS code that reads the drive >> firmware between the first time I ran cvsup on (about) the 9th and the >> second time I ran it about the 18th. >> >> >> >> This is the output from the first upgrade (3/11/2012) when the drive is >> inserted: >> >> >> >> ugen4.2: at usbus4 >> umass0: on usbus4 >> umass0: SCSI over Bulk-Only; quirks = 0x0100 >> umass0:2:0:-1: Attached to scbus2 >> da0 at umass-sim0 bus 0 scbus2 target 0 lun 0 >> da0: Removable Direct Access SCSI-4 device >> da0: 40.000MB/s transfers >> da0: 30960MB (63406080 512 byte sectors: 255H 63S/T 3946C) >> And diskinfo output: >> >> >> >> da0 >> 512 # sectorsize >> 32463912960 # mediasize in bytes (30G) >> 63406080 # mediasize in sectors >> 0 # stripesize >> 0 # stripeoffset >> 3946 # Cylinders according to firmware. >> 255 # Heads according to firmware. >> 63 # Sectors according to firmware. >> AA22064F00000035 # Disk ident. >> This is the output from the second upgrade (3/18/2012) when the drive is >> inserted: >> >> >> >> ugen4.2: at usbus4 >> umass0: on usbus4 >> umass0: SCSI over Bulk-Only; quirks = 0x0100 >> umass0:2:0:-1: Attached to scbus2 >> da0 at umass-sim0 bus 0 scbus2 target 0 lun 0 >> da0: Removable Direct Access SCSI-4 device >> da0: 40.000MB/s transfers >> da0: 17454747090944MB (71776119061217281 512 byte sectors: 64H 32S/T 0C) >> And diskinfo shows: >> > > Hi, > >> >> da0 >> 512 # sectorsize >> -144115188075855360 # mediasize in bytes () >> -281474976710655 # mediasize in sectors >> 0 # stripesize >> 0 # stripeoffset >> -137438953471 # Cylinders according to firmware. >> 64 # Heads according to firmware. >> 32 # Sectors according to firmware. >> AA22064F00000035 # Disk ident. >> Since the size information is incorrect, the /dev/da0s1 device is not >> created and the drive cannot be mounted. The problem only happens with a >> large drive. When I use a 4GB or 8GB drive, everything works correctly. >> >> If there is any information that I can submit that can assist in solving >> the problem please let me know. >> > > This does not look like a USB problem. It is the SCSI/CAM layer which queries > over SCSI USB how big the disk is. > > BTW: > > dec2hex(17454747090944) > ans = FE000000000 > > So it looks like some additional bits have sneaked in there? > > dec2hex(32463912960) > ans = 78F000000 > > 0xFE000000000 / 0x78F000000 > ans = 537.67 > > So it looks like the mediasize was multiplied by 512 when it shouldn't. > > --HPS -- Andriy Gapon From owner-freebsd-usb@FreeBSD.ORG Sat Mar 24 17:15:50 2012 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 664FE106566C for ; Sat, 24 Mar 2012 17:15:50 +0000 (UTC) (envelope-from denverh@comcast.net) Received: from qmta10.westchester.pa.mail.comcast.net (qmta10.westchester.pa.mail.comcast.net [76.96.62.17]) by mx1.freebsd.org (Postfix) with ESMTP id 13AC98FC0C for ; Sat, 24 Mar 2012 17:15:49 +0000 (UTC) Received: from omta13.westchester.pa.mail.comcast.net ([76.96.62.52]) by qmta10.westchester.pa.mail.comcast.net with comcast id pVEg1i00A17dt5G5AVEjNh; Sat, 24 Mar 2012 17:14:43 +0000 Received: from [192.168.0.30] ([66.41.84.80]) by omta13.westchester.pa.mail.comcast.net with comcast id pVEi1i00g1jzK7m3ZVEiSL; Sat, 24 Mar 2012 17:14:43 +0000 Message-ID: <4F6E0101.8020806@comcast.net> Date: Sat, 24 Mar 2012 12:14:41 -0500 From: Denver Hull User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.19) Gecko/20110521 SeaMonkey/2.0.14 MIME-Version: 1.0 To: freebsd-usb@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: wacom and x11 and webcamd X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Mar 2012 17:15:50 -0000 Hello, I discovered this when I saw an update to input-wacom at freshports.org. I've installed cuse4bsd, the new input-wacom, and the latest webcamd: cuse4bsd-kmod-0.1.23 input-wacom-40.0.11.1 webcamd-3.2.0.2 I believe I've followed all the instructions properly, and when I start webcamd, everything seems to be correct: Attached ugen1.2[0] to cuse unit 0 Creating /dev/input/event0 According to dmesg, ugen1.2 is the correct device (I have a Bamboo Pen): ugen1.2: at usbus1 The /dev/input/event0 node is indeed created. However, when I start X, I get the following: (EE) stylus: Wacom X driver can't grab event device (Bad address) (EE) eraser: Wacom X driver can't grab event device (Bad address) (EE) cursor: Wacom X driver can't grab event device (Bad address) (EE) pad: Wacom X driver can't grab event device (Bad address) (EE) touch: Wacom X driver can't grab event device (Bad address) Protocol not supported by server The last line repeats indefinitely, and X never finishes starting up. The system I'm trying this on is 8.3-PRERELEASE. I had tried this quickly a while ago on 8.2-STABLE with similar results. Does anyone have any ideas about what might be wrong? Regards, Denver