开云体育

开云体育

Great !
I've got the image on a 6tb usb drive. I'll just burn it to the ssd and be done. I used Gparted to expand to 256gb drive.
Thanks Cliff

Stan W8SRD

The way I do it to a USB to an SSD is to boot to the SD Card and use the utility in the Accessories menu called SD Card Copier. It just images what's on the SD Card to the SSD. As I recall the SSD doesn't need to be formatted either, but it's been a while. I make backups just going the other way to a SD Card.

73,

Cliff, AE5ZA

On Dec 1, 2023, at 15:30, sdegroff, W8SRD via <sdegroff@...> wrote:

woops, spoke too soon. Now it does not work, again. Even toggling the wayland setting did not work. First time it ran great. guess running off ssd on usb port is the next thing to try. if i can find the one i got somewhere.? When doing that, do you image the whole system to the ssd or do you boot from uSD and install and use the ssd formatted as ext4 and just use the drive for everthing that gets installed?? Not certain about ubuntu file system.

Stan W8SRD

On 11/30/23 23:25, sdegroff, W8SRD via wrote:

FIXED !!!
Installed raspi-config

sudo apt install raspi-config

then run as admin

sudo raspi-config

go to advanced settings
choose to run wayland experimental

done

Xwayland was what was sucking down the processor in the "top" report.
Experimental must include some big changes. ran like a little big computer.
being chased with a knife Hi Hi

On 11/28/23 14:26, Haris SV1GRB wrote:

I tried Fldigi on my Raspberry Pi 5 with the last version of Raspberry Pi OS (bookworm).
This version use Wayland (like the Ubuntu version you tried) as default instead of X11.
From the release notes:

* Desktop now runs on the Wayfire Wayland compositing window manager on Raspberry Pi 4 and 5 platforms; on X11 using the openbox window manager on older platforms
* lxpanel replaced with new wf-panel-pi application when running Wayland; existing lxpanel plugins migrated; gpu performance and power plugins added

I also noticed a slow response when the waterfall was drawing something and the Xwayland process was using a lot of resources.
I tried switching to X11 using the Advanced settings in the raspi-config tool and Fldigi was happy again.

I suppose that the Wayland implementation is too new.

73
Haris
SV1GRB

-- 
Remember this: The Government does NOT have any money of their own – they only have what they take from YOU! Choose your government wisely.

-- 
Remember this: The Government does NOT have any money of their own – they only have what they take from YOU! Choose your government wisely.

<sdegroff.vcf>

-- 
Remember this: The Government does NOT have any money of their own – they only have what they take from YOU! Choose your government wisely.

开云体育

The way I do it to a USB to an SSD is to boot to the SD Card and use the utility in the Accessories menu called SD Card Copier. It just images what's on the SD Card to the SSD. As I recall the SSD doesn't need to be formatted either, but it's been a while. I make backups just going the other way to a SD Card.

开云体育

woops, spoke too soon. Now it does not work, again. Even toggling the wayland setting did not work. First time it ran great. guess running off ssd on usb port is the next thing to try. if i can find the one i got somewhere.? When doing that, do you image the whole system to the ssd or do you boot from uSD and install and use the ssd formatted as ext4 and just use the drive for everthing that gets installed?? Not certain about ubuntu file system.

Stan W8SRD

FIXED !!!
Installed raspi-config

sudo apt install raspi-config

then run as admin

sudo raspi-config

go to advanced settings
choose to run wayland experimental

done

Xwayland was what was sucking down the processor in the "top" report.
Experimental must include some big changes. ran like a little big computer.
being chased with a knife Hi Hi

On 11/28/23 14:26, Haris SV1GRB wrote:

I tried Fldigi on my Raspberry Pi 5 with the last version of Raspberry Pi OS (bookworm).
This version use Wayland (like the Ubuntu version you tried) as default instead of X11.
From the release notes:

* Desktop now runs on the Wayfire Wayland compositing window manager on Raspberry Pi 4 and 5 platforms; on X11 using the openbox window manager on older platforms
* lxpanel replaced with new wf-panel-pi application when running Wayland; existing lxpanel plugins migrated; gpu performance and power plugins added

I also noticed a slow response when the waterfall was drawing something and the Xwayland process was using a lot of resources.
I tried switching to X11 using the Advanced settings in the raspi-config tool and Fldigi was happy again.

I suppose that the Wayland implementation is too new.

73
Haris
SV1GRB

-- 
Remember this: The Government does NOT have any money of their own – they only have what they take from YOU! Choose your government wisely.

-- 
Remember this: The Government does NOT have any money of their own – they only have what they take from YOU! Choose your government wisely.

开云体育

James,

开云体育

?

开云体育

FIXED !!!
Installed raspi-config

sudo apt install raspi-config

then run as admin

sudo raspi-config

go to advanced settings
choose to run wayland experimental

done

Xwayland was what was sucking down the processor in the "top" report.
Experimental must include some big changes. ran like a little big computer.
being chased with a knife Hi Hi

I tried Fldigi on my Raspberry Pi 5 with the last version of Raspberry Pi OS (bookworm).
This version use Wayland (like the Ubuntu version you tried) as default instead of X11.
From the release notes:

* Desktop now runs on the Wayfire Wayland compositing window manager on Raspberry Pi 4 and 5 platforms; on X11 using the openbox window manager on older platforms
* lxpanel replaced with new wf-panel-pi application when running Wayland; existing lxpanel plugins migrated; gpu performance and power plugins added

I also noticed a slow response when the waterfall was drawing something and the Xwayland process was using a lot of resources.
I tried switching to X11 using the Advanced settings in the raspi-config tool and Fldigi was happy again.

I suppose that the Wayland implementation is too new.

73
Haris
SV1GRB

-- 
Remember this: The Government does NOT have any money of their own – they only have what they take from YOU! Choose your government wisely.

I have the latest linux mint, installed wine, and CwSkimmer seems to be running just fine....EXCEPT
The only Audio I/O device it lets me select is '01 Pulseaudio' and that seems to be incorrect as my scrolling window shows nothing,

My soundcard is the digirig plugged into my G90 and WSJTX works fine so I know there is radio audio in the linux system.

Is there anything I can do to see the CW waveforms scroll, or is it futile under wine on Linux?

Thanks,
Larry

On Thu, 30 Nov 2023 12:33:29 -0600
"Dave, W1HKJ" <w1hkj@...> wrote:

Brian,

Apply the attached patch (or wait for next source release / push to
Source Forge)

Dave

Thanks, that nailed it. Luckily it was a fairly small change.

--

Brian G8SEZ

开云体育

Brian,

Apply the attached patch (or wait for next source release / push to Source Forge)

Dave

On Thu, 30 Nov 2023 11:05:47 -0600
"Dave, W1HKJ" <w1hkj@...> wrote:

at


Index of /alpha/fldigi

* Parent Directory <>
* fldigi-4.2.03.08.tar.gz
<>

FYI Dave there is a newly created 'feature' in hamlib-4.6~git that
caused some problems with compilation in freedv. It seems to be the
same with fldigi:


rigcontrol/hamlib.cxx: In function ‘void hamlib_get_rigs()’:
rigcontrol/hamlib.cxx:608:26: error: invalid conversion from ‘int (*)(const rig_caps*, void*)’ to ‘int (*)(rig_caps*, void*)’ [-fpermissive]
608 | rig_list_foreach(add_to_list, 0);
| ^~~~~~~~~~~
| |
| int (*)(const rig_caps*, void*)
In file included from ./include/rigclass.h:27,
from ./include/main.h:36,
from ./include/squelch_status.h:31,
from ./include/status.h:29,
from ./include/nanoIO.h:42,
from ./include/confdialog.h:388,
from rigcontrol/hamlib.cxx:34:
/usr/include/hamlib/rig.h:3690:18: note: initializing argument 1 of ‘int rig_list_foreach(int (*)(rig_caps*, void*), void*)’
3690 | rig_list_foreach HAMLIB_PARAMS((int (*cfunc)(struct rig_caps *, rig_ptr_t),
| ^~~~~~~~~~~~~
make[3]: *** [Makefile:5610: rigcontrol/fldigi-hamlib.o] Error 1
make[3]: *** Waiting for unfinished jobs....
make[3]: Leaving directory '/home/bdm/rpmbuild/BUILD/fldigi-4.2.03.08/src'
make[2]: *** [Makefile:8792: all-recursive] Error 1
make[2]: Leaving directory '/home/bdm/rpmbuild/BUILD/fldigi-4.2.03.08/src'
make[1]: *** [Makefile:2033: all] Error 2
make[1]: Leaving directory '/home/bdm/rpmbuild/BUILD/fldigi-4.2.03.08/src'
make: *** [Makefile:471: all-recursive] Error 1


The freedv PR here:



may describe the same reason and provide enough information to add a fix
to fl* apps.

HTH

--

Brian G8SEZ

开云体育

at

Index of /alpha/fldigi

commit d33ab81d900326932dd918d0c453017b55c59fb2
Author: dave-w1hkj <w1hkj@...>
Date:   Thu Nov 30 09:31:00 2023 -0600

    alpha

commit 69311d7c9efcf14cdbf4f7706cdd07e4c09599e0
Author: Michael Black <mdblack98@...>
Date:   Thu Nov 30 09:28:48 2023 -0600

    FMT zombie
    
      * fix potential thread zombie if FMT modem shut down
        during a log write
      * added Mike to list of developers in About dialog

commit 9561c358b214f4ed46e25037e631137bb5f71b96
Author: dave-w1hkj <w1hkj@...>
Date:   Sat Nov 25 10:38:47 2023 -0600

    Squelch Macro tags
    
      * Add
            <SQL:on|off|t>       Digital Squelch on, off,toggle
            <SQLCH:nnn>          Digital Squelch level, 0..100

commit 1b164deec6279e6b3748be459125ab8adf4b3aa2
Author: dave-w1hkj <w1hkj@...>
Date:   Mon Nov 20 15:53:23 2023 -0600

    PO files
    
      * Add Catalan ca.po
      * Update Greek el.po

commit 90b760997f493d741a6fd1d12a2910a5d1f29c59
Author: dave-w1hkj <w1hkj@...>
Date:   Sat Nov 18 13:27:08 2023 -0600

    CLRLOG LOG LNW
    
      * Correct macro functions

commit fdb9fc8827b37583911a25e5392f2ea7b976a46f
Author: dave-w1hkj <w1hkj@...>
Date:   Sun Nov 12 08:08:23 2023 -0600

    JTSDK build
    
      * changes required for building in mingw JTSDK environment

commit 2e5db4f16a89b551e44b43d03961e88e89964b11
Author: dave-w1hkj <w1hkj@...>
Date:   Tue Nov 7 10:40:03 2023 -0600

    metar report
    
      * add unprocessed ob: line as a report option

commit 80882af1319a745754d5b66bd3ddd8ca6c94bb20
Author: dave-w1hkj <w1hkj@...>
Date:   Thu Nov 9 14:21:41 2023 -0600

    Log fields
    
      * add MY_STATE
      * trim leading/trailing blanks
      * add UK counties to counties list
      * changed short form to blank when NIL selected for state
      * store fldigi version number in SQSO.txt file
        . regenerate list from internal string if version number
          does not match with executing binary

commit 49b38e31d59c960a0c6921a6a72b2de26908c86f
Author: dave-w1hkj <w1hkj@...>
Date:   Tue Oct 31 21:53:19 2023 -0500

    Version 4.2.03


73, David, W1HKJ

You should see what we see on 40m and 20m over hear re FT8/JS8 "QRM" leaching over other band segments a lot of the time.

Evidence of harmonic distortion in the TX audio stages, as often two or three copies of the original signal are seen but correspondingly wider per harmonic number!

And I still see digimode fans inline saying "Just hook up your PC's Line Out to the rig Mic input, and your done."? With absolutely no mention of any form of passive attenuator to bring the "Line" level down to "Mic" level for the radio.? (Let alone, if the rig has an ACC port with a TX/RX audio I/O, to use that, as the levels are usually more compatible with computer sound card I/O levels...

And many of those are sporting call-signs that indicate they are not novices...

Oddly, many report having to attenuate the Radio's output, to prevent overloading the PC's Sound input, but absolutely no hint of realisation that might indicate they should address the TX path likewise...

If one attempts to give polite advice re attenuators, one gets shot down in flames.

The result on air is all too predictable.? And is also mostly the FT8/FT4 "instant gratification" crowd? Sigh...

There also seems to be a trend of running PSK at high power, with some spectacular (In a bad way) IMD as a result.
The worst I've seen, Fldigi reported -7dB? And that signal was not more than S5 with me.? Other stronger signals were clean, so not my RX.

73.

Dave G0WBX.



--
Sent from a MicroSoft free zone:

I just finished drafting a set of custom forms for use with flmsg (v4.0.17).? The forms were constructed using an external CSS reference (<link rel="stylesheet" href="mycss.css"> inside the HTML document <head> section) where the file "mycss.css" was placed in the ~/.nbems/CUSTOM/ folder alongside the custom form .html files (Linux OS).? When I attempt to edit or view the custom forms from flmsg, the default web browser opens and eventually loads the .html page, but the CSS file is not loaded.? Is there a different location where I should place the CSS file to have it load with the custom form file?
73,
Kurt
KE7KUS

开云体育

There is a flrig.prefs and a rig.prefs the radio name.prefs is it starts and gets setup. It's created on the first exit so it you're hanging and completing a normal setup and close down then no rig.prefs.