Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- RaspberryPi-4-HamRadio
- Messages
Search
|
Re: Seeking case compatible with Pi 5 + Pimoroni NVMe BASE
¿ªÔÆÌåÓýI'm hoping to have my pimoroni this week. I 3D printed a case that holds the Pi5 with the pineberry pi bottom "hat" and if it doesn't directly fit, I may be able to modify it.
Get
On Feb 5, 2024, at 04:26, "Kenneth R. van Wyk" <ken@...> wrote:
|
|
Re: Seeking case compatible with Pi 5 + Pimoroni NVMe BASE
¿ªÔÆÌåÓýHmmm, I might have answered my own question. After looking at a few of the online Pi shops without success, I searched broader and found a couple of 3D cases that should work.This one looks excellent:? Cheers, Ken van Wyk Armata Scientia
|
|
Seeking case compatible with Pi 5 + Pimoroni NVMe BASE
¿ªÔÆÌåÓýI plan on adding my Pi 5 to my portable rig. It¡¯s currently caseless, however, as the Pimoroni NVM3 base board doesn¡¯t seem happy in other cases. Anyone know of a case that can accommodate this configuration, while still allowing access to the external ports? Cheers, Ken van Wyk Armata Scientia |
|
Re: RPi Kernel Panic on Bookworm
2019-06-20-raspbian-buster-lite.img, Pi-3, did not "apt update;apt upgrade", the system is 32bit, will investigate what kernel versions live in the repos later.
Linux Pi3-2019 4.19.50-v7+ #896 SMP Thu Jun 20 16:11:44 BST 2019 armv7l GNU/Linux Needed this to allow "oldoldstable" repositories. apt-get update --allow-releaseinfo-change The dependency packages to compile rmsgw install cleanly, and the app builds without any issues. the rmsgw_aci python script runs and updates just fine.? Send/Get over VHF works.? The timer is started. |
|
Re: RPi Kernel Panic on Bookworm
When I pick this up again, I'm looking at the 2022-04-04 release of Bullseye, which should have the 5.15.xx kernel.? Buster has a release of 4.19 kernel I'll test also.
Describe "works okay" for your environment.? Where does it fall apart and what are you using? I used to run 64 bit only Slackware 13.? |
|
Re: RPi Kernel Panic on Bookworm
¿ªÔÆÌåÓýI know I am jumping in late here, but the AX.25 stuff mostly works on kernel version 4.19, and does ok on 5.15 with some patches.? Version 6 just seems to explode.? I am running my linux/AX.25 on an old version of Slackware (13.37) that runs kernel version 2.6, and it is running perfectly for all the stuff I am using.? It is kind of sad that this has been neglected for that long. -Chris KQ6UP On 2/2/2024 9:53 PM, Jon Bousselot
KK6VLO wrote:
JJ, how far back must we go to get a Raspbian release where this isn't broken? |
|
Winlink + VARA on Pi 5 tests
¿ªÔÆÌåÓýGreetings, I thought I¡¯d share my results thus far here. YMMV, of course, but this is what I¡¯ve found in my testing. Setup Icom IC-7100 with Chameleon EmComm III Base antenna Raspberry Pi 5 with Raspberry Pi OS (Linux hampi 6.1.0-rpi7-rpi-v8 #1 SMP PREEMPT Debian 1:6.1.63-1+rpt1 (2023-11-24) aarch64 GNU/Linux) Wine + Box86 + Box64 Results With some help from a couple of youtube videos and tips here on this list, I got things running. (The version of Box64 was really important.) I did initial testing with my Icom 7200 and a dummy load on the antenna. Rig comms were pretty easy to get working. Then I moved to my 7100 with the real antenna. Linux-based ham radio apps worked really well. I use GridTracker for logging and jtdx for FT8 a lot, so I got those going first. I also got flrig running so I could set rig parameters (e.g., power level) easily. All of these worked fine, although I occasionally have to reset audio device names in setup. (Not sure why, but they¡¯d occasionally ¡°forget¡± prior functioning configurations.) For GridTracker, I use UDP forwarding to send my log entries to my Mac running MacLogger. Worked flawlessly. And then I started working with Winlink Express, VARA HF, and VARA FM. The good news is I got them all working and was able to send and receive emails via RMS as well as P2P. (I run an alternate NCS for Winlink Wednesday, so Winlink P2P mode matters greatly to me.) The bad news is that stability is not ideal. Sometimes, when I switch from RMS to P2P, I get an error saying the TNC couldn¡¯t initialize the server on 127.0.0.1. That seemed to be largely due to device resources being released slowly. If I waited a minute or two, it would usually work, but not always. I could manually kill windows process and that seemed to do it, but not every single time. Even merely running for extended periods of time was not stable. I put my rig into VARA HF P2P mode and sent/received email with a buddy about 500 miles away (Alexandria, VA to Nashville, TN). It worked, bidirectionally just fine. But, after a couple hours, Winlink Express would sometimes die without warning or user interaction. Just poof and it was gone. Conclusion As of right now (Feb 2024), I feel the setup is great for lightweight portable operations. POTA would be awesome. Low power and light weight. Certainly, all the Linux ham apps ran like champs. My family and I take week-long trips to the North Carolina Outer Banks beaches often, and this will be my go-to for radio comms there. I run entirely on solar power + battery there, and this setup should be just fine. (Even better once the USB-C power issues are figured out completely.) But, I am NOT ready to run it as my Winlink Wednesday station, though. I¡¯ll stick with windows (ptui!) for now on that. When a windows (ptui!) app has better stability than a Linux one, that¡¯s bad news. I hope things improve on that front, and I have no doubt they will. Cheers, Ken van Wyk, K0RvW Armata Scientia |
|
Re: RPi Kernel Panic on Bookworm
Used the rpi-update to get onto 6.1.y kernel branch, which is 6.1.74-v8+.
The system was up for about 2h 24m.? I connected to the gateway twice and exchanged mail. First I got a kernel message about rmsgw, shortly after I connected and sent mail. Feb 03 19:14:00 rpi3-dev rmsgw[1191]: sendrf(): [; KK6VLO de WA6BGS-10 SK Feb 03 19:14:00 rpi3-dev rmsgw[1191]: sendrf(): wrote 25 of 25 characters Feb 03 19:14:00 rpi3-dev rmsgw[1191]: Logout KK6VLO??? tx:63 rx:9902 173.0s 57.6 Bytes/s (0) Feb 03 19:14:00 rpi3-dev rmsgw[1191]: CMS Disconnected Feb 03 19:14:00 rpi3-dev kernel: ------------[ cut here ]------------ Feb 03 19:14:00 rpi3-dev kernel: refcount_t: underflow; use-after-free. Feb 03 19:14:00 rpi3-dev kernel: WARNING: CPU: 2 PID: 1191 at lib/refcount.c:28 refcount_warn_saturate+0xf8/0x148 Feb 03 19:14:00 rpi3-dev kernel: Modules linked in: mkiss ax25 cmac algif_hash aes_arm64 aes_generic algif_skcipher af_alg bnep vc4 brcmfmac snd_soc_hdmi_codec drm_display_helper cec drm_dma_helper drm_kms_helper brcmutil binfmt_misc snd_soc_core hci_uart btbcm bluetooth cfg80211 snd_compress snd_pcm_dmaengine fb_sys_fops syscopyarea cdc_acm sysfillrect raspberrypi_hwmon sysimgblt bcm2835_codec(C) bcm2835_isp(C) bcm2835_v4l2(C) v4l2_mem2mem bcm2835_mmal_vchiq(C) videobuf2_dma_contig videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common snd_bcm2835(C) videodev i2c_bcm2835 snd_pcm ecdh_generic ecc rfkill libaes snd_timer mc snd vc_sm_cma(C) raspberrypi_gpiomem uio_pdrv_genirq uio fuse drm dm_mod drm_panel_orientation_quirks backlight ip_tables x_tables ipv6 Feb 03 19:14:00 rpi3-dev kernel: CPU: 2 PID: 1191 Comm: rmsgw Tainted: G???????? C???????? 6.1.74-v8+ #1725 Feb 03 19:14:00 rpi3-dev kernel: Hardware name: Raspberry Pi 3 Model B Rev 1.2 (DT) Feb 03 19:14:00 rpi3-dev kernel: pstate: 40000005 (nZcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) Feb 03 19:14:00 rpi3-dev kernel: pc : refcount_warn_saturate+0xf8/0x148 Feb 03 19:14:00 rpi3-dev kernel: lr : refcount_warn_saturate+0xf8/0x148 Then it crashed a few minutes later on beacon... Feb 03 19:20:01 rpi3-dev kernel: ------------[ cut here ]------------ Feb 03 19:20:01 rpi3-dev kernel: refcount_t: saturated; leaking memory. Feb 03 19:20:01 rpi3-dev kernel: WARNING: CPU: 3 PID: 873 at lib/refcount.c:22 refcount_warn_saturate+0x78/0x148 Feb 03 19:20:01 rpi3-dev kernel: Modules linked in: mkiss ax25 cmac algif_hash aes_arm64 aes_generic algif_skcipher af_alg bnep vc4 brcmfmac snd_soc_hdmi_codec drm_display_helper cec drm_dma_helper drm_kms_helper brcmutil binfmt_misc snd_soc_core hci_uart btbcm bluetooth cfg80211 snd_compress snd_pcm_dmaengine fb_sys_fops syscopyarea cdc_acm sysfillrect raspberrypi_hwmon sysimgblt bcm2835_codec(C) bcm2835_isp(C) bcm2835_v4l2(C) v4l2_mem2mem bcm2835_mmal_vchiq(C) videobuf2_dma_contig videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common snd_bcm2835(C) videodev i2c_bcm2835 snd_pcm ecdh_generic ecc rfkill libaes snd_timer mc snd vc_sm_cma(C) raspberrypi_gpiomem uio_pdrv_genirq uio fuse drm dm_mod drm_panel_orientation_quirks backlight ip_tables x_tables ipv6 Feb 03 19:20:01 rpi3-dev kernel: CPU: 3 PID: 873 Comm: beacon Tainted: G??????? WC???????? 6.1.74-v8+ #1725 Feb 03 19:20:01 rpi3-dev kernel: Hardware name: Raspberry Pi 3 Model B Rev 1.2 (DT) Feb 03 19:20:01 rpi3-dev kernel: pstate: 40000005 (nZcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) Feb 03 19:20:01 rpi3-dev kernel: pc : refcount_warn_saturate+0x78/0x148 Feb 03 19:20:01 rpi3-dev kernel: lr : refcount_warn_saturate+0x78/0x148 And strangely it still had enough to run one more cron entry. Feb 03 19:42:01 rpi3-dev CRON[1246]: pam_unix(cron:session): session opened for user rmsgw(uid=999) by (uid=0) Feb 03 19:42:01 rpi3-dev CRON[1247]: (rmsgw) CMD (/usr/local/bin/rmsgw_aci > /dev/null 2>&1) Feb 03 19:42:01 rpi3-dev rmsgw_aci[1248]: WA6BGS-10 - Linux RMS Gateway ACI 2.5.1 Feb? 3 2024 (DM12ms) Feb 03 19:42:01 rpi3-dev rmsgw_aci[1248]: shm_init(): shmkey = 159412 (0x26eb4) Feb 03 19:42:01 rpi3-dev rmsgw_aci[1248]: shm_init(): shmid = 0 (0x0) Feb 03 19:42:01 rpi3-dev rmsgw_aci[1248]: Channel update interval = 7140 Feb 03 19:42:01 rpi3-dev rmsgw_aci[1248]: Using channel file '/etc/rmsgw/channels.xml Feb 03 19:42:01 rpi3-dev rmsgw_aci[1248]: Channel file '/etc/rmsgw/channels.xml' age? 8109 Feb 03 19:42:01 rpi3-dev rmsgw_aci[1248]: Channel: WA6BGS-10 on radio (145070000 Hz, mode 0) Feb 03 19:42:01 rpi3-dev rmsgw_aci[1248]: /usr/local/bin/rmschanstat ax25 radio WA6BGS-10 reports unavailable Feb 03 19:42:01 rpi3-dev rmsgw_aci[1248]: Channel: WA6BGS-10 on radio is DOWN -- not updated Feb 03 19:42:01 rpi3-dev rmsgw_aci[1248]: Channel Stats: 1 read, 1 active, 1 down, 0 updated, 0 errors Feb 03 19:42:01 rpi3-dev rmsgw_aci[1248]: Version update interval = 86400 Feb 03 19:42:01 rpi3-dev rmsgw_aci[1248]: Version file '/usr/local/etc/rmsgw/stat/.version.WA6BGS-10' age 7578 Feb 03 19:42:01 rpi3-dev CRON[1246]: pam_unix(cron:session): session closed for user rmsgw On the serial console, this appears. [ 8670.831800] Call trace: [ 8670.834290]? ax25cmp+0x14/0x60 [ax25] [ 8670.838066]? ax25_bind+0x244/0x278 [ax25] [ 8670.842194]? __sys_bind+0xe0/0x118 [ 8670.845668]? __arm64_sys_bind+0x28/0x38 [ 8670.849581]? invoke_syscall+0x4c/0x110 [ 8670.853409]? el0_svc_common.constprop.3+0x9c/0x100 [ 8670.858295]? do_el0_svc+0x34/0xd0 [ 8670.861679]? el0_svc+0x2c/0x78 [ 8670.864796]? el0t_64_sync_handler+0x98/0xc0 [ 8670.869059]? el0t_64_sync+0x18c/0x190 [ 8670.872800] Code: d503201f d2800002 d503233f 38626803 (38626824) [ 8670.879001] ---[ end trace 0000000000000000 ]--- It's getting worse. Time to find a release of Raspbian that will run 5.15, and while I work on that...? I'm going to load an x86_64 system and see if its any better. |
|
Re: RPi Kernel Panic on Bookworm
Here's the info from the RPI website as to what it does
.
Get
On Feb 3, 2024, at 17:03, Jon Bousselot KK6VLO <jon-bousselot@...> wrote: I did not know this existed.? Tons of warnings, upgrade first, read release notes later.? Thanks for the info! |
|
Re: RPi Kernel Panic on Bookworm
I did not know this existed.? Tons of warnings, upgrade first, read release notes later.? Thanks for the info!
I did this on Pi-3 and it took way less time than custom compile.? Now I have this version. Linux rpi3-dev 6.1.74-v8+ #1725 SMP PREEMPT Mon Jan 22 13:35:32 GMT 2024 aarch64 GNU/Linux Will load up rmsgw and see if we get more than 17 hours uptime. And I'm a bit puzzled as to what that program did.? The boot commandline doesn't match the kernel. |
|
Re: RPi Kernel Panic on Bookworm
? This link is into the stable branch; I'll agree that one looks unpatched. ?But if you are compiling the stable branch, you may not end up on 6.1.
You should look at what Git actually downloaded. ?When I get clone the default or with --branch rpi-6.1.y, I received patched versions. ? Cheers ? Mike |
|
Re: RPi Kernel Panic on Bookworm
Have you tried running sudo rpi-update
That brings in the latest kernel, not the stable version.
Get
On Feb 3, 2024, at 13:02, Jon Bousselot KK6VLO <jon-bousselot@...> wrote: downloaded whatever version this brings? (which looks like it is rpi-6.1.y) |
|
Re: RPi Kernel Panic on Bookworm
downloaded whatever version this brings? (which looks like it is rpi-6.1.y)
git clone --depth=1 It does have the ax25 patch.? Downloaded this git clone --depth=1 --branch=stable And it does NOT have the patches. Based on the links given in the KM4ACK-PI group, this seems like a reasonable path to gain stability. ? I'm looking for a reliable answer on where raspbian gets their kernel source and what branch it is.? If this fails, I'll be getting the 5.15 kernel |
|
Re: RPi Kernel Panic on Bookworm
If I'm looking at the right thing, the ax25 patches don't appear here, and this stable version is what I think Raspbian is running.? Let me know if you learn otherwise, and where you found it.
Go down to line 62 and it doesn't match what I believe we both understand is the patched version. What release did you pull from raspberryPi git? I ran this git clone --depth=1 --branch rpi-6.1.y https://github.com/raspberrypi/linux |
|
Re: RPi Kernel Panic on Bookworm
On Sat, Feb 3, 2024 at 11:29 AM, Jon Bousselot KK6VLO wrote:
I'm going down this route, starting on the Pi-1 ? Hi Jon, Can you share why you think the patches aren't in the Rasp Pi OS kernel? I pulled the raspberrypi.com git repo and diff'ed against the kernel.org source; they came out the same. ?I see the patches as applied: root@hammytest:/usr/src# diff kernel.org/linux-6.1.63/include/net/ax25.h raspberrypi.com/linux/include/net/ax25.h
root@hammytest:/usr/src# diff kernel.org/linux-6.1.63/net/ax25/af_ax25.c raspberrypi.com/linux/net/ax25/af_ax25.c
root@hammytest:/usr/src# diff kernel.org/linux-6.1.63/net/ax25/ax25_dev.c raspberrypi.com/linux/net/ax25/ax25_dev.c
root@hammytest:/usr/src# diff kernel.org/linux-6.1.63/net/ax25/ax25_subr.c raspberrypi.com/linux/net/ax25/ax25_subr.c
I'd be interested in your results, but I don't understand how the patch fits the crash behavior. ? Thanks ? Mike |
|
Re: RPi Kernel Panic on Bookworm
I'm going down this route, starting on the Pi-1
git the rpi-6.1.y kernel Verify the patches referenced in this thread exist in the code tree (they are) compile eat lunch and then dinner install the kernel and see if it crashes 17 hours later. For my ubuntu x86_64 desktop, I also did the apt source for the current source tree, and apt source linux-image-unsigned-6.5.0-15-generic in the downloaded tree, I notice the ax25 patches appear to be applied, so I wonder if desktop distros have these updates in place? Add that to my list of things to try. If I'm seeing this correctly, the stable kernel tree for rpi does NOT have the ax25 patches applied.? The ax25 patches do appear in 5.15.y and the 6.1.y.? The only two I checked. |
|
Re: RPi Kernel Panic on Bookworm
The bug description sounds more like a disconnect bug David was describing a few weeks ago. ?This doesn't look related to our kernel panic. ?Still I was curious ... I used?apt-get source linux-image-$(uname -r) to pull the source for my kernel, which resulted in a linux-6.1.69 source tree. ?Down under net/ax25, I manually verified that 3 of the patches had been applied and a 4th applied at include/net/ax25.h . ?Seems like this has been patched in the source version for my system. The only thing I couldn't figure out is why apt loads 6.1.69 source, when dmesg shows the running kernel is 6.1.63 . ?I guess the distro maintainers have moved on from .63, but I haven't updated yet. ?I'm a bit reluctant to update since the bug is currently reproducible. ?Instead, I pulled the 6.1.63 source from kernel.org and directly verified the ax.25 patch, so I know these fixes are in my running kernel. ?The patch was made for 5.15 a kernel and there are minor code differences with the 6.1.x kernels. ?However, it's very apparent the patch was applied to the running kernel version. ? Cheers ? Mike ??
|
to navigate to use esc to dismiss