Mastodon

FrankMEin neuer Forumbeitrag: <a href="https://linux-nerds.org/topic/1676/rockpro64-mainline-kernel-6.13.0-1197-ayufan" rel="nofollow noopener" translate="no" target="_blank">https://linux-nerds.org/topic/1676/rockpro64-mainline-kernel-6.13.0-1197-ayufan</a> <a href="https://nrw.social/tags/rockpro64" class="mention hashtag" rel="nofollow noopener" target="_blank">#rockpro64</a> <a href="https://nrw.social/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a>

Chris VogelFollow-up to <a href="https://chrichri.ween.de/o/289704403f2f4abea071c3d9cc9f2ab8" rel="nofollow noopener" target="_blank">this note</a>. Dragan had asked me to do repeated power-cycle tests with different kernel versions using the patched dtb for <a href="https://chrichri.ween.de/t/rockpro64" class="mention hashtag" rel="nofollow noopener" target="_blank">#RockPro64</a> to make sure the kernel <a href="https://chrichri.ween.de/t/oops" class="mention hashtag" rel="nofollow noopener" target="_blank">#oops</a> wouldn't still be an issue. I learned that cutting the power of the device could kill the <a href="https://chrichri.ween.de/t/lpddr4" class="mention hashtag" rel="nofollow noopener" target="_blank">#LPDDR4</a> <a href="https://chrichri.ween.de/t/ram" class="mention hashtag" rel="nofollow noopener" target="_blank">#RAM</a>. This is documented in the specification referenced on the <a href="https://wiki.pine64.org/wiki/ROCKPro64#Datasheets_for_Components_and_Peripherals" rel="nofollow noopener" target="_blank">RockPro64 wiki page</a> for <a href="https://files.pine64.org/doc/datasheet/rockpro64/SM512M32Z01MD2BNP(200BALL).pdf" rel="nofollow noopener" target="_blank">Micron LPDDR4 Mobile LPDDR4 Datasheet</a> as stated on page 37 in Uncontrolled Power-Off: <blockquote> An uncontrolled power-off sequence can occur a maximum of 400 times over the life of the device. </blockquote> I never had heard about this before! Cutting power without shutdown can kill my RAM? show dmesg and shutdown To get all the debugging information I needed I wanted the system after booting to print <code>dmesg</code> to the serial console, wait a short time and then actually shutdown. <pre><code> root:~# cat /root/bin/dmesg_and_shutdown.sh #!/bin/bash # a small script that outputs dmesg to serial # console, waits 20 seconds and shuts down dmesg > /dev/ttyS2 # show a message how to stop this script and wait 20 seconds echo "Will shutdown in 20 seconds - to stop me call 'pkill dmesg_and_shut'" > /dev/ttyS2 sleep 20 echo "shutdown -h" > /dev/ttyS2 shutdown -h now # a cronjob that runs after each boot root:~# crontab -l @reboot /root/bin/dmesg_and_shutdown.sh </code></pre> powercycle the board I took the time needed for a complete cycle of booting, showing dmesg, waiting and shutting down: well below 2 minutes. To automate the power cycle I used an <a href="https://chrichri.ween.de/t/esp8266" class="mention hashtag" rel="nofollow noopener" target="_blank">#esp8266</a> based power switch made by <a href="https://chrichri.ween.de/t/sonoff" class="mention hashtag" rel="nofollow noopener" target="_blank">#Sonoff</a> (Powr2) running <a href="https://github.com/letscontrolit/ESPEasy" rel="nofollow noopener" target="_blank">ESP Easy</a> (mega-20210503). <a href="https://chrichri.ween.de/t/espeasy" class="mention hashtag" rel="nofollow noopener" target="_blank">#ESPeasy</a> offers a simple scripting language I used to powercycle after 120 seconds of being switched on: <pre><code> On System#Boot do gpio,12,0 gpio,13,1 endon On button#button_state do if [blue_led#blue_led_state]=1 gpio,13,0 timerSet,1,2 else gpio,13,1 gpio,12,1 timerSet,1,0 timerSet,2,0 endif endon On Rules#Timer=1 do gpio,12,0 timerSet,2,1 endon On Rules#Timer=2 do gpio,12,1 timerSet,1,2 endon </code></pre> Pressing the button on the Sonoff device toggles between: <ul> <li>blue led off: timers disabled, relay on permanently</li> <li>blue led on: timers switch the relay off for 5 seconds, on for 120 seconds and then repeat</li> </ul> logging <code>minicom</code> logged the serial output to a file. Further down the <a href="https://chrichri.ween.de/t/rabbithole" class="mention hashtag" rel="nofollow noopener" target="_blank">#RabbitHole</a> I went when looking at the resulting logfile…

