Oops. Too late for this, I put my foot in it. For the ttyUSBx device I had to
chgrp tty /dev/ttyUSBx (mine was dialout) chmod 777 /dev/ttyUSBx The problem with the ttyUSBx was when I was trying to get the usb adapter to work when I had a usb to serial adapter plugged in. When I unplugged the usb adapter the ttyUSBx device would disappear, when I plugged it in the ttyUSBx device re-appeared. Very confusing even now. But they are unrelated phsically, it was just my OS playing games with me. Unrelated to the serial device problem. William Brown wrote: > After struggling to get the HL-340 working I can maybe point him in the > right direction. We need to know which linux, I had to upgrade to > Ubuntu 8.10. Second I had to do a clean install to remove all the tracks > I left following different guides for versions prior to 8.10. Third I > had to ignore the ttyUSBx device. Just start owfs or server or whatever > with the -u parameter. Regarding the ttyUSBx device, I had the same > thing happen in versions prior to Ubuntu 8.10 but it doesn't connect to > the usb adapter. I have no device listed except as an usb device in > dmesg and lsusb. > > From the page at (http://www.etheus.net/CP210x_Linux_Driver), this > seems to be the major problem with usb devices, getting the vendor > id/product id into device id list. Follow their instructions copied below: > > > Troubleshooting > > First, ensure that the driver has loaded, run *dmesg* There should be a > line saying something similar to "cp210x.c: Silicon Labs > CP2101/CP2102/CP2103 RS232 serial adaptor driver..." Second, check that > the driver has bound to the device, after making a connection to the > USB, the following message should be present in dmesg, "CP210x converter > detected", and "CP210x converter now attached to..." If these stages > have not happened, ensure the driver is loaded, check the output of > lsmod. In order to detect your device, the product and vendor IDs must > be recognised. CP210x based devices have vendor programmable device IDs > and it is likely that if your device is not being detected, the device > IDs are unknown. The device IDs can be obtained by running *lsusb* and > appear as hex numbers in the format *vendor:product*. Verify that they > are present in the list towards the top of drivers/usb/serial/cp210x.c > which can be found in the kernel source directory. If modifications to > the driver's device ID list are required, the module must be recompiled, > and reinstalled. After these initial stages, further problems are rare. > However if you are still getting trouble, reload the module with the > debug option "*rmmod cp210x; modprobe cp210x debug*". Then send me the > output of *lsusb -v*, and the output of *dmesg*, when the driver is > loaded, when the device inserted, and when an attempt is made to use the > device. Also include the command line parameters/output of the program > that was having trouble communicating. My email address is at the end of > this page. > > > > > Paul Alfille wrote: > >> Dr. Simon Malhuish of OWW pointed out this new bus master >> (http://www.aag.com.mx/aagusa/index1.html part of their new WSI603 >> weather station http://www.aag.com.mx/aagusa/index1.html). He has >> found it difficult to get it to function under linux and asks if we >> have any experience. >> >> It appears to be a DS2480B-based (standard serial) adapter coupled >> with a USB->serial chip (Silicon Labs CP2101). >> >> There seems to be support for the chip in the linux kernel >> (http://www.etheus.net/CP210x_Linux_Driver), and it gets recognized as >> a a ttyUSB device. >> >> Any users? >> >> Paul Alfille >> ------------------------------------------------------------------------ >> >> ------------------------------------------------------------------------------ >> This SF.net email is sponsored by: >> High Quality Requirements in a Collaborative Environment. >> Download a free trial of Rational Requirements Composer Now! >> http://p.sf.net/sfu/www-ibm-com >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Owfs-developers mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/owfs-developers >> >> > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > High Quality Requirements in a Collaborative Environment. > Download a free trial of Rational Requirements Composer Now! > http://p.sf.net/sfu/www-ibm-com > _______________________________________________ > Owfs-developers mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/owfs-developers > > ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Owfs-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/owfs-developers
