First thing I did upon receiving my NOMAD was setup WiFi and perform sudo apt update & sudo apt upgrade.
Which broke several things. :-o
One item was xtrx.c. A few kernel API call params chenged in the recent version. I was able to get those corrected if anyone is interested.
However I would recommend imaging the SDRAM upon arival (long skinny needlenose pliers through the side hole) before touching anything else.
Thank you for pointing this out. Yes, unfortunately with a long list of dependencies, there's no real way to ensure the image is future proofed so your advice to image the working, shipping image and saving that is appreciated.
@Sigmund logged into the forum today LITERALLY to ask about exactly this, lololol. also discovered xtrx.c was mad about something. I'm guessing that's part of the SDR hardware in the device. how do we fix this issue? somehow it seems Chromium is also broken on my device after upgrading. ETA: fixed Chromium, it was just mad that I changed hostnames.
what do you mean by "imaging the SDRAM?" how does one "image" RAM?
@Sigmund any luck figuring out the SX1262 kmod issue? I dove into it a little the last couple days but no luck here.
@Sigmund Southpaw I think I may have a solution for the SX1262 issue post updating the pi.
Please backup your image first. This is experimental and while I have the system working on my device, I have done a lot of wrangling with it so none of these instructions below should be considered 100% verified.
Once you're done updating the image, do the following:
sudo apt remove dkms
sudo apt install linux-headers-6.1.0-26-arm64
sudo apt install dkms
Then:
sudo apt install build-essential dkms libncurses-dev bison flex libssl-dev libelf-dev
sudo apt install libgpiod-dev libyaml-cpp-dev libbluetooth-dev
And finally:
@TX Programmer this fixed it for me, thanks!
Glad to hear it!
New to Meshtastic and have the NOMAD and like Sigmund, first thing I did was update the PI which broke things.
I did a back up of the SD card and now when I power on all I get is a blank screen other then a flashing curser in the top left corner. I get the same with the back I made. Did try freshly imaged card of just the PI OS and no issues getting to the desktop.
If I follow the steps above get me back in working order or is there more I need to do?
Thanks
@Kirk It has been verified by one other to work just fine. But I don't know about what future sudo apt upgrade's might do.
So instead (BACKUP FIRST), I started from scratch with a standard RasPi image from: https://www.raspberrypi.com/software/operating-systems/. (Use Pi OS 64 bit for Raspi 4/5) Then perform the following:
@J Sorry for the delay in my reply. :-/
You can go diectly here: https://www.raspberrypi.com/software/operating-systems/ to get an image you can install with the built-in Raspi Imager (under accessories) using the SD card slot in your Pi. But (obviously) you'll need to be running your Pi from an external drive of some sort (I often use the "official" Pi NVMe module from Pimoroni: https://shop.pimoroni.com/products/nvme-base?variant=41219587178579). Cuz you'll need to be booted up on the external drive without a card in the SD Card slot on the Pi - for the slot to be available to copy an image to your SD card. Pimoroni has full instructions on how to install the NVMe adapter as well as how to configure things to get it working: https://learn.pimoroni.com/article/getting-started-with-nvme-base.
*OR* you can go here: https://www.raspberrypi.com/news/raspberry-pi-imager-imaging-utility/. Install it on a windoze machine that has a SD Card slot/adapter and copy the Pi OS 64 bit image to a SD Card from there.
Hello, I finally found time to work on this again.
Cerated a new image on a new sd card
went through the above install steps with no issues until I ran: "sudo apt install ./meshtasticd_2.5.7.f77c87d_arm64.deb"
Then I get the following:
Setting up meshtasticd (2.5.7.f77c87d) .
..
N: Download is performed unsandboxed as root as file '/home/KENOMAD/meshtasticd_2.5.7.f77c87d_arm64.deb' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)
I have tried installing it several times all the samne results.
Sugestions?
@Kirk Take a look at this:
I'm going to try the procedure myself from scratch and see what hapens.
(delete this entry)
