All Activity

thanks @eselarm. I think I may not have made myself clear. I want to be able to "Power On" i.e. boot the board using a remote switch and not Power (provide 5v) to the board via the GPIO pins. The Banana Pi docs here (half way down page to GPIO section) actually states that you cannot use the GPIO pins for injecting power only drawing power for ancillary boards etc. When testing the board and setting it up I accidentally touch the SATA case against the GPIO pins and the board started, I'm not sure what pin it was and if it might cause damage long term starting the board this way but I need to know if its possible and which pin(s) i need to short to ground? As regards SATA drive I'm fixing the 2.5" drive to the lid of the box and using one of these SATA right angle adapters and a short100mm very flexible SATA cable to connect to the SATA port on the board and the adapter. when its built I will upload a photo. In the meantime I need to be able to reboot the board externally when the power has been disrupted. I could unsolder the existing switch but the solder pads look tiny.

Hi all, I’m trying to enable the front VFD/LED display on an RK3318 TV box. OS: Armbian 23.11.1 Jammy, kernel 6.18.10-current-rockchip64 DTB: rk3318-box.dtb (fdtfile=rockchip/rk3318-box.dtb) In DTB I found: fd628_dev { compatible = "fd628_dev"; fd628_gpio_clk = <0x7a 0x10 0x00>; // bank2, offset16 fd628_gpio_dat = <0x7a 0x0f 0x00>; // bank2, offset15 }; I built linux_openvfd and added an openvfd node in DTB: openvfd { compatible = "open,vfd"; dev_name = "openvfd"; status = "okay"; }; Module loads, /dev/openvfd appears with: vfd_gpio_clk=2,16,0 vfd_gpio_dat=2,15,0 vfd_gpio_stb=2,19,0 vfd_display_type=0,0,0,0 vfd_chars=0,1,2,3,4,5,6 vfd_dot_bits=0,1,2,3,4,5,6,0 dmesg shows: OpenVFD: Select FD628 controller OpenVFD: SPI 3-wire interface initialized (LSB mode) /sys/class/leds/openvfd exists, but no indicators light up. Tried multiple display_type values and STB pins (bank2 offsets 18–22 + other banks) — still no output. Question: Does anyone know the correct GPIO pins (CLK/DAT/STB) for rk3318-box VFD, or a working driver/service for FD628/FD650 on this board? Any confirmed configs for RK3318 boxes would be greatly appreciated. I’ve been working on this for ~2 weeks and tried multiple configs/drivers without success. Thanks!

One interesting thing I discovered today is that you can actually boot from a flash drive, if you don't have a SD Card! In my case, I would have to buy a SD Card and had a flash drive laying around so I thought I might just give it a try, worked on an Arm Cortex-A53 CPU. I used u-boot-s905x-912 for .ext and meson-gxl-s905x-p212.dtb.

If you look at the wiki page you find the typical 26-pin header like for the original RaspberryPi. pins 2 and 4 are tagged 5V and pin 6 is tagged GND. However, in the schematics there is no mentioning of the 26-pin header. There is GND ofcourse and there is ACIN, that is the 'master' 5V you need to apply and is the same as the VBUS of the microUSB power connector. As there is also the option to connect a LiPo battery (needs soldering), I decided to use the microUSB input for power, I have enough DIY of those connectors (need soldering) as I am not 100% sure if ACIN is exactly the same as pins 2 and 4. I also use a very small DC/DC from 12V to 5V, so I have 12V, 5V, GND for BananaPi and 3.5inch HDD. In never do anything with power button, It is just and old molex connector that I use to connect/disconnect power. You will have the SATA connector sticking out quite a bit, even more then the microUSB for power, so using 26-pin header for power is not getting it much more compact.

Btw. do you know if: 1. Is it possible to use the internal dvb-s tuner in the wetek play 2 with tvheadend? "dmesg | grep -i dvb" showed nothing (an external usb dvb-c wintv solohd was found). 2. Is hardware acellerated "Moonlight Gamestream" possible? In newer/latest Libreelec, the Wetek Play 2 Tuner isnt supported and hardware accelerated x264 is buggy. I think these problems also exist in armbian, or? 🙏

OMG. You really should make this more noticeable For somebody like me, whose only Linux experience is, to play around with Tomato, Libreelec & Coreelec, you don't think that something more might be needed. No matter it runs now ... Thx a lot

I want to put a banana Pi M1 plus a 2.5" SATA drive in a plastic box with only the ethernet and USB ports exposed. This means the onboard power button is not accessible to boot the board. Are you able to power on the board using the GPIO pins? If so please could someone advise which pins to connect to? I also aim to put a 5.5 x 2.1mm barrel connection on the box (with a latching press button switch for isolation) for the +5v supply and connect a short micro USB connector from the barrel socket to the board and also attach the SATA power leads directly rather than powering from the board 2 pin connector to take the load off the micro USB input.

Thanks @bedna Ive now got it working with read write execute on the share via Windows. I searched the Ubuntu forums and foud a couple of posts relating to the issue I was hving with an exfat formatted hard drive. For anyone else searching this forum the answer was to edit the fstab file as follows: To enable read-write access for an exFAT drive in /etc/fstab, add rw,uid=1000,gid=1000,umask=000 to the options field. Using umask=000 ensures all users have read/write access, while setting the uid and gid to your user ID (typically 1000) assigns ownership to your account. Also from Reddit Linux Add this to your /etc/fstab file (replacing the UUID and mount point): UUID=XXXX-XXXX /mnt/exfat exfat defaults,uid=1000,gid=1000,umask=000,nofail 0 0 Key Options Explained rw: Explicitly mounts the drive as read-write. uid=1000,gid=1000: Sets the user and group owner to your user account, preventing root-only lockouts. Use the id command to check your actual UID if needed. umask=000: Sets permissions to 777 (read/write/execute for all), which is usually necessary because exFAT doesn't support native Linux permissions. nofail: Allows the system to boot even if the drive is unplugged. To remove the guest share that appeared all I did was remove the [Global] settings inserted from the Samba wiki i.e. [global] map to guest = Bad User log file = /var/log/samba/%m log level = 1 server role = standalone server [guest] # This share allows anonymous (guest) access # without authentication path = /srv/samba/guest/ read only = no guest ok = yes guest only = yes All working correctly now. I just need to mount the board in a small plastic box and change the IP address to a static one on my daughters subnet.🙂

https://paste.armbian.com/xacimaxamo here's the output from the build from Bigtreetech repo (https://github.com/bigtreetech/build)

Did you ran apt update + upgrade + reboot before ? Edit: we might add warning if installed and running kernel version differs. I ran into this problem myself.

HC4 kernel and headers version dont match. Does not install ZFS.

I was using hdmi cable on hdmi port to only hours later discover that it is hdmi INPUT port, the hdmi output is a usb-c type.

Hi everyone, I'm using a new MXQ box with the SK Hynix H9TP32A8JDBC-PRKM but after flash the bootloader rk322x_loader_v1.10.238_256.bin, rkdeveloptool only detect ~4GB of flash with manufacturer name is SAMSUNG. How can I fix this? Thanks!

What about the step of selecting the uboot?

Step 1. Downloaded "Armbian_community_26.2.0-trunk.606_Aml-s9xx-box_trixie_current_6.18.18_minimal.img.xz" again. Step 2. Opend it with balenaEtcher on 24.04.4 LTS and flashed successful to 16GB Sandisk SD Card. Step 3: Edited extlinux.conf Step 4. I shutted down the Optiplex 3000 TC and removed the SD-Card. Step 5. I inserted the SD-Card into the SD-Card Slot of my Wetek Play 2 (of course WeOS 3.2 is on internal eMMC). Step 6. I press and hold the Power Button of the Wetek Play 2 to initiate the SD-Card Boot. Result: After unexpected long time the WETEK Play.2 Logo disappears and WeOS starts and NOT armbian.

if I understand it correctly, LT8619C is responsible for extracting the audio from HDMI output, and the kernel doesn't have support for it. here's the closest thing that I could find: https://github.com/torvalds/linux/blob/master/drivers/gpu/drm/bridge/lontium-lt8912b.c the original Bigtreetech firmware has the sound, will try their image again tomorrow.

Thanks Werner, Unfortunately I have to halt this project. Though I can now create an booting Neo3plus Armbian image based on the Zero2, it does not fit my initial requirements. Obviously u-boot requires an android partition scheme. The current version as used by the nanopi zero2 cannot be used for my own purposes. So it will need to wait until the board can boot without a vendor u-boot version.

--deleted--

Those are not the correct instructions. Please follow the instructions linked off of the download page: https://www.armbian.com/amlogic-s9xx-tv-box

I haven't used samba for a long time so I'm probably not the best to ask, but I checked my old notes about samba, and this was my goto config: [samba] # edit, or whatever name you want to give it path = /path/to/mountlocation/ browsable = yes writable = yes read only = no force user = <your_username> force group = <your_usergroup> create mask = 0644 # edit, you should probably set this to 0640. This is for files, no need for 7 here, unless you want every file to be executable on the samba share? direcotry mask = 0755 # make sure this works on debian, errors on arch (edit, this was in my notes, so I guess 755 instead of 0755.. maybe.. Or rather 0750 or 750 to only give access to your user and group) public = no This was the only thing I changed from default IIRC, so no guest access or anything, just a uname and passwd to connect. Changing the directory permissions on the server filesystem (chmod) does not matter at all when it comes to samba. As you can see in the conf I provided, the mask is defined there, and all files will get that user/mask (if ext4, exfat does not support user/group/all masks, what you see in your filesystem is what you set in fstab for exfat) and is the mask you will se when looking through a samba mount on another computer. And as a rule of thumb, don't use 777 or 666, the solution is very rarely to completely open up everything, that's a "windows thing" (run as administrator or give everybody access to the directory/application), try to get rid of that habit.

Now flashed with Rufus (very popular windows program) and of course also no boot. I just strictly follow Google KI: Step-by-Step Instructions: Download Image: Download a suitable Armbian image for Amlogic S905/S905X devices (e.g., from the Armbian forum threads by balbes150). Flash SD Card: Use BalenaEtcher or Rufus to flash the image to a MicroSD card. Configure DTB: Open the SD card's boot partition, navigate to dtb/amlogic/, and locate a file for the S905H or generic S905 (gxbb_p200_wetek_play2.dtb or similar). Edit uEnv.txt or extlinux/extlinux.conf to point FDT to this file. Wetek Play 2 dtb on "Minix Neo U1" because: 1. 2. Its the only dtb which makes all working with a Minix Neo U1 in Libreelec. So now i need a detailed step by step manual on how to get a working armbian on a wetek play 2 or minix neo u1!

That's the proprietary trust OS problem Let me understand: if you erase the emmc, and boot armbian from sdcard, doesn't it freeze anymore?

truck.xxx builds are daily/weekly rolling release builds and are not archived.

First some logs would be helpful. You may have to solder a usb-uart connector to the debug uart pads on your board to get boot log information. Without knowing what is going on, diagnosis is difficult. Second, you don't say which u-boot you are using. Can you provide that information? Finally, why are you using the wetek-play2.dtb for this box?

Minix Neo U1 Armbian_community_26.2.0-trunk.606_Aml-s9xx-box_trixie_current_6.18.18_minimal.img win32diskimager to sandisk 16gb sdcard extlinux.conf -> fdt /dtb/amlogic/meson-gxbb-wetek-play2.dtb =NOBOOT!!! "if you have ever booted a different distribution then your box will be incompatible with the Armbian build" Ok, but hey ... i forgot ... i own a Wetek Play 2 and the internal WeOS was never touched in any way. So it must work ... or ??? Lets see: Wetek Play 2 Armbian_community_26.2.0-trunk.606_Aml-s9xx-box_trixie_current_6.18.18_minimal.img win32diskimager to sandisk 16gb sdcard extlinux.conf -> fdt /dtb/amlogic/meson-gxbb-wetek-play2.dtb =OF COURSE !!! ... ... HYPERTENSION ... ... NOFUCKINGBOOT!!! armbian s9xxx makers: please explain! 🤔❓