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.