Project

General

Profile

Actions

Bug #4061

closed

Get error "Could not configure port: (5, 'Input/output error')" when trying to read radio (two different ones) using latest CHIRP build on Ubuntu 14.04 LTS

Added by Michael Bower over 7 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
09/24/2016
Due date:
% Done:

0%

Estimated time:
Chirp Version:
daily
Model affected:
(All models)
Platform:
Windows
Debug Log:
I read the instructions above:

Description

Get error "Could not configure port: (5, 'Input/output error')" when trying to read radio (two different ones) using latest CHIRP build on Ubuntu 14.04 LTS. Most error reference for this type of thing mentions changes to Python code. I assume I don't have access to that here.

I'm not new to ham radio but new to CHIRP.

Same error trying to read from:

BaoFeng BF-F8HP
Yaesu VX-7R

Thank you.


Related issues

Related to Bug #7891: Could not configure port: (5, 'Input/output error') --- STILL NOT SOLVED !Closed05/18/2020

Actions
Actions #1

Updated by Jim Unroe over 7 years ago

  • Status changed from New to Feedback

Michael,

I assume that you are using a USB based programming cable. Which port are you selecting? On my computer running Linux Mint 17.3 (based on Ubuntu), I had to scroll all the way to the bottom of the the port list to find "/dev/ttyUSB0" (the correct selection for a USB based programming cable).

Also which version of CHIRP are you using? Don't install CHIRP from the repository in Ubuntu. That will get you v0.4.1 which is nearly 4 years old. If you did that, then you must uninstall it and then follow the instructions on the CHIRP download page to add the CHIRP snapshot repository and install the latest CHIRP daily build (which is currently CHIRP daily-20160924).

Jim KC9HI

Actions #2

Updated by Dan Smith over 7 years ago

There is an issue with some kernels in 14.04 that cause this problem for all serial ports. Please make sure you're fully updated to 14.04.5 (where I think it has been fixed). It's definitely fixed in 16.04 if you want to upgrade to that.

Either way, an IO error comes from the base OS, not CHIRP, just FYI.

Actions #3

Updated by Michael Bower over 7 years ago

Update:

Based on Dan's statement, I upgraded my computer to Ubuntu 16.04.

Based on Jim's statement, that is a big "DUH" on my part. Didn't think to look all the way at the bottom.

I am now able to connect with the BF-F8HP and read/write the memories. Wahoo!!!!!

I am still unable to connect with my VX-7R but will keep trying.

Thanks for the help, guys.

73s

Actions #4

Updated by Bernhard Hailer about 4 years ago

  • Status changed from Feedback to Closed
  • Chirp Version changed from 0.4.0 to daily

(Mostly) resolved by submitter. Please re-open or open new ticket if any problem is left.

Actions

Also available in: Atom PDF