All Activity

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.

> Is there a way to test different DTS without physical meddling with our SBCs? Using armbian-config from Armbian-unofficial_25.05.0-trunk_Transpeed-8k618 image says I cannot edit DTS at all, but even if I could, wouldn't it simply soft-brick the SBC if DTS is incompatible? > Would it be feasible to have uboot + dts + maybe a kernel + some utils, so that we could boot any standard ARM ISO ever produced? Armbian would become standardised, then "firmware" layer is up to the user - whether their device has real UEFI, my proposed environment, or the current all-in-one blob solution seen in all ARM distros. > I found zero actionable information on how to create DTS for given device, is it arcane information for electronics lovers? Do I need to compile specific kernel for it? Given our SBCs have 100% working DTS for Android, couldn't LLMs work out the difference between how Android expects it and how Armbian does? It's awful this division exists, but c'mon this doesn't seem like intelligent problem requiring solutions, but a machinistic mapping of boring register addresses and the corresponding syntax? These seem like standard groundwork that needs to be laid out before any work on any project starts, but in embedded world these lacks in operational hygene consume 99.99% of work focus, don't they? and in the end nothing really works as it should.. Yes, I'm worthless here, but aren't these problems hurting literally everyone to ever use any SBCs, including raspberries, oranges etc. I wish I could help, but the entry seems steep.

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! 🤔❓

Google's AndroidXR. Qualcomm's Snapdragon Spaces. NVIDIA CloudXR. What do they have in common? Monado, the Open Source, cross-platform OpenXR runtime Collabora launched as an alternative to proprietary XR stacks. View the full article

same thing with edge kernel: https://paste.armbian.com/orivozogil

