Hi Eric,
Thanks for pointing me this way, although it seems I am not auto configuring a
module for ttyUSB0. I am attaching the output of
> lsmod | sed -n 'p;$=' > lsmod-count.txt
Where the last line is a line count. There is no changes in this output between
having the phoe unplugged versus plugged, so perhaps that is an indicator that
auto-config of a module to talk to the radio is misfiring. I dunno. Is this
where modprobe comes in? What module name should I install for Chirp managing
traffic over ttyUSB0?
Thanks!
Robert
On 4/6/21 9:04 PM, Eric Oyen via chirp_users wrote:
> Well,
> It does depend on the GUI. There is actually a control panel of sorts if you
> use Unity or gnome as your desktop. Under there will be a number of “applets”
> for hardware configuration. This was the gnome project idea of mimicking a
> windows interface as well as it’s control panel. However, it is sometimes not
> as useful as being able to troubleshoot and add/remove devices from the CLI.
> One should look up lsmod as well as modprobe and Insmod. If things are
> working correctly, new devices will always appear in the /dev directory and
> may even have some sort of “magic number” associated with them. That’s an
> advanced idea and shouldn’t really be of concern for this discussion.
>
> Now, if you use the “Lsmod” command (not capitalized, as my stupid
> autocorrect is trying to change it) before you plug in the usb cable, you
> should see a list of modules and what they do. After plugging in the cable
> that connects to your radio, and doing the same command, you should see 1 or
> more new modules loaded. Those modules will be associated with new devices
> that show up under /dev. Now, they may be listed as TTYS0 or TTYS1, etc.
> those would be your comm port entries. ttys0 should be associated with comm
> 1, etc.
>
> Now, if your system is properly configured, then most of this already happens
> in background. However, there may be some cases where you may have to add
> your user account to the appropriate group in order to use the device. There
> are GUI programs for this as well as some CLI commands. Now, some of the
> commands above may require that you use sudo and log into root. 2 items of
> caution here:
> 1. If you are unsure, don’t use sudo
> 2. Sudo is dangerous if you mess up. Only for advanced users! So, be very
> careful if you do have to use it.
>
> As always, read the associated man pages.
>
> DE n7zzt Eric
>
>> On Apr 6, 2021, at 4:24 PM, Al Jones <[email protected]> wrote:
>>
>> It appears as if we have a computer newbie on our hands since he's looking
>> fordevice manageron Ubuntu ... one of you good linux guys want to take him
>> in hand and walk him through?
>> I'm no help, I know a bit about linux but like most of the world I live in
>> windows.
>> //al
>>
>> ------ Original Message ------
>> From: "Matthew Poletiek" <[email protected]>
>> To: "Robert" <[email protected]>; "Discussion of CHIRP"
>> <[email protected]>
>> Sent: Tue 4 6 21 18:20:30
>> Subject: Re: [chirp_users] Download From Radio under Ubuntu 20.04 error
>>
>>> 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](http://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
>>>>> > [email protected]:
>>>>> >
>>>>> > 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
>>>>> >
>>>>> > . .. ... ‘...^,^
>>>>> >
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
_______________________________________________
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]
