Minicom has some quirks when it comes to saving and loading configuration files. The configuration directory for the access file and the configurations We can look up the required group membership using the ls command.
This is achieved by adding the correct group membership to our user account. Our user account requires rw permissions to initiate a connection with the device.
#MINICOM EXIT SERIAL#
The rest of this blog post will simply use ttyUSB0 as the name of the serial port, but you must use the correctly named serial port assigned to your connected device if you are following along. The device name for a serial connection is properly referred to as a serial port. Also, the index number at the end of the name is determined by the devices minor number and may not be 0. There are more serial port names than I mention here. If your system architecture is ARM, you might see a name like this ttyAMA0 and if it is a Samsung, then the device might be named ttySAC0. In my case the TTY device name was ttyUSB0 however, if your cable is not a USB converter, then it might be named ttyS0 instead. usb 1-2: FTDI USB Serial Device converter now attached to ttyUSB0 ftdi_sio 1-2:1.0: FTDI USB Serial Device converter detected This problem only appeared after some updates were installed a list of the packages updated right before this problem manifested follows: The system cannot be rebooted from the desktop (possibly because the stalled terminal can't be stopped) and has to be manually power cycled. Multiple RS232->USB adapters and USB port combinations were tried with the same results. Terminal becomes unusable (Ctrl+Z displays the character instead of stopping minicom) If minicom opens, the problem instead appears on exit.īlank terminal window with a cursor but no bash prompt. Launch minicom from gnome-terminal (minicom) OR launch it using the setup switch (minicom -s)ģ. Plug an RS232->USB adapter into one of the system's USB portsĢ. Version-Release number of selected component (if applicable):įedora 18 kernel 3.8.86_64 (also occurs in kernel 3.8.2)Īnytime minicom is run with serial port ttyUSB0 or ttyUSB1, using an RS232->USB serial adapter.ġ. The serial port used for the adapter is either ttyUSB0 or ttyUSB1. This causes the terminal it was opened from to become unusable, and other instances of the terminal opened after minicom are also unusable (they display a cursor but no bash prompt), and they also cannot be killed.
When using an RS232->USB serial adapter, minicom hangs on open and/or close and cannot be stopped or killed.