Pat Anderson, I would wonder if your
odd setup is creating devices in some strange group instead of
dialout. Mine shows:
wpmills@suzanne1:~$ vdir /dev/tty[SU]*
crw-rw 1 root dialout 4, 64 Dec 6 22:52 /dev/ttyS0
crw-rw 1 root dialout 4, 65 Dec 6
I agree with this, but... On a linux computer I have spent ALL day trying
to figure out day """I""" was doing wrong. Not for one thing, but for
EVERYTHING... I don't need that in my life.
Dennis M. Wage (W9BOQ)
245 Corum Hill Road
Castalian Springs, TN 37031
(615) 310-4242 Cell
(615) 562-5128 Hom
Dunno. Try it and report back with the results.
> On 25 December 2019 at 19:38 "Glenn K 0 L N Y :)"
> wrote:
>
> Does anyone know if it would be bad to add the Chirp repository to the
> ARM Ubuntu Mate running on my Pine64 and then proceed to install it?
> Glenn
>
>
> > >
>
Does anyone know if it would be bad to add the Chirp repository to the ARM
Ubuntu Mate running on my Pine64 and then proceed to install it?
Glenn
- Original Message -
From: Pat Anderson
To: Discussion of CHIRP
Sent: Wednesday, December 25, 2019 6:24 PM
Subject: Re: [chirp_use
For me running Ubuntu (16.04) on a Chromebook under Crouton (which is not a
garden variety setup for sure), and using a cable with a counterfeit chip,
it still "just works." However, even though I am a member of the Dialout
group, I still need to do the "sudo chmod 777 /dev/ttyUSB0" each time. It
For me, and for everybody I know, in Linux it "just simply works." When for
everybody else, it works, perhaps rather than blaming the program or the OS,
maybe you should start thinking, "What am **_I_** doing wrong?"
On December 23, 2019 6:59:27 AM PST, Dennis Wage wrote:
>I once saw posted
