Date: Tue, 8 Jun 2010 16:16:03 +0530 (IST) From: akash kumar <akashb503@yahoo.co.in> To: "C. P. Ghost" <cpghost@cordula.ws> Cc: freebsd-questions@freebsd.org Subject: Re: minicom freebsd 8.0 Message-ID: <274113.20639.qm@web95109.mail.in2.yahoo.com> In-Reply-To: <AANLkTilcvdWwsG4XAmE_iHULrK62-m-a3EHvA71BEEI3@mail.gmail.com> References: <629087.29185.qm@web95103.mail.in2.yahoo.com> <4C06171E.2070608@a1poweruser.com> <382060.97070.qm@web95103.mail.in2.yahoo.com> <AANLkTilcvdWwsG4XAmE_iHULrK62-m-a3EHvA71BEEI3@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi,=0A=0AFinally worked for me. Thanks all for your help.=0ABelow are the s= teps.=0A=0A1. /var/log/messages has below message when ever usb port is ins= erted. =0A> Unknown USB device: vendor 0x4348 product* 0x5523* bus uhub2 = =0A=0A2. grepping for vendor no. =0A> grep 0x4348 /usr/src/sys/dev/usb/* = =0A/usr/src/sys/dev/usb/usbdevs:vendor WCH 0x4348 QinHeng Electro= nics =0A=0A> cat /usr/src/sys/dev/usb/usbdevs | grep WCH =0Avendor WCH = 0x4348 QinHeng Electronics =0A/* WCH products */ =0Aproduct WCH CH341= SER *0x5523 * CH341/CH340 USB-Serial Bridge =0Aproduct WCH2 CH341S= ER 0x7523 CH341/CH340 USB-Serial Bridge =0A=0A=0A3. After bit of = googling with 'CH341/CH340 USB-Serial Bridge', found that specific module i= s missing.=0A Added uchcom in to the config file and rebuilt the kernel an= d booted =0Awith it. =0A> kldstat -v | grep uchcom =0A 309 uhub/uchco= m =0A=0A4. After rebooting could see below messages i.e device being recogn= ized =0Aas the module is already present =0Augen2.3: <vendor 0x4348> at usb= us2 =0Aucom0: <vendor 0x4348 USB-SER!, rev 1.10/2.50, addr 3> on usbus2 =0A= ucom0: CH340 detected =0A=0AThe device is created with name /dev/cuaU0 and= it worked finally with minicom. =0A=0A=0AThanks,=0AAkash.=0A=0A=0A=0A_____= ___________________________=0AFrom: C. P. Ghost <cpghost@cordula.ws>=0ATo: = akash kumar <akashb503@yahoo.co.in>=0ACc: freebsd-questions@freebsd.org=0AS= ent: Wed, 2 June, 2010 3:36:54 PM=0ASubject: Re: minicom freebsd 8.0=0A=0AO= n Wed, Jun 2, 2010 at 11:30 AM, akash kumar <akashb503@yahoo.co.in> wrote:= =0A> Hi,=0A>=0A> I was referring to minicom command similar to one on linux= .=0A> On linux the config file is /etc/minirc.<configfile> and the Serial = Device is /dev/ttyUSB0, which was working for me.=0A> On freebsd the conf= ig file is /usr/local/etc/minicom/minirc.<configfile>, but not sure what to= update in the field 'pu port'.=0A>=0A> I tried with /dev/ugen2.2 but got b= elow error=0A>> minicom: cannot open /dev/ugen2.2: Permission denied=0A>=0A= > Please let me know what needs to be updated in the 'pu port' field.=0A=0A= Ah, okay. ugen is a generic device. I think you can't use that directly=0Ai= f you have a usb-to-serial converter.=0A=0AI guess you need to kldload a ke= rnel module specific to your usb-to-serial=0Aconverter. For example somethi= ng like uplcom, umodem etc. This would=0Acreate a new entry in /dev that yo= u can use in minicom.=0A=0APermissions for those devices can be set in /etc= /devfs.rules (and restarting=0Adevfs with /etc/rc.d/devfs restart). You may= also want to look at /etc/devd.conf=0A=0AI'm not familiar with usb-to-seri= al converters, so I can't help more than that.=0AOthers may have more exper= ience there.=0A=0A> Thanks,=0A> Akash.=0A=0A-cpghost.=0A=0A-- =0ACordula's = Web. http://www.cordula.ws/=0A=0A=0A
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?274113.20639.qm>