joey99

So how would I be able to fix it? My router is allowing the url requests, and not dropping them.

I have an orange pi zero that I'm going to use as a pi hole. When installing pi hole, I received a "Error: Unable to update package cache. Please try "sudo apt update"." I did just that and received another error stating Err:1 https://ports.ubuntu.com focal InRelease Could not connect to ports.ubuntu.com:443 (2620:2d:4000:1::19). - connect (111: Connection refused) Could not connect to ports.ubuntu.com:443 (185.125.190.39). - connect (111: Connection refused) Could not connect to ports.ubuntu.com:443 (2620:2d:4000:1::16). - connect (111: Connection refused) Could not connect to ports.ubuntu.com:443 (185.125.190.36). - connect (111: Connection refused) Err:2 https://ports.ubuntu.com focal-security InRelease Unable to connect to ports.ubuntu.com:https: Err:3 https://ports.ubuntu.com focal-updates InRelease Unable to connect to ports.ubuntu.com:https: Err:4 https://ports.ubuntu.com focal-backports InRelease Unable to connect to ports.ubuntu.com:https: Ign:5 https://apt.armbian.com focal InRelease Err:6 https://apt.armbian.com focal Release Redirection from https to 'http://armbian.chi.auroradev.org/apt/dists/focal/Release' is forbidden [IP: 2605:7900:20::5 443] Reading package lists... Done E: The repository 'https://apt.armbian.com focal Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. I tried changing the mirror url in /etc/apt/sources.list.d/armbian.list as @Werner suggested, but I still get the same error even when using the mirror. This is basically what's in the armbian.list deb http://armbian.tnahosting.net/dl/ focal main focal-utils focal-desktop Any clues as to what's going on??

Ya, I though it would not be as simple. Shame there isn't as big as a community for the rock64 compared to Raspberry or even the Orange pi, especially on emulation. It's a pretty solid board for that. The issue is to connect the Rock64 to the display using the provided HDMI angle adapter, I'll have to connect it to the GPIO too. Which is still uncertain as the GPIO's on the Rock64 are slightly different than on the raspberry pi, as what Tony stated. Not sure if it would cause any damage to either the board, screen or both. I could also just use an HDMI cable, but I want to be able to mount the Rock64 on the back of the display with the provided display housing, while also using the provided HDMI angle adapter as it is much neater/cleaner looking. Unless of course if I use the provided HDMI adapter while it is connected to the GPIO, the pins will be bypassed except the 5v and ground. Otherwise, I'll keep looking around for a display without a GPIO connector.

Hello @TonyMac32, many thanks for the information! I did some further research, and it looks like the TXD and RXD on the Rock64 is on pins 19 and 20. Where as on the Pi, it's on pins 8 and 10. So you are right, the display might not work on the rock64 if I were to use the SPI interface, rather than the HDMI. I don't want to risk damaging my Rock64, so I'll hold off on that display until I get a PI. I did found a very detailed document HERE that goes over all of the pins on the Rock64. If an SD card is in place, pins 19, 21, 23 and 24 will become unavailable, as those occupied by the memory chip. So long story short, I think I'll continue to use my monitor as a display for my Rock64. Which is strange, as other documentations did say that the Rock64 is quasi-Raspberry pi compatible, but oh well. The Rock64 is a great emulation machine for it's price, since I got the bundle on Amazon. It's just a shame that not a lot of GPIO devices support the Rock64. EDIT: also found this very detailed post that goes over the rock64's GPIO pins. Forum link

The GPIO pins on the Rock64 are very similar to the Raspberry Pi's GPIO, except the Raspberry pi calls pin #19 GPIO 10, pin #21 GPIO 9 and pin #23 GPIO 11. Where as the Rock64's pin #19 is GPIO3_A1, pin #21 GPIO_A2 and pin #23 GPIO3_A0. The Rock64 documentation does say that it is quasi-Raspberry Pi compatible, but it's hard to find anyone who has actually tested this. Here is the GPIO layout of the Rock64, compared to the Pi 3 I'm currently trying to figure out if a display such as THIS can be connected to the Rock64's GPIO pins without any major issues. User documentation for the display can be found HERE on page 2, in the PDF named 5inch_HDMI_Display_User_Manual. Any information will be greatly appreciated.