I am concerned about the use of this config.txt setting to suppress low battery voltage.
I have successfully fed power to several raspberry pis through the GPIO pins and never had to use this setting.
I think there is insufficient regulation to supply the peak current required by the PI.
Even if the warnings are suppressed the Pi will slow its clocks until the power stress is removed.
Additionally I would only supply the Pi with an absolute maximum of 5.25 volts.
It would be interesting to see if adding a suitable cable from the USB power port on the Pi to the regulator in the sBITX also eliminated the warnings.

Used now a raspberry pi 4b 4gb!thanks

I have an 4GB Pi here for testing 64bit and it does work a little faster.. It isn't a night and day difference, but it is faster especially with multiple apps running at the same time. If you primarily use the sBitx without a bunch of 3rd party apps running, then the 2GB Pi is fine.

Those are my 2 cents worth of observation..



-JJ

On Tue, Apr 2, 2024 at 07:16 PM, W6LKB wrote:

And lastly, entering SBITX.local on another PC browser on my home network used to open the web version on the 32 bit code. It no longer works on this beta. The web does open in chromium on the RPi after hitting the WEB button.

Hi Louis,

This should work as it was fixed in beta2.. You may need to refresh your DNS cache on your computer with the PC browser since the IP address may have changed on your sBitx.

You can also open a command window on your pc with:

1. Open the Run menu with Windows Key + R, type "cmd," and press "Enter"
2. Type ping sbitx.local

You should get numbers printed on the screen. If you get a message back stating not found or no response, then it could be DNS issue on your network.?

Try entering this in the cmd window.
ipconfig /flushdns

Try again with sbitx.local? ?If that doesn't work, then try the IP address displayed on your sBitx at startup.


More troubleshooting information can be found at??




-JJ

On Tue, Apr 2, 2024 at 08:20 PM, W6LKB wrote:

I never adjusted the regulator. The line avoid_warnings=1 is in the 64 bit Sbitx folder.

I do have a HDMI TV/monitor connected as desktop 1, but again that didn't change.

Thanks for your help Evan.

Hello Evan and??

The 64bit build suppresses low voltage warnings with this command in config.txt






-JJ

I'm using a 4mb rPi4B.

W6LKB,

I thought that I read where config.txt is in a different folder for the 64-bit Bookworm.? I cannot get to my bench to verify.

Memory usage is the only other thing I can think of that might be different.? If you have the original 2 GB RAM RPi4, there may be more memory swapping with the 64-bit OS and an external monitor.? Try running htop or top to see if there is a lot of swapping.

JJ may have better ideas.

73
Evan
AC9TU

I never adjusted the regulator. The line avoid_warnings=1 is in the 64 bit Sbitx folder.

I do have a HDMI TV/monitor connected as desktop 1, but again that didn't change.

Thanks for your help Evan.

W6LKB,

The original image had warnings suppressed in the config.txt file in the last line:

And lastly, entering SBITX.local on another PC browser on my home network used to open the web version on the 32 bit code. It no longer works on this beta. The web does open in chromium on the RPi after hitting the WEB button.

BTW I'm running a DE with the shipped out mods.

Nothing on USB other than a mouse/keyboard WiFi connector. But that was in use with the 32 bit version and I never got this warning.

Thanks for the assistance.

开云体育

Something to check - It is possible if you have anything plugged into a USB port on the Pi with a heavy enough draw, it can trigger that warning.

Update: 64 bit beta is working fine. Made a few FT8 QSOs with WSJTx and the native FT8 code.

One thing I can't figure out is why I am now getting persistent Low Voltage Warnings. I am using the same power supply that I set at 12.8V which has always worked fine while running the 32 bit OS and SBITX. Increasing the PS voltage to 13.2 had no effect. Despite the warning the system seems to be working fine.

On Tue, Apr 2, 2024 at 10:43 AM, Ashhar Farhan wrote:

Sacrilege!

ROFL !! ....
?
--
Pete VK3PYE

In the meantime, you can do this to avoid upgrading the kernel and still receive other updates.

I've added functionality to the./update?script on the beta2 build for now to hold the packages on my beta build..
You have to run this in terminal.. The ./update command is in there twice to pull from my repo then add the package hold..

cd $HOME
cd sbitx
./update
./update

You can then run?sudo apt update?without issues


If you are running another 64bit build, then?open terminal and copy/paste this..

sudo apt-mark hold linux-headers-6.6.20+rpt-common-rpi linux-headers-6.6.20+rpt-rpi-2712 linux-headers-6.6.20+rpt-rpi-v8 linux-image-6.6.20+rpt-rpi-2712 linux-image-6.6.20+rpt-rpi-v8 linux-kbuild-6.6.20+rpt

then run sudo apt update




-JJ

I spent some time this evening to identify the cause. It was the kernel update that broke functionality.

I will soon release RC1 that fixes the flicker/whitescreen and GPIO errors. I've been testing this evening and no issues so far. Will need a few more days before I know for sure.



-JJ

After hearing about the success of the 64 bit beta version I started to do the upgrade. I grabbed the image file but got stuck trying to download Balena Etcher. The link in your read.me instructions takes me to a list of options none of which seem appropriate for my RPi 4. I searched some forums and even tried a suggestion to use pi-apps to install Etcher, which didn't work. It didn't seem to like my 32-bit OS.So after killing my afternoon, I decided to try using RPi Imager since it is installed with the following line in Terminal:

sudo apt install rpi-imager

Then I used it to burn the image onto a bootable USB drive, and I am now running JJs 64 bit OS with all the other goodies.

Now to test it and migrate all my WSJT and Grid tracker settings.

Hopefully this might help other less experienced Linux folks.

There we go, back to normal.