Jump to content

Myron

Members
  • Posts

    167
  • Joined

  • Last visited

Everything posted by Myron

  1. Provide diagnostic logs with ... armbianmonitor -u ... and post the link here. It'll may help others determine what the issue is.
  2. You mentioned that it's a fake. Possibly because it is a copy it may have not be a perfect copy and that may be why you can't find firmware that will work with it. Also, the only place to find official Armbian images. Have you tried building your own image using the Armbian build tools? That way you can customise the image you're building to your requirements. Read the Armbian documentation: https://docs.armbian.com/
  3. Have you gone through the basic troubleshooting steps? See: https://docs.armbian.com/User-Guide_Basic-Troubleshooting/
  4. Maybe there has been a glitch in the update release process? I performed a sudo apt update && sudo apt upgrade and this has pulled down an automated build. Should it had pulled down a supported build instead?
  5. @NepT1 I think ufw and iptables-restore are not compatible with each other. Several articles on the Internet I've seen seem to mention to turn off UFW if using iptables-restore. Something I've not looked at for myself so I need to do some of my own research. To signpost you, I guess a good place to start is a Google search like, or similar to: https://www.google.com/search?q=linux+"iptables-restore"+"ufw"
  6. https://docs.armbian.com/User-Guide_Recovery/
  7. @Esteve Have a look at this article: https://www.cyberciti.biz/faq/switch-boot-target-to-text-gui-in-systemd-linux/ What is the result of the command ... systemctl get-default ... ?
  8. Yup. That's an oops on my part. If you've got one, use a USB to Serial card to connect a computer to the serial debug port on the SBC and you'll be able to login to the system that way and then try diagnose the issue that way. See: https://wiki.t-firefly.com/en/ROC-RK3568-PC/debug.html When I started with my Banana Pi Pro I could not get any video to display on the HDMI port right from the beginning. When I got a USN-to-Serial bridge I completed the initial setup using that method and, mysteriously, the HDMI port started to work and still works to this day.
  9. Provide diagnostic logs with ... armbianmonitor -u ... and post the link here. It'll may help others determine what the issue is.
  10. Try this: https://linuxconfig.org/automatically-mount-usb-external-drive-with-autofs Found it using a search on Google using: linux automount usb drive
  11. Provide diagnostic logs with ... armbianmonitor -u ... and post the link here. I don't know why this is happening buy it may help others determine what the issue is.
  12. Can you please provide diagnostic logs for the Rock Pi 4B+ with ... armbianmonitor -u ... and post the link here. It'll may help others determine what the issue is.
  13. Please provide diagnostic logs with ... armbianmonitor -u ... and post the link here. It'll may help others determine what the issue is.
  14. Please provide diagnostic logs with ... armbianmonitor -u ... and post the link here. It'll may help others determine what the issue is.
  15. @RES ... except when I look at the diagnostic log there is no mmc0 device. There is an mmcblk0. Is this the one you're referring to?
  16. @cryk_ Have you run a file system check and repair on the root file system? There are conditions where if the file system is not clean then the root file system is always mounted as read-only. Also check the /etc/fstab file and make sure there are no errors and/or inconsistencies in there. Also see: https://www.thegeekstuff.com/2016/03/forcefsck-on-reboot/. Should work on an Armbian built system. I believe it is safe to invoke e2fsck on a read-only root file system as nothing is getting written. It's dangerous to use e2fsck on a read-write root file system and I don't believe e2fsck will allow you to perform repair operations on a read-write enabled file system.
  17. @cryk_ Provide diagnostic logs with ... armbianmonitor -u ... and post the link here. It'll may help others determine what the issue is. The diagnostic logs might reveal why your file system is read-only and not read-write.
  18. What was the solution @freezr? It appears the member who helped you has erased their reply.
  19. Is there a file named .... .xsession .... in that user's home directory and if there is, what is the contents of that file? I had the same issue not too long ago and I had this file there with its contents being .... "xfce4-session" After reviewing the logs I removed that file (it was not needed in my case) and the xfce4 desktop started.
  20. If possible, please provide diagnostic logs with ... armbianmonitor -u ... and post the link here. It'll may help others determine what the issue is.
  21. Provide logs with ... armbianmonitor -u ... and post on here. It'll may help others determine what the issue is.
  22. Sorry @jonnyvh. my mistake. Thought you had posted partial diagnostic data. Note to self... "I need to open the attachment and see what's in there before I post." 🙂
  23. Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines