m wrote:
> > Message: 2
> > Date: Sun, 13 Jan 2019 19:52:59 -0700
> > From:
> > Subject: Re: [chirp_users] Possibly Bad USB to radio cable
> > To: "'Discussion of CHIRP'"
> > Message-ID: <008601d4abb4$4407c590$cc1750b0$@elp.rr.com>
&g
From:
> Subject: Re: [chirp_users] Possibly Bad USB to radio cable
> To: "'Discussion of CHIRP'"
> Message-ID: <008601d4abb4$4407c590$cc1750b0$@elp.rr.com>
> Content-Type: text/plain; charset="utf-8"
>
> Completely true. Sadly, Linux will not d
: chirp_users-boun...@intrepid.danplanet.com
On Behalf Of Tom Henderson
Sent: Sunday, January 13, 2019 5:52 AM
To: chirp_users@intrepid.danplanet.com
Subject: Re: [chirp_users] Possibly Bad USB to radio cable
For those fortunate enough to have Linux, this whole conversation is moot.
Tom
un...@intrepid.danplanet.com>
<mailto:chirp_users-boun...@intrepid.danplanet.com> *On Behalf Of
*Christopher Knowles
*Sent:* Saturday, January 12, 2019 9:08 PM
*To:* chirp_users@intrepid.danplanet.com
<mailto:chirp_users@intrepid.danplanet.com>
*Subject:* Re: [c
t;> The canyons are calling, colorful and deep. But I have promises to keep.
>>
>> And miles to go still in my Jeep... And miles to go still in my Jeep...
>>
>>
>>
>> [image: Big Bend JEEP Rear]
>>
>>
>>
>>
>>
>>
>>
>> *
>
>
>
>
>
>
>
> *From:* chirp_users-boun...@intrepid.danplanet.com
>
> *On Behalf Of *Christopher
> Knowles
> *Sent:* Saturday, January 12, 2019 9:08 PM
> *To:* chirp_users@intrepid.danplanet.com
> *Subject:* Re: [chirp_users] Possibly Bad USB to radio cable
&
@intrepid.danplanet.com
*Subject:* Re: [chirp_users] Possibly Bad USB to radio cable
Beware that Microsoft just downloaded a new version of Windows 10 to
all computers running it. Unless you have told your Windows software
not to update it, it has downloaded a new "Prolific" driver which will
...
From: chirp_users-boun...@intrepid.danplanet.com
On Behalf Of Christopher Knowles
Sent: Saturday, January 12, 2019 9:08 PM
To: chirp_users@intrepid.danplanet.com
Subject: Re: [chirp_users] Possibly Bad USB to radio cable
Beware that Microsoft just downloaded a new version of Windows 10 to
I mostly run Linux, but I tried CHIRP under Windows.
It doesn't work on either.
Thanks for the info on Prolific driver, my USB cable doesn't use that chip.
I think it is the radio.
73
David N1EA
___
chirp_users mailing list
chirp_users@intrepid.danpla
Beware that Microsoft just downloaded a new version of Windows 10 to all
computers running it. Unless you have told your Windows software not to
update it, it has downloaded a new "Prolific" driver which will not work
and hence its's not your cable but your driver. Go to Miklor. There
they w
No, : Silicon Labs.
I sent more info in a separate email.
Plus I said I was using both Win10 and Linux. Linux never has given
me driver problems!
73
DR
N1EA
On Sat, Jan 12, 2019 at 10:37 PM Jardy via chirp_users
wrote:
>
> Check Device Manager and see if the cable shows to be a Prolific. If i
Check Device Manager and see if the cable shows to be a Prolific. If it is,
roll your driver back to 3.2.0.0. See www.miklor.com for more info on this.
Jardy Dawson WA7JRD
Message sent through sub space hailing frequencies using the Universal
Translator.
> On Jan 12, 2019, at 19:22, D.J.J. R
When I plug in the cable I get this in dmesg | tail:
]$ sudo dmesg | tail
[ 773.851772] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0
[ 773.851833] cp210x 1-1:1.0: device disconnected
[ 780.717963] usb 1-1: new full-speed USB device number 7 using xhci_hcd
[ 780.860262] usb 1-
Hi,
I have a Wouxun red colored cable, suddenly it no longer works. I
have the Wouxun Windows programming software: Doesn't communicate
with radio. CHIRP on Win10 and Arch Linux: Same problem, radio
doesn't respond.
It used to work, now suddenly it doesn't work!
Is there some way I can check
14 matches
Mail list logo
