Skip to content
View in the app

A better way to browse. Learn more.

Armbian Community Forums

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Gunjan Gupta

Members
  • Joined

  • Last visited

Everything posted by Gunjan Gupta

  1. MRAA doesn't depend on sysfs. Its intelligent enough to choose either that or /dev/gpiochip* device Simpler method if you wish to try - https://github.com/eclipse/mraa/blob/master/docs/jsonplatform.md Example file for the same - https://github.com/eclipse/mraa/blob/master/examples/platform/turbotjson.json create json file, export MRAA_JSON_PLATFORM=<path_to_json_file> and you should have it working
  2. Another possible library to try - https://github.com/eclipse/mraa And a sample implementation if you wish to develop and merge support upstream - https://github.com/eclipse/mraa/pull/1111
  3. The most recent CI job got failed in the stage that updates the website. Hence the image got missing from the web page. It will be back in few hours. Until then you can download them from the link that @ag123shared above. The CI jobs finds what board images need to be rebuilt based on the changes made in the build repository. As there are no changes merged for zero3 in last two days, no new Images were generated for the same.
  4. Ah..I see whats going on here. The nightly images uses unreleased OS versions. Debian trixie is to be released next year, and Ubunu Noble will not be released for another 2 months. Hence docker doesn't have a repository for them yet as can be seen by going to - https://download.docker.com/linux/debian/dists/ Install docker.io package using apt instead of following the docker installation guide.
  5. Yeah speaking from personal experience, he didn't meant to offend you. He uses an online translator so I guess if message appeared rude, that is not his fault. He was only trying to help FTDI232 and FT232 is actually the same thing. its just printed differently on different chips. But as I said before, anyone of the adapters will be fine. Some boards require to communicate at very high speed and thats when generally we have to be careful in choosing the uart adapter. But this board uses standard 115200 bps rate. So any adapter can handle it.
  6. I would suggest you to try latest rolling release from https://www.armbian.com/orange-pi-zero-3/
  7. Just checking in if we reached a conclusion. Do we have a root cause? Are we concluding that the issue was due to DRAM_CLK patch?
  8. is there any output on serial console?
  9. Yeah, I think anyone of them should do. I am personally using one thats based on FT232R. In the video I think its mentioned to use one based on CH340C, CP2104 or FT232R. But anyone should work fine for this board.
  10. The difference is mostly in what handles the process. As you already discovered startx doesn't ask you password. Thats because you already logged in and desktop is being started for your user only. If you are familiar with old run level concept, "Systemctl isolate multi-user.target" is like calling telinit 3 and "Systemctl isolate graphical.target" is like calling telinit 5. Desktop is started for all users. Anyone who have access can login.
  11. May be Software Updater is not installed? Anyways rolling release is based on distributions that are not even released yet. Debian Trixie will release next year. Ubuntu Noble will release close to end of April. So bugs in those distributions are kind of expected. May be shortcut is not defined. Not sure, I have to check and come back to you That is weird. I wonder if its the wrong ram size detection thing that I mentioned. Only way to tell is by using serial console and looking at the output. So if you can share the same, that will be great

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.