OK thanks @bedna With your help I've made some progress. I followed one of your links to the wiki regarding a standalone server and modified the smb.conf file as below # # Sample configuration file for the Samba suite for Debian GNU/Linux. # # # This is the main Samba configuration file. You should read the # smb.conf(5) manual page in order to understand the options listed # here. Samba has a huge number of configurable options most of which # are not shown in this example # # Some options that are often worth tuning have been included as # commented-out examples in this file. # - When such options are commented with ";", the proposed setting # differs from the default Samba behaviour # - When commented with "#", the proposed setting is the default # behaviour of Samba but the option is considered important # enough to be mentioned here # # NOTE: Whenever you modify this file you should run the command # "testparm" to check that you have not made any basic syntactic # errors. #======================= Global Settings ======================= [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 ## Browsing/Identification ### # Change this to the workgroup/NT-domain name your Samba server will part of workgroup = WORKGROUP # server string is the equivalent of the NT Description field server string = %h server (Samba, Ubuntu) #### Networking #### # The specific set of interfaces / networks to bind to # This can be either the interface name or an IP address/netmask; # interface names are normally preferred ; interfaces = 127.0.0.0/8 eth0 # Only bind to the named interfaces and/or networks; you must use the # 'interfaces' option above to use this. # It is recommended that you enable this feature if your Samba machine is # not protected by a firewall or is a firewall itself. However, this # option cannot handle dynamic or non-broadcast interfaces correctly. ; bind interfaces only = yes #### Debugging/Accounting #### # This tells Samba to use a separate log file for each machine # that connects log file = /var/log/samba/log.%m # Cap the size of the individual log files (in KiB). max log size = 1000 # We want Samba to only log to /var/log/samba/log.{smbd,nmbd}. # Append syslog@1 if you want important messages to be sent to syslog too. logging = file # Do something sensible when Samba crashes: mail the admin a backtrace panic action = /usr/share/samba/panic-action %d ####### Authentication ####### # Server role. Defines in which mode Samba will operate. Possible # values are "standalone server", "member server", "classic primary # domain controller", "classic backup domain controller", "active # directory domain controller". # # Most people will want "standalone server" or "member server". # Running as "active directory domain controller" will require first # running "samba-tool domain provision" to wipe databases and create a # new domain. server role = standalone server obey pam restrictions = yes # This boolean parameter controls whether Samba attempts to sync the Unix # password with the SMB password when the encrypted SMB password in the # passdb is changed. unix password sync = yes # For Unix password sync to work on a Debian GNU/Linux system, the following # parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for # sending the correct chat script for the passwd program in Debian Sarge). passwd program = /usr/bin/passwd %u passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* . # This boolean controls whether PAM will be used for password changes # when requested by an SMB client instead of the program listed in # 'passwd program'. The default is 'no'. pam password change = yes # This option controls how unsuccessful authentication attempts are mapped # to anonymous connections map to guest = bad user ########## Domains ########### # # The following settings only takes effect if 'server role = classic # primary domain controller', 'server role = classic backup domain controller' # or 'domain logons' is set # # It specifies the location of the user's # profile directory from the client point of view) The following # required a [profiles] share to be setup on the samba server (see # below) ; logon path = \\%N\profiles\%U # Another common choice is storing the profile in the user's home directory # (this is Samba's default) # logon path = \\%N\%U\profile # The following setting only takes effect if 'domain logons' is set # It specifies the location of a user's home directory (from the client # point of view) ; logon drive = H: # logon home = \\%N\%U # The following setting only takes effect if 'domain logons' is set # It specifies the script to run during logon. The script must be stored # in the [netlogon] share # NOTE: Must be store in 'DOS' file format convention ; logon script = logon.cmd # This allows Unix users to be created on the domain controller via the SAMR # RPC pipe. The example command creates a user account with a disabled Unix # password; please adapt to your needs ; add user script = /usr/sbin/useradd --create-home %u # This allows machine accounts to be created on the domain controller via the # SAMR RPC pipe. # The following assumes a "machines" group exists on the system ; add machine script = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u # This allows Unix groups to be created on the domain controller via the SAMR # RPC pipe. ; add group script = /usr/sbin/addgroup --force-badname %g ############ Misc ############ # Using the following line enables you to customise your configuration # on a per machine basis. The %m gets replaced with the netbios name # of the machine that is connecting ; include = /home/samba/etc/smb.conf.%m # Some defaults for winbind (make sure you're not using the ranges # for something else.) ; idmap config * : backend = tdb ; idmap config * : range = 3000-7999 ; idmap config YOURDOMAINHERE : backend = tdb ; idmap config YOURDOMAINHERE : range = 100000-999999 ; template shell = /bin/bash # Setup usershare options to enable non-root users to share folders # with the net usershare command. # Maximum number of usershare. 0 means that usershare is disabled. # usershare max shares = 100 # Allow users who've been granted usershare privileges to create # public shares, not just authenticated ones usershare allow guests = yes #======================= Share Definitions ======================= # Un-comment the following (and tweak the other settings below to suit) # to enable the default home directory shares. This will share each # user's home directory as \\server\username ;[homes] ; comment = Home Directories ; browseable = no # By default, the home directories are exported read-only. Change the # next parameter to 'no' if you want to be able to write to them. ; read only = yes # File creation mask is set to 0700 for security reasons. If you want to # create files with group=rw permissions, set next parameter to 0775. ; create mask = 0700 # Directory creation mask is set to 0700 for security reasons. If you want to # create dirs. with group=rw permissions, set next parameter to 0775. ; directory mask = 0700 # By default, \\server\username shares can be connected to by anyone # with access to the samba server. # Un-comment the following parameter to make sure that only "username" # can connect to \\server\username # This might need tweaking when using external authentication schemes ; valid users = %S # Un-comment the following and create the netlogon directory for Domain Logons # (you need to configure Samba to act as a domain controller too.) ;[netlogon] ; comment = Network Logon Service ; path = /home/samba/netlogon ; guest ok = yes ; read only = yes # Un-comment the following and create the profiles directory to store # users profiles (see the "logon path" option above) # (you need to configure Samba to act as a domain controller too.) # The path below should be writable by all users so that their # profile directory may be created the first time they log on ;[profiles] ; comment = Users profiles ; path = /home/samba/profiles ; guest ok = no ; browseable = no ; create mask = 0600 ; directory mask = 0700 [printers] comment = All Printers browseable = no path = /var/tmp printable = yes guest ok = no read only = yes create mask = 0700 # Windows clients look for this share name as a source of downloadable # printer drivers [print$] comment = Printer Drivers path = /var/lib/samba/printers browseable = yes read only = yes guest ok = no # Uncomment to allow remote administration of Windows print drivers. # You may need to replace 'lpadmin' with the name of the group your # admin users are members of. # Please note that you also need to set appropriate Unix permissions # to the drivers directory for these users to have write rights in it ; write list = root, @lpadmin [data] path = /mnt/data read only = no browseable = yes writeable = yes create mask = 0777 directory mask = 0777 I've inserted the global settings as found in the wiki and an entry [data] for the share as above. I can now see the share from windows but could not connect due to a windows security policy for guest users. I therefore ran sudo smbpasswd -a your_username to add the local user to samba. This allowed me to connect to the share using the local user account. However i have two issues:- 1) Whilst i can browse the share I cannot write to it from windows. 2) There is a second share named guest which has appeared. See (attachment) I can only think this is something to do with the global entry at the beginning of the smb.conf? Which entry should i remove from smb.conf to remove this share (everything in [guest] ?? ) as clearly guest only access is not working from windows. As regards writing to the share I have tried running chmod -R 777 /mnt/data/ this appears to finish without errors but I still cannot write to the share from windows. Could this be because the file system is exFat? If I try and convert the partition to Ext4 then I need to run gnome-disks as Sudo and afterwards I still cannot access the share on the pi with the local user permissions. I am therefore stuck. Any suggestions as to change the permissions to allow write access to the share please?

