Jump to content

Meestor_X

Members
 View Profile  See their activity

  • Posts

    71

  • Joined

  • Last visited

 Content Type 

Everything posted by Meestor_X

  1. Meestor_X
    Interesting that you were able to get the overlay to work on Noble. Cannot get any overlay to work on bookworm 24.11.1...
  2. Meestor_X
    Update to say that I was able to update the RockPi-S to the latest armbian, and was able to copy the image to the eMMC and it boots properly, using armbian-install. armbian-install's menus are still broken, but it seems to still do the imaging properly. So, let's call this one closed for now.
  3. Meestor_X
    My understanding is that it might take an RS232 logger to see what happens when the device is booting. I bought an RS232 to USB adapter and if I can figure out how to use it to watch the boot process maybe that will lead to an answer. I was hoping that one of the experts here had done this already, but I know how busy everyone is!
  4. Meestor_X
    It's been a few weeks, I've been unable to figure out why overlays don't load in armbian. I've tried everything I can think of, scoured the internet with no answers... Anyone figured anything out yet? I can't be the only one having this problem??
  5. Meestor_X
    Copy that, @Igor. Just learning my way around here. Hopefully my donation will help a little! I appreciate you and your team. Armbian is a great gift to the SBC community.
  6. Meestor_X
    @Igor I got armbianmonitor working and sent the link it created in a PM to you.
  7. Meestor_X
    Thank you, I will give that a try.
  8. Meestor_X
    Is anyone be able to say whether or not overlays are working in the latest Armbian (with or without armbian-config, I can edit /boot/armbianEnv.txt directly)?
  9. Meestor_X
    I get the following result when trying to run armbianmonitor -u. Is it broken or am I doing something wrong? Armbian 24.8.3 Bookworm CLI on a Rock-Pi S # armbianmonitor -u Collecting info and sending to paste.armbian.com, wait... /usr/bin/armbianmonitor: line 976: iostat: command not found <!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <title>Error</title> </head> <body> <pre>Cannot POST /log</pre> </body> </html> Please post the URL in the forum where you've been asked for.
  10. Meestor_X
    Thank you for that detailed explanation. I am using Armbian on tiny headless devices that are not made to be user-configurable. Just need to get things working again with the newer OS. Hopefully I'll have some more time soon to start from scratch with the latest OS, and see if armbian-install is working now.
  11. Meestor_X
    Huh! And my feeling is that the ability test out new functionality without messing with a working system (the working system being on the eMMC) is to try things out on the µSD first. Also, SUPER easy to copy a working µSD build to the eMMC with Armbian-install. Thanks anyway, I'll keep digging - using a serial monitor will be my last resort if I can't find another answer.
  12. Meestor_X
    Thank you for your reply, @eselarm. Any chance you could ELI5 what you just said? I didn't glean what specifically I would need to do to resolve the issue from what you wrote.
  13. Meestor_X
    Ok, I'm not sure that it's working? # armbianmonitor -u Collecting info and sending to paste.armbian.com, wait... /usr/bin/armbianmonitor: line 976: iostat: command not found <!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <title>Error</title> </head> <body> <pre>Cannot POST /log</pre> </body> </html> Please post the URL in the forum where you've been asked for. Yes, it's recognized and working as expected. The system runs off of the eMMC when there's no bootable image on the µSD card or no card inserted. To do a fresh install of Armbian would take quite a while, I had tried a couple of days ago, but Armbian-install wasn't working so I went back to 24.8.3. However, I tried apt update/upgrade and ran into a new problem...
  14. Meestor_X
    # ls -l /dev/mmcblk* brw-rw---- 1 root disk 179, 0 Dec 12 00:46 /dev/mmcblk0 brw-rw---- 1 root disk 179, 1 Dec 12 00:46 /dev/mmcblk0p1 brw-rw---- 1 root disk 179, 32 Dec 12 00:46 /dev/mmcblk1 brw-rw---- 1 root disk 179, 33 Dec 12 00:46 /dev/mmcblk1p1
  15. Meestor_X
    Right you are! Is this the preferred method to send logs?
  16. Meestor_X
    running 24.8.3, and Armbian-install's screen looks like this: Current root: UUID=117b851b-2be0-4bb7-8572-7edce1ef7375 SD card (/dev/mmcblk1) 1 Boot from SD - system on SATA, USB or NVMe 2 Boot from - system on 3 Boot from - system on SATA, USB or NVMe 5 Install/Update the bootloader on SD card (/dev/mmcblk1) I have a µSD card inserted and a 4gb eMMC, but it looks like the names of these devices are missing?
  17. Meestor_X
    Currently running 24.8.3 and have copied it to the eMMC, working fine on both the µSD image and eMMC. (On the Rock-Pi-S, if you have a bootable image on the µSD card, it boots from that. If not, it boots from the eMMC.) Today, running from the µSD, I did an apt update and apt upgrade, and it updated a few packages (here's the list): # apt list --upgradeable Listing... Done armbian-config/unknown 25.2.0-trunk.154.1212.080011 all [upgradable from: 24.11.1] armbian-firmware/bookworm,bookworm 24.11.2 all [upgradable from: 24.11.1] base-files/bookworm 24.11.2-12.4+deb12u8-bookworm arm64 [upgradable from: 24.11.1-12.4+deb12u8-bookworm] linux-dtb-current-rockchip64/bookworm 24.11.1 arm64 [upgradable from: 24.11.1] linux-image-current-rockchip64/bookworm 24.11.1 arm64 [upgradable from: 24.11.1] tzdata/stable-updates 2024b-0+deb12u1 all [upgradable from: 2024a-0+deb12u1] Now, it no longer boots from the µSD card. So I assume it's done something catastrophic to the image on that card?
  18. Meestor_X
    Thank you @brentr ! So you're saying that Armbian 24.8.3 (or later) does not need this additional line in /etc/udev/rules,d/05-fixMACaddress.rules anymore for the interface to have a unique and fixed (unchanging) MAC address? Is there any issue in leaving the extra line in there?
  19. Meestor_X
    @eselarmI've been working on this for several days, and as far as I can tell, on Armbian 24.8.3, if the "simple test" for whether an overlay has installed is to see if it shows up in `/proc/device-tree` then they are not loading, whether they are added via the overlays= or user_overlays= lines in /boot/armbianEnv.txt. This is for exisitng .dbto files (like s0-ext-antenna, bs, bs@1.3ghz, sdio@10mhz, etc), ones I've copied from websites or forums, or self-created ones. The ONLY way I've been able to successfully install an overlay is by decompiling rk3308-rock-pi-s.dtb, editing it, and recompiling it. Annoyingly, `apt upgrade` will revert that file, so being able to add overlays or user_overlays would be very helpful. References: https://docs.armbian.com/User-Guide_Armbian_overlays/ https://forum.radxa.com/t/usb-sound-card-on-type-c-connector/17627 https://source.android.com/docs/core/architecture/dto/syntax#reference
  20. Meestor_X
    @eselarm are you saying that overlays are working now in 24.11.1 ? (I'm unable to update due to an issue with Armbian-config and apt update not being able to find servers)
  21. Meestor_X
    I too am not seeing any overlays added via armbianEnv.txt whether I add them on the overlays= line or user_overlays= line. ls /proc/device-tree is the same whether items are added or not. Running 24.8.3 (bookworm). Can anyone confirm that overlays aren't working in case it's something I'm doing wrong?
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines

  I accept