search for: ttyusb0

Kernel parameters aside (console=ttyUSB0 console=tty0), I am trying to get a login console working on a USB-to-serial adapter. systemctl enable serial-getty at ttyUSB0.service systemctl start serial-getty at ttyUSB0.service This works without issue on Debian 8. However when running the same on CentOS 7, my logs are filled with: May 1...

...usb 6-2: New USB device found, idVendor=067b, idProduct=2303 usb 6-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 6-2: Product: USB-Serial Controller usb 6-2: Manufacturer: Prolific Technology Inc. pl2303 6-2:1.0: pl2303 converter detected usb 6-2: pl2303 converter now attached to ttyUSB0 This converter appears to the system as /dev/ttyUSB0. But I presume for all practical purposes I should assume that this is just another serial port (correct me if that's wrong). My ups.conf looks line: [DSAups] driver = bcmxcp port = /dev/ttyUSB0 desc = "Eaton...

Ubuntu creates /dev/ttyUSB0 for me when I plug in the usb-to-serial-adapter. I have a symbolic-link to /dev/ttyUSB0 from 'dosdevices/com1'. What is new in 10.04 Ubuntu is that I have to sudo chmod o+r and sudo chmod o+w on /dev/ttyUSB0 every time before I start the app which uses that serial line. ttyUSB0 goes a...

I have been trying to get an EVDO modem to work with Centos 5. I can make it dial out with wvdial only when I'm the root user. Otherwise I get this error: Cannot open /dev/ttyUSB0: Device or resource busy I added the user to the uucp group. crw-rw---- 1 root uucp 188, 0 Dec 3 02:30 /dev/ttyUSB0 crw-rw---- 1 root uucp 188, 1 Dec 3 02:30 /dev/ttyUSB1 crw-rw---- 1 root uucp 188, 2 Dec 3 02:30 /dev/ttyUSB2 crw-rw---- 1 root uucp 188, 3 Dec 3 02:30 /dev/ttyUSB3 What ha...

...xPacketSize 0x0008 1x 8 bytes bInterval 1 When I try to use blazer_ser, the command: sudo upsdrvctl start Result the below message: Network UPS Tools - UPS driver controller 2.6.4 Network UPS Tools - Megatec/Q1 protocol serial driver 1.55 (2.6.4) Unable to open /dev/ttyUSB0: Input/output error Current user id: nut (116) Serial port owner: root (0) Serial port group: nut (122) Mode of port: 1660 Things to try: - Use another port (with the right permissions) - Fix the port owner/group or permissions on this port - Run this driver as another user (upsdrvct...

On Feb 18, 2014, at 10:15 PM, Charles Lepple wrote: > On Feb 18, 2014, at 5:55 PM, Thiago Tiedtke dos Reis wrote: > >> Hi, >> >> Recently I got three units of this nobreak [0]: > ... >> [0] http://www.sms.com.br/produtos/Nobreak-SMS/Manager-III-Senoidal > > According to the HCL, for the Manager III, you might want to try the blazer_ser (or in 2.7.1,

Since I'm new to this forum I probably I'm doing something wrong, I'm sorry if this's the case! I don't have a windows base system, solely Puppy Linux. I do have an Axim, though; can't do hardly anything useful with it since starting using just Linux. Went through many pages about WINE but failed to locate any useful info. That's the reason for posting my issue here.

...test pc and test how the driver behaves while running on battery and its responses to commands. After this, I will compare against vendor software and post final results here. I am also looking for any advice on test methodology. Rodrigo [smsbrasil] driver = smsbrasil port = /dev/ttyUSB0 desc = "smsbr" default.ups.power = 1400 default.ups.efficiency = 85 default.battery.capacity = 14 root at home:~# upsc smsbrasil battery.capacity: 14 battery.charge: 100.0 battery.charge.low: 30 battery.charge.restart: 25 battery.charge.warning: 40 battery...

...beeper.toggle works as expected. cmd shutdown.return works as expected. cmd shutdown.reboot does not work entirely. After a minute, UPS is shut down but didn't come back. (Issuing shutdown.stop power up it again) Some details I found: After shutdown.return and shutdown.reboot, usb port (/dev/ttyUSB0) is still open and working. Powering down from ups button disables communication. Power up from ups button issues power-on self test (pop, crack and clicking sounds) whereas shutdown.return and shutdown.stop just bring it on without post. I think this is normal. Also, from ups button power up, po...

Hello! I've ran into this annoying issue when setting up a new server. I have an APC SmartUPS hooked up on a USB-serial converter on /dev/ttyUSB0. This works nicely, until: hub 3-0:1.0: port 1 disabled by hub (EMI?), re-enabling... pl2303 ttyUSB0: pl2303 converter now disconnected from ttyUSB0 usb 3-1: pl2303 converter now attached to ttyUSB1 apcsmart gets into an infinite loop of this: apcsmart[2285]: smartmode: issuing 'Y' fail...

...Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub The description of equipment don't appear. In the ups.conf, i used the follow lines. [ups] driver = blazer_ser port = /dev/ttyUSB0 desc = "SMS 8 KVA" When start the process by the nut, i received a Error message: root at rasp:/etc/nut# upsdrvctl start Network UPS Tools - UPS driver controller 2.7.4 Network UPS Tools - Megatec/Q1 protocol serial driver 1.57 (2.7.4) No supported UPS detected Driver failed to...

Hi I am trying to connect a reliance netconnect data card on my linux box ( cent os ) , i am able to the detect the device /dev/ttyUSB0 these are the following steps I did : Check your card is recognized by the kernel # cat /proc/bus/usb/devices ..... ..... T: Bus=07 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 11 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=19d2 ProdID=fff5 Rev= 0.00 S: Ma...

...rough a USB-to-serial cable. > OS: ubuntu-8.10, kubuntu-8.10, debian/lenny (tried them all) > > lsusb identifies the cable as follows: > Bus 002 Device 002: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port > > I set up the link in dosdevices as follows: > ln -s /dev/ttyUSB0 com5 > > When I change the baud rate in the software, and then check with stty, it is changing the baud rate on ttyUSB0, so that part works. This computer has only USB ports, no serial. I actually have several other devices with the same problem -- need to program with USB-serisl cables. &gt...

Yes I do have Linux. I have assigned the ups.conf file as seen below.. [testups] Driver = usbhid-ups Port = /dev/ttyUSB0 When I try to start the ups driver I get the following error... $ sudo upsdrvctl start Network Ups Tools - UPS driver controller 2.7.1 Network Ups Tools - Generic HID driver 0.38 (2.7.1) USB communication driver 0.32 No matching HID UPS found Driver failed to start (exit status=1) Thanks for th...

...recognised well without losing connections) > > > Instalation: > > I'm have little NUT experiance. Because of that was read that blog at the begining. > I made same installation of nut but without usb drivers at the begining. > > I setup apcsmart driver on port /dev/ttyUSB0 in ups.conf and check that runing user=root. > user=root is only for testing- this may cause other permissions problems later. I have been meaning to collect some information on using serial UPSes with NUT via USB-to-serial converters, but you can adapt the udev rules to match your converter,...

>> I setup apcsmart driver on port /dev/ttyUSB0 in ups.conf and check that runing user=root. >> > user=root is only for testing- this may cause other permissions problems later. It looks like the simplest way to handle this on Debian is to add the system 'nut' user to the 'dialout' group: $ sudo adduser nut dialout...

...ian-or-ubuntu-linux/and seeing support for Apollo UPSes mentioned on the compatibility list (genericups, type=4) I tried to set up Nut as follows. OS: Ubuntu Server 12.04 Nut: 2.6.3 (I believe - from Ubuntu repos) ups.conf: > [apollo] > driver = genericups > upstype = 4 > port = /dev/ttyUSB0 Problem is that there is no ttyUSB0 device. UPS attaches to machine via USB cable, and lsusb indicates that it is a Cypress Semiconductor USB to Serial cable. > $ lsusb > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2...

please subscribe to the list: http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev On Feb 19, 2014, at 7:52 AM, Thiago Tiedtke dos Reis wrote: > If I try to access the port /dev/ttyUSB0 using minicon (minicom -D /dev/ttyUSB0) or cat ( cat /dev/ttyUSB0 ), the access to device is denied. even as root? > Then, I try these instructions [0], but nothing changes when I try to open the serial port: That blog is slightly misleading: if you have a USB UPS which pretends to be a seri...

Thanks for the response. No /dev/ttyUSB0. /dev/tty and /dev/tty1 ... /dev/tty63 /dev/ttyS0 ... /dev/ttyS3 but no /dev/ttyUSB0 How can I get one? Just make one? All the rest are 4,0-67 plus one 5,0 What ought the major number be? On 2016-10-20 07:33, Charles Lepple wrote: > [please use reply-all to include the list - the headers...

...is an issue in getting MapSource to recognize the GPS while connected via USB but I am unable to understand the steps provided to solve this issue. I've been advised to enter "sudo modprobe garmin_gps" in terminal and to check the results. So I connect the GPS and get a "/dev/ttyUSB0" file. I've been advised it should be owned by root and dialup group and to change the ownership to myself. However I don't know how to do this. I was also told to go to ~/.wine/devices and make a soft link called com1 to /dev/ttyUSB0. Again I don't know if this creates the so...