Date   

Re: partition for lubuntu from previous ubuntu

Marty Hartwell
 

Ok one thing is the Ubuntu for Raspberry Pi is different from the Ubuntu linux, at least that is my

understanding. If the Lubuntu isn't designed for the Pi I don't think it will work after it is installed.

Now to your question as asked, you can continue with the load of Lubuntu just like you would with

Ubuntu or Xubuntu, I have used all three. You can used the existing partitioning as configured for

Ubuntu. I personally like separate partitions, Root about 20GB, /home large, and swap. But on a

Pi I let the Raspbian set it up and after it is finished I expand to the whole sd card.

But I haven't tried the Ubuntu load for the Raspberry.


I don't know if this helps but just my observations.


Marty kd8bj


On 10/13/19 8:23 PM, Don - KM4UDX wrote:
So ubuntu was working okay with fldigi and wsjtx. I'd get the occasional lockups, but a reboot and I was good to go.    So, I figured I could try a "lite" OS, and lubuntu looked like a great option. And my problems started there. hahaha.  

At the moment, during the lubuntu install, I'm totally flummoxed on what to do during the lubuntu partitioning process. Given that there is already a partitioning from ubuntu, the lubuntu install recognizes the existing ubuntu partition and stops, and I don't know what to do. 

If I wiped the onboard memory, the lubuntu might consider is a total fresh install and recommend whatever it wanted for partition. Which I would accept and move on. 

Guidance, oh wise ones....

And thanks as always.

Don
km4udx


KD9MDL initial email

Bill Lamm
 

Thank you


Re: partition for lubuntu from previous ubuntu

Don - KM4UDX <dontAy155@...>
 

Dan -- yes, I ended up doing as you suggested. I still had to go through the partition process. Which freeked me out a bit, but you set a fat32 primary with root/efi (or close to that) with a flag of "esp" set, and I made the rest of the space root mounted at the "/".  Then the install worked, and I am using firefox now as I type this. So yeaaaaa.

As for the motivation, under ubuntu, my mouse would freeze, the system would lock, all at random times. So I wanted to try and improve things....

Now I have to get WSJTX and FLDIGI installed on this new lubuntu OS.  If I can get these two apps working, then I will be a happy camper.

So far so good.

Thanks!!!

Don
km4udx


Re: partition for lubuntu from previous ubuntu

Daniel Holmes
 

Personally, I’d get another card and install new other OS fresh. That way you have the other card to fall back on. 

Dan

--
. Please pardon any mispelings or errors.


On Oct 13, 2019, at 7:24 PM, Don - KM4UDX <dontAy155@...> wrote:

So ubuntu was working okay with fldigi and wsjtx. I'd get the occasional lockups, but a reboot and I was good to go.    So, I figured I could try a "lite" OS, and lubuntu looked like a great option. And my problems started there. hahaha.  

At the moment, during the lubuntu install, I'm totally flummoxed on what to do during the lubuntu partitioning process. Given that there is already a partitioning from ubuntu, the lubuntu install recognizes the existing ubuntu partition and stops, and I don't know what to do. 

If I wiped the onboard memory, the lubuntu might consider is a total fresh install and recommend whatever it wanted for partition. Which I would accept and move on. 

Guidance, oh wise ones....

And thanks as always.

Don
km4udx


Re: partition for lubuntu from previous ubuntu

bbillp
 

My first question is ‘WHY’ ?
K6acj


partition for lubuntu from previous ubuntu

Don - KM4UDX <dontAy155@...>
 

So ubuntu was working okay with fldigi and wsjtx. I'd get the occasional lockups, but a reboot and I was good to go.    So, I figured I could try a "lite" OS, and lubuntu looked like a great option. And my problems started there. hahaha.  

At the moment, during the lubuntu install, I'm totally flummoxed on what to do during the lubuntu partitioning process. Given that there is already a partitioning from ubuntu, the lubuntu install recognizes the existing ubuntu partition and stops, and I don't know what to do. 

If I wiped the onboard memory, the lubuntu might consider is a total fresh install and recommend whatever it wanted for partition. Which I would accept and move on. 

