For now it is assumed, that users who are given access to a modem are responsible enough for their actions. is made, so a normal user could interfere with things like uucp. It is potentially dangerous though: no check for lock files etc. This option is handy if you quitted from minicom without resetting, and then want to restart a Minicom will skip the initialization code. This is very handy if minicom refuses to start up because your system has changed, or for the first time you run minicom.įor most systems, reasonable defaults are already compiled in.ĭo not initialize. When it is used, minicom does not initialize, but puts youĭirectly into the configuration menu. Root edits the system-wide defaults in /etc/minirc.dfl with this option. Any help on this one would be greatly appreciated.Minicom is a communication program which somewhat resembles the shareware program TELIX but is free with source code and runs under most unices.įeatures include dialing directory with auto-redial, support for UUCP-style lock files on serial devices, a separate script language interpreter, capture toįile, multiple users with individual configurations, and more.
I checked and confirmed that the cable is good using Hyper terminal with the same serial port settings. I don't know if I am missing a driver or something else.
usb 5-1: pl2303 converter now attached to ttyUSB0.Įarlier I associated ttyS0 to ttyUSB0 using the ln command then removed the ttySO from the /dev/ folder.
When I typed in dmesg | grep tty I got this: When I typed lsusb at the terminal I got:īus 005 Device 010: ID 067b:2303 Prolific Technology, Inc. Then a flashing cursor which allowed me to type but did not echo back anything. When I opened minicom with this configuration I got this output: I shorted out the pins 2,3 and changed the baud rate in Minicom to 19200 with 8N1 with no flow control and also changed the serial device to /dev/ttyUSB0. I am using a pl2303x USB-serial converter cable and running Ubuntu 10.0.4 on my PC. I also noticed that if I restart the virtual machine ttyS0 gets reset to 660 probably normal. PS: I'm not trying to get internet, VMWare set up NAT/Bridged connection's fine automatically for me, however, I have a wireless modem that I wanted to test/work on using a desktop PC, and I'll eventually use it in an embedded device.ĮDIT: I also thought it might be mod on ttyS0 so I set it to 777 and tried restarting minicom but it didn't work. Is this normal in Minicom v2.3? Is there a setting I need to make sure I have enabled to type manually? Could I have the "9600 8N1" wrong? If I connect Hyperterminal using "9600 8N1" to COM1 then I'm able to type things like "at" and see an "OK". OKI think it can see the modem fine because if I unplug the modem and restart minicom I don't get the automatic "AT S7=45 S0=0 L1 V1 X4 &c1 E1 Q0" message.
0 kommentar(er)
