I ran this command, found on web to install python-future, as the apt install
command was unable to locate package python-future.
> rabbit@ganymede:~$ pip install future
> Defaulting to user installation because normal site-packages is not writeable
> Requirement already satisfied: future in /usr/lib/python3/dist-packages
> (0.18.2)
> WARNING: You are using pip version 20.2.4; however, version 21.0.1 is
> available.
> You should consider upgrading via the '/usr/bin/python3 -m pip install
> --upgrade pip' command.
I ran the two commands you specified. The output is attached. In the syslog
file, the first 3 lines are unplug, the rest are due to replugging in the FTDI
cable. Here seems to be the pertinent line from syslog;
> Apr 7 15:06:08 ganymede ModemManager[1098]: <info> Couldn't check support for
> device '/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1.3': not
> supported by any plugin
Not sure what move to make now.
Kindly,
Robert
On 4/7/21 11:51 AM, Matthew Poletiek wrote:
> Hi Robert,
>
> Looks like you're missing the future module. Not sure if that's
> absolutely required for your radio, but I recommend it.
>
> `sudo apt install python-future`
>
> Did you add rabbit to the usb group? I can't remember if there is one
> in Ubuntu. Don't forget to refresh your profile or try chirp in a new
> terminal after making group adjustments.
>
> Besides that I can't think of anything else you should need to do to
> get this working from Linux's perspective. Out of curiosity can I see
> the output of `sudo dmesg | grep -i ttyusb` ?
>
> Another thing you can watch is syslog while trying to connect to your
> radio. `sudo tail -f /var/log/syslog`.
>
> If everything looks good in those two places I'd double check the
> radio/cable setup.
>
> -------------------------------------------
> Matthew Poletiek
> 303.810.9082
> [email protected]
>
> www.matthewpoletiek.com
> On Wed, Apr 7, 2021 at 9:38 AM Robert Withers
> [<[email protected]>](mailto:[email protected])
> wrote:
>
>> Hi Matthew, here is my attached output from chirpw...
>>
>> Kindly,
>> Robert
>>
>> On 4/6/21 9:49 PM, Matthew Poletiek wrote:
>>
>>> Hi Robert,
>>>
>>> I see Linux sees the device just fine, and you should be in the right
>>> groups. I'd add the 'usb' group just in case as well.
>>>
>>> If that doesn't work then maybe the output of CHIRP run in the command
>>> line might hint at whats going wrong.
>>>
>>> Also, how did you install this? You might be missing some Python 2
>>> dependencies. Personally I use Gentoo and they ditched Python 2 a
>>> while back and we lost CHIRP due to lack of Python 3 support so I
>>> forked and use this version instead:
>>> https://github.com/mpoletiek/py3-CHIRP
>>> But before you try that, let's add rabbit to the usb group if there is
>>> one and see what CHIRP is outputting when run from a terminal.
>>> -------------------------------------------
>>> Matthew Poletiek
>>> 303.810.9082
>>> [email protected]
>>>
>>> www.matthewpoletiek.com
>>> On Tue, Apr 6, 2021 at 7:20 PM Robert
>>> [<[email protected]>](mailto:[email protected])
>>> wrote:
>>>
>>>> Hi Matthew, user is in the dialout group, which is the correct group for
>>>> /dev/ttyUSB0.
>>>>
>>>> rabbit@ganymede:~$ cat /etc/group | grep -i rabbit
>>>> adm:x:4:syslog,rabbit
>>>> dialout:x:20:rabbit
>>>> cdrom:x:24:rabbit
>>>> sudo:x:27:rabbit
>>>> dip:x:30:rabbit
>>>> plugdev:x:46:rabbit
>>>> lpadmin:x:120:rabbit
>>>> lxd:x:131:rabbit
>>>> rabbit:x:1000:
>>>> sambashare:x:132:rabbit
>>>> rabbit@ganymede:~$ ll /dev/ttyUSB0
>>>> crw-rw---- 1 root dialout 188, 0 Apr 6 19:10 /dev/ttyUSB0
>>>>
>>>> I wasn't sure that there may be a new graphical device manager I did not
>>>> know about in Ubuntu. And why not? I don't think there is a System menu,
>>>> either! So back to the command line...I started with Slackware 0.96, so
>>>> not a noob to Linux, but it has been awhile since serious sysadmin hacking
>>>> and never before any serial work. I am a noob to Chirp. As I mentioned
>>>> earlier, my ham radio appears to be on /dev/ttyUSB0:
>>>>
>>>> rabbit@ganymede:~$ dmesg | grep tty
>>>> [ 0.108706] printk: console [tty0] enabled
>>>> [ 0.396467] 00:05: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is
>>>> a 16550A
>>>> [ 0.418518] 0000:00:16.3: ttyS4 at I/O 0xf0e0 (irq = 19, base_baud =
>>>> 115200) is a 16550A
>>>> [ 3.348131] usb 1-1.1.3: FTDI USB Serial Device converter now attached
>>>> to ttyUSB0
>>>>
>>>> Kindly,
>>>> Robert
>>>>
>>>> . .. ... ‘...^,^
>>>>
>>>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>>>>
>>>> On Tuesday, April 6th, 2021 at 7:21 PM, Matthew Poletiek
>>>> [<[email protected]>](mailto:[email protected])
>>>> wrote:
>>>>
>>>>> I'll just add you can see your current groups with;
>>>>>
>>>>> `cat /etc/group | grep -i <username>`
>>>>>
>>>>> Matthew Poletiek
>>>>>
>>>>> 303.810.9082
>>>>> [email protected]
>>>>>
>>>>> www.matthewpoletiek.com
>>>>> On Tue, Apr 6, 2021 at 6:20 PM Matthew Poletiek
>>>>> [email protected]
>>>>> wrote:
>>>>>
>>>>>> Hi Robert,
>>>>>>
>>>>>> You might want to check to make sure your user has proper permissions.
>>>>>>
>>>>>> In linux, typically the groups you might need for this kind of
>>>>>>
>>>>>> operation include `dialout`, `usb`, and while you're at it you might
>>>>>>
>>>>>> as well include `plugdev`.
>>>>>>
>>>>>> The command to add your user to a group might be `sudo gpasswd -a <user>
>>>>>> group`.
>>>>>>
>>>>>> Once thats finished you might need to refresh your profile. Either try
>>>>>>
>>>>>> opening CHIRP in a new terminal, or log out and log back in.
>>>>>> ------------------------------------------------------------------------------------------------------------------------------------
>>>>>>
>>>>>> Matthew Poletiek
>>>>>>
>>>>>> 303.810.9082
>>>>>> [email protected]
>>>>>>
>>>>>> www.matthewpoletiek.com
>>>>>> On Tue, Apr 6, 2021 at 5:56 PM Robert via chirp_users
>>>>>> [email protected]
>>>>>> wrote:
>>>>>>
>>>>>>> Nigel,
>>>>>>>
>>>>>>> Here is some more info, I think this is saying it is attached to
>>>>>>> /dev/ttyUSB0, but same issue.
>>>>>>>
>>>>>>> rabbit@ganymede:/dev$ dmesg | grep tty
>>>>>>>
>>>>>>> [ 0.108543] printk: console [tty0] enabled
>>>>>>>
>>>>>>> [ 0.396294] 00:05: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is
>>>>>>> a 16550A
>>>>>>>
>>>>>>> [ 0.418318] 0000:00:16.3: ttyS4 at I/O 0xf0e0 (irq = 19, base_baud =
>>>>>>> 115200) is a 16550A
>>>>>>>
>>>>>>> [ 9667.132474] usb 1-1.1.3: FTDI USB Serial Device converter now
>>>>>>> attached to ttyUSB0
>>>>>>>
>>>>>>> [10669.642560] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now
>>>>>>> disconnected from ttyUSB0
>>>>>>>
>>>>>>> [10670.495576] usb 1-1.1.3: FTDI USB Serial Device converter now
>>>>>>> attached to ttyUSB0
>>>>>>>
>>>>>>> Kindly,
>>>>>>>
>>>>>>> Robert
>>>>>>>
>>>>>>> . .. ... ‘...^,^
>>>>>>>
>>>>>>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>>>>>>>
>>>>>>> On Tuesday, April 6th, 2021 at 5:51 PM, Nigel A. Gunn G8IFF/W8IFF
>>>>>>> [email protected]
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Usually /dev/ttyUSB0 unless you already have another serial device
>>>>>>>> already plugged in to a USB port.
>>>>>>>>
>>>>>>>> Go to file manager and look in /dev/ and see what appears and
>>>>>>>> disappears when you plun in and unplug the cable.
>>>>>>>>
>>>>>>>>> On 06/04/2021 17:34 Robert via chirp_users
>>>>>>>>> [email protected]
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> Hello,
>>>>>>>>>
>>>>>>>>> Total noob, here. Taking my exams on Thursday. Got my TIDRADIO UV-5R
>>>>>>>>> and the FTDI cable. How can I detect which /dev/tty is being used for
>>>>>>>>> the FTDI connection to my radio? I tried /dev/ttyS0 and /dev/ttyUSB0
>>>>>>>>> which resulted in the error 'Radio did not respond'.
>>>>>>>>>
>>>>>>>>> Kindly,
>>>>>>>>>
>>>>>>>>> Robert
>>>>>>>>>
>>>>>>>>> . .. ... ‘...^,^
>>>>>>>>>
>>>>>>>>> _______________________________________________ chirp_users mailing
>>>>>>>>> list
>>>>>>>>> [email protected]
>>>>>>>>>
>>>>>>>>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>>>>>>>>> This message was sent to Nigel Gunn, W8IFF at
>>>>>>>>> [email protected]
>>>>>>>>> To unsubscribe, send an email to
>>>>>>>>> [email protected]
>>>>>>>>
>>>>>>>> Nigel A. Gunn, ///shoulders.outwards.resolutions tel +1-937-971-0366
>>>>>>>>
>>>>>>>> Amateur Radio G8IFF W8IFF and GMRS WRBV701, e-mail
>>>>>>>> [email protected]
>>>>>>>> www
>>>>>>>> http://www.ngunn.net
>>>>>>>
>>>>>>> chirp_users mailing list
>>>>>>> [email protected]
>>>>>>>
>>>>>>> http://intrepid.danplanet.com/mailman/listinfo/chirp_users
>>>>>>> This message was sent to Matthew Poletiek at
>>>>>>> [email protected]
>>>>>>> To unsubscribe, send an email to
>>>>>>> [email protected]
Module Size Used by
binfmt_misc 24576 1
rfcomm 81920 4
cmac 16384 3
algif_hash 16384 1
algif_skcipher 16384 1
af_alg 28672 6 algif_hash,algif_skcipher
bnep 24576 2
ipheth 16384 0
nls_iso8859_1 16384 2
snd_hda_codec_hdmi 61440 1
snd_hda_codec_realtek 131072 1
snd_hda_codec_generic 81920 1 snd_hda_codec_realtek
ledtrig_audio 16384 1 snd_hda_codec_generic
intel_rapl_msr 20480 0
snd_hda_intel 53248 3
snd_intel_dspcfg 24576 1 snd_hda_intel
snd_usb_audio 282624 2
mei_hdcp 24576 0
intel_rapl_common 28672 1 intel_rapl_msr
snd_hda_codec 139264 4
snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek
snd_usbmidi_lib 36864 1 snd_usb_audio
x86_pkg_temp_thermal 20480 0
apple_mfi_fastcharge 20480 0
snd_hda_core 94208 5
snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek
intel_powerclamp 20480 0
uvcvideo 98304 0
snd_hwdep 20480 2 snd_usb_audio,snd_hda_codec
coretemp 20480 0
snd_pcm 114688 5
snd_hda_codec_hdmi,snd_hda_intel,snd_usb_audio,snd_hda_codec,snd_hda_core
videobuf2_vmalloc 20480 1 uvcvideo
videobuf2_memops 20480 1 videobuf2_vmalloc
btusb 57344 0
videobuf2_v4l2 24576 1 uvcvideo
crct10dif_pclmul 16384 1
btrtl 24576 1 btusb
snd_seq_midi 20480 0
ghash_clmulni_intel 16384 0
i915 2195456 45
snd_seq_midi_event 16384 1 snd_seq_midi
btbcm 16384 1 btusb
videobuf2_common 57344 2 videobuf2_v4l2,uvcvideo
r8188eu 430080 0
aesni_intel 372736 4
btintel 28672 1 btusb
ftdi_sio 61440 0
snd_rawmidi 36864 2 snd_seq_midi,snd_usbmidi_lib
crypto_simd 16384 1 aesni_intel
bluetooth 581632 31 btrtl,btintel,btbcm,bnep,btusb,rfcomm
lib80211 16384 1 r8188eu
snd_seq 69632 2 snd_seq_midi,snd_seq_midi_event
videodev 241664 3 videobuf2_v4l2,uvcvideo,videobuf2_common
cryptd 24576 3 crypto_simd,ghash_clmulni_intel
ecdh_generic 16384 2 bluetooth
cfg80211 778240 1 r8188eu
ecc 32768 1 ecdh_generic
drm_kms_helper 217088 1 i915
glue_helper 16384 1 aesni_intel
snd_seq_device 16384 3 snd_seq,snd_seq_midi,snd_rawmidi
joydev 24576 0
usbserial 53248 1 ftdi_sio
mc 57344 5
videodev,snd_usb_audio,videobuf2_v4l2,uvcvideo,videobuf2_common
input_leds 16384 0
cec 53248 2 drm_kms_helper,i915
snd_timer 40960 2 snd_seq,snd_pcm
rc_core 57344 1 cec
rapl 20480 0
intel_cstate 20480 0
snd 94208 23
snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_usb_audio,snd_usbmidi_lib,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_pcm,snd_rawmidi
i2c_algo_bit 16384 1 i915
wmi_bmof 16384 0
at24 24576 0
fb_sys_fops 16384 1 drm_kms_helper
syscopyarea 16384 1 drm_kms_helper
soundcore 16384 1 snd
sysfillrect 16384 1 drm_kms_helper
mei_me 40960 1
sysimgblt 16384 1 drm_kms_helper
mei 106496 3 mei_hdcp,mei_me
mac_hid 16384 0
sch_fq_codel 20480 7
parport_pc 45056 0
ppdev 24576 0
lp 20480 0
parport 65536 3 parport_pc,lp,ppdev
drm 552960 12 drm_kms_helper,i915
ip_tables 32768 0
x_tables 49152 1 ip_tables
autofs4 45056 2
uas 28672 0
usb_storage 73728 2 uas
hid_logitech_hidpp 45056 0
hid_logitech_dj 28672 0
hid_generic 16384 0
usbhid 57344 1 hid_logitech_dj
hid 135168 4
usbhid,hid_generic,hid_logitech_dj,hid_logitech_hidpp
crc32_pclmul 16384 0
ahci 40960 2
e1000e 262144 0
i2c_i801 32768 0
libahci 36864 1 ahci
xhci_pci 20480 0
i2c_smbus 20480 1 i2c_i801
lpc_ich 24576 0
xhci_pci_renesas 20480 1 xhci_pci
wmi 32768 1 wmi_bmof
video 49152 1 i915
107
[ 512.635800] usb 1-1.1.3: FTDI USB Serial Device converter now attached to
ttyUSB0
rabbit@ganymede:~$ sudo tail -f /var/log/syslog
Apr 7 15:05:54 ganymede kernel: [16883.564052] usb 1-1.1.3: USB disconnect,
device number 6
Apr 7 15:05:54 ganymede kernel: [16883.564390] ftdi_sio ttyUSB0: FTDI USB
Serial Device converter now disconnected from ttyUSB0
Apr 7 15:05:54 ganymede kernel: [16883.564433] ftdi_sio 1-1.1.3:1.0: device
disconnected
Apr 7 15:06:05 ganymede kernel: [16894.564209] usb 1-1.1.3: new full-speed USB
device number 8 using ehci-pci
Apr 7 15:06:05 ganymede kernel: [16894.703346] usb 1-1.1.3: New USB device
found, idVendor=0403, idProduct=6001, bcdDevice= 6.00
Apr 7 15:06:05 ganymede kernel: [16894.703349] usb 1-1.1.3: New USB device
strings: Mfr=1, Product=2, SerialNumber=3
Apr 7 15:06:05 ganymede kernel: [16894.703351] usb 1-1.1.3: Product: FT232R
USB UART
Apr 7 15:06:05 ganymede kernel: [16894.703353] usb 1-1.1.3: Manufacturer: FTDI
Apr 7 15:06:05 ganymede kernel: [16894.703354] usb 1-1.1.3: SerialNumber:
AD0K6AOG
Apr 7 15:06:05 ganymede kernel: [16894.706527] ftdi_sio 1-1.1.3:1.0: FTDI USB
Serial Device converter detected
Apr 7 15:06:05 ganymede kernel: [16894.706563] usb 1-1.1.3: Detected FT232RL
Apr 7 15:06:05 ganymede kernel: [16894.707460] usb 1-1.1.3: FTDI USB Serial
Device converter now attached to ttyUSB0
Apr 7 15:06:05 ganymede mtp-probe: checking bus 1, device 8:
"/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1.3"
Apr 7 15:06:05 ganymede mtp-probe: bus: 1, device: 8 was not an MTP device
Apr 7 15:06:05 ganymede snapd[1017]: hotplug.go:199: hotplug device add event
ignored, enable experimental.hotplug
Apr 7 15:06:05 ganymede mtp-probe: checking bus 1, device 8:
"/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1.3"
Apr 7 15:06:05 ganymede mtp-probe: bus: 1, device: 8 was not an MTP device
Apr 7 15:06:06 ganymede wpa_supplicant[1031]: wlx34e89466bba6: WPA: Group
rekeying completed with 1c:bf:ce:01:cf:80 [GTK=CCMP]
Apr 7 15:06:08 ganymede ModemManager[1098]: <info> Couldn't check support for
device '/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1.3': not
supported by any plugin
Apr 7 15:07:11 ganymede systemd[1]: Starting Refresh fwupd metadata and update
motd...
Apr 7 15:07:11 ganymede dbus-daemon[996]: [system] Activating via systemd:
service name='org.freedesktop.fwupd' unit='fwupd.service' requested by ':1.199'
(uid=62803 pid=13312 comm="/usr/bin/fwupdmgr refresh --no-metadata-check "
label="unconfined")
Apr 7 15:07:11 ganymede systemd[1]: Starting Firmware update daemon...
Apr 7 15:07:11 ganymede fwupd[13315]: 19:07:11:0578 FuPluginUefi
kernel efivars support missing: /sys/firmware/efi/efivars
Apr 7 15:07:11 ganymede fwupd[13315]:
ERROR:sys:src/tss2-sys/api/Tss2_Sys_Execute.c:114:Tss2_Sys_ExecuteFinish()
Unsupported device. The device is a TPM 1.2
Apr 7 15:07:11 ganymede fwupd[13315]:
ERROR:esys:src/tss2-esys/api/Esys_Startup.c:216:Esys_Startup_Finish() Received
a non-TPM Error
Apr 7 15:07:11 ganymede fwupd[13315]:
ERROR:esys:src/tss2-esys/api/Esys_Startup.c:78:Esys_Startup() Esys Finish
ErrorCode (0x00080001)
Apr 7 15:07:11 ganymede fwupd[13315]: 19:07:11:0810 FuEngine
failed to add udev device /sys/devices/pnp0/00:06/tpm/tpm0: failed to
initialize TPM
Apr 7 15:07:11 ganymede fwupd[13315]: 19:07:11:0822 FuEngine
device 602b0a6cc821d155208724f0e22f8d111542b74c [FTM48N325H] does not define a
vendor-id!
Apr 7 15:07:11 ganymede dbus-daemon[996]: [system] Successfully activated
service 'org.freedesktop.fwupd'
Apr 7 15:07:11 ganymede systemd[1]: Started Firmware update daemon.
Apr 7 15:07:11 ganymede systemd[1]: fwupd-refresh.service: Succeeded.
Apr 7 15:07:11 ganymede systemd[1]: Finished Refresh fwupd metadata and update
motd.
_______________________________________________
chirp_users mailing list
[email protected]
http://intrepid.danplanet.com/mailman/listinfo/chirp_users
This message was sent to [email protected] at [email protected]
To unsubscribe, send an email to [email protected]
