lanefu

  • Posts

    1148
  • Joined

  • Last visited

Everything posted by lanefu

  1. There's consistency on the port ids of the hub im plugging into. Ill add some more samples
  2. Re: binfmt. if using lxc the container. you need to execute it with more priviledges if you are already, or are using lxc the VM your kernel needs to be ubuntu's -generic kernel rather than the -virtual kernel... -virtual doesn't have binfmt support in it the last time I checked. misc building tips.. I personally hate the LIB_TAG thing.. and prefer to just force it to use whatever branch I'm using.. here's a hint for that https://docs.armbian.com/Developer-Guide_Build-Preparation/#using-alternate-armbian-builder-repos-and-branches How to build from the kernel source you want and love armbian builder As we mentioned. it's not that the armbian build checkout has changed the minor release. it's that the upstream has (it's a weakness we have). So you're going to want to specify your own kernel branch/commit/target etc by hand. https://docs.armbian.com/Developer-Guide_Build-Preparation/#using-alternate-armbian-builder-repos-and-branches So step 1.. we need to figure out what "family" your odroidn2 is lane@billroyall:~/GIT/build$ fgrep -i FAMILY config/boards/odroidn2.conf BOARDFAMILY="meson-g12b" okay.. it's part of the meson-g12b family https://github.com/armbian/build/blob/master/config/sources/families/meson-g12b.conf#L1 hmmmm ---- code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } source "${BASH_SOURCE%/*}/include/meson64_common.inc" okay lets look at its common include https://github.com/armbian/build/blob/master/config/sources/families/include/meson64_common.inc#L30-L32 code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } branch:linux-5.10.y alright so.. it's just following the linux-5.10.y branch.. hence the minor release update.... and since no explicit kernel source is specified.. we can assuming it's using the default mainline https://github.com/armbian/build/blob/master/lib/configuration.sh#L86 which means hunting here https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/?h=linux-5.10.y https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tag/?h=v5.10.43 and lucky for us there's a tag so in theory you should be able to create the file code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } userpatches/sources/meson-g12b.conf with the contents of KERNELBRANCH=tag:v5.10.43
  3. @rob which board are you building for? Most of our kernel versions are bound to upstream tags or branches. Minor release versions do tend to change.
  4. Please confirm IP forwarding is enabled https://linuxconfig.org/how-to-turn-on-off-ip-forwarding-in-linux
  5. there's a lot of variables with the internet involved.. but you could try scaling down MTU size.. or test inside a VPN
  6. We also have our SBC test rigs which have GPIO power control. I've proven out the general process of SSHing into a board, doing `curl -s http://path/to/armbian.omg | dd of=/dev/blockdev bs=1M conv=fsync` and then immediately cutting power as a 90% reliable process for applying images. I really want to tie this library. https://github.com/lanefu/sbc-gpio-pcf857x/blob/main/lib/gpio.sh with ansible and our netbox inventory to find board and gpio on our pdu. I have POC of ansible inventory We also have an armbian ansible collection which currently has a facts module for identifying armbian specifics in /etc/armbian-release https://github.com/armbian/ansible-collection-armbian We have lots of great pieces now we need to glue them together!
  7. I have a bunch of UARTS attached to a USB hub, and I need to map them consistent to /dev/ttyUSB[x] I've done some mapping of the ports. but I don't quite know what I'm doing.. any help with some example rules would be great.. here's a sample /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/1p, 480M ID 1d6b:0002 Linux Foundation 2.0 root hub |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M ID 05e3:0608 Genesys Logic, Inc. Hub |__ Port 3: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M ID 05e3:0608 Genesys Logic, Inc. Hub |__ Port 4: Dev 4, If 0, Class=Vendor Specific Class, Driver=ch341, 12M ID 1a86:7523 QinHeng Electronics CH340 serial converter
  8. Cleaned up and sorted Jira Board https://armbian.atlassian.net/secure/RapidBoard.jspa?rapidView=2&selectedIssue=AR-572&atlOrigin=eyJpIjoiY2FjZTM3YjZmZDI2NDI0MmIzY2MzYzdmYzg3Nzc1YjIiLCJwIjoiaiJ9
  9. ah yeah.. true.... I meant the pluggable emmc modules on the Tritium-Hx boards
  10. yeah honestly I doubt any of us have tried emmc on the H5....
  11. Testing RC images when we make them.. testing nightlies now.. test upgrading stable images to nightly packages etc.
  12. is a emmc v4 module? Allwinner H3 and h5 doesn't' support v5
  13. Actually this isnt docker issue. This is our vnstat install and motd making noise. Because of the new interface created by docker
  14. Yeah ultimately the rock64v2 is an unstable board. Armbian is using a mainline linux kernel and will have fewer "workarounds" than an ayufan build from a bsp kernel
  15. so I did see interrupt stuff regarding the NIC. I don't know exactly what it means.. but look here for inspiration on knobs to turn https://github.com/armbian/build/blob/master/packages/bsp/common/usr/lib/armbian/armbian-hardware-optimization#L145
  16. Lol id be looking for less page allocation errors. Hard to tell. Is memory consumption tight?
  17. probably follow dmesg -w -T from serial console or tee into log file
  18. Release Candidate Code Freeze Date: 2021-07-18. (Fixes only afterwards) Release Planning Meeting Date: 2021-07-10 1400GMT Release Date: 2021-08-08 Release Candidate Branch Link: TBD Release Changelog: TBD Release Coordinator: @lanefu Testing Tracking Sheet: TBD (google sheets) The purpose of this thread is to discuss testing, bugfixes, and the overall quality of the release. Once the release is complete, this thread should be locked and unpinned. Please subscribe to this thread! I want this release to focus on upgrade stability. That means we need to strongly focus on: * kernel packages * rootfs packages * u-boot updates * -current kernel remains on 5.10LTS! * testing * testing * TESTING Please share you priorities, thoughts, etc in this thread... Any format is fine.. post, GitHub link, jira issue. help me menton peeps plz. @Igor@Werner @TonyMac32 @martinayotte@piter75 @ning@Myy@balbes150 @sfx2000 @ebin-dev@chwe@gprovost@aprayoga@5kft@JMCC@going@jeanrhum@dolphs @jock@belfastraven@TRS-80@Bozza@Rich Neese@sgjava@Mangix@tony013
  19. In case its help i made a helper script for managing relays https://github.com/lanefu/sbc-gpio-pcf857x