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.