Chris VogelFollow-up to <a href="https://chrichri.ween.de/o/aa4e54ecd04e44e1a13ef079fddffa2f" rel="nofollow noopener" target="_blank">this note</a> Meanwhile Dragans changes to the dtb file helped my testing setup to boot without eMMC. So I could test booting manually from scsi devices like on my production system. Looking for some simple instructions on how-to do this failed and I put together the following information. u-boot on <a href="https://chrichri.ween.de/t/rockpro64" class="mention hashtag" rel="nofollow noopener" target="_blank">#RockPro64</a> uses <a href="https://git.sr.ht/~chrichri/RockPro64_u-boot_SATA_software_RAID_howto#copy-u-boot-environment-to-spi" rel="nofollow noopener" target="_blank">variables written to flash</a>. The important ones for choosing a device/kernel to boot: <pre><code> # this u-boot will look for scsi devices only boot_targets=scsi # it will scan the devices for bootcmd=bootflow scan </code></pre> Since I have a <code>boot.scr</code> in my <code>/boot</code> the <a href="https://docs.u-boot.org/en/latest/develop/bootstd/script.html" rel="nofollow noopener" target="_blank">bootmeth</a> seems to be script. There's also the source of that file <code>boot.cmd</code> available and from there I extracted the commands to run on the u-boot console to start any kernel/initrd/dtb I could find on disk: <pre><code> # initialize pci bus pci enum # show devices on pci pci # reset bus and scan for scsi devices scsi reset # get partition table scsi part # find boot files ls scsi 0:1 /boot # load armbian defaults load scsi 0:1 0x800800 /boot/armbianEnv.txt # replace the xyz on the following line with the # filesize output by 'load' above env import -t 0x800800 xyz # write uuid of partition to variable partuuid part uuid scsi 0:1 partuuid # arguments passed to the kernel on boot setenv bootargs "root=${rootdev} rootwait rootfstype=${rootfstype} ${consoleargs} consoleblank=0 loglevel=${verbosity} ubootpart=${partuuid} usb-storage.quirks=${usbstoragequirks} ${extraargs} ${extraboardargs}" # look for available images, initrds and dtbs ls scsi 0:1 /boot # get the dtb directory, **uInitrd** and the vmlinuz # from the output to use with the following 'load' commands load scsi 0:1 0x02080000 /boot/ load scsi 0:1 0x06000000 /boot/ load scsi 0:1 0x01f00000 /boot//rockchip/rk3399-rockpro64.dtb booti 0x02080000 0x06000000 0x01f00000 </code></pre> At this point I only needed to wait for the Pine64 sata ctrl to arrive to test the <code>current</code> kernel with the same ctrl used in my production system. So I went back to the fork in the tunnels and took the other way down the <a href="https://chrichri.ween.de/t/rabbithole" class="mention hashtag" rel="nofollow noopener" target="_blank">#RabbitHole</a>…

