-
Posts
1148 -
Joined
-
Last visited
Posts posted by lanefu
-
-
4K is hard. I gave up on it.
Try this conf but remove the screen section to make sure you're at least using the drm display driver
https://raw.githubusercontent.com/armbian/build/master/packages/bsp/pinebook-pro/xorg.conf
-
I want a stripped down board that has real 802.3af POE
-
-
9 minutes ago, arox said:
Using an overkilled dynamic system configuration system like udev to make a static configuration is somewhere strange ..
I think udev is appropriate.. its a situation that could just as easily be needed on a x86 machine w/o device tree to enforce enumeration -
2 hours ago, arox said:
The method "filtering by devpath" I have indicated before is targeted at providing a solution in that case. The match is done for a type of (identical) devices (same idVendor/idProduct) and the device name chosen according to the index of USB port.
This is great! I had a similar problem to solve
-
FYI keep an eye on this PR from @rpardini provides more customization opportunities. (I know this doesn't address the 32bit use space stuff, but seemed relevant to share
)
https://github.com/armbian/build/pull/2799 -
6 hours ago, tparys said:
# mount /dev/mapper/loop9p1 /dev/shm/original
ha I love the idea of mounting to /dev/shm .. clever.. I always just made a dummy folder from /mnt -
2 hours ago, Jeremiah Cornelius said:
n the background are plans for ready-to-run Armbian VIM images with Budgie desktop and Elementary OS, pre-built. Being unsupported, some of these may advance from Focal to Groovy or Hirsute.
BTW have you played with https://github.com/armbian/build. We have budgie I there, and would gladly take help there as well
..but you're doing 32bit userspace? -
5 hours ago, Jeremiah Cornelius said:
I'd like the unit disabled, and maybe a re-settable flag written to the image, preventing accidental firstrun.
Yeah first run has a few distributed touchpoint.. kind of needs to be consolidated and more intuitive to manage as you describe.. I know many have interest in being able to bundle in cloud-init to the image.. and making the first-riun and first-login components a little more polished would help with that. -
4 hours ago, Jeremiah Cornelius said:
Results: New ssh keys are generated, and new UUID appended to /etc/armbian-image-release - no other config tasks are run (update root pw, create normal user, choose logon environment, etc)
Doing this should probably trigger it. https://github.com/armbian/build/blob/master/lib/distributions.sh#L157
Also take a look at
https://github.com/armbian/build/blob/master/lib/distributions.sh#L372-L379
QuoteObservation: /usr/lib/systemd/system/armbian-firstrun-config is deleted after being enabled, on next boot.
Is this expected behavior?
Is it an error in how symlinks under /etc/systemd are handled?
Might be related to https://github.com/armbian/build/blob/master/packages/bsp/common/lib/systemd/system/armbian-firstrun-config.service#L95 hours ago, Jeremiah Cornelius said:Would an issue on the git repository be well received?
Probably best to keep conversation here for now. Mostly we use issues in GitHub for major bugs / problems -
3 hours ago, Jeremiah Cornelius said:
After a couple of days, this seems to be a stumper.
I'd wish that this, an essential piece of Armbian configuration and operation, were documented as well as the image building process!
Can you just give me some quick bullet points on what you're waiting to achieve... I may have an answer. -
Yep you need at least ubuntu 20.04.
-
10 hours ago, J.M. said:
Hi all,
Which branch or tag should I use if I'm willing to work on the latest stable linux version on Banana Pi M1 ?
How do I choose between legacy / current / dev, and what are the differences between them ?
Is there some guide that explain these issues ?
If someone is willing to answer by giving an example, then lets assume I want to build from source kernel 5.10.32 on Banana Pi M1.
Thanks in advance
if you wanted to build last stable release that would be
LIB_TAG=v21.02.. but you probably just want to stick with building from MASTER and use "current" as your kernel branch. -
you can try uninstalling. FYI iptables is a wrapper for nftables in modern kernels.
-
to @arox's point.. MQTT is a good fit for this.
Mosquito is easy to install.
Here's an example of doing something similar.. with a different library
Spoilerimport OPi.GPIO as gpio
import logging#import RPi.GPIO as GPIO
import dht22
import time
import datetime
import paho.mqtt.client as mqtt
import os
#import config
import time
import sys, getopt
import logging
import queue
import random
import sys
from configparser import ConfigParser
import jsondef on_connect(client, userdata, flags, rc):
if rc==0:
print("connected ok")config = ConfigParser(delimiters=('=', ))
config.read('config.ini')
topic = config['mqtt'].get('topic', 'temperature/dht22')
decim_digits = config['sensor'].getint('decimal_digits', 2)
sleep_time = config['sensor'].getint('interval', 60)decim_digits = config['sensor'].getint('decimal_digits', 2)
sleep_time = config['sensor'].getint('interval', 60)client = mqtt.Client()
client.username_pw_set(config['mqtt'].get('user'), password=config['mqtt'].get('password'))
client.on_connect = on_connect
client.connect(config['mqtt'].get('hostname', 'homeassistant'),
config['mqtt'].getint('port', 1883),
config['mqtt'].getint('timeout', 60))
client.loop_start()# initialize GPIO
#gpio.setwarnings(False)
gpio.setboard(gpio.PRIME)
gpio.setmode(gpio.SOC)
#PIN2 = port.PA13
pin = gpio.PA + 10
#gpio.cleanup()gpio.setup(pin, gpio.IN, pull_up_down=gpio.PUD_OFF)
# read data using pin 14
instance = dht22.DHT22(pin)while True:
result = instance.read()
if result.is_valid():
fResult = ( result.temperature * (9 / 5) + 32)
print("Last valid input: " + str(datetime.datetime.now()))
print("Temperature: %.2f C" % result.temperature)
#im an American
print("Temperature: %.2f F" % fResult)
print("Humidity: %.2f %%\n" % result.humidity)
client.publish(topic + "/humidity", str(result.humidity))
client.publish(topic + "/temperature", f"{fResult:.2f}")
time.sleep(15)
-
FYI The house-brand Ameridroid eMMC chips work without issue on my pineh64-b. Didn't make any adjustments to dts etc. Running kernel 5.10.21-sunxi64
https://ameridroid.com/products/emmc-5-1-module-blank?_pos=3&_sid=086ab1282&_ss=r -
Here's an example of adding RT patches to allwinner build.
https://github.com/lanefu/build/commits/RTAttempt -
-
yeah... it seems like network issue.. or something. need @Igor to look on his side..
I read concurrency can cause problems.. so I made some adjustments so that it only does 2 sessions.. but still getting errorSpoilersend packet: EOF
Apr 12 15:00:52 worksonarmbian.armbian.com systemd[1]: armbian_users_sync_balbes150.service: Current command vanished from the unit file, execution of the command list won't be resumed.
Apr 12 15:00:55 worksonarmbian.armbian.com systemd[1]: armbian_users_sync_balbes150.service: Succeeded.
Apr 12 15:01:00 worksonarmbian.armbian.com systemd[1]: Started "Sync /home/balbes150/users_armbian_com_upload".
Apr 12 15:01:03 worksonarmbian.armbian.com rclone[3290808]: INFO : sftp://balbes150@users.armbian.com:22/web/: Running all checks before starting transfers
Apr 12 15:01:13 worksonarmbian.armbian.com rclone[3290808]: INFO : sftp://balbes150@users.armbian.com:22/web/: Checks finished, now starting transfers
Apr 12 15:02:04 worksonarmbian.armbian.com rclone[3290808]: INFO : 11.305M / 22.565 GBytes, 0%, 228.470 kBytes/s, ETA 1d4h45m10s (xfr#0/45)
Apr 12 15:02:18 worksonarmbian.armbian.com rclone[3290808]: ERROR : jetson-nano/Armbian_21.05.0-trunk_Jetson-nano_buster_current_5.10.29_xfce_desktop.img.xz: Failed to copy: Update ReadFrom failed: failed to send packet: EOF
Apr 12 15:02:18 worksonarmbian.armbian.com rclone[3290808]: ERROR : jetson-nano/Armbian_21.05.0-trunk_Jetson-nano_focal_current_5.10.29.img.xz: Failed to copy: Update ReadFrom failed: failed to send packet: EOF
Apr 12 15:03:03 worksonarmbian.armbian.com rclone[3290808]: INFO : 23.359M / 21.449 GBytes, 0%, 216.143 kBytes/s, ETA 1d4h52m23s (xfr#0/43)
Apr 12 15:03:23 worksonarmbian.armbian.com rclone[3290808]: ERROR : jetson-nano/Armbian_21.05.0-trunk_Jetson-nano_hirsute_current_5.10.29.img.xz: Failed to copy: Update ReadFrom failed: failed to send packet: EOF
Apr 12 15:03:23 worksonarmbian.armbian.com rclone[3290808]: ERROR : jetson-nano/Armbian_21.05.0-trunk_Jetson-nano_focal_current_5.10.29_xfce_desktop.img.xz: Failed to copy: Update ReadFrom failed: failed to send packet: EOF
Apr 12 15:04:03 worksonarmbian.armbian.com rclone[3290808]: INFO : 35.820M / 20.443 GBytes, 0%, 214.922 kBytes/s, ETA 1d3h39m27s (xfr#0/41)
Apr 12 15:04:28 worksonarmbian.armbian.com rclone[3290808]: ERROR : jetson-nano/Armbian_21.05.0-trunk_Jetson-nano_sid_current_5.10.29.img.xz: Failed to copy: Update ReadFrom failed: failed to send packet: EOF
Apr 12 15:04:28 worksonarmbian.armbian.com rclone[3290808]: ERROR : jetson-nano/Armbian_21.05.0-trunk_Jetson-nano_buster_current_5.10.29.img.xz: Failed to copy: Update ReadFrom failed: failed to send packet: EOF
Apr 12 15:05:03 worksonarmbian.armbian.com rclone[3290808]: INFO : 47.812M / 19.797 GBytes, 0%, 212.254 kBytes/s, ETA 1d3h6m11s (xfr#0/39)
Apr 12 15:05:33 worksonarmbian.armbian.com rclone[3290808]: ERROR : renegade/Armbian_21.05.0-trunk_Renegade_buster_current_5.10.29.img.xz: Failed to copy: Update ReadFrom failed: failed to send packet: EOF
Apr 12 15:05:33 worksonarmbian.armbian.com rclone[3290808]: ERROR : renegade/Armbian_21.05.0-trunk_Renegade_buster_current_5.10.29_xfce_desktop.img.xz: Failed to copy: Update ReadFrom failed: failed to send packet: EOF
Apr 12 15:06:04 worksonarmbian.armbian.com rclone[3290808]: INFO : 60.180M / 18.530 GBytes, 0%, 212.008 kBytes/s, ETA 1d1h22m36s (xfr#0/37)
Apr 12 15:06:38 worksonarmbian.armbian.com rclone[3290808]: ERROR : renegade/Armbian_21.05.0-trunk_Renegade_buster_legacy_4.4.194_xfce_desktop.img.xz: Failed to copy: Update ReadFrom failed: failed to send packet: EOF
Apr 12 15:06:38 worksonarmbian.armbian.com rclone[3290808]: ERROR : renegade/Armbian_21.05.0-trunk_Renegade_focal_current_5.10.29.img.xz: Failed to copy: Update ReadFrom failed: failed to send packet: EOF
Apr 12 15:07:04 worksonarmbian.armbian.com rclone[3290808]: INFO : 72.578M / 17.391 GBytes, 0%, 211.938 kBytes/s, ETA 23h48m9s (xfr#0/35)
Apr 12 15:07:43 worksonarmbian.armbian.com rclone[3290808]: ERROR : renegade/Armbian_21.05.0-trunk_Renegade_focal_current_5.10.29_xfce_desktop.img.xz: Failed to copy: Update ReadFrom failed: failed to send packet: EOF
Apr 12 15:07:43 worksonarmbian.armbian.com rclone[3290808]: ERROR : renegade/Armbian_21.05.0-trunk_Renegade_hirsute_current_5.10.29.img.xz: Failed to copy: Update ReadFrom failed: failed to send packet: EOF
Apr 12 15:08:03 worksonarmbian.armbian.com rclone[3290808]: INFO : 84.883M / 16.326 GBytes, 1%, 211.655 kBytes/s, ETA 22h21m11s (xfr#0/33)
Apr 12 15:08:48 worksonarmbian.armbian.com rclone[3290808]: ERROR : renegade/Armbian_21.05.0-trunk_Renegade_sid_current_5.10.29.img.xz: Failed to copy: Update ReadFrom failed: failed to send packet: EOF
Apr 12 15:08:48 worksonarmbian.armbian.com rclone[3290808]: ERROR : aw-h6-tv/Armbian_21.05.0-trunk_Aw-h6-tv_buster_current_5.10.29.img.xz: Failed to copy: Update ReadFrom failed: failed to send packet: EOF
Apr 12 15:09:03 worksonarmbian.armbian.com rclone[3290808]: INFO : 96.906M / 15.634 GBytes, 1%, 210.832 kBytes/s, ETA 21h28m6s (xfr#0/31) -
4 hours ago, balbes150 said:
@lanefu It looks like the synchronization is broken.
Yeah weird error messageSpoilerpr 12 13:16:24 worksonarmbian.armbian.com rclone[2558396]: Elapsed time: 9m3.9s
Apr 12 13:16:24 worksonarmbian.armbian.com rclone[2558396]: Transferring:
Apr 12 13:16:24 worksonarmbian.armbian.com rclone[2558396]: * jetson-nano/Armbian_21…current_5.10.29.img.xz: 2% /238.977M, 115.268k/s, 34m22s
Apr 12 13:16:24 worksonarmbian.armbian.com rclone[2558396]: * jetson-nano/Armbian_21…29_xfce_desktop.img.xz: 0% /782.986M, 111.006k/s, 1h59m21s
Apr 12 13:16:24 worksonarmbian.armbian.com rclone[2558396]: * jetson-nano/Armbian_21…current_5.10.29.img.xz: 2% /260.381M, 115.042k/s, 37m37s
Apr 12 13:16:24 worksonarmbian.armbian.com rclone[2558396]: * jetson-nano/Armbian_21…current_5.10.29.img.xz: 2% /338.123M, 119.849k/s, 47m9s
Apr 12 13:16:29 worksonarmbian.armbian.com rclone[2558396]: ERROR : jetson-nano/Armbian_21.05.0-trunk_Jetson-nano_focal_current_5.10.29.img.xz: Failed to copy: Update ReadFrom failed: failed to send packet: EOF
Apr 12 13:16:30 worksonarmbian.armbian.com rclone[2558396]: ERROR : jetson-nano/Armbian_21.05.0-trunk_Jetson-nano_hirsute_current_5.10.29.img.xz: Failed to copy: Update ReadFrom failed: Connection Lost
Apr 12 13:16:30 worksonarmbian.armbian.com rclone[2558396]: ERROR : jetson-nano/Armbian_21.05.0-trunk_Jetson-nano_focal_current_5.10.29_xfce_desktop.img.xz: Failed to copy: Update ReadFrom failed: failed to send packet: EOF
Apr 12 13:16:30 worksonarmbian.armbian.com rclone[2558396]: ERROR : jetson-nano/Armbian_21.05.0-trunk_Jetson-nano_sid_current_5.10.29.img.xz: Failed to copy: Update ReadFrom failed: failed to send packet: EOF
Apr 12 13:17:24 worksonarmbian.armbian.com rclone[2558396]: INFO :
Apr 12 13:17:24 worksonarmbian.armbian.com rclone[2558396]: Transferred: 240.454M / 2.878 GBytes, 8%, 414.604 kBytes/s, ETA 1h51m24s
Apr 12 13:17:24 worksonarmbian.armbian.com rclone[2558396]: Errors: 32 (retrying may help)
Apr 12 13:17:24 worksonarmbian.armbian.com rclone[2558396]: Checks: 32 / 32, 100%
Apr 12 13:17:24 worksonarmbian.armbian.com rclone[2558396]: Transferred: 7 / 13, 54%
Apr 12 13:17:24 worksonarmbian.armbian.com rclone[2558396]: Elapsed time: 10m3.9s
Apr 12 13:17:24 worksonarmbian.armbian.com rclone[2558396]: Transferring:
Apr 12 13:17:24 worksonarmbian.armbian.com rclone[2558396]: * rk3288/Armbian_21.05.0…current_5.10.29.img.xz: 1% /283.066M, 115.071k/s, 41m9s
Apr 12 13:17:24 worksonarmbian.armbian.com rclone[2558396]: * rk3288/Armbian_21.05.0…29_xfce_desktop.img.xz: 0% /888.227M, 119.986k/s, 2h5m27s
Apr 12 13:17:24 worksonarmbian.armbian.com rclone[2558396]: * rk3288/Armbian_21.05.0…current_5.10.29.img.xz: 2% /226.541M, 119.959k/s, 31m20s
Apr 12 13:17:24 worksonarmbian.armbian.com rclone[2558396]: * rk3288/Armbian_21.05.0…29_xfce_desktop.img.xz: 0% /770.747M, 114.984k/s, 1h53m35s
Apr 12 13:17:36 worksonarmbian.armbian.com rclone[2558396]: ERROR : rk3288/Armbian_21.05.0-trunk_Rk3288_buster_current_5.10.29.img.xz: Failed to copy: Update ReadFrom failed: failed to send packet: EOF
Apr 12 13:17:36 worksonarmbian.armbian.com rclone[2558396]: ERROR : rk3288/Armbian_21.05.0-trunk_Rk3288_buster_current_5.10.29_xfce_desktop.img.xz: Failed to copy: Update ReadFrom failed: failed to send packet: EOF
Apr 12 13:17:36 worksonarmbian.armbian.com rclone[2558396]: ERROR : rk3288/Armbian_21.05.0-trunk_Rk3288_focal_current_5.10.29_xfce_desktop.img.xz: Failed to copy: Update ReadFrom failed: failed to send packet: EOF
Apr 12 13:17:36 worksonarmbian.armbian.com rclone[2558396]: ERROR : rk3288/Armbian_21.05.0-trunk_Rk3288_focal_current_5.10.29.img.xz: Failed to copy: Update ReadFrom failed: failed to send packet: EOF -
maintenance complete
-
Gonna patch and reboot forum server at 10PM my time. (US EAST)
should be quick.. assuming no surprises
-
13 minutes ago, Igor said:
This time it was first time that also this responsibility was not mine
Didn't I do the 2nd one?
maybe it was just the thread
-
6 hours ago, balbes150 said:
Sorry I didn't get it, wedding chores.
Congratulations! Are you marrying S905X?

Armbian v21.05 (Jerboa) Release Thread
in Armbian build framework
Posted
Yeah we ususlly ssh in on first boot so wouldn't see that. But yes its only cosmetic and you could just press enter and proceed as normal
If you are particular about your system and avoiding changes you may want to freeze the kernel on your 21.02 install via armbian-config
Add jira task https://armbian.atlassian.net/browse/AR-743