Robert Heller

I am trying to update my Banana Pi M64: missinglink% cat /etc/armbian-release # PLEASE DO NOT EDIT THIS FILE BOARD=bananapim64 BOARD_NAME="Banana Pi M64" BOARDFAMILY=sun50iw1 BUILD_REPOSITORY_URL=https://github.com/armbian/build BUILD_REPOSITORY_COMMIT=869a89d6-dirty DISTRIBUTION_CODENAME=focal DISTRIBUTION_STATUS=supported VERSION=20.05.4 LINUXFAMILY=sunxi64 BRANCH=current ARCH=arm64 IMAGE_TYPE=stable BOARD_TYPE=conf INITRD_ARCH=arm64 KERNEL_IMAGE_TYPE=Image but when I run this command: missinglink% sudo apt update && sudo apt dist-upgrade -y I get these errors: W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://deb.debian.org/debian stable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0E98404D386FA1D9 NO_PUBKEY 6ED0E7B82643E131 NO_PUBKEY F8D2585B8783D481 W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://deb.debian.org/debian stable-updates InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0E98404D386FA1D9 NO_PUBKEY 6ED0E7B82643E131 W: Failed to fetch http://deb.debian.org/debian/dists/stable/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0E98404D386FA1D9 NO_PUBKEY 6ED0E7B82643E131 NO_PUBKEY F8D2585B8783D481 W: Failed to fetch http://deb.debian.org/debian/dists/stable-updates/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0E98404D386FA1D9 NO_PUBKEY 6ED0E7B82643E131 W: Some index files failed to download. They have been ignored, or old ones used instead. and the update is a noop. What do I need to fix this?

armbianmonitor -u is bitching about some sort of firewall or network issue. I am using this kernel: Linux gollumm64 5.15.25-sunxi64 #22.02.1 SMP Sun Feb 27 09:24:04 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux With Armbian 22.02.1 Focal Attached is a Fritzing of the adapter I made (mirrored in the Z axis). I expect that I need to create a custom overlay -- I am just not sure if what it should look like. Or if someone has already done this (or something similar).

OK, with more groveling I found /etc/update-motd.d/30-armbian-sysinfo, and it looks like /etc/armbianmonitor/datasources/soctemp (aka /sys/class/hwmon/hwmon0/temp1_input) in units of .001 C. This is all I need. Thanks.

OK, that is some large integer (and that is the wrong pathname -- the correct one is /etc/armbianmonitor/datasources/soctemp, which is a symlink to /sys/class/hwmon/hwmon0/temp1_input). How is that converted to something like centagrade, etc.? That is what units are the values under /sys/class/hwmon/hwmon0/? BTW: I was already away of /sys/class/hwmon/. I am looking for a more "human friendly" output, which I presume exists, since the motd output has it. Or are you telling me that every time I want to check the CPU temp I need to go to a blank virtual term and log in?

spi-spidev is already enabled. There is nothing about overlays for the SD Card Reader.

I don't need troubleshooting help. I am just want to know what the cpu temperature it.

I built an adapter for a SPI interface SD Card Reader (https://www.ebay.com/itm/161201009722). I'm assuming I need to add in an overlay to make this reader show up, but I am not sure what that should be.

When I login on the console, there is this display with a bunch of information, including the CPU temp. I have need to keep track of my CPU's temp, since it seems to be overheating (I have a heat sink on it, but does not seem to be enough -- I have a fan on order). I want to be able to check the temp from time to time, so I would like to run at least the part of the login banner program. What program is that? I am not seeing anything obvious in /bin.

A fragment of my DTS is elsewhere in this thread. Note: it is for a Banana Pi M64, which is probably different from your Pine64. I got my working properly by refering to the schematic diagram I have for the Banana Pi M64. You need to get the schematic diagram for your Pine64, so you know exactly which GPIO pines are wired to the CSI connector, then you can be sure that the DTS file properly sets up the correct GPIO pins to the correct functions.

OK, make sure that the ov5640 module is also enabled.

I found a .dts file that was similar to my board and copy and pasted the parts relating to the camera to the dts file for mine, and then recompiled the dts to a dtb with "make dtbs" and then installed it using "make dtbs_install". Do you have the schematic for your board? That should show you which GPIO pins are used for the camera, so you can make the necessary changes to the device tree code you copied.

You need to enable "V4L platform devices" under Device Drivers > Multimedia support > Media drivers, then under "V4L platform devices" you want "Allwinner V3s Camera Sensor Interface driver" enabled as M.

I have a couple of questions: Exactly how is the Image Format and Image Size information get decoded from the output of and into the command line arguments to media-ctl and fswebcam, and how do I make the settings "stick" for programs like cheese and chromium (the latter so I can use programs / sites like Zoom and GoToMeeting and Google Hangouts -- eg video conferencing, etc.)?

Thanks! I was able to grab a picture!