similar to: Can't connect USB Serial (COM3)

doctordruidphd wrote: > I am trying to use software to program a scanner radio (BCD396t and UASD software). The software installs and seems to run properly, reading and writing database files. But I cannot connect to the scanner, through 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

OK, I am running CentOS 6 on my Laptop and Desktop, presently kernel version 2.6.32-696.20.1.el6.x86_64 (yes, a version or so out of date -- I'll probably do an update soon -- non-trivial since my Internet connection is via dialup). I recently bought a couple of Adafruit Arduino compatibles, a Flora and a Metro 328. Hooking up the Flora and the Metro to a Raspberry Pi running Raspbian

Hello We have computers which redirect COM2(ttyS1) to SOL(Searial console Over Lan). We have been using pxelinux to boot them with the following pxelinux.cfg/default setting. pxelinux.cfg/default serial 1 19200 console 1 prompt 0 timeout 100 default menu.c32 label Linux Diskless menu label ^Linux Diskless kernel menu.c32 append pxelinux.cfg/linux.menu label Bios Setup

hello everyone, I've been testing the NUT solution as opposed to the undocumented LanSafe application to control my Eaton UPS. I am on a Slackware 13.37 system with a 2.6.37.6 kernel. NUT version is 2.4.3 . I installed the tarball by compiling it directly on my system (as a slackbuild package). The UPS is an Eaton Powerware 9155, but I don't know how to obtain the manufacturing date. The

Anyone have an idea as to how to automatically detect the USB number and create a sym link in the dosdevices directory. The problem is that I have several USB devices not used at the same time, and when the USB to serial adapter is connected, a /dev/ttyUSB? is assigned. To use this assignment under WINE, I need to automatically detect /dev/ttyUSB? and then create a sym link in

I am trying to use software to program a scanner radio (BCD396t and UASD software). The software installs and seems to run properly, reading and writing database files. But I cannot connect to the scanner, through 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.

I decided to try this to see if it worked better since Powerware decided to build in some oddball USB protocol instead of using a HID UPS profile, but it doesn't seem to work. The USB/serial dongle is recognized by Linux and added as /dev/ttyUSB0, owned by group "dialout", so I had to add the nut user to the dialout group. In the compatibility list, the proper driver for the

Hi Charles! Thanks a lot for your response. Now I figure why the isbmex driver was not working. On the other hand I've tried to run the command suggested. But no success. I got this information when running the dmesg command after running the modprobe $ sudo modprobe ftdi_sio vendor=0x0483 product=0x0035 [35816.111760] usbcore: registered new interface driver usbserial [35816.111792]

I've got USB->Serial converter: Code: Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC and I need communicate with this converter to devices(Kirk) via specific Kirk windows software. I have mapped converter: Code: ln -s /dev/ttyUSB0 com1 but I can't connect to it. If I connect the Kirk device directly through mapped /dev/ttyS0, the device get connected. Any

I'm fairly new to wine. I'm running the version (Wine 20050211) that comes with SuSE 9.3. I had been using the version that came with SuSE 9.1 (Wine 20040213), and recently ran the SuSE 9.3 upgrade installation. Getting ready to try installing Word Perfect 8.0, I've been reading the help documents. I recollect a warning not to run wine as root. By mistake, I did so. When I did, it

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 away when I unplug the serial adapter from the USB port or shut down the

Hello everyone and best wishes for 2023 :) I have an old *Garmin Drive Smart 50 GPS* and I want to be able to attach it when it is in preboot mode to a VM hosted by a *Debian 11 host*. From what I understand, the preboot mode allows us to flash a firmware before the GPS actually starts (used among other things when the GPS is soft bricked). When I connect the GPS to the host it gives:

[please use the nut-upsuser@ address rather than nut-upsuser-owner@ and be sure to use Reply-All - thanks!] On Dec 23, 2014, at 1:52 PM, Janez Kremzer <janez256 at gmail.com> wrote: > Hi! > > I woud like to use Raspberry Pi with NUT installed whic coud shut down NAS in the office. > NAS doesn't have comport and this is the reasion why not to use NAS directly. > >

OK, I know this has been asked before, but I'm afraid I can't find it in the archives, so I'm asking *again*. Sorry. I have a USB device (Parallax Propellor USB servo controller http://tinyurl.com/425jm8q) - that uses an FTDI chip to appear on a Windows system as a COM port and which, so far as I can tell, appears on my Linux box as /dev/ttyUSB0 (at least, that device appears

I am in the process of migrating from running CentOS 4.8 (32-bit) to CentOS 5.4 (64-bit) on my AMD Sempron(tm) Processor LE-1300 system (it is running CentOS 4.8 32-bit because the disk images are from a previous PIII system), and things are 'interesting' WRT how the Lava Computer mfg Inc Quattro-PCI card is being handled. lspci (on CentOS 4.8 32-bit) yields: 01:0a.0 Serial controller:

Hi all! I have a very special device connected to my serial port and want to execute a Win32 program to work with the device. I trying to execute it with wine 1.0.1 form debian package. Win32 software starts and says that can not find a device. Under VirtualBox it works fine. This is a part of log with +file,+comm debug flags: Code: trace:file:get_dos_device L"COM1" ->

Hello, I have an application that sends data out to a serial port, then should receive the reply. After some hassles I got the application to enumerate the serials (in a dialog box where you select the port), and after creating the link in dosdevices (in lower case I should note, wine will not recognize COM1) it actually starts sending out data (verified using a terminal on the other end). But

Wine version: Wine 20040914 Config:....... [serialports] "Com1" = "/dev/cua0, 38400" "Com2" = "/dev/ttyS1, 38400" "Com3" = "/dev/ttyS2, 38400" "Com4" = "/dev/modem, 38400" I added the 38400's later. I have been trying to run a zoom modem flash upgrade application on Linux with wine (No native windows

I'm trying to get the Windows-software for my digital camera to work in wine under Mandrake 8.0 (kernel 2.4.3). Installed wine without errors. Had a look at the ~/.wine/config and it looked ok for me. The part concerning the serial ports: [serialports] "Com1" = "/dev/ttyS0" "Com2" = "/dev/ttyS1" "Com3" = "/dev/ttyS2" "Com4"

Hi Folks, I'm trying to install Debian onto a headless server (Supermicro X8SIE-LN4F motherboard). The on-board IPMI BMC redirects the serial port to COM3, and I can talk to it just fine over a remote console connection. I've been trying to install Debian remotely, and have the DHCP and TFTP servers working, and things seem to work (at least into the Splash screen) if I'm using