OpenSUSE Hardware - Pl2303 Serial - USB Adapter Not Working - Minicom Reports Offline
Oct 1, 2010
I am using a Prolific pl2303 USB<=>Serial adapter. dmesg reports everything seems ok when I plug it in (see below) but when I open the ttyUSB0 port in minicom, it is always offline and nothing works. Also, minicom reports:
[code]....
If I plug the adapter into a different machine (Windows) everything works fine. The serial port is setup correctly (9600-8-N-1) What can I do to get this working?
usb 5-2: new full speed USB device using uhci_hcd and address 3
usb 5-2: configuration #1 chosen from 1 choice
pl2303 5-2:1.0: pl2303 converter detected
usb 5-2: pl2303 converter now attached to ttyUSB0
usb 5-2: New USB device found, idVendor=067b, idProduct=2303
[Code]....
I have a usb serial adapter and was happily using minicom with it under openSUSE 11.2. I've upgraded to openSUSE 11.3 and I can only use minicom with this serial adapter as root. I had previously had problems writing to /var/lock under openSUSE 11.2 which I worked around by changing the minicom config to use /tmp as its lock file location.
Unfortunately my laptop doesn't have a built in serial port so I can't tell if its a general problem or something specific to the /dev/ttyUSB0 device. This is the output I get when I run minicom with my regular user account. I get the same output whether the lock file location is set to /tmp or /var/lock
Code:minicom usb0 Device /dev/ttyUSB0 lock failed: Permission denied. Before I started tinkering my user belonged to the following groups groups=16(dialout),33(video),100(users) I've since added 5(tty),14(uucp),21(console) but still no joy.
Minicom was running fine two days ago capturing data from a gage device via a serial cable. Yesterday, users of the data started complaining that they were not receiving any data.
The minicom status line reads offline. Is this part of the problem or is this normal (I never really noticed it before.) All settings on the gage device match the minicom settings.
I am trying to access an OpenBSD system that I have just installed via my PcBSD system by the use of a serial cable. I have been trying both minicom and cu but I am obviously doing something wrong... cu -l /dev/cuad0 returns /var/spool/lock/LCK...cuad0 Permission Denied. Can't Open lock file. all ports busy. And when I try to connect through minicom I either get a similar lock error, or minicom will sit at the connection screen with (offline status). I feel like the answer to my problems is a rather simple one, but I do not know where else to look for information.
1) Compaq laptop, legacy free (no COM or LPT ports, USB only)
2) The laptop owner has dial-up and can't get broadband right now.
3) The laptop is running F12 with the PAE kernel.
4) Internal modem is a Conexant modem masquerading as Intel ICHxxx chipset. All attempts at getting a driver to work for this so far have failed.
5) I downloaded a Linuxant RPM but this failed to work.
So my only option that will get the computer back to its owner is an external modem using a Prolific PL2303 USB to SERIAL adaptor cable. When using the PL2303 cable my external modem appears as /dev/ttyUSB0 For the most part this works fine. I used the steps in the solution from the following thread
[URL]
The only problem I have is getting PPP to work THROUGH the cable. I have verified the cable is the issue. HOW?
1) I have tested all the modems on another machine with F12 through the onboard COM port. All modems dial, connect, then authenticate and maintain connection until I manually disconnect.
2) I have tested all modems used on the other machine with the PL2303 and can replicate the problem on that machine.
3) I have used more than one PL2303 cable and get the same behaviour.
Using the network configuration utility / wvdial / modem lights OR kppp produces the same results when controlling the modem located at /dev/ttyUSB0 So do I
1) have to make some configuration changes to relating to /dev/ttyUSB0
OR
2) is the something in ppp that needs configuring
OR
3) is it something else altogether that I am not aware of?
I picked up as Dynex usb2serial converter to use with my cisco router/switch. The dongle works fine if plugged into a windows box & puTTy, but I cannot get it to work with Fedora 14. When I try to use cute, mini or command line it tells me it cannot open the connection. Here is the output from lsusb and dmesg. susb output:
I am working on a embedded target board which runs on linux. The target board is connected to a linux machine through serial port. To bootup the target board, I run the minicom in the linux machine, boot the kernal of the target board through giving the boot command through the serial console (minicom). Now the question is when the target board boots up, it doesn't starts a shell. The rc scripts are getting executed. There are target specific applications getting started from the rc scripts. I appended & to the last launched application. Still I don't get shell prompt.
I am running kubuntu 9.04. I have minicom, Gtkterm and Putty installed. minicom seems to be really good, but I am missing scroll back functionality on there. Either that or I'm a novice with it and don't know how to do it. Putty is a GREAT app. But what I'm finding is that after the terminal runs for a bit, the screen shows characters from the previous lines and goofs up the output. If I move the window, the gibirish disappears. gtkterm is adding several empty lines to any of the screen output.
I am hoping to be able to get an old serial-touchscreen to work with a usb/serial adapter. I had this touchscreen working some years ago on different hardware. I would like to hook it to the machine I am setting up as a multimedia host with mythtv among other things.
Following the instructions I left behind when I got this to work way back when does not work. See [URL] ....
This info is a work around to get the xserver to see the touchscreen. [URL] ....
I do know that the touchscreen works as I am able to get garbage on the screen as in the first part of my howto. But I have not had any success getting xorg to see it. I wish I had posted a copy of the xorg.conf at the time, but......
There is an issue with the current xserver in testing that I am hoping the next update (in unstable) will fix when it gets pushed to testing. That is that Code: Select all# X -configure fails with a segfault. So I am not able to generate the xorg.conf needed to get it to work. I was going to post a bugreport, that is when I found out there is an update in unstable, so I am waiting for it to get pushed at the moment.
Anyway I am hoping that I can link /dev/ttyUSB0 to /dev/tty0 and get it to work. I would like some kind of guess as to my chances of success before I go to all the work of getting the monitor hooked to the host.
i need a usb to rs-232 converter to get into the console port i have an aten uc-232a converter and i have downloaded a .gz file called uplcom.4freebsd.gz i have unpacked it but i do not know what to do from here could some one please help i need to do some practice for the external icnd 2 exam and i have left it to the last minute as per usual.
I am using a Sealink PN 2202 USB serial adapter on a linux box (Ubuntu 10.4) running kernel 2.6.32-28-generic. I have written a perl script to simply log the incoming RS232 data (9600 8N2) and it works fine when I start it from a bash shell: perl /home/pk/PerlCode/RS232_D4_v11.pl
However, I need the computer to boot and start logging after a POR. If I try to use Startup Manager to execute my script everything seems ok but I randomly loose about 20% of the incoming RS232 data. In Startup Manager I use the command gnome-terminal --title="D4 RS232 Log" --execute bash -c "perl /home/pk/PerlCode/RS232_D4_v11.pl"
If I close the automatically-started script and restart it from a bash shell, I again will randomly loose about 20% of the incoming RS232 data. It almost seems like I have screwed up the driver by using the Startup Manager. The only way I can get reliable logging again is to remove the script from Startup Manager, then restart the computer and manually launch the perl script. I was thinking that maybe the order in which the driver was loaded and perl script started might be an issue. So I tried a bash script that sleeps for 15seconds, then starts the perl script. Again, I loose random pieces of incoming data when this is initiated by Startup Manager.
Here is some more info: lsusb Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 004: ID 0c52:2223 Sealevel Systems, Inc. Bus 002 Device 003: ID 0c52:2213 Sealevel Systems, Inc. Bus 002 Device 002: ID 03eb:3301 Atmel Corp. at43301 4-Port Hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub .....
sudo cat /proc/tty/driver/usbserial usbserinfo:1.0 driver:2.0 0: module:ftdi_sio name:"FTDI USB Serial Device" vendor:0c52 product:2213 num_ports:1 port:1 path:usb-0000:00:1d.0-2.1 1: module:ftdi_sio name:"FTDI USB Serial Device" vendor:0c52 product:2223 num_ports:1 port:1 path:usb-0000:00:1d.0-2.2
ls -al /dev/ttyUSB* crw-rw---- 1 root dialout 188, 0 2011-03-08 09:56 /dev/ttyUSB0 crw-rw---- 1 root dialout 188, 1 2011-03-08 09:56 /dev/ttyUSB1 I am a member of the group dialout.
I though it may have something to do with su vs my ownership of files. If I do a sudo chmod 777 /dev/ttyUSB* then ls -al /dev/ttyUSB* crwxrwxrwx 1 root dialout 188, 0 2011-03-08 09:56 /dev/ttyUSB0 crwxrwxrwx 1 root dialout 188, 1 2011-03-08 09:56 /dev/ttyUSB1
However, after rebooting it reverts to ls -al /dev/ttyUSB* crw-rw---- 1 root dialout 188, 0 2011-03-08 09:56 /dev/ttyUSB0 crw-rw---- 1 root dialout 188, 1 2011-03-08 09:56 /dev/ttyUSB1
Im a very basic Linux/ Centos user. I have Putty installed and a USB to serial adapter. All settings seem to be right as far as speed, etc, but I'm not sure how to list the device to open for the program. The default location it gives is "/dev/ttyS0" Trying to find where the USB is located using the "/sbin/lsusb" command gives me-
Bus 001 Device 001: ID 0000:0000 Bus 002 Device 001: ID 0000:0000 Bus 003 Device 001: ID 0000:0000 Bus 004 Device 002: ID 0557:2008 ATEN International Co., Ltd UC-232A Serial Port [pl2303] Bus 004 Device 001: ID 0000:0000
So I think this means that it is on bus 4 correct? So how do I list this for putty to open the device.
I tried connecting my Debian laptop to a vintage Apple //e using a Super Serial Card on the Apple side and a USB to serial adapter on the laptop side. It kind of works -- I can send data over to the Apple using e.g. echo "foobar" > /dev/ttyUSB0 or via minicom --, but every 20 seconds (quite exactly!) some 4 random characters appear on the Apple's screen (mostly tildes, sometimes a pipe). This does *not* happen when booting the laptop into Debian rescue mode; so I guess it must be some (daemon?) process messing around with the usb serial device in regular intervals.
I tried to disable quite some services, but the problem remains.I don't have any clue how I might catch the evil-doer in the act -- virtually all serial monitors I've so far read about allow only monitoring the interaction of a known program/process with a serial port. But in this case I first have to actually find out which process is talking to the serial port in the first place.
I got the following task from my boss. I have to find out if there is some alternative tool for create reports from Squid except SARG. Now, we use SARG, but my boss told to me, that the main problem of SARG is, that SARG generate huge amount files, which cause problems during migration our servers. He told to me the following condition for change of current tool (SARG):
* standard package of Debian * generate less amount of files, optimal is to save reports to the database
So I would like to ask you if you know about some tool (I can not find some by google)... and the best would be if you told to me some practical experiences.
I installed Fedora 12 in my PC and after that when I tried to use minicom it was not installed. I tried copying the executable of minicom in /usr/bin from another PC and tried using it. But, I was not able to enter any commands in minicom..
I had my wired internet working ok, but now that's not working for god knows what reason (yes I'm new). I've got my D-Link DWL-G120 usb wireless adapter pluged in but it's not "working". In the Hardare section it shows all the information for it but it shows it as a unclassified device. At this point I'm thinking of buying a bridge and just reinstalling the OS (plus I want to get a bigger Hard drive as I've got it on a 7 GB drive right now).
We are using thin client systems in our work environment. There is a central ubuntu server and by using thin clients, we are connecting to our homes. The problem is when I try to install an application, it reported me that I had 200 mb of disk space. But when i try to look from console, I see that /home folder has over 250 gb s of disk space. Even when I try to look from baobab, Disk Usage Analyzer in Ubuntu, i see that my home file system is full.
So what's the reason that I am receiving different kinds of disk space report from different sources? Our system admin here told me that some applications foolishly try to see the physical devices on the thin client and got confused as a result. Is this true?
All operation result in a seperate window displaying the progress of the compression but with an error.
Error 127, cannot execute requested operation.
Then when the progress bar reaches full it resets and then resets again continuing the same loop with it becoming slower with every repetition. There is no information posted in the report log of the window. Except that the task has started.
I'm trying to simply archive a file and password protect it. This shouldent be such a difficult task.
P7zip also gives me its own set of errors when archiving.
after installing the OS my mouse was not working. After searching in net for a day, I made it working. Shall give the details hereIf its a repeat thread please ignore it.1. Go to Terminal.2. Login as root.3. su -c 'yum install -y system-config-display'This step will take some 2 to 5 mins 4. su -c 'system-config-display --reconfig'After Fedora 9/10, the xorg.conf is not available and it uses HAL to detect the hardwares. The above steps create the config file.
5. su -c 'cp /etc/X11/xorg.conf /etc/X11/xorg.conf.bak' back up 6. su - -c 'gedit /etc/X11/xorg.conf'
I have RHEL 5.3 installed on HP ProLiant DL320 Generation 5 but i cant get serial port workingdmesg | grep ttyserial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A00:09: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
We have just installed the 11.3 version of opensuse in a Dell Poweredge T610 with 8 Gb in RAM and two (2) Xeon Quadcore proccesors. Well, the first time the Opensuse resets the computer, after the installation (it was fine, w/o any problem) the system goes frezze showing a screen which reports a BUG ERROR in the Kernel code, specifically:
Kernel bug at /usr/package/BUILD/kernel-desktop-2.6.34/kernel/timer.c:643 invalid opcode: 0000 [#1] PREEMPT SMP last sysfs file: /sys/module/thermal_sys/sections/__ksymtab_strings CPU 11 ... ...
After a "button off" reset the machine boots fine and we could finish the configuration of the applications that we needed. We tested the machine by two days and it didn't show again the problem mentioned, and we believe it was a little bug in the installation, but today, the server halts again in the boot process 3 (three) times before it runs again well.We have repeated this installation in other computers, one in a 32 bit version and other in 64 bits version (like the Dell) and only in the last one has repeated the problem, I mean, no problems in the 32 bit installation. Fortunately, this new server is just a replacement for an old machine, that is running with the 10.3 version. Perhaps, does we continue using the 10.3 instead of the 11.3 meanwhile it is deputed?
Opensuse Linux (Linux sr-server 2.6.37.6-0.7-default #1 SMP 2011-07-21 02:17:24 +0200 i686 athlon i386 GNU/Linux). I have a very unusual problem where fdisk reports one size BUT df reports a TOTALLY different and unexpected size. Besides doing a full backup, repartition, reformat and restore, is there anything else I can try first??
Here are the outputs: (sda1 and sda2 sizes are completely different from fdisk!!) df -v -h Filesystem Size Used Avail Use% Mounted on rootfs 22G 17G 4.2G 81% / devtmpfs 369M 152K 368M 1% /dev tmpfs 375M 648K 374M 1% /dev/shm /dev/sda2 22G 17G 4.2G 81% / /dev/sda1 15G 7.8G 6.6G 54% /windows/C
but I'm not seeing anything from a GPS receiver in NMEA at 4800 no par 1 stp I know that was working about a year ago. I think udev was not helping ,as I was getting permission denied to the com port, I added myself to group dialout. and no message on startup now
I need to be able to talk to a piece of kit with 9600 baud and nothing. I have win32 s/w to drive it , but it falls over in wine. My laptop still has win7 on it in a tiny partition but no 9w d connector and I'm waiting for a USB converter cable. Too many variables ! I'd forgotten all the hassle of having to install drivers just to get basic things running. But as the stupid thing couldn't manage using the driver for my NIC, I was stuck with hyper-terminal, and nothing from the GPS board @4800 or another piece of equipment running at 9600. I suspect the com port on the new mobo doesn't wan to play
I am using linux 2.6.20 from ltib-mpc8313erdb-20070824 on my development board having MPC8313 powerpc processor. Whenever I plug-in the USB device, the serial port starts mal-functioning. It does not receive all the packets.