Chris VogelFollow-up to <a href="https://chrichri.ween.de/o/c25a04650dc942b5b728dd8e48133f9f" rel="nofollow noopener" target="_blank">this note</a>: At one of the times the <code>current</code> <a href="https://chrichri.ween.de/t/armbian" class="mention hashtag" rel="nofollow noopener" target="_blank">#Armbian</a> <a href="https://chrichri.ween.de/t/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> kernel didn't crash, but booted on my <a href="https://chrichri.ween.de/t/rockpro64" class="mention hashtag" rel="nofollow noopener" target="_blank">#RockPro64</a> I installed <a href="https://chrichri.ween.de/t/gotosocial" class="mention hashtag" rel="nofollow noopener" target="_blank">#GotoSocial</a> and yes: no more <a href="https://github.com/superseriousbusiness/gotosocial/issues/3840#issue-2881055359" rel="nofollow noopener" target="_blank">strange error messages</a> running it. The only time I remember that I updated a linux kernel to make an application work. Preparations to get the production system running with the newer kernel: <ul> <li>in case of problems I'd need to know my way back to boot the old kernel: u-boot recap and learning</li> <li>test suspected problems with the <a href="https://chrichri.ween.de/t/sata" class="mention hashtag" rel="nofollow noopener" target="_blank">#sata</a> <a href="https://chrichri.ween.de/t/pcie" class="mention hashtag" rel="nofollow noopener" target="_blank">#pcie</a> ctrl beforehand (get a second Pine64 sata ctrl for the test system)</li> </ul> Meanwhile Dragan had <a href="https://lore.kernel.org/linux-rockchip/cover.1740748439.git.dsimic@manjaro.org/T/#u" rel="nofollow noopener" target="_blank">patched the device tree</a> and asked to check on a few reboots whether this would make a difference or cause any regressions. Further down the <a href="https://chrichri.ween.de/t/rabbithole" class="mention hashtag" rel="nofollow noopener" target="_blank">#RabbitHole</a> the tunnel forks…

Chris VogelFollow-up to <a href="https://chrichri.ween.de/o/ea126f38d1584f7aa92ff37ddcdf50f1" rel="nofollow noopener" target="_blank">this note</a>: I decided to test whether <a href="https://chrichri.ween.de/t/gotosocial" class="mention hashtag" rel="nofollow noopener" target="_blank">#GotoSocial</a> would work on the <a href="https://chrichri.ween.de/t/rockpro64" class="mention hashtag" rel="nofollow noopener" target="_blank">#RockPro64</a> using the <code>current</code> instead of the <code>legacy</code> <a href="https://chrichri.ween.de/t/armbian" class="mention hashtag" rel="nofollow noopener" target="_blank">#Armbian</a> kernel before risking problems upgrading my production <a href="https://chrichri.ween.de/t/yunohost" class="mention hashtag" rel="nofollow noopener" target="_blank">#yunohost</a>. I have a similar testing setup: old mechanical drives instead of SSDs, a different PCIe SATA controller, an additional eMMC. The additional eMMC I need to boot from, because for some reason the <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052610" rel="nofollow noopener" target="_blank">PCIe SATA ctrl didn't work, when u-boot initializes the controller before the kernel</a>. Installing the <code>current</code> kernel on my testing setup I found it not working: no console on hdmi, no network. Forgot to install the newer dtb (<a href="https://en.wikipedia.org/wiki/Devicetree" rel="nofollow noopener" target="_blank">device tree binary</a>) as well. With <code>currrent</code> kernel and dtb from <a href="https://chrichri.ween.de/t/armbian" class="mention hashtag" rel="nofollow noopener" target="_blank">#Armbian</a> installed the system booted half of the times I switched it on. Asking around on the <a href="https://pine64.org/community/#chat-platforms" rel="nofollow noopener" target="_blank">rock64 chat</a> I met Dragan Simic who greatly helped me to get further down the <a href="https://chrichri.ween.de/t/rabbithole" class="mention hashtag" rel="nofollow noopener" target="_blank">#RabbitHole</a>…

Chris VogelOn my <a href="https://chrichri.ween.de/t/yunohost" class="mention hashtag" rel="nofollow noopener" target="_blank">#yunohost</a> I tried to update <a href="https://chrichri.ween.de/t/gotosocial" class="mention hashtag" rel="nofollow noopener" target="_blank">#gotosocial</a> from <code>0.17.4~ynh1</code> to <code>0.18.1~ynh1</code> and the update failed. GotoSocial just showed some cryptical error messages when started. <a href="https://gts.superseriousbusiness.org/@dumpsterqueer" class="u-url mention" rel="nofollow noopener" target="_blank">@dumpsterqueer@superseriousbusiness.org</a> traced the <a href="https://github.com/superseriousbusiness/gotosocial/issues/3840" rel="nofollow noopener" target="_blank">problem</a> back to a changed lib version used in the new GotoSocial version and the developer of the lib answered my <a href="https://chrichri.ween.de/t/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://github.com/tetratelabs/wazero/issues/2383#issuecomment-2684617443" rel="nofollow noopener" target="_blank">kernel would be too old</a>. The old <a href="https://chrichri.ween.de/t/armbian" class="mention hashtag" rel="nofollow noopener" target="_blank">#armbian</a> legacy kernel is running, because … I don't remember. I need a kernel update for my <a href="https://chrichri.ween.de/t/rockpro64" class="mention hashtag" rel="nofollow noopener" target="_blank">#rockpro64</a>. Down the <a href="https://chrichri.ween.de/t/rabbithole" class="mention hashtag" rel="nofollow noopener" target="_blank">#RabbitHole</a>…

PublicLewdnessI used Pmbootstrap to install PostmarketOS onto my RockPro64. You pick a variety of options and settings then you choose which disk to install it to and whether you want fde or not. <a href="https://wiki.postmarketos.org/wiki/Installation/Using_pmbootstrap" rel="nofollow noopener" target="_blank">wiki.postmarketos.org/wiki/Install...</a> <a href="https://bsky.app/search?q=%23postmarketos" rel="nofollow noopener" target="_blank">#postmarketos</a> <a href="https://bsky.app/search?q=%23pine64" rel="nofollow noopener" target="_blank">#pine64</a> <a href="https://bsky.app/search?q=%23rockpro64" rel="nofollow noopener" target="_blank">#rockpro64</a> <a href="https://wiki.postmarketos.org/wiki/Installation/Using_pmbootstrap" rel="nofollow noopener" target="_blank">Installation/Using pmbootstrap...</a>

Joel P.It's been a nice holiday break with relaxing <a href="https://mastodon.sdf.org/tags/bsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#bsd</a> projects. Final upgrade before heading back to $DAYJOB:Upgrade to NetBSD 10.1 on my <a href="https://mastodon.sdf.org/tags/pine64" class="mention hashtag" rel="nofollow noopener" target="_blank">#pine64</a> <a href="https://mastodon.sdf.org/tags/rockpro64" class="mention hashtag" rel="nofollow noopener" target="_blank">#rockpro64</a> I run ZFS on this ARM64 board with an NVMe SSD attached via PCI card.Running well. dmesg:<a href="https://dmesgd.nycbug.org/index.cgi?do=view&id=8133" rel="nofollow noopener" target="_blank">https://dmesgd.nycbug.org/index.cgi?do=view&id=8133</a><a href="https://mastodon.sdf.org/tags/netbsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#netbsd</a> <a href="https://mastodon.sdf.org/tags/zfs" class="mention hashtag" rel="nofollow noopener" target="_blank">#zfs</a> <a href="https://mastodon.sdf.org/tags/aarch64" class="mention hashtag" rel="nofollow noopener" target="_blank">#aarch64</a>

SpaceWaterThis thing has been a headache and a half to get up and running, but now is running so smoothly<a href="https://infosec.exchange/tags/nixos" class="mention hashtag" rel="nofollow noopener" target="_blank">#nixos</a> <a href="https://infosec.exchange/tags/homelab" class="mention hashtag" rel="nofollow noopener" target="_blank">#homelab</a> <a href="https://infosec.exchange/tags/rockpro64" class="mention hashtag" rel="nofollow noopener" target="_blank">#rockpro64</a> <a href="https://infosec.exchange/tags/pine64" class="mention hashtag" rel="nofollow noopener" target="_blank">#pine64</a>

