Re: [chirp_users] chirp_users Digest, Vol 109, Issue 2
Hi.
Other than for software that just isn't available for anything other than Windows, there is no reason whatsoever to try to use WINE to run Chirp under Linux.
Just go to:- https://chirp.danplanet.com/projects/chirp/wiki/Download
And follow the instructions how to get the version you need for your OS.
There is even a "Live CD" (bootable self contained system) version!
As well as the ability to run it directly from a "tarball" file once the contents are extracted.
https://chirp.danplanet.com/projects/chirp/wiki/Running_Under_Linux
I do have some Windows specific programs that I need to use, that do run well under WINE, but sadly the DMR codeplug software from Motorola will not install, as the installer needs .NET version whatever, and the Mono equivalent tools are not compatible.
All my other radio programming and configuring needs are happily done via Chirp running natively under Linux.
As to the serial port issue, it's a "symbolic link" that you create, that in effect redirects references to (for example) COM1: to /dev/ttyUSB0 Job done. As you say, instructions are available how to do that from many sources.
I would also dispute the assumption re the probably low importance of the handshake lines. Many radio's use them to enter programming mode, enable some esoteric mode, and/or exit from such modes.
It is best to use the version of Chirp, that is natively configured for your OS, rather than try to bludgeon it into working via an abstraction layer, that can itself impose "other feature" you may not want..
73.
Dave G0WBX.
On 02/01/18 20:00, chirp_users-request@intrepid.danplanet.com wrote:
From: Tom Consodine ND5Y nd5y@yahoo.com Subject: [chirp_users] USB serial ports and Linux/WINE To: chirp_users@intrepid.danplanet.com Message-ID: 7d46aaec-b155-f3f6-6697-f339bb204881@yahoo.com Content-Type: text/plain; charset=utf-8; format=flowed
I have no problems using USB serial ports with Windows software running on Linux/WINE. One of the reasons I switched to Linux was one USB cable I have would work on Windows 7 but not on Windows 10.
You have to configure the serial port permissions in Linux. There are instructions for doing that on the Chirp web site.
If you are using WINE 2.8 or later you might have to configure the port settings in WINE or manually make a "registry" key. There are instructions for doing that on their web site at
https://wiki.winehq.org/index.php?title=Wine_User%27s_Guide&oldid=2519#S...
Versions before that only require making a link in the wine folder to the port.
Older versions of WINE before about 1.7 don't support all the RS-232 lines. This probably isn't an issue for radio programming cables that only use TXD and RXD lines but it is if you need the RTS, CTS, DTR, DSR lines to work properly.
Dave, I hereby nominate your reply for the 2018 Chirp list hall of fame. Expect-level advice, yet lighthearted and fun to read. Two thumbs up with five stars on top.
On January 3, 2018 4:16:41 AM MST, Dave B g8kbv@uku.co.uk wrote:
Hi.
Other than for software that just isn't available for anything other than Windows, there is no reason whatsoever to try to use WINE to run Chirp under Linux.
Just go to:- https://chirp.danplanet.com/projects/chirp/wiki/Download
And follow the instructions how to get the version you need for your OS.
There is even a "Live CD" (bootable self contained system) version!
As well as the ability to run it directly from a "tarball" file once the contents are extracted.
https://chirp.danplanet.com/projects/chirp/wiki/Running_Under_Linux
I do have some Windows specific programs that I need to use, that do run well under WINE, but sadly the DMR codeplug software from Motorola will not install, as the installer needs .NET version whatever, and the Mono equivalent tools are not compatible.
All my other radio programming and configuring needs are happily done via Chirp running natively under Linux.
As to the serial port issue, it's a "symbolic link" that you create, that in effect redirects references to (for example) COM1: to /dev/ttyUSB0 Job done. As you say, instructions are available how to do that from many sources.
I would also dispute the assumption re the probably low importance of the handshake lines. Many radio's use them to enter programming mode, enable some esoteric mode, and/or exit from such modes.
It is best to use the version of Chirp, that is natively configured for your OS, rather than try to bludgeon it into working via an abstraction layer, that can itself impose "other feature" you may not want..
Dave G0WBX.
On 02/01/18 20:00, chirp_users-request@intrepid.danplanet.com wrote:
From: Tom Consodine ND5Y nd5y@yahoo.com Subject: [chirp_users] USB serial ports and Linux/WINE To: chirp_users@intrepid.danplanet.com Message-ID: 7d46aaec-b155-f3f6-6697-f339bb204881@yahoo.com Content-Type: text/plain; charset=utf-8; format=flowed
I have no problems using USB serial ports with Windows software
running
on Linux/WINE. One of the reasons I switched to Linux was one USB
cable
I have would work on Windows 7 but not on Windows 10.
You have to configure the serial port permissions in Linux. There are
instructions for doing that on the Chirp web site.
If you are using WINE 2.8 or later you might have to configure the
port
settings in WINE or manually make a "registry" key. There are instructions for doing that on their web site at
https://wiki.winehq.org/index.php?title=Wine_User%27s_Guide&oldid=2519#S...
Versions before that only require making a link in the wine folder to
the port.
Older versions of WINE before about 1.7 don't support all the RS-232 lines. This probably isn't an issue for radio programming cables that
only use TXD and RXD lines but it is if you need the RTS, CTS, DTR,
DSR
lines to work properly.
I agree, that was very good. Indeed I can see going the other way and running chirp in a linux VM on windows, but not under wine, defeats the whole thing.
Chirp + Linux, to me the only way to go...
By way for the one who recommended Dale Farnsworth's DM-380 software it works great, very smooth and well behaved. It does toss some errors that are caused by the radio programming but you just ignore them and press on.
Now with Chirp for my analog radios and Editcp for the DM-380 I am smoking!! Errr forgot the ID-5100, perhaps someday that will get sorted out.
On Wed, Jan 3, 2018 at 8:29 AM, Jeff wireless3.14159@gmail.com wrote:
Dave, I hereby nominate your reply for the 2018 Chirp list hall of fame. Expect-level advice, yet lighthearted and fun to read. Two thumbs up with five stars on top.
On January 3, 2018 4:16:41 AM MST, Dave B g8kbv@uku.co.uk wrote:
Hi.
Other than for software that just isn't available for anything other than Windows, there is no reason whatsoever to try to use WINE to run Chirp under Linux.
Just go to:- https://chirp.danplanet.com/projects/chirp/wiki/Download
And follow the instructions how to get the version you need for your OS.
There is even a "Live CD" (bootable self contained system) version!
As well as the ability to run it directly from a "tarball" file once the contents are extracted.
https://chirp.danplanet.com/projects/chirp/wiki/Running_Under_Linux
I do have some Windows specific programs that I need to use, that do run well under WINE, but sadly the DMR codeplug software from Motorola will not install, as the installer needs .NET version whatever, and the Mono equivalent tools are not compatible.
All my other radio programming and configuring needs are happily done via Chirp running natively under Linux.
As to the serial port issue, it's a "symbolic link" that you create, that in effect redirects references to (for example) COM1: to /dev/ttyUSB0 Job done. As you say, instructions are available how to do that from many sources.
I would also dispute the assumption re the probably low importance of the handshake lines. Many radio's use them to enter programming mode, enable some esoteric mode, and/or exit from such modes.
It is best to use the version of Chirp, that is natively configured for your OS, rather than try to bludgeon it into working via an abstraction layer, that can itself impose "other feature" you may not want..
Dave G0WBX.
On 02/01/18 20:00, chirp_users-request@intrepid.danplanet.com wrote:
From: Tom Consodine ND5Y nd5y@yahoo.com nd5y@yahoo.com Subject: [chirp_users] USB serial ports and Linux/WINE To: chirp_users@intrepid.danplanet.com Message-ID: 7d46aaec-b155-f3f6-6697-f339bb204881@yahoo.com 7d46aaec-b155-f3f6-6697-f339bb204881@yahoo.com Content-Type: text/plain; charset=utf-8; format=flowed
I have no problems using USB serial ports with Windows software running on Linux/WINE. One of the reasons I switched to Linux was one USB cable I have would work on Windows 7 but not on Windows 10.
You have to configure the serial port permissions in Linux. There are instructions for doing that on the Chirp web site.
If you are using WINE 2.8 or later you might have to configure the port settings in WINE or manually make a "registry" key. There are instructions for doing that on their web site at https://wiki.winehq.org/index.php?title=Wine_User%27s_Guide&oldid=2519#S...
Versions before that only require making a link in the wine folder to the port.
Older versions of WINE before about 1.7 don't support all the RS-232 lines. This probably isn't an issue for radio programming cables that only use TXD and RXD lines but it is if you need the RTS, CTS, DTR, DSR lines to work properly.
chirp_users mailing list chirp_users@intrepid.danplanet.com http://intrepid.danplanet.com/mailman/listinfo/chirp_users This message was sent to Chuck Hast at kp4djt@gmail.com To unsubscribe, send an email to chirp_users-unsubscribe@ intrepid.danplanet.com
I meant expert-level advice. Sheesh.
On January 3, 2018 7:29:59 AM MST, Jeff wireless3.14159@gmail.com wrote:
Dave, I hereby nominate your reply for the 2018 Chirp list hall of fame. Expect-level advice, yet lighthearted and fun to read. Two thumbs up with five stars on top.
On January 3, 2018 4:16:41 AM MST, Dave B g8kbv@uku.co.uk wrote:
Hi.
Other than for software that just isn't available for anything other than Windows, there is no reason whatsoever to try to use WINE to run Chirp under Linux.
Just go to:- https://chirp.danplanet.com/projects/chirp/wiki/Download
And follow the instructions how to get the version you need for your OS.
There is even a "Live CD" (bootable self contained system) version!
As well as the ability to run it directly from a "tarball" file once the contents are extracted.
https://chirp.danplanet.com/projects/chirp/wiki/Running_Under_Linux
I do have some Windows specific programs that I need to use, that do run well under WINE, but sadly the DMR codeplug software from Motorola
will
not install, as the installer needs .NET version whatever, and the
Mono
equivalent tools are not compatible.
All my other radio programming and configuring needs are happily done via Chirp running natively under Linux.
As to the serial port issue, it's a "symbolic link" that you create, that in effect redirects references to (for example) COM1: to /dev/ttyUSB0 Job done. As you say, instructions are available how to do that from many sources.
I would also dispute the assumption re the probably low importance of the handshake lines. Many radio's use them to enter programming mode, enable some esoteric mode, and/or exit from such modes.
It is best to use the version of Chirp, that is natively configured
for
your OS, rather than try to bludgeon it into working via an
abstraction
layer, that can itself impose "other feature" you may not want..
Dave G0WBX.
On 02/01/18 20:00, chirp_users-request@intrepid.danplanet.com wrote:
From: Tom Consodine ND5Y nd5y@yahoo.com Subject: [chirp_users] USB serial ports and Linux/WINE To: chirp_users@intrepid.danplanet.com Message-ID: 7d46aaec-b155-f3f6-6697-f339bb204881@yahoo.com Content-Type: text/plain; charset=utf-8; format=flowed
I have no problems using USB serial ports with Windows software
running
on Linux/WINE. One of the reasons I switched to Linux was one USB
cable
I have would work on Windows 7 but not on Windows 10.
You have to configure the serial port permissions in Linux. There
are
instructions for doing that on the Chirp web site.
If you are using WINE 2.8 or later you might have to configure the
port
settings in WINE or manually make a "registry" key. There are instructions for doing that on their web site at
https://wiki.winehq.org/index.php?title=Wine_User%27s_Guide&oldid=2519#S...
Versions before that only require making a link in the wine folder
to
the port.
Older versions of WINE before about 1.7 don't support all the RS-232
lines. This probably isn't an issue for radio programming cables
that
only use TXD and RXD lines but it is if you need the RTS, CTS, DTR,
DSR
lines to work properly.
participants (3)
-
Chuck Hast -
Dave B -
Jeff