I tried to build a image from the current main branch (kernel: 6.18.20) and I found the problem is the same. I changed KERNELBRANCH to "tag:v6.18.18" from "branch:linux-6.18.y" and rebuild. It can boot to desktop as expected. It seems some change in the 6.18.19 kernel causes the problem

What happened? I used image https://github.com/armbian/community/releases/download/26.2.0-trunk.606/Armbian_community_26.2.0-trunk.606_Ayn-odin2_noble_current_6.18.19_gnome_desktop.img.xz and I found the device cannot boot into desktop. It stuck in the first boot wizard after message "Please use this account for your daily work from now on." How to reproduce? Download image from https://github.com/armbian/community/releases/download/26.2.0-trunk.606/Armbian_community_26.2.0-trunk.606_Ayn-odin2_noble_current_6.18.19_gnome_desktop.img.xz Flash it to TF card using Armbian Imager Insert the TF card to Odin2 device and power on Wait for it to boot to desktop Observation: It stuck in the first boot wizard after message "Please use this account for your daily work from now on."

Thanks I got it.

Found an error in the "use proprietary GPU driver for Spacemit K1" script. Because I cannot edit here is the corrected install script. spacemit-gpu-addon.sh

Samba has one gazillion options, you can read about all of them here: https://www.samba.org/samba/docs/current/man-html/smb.conf.5.html You can read the wiki with examples here: https://wiki.samba.org/index.php/Setting_up_Samba_as_a_Standalone_Server I would NOT use a samba server without a password.

I built an Ubuntu current image, as of commit f15f594d0bd4ad1e5d0fa412f1d25120e76e4f9a (Armbian-unofficial_26.05.0-trunk_Bigtreetech-cb1_noble_current_6.18.20.img) and started my newly arrived Pad 7 from it. Things that work out of the box: display, touchscreen, wifi, USB. Not working: LAN is not visible at all (only two wlan interfaces). Also, no audio device. According to schematics, audio is taken from HDMI output, so it should be supported by standard HDMI drivers. Where do I enable it in kernel config? https://github.com/bigtreetech/Pad7/tree/master/Hardware your hints will be appreciated. smartkbd@bigtreetech-cb1:~$ wpctl status PipeWire 'pipewire-0' [1.0.5, smartkbd@bigtreetech-cb1, cookie:3329793852] └─ Clients: 32. pipewire [1.0.5, smartkbd@bigtreetech-cb1, pid:1127] 34. WirePlumber [1.0.5, smartkbd@bigtreetech-cb1, pid:1126] 35. WirePlumber [export] [1.0.5, smartkbd@bigtreetech-cb1, pid:1126] 43. wpctl [1.0.5, smartkbd@bigtreetech-cb1, pid:2162] Audio ├─ Devices: │ ├─ Sinks: │ * 33. Dummy Output [vol: 1.00] │ ├─ Sink endpoints: │ ├─ Sources: │ ├─ Source endpoints: │ └─ Streams: Video ├─ Devices: │ ├─ Sinks: │ ├─ Sink endpoints: │ ├─ Sources: │ ├─ Source endpoints: │ └─ Streams: Settings └─ Default Configured Node Names:

I have 3 Aceline AG-216 consoles. Help me find the right image for her. QHZIW_H313_A3_2LP4. V2.0 20240603 EA6521QF 2+16G

Example for adding a new board with already existing board family: https://github.com/armbian/build/pull/9456/changes

Maybe. Trunk are untested auto-builds and support for this board is from the community. Its functionality is unknown to the Armbian team. Get serial console logs. This makes investigation way easier.

Try running a2jmidid with pw-jack a2jmidid first — that bridges ALSA MIDI to JACK MIDI, and then use pw-link or qpwgraph to connect your app's MIDI input to the resulting Midi-Bridge ports

I was able to run Steam games with GPU accelerated ofc. But since my Opi5 only has 8Gb, I mainly run non-Steam games. I can see your SBC has 32Gb, so you are good. I assume your game is 64-bit DX11. Change the Steam Play compatible layer to "GE-proton". Download Dxvk-stripped here: https://github.com/khanh-it/dxvk/releases/tag/releases Copy x64/d3d11.dll, x64/dxgi.dll to the <<game>>.exe folder. Then run the game with a command like so: