On Sat, 17 Mar 2012 07:55:16 -0700 Alan <[email protected]> wrote: > Now that I have it all compiled in and listed in my dmesg, I'm still > needing some additional deep assistance on this one. With the serial > cable from my lfs machine to a windows machine, I get NOTHING over > that /dev/ttyUSB0 serial port.
OK, after plugging one of these devices in on my system, dmesg says: usb 3-2: new full-speed USB device number 2 using ohci_hcd usb 3-2: New USB device found, idVendor=067b, idProduct=2303 usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 3-2: Product: USB-Serial Controller usb 3-2: Manufacturer: Prolific Technology Inc. pl2303 3-2:1.0: pl2303 converter detected usb 3-2: pl2303 converter now attached to ttyUSB0 Now, chatting over a link to another machine has more pitfalls than, say, chatting with an external modem because of all the extra configuration/software on the other side as well as the null modem cable issue. If you have an old external modem, these are helpful for test chats. If you want to connect to another machine, remember that you will need to use a "null modem" RS232 adapter (or cable) that reverses the RS232 receive and transmit lines so that two computers "hosts" can communicate: http://www.ebay.com/itm/150709914927 Note that using a F/F version should allow two PL2303 devices to connect directly to each other. Minicom has its own little hangups. First of all, run it as root first to avoid any potential device permission issues. I'm running a old version (2.2, 2.6.1 is current). When I try to do this: minicom -p /dev/ttyUSB0 it spits out: minicom: argument to -p must be a pty It is a simple, direct, and I would think common, request - use the specified serial device, and that always seems to end up like pulling teeth with minicom. Changing the serial device in the minicom configuration menu does *not* seem to immediately alter the device in use. Putting this line: pu port /dev/ttyUSB0 in my /etc/minirc.dfl and restarting minicom without using -p option does the trick and I can then chat with an external modem connected to the PL2303 adapter: ati0 Agere OCM V.92 Ver2.7a (Jun 14 2004) Voice Mercury DP2SH mode-ii SERIAL So, assuming your dmesg info is OK, I think the USB driver is OK and the problem now lies with the cabling or the configuration on the other machine. Cheers, Mike -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
