Thank you for isolating the issue. It is definitely the entire snapshot repo with all its packages that need to have their keys renewed since they all [expired: 2023-01-31]. At least we now know who to report the issue to.
We need to email
ftpmaster@ports-master.debian.org
and request them to renew their key since it expired 2 days ago and re-package all the packages with the new key.
Thanks, neither worked for me though.
sudo apt-get --allow-unauthenticated update
sudo: unable to resolve host starfive: Name or service not known
Hit:1 debian-ports:/ 2022-06-16 19:48:33 - snapshot.debian.org unstable InRelease
Err:1 debian-ports:/ 2022-06-16 19:48:33 - snapshot.debian.org unstable InRelease
The following signatures were invalid: EXPKEYSIG E852514F5DF312F6 Debian Ports Archive Automatic Signing Key (2022) ftpmaster@ports-master.debian.org
Reading package lists… Done
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: debian-ports:/ 2022-06-16 19:48:33 - snapshot.debian.org unstable InRelease: The following signatures were invalid: EXPKEYSIG E852514F5DF312F6 Debian Ports Archive Automatic Signing Key (2022) ftpmaster@ports-master.debian.org
W: Failed to fetch https://snapshot.debian.org/archive/debian-ports/20220616T194833Z/dists/unstable/InRelease The following signatures were invalid: EXPKEYSIG E852514F5DF312F6 Debian Ports Archive Automatic Signing Key (2022) ftpmaster@ports-master.debian.org
W: Some index files failed to download. They have been ignored, or old ones used instead.
user@starfive:~/ChrysaLisp$ cat /etc/apt/sources.list
deb [trusted=yes] debian-ports:/ 2022-06-16 19:48:33 - snapshot.debian.org unstable main
The 2023 package is in the updated package list. If not able to update with the mentioned args, try wget/curl the package directly and install with dpkg -i debian-ports-archive-keyring_2023.02.01_all.deb
Where’s the best place to submit issues for this Debian Image 69?
Issue
sudo apt-get install aptitude
sudo: unable to resolve host starfiveYOW: Name or service not known
Issue
the gui desktop closes suddenly and after a long while the login prompt is displayed again.
Issue
Rust “ring” crate on the vf2 and other riscv boards doesn’t build. Build for riscv64gc-unknown-linux-gnu failed. · Issue #1419 · briansmith/ring · GitHub
Good news: aptitude and emacs-nox work. The full unstable repo snapshot is available to install which is impressive. Java was already installed. I installed Rust nightly with no issues via the standard https://rustup.rs way. Rust likes to have a cc around so I installed build-essential,clang-15-tools, lld-15, llvm 15 as well with no issues.
Hello together,
does anyone has send an e-mail to ftpmaster@ports-master.debian.org to resolve the issue with the signature ?
Best regards
Damian
PS: I have now sent a mail
There is a much simpler solution:
1- download the debian-ports-archive-keyring_2023.02.01_all.deb package from https://deb.debian.org/debian-ports/pool/main/d/debian-ports-archive-keyring/debian-ports-archive-keyring_2023.02.01_all.deb with wget or curl,
install with dpkg -i debian-ports-archive-keyring_2023.02.01_all.deb
2-Use the regular unstable ports directory in /etc/apt/sources.list:
deb http://ftp.ports.debian.org/debian-ports/ unstable main
instead of (or comment out)
#deb https://snapshot.debian.org/archive/debian-ports/20220616T194833Z unstable main
Thanks @johanhenselmans; 1. by itself didn’t fix anything for me (maybe it wasn’t supposed to), but 1. and 2. seems to work (and boy, it’s working itself through 895 updates now).
I also like a CLI only image version. Many I suspect use as 24/7/365. Therefore only need a CLI version that ssh to when need access.
A method to easily enable SSH from base image would be most helpful so do not need to connect HDMI and keyboard to download/enable SSH. For example with RaspberryOS all one needs to do to enable ssh on image is to touch /boot/ssh. When RaspberyPiOS boots it enables ssh and deletes the /boot/ssh file.
Unfortunately I can’t boot after I update it.
(“Can’t boot” is a particularly useless bug report - you need to share how fair it gets at the very least)
It worked for me, but I saw one scary potential failure: the apt upgrade proposed a change to /etc/defaults/u-boot which would probably break boot if accepted:
+#U_BOOT_FDT_OVERLAYS=""
+#U_BOOT_FDT_OVERLAYS_DIR="/boot/dtbo/"
-U_BOOT_PARAMETERS="root=/dev/mmcblk1p3 rw console=tty0 console=ttyS0,115200 earlycon rootwait stmmaceth=chain_mode:1 selinux=0"
-U_BOOT_FDT_DIR="/boot/dtbs/"
If you took that change, the easiest fix is probably to mount that partition on a different machine and change u-boot back.
You’re right, I should’ve been much more specific.
After a bit of analysis, my machine actually boots up, but the HDMI isn’t working. And when I try the SSH connection(I had to connect my sd card to another machine to change ssh conf), this works fine. Is there any logs I should provide to troubleshoot this?
Plus, The apt suggested two configuration changes, one is mime.conf and another one is uboot. I used previous configuration for uboot, and I changed mime conf file to new one. Like you said this debian image has unique uboot configuration, so it shouldn’t be changed.
Thanks.
Well HDMI has never worked for me (see other threads). @Michael.Zhu has proposed workaround which should give 1920x1080 on my 2560x1440 monitor. I haven’t tested it as I mostly use it remotely anyway. I’ve seen plenty of other people with HDMI issues, so I assume it’s a know issue being worked.
I just read your comments from other threads. HDMI worked for me (mine is 1920x1080) before I update it. Even I tried to update firmware, but it doesn’t helped. I should find out more or just wait for fixes. Anyways, thank you for information.
Thanks for all the help on update && upgrade. Yesterday I installed more than 800 upgrades!
Now I have a question on Docker.
I have it installed:
Version: 20.10.23+dfsg1
API version: 1.41
Go version: go1.19.5
Git commit: 7155243
Built: Fri Jan 20 08:04:03 2023
OS/Arch: linux/riscv64
Context: default
Experimental: true
But I can’t get it running.
after executing:
sudo systemctl start docker
Job for docker.service failed because the control process exited with error code.
See “systemctl status docker.service” and “journalctl -xeu docker.service” for details.
and:
sudo systemctl status docker
× docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Tue 2023-02-07 05:58:29 UTC; 10s ago
TriggeredBy: × docker.socket
Docs: https://docs.docker.com
Process: 270690 ExecStart=/usr/sbin/dockerd -H fd:// --containerd=/run/containerd/containerd.s>
Main PID: 270690 (code=exited, status=1/FAILURE)
CPU: 419ms
Feb 07 05:58:29 rvsvrwsv02 systemd[1]: docker.service: Scheduled restart job, restart counter is a>
Feb 07 05:58:29 rvsvrwsv02 systemd[1]: Stopped docker.service - Docker Application Container Engin>
Feb 07 05:58:29 rvsvrwsv02 systemd[1]: docker.service: Start request repeated too quickly.
Feb 07 05:58:29 rvsvrwsv02 systemd[1]: docker.service: Failed with result ‘exit-code’.
Feb 07 05:58:29 rvsvrwsv02 systemd[1]: Failed to start docker.service - Docker Application Contain>
lines 1-14/14 (END)
I am stuck. Docker runs fine on my Visionfive 1 sbc under UBUNTU.
Does anybody have a tip?
Help appreciated!
I tried it on the debian image and there was a few things missing in the kernel.
Is this all the logs you get ? iirc there was a lot more detailed things it complained on when I messed around with it.
all the stuff between these two lines, run with journalctl -u docker -n 50:
Jan 26 12:19:21 starfive dockerd[8267]: time="2023-01-26T12:19:21.271999471Z" level=info msg="Starting up"
...
Jan 26 12:19:22 starfive dockerd[8267]: (exit status 4))
Hello Knegge,
thanks for the tip. This is the result:
sudo journalctl -u docker -n 50
Feb 07 05:58:27 rvsvrwsv02 dockerd[270644]: time=“2023-02-07T05:58:27.661619622Z” level=info msg=“Waiting for containerd to be ready to restart event processing” module=libcontainerd namespace=moby
Feb 07 05:58:27 rvsvrwsv02 dockerd[270644]: failed to start daemon: Error initializing network controller: error obtaining controller instance: unable to add return rule in DOCKER-ISOLATION-STAGE-1 chain: (iptables f>
Feb 07 05:58:27 rvsvrwsv02 dockerd[270644]: (exit status 4))
Feb 07 05:58:27 rvsvrwsv02 systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Feb 07 05:58:27 rvsvrwsv02 systemd[1]: docker.service: Failed with result ‘exit-code’.
Feb 07 05:58:27 rvsvrwsv02 systemd[1]: Failed to start docker.service - Docker Application Container Engine.
Feb 07 05:58:27 rvsvrwsv02 systemd[1]: docker.service: Scheduled restart job, restart counter is at 2.
Feb 07 05:58:27 rvsvrwsv02 systemd[1]: Stopped docker.service - Docker Application Container Engine.
Feb 07 05:58:27 rvsvrwsv02 systemd[1]: Starting docker.service - Docker Application Container Engine…
Feb 07 05:58:28 rvsvrwsv02 dockerd[270690]: time=“2023-02-07T05:58:28.146321796Z” level=info msg=“Starting up”
Feb 07 05:58:28 rvsvrwsv02 dockerd[270690]: time=“2023-02-07T05:58:28.150123347Z” level=info msg=“[core] parsed scheme: "unix"” module=grpc
Feb 07 05:58:28 rvsvrwsv02 dockerd[270690]: time=“2023-02-07T05:58:28.150223848Z” level=info msg=“[core] scheme "unix" not registered, fallback to default scheme” module=grpc
Feb 07 05:58:28 rvsvrwsv02 dockerd[270690]: time=“2023-02-07T05:58:28.150335099Z” level=info msg=“[core] ccResolverWrapper: sending update to cc: {[{unix:///run/containerd/containerd.sock 0 }] }>
Feb 07 05:58:28 rvsvrwsv02 dockerd[270690]: time=“2023-02-07T05:58:28.150418601Z” level=info msg=”[core] ClientConn switching balancer to "pick_first"" module=grpc
Feb 07 05:58:28 rvsvrwsv02 dockerd[270690]: time=“2023-02-07T05:58:28.150477851Z” level=info msg=“[core] Channel switches to new LB policy "pick_first"” module=grpc
Feb 07 05:58:28 rvsvrwsv02 dockerd[270690]: time=“2023-02-07T05:58:28.150605853Z” level=info msg=“[core] Subchannel Connectivity change to CONNECTING” module=grpc
Feb 07 05:58:28 rvsvrwsv02 dockerd[270690]: time=“2023-02-07T05:58:28.150736355Z” level=info msg=“[core] Subchannel picks a new address "unix:///run/containerd/containerd.sock" to connect” module=grpc
Feb 07 05:58:28 rvsvrwsv02 dockerd[270690]: time=“2023-02-07T05:58:28.151381613Z” level=info msg=“[core] Channel Connectivity change to CONNECTING” module=grpc
Feb 07 05:58:28 rvsvrwsv02 dockerd[270690]: time=“2023-02-07T05:58:28.151982621Z” level=info msg=“[core] Subchannel Connectivity change to READY” module=grpc
Feb 07 05:58:28 rvsvrwsv02 dockerd[270690]: time=“2023-02-07T05:58:28.152101623Z” level=info msg=“[core] Channel Connectivity change to READY” module=grpc
Feb 07 05:58:28 rvsvrwsv02 dockerd[270690]: time=“2023-02-07T05:58:28.153711644Z” level=info msg=“[core] parsed scheme: "unix"” module=grpc
Feb 07 05:58:28 rvsvrwsv02 dockerd[270690]: time=“2023-02-07T05:58:28.153788645Z” level=info msg=“[core] scheme "unix" not registered, fallback to default scheme” module=grpc
Feb 07 05:58:28 rvsvrwsv02 dockerd[270690]: time=“2023-02-07T05:58:28.153891397Z” level=info msg=“[core] ccResolverWrapper: sending update to cc: {[{unix:///run/containerd/containerd.sock 0 }] }>
Feb 07 05:58:28 rvsvrwsv02 dockerd[270690]: time=“2023-02-07T05:58:28.153961897Z” level=info msg=”[core] ClientConn switching balancer to "pick_first"" module=grpc
Feb 07 05:58:28 rvsvrwsv02 dockerd[270690]: time=“2023-02-07T05:58:28.154018148Z” level=info msg=“[core] Channel switches to new LB policy "pick_first"” module=grpc
Feb 07 05:58:28 rvsvrwsv02 dockerd[270690]: time=“2023-02-07T05:58:28.154108649Z” level=info msg=“[core] Subchannel Connectivity change to CONNECTING” module=grpc
Feb 07 05:58:28 rvsvrwsv02 dockerd[270690]: time=“2023-02-07T05:58:28.154209901Z” level=info msg=“[core] Subchannel picks a new address "unix:///run/containerd/containerd.sock" to connect” module=grpc
Feb 07 05:58:28 rvsvrwsv02 dockerd[270690]: time=“2023-02-07T05:58:28.154834409Z” level=info msg=“[core] Channel Connectivity change to CONNECTING” module=grpc
Feb 07 05:58:28 rvsvrwsv02 dockerd[270690]: time=“2023-02-07T05:58:28.155044912Z” level=info msg=“[core] Subchannel Connectivity change to READY” module=grpc
Feb 07 05:58:28 rvsvrwsv02 dockerd[270690]: time=“2023-02-07T05:58:28.155119663Z” level=info msg=“[core] Channel Connectivity change to READY” module=grpc
Feb 07 05:58:28 rvsvrwsv02 dockerd[270690]: time=“2023-02-07T05:58:28.863688052Z” level=info msg=“[graphdriver] using prior storage driver: overlay2”
Feb 07 05:58:28 rvsvrwsv02 dockerd[270690]: time=“2023-02-07T05:58:28.886353353Z” level=warning msg=“Unable to find memory controller”
Feb 07 05:58:28 rvsvrwsv02 dockerd[270690]: time=“2023-02-07T05:58:28.886459354Z” level=warning msg=“Unable to find io controller”
Feb 07 05:58:28 rvsvrwsv02 dockerd[270690]: time=“2023-02-07T05:58:28.886532605Z” level=warning msg=“Unable to find cpuset controller”
Feb 07 05:58:28 rvsvrwsv02 dockerd[270690]: time=“2023-02-07T05:58:28.886601606Z” level=warning msg=“Unable to find pids controller”
Feb 07 05:58:28 rvsvrwsv02 dockerd[270690]: time=“2023-02-07T05:58:28.887742121Z” level=info msg=“Loading containers: start.”
Feb 07 05:58:28 rvsvrwsv02 dockerd[270690]: time=“2023-02-07T05:58:28.900252287Z” level=warning msg=“Running modprobe bridge br_netfilter failed with message: modprobe: WARNING: Module bridge not found in directory /l>
Feb 07 05:58:29 rvsvrwsv02 dockerd[270690]: time=“2023-02-07T05:58:29.238473018Z” level=info msg=”[core] Channel Connectivity change to SHUTDOWN" module=grpc
Feb 07 05:58:29 rvsvrwsv02 dockerd[270690]: time=“2023-02-07T05:58:29.238834523Z” level=info msg=“[core] Subchannel Connectivity change to SHUTDOWN” module=grpc
Feb 07 05:58:29 rvsvrwsv02 dockerd[270690]: time=“2023-02-07T05:58:29.240252542Z” level=info msg=“stopping event stream following graceful shutdown” error=“” module=libcontainerd namespace=moby
Feb 07 05:58:29 rvsvrwsv02 dockerd[270690]: failed to start daemon: Error initializing network controller: error obtaining controller instance: unable to add return rule in DOCKER-ISOLATION-STAGE-1 chain: (iptables f>
Feb 07 05:58:29 rvsvrwsv02 dockerd[270690]: (exit status 4))
Feb 07 05:58:29 rvsvrwsv02 systemd[1]: docker.service: Main process exited, code=exited, status=1/FAILURE
Feb 07 05:58:29 rvsvrwsv02 systemd[1]: docker.service: Failed with result ‘exit-code’.
Feb 07 05:58:29 rvsvrwsv02 systemd[1]: Failed to start docker.service - Docker Application Container Engine.
Feb 07 05:58:29 rvsvrwsv02 systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Feb 07 05:58:29 rvsvrwsv02 systemd[1]: Stopped docker.service - Docker Application Container Engine.
Feb 07 05:58:29 rvsvrwsv02 systemd[1]: docker.service: Start request repeated too quickly.
Feb 07 05:58:29 rvsvrwsv02 systemd[1]: docker.service: Failed with result ‘exit-code’.
Feb 07 05:58:29 rvsvrwsv02 systemd[1]: Failed to start docker.service - Docker Application Container Engine.
As a relative newby to linux it seems to me that Docker is unable to create a bridge for networking.
Any tricks I can apply now? Or just be patient until it is fixed?
Hello together,
during the update i got the question to update u-boot config and other config please say NO.
Then the upgrade works and debian starts.
Damian
The journalctl was truncated a bit, but not too important. If you want the full rows then add --no-pager to the command.
This is the main issue so far, and it is related to the kernel and modules available.
“Running modprobe bridge br_netfilter failed with message: modprobe: WARNING: Module bridge not found in directory /l"
When I got docker running I used this build-script in the cross-compiler. Either try using the config from it (did not work for me back then) or just build that one and try it out. Remember to also bring the modules over to it, not only the kernel.
You can simply follow the guide here.
Hello Knegge,
thanks for the help.
(cross)compiling my own kernel goes way beyond my knowledge/experience, so I will have to be patient 
Thank you for this guide! It worked perfectly and saved a ton of time over trying to get TFTP set up.