Re: minicom freebsd 8.0
Hi, Finally worked for me. Thanks all for your help. Below are the steps. 1. /var/log/messages has below message when ever usb port is inserted. Unknown USB device: vendor 0x4348 product* 0x5523* bus uhub2 2. grepping for vendor no. grep 0x4348 /usr/src/sys/dev/usb/* /usr/src/sys/dev/usb/usbdevs:vendor WCH0x4348QinHeng Electronics cat /usr/src/sys/dev/usb/usbdevs | grep WCH vendor WCH0x4348QinHeng Electronics /* WCH products */ product WCH CH341SER*0x5523 * CH341/CH340 USB-Serial Bridge product WCH2 CH341SER0x7523CH341/CH340 USB-Serial Bridge 3. After bit of googling with 'CH341/CH340 USB-Serial Bridge', found that specific module is missing. Added uchcom in to the config file and rebuilt the kernel and booted with it. kldstat -v | grep uchcom 309 uhub/uchcom 4. After rebooting could see below messages i.e device being recognized as the module is already present ugen2.3: vendor 0x4348 at usbus2 ucom0: vendor 0x4348 USB-SER!, rev 1.10/2.50, addr 3 on usbus2 ucom0: CH340 detected The device is created with name /dev/cuaU0 and it worked finally with minicom. Thanks, Akash. From: C. P. Ghost cpgh...@cordula.ws To: akash kumar akashb...@yahoo.co.in Cc: freebsd-questions@freebsd.org Sent: Wed, 2 June, 2010 3:36:54 PM Subject: Re: minicom freebsd 8.0 On Wed, Jun 2, 2010 at 11:30 AM, akash kumar akashb...@yahoo.co.in wrote: Hi, I was referring to minicom command similar to one on linux. On linux the config file is /etc/minirc.configfile and the Serial Device is /dev/ttyUSB0, which was working for me. On freebsd the config file is /usr/local/etc/minicom/minirc.configfile, but not sure what to update in the field 'pu port'. I tried with /dev/ugen2.2 but got below error minicom: cannot open /dev/ugen2.2: Permission denied Please let me know what needs to be updated in the 'pu port' field. Ah, okay. ugen is a generic device. I think you can't use that directly if you have a usb-to-serial converter. I guess you need to kldload a kernel module specific to your usb-to-serial converter. For example something like uplcom, umodem etc. This would create a new entry in /dev that you can use in minicom. Permissions for those devices can be set in /etc/devfs.rules (and restarting devfs with /etc/rc.d/devfs restart). You may also want to look at /etc/devd.conf I'm not familiar with usb-to-serial converters, so I can't help more than that. Others may have more experience there. Thanks, Akash. -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
minicom freebsd 8.0
Hi, Can some one help me with the steps configuring minicom on freebsd 8.0. I have a serial to usb converter running between my board and host machine. Thanks, Akash. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: minicom freebsd 8.0
akash kumar wrote: Hi, Can some one help me with the steps configuring minicom on freebsd 8.0. I have a serial to usb converter running between my board and host machine. Thanks, Akash. I take it a minicom is a external serial modem for internet access over the phone lines. First off you better check if this is a windows modem. Phone modems are manufactured for two target markets, MS/Windows (Winmodems) and every thing else. Winmodems are cheep because the hardware controller function is handled by the software you have to install into MS/Windows. This hardware controller function is normally contained in a chip on the modem circuit board. Winmodems are missing this chip and directs the modem to use driver software running in the MS/Windows system to perform the controller function. The most common Winmodem chips are manufactured by Lucent. There are many versions of this Lucent chip resulting in each chip version needing a different MS/Windows software driver version. Up until version 4.4, FBSD did not have any solution to using Winmodems, but with the release of 4.4 the ports collection now contains the Linux Winmodem 'ltmdm' driver which was ported to FBSD. This port is very poorly documented, only works with a limited number of Lucent chip version, and can be somewhat unreliable. Your whole Internet connection is managed by your modem and trying to shoe horn a modem specially manufactured for the MS/Windows operating system into FreeBSD is not the way to achieve a satisfactory dialup Internet connection. Plug the usb to serial converter into a usb port on the pc. Plug the serial cable into the modem and the converter. Power on the minicon, and boot your pc. Check your boot messages for the address of the usb to serial converter and use that address in your ppp config for dialing your ISP. If you can't id the address you need, then post your boot message log here for next step in help. Use dmesg boot.msg.file to get a copy of the boot log. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: minicom freebsd 8.0
Hi, I was referring to minicom command similar to one on linux. On linux the config file is /etc/minirc.configfile and the Serial Device is /dev/ttyUSB0, which was working for me. On freebsd the config file is /usr/local/etc/minicom/minirc.configfile, but not sure what to update in the field 'pu port'. I tried with /dev/ugen2.2 but got below error minicom: cannot open /dev/ugen2.2: Permission denied Please let me know what needs to be updated in the 'pu port' field. Thanks, Akash. From: Fbsd1 fb...@a1poweruser.com To: akash kumar akashb...@yahoo.co.in Cc: freebsd-questions@freebsd.org Sent: Wed, 2 June, 2010 2:02:30 PM Subject: Re: minicom freebsd 8.0 akash kumar wrote: Hi, Can some one help me with the steps configuring minicom on freebsd 8.0. I have a serial to usb converter running between my board and host machine. Thanks, Akash. I take it a minicom is a external serial modem for internet access over the phone lines. First off you better check if this is a windows modem. Phone modems are manufactured for two target markets, MS/Windows (Winmodems) and every thing else. Winmodems are cheep because the hardware controller function is handled by the software you have to install into MS/Windows. This hardware controller function is normally contained in a chip on the modem circuit board. Winmodems are missing this chip and directs the modem to use driver software running in the MS/Windows system to perform the controller function. The most common Winmodem chips are manufactured by Lucent. There are many versions of this Lucent chip resulting in each chip version needing a different MS/Windows software driver version. Up until version 4.4, FBSD did not have any solution to using Winmodems, but with the release of 4.4 the ports collection now contains the Linux Winmodem 'ltmdm' driver which was ported to FBSD. This port is very poorly documented, only works with a limited number of Lucent chip version, and can be somewhat unreliable. Your whole Internet connection is managed by your modem and trying to shoe horn a modem specially manufactured for the MS/Windows operating system into FreeBSD is not the way to achieve a satisfactory dialup Internet connection. Plug the usb to serial converter into a usb port on the pc. Plug the serial cable into the modem and the converter. Power on the minicon, and boot your pc. Check your boot messages for the address of the usb to serial converter and use that address in your ppp config for dialing your ISP. If you can't id the address you need, then post your boot message log here for next step in help. Use dmesg boot.msg.file to get a copy of the boot log. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: minicom freebsd 8.0
On Wed, Jun 2, 2010 at 10:32 AM, Fbsd1 fb...@a1poweruser.com wrote: akash kumar wrote: Hi, Can some one help me with the steps configuring minicom on freebsd 8.0. I have a serial to usb converter running between my board and host machine. Thanks, Akash. I take it a minicom is a external serial modem for internet access over the phone lines. I guess akash is asking about the port comms/minicom, the special files under /dev and the kernel modules needed to access the serial port of the modem via a usb-to-serial converter. -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: minicom freebsd 8.0
On Wed, Jun 2, 2010 at 11:30 AM, akash kumar akashb...@yahoo.co.in wrote: Hi, I was referring to minicom command similar to one on linux. On linux the config file is /etc/minirc.configfile and the Serial Device is /dev/ttyUSB0, which was working for me. On freebsd the config file is /usr/local/etc/minicom/minirc.configfile, but not sure what to update in the field 'pu port'. I tried with /dev/ugen2.2 but got below error minicom: cannot open /dev/ugen2.2: Permission denied Please let me know what needs to be updated in the 'pu port' field. Ah, okay. ugen is a generic device. I think you can't use that directly if you have a usb-to-serial converter. I guess you need to kldload a kernel module specific to your usb-to-serial converter. For example something like uplcom, umodem etc. This would create a new entry in /dev that you can use in minicom. Permissions for those devices can be set in /etc/devfs.rules (and restarting devfs with /etc/rc.d/devfs restart). You may also want to look at /etc/devd.conf I'm not familiar with usb-to-serial converters, so I can't help more than that. Others may have more experience there. Thanks, Akash. -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