Guidance, oh wise ones....

And thanks as always.

Don
km4udx


Re: Raspberry Pi 3 + TNC-Pi issue with serial port

js8call@...
 

Still not solved, always investigating :-(


Re: Fan SHIM for Raspberry Pi

Jeff AE8W
 

While I am currently a lurker, I am following not just because I enjoy the the thrill of victory... and the agony of defeat. Maybe not quite that bad, I hope.

$70 is steep relative to ludicrously mass marketed & produced computer. Maybe if something between 500 to 1000 hams sign up the case price would drop to $2. But the computer cost would be the same

When I am ready, I would buy it. Heat transfer & sinking is not trivial. On the other hand, I do have a few computer fans packed away so one of those sitting the desk blowing air across said cheap computer would probably do the same. Appearance is a little difference. I guess it is all about how you like to see your handiwork? 

-Jeff NE1U


Re: Fan SHIM for Raspberry Pi

David Ranch <dranch@...>
 


Hello James,

While that looks like a very nice case, there is ZERO chance I'm going to buy a $70 case for a $35 computer.  Btw, there are other aluminum heatsink cases out there but this is the first one I've seen that's HATT compatible.

--David
KI6ZHD


On 10/12/2019 01:33 PM, James Johnson wrote:
You are better off to buy an Open Sheild Aluminum case from Ben.
He is working on a top cover that the TNC-Pi will fit under.

Tell him James VE7HJ sent you.


73 VE7HJ


Re: Fan SHIM for Raspberry Pi

James Johnson
 

You are better off to buy an Open Sheild Aluminum case from Ben.
He is working on a top cover that the TNC-Pi will fit under.

Tell him James VE7HJ sent you.


73 VE7HJ


From: "David Ranch" <dranch@...>
To: "RaspberryPi-4-HamRadio" <RaspberryPi-4-HamRadio@groups.io>
Sent: Saturday, October 12, 2019 1:10:03 PM
Subject: Re: [RaspberryPi-4-HamRadio] Fan SHIM for Raspberry Pi


Hey Larry,

Thanks for the comprehensive post!

I've been thinking of buying one of these units too but the use of the I2S pin is a killer for me as I need that bus for the FePi HATT.  So, I guess I'm back to square one trying to find an intelligent fan for the Raspberry Pi.  I'd personally like to see an Rpi cooler that uses a three our four pin fan and I can monitor it's RPM via the I2C bus.  This should be pretty simple using something like a Micrchip EMC2301 ( https://www.mikroe.com/fan-click ) but I haven't found anything that's pre-made and something very small like the Fan SHIM.  I know I could do something like this via an Arduino and I've done something similar showing the RPM on an LCD display but not putting the data into an I2C bus but that's all too "big" and I'm again looking for something just as small as a Fan SHIM.

Maybe someone else on the list has found something like what I'm looking for?

--David
KI6ZHD




On 10/06/2019 10:33 AM, Larry Dighera wrote:
I want to report that the inexpensive Pimoroni FanSHIM performs very
well in preventing the RPi4 from CPU throttling due to excessive heat.
The supplied Python-based software
https://github.com/pimoroni/fanshim-python implements temperature
control of the fan in proportional response to CPU temperature.  If
you prefer a full time daemon to control the fan, that is included as
well.

CONS
Incompatible with I2S HATs.
Booster Header https://shop.pimoroni.com/products/booster-header
required for some GPIO use.
Moving parts.
Button needs a pending GPIO Zero software update.



30mm no-solder, controllable CPU fan with RGB LED and tactile switch
£9.60
https://shop.pimoroni.com/products/fan-shim

Features
30mm 5V DC fan
4,200 RPM
0.05 m3/min air flow
18.6 dB acoustic noise (whisper-quiet)
Friction-fit header
No soldering required
RGB LED (APA102)
Tactile switch
Basic assembly required
Compatible with Raspberry Pi 4 (and 3 B+, 3 A+)
Python library and daemon
Pinout
Kit contains
Fan SHIM PCB
30mm 5V DC fan with JST connector
M2.5 nuts and bolts
Assembly
Assembly is really easy, and will take less than two minutes.

With the component side of the PCB facing upwards, push the two M2.5
bolts through the holes from below, then screw on the first pair of
nuts to secure them and act as spacers.
Push the fan's mounting holes down onto the bolts, with the cable side
of the fan downwards (as pictured) and the text on the fan upwards.
Attach with another two nuts.
Push the fan's JST connector into the socket on Fan SHIM.
Software
Our Python library lets you control the fan (on/off), RGB LED, and
switch. There's a handful of examples to show you how to use each
feature, and a script to install a daemon (a service that runs in the
background) that runs the fan in automatic mode, triggering it on or
off when the CPU reaches a threshold temperature, with a manual
override via the tactile switch.

Tutorial
You can read our Getting Started with Fan SHIM tutorial for a really
detailed guide on assembling Fan SHIM and installing the software,
with photos for each step of the assembly.

Notes
When mounting or detaching the fan, or assembled Fan SHIM, do not push
on the fan itself, as it is liable to break.
Be careful to mount your Fan SHIM on the correct pins on your Pi, with
the Pi shut down and power disconnected. Shifting it left by one pin
or down a full row of pins could cause damage to both the Fan SHIM and
the Pi. Check out the photos in our tutorial if you're not sure.
?Not heatsink-compatible!
Because Fan SHIM uses pin BCM18 to control the fan, and this pin is
also used by I2S audio devices, you won't be able to use I2S DACs like
pHAT DAC, pHAT BEAT, and the IQAudio boards at the same time as Fan
SHIM
Dimensions: 45x39x11mm


Benchmarking the Raspberry Pi 4
https://medium.com/@ghalfacree/benchmarking-the-raspberry-pi-4-73e5afbcd54b


Raspberry Pi 4 Cooling Review: Pimoroni Heatsink and Fan Shim Tested
https://www.tomshardware.com/reviews/pimoroni-fan-shim-heatsink-raspberry-pi-4,6219.html
By default, the Fan Shim spins up to its full 4,200 RPM as soon as the
Raspberry Pi is switched on. In this mode, its cooling performance is
extremely impressive: the SoC idles at around 37 degrees Celcius in a
24.5 degrees Celcius ambient environment, and remains below 55 degrees
Celsius throughout the test. This is well below the 80 degrees Celcius
throttle point of the Raspberry Pi 4’s BCM2711B0 SoC, so no throttle
operations are recorded - the CPU runs at its full 1.5GHz throughout.
There is a cost, however: the fan pulls an additional 0.6W from the
power supply while running.

The Fan Shim has another operating mode, however: software control via
a Python-based application programming interface (API). Using this,
it’s possible to turn the fan on and off - though not to vary its
speed, other than by turning it on and off in rapid succession to
simulate a pulse-width modulation (PWM) signal - and to make use of
the tactile switch and RGB LED.

A sample program is included which sets an upper temperature limit and
a hysteresis temperature, which Pimoroni recommends be set at 65
degrees Celsius and 5 degrees Celsius respectively. When running with
these settings, the fan switches on - and the RGB LED toggles from red
to green - at 65 degrees Celsius then cools until 60 degrees Celsius
is reached before turning off and waiting for the temperature to rise
again.

Here the Raspberry Pi idles at the same temperature as its uncooled,
stock incarnation: around 50 degrees Celsius. The fan doesn’t spin up
until the temperature hits 65 degrees Celsius, and then spends the
rest of the test toggling on and off in order to keep the Raspberry Pi
4 below its target temperature. It does so admirably: as with the
always-on mode, the SoC is kept far from its throttle point, and the
ten-minute test completes without a single throttle operation being
recorded. The same is also true when overclocked, though the fan will
kick in more quickly and more often to compensate for the additional
heat.

Combined Cooling
Most desktop and laptops computers don’t rely on only a heatsink or
only a fan; they use a combination of both, and it’s possible to do so
with the Fan Shim and heatsink too - though it is not recommended by
Pimoroni itself, which carried out its own testing and
counterintuitively found the combination cooled less effectively than
simply using the Fan Shim alone.

There’s only one way to verify that, mind you: to carry out the same
test ourselves. The Pimoroni heatsink with Fan Shim connected on top
is a combination which really necessitates the installation of pin
extensions or Pimoroni’s Booster Header to the GPIO header; without
them, there’s not enough pin for the Fan Shim to grip and it runs the
risk of falling off - potentially shorting out the GPIO pins on its
way, damaging the Raspberry Pi 4.

For this test, the Fan Shim is left in software-controlled mode with
the same temperature target of 65 degree Celcius as before. The result
is a graph looking remarkably similar to using the Fan Shim alone,
only stretched: the heatsink effectively stores up the heat generated
by the SoC, slowing down the time until the Fan Shim needs to switch
on; the downside is it also slows down the time it needs to switch off
again afterwards. In terms of actual performance, though, there’s
little difference: once again the SoC is cooled to the point where it
doesn’t need to throttle the CPU to protect itself.

The Performance Impact
Being able to prevent your Raspberry Pi 4 from throttling has a
measurable impact on performance, though how measurable will depend
entirely on how badly it’s throttling. In our test environment, which
was at a stable 24.5 degrees Celcius throughout, the throttling wasn’t
terrible: while the CPU did frequently drop to 1GHz under sustained
load, it would quickly pop back up to 1.5GHz again. In a warmer
environment the throttling would happen sooner and be sustained for
longer, meaning the cooling accessories would have a greater impact on
measured performance.

For this test, the Raspberry Pi 4 is instructed to compress an 8GB
file stored on a USB 3.0 SSD, using the multi-threaded lbzip2
compression utility, while the time it takes is measured. Compressing
such a large file on the Raspberry Pi 4 typically takes around twenty
minutes, roughly double the synthetic load from the throttle testing,
and on an uncooled Raspberry Pi triggers thermal throttling.

There’s not a huge amount between them, but the Fan Shim definitely
has an impact: the compression operation took 22 minutes and 14
seconds on an uncooled Raspberry Pi 4 but completed in 20 minutes and
four seconds with the Fan Shim attached, saving over two minutes -
just shy of a ten percent performance gain. Had the operation gone on
longer, or taken place in a hotter environment, the difference would
be greater.

For those who don’t like the idea of adding a spinning fan to their
Raspberry Pi 4, the heatsink is a realistic alternative: with just the
heatsink attached the benchmark completed in 20 minutes and 23 seconds
- a respectable eight percent boost over uncooled stock, lagging just
slightly behind the Fan Shim. Unlike the Fan Shim, though, the
heatsink is unlikely to offer the same gains in a hot environment,
where it can’t bleed off the heat it is conducting quickly enough, or
for sustained workloads in excess of twenty minutes.

The combined Fan Shim and heatsink option, meanwhile, performed within
the margin of error identically to using the Fan Shim alone - meaning
unless you want to reduce the amount of time the fan spends toggling
on and off, which you could also achieve in software by increasing the
hysteresis temperature, there’s little real-world point to combining
the two.

Bottom Line
If your Raspberry Pi 4 is used for sustained workloads, you’re going
to need some form of cooling to get the most out of it. While the
passive heatsink option is simple and cheap, it’s only a partial
solution; the Fan Shim, by contrast, solves the problem completely -
or, at least, mostly.

The caveat which prevents it from being truly “completely” solved: the
Fan Shim is only effective in a relatively open environment, or when
used with cases like Pimoroni’s own Pibow which keep it uncovered. If
installed in an enclosed case like the Official Raspberry Pi 4 Case,
the Fan Shim can only do so much and throttling under sustained
workloads may still be a problem. The solution: look for cases with
ventilation, or take a drill to the Official Case to create your own.

Certain heavy workloads and enclosed environments aside, though,
neither active nor passive cooling accessories are strictly necessary
on the Raspberry Pi 4: even when hitting its thermal throttle point
it’s still an impressively powerful upgrade from its predecessors, and
running hot is unlikely to do the boards any permanent damage - the 80
degrees Celsius throttle point being comfortably below the components’
maximum rated operating temperatures.



Re: Fan SHIM for Raspberry Pi

David Ranch <dranch@...>
 


Hey Larry,

Thanks for the comprehensive post!

I've been thinking of buying one of these units too but the use of the I2S pin is a killer for me as I need that bus for the FePi HATT.  So, I guess I'm back to square one trying to find an intelligent fan for the Raspberry Pi.  I'd personally like to see an Rpi cooler that uses a three our four pin fan and I can monitor it's RPM via the I2C bus.  This should be pretty simple using something like a Micrchip EMC2301 ( https://www.mikroe.com/fan-click ) but I haven't found anything that's pre-made and something very small like the Fan SHIM.  I know I could do something like this via an Arduino and I've done something similar showing the RPM on an LCD display but not putting the data into an I2C bus but that's all too "big" and I'm again looking for something just as small as a Fan SHIM.

Maybe someone else on the list has found something like what I'm looking for?

--David
KI6ZHD




On 10/06/2019 10:33 AM, Larry Dighera wrote:
I want to report that the inexpensive Pimoroni FanSHIM performs very
well in preventing the RPi4 from CPU throttling due to excessive heat.
The supplied Python-based software
https://github.com/pimoroni/fanshim-python implements temperature
control of the fan in proportional response to CPU temperature.  If
you prefer a full time daemon to control the fan, that is included as
well.

CONS
Incompatible with I2S HATs.
Booster Header https://shop.pimoroni.com/products/booster-header
required for some GPIO use.
Moving parts.
Button needs a pending GPIO Zero software update.



30mm no-solder, controllable CPU fan with RGB LED and tactile switch
£9.60
https://shop.pimoroni.com/products/fan-shim

Features
30mm 5V DC fan
4,200 RPM
0.05 m3/min air flow
18.6 dB acoustic noise (whisper-quiet)
Friction-fit header
No soldering required
RGB LED (APA102)
Tactile switch
Basic assembly required
Compatible with Raspberry Pi 4 (and 3 B+, 3 A+)
Python library and daemon
Pinout
Kit contains
Fan SHIM PCB
30mm 5V DC fan with JST connector
M2.5 nuts and bolts
Assembly
Assembly is really easy, and will take less than two minutes.

With the component side of the PCB facing upwards, push the two M2.5
bolts through the holes from below, then screw on the first pair of
nuts to secure them and act as spacers.
Push the fan's mounting holes down onto the bolts, with the cable side
of the fan downwards (as pictured) and the text on the fan upwards.
Attach with another two nuts.
Push the fan's JST connector into the socket on Fan SHIM.
Software
Our Python library lets you control the fan (on/off), RGB LED, and
switch. There's a handful of examples to show you how to use each
feature, and a script to install a daemon (a service that runs in the
background) that runs the fan in automatic mode, triggering it on or
off when the CPU reaches a threshold temperature, with a manual
override via the tactile switch.

Tutorial
You can read our Getting Started with Fan SHIM tutorial for a really
detailed guide on assembling Fan SHIM and installing the software,
with photos for each step of the assembly.

Notes
When mounting or detaching the fan, or assembled Fan SHIM, do not push
on the fan itself, as it is liable to break.
Be careful to mount your Fan SHIM on the correct pins on your Pi, with
the Pi shut down and power disconnected. Shifting it left by one pin
or down a full row of pins could cause damage to both the Fan SHIM and
the Pi. Check out the photos in our tutorial if you're not sure.
?Not heatsink-compatible!
Because Fan SHIM uses pin BCM18 to control the fan, and this pin is
also used by I2S audio devices, you won't be able to use I2S DACs like
pHAT DAC, pHAT BEAT, and the IQAudio boards at the same time as Fan
SHIM
Dimensions: 45x39x11mm


Benchmarking the Raspberry Pi 4
https://medium.com/@ghalfacree/benchmarking-the-raspberry-pi-4-73e5afbcd54b


Raspberry Pi 4 Cooling Review: Pimoroni Heatsink and Fan Shim Tested
https://www.tomshardware.com/reviews/pimoroni-fan-shim-heatsink-raspberry-pi-4,6219.html
By default, the Fan Shim spins up to its full 4,200 RPM as soon as the
Raspberry Pi is switched on. In this mode, its cooling performance is
extremely impressive: the SoC idles at around 37 degrees Celcius in a
24.5 degrees Celcius ambient environment, and remains below 55 degrees
Celsius throughout the test. This is well below the 80 degrees Celcius
throttle point of the Raspberry Pi 4’s BCM2711B0 SoC, so no throttle
operations are recorded - the CPU runs at its full 1.5GHz throughout.
There is a cost, however: the fan pulls an additional 0.6W from the
power supply while running.

The Fan Shim has another operating mode, however: software control via
a Python-based application programming interface (API). Using this,
it’s possible to turn the fan on and off - though not to vary its
speed, other than by turning it on and off in rapid succession to
simulate a pulse-width modulation (PWM) signal - and to make use of
the tactile switch and RGB LED.

A sample program is included which sets an upper temperature limit and
a hysteresis temperature, which Pimoroni recommends be set at 65
degrees Celsius and 5 degrees Celsius respectively. When running with
these settings, the fan switches on - and the RGB LED toggles from red
to green - at 65 degrees Celsius then cools until 60 degrees Celsius
is reached before turning off and waiting for the temperature to rise
again.

Here the Raspberry Pi idles at the same temperature as its uncooled,
stock incarnation: around 50 degrees Celsius. The fan doesn’t spin up
until the temperature hits 65 degrees Celsius, and then spends the
rest of the test toggling on and off in order to keep the Raspberry Pi
4 below its target temperature. It does so admirably: as with the
always-on mode, the SoC is kept far from its throttle point, and the
ten-minute test completes without a single throttle operation being
recorded. The same is also true when overclocked, though the fan will
kick in more quickly and more often to compensate for the additional
heat.

Combined Cooling
Most desktop and laptops computers don’t rely on only a heatsink or
only a fan; they use a combination of both, and it’s possible to do so
with the Fan Shim and heatsink too - though it is not recommended by
Pimoroni itself, which carried out its own testing and
counterintuitively found the combination cooled less effectively than
simply using the Fan Shim alone.

There’s only one way to verify that, mind you: to carry out the same
test ourselves. The Pimoroni heatsink with Fan Shim connected on top
is a combination which really necessitates the installation of pin
extensions or Pimoroni’s Booster Header to the GPIO header; without
them, there’s not enough pin for the Fan Shim to grip and it runs the
risk of falling off - potentially shorting out the GPIO pins on its
way, damaging the Raspberry Pi 4.

For this test, the Fan Shim is left in software-controlled mode with
the same temperature target of 65 degree Celcius as before. The result
is a graph looking remarkably similar to using the Fan Shim alone,
only stretched: the heatsink effectively stores up the heat generated
by the SoC, slowing down the time until the Fan Shim needs to switch
on; the downside is it also slows down the time it needs to switch off
again afterwards. In terms of actual performance, though, there’s
little difference: once again the SoC is cooled to the point where it
doesn’t need to throttle the CPU to protect itself.

The Performance Impact
Being able to prevent your Raspberry Pi 4 from throttling has a
measurable impact on performance, though how measurable will depend
entirely on how badly it’s throttling. In our test environment, which
was at a stable 24.5 degrees Celcius throughout, the throttling wasn’t
terrible: while the CPU did frequently drop to 1GHz under sustained
load, it would quickly pop back up to 1.5GHz again. In a warmer
environment the throttling would happen sooner and be sustained for
longer, meaning the cooling accessories would have a greater impact on
measured performance.

For this test, the Raspberry Pi 4 is instructed to compress an 8GB
file stored on a USB 3.0 SSD, using the multi-threaded lbzip2
compression utility, while the time it takes is measured. Compressing
such a large file on the Raspberry Pi 4 typically takes around twenty
minutes, roughly double the synthetic load from the throttle testing,
and on an uncooled Raspberry Pi triggers thermal throttling.

There’s not a huge amount between them, but the Fan Shim definitely
has an impact: the compression operation took 22 minutes and 14
seconds on an uncooled Raspberry Pi 4 but completed in 20 minutes and
four seconds with the Fan Shim attached, saving over two minutes -
just shy of a ten percent performance gain. Had the operation gone on
longer, or taken place in a hotter environment, the difference would
be greater.

For those who don’t like the idea of adding a spinning fan to their
Raspberry Pi 4, the heatsink is a realistic alternative: with just the
heatsink attached the benchmark completed in 20 minutes and 23 seconds
- a respectable eight percent boost over uncooled stock, lagging just
slightly behind the Fan Shim. Unlike the Fan Shim, though, the
heatsink is unlikely to offer the same gains in a hot environment,
where it can’t bleed off the heat it is conducting quickly enough, or
for sustained workloads in excess of twenty minutes.

The combined Fan Shim and heatsink option, meanwhile, performed within
the margin of error identically to using the Fan Shim alone - meaning
unless you want to reduce the amount of time the fan spends toggling
on and off, which you could also achieve in software by increasing the
hysteresis temperature, there’s little real-world point to combining
the two.

Bottom Line
If your Raspberry Pi 4 is used for sustained workloads, you’re going
to need some form of cooling to get the most out of it. While the
passive heatsink option is simple and cheap, it’s only a partial
solution; the Fan Shim, by contrast, solves the problem completely -
or, at least, mostly.

The caveat which prevents it from being truly “completely” solved: the
Fan Shim is only effective in a relatively open environment, or when
used with cases like Pimoroni’s own Pibow which keep it uncovered. If
installed in an enclosed case like the Official Raspberry Pi 4 Case,
the Fan Shim can only do so much and throttling under sustained
workloads may still be a problem. The solution: look for cases with
ventilation, or take a drill to the Official Case to create your own.

Certain heavy workloads and enclosed environments aside, though,
neither active nor passive cooling accessories are strictly necessary
on the Raspberry Pi 4: even when hitting its thermal throttle point
it’s still an impressively powerful upgrade from its predecessors, and
running hot is unlikely to do the boards any permanent damage - the 80
degrees Celsius throttle point being comfortably below the components’
maximum rated operating temperatures.


Re: Raspberry Pi 3 + TNC-Pi issue with serial port

 

I had a problem that pitnc_getparams would not work if the ax.25 service was running. Since I have ax.25 set to autostart, I have to stop the service before I run pitnc_getparams.
--
Bob AF9W


Re: Raspberry Pi 3 + TNC-Pi issue with serial port

James Johnson
 

I have the same problem with Pi 3 and a Pi 4.

James VE7HJ


From: js8call@...
To: "RaspberryPi-4-HamRadio" <RaspberryPi-4-HamRadio@groups.io>
Sent: Thursday, October 10, 2019 12:40:36 PM
Subject: Re: [RaspberryPi-4-HamRadio] Raspberry Pi 3 + TNC-Pi issue with serial port

Thank you very much for your fast answers.

Unfortunately it is still not working.

I will continue investigations, I hope I'll be able to post there the solution...

73


Re: Raspberry Pi 3 + TNC-Pi issue with serial port

js8call@...
 

Thank you very much for your fast answers.

Unfortunately it is still not working.

I will continue investigations, I hope I'll be able to post there the solution...

73


Re: Raspberry Pi 3 + TNC-Pi issue with serial port

Steve KC1AWV
 

Try these steps:

Disable Bluetooth
Insert dtoverlay=pi3-disable-bt into /boot/config.txt

Disable hciuart
systemctl disable hciuart

Disable serial getty
systemctl disable serial-getty@...

Reboot Raspberry Pi
systemctl reboot

When Pi is back on, try running the pitnc programs as root or use sudo

Steve KC1AWV


On Thu, Oct 10, 2019 at 12:04 PM <js8call@...> wrote:
Hello,

A few years ago I installed a BBS on a Raspberry with a TNC-Pi2. Unfortunatly my SD card died recently and I had to re-install all.

I follow the last version of the documentation available on https://tnc-x.com/TNCPi.pdf but I'm not able to get "pitnc_getparams"  working (Raspberry Pi3 B).

- I installed Raspbian Stretch (2019-04-08-raspbian-stretch-lite.img)
- I set the Serial port as mentioned (serial login shell disable/serial interface enable).
- Then I downloaded the the pitnc_get/set_param binaries, made them executable and launch "./pitnc_getparams /dev/serial0 0"  but it is constantly "retrying..." .
- Just in case I tried with ttyAMA0 but it is not better...

I also tried to follow the note mentioned in the documentation "Note added 12/4/2018" but it is not working better, I even try with Raspbian version with the GUI, still the same...

Now I don't know where to search to troubleshoot the issue, if you have some advices to guide me, they are welcome :-)

Thank you



--
Steve Miller
KC1AWV


Re: Raspberry Pi 3 + TNC-Pi issue with serial port

Levi Anderson
 

I had a similar problem, and realized that I forgot to activate the serial port in rasbpi-config.  That is where I would start.  YMMV and good luck OM

73 de KD8SKZ,
Levi


Raspberry Pi 3 + TNC-Pi issue with serial port

js8call@...
 

Hello,

A few years ago I installed a BBS on a Raspberry with a TNC-Pi2. Unfortunatly my SD card died recently and I had to re-install all.

I follow the last version of the documentation available on https://tnc-x.com/TNCPi.pdf but I'm not able to get "pitnc_getparams"  working (Raspberry Pi3 B).

- I installed Raspbian Stretch (2019-04-08-raspbian-stretch-lite.img)
- I set the Serial port as mentioned (serial login shell disable/serial interface enable).
- Then I downloaded the the pitnc_get/set_param binaries, made them executable and launch "./pitnc_getparams /dev/serial0 0"  but it is constantly "retrying..." .
- Just in case I tried with ttyAMA0 but it is not better...

I also tried to follow the note mentioned in the documentation "Note added 12/4/2018" but it is not working better, I even try with Raspbian version with the GUI, still the same...

Now I don't know where to search to troubleshoot the issue, if you have some advices to guide me, they are welcome :-)

Thank you


Re: RPi 3B+ w/ Buster, Alsa, Signalink USB

Mitch
 

That's the issue.  Alsamixer doesn't recognize that there is even any microphone to adjust.  It's so low that even FLDIGI's waterfall gain control won't bring it up enough for my satisfaction.  I was surprised when this happened in Mint on an x86_64 machine though.


Re: RPi 3B+ w/ Buster, Alsa, Signalink USB

Daniel Holmes
 

I have a 4 that I just configured, and didn’t have any trouble with ALSA and a signalink. I did have to go into alsamixer and set the levels first, then fldigi and such seemed to work ok. 

Dan

--
. Please pardon any mispelings or errors.


On Oct 9, 2019, at 1:32 PM, Mitch <ab4mw@...> wrote:

Anyone have any luck with this configuration?  Alsamixer cannot see the microphone input of the Signalink USB (or another USB sound card on hand).  The audio level is very marginal on the low side with the RX knob turned all the way up.

It looks like a driver issue to me.  I tested the Signalink USB on a recent Linux Mint version with the same symptom.

Pulse Audio on the Mint system seems to be able to see and control the microphone, but I would rather not burden an RPi with Pulse if at all possible.

Thanks,
Mitch, AB4MW


RPi 3B+ w/ Buster, Alsa, Signalink USB

Mitch
 

Anyone have any luck with this configuration?  Alsamixer cannot see the microphone input of the Signalink USB (or another USB sound card on hand).  The audio level is very marginal on the low side with the RX knob turned all the way up.

It looks like a driver issue to me.  I tested the Signalink USB on a recent Linux Mint version with the same symptom.

Pulse Audio on the Mint system seems to be able to see and control the microphone, but I would rather not burden an RPi with Pulse if at all possible.

Thanks,
Mitch, AB4MW