Keyboard Shortcuts
Likes
- RaspberryPi-4-HamRadio
- Messages
Search
Raspberry Pi 5 vs. Box64
开云体育One step forward, two steps back, one step forward again… So, I’d been working to get VARA* running on my Pi 5. I reported some successes here (and will begin testing with IC-7200 on dummy load later today). This morning, I ran an apt-get upgrade and saw box64 was updated. Oh noes! Sure enough, VARA had stopped working. So, I poked around a bit. Turns out, there are numerous versions of box64 in the Raspberry Pi distro. (To be fair, I haven’t checked which package repository each of these came from.) I tried a couple of them, booting with both the 8 kb page kernel and the 16 kb kernel. Eventually, I found one that works fine. Note the package used here (below). “box64-rpi4arm64”. The box-64-generic-arm ones seem to be for 32 bit ARM CPUs, though I’m just guessing based on the names. If anyone here has insight into what’s going on with these packages, please share. They seem to getting active updates right now. In any case, VARA is running again here. Will report back on my hardware testing. *REALLY* hoping to decommission my Windows box I use for running my rig. Cheers, Ken van Wyk Armata Scientia |
Re: RPi Kernel Panic on Bookworm
? Hi Jon,
Very interesting and welcome to the crash club :) . ?Could you share what kernel version you are on? ?I'm on?6.1.0-rpi7-rpi-v8. ?I also match on the ax25 package versions up to the "+" sign; since we are on different architectures, the package version won't be an exact match. ?Same here for rmsgw, N7NIX built from source. If you can hook up a serial console, I'd recommend it. ?That would allow you to copy/paste the crash messages. ?Make sure you have a TTL level serial adapter. I would recommend moving the beacon to the TNC or just turning it off for a few days. ?You may find the system still crashes, which would be diagnostic. ?In my case a different process triggered the crash, so the serial console would be important. ? Cheers ? Mike |
Re: RPi Kernel Panic on Bookworm
Hi David,
No, the Linux "listen" program can print out TXed packets but you need to enable that feature with the "-a" option:? What I mean by this is that a client and a service sharing the same ax port will never hear each other. ?If rmsgw listens for -10 on ax0 and pat tries to call -10 on ax0, the two will never connect. ?I built the loopback to solve this problem. Ok, this is the second part of new news.? Pat is making an outbound connection via a local digi and back to your Raspberry Pi.? Now to be clear, are you digipeating or NODEing out and back?? I ask because when you NODE around, your SSID gets decremented by one.? That nuance might matter here.? ?So, nomenclature here to make sure we are on the same page, by digipeating you mean adding a digipeater to the initial connection, correct? ?Versus NODEing, where you make an initial connection to a NODE and make a second, in-band connection to the destination? ?In that context, definitely digipeating. ?In general form, the pat connect alias looks like this: ?ax25://dw12/DIGI/MYRMS-10 where "dw12" is the ax port, DIGI is any digipeater, and MYRMS-10 is rmsgw on the Pi. That's a LOT of power for only being so close to each other.? Can you put them in to "EL" or Extra Low mode which is 0.5w?? That might help here.? I would also argue that moving them father apart and also onto different Z-planes aka elevation might help if this is really an RFI issue.? If it is RFI related, I would expect to see other errors like USB device drops, etc.I'm not sure what you mean here by "close to each other". ?Are you referring to distance between Pi and radio, or are you talking about my RF partners? ?I actually think 10w is pretty conservative, given my closest RF partners are 25-30 miles away. ?I did run this radio at 5w for a few years, but noticed that distant partners were unreliable at that power setting. ?I would be glad to test with the power set to "low", but I don't have an "EL" option. ?Again, a single radio being controlled by a single Pi (PROD). ?You used the plural "them" when referring to "EL" setting as if maybe you thought I had 2 radios, but I don't. The Z-plane confused me for a minute because I was thinking cartesian coordinates, but you must be referring to an antenna coordinate system where Z runs up and down (parallel to gravity). ?In that coordinate system, the relationship between radio and Pi would be described as the radio at the origin, and the Pi is at x=0, y=0, z=-3 where units are in feet. ?To paint a word picture, the radio is mounted on the top of a bakers rack, with the Pi directly underneath, but 3 shelves down. ?If I moved the Pi, the best distance I could practically get would be x=-2, y=-8 and z=-5. ?It would take me a while to get the lengths of cables needed to make that happen. Swapping the SD cards around might help here and I imagine that "LEGACY" os is using an older kernel that might not have these AX.25 issues.? Did that LEGACY setup also have rmsgw and Pat running at the same time on it?? In addition to this test and since you have multiple PIs, you might consider splitting apart of the Pat and rmsgw onto different Pis.? That might help isolate the issue as well.My thought was actually swapping the whole Pi (LEGACY for TEST). ?The value in the LEGACY unit is that it is a known quantity; working software, firmware and hardware in the RF environment. ?Besides, LEGACY is a Pi3, where TEST is a Pi4, so I don't think a swapped SD would boot. ?Correct, LEGACY is an older build, maybe jessie or buster, but definitely an older kernel. ?LEGACY has both rmsgw and Pat; it's nearly an identical configuration to PROD/TEST, just older software versions. ?However, LEGACY was using different sound hardware, a UDRC-II. ?I would pry the UDRC-II off the header and use the CM108 usb adapter from TEST. As for splitting up rmsgw and Pat, I decided that I would just turn off Pat for a test cycle. ?If the Pi crashes, then we know that the kernel blaming Pat is a red-herring. ?Since we need some traffic to trigger the crash, I've been just axcall'ing to another node and disconnecting on occasion. ? Thanks ? Mike |
Re: RPi Kernel Panic on Bookworm
Looking for answers on this specifically, I see others are having the same problem.? Beacon seems to be in the panic string each time my Pi crashes.? I'm using a Nino TNC, Raspbian Bookworm 32 bit, and can duplicate the crash on a Pi-3 and Pi-1.? I needed a serial console to capture the full crash content.? If I launch beacon to fork into the background, sending a station beacon every 35 minutes, the system crashes after about 2 days.? I can also get the system to crash sometimes if I invoke beacon to do a one-time send.
I'm trying to setup RMSGW for Winlink mail.? Using the distro supplied packages for ax25-tools and ax25-apps, and the N7NIX source for rmwgw.? This is a new install. ax25-tools???? 0.0.10-rc5+git20190411+3595f87-6 ax25-apps????? 0.0.8-rc5+git20190411+0ff1383-5 Without beacon, it is fairly stable on Pi-1 and Pi-3. Yes, the Pi-1 is kind of slow, but the TNC is doing the work.? The TNC can also beacon on its own - an option I have on my list to try. |
Re: Update from SparkFun regarding Rpi5 order
I saw a YouTube video on doing an install from *.tar.z. all went well until the "git" command.? The Rpi O/S didn't support it. Like I said, I'm new to Linux.? Your first response made virtually zero sense to me. Your elaboration helped a lot. I'm an old dog with bits of education in Fortran, Basic, Unix, and C. I have a hobbiests interest in computers but my career was built around highway and bridge construction.? I spent significant time analyzing data on the National Bridge Inventory using Structured Query Language.? I'm not ashamed to point out my limits to speed my education, so I thank you for?your help. On Tue, Jan 30, 2024, 16:59 Edward Seeliger <eseeliger@...> wrote: Good evening Terry. |
Re: Update from SparkFun regarding Rpi5 order
Good evening Terry.
As I said in my updated post, the sdrpp_debian_bookworm_amd64.deb will install but will not run on RPi5 / BookwormOS / X11 desktop. The sdrpp_raspios_bullseye.deb package will not install. The install command is : sudo apt install xxxxx. To remove / uninstall : sudo apt remove xxxx So we must wait for an installable version for the RPi5 / Bookworm OS or you can build from src (source code) which is also available on the site - but that is a much more involved process. Edd - KD5M |
Re: Update from SparkFun regarding Rpi5 order
Hi Edd. Ive downloaded the SDRpp*.deb file but i'm a newby to LINUX so I don't know where to go from here. is there a command for the command line interface that will install from that?
Here's my layout. Pi 5 8gb w/ 64 bit RPi o/s & bookworm . tnx Terry KGoDU |
Re: Update from SparkFun regarding Rpi5 order
That indeed is the issue. Just did that on mine, did sudo apt install WSJTX -y and it installs and runs as it should
Get
On Jan 30, 2024, at 13:53, "N5XMT via " <gmail.com@groups.io target=_blank>[email protected]> wrote:
|
Re: Update from SparkFun regarding Rpi5 order
Meanwhile, DigiKey shows 697 Pi5 8GB in stock right now ... On Tue, Jan 30, 2024, 3:50?PM Edward Seeliger <eseeliger@...> wrote:
|
Re: Update from SparkFun regarding Rpi5 order
That may be the issue with WSJTX... PiOS bookworm on the Pi5 no longer uses X11. It installs Wayland/Wayfire/WayVNC for the desktop instead.? Before you try and install them, you need to go to? sudo raspi-config, then to Advanced options. Select Wayland, then select X11
Get
On Jan 30, 2024, at 11:25, Edward Seeliger <eseeliger@...> wrote: Good afternoon Terry. Try here and pick? |
Re: Update from SparkFun regarding Rpi5 order
Good afternoon Terry. Try here and pick?
?
That package will install on RPI5 Raspian but will not run. The raspios_bullseye package will not install JTDX and WSJTX can be installed (on Bookworm / X11 desktop) with sudo apt install. FLDigi / FLRig and MSHV can be built from source. Edd - KD5M |
Re: Update from SparkFun regarding Rpi5 order
I ordered?a RPi 5 8G from PiShop last week with a charger and case. it was delivered within 4 days from Deleware?to California I''ve got RPi O/S 64 bit loaded and working. Now can someone guide me to a resource for loading SDR++ ? how about other Ham Software for RPi? Tnx es 73 KGODU Terry On Tue, Jan 30, 2024 at 10:05?AM David Ranch <rpi4hamradio-groupsio@...> wrote:
|
Update from SparkFun regarding Rpi5 order
开云体育I just received an update from SparkFun regarding my three month delayed Rpi5 Essential kit order.? The prospect of them taking another MONTH is rather surprising to me and in some respects, I might just keep my order with them to see if they ever follow through.? At the same time, I see that Parallax just received a shipment of 500 Rpi5 8GB models though I don't know if those are just the bare boards or some level of a kit. --David KI6ZHD From: Maria Henderson from Sparkfun <support@...> -- We sincerely apologize for the delay in processing your order. The shipment is anticipated to be dispatched in mid to late February. ?We acknowledge the inconvenience this delay may have caused and sincerely appreciate your understanding and patience in this matter. Please advise if you would like to cancel your order and receive a full refund. Thank you! Maria
Sales & Support Team
6333 Dry Creek Parkway
Niwot, CO. 80503
-- |
Re: RPi Kernel Panic on Bookworm
开云体育Hello Mike, ?? - I don't think your statement of "I thought this detail was significant as?beacon?and?pat?are the only processes that produce UI frames"?is correct?? Connectionless beacons use UI frames but PAT uses connected sessions.I think we may have talked past each other on this one before, so to clarify, Pat uses connected mode sessions to retrieve mail AND can be configured to send beacons via UI. ?Below is how I had Pat configured (from Pat's config.json) to advertise peer to peer Winlink. ?I've removed this configuration for testing, but does that make sense why I was concerned with UI frames? ?Pat can send UI frames and, of course, use connected mode sessions. Ok.. I didn't know that Pat included it's own "beacon" unique program.? Disabling that will hopefully help narrow things down. ? ?- What is the interval on your beacon message(s)?? Are you only sending one beacon or multiple?? Are you using a digi path on your beacons?I have two beacons; one transmits every 30 minutes with node and RMS SSIDs. ?The other is the hourly Winlink P2P beacon you see above. ?I've de-configured /usr/sbin/beacon and Pat's beacons, and instead I'm now producing these beacons out of direwolf directly. ?No digipeater, just direct to local RF. Got it.
No, the Linux "listen" program can print out TXed packets but you need to enable that feature with the "-a" option: ?? ?????? "-a??????? Allow for the monitoring of outgoing frames as well as incoming ones."
Ah.. ok, so you running rmsgw also on this machine is news.? Might not be a problem but it's worth knowing since as I mentioned before, there are known INCOMING "connected" mode issues with the Linux AX.25 stack but they aren't kernel panic level issues.
Ok.. for now, please keep things simple to figure out this issue.
Ok, this is the second part of new news.? Pat is making an outbound connection via a local digi and back to your Raspberry Pi.? Now to be clear, are you digipeating or NODEing out and back?? I ask because when you NODE around, your SSID gets decremented by one.? That nuance might matter here.
Ok.. so it's the same output as before.? Got it.
That's a LOT of power for only being so close to each other.? Can you put them in to "EL" or Extra Low mode which is 0.5w?? That might help here.? I would also argue that moving them father apart and also onto different Z-planes aka elevation might help if this is really an RFI issue.? If it is RFI related, I would expect to see other errors like USB device drops, etc.
Understood.
Swapping the SD cards around might help here and I imagine that "LEGACY" os is using an older kernel that might not have these AX.25 issues.? Did that LEGACY setup also have rmsgw and Pat running at the same time on it?? In addition to this test and since you have multiple PIs, you might consider splitting apart of the Pat and rmsgw onto different Pis.? That might help isolate the issue as well. --David KI6ZHD |
Re: RPi Kernel Panic on Bookworm
?Hi David,
Thanks for looking though my notes, let's look at this one first, as I think it dovetails into some of the other topics. ?? - I don't think your statement of "I thought this detail was significant as?beacon?and?pat?are the only processes that produce UI frames"?is correct?? Connectionless beacons use UI frames but PAT uses connected sessions.I think we may have talked past each other on this one before, so to clarify, Pat uses connected mode sessions to retrieve mail AND can be configured to send beacons via UI. ?Below is how I had Pat configured (from Pat's config.json) to advertise peer to peer Winlink. ?I've removed this configuration for testing, but does that make sense why I was concerned with UI frames? ?Pat can send UI frames and, of course, use connected mode sessions. ? "ax25": {
? ? "port": "dw12",
? ? "beacon": {
? ? ? "every": 3600,
? ? ? "message": "Winlink P2P",
? ? ? "destination": "BEACON"
? ? }
??}
?
? ?- What is the interval on your beacon message(s)?? Are you only sending one beacon or multiple?? Are you using a digi path on your beacons?I have two beacons; one transmits every 30 minutes with node and RMS SSIDs. ?The other is the hourly Winlink P2P beacon you see above. ?I've de-configured /usr/sbin/beacon and Pat's beacons, and instead I'm now producing these beacons out of direwolf directly. ?No digipeater, just direct to local RF. ?? - When you use Pat, are you making an outbound AX.25 connection to a remote system or is some remote system making a AX.25 connection to you?Do you remember I mentioned the "complexity" in my AX.25 stack? ?I might need a little latitude on this one, so apologies in advance. As I'm sure you are aware, when you transmit through the AX.25 stack, you cannot "hear" that transmission. ?If you could, chaos would ensue. ?This is a bit inconvenient in the scenario where you want to monitor your own services. ?As an example, if you ran your Winlink client (pat) on the same station as your Winlink server (rmsgw), those two could never talk. ?Such is my situation where pat/rmsgw run on the same Pi and it is my only packet station. I found two solutions to this dilemma; the first is to digi back to yourself. ?Of course that's a massive waste of RF and I didn't want to be "that guy". ?The other, more elegant solution, involves kissnetd and a pair of loopback ax ports (a.k.a. "the complexity"). ?You can probably see why I didn't want to muddy the waters with this before; sorry about that. ?I've had this loopback config setup for about 5 years now. ?Did I mention I have disabled this? ?Just making sure. To answer the question, I've normally used the loopback for Pat's connections, so checking my mail doesn't cross RF. ?Realizing the loopback complexity was a liability, I removed those parts last week and I've been using the digi back to myself option. ?The schedule runs just once a day a 9:15a. ?I've had very few inbound connections to my RMS server, but I've never been able to correlate an inbound connection with a crash. ? ?- It might be good to run a script via cron running every minute on your Pis under test that:I've actually done most of that (uptime, free, slabtop, proc temperature, voltage events) on a 10 second cycle. ?I've not recorded disk space or process list as I didn't see much value there. ?As you implied, when the kernel crashes, nothing gets flushed to disk, so my logs are unremarkable. ?However, I like the dmesg idea. ?Given that's a direct read from /dev/kmsg, I think I'll avoid writing that to disk and just stream it to a terminal. ?The hot pipe means it has a better chance of making it to the wire than down to disk. ? ? ?- What kernel version are you currently using?? - Can you take a picture of the kernel crash screen?The kernel is?6.1.0-rpi7-rpi-v8. ?I do have a photo of the crash, but groups.io compresses the picture to such an extent that it is illegible. ?I posted the text of the crash (from the serial console) in a message a few weeks ago. ?Were you looking for something that might be on the screen that wouldn't be on the serial console? ? ?- You mentioned that when you rebuilt the TEST machine to use a real sound device instead of a sound-loopback, it started to crash.? To me, this could be RFI induced.? How physically close is the radio to your Raspberry PIs?? How much RF power is the radio transmitting at?Drats, RFI! ?Don't worry, I'm not going to pull the "not in my shack" argument. ?RFI is always an option, but is notoriously hard to diagnose. ?To answer your questions, I have 3 Pi (PROD, TEST, and an unrelated Pi4) 3 to 4 feet away from the radio and my radio is set to "Mid" power (which is 10w in Kenwood speak). ?I mentioned the audio tap, so my data cable is your typical Mini-DIN6 on the radio end and a very atypical, butchered mess of ribbon cable, and Dupont/TRS connectors on the other (i.e. RFI playground). ?However, do think back just a moment to my loopback remarks, and understand that the crash has usually happened without any RF transmit (i.e. no RFI) while mail was being checked over the loopback. Since RFI is so difficult to identify, how about a differential test against RFI? ?As it happens, I have an idle Pi3 sitting here. ?This Pi, let's call it LEGACY, is the direct predecessor to PROD, so it has a fully operational packet configuration that was decommissioned a couple of months ago. ?More importantly though, it has 2 years of clean operational history (no crashes) in this environment just a few inches away from where TEST and PROD are right now. ?It would be trivial to swap LEGACY into where TEST sits today. ?In that scenario, if LEGACY were to crash, then it points the finger at RFI; if it doesn't crash then a kernel bug is likely to blame. ?Thoughts? ? Thanks ? Mike ? Thanks ? Mike |
Re: Pi5 12v supply
There seems to be confusion about PD for the Pi 5.
toggle quoted message
Show quoted text
Here are a couple of references - make sure you are talking about PD or not! " " " " John Sunderson, Jr. Cell 626-399-6359 drbatch@... -----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Michael WA7SKG Sent: Saturday, January 27, 2024 8:50 PM To: [email protected] Subject: Re: [RaspberryPi-4-HamRadio] Pi5 12v supply Gotta say, this thread has been entertaining. From what I can tell, the RPi5 wants USB-C PD power. The "Official RPi5 Power Supply" provides PD (27W), but is a wall-wart only. The OP I believe wanted something to run from 12V. So... This takes 9-24VDC in and gives USB-A and USB-C/PD outputs. It is hardwired in to whatever power source you have. Chargeit! Mini 75W Dual Port USB-A & USB-C PD Charger w/ PPS & QC4.0 Support This is a cigarette lighter/power point plug in that gives basically the same thing, a USB-A(QC 3.0) and a USB-C(PD) outputs. USB C Car Charger 5 Pack, I believe either one of these should power your RPi5. Personally, I think I would go with the CoolGear item as it supports a higher output (75W combined) than the Bangfun (20W) device. Michael WA7SKG Kelly K7MHI via groups.io wrote on 1/27/24 2:31 PM: Sheesh haha this group … -- KG6TPA - drbatch@... |
5v or 12v or PD??
开云体育There seems to be confusion about PD for the Pi 5. Here are a couple of references - make sure you are talking about PD or not! " " ? " " ? ? John Sunderson, Jr. Cell 626-399-6359 ? -- KG6TPA - drbatch@... |
Re: Pineberry Pi SSD HATs
Sounds like that is what they were doing.? My order was the 27W power supply and the Pi5.? Both showed pre-ordered.? In late October, the Pi5 changed to "Backordered" while the 27W supply was no longer pending.? I found out in November that several people had ordered in late October and received their Pi5's in 2-3 weeks... I sent a couple emails asking why my Pi5 went from pre-order to backordered with zero responses.? I had ordered other items from them over the years and never had issues... I was so fed up with them that after I cancelled my order, I wrote a nice long email to the Pi Foundation.? Since they were certified resellers, they had to sign agreements agreeing to the pi foundations rules.
Hoping the pi foundation removed them from their preferred sellers
Get
On Jan 29, 2024, at 09:10, John <radio@...> wrote:
|