balletproof vestCan anyone just tell me in like a dozen simple steps or less how to install <a href="https://beach.city/tags/Debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#Debian</a> onto a SATA disk in a <a href="https://beach.city/tags/RockPro64" class="mention hashtag" rel="nofollow noopener" target="_blank">#RockPro64</a> without fucking hammering nails directly into my forehead or reading a 438 page forum thread please for the love of godIf your answer starts with “maybe” or “I think” or “Just™️” please directly fuck off into deep space, I only want to hear from people who have actually accomplished this and not vague reply guy guesses

Anachron :void:Even though I don't think <a href="https://fosstodon.org/tags/Pine64" class="mention hashtag" rel="nofollow noopener" target="_blank">#Pine64</a> is going strong currently, I have to admit that my <a href="https://fosstodon.org/tags/RockPro64" class="mention hashtag" rel="nofollow noopener" target="_blank">#RockPro64</a> is very solid hardware and has no issues whatsoever.

🇺🇦PhotoSniperFox🇺🇦I didn't die.But my <a href="https://universeodon.com/tags/ISP" class="mention hashtag" rel="nofollow noopener" target="_blank">#ISP</a> (Hi <a href="https://universeodon.com/tags/Xfinity" class="mention hashtag" rel="nofollow noopener" target="_blank">#Xfinity</a>) decided that it was entitled to wait a week to fix it. Then I found out my modem died, even though it lit up it couldn't connect to anything.. The Ethernet ports of the router stopped working. A Single-Board Computer ( <a href="https://universeodon.com/tags/SBC" class="mention hashtag" rel="nofollow noopener" target="_blank">#SBC</a> <a href="https://universeodon.com/tags/RockPro64" class="mention hashtag" rel="nofollow noopener" target="_blank">#RockPro64</a> ) attached by Ethernet died, which controlled my NAS. The Ethernet port on my mobo died. Then my mobo died, probably taking everything with it. So I needed to buy a new computer and new NAS.Also I really wish a non-Xfinity <a href="https://universeodon.com/tags/ISP" class="mention hashtag" rel="nofollow noopener" target="_blank">#ISP</a> could serve our area, that'd be great.

Josh :t_blink:So far the <a href="https://fosstodon.org/tags/RockPro64" class="mention hashtag" rel="nofollow noopener" target="_blank">#RockPro64</a> and the <a href="https://fosstodon.org/tags/MangoPi" class="mention hashtag" rel="nofollow noopener" target="_blank">#MangoPi</a> MqPro have been a blast to tinker around with and to set up in their final forms/use case.The <a href="https://fosstodon.org/tags/OrangePi" class="mention hashtag" rel="nofollow noopener" target="_blank">#OrangePi</a> Zero 2w has been a fine addition and has a promising future.Both RPi zeros have steady and running well for their respective use cases (pi-hole and mini nas).The <a href="https://fosstodon.org/tags/MilkVMars" class="mention hashtag" rel="nofollow noopener" target="_blank">#MilkVMars</a> has kind of been a disappointment since day one and not much has improved since then. Maybe it needs more time, but I just get more meh as it goes on.

Josh :t_blink:Beholden thy <a href="https://fosstodon.org/tags/SBC" class="mention hashtag" rel="nofollow noopener" target="_blank">#SBC</a> abomination of jank. A <a href="https://fosstodon.org/tags/MangoPi" class="mention hashtag" rel="nofollow noopener" target="_blank">#MangoPi</a> MqPro plugged into a <a href="https://fosstodon.org/tags/OrangePi" class="mention hashtag" rel="nofollow noopener" target="_blank">#OrangePi</a> Zero W2 that controls 2 <a href="https://fosstodon.org/tags/RaspberryPiZeros" class="mention hashtag" rel="nofollow noopener" target="_blank">#RaspberryPiZeros</a> (W & 2W) and a <a href="https://fosstodon.org/tags/RockPro64" class="mention hashtag" rel="nofollow noopener" target="_blank">#RockPro64</a>.So much janky awesomeness in one place, it’s almost too much to handle! I now “offically” feel like a SBC enthusiast

Joel P.<a href="https://mastodon.sdf.org/@netbsd" class="u-url mention" rel="nofollow noopener" target="_blank">@netbsd</a> Just upgraded my Pine RockPro64!<a href="https://mastodon.sdf.org/tags/pine64" class="mention hashtag" rel="nofollow noopener" target="_blank">#pine64</a> <a href="https://mastodon.sdf.org/tags/rockpro64" class="mention hashtag" rel="nofollow noopener" target="_blank">#rockpro64</a>

Joel P.Finally got time to do a clean install of NetBSD10_RC5 on my <a href="https://mastodon.sdf.org/tags/RockPro64" class="mention hashtag" rel="nofollow noopener" target="_blank">#RockPro64</a> with an eMMC module. Previously I had RC1 running for several months. I have a PCIe M.2 card and a 500gb SSD; hence a breeze to backup key config files from RC1 and then restore once RC5 was up and SSD mounted. Everything looks great 👍<a href="https://mastodon.sdf.org/tags/netbsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#netbsd</a> <a href="https://mastodon.sdf.org/tags/netbsd10" class="mention hashtag" rel="nofollow noopener" target="_blank">#netbsd10</a>

Joel P.I've been running NetBSD10_RC for months on my RockPro64 and only recently learned about using /usr/sbin/schedctl -A 4,5 to force a process to use the faster CPUs. Hopefully this improves a daily ffmpeg job I have. <a href="https://mastodon.sdf.org/tags/NetBSD" class="mention hashtag" rel="nofollow noopener" target="_blank">#NetBSD</a> <a href="https://mastodon.sdf.org/tags/RockPro64" class="mention hashtag" rel="nofollow noopener" target="_blank">#RockPro64</a> <a href="https://mastodon.sdf.org/tags/pine64" class="mention hashtag" rel="nofollow noopener" target="_blank">#pine64</a>

Linux Boards<a href="https://linuxboards.com/harness-the-power-of-linux-with-rockpro64-single-board-computer/" target="_blank" rel="nofollow noopener" translate="no">https://linuxboards.com/harness-the-power-of-linux-with-rockpro64-single-board-computer/</a><a href="https://mastodon.social/tags/Linux" class="mention hashtag" rel="tag">#Linux</a> <a href="https://mastodon.social/tags/ROCKPro64" class="mention hashtag" rel="tag">#ROCKPro64</a>

FrankMEin neuer Forumbeitrag: <a href="https://linux-nerds.org/topic/1555/rockpro64-mainline-kernel-6-8-0-rc3" rel="nofollow noopener" translate="no" target="_blank">https://linux-nerds.org/topic/1555/rockpro64-mainline-kernel-6-8-0-rc3</a> 1555/rockpro64-mainline-kernel-6-8-0-rc3 <a href="https://nrw.social/tags/rockpro64" class="mention hashtag" rel="nofollow noopener" target="_blank">#rockpro64</a> <a href="https://nrw.social/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://nrw.social/tags/mainline" class="mention hashtag" rel="nofollow noopener" target="_blank">#mainline</a>

Shenzi Thinker AbouterConclusion: Linux 6.6 broke something and uboot can't deal with itTried 23.01, 23.07, 23.10, 24.01 All failed to boot 6.6.8Downgraded kernel to 6.5.13 and it came up fineStill need to test another platform (like quartz64 or rock64) but this is my result on rockpro64<a href="https://masto.asonix.dog/tags/sbc" class="mention hashtag" rel="nofollow noopener" target="_blank">#sbc</a> <a href="https://masto.asonix.dog/tags/NixOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#NixOS</a> <a href="https://masto.asonix.dog/tags/uBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#uBoot</a> <a href="https://masto.asonix.dog/tags/RockPro64" class="mention hashtag" rel="nofollow noopener" target="_blank">#RockPro64</a>

Recent searches

Search options

Administered by:

Server stats:

#rockpro64