Jump to content

Heisath

  • Posts

    286
  • Joined

  • Last visited

Reputation Activity

  1. Like
    Heisath got a reaction from lanefu in Armbian 22.05 (Jade) Release Thread   
    I will run mvebu tests tomorrow. Sorry for not being available for the meeting, turns out, building a house is a pretty major thing...
  2. Like
    Heisath got a reaction from Werner in Armbian 22.05 (Jade) Release Thread   
    I will run mvebu tests tomorrow. Sorry for not being available for the meeting, turns out, building a house is a pretty major thing...
  3. Like
    Heisath got a reaction from Igor in In some forums tagging has been enforced   
    No I do not think so. The hardware is nearly the same - base is just pro with removed devices.
  4. Like
    Heisath got a reaction from Willy Moto in Armbian 22.02 (Pig) Release Thread   
    Release Candidate Code Freeze Date: 2022-02-14
    Release Planning Meeting Date:  2022-01-29 14:00 UTC+1 
    Release Planning Meeting Location: Armbian IRC
    Release Date: 2022-02-28
    Release Branch Link: https://github.com/armbian/build/tree/v22.02
    Release Changelog:
     
     
    Release Coordinator: @Heisath and hopefully some new person on the team
     
    Already creating this release topic for 22.02, to discuss upcoming changes, no longer maintained boards and help new people get into the release / maintain flow.
     
    Current steps:
    - Refine supported/WIP/CSC/etc. board status
    - Update maintainer list
    - Onboard new maintainers / contributors
    - Move Jira issues to new release
    - Select release name 
     
    @Igor @Werner @TonyMac32 @martinayotte @piter75 @ning @Myy @balbes150 @sfx2000 @ebin-dev @chwe  @gprovost @aprayoga @lanefu @5kft @JMCC @going @jeanrhum @dolphs @jock @belfastraven @TRS-80 @Bozza @Rich Neese @sgjava @Mangix @tony013  @rpardini
     
    Pls. ping developers I forgot  
  5. Like
    Heisath got a reaction from lanefu in Armbian 22.02 (Pig) Release Thread   
    If possible it would be great if all maintainers could send a PR with fixed tag for kernel source.
    Follow this PR https://github.com/armbian/build/pull/3500
    This would allow for more reproducible builds.
     
    This together with Igors suggestion of merging 
    https://github.com/armbian/build/pull/3489
    https://github.com/armbian/build/pull/3499
    could go into a new RC branch.
     
     
    @Contributor/Maintainer
     
  6. Like
    Heisath got a reaction from lanefu in Making EspressoBin V7 work in 2022 ...   
    I created branch with Ebin improvements and PR https://github.com/armbian/build/pull/3498
     
    This is still WIP. Feedback + help welcome. 
     
    Currently building TF-A fails because:
     
    plat/marvell/armada/a3k/common/a3700_common.mk:148: *** "Platform 'a3700' for WTP image tool requires CRYPTOPP_PATH or CRYPTOPP_LIBDIR. Please set CRYPTOPP_PATH or CRYPTOPP_LIBDIR to point to the right directory". Stop.  
     
    Got it working, see https://github.com/armbian/build/pull/3498 
    Compilation seems to work now. Waiting on feedback from ebin owners.
     
    armbianEnv.txt still needs adjustment!
  7. Like
    Heisath got a reaction from lanefu in Armbian 22.02 (Pig) Release Thread   
    Release candidate has been branched off. Please direct all bugfixes to 'master' AND 'v22.02-RC'.  Please build, test etc. the RC branch. 
     
    https://github.com/armbian/build/tree/v22.02-RC
  8. Like
    Heisath got a reaction from lanefu in Armbian 22.02 (Pig) Release Thread   
    Today is code freeze day. *ice*
    I am currently testing mvebu 5.15 + 5.16 - afterwards I will do the code freeze / RC branch.
     
    Is anyone still working on something important, that should go into this release / RC ?
     
    @private/contributor
    @Contributor/Maintainer
  9. Like
    Heisath got a reaction from Myy in Armbian 22.02 (Pig) Release Thread   
    Reminder! The release meeting is happening this saturday 14:00 UTC+1 (which is 13:00 UTC or 8 am EST or 2 pm CET or 5 am PST (sorry california dudes) or 9 pm CST).
     
    I will look through the Jira issues remaining today. Would be great if you could check them too and add the ones you have finished (or are planning to include in 22.02) to the release.
     
    @Igor @Werner @TonyMac32 @martinayotte @piter75 @ning @Myy @balbes150 @sfx2000 @ebin-dev @chwe @gprovost @aprayoga @lanefu @5kft @JMCC @going @jeanrhum @dolphs @jock @belfastraven @TRS-80 @Bozza @Rich Neese @sgjava @Mangix @tony013 @rpardini @yang @adeepn
  10. Like
    Heisath got a reaction from JMCC in Armbian 22.02 (Pig) Release Thread   
    Reminder! The release meeting is happening this saturday 14:00 UTC+1 (which is 13:00 UTC or 8 am EST or 2 pm CET or 5 am PST (sorry california dudes) or 9 pm CST).
     
    I will look through the Jira issues remaining today. Would be great if you could check them too and add the ones you have finished (or are planning to include in 22.02) to the release.
     
    @Igor @Werner @TonyMac32 @martinayotte @piter75 @ning @Myy @balbes150 @sfx2000 @ebin-dev @chwe @gprovost @aprayoga @lanefu @5kft @JMCC @going @jeanrhum @dolphs @jock @belfastraven @TRS-80 @Bozza @Rich Neese @sgjava @Mangix @tony013 @rpardini @yang @adeepn
  11. Like
    Heisath got a reaction from jock in Armbian 22.02 (Pig) Release Thread   
    Reminder! The release meeting is happening this saturday 14:00 UTC+1 (which is 13:00 UTC or 8 am EST or 2 pm CET or 5 am PST (sorry california dudes) or 9 pm CST).
     
    I will look through the Jira issues remaining today. Would be great if you could check them too and add the ones you have finished (or are planning to include in 22.02) to the release.
     
    @Igor @Werner @TonyMac32 @martinayotte @piter75 @ning @Myy @balbes150 @sfx2000 @ebin-dev @chwe @gprovost @aprayoga @lanefu @5kft @JMCC @going @jeanrhum @dolphs @jock @belfastraven @TRS-80 @Bozza @Rich Neese @sgjava @Mangix @tony013 @rpardini @yang @adeepn
  12. Like
    Heisath got a reaction from Igor in Armbian 22.02 (Pig) Release Thread   
    I would still go on with the February release, we skipped last one, lets get this one done.
     
    Am targeting 2022-01-29 (Saturday, 29 of January 2022) for release meeting, and then about 4 weeks later 2022-02-25 (Friday, 25 of February 2022) for actual release. 
    Release meeting earlier than 2022-01-25 is not possible from my calendar.
     
     
  13. Like
    Heisath got a reaction from aaditya in armbian upgrade from buster to bullseye   
    I did the upgrade from Buster to Bullseye. 
     
    As far as steps:
    - Backup
    - apt update & full-upgrade
    - Disable /etc/apt/sources.list.d/armbian.list all entries to stop armbian from upgrading
    - Use normal debian upgrade steps -> Change release in /etc/apt/sources.list 
    - apt update & full-upgrade
    - Restart, validate working system
    - Update /etc/apt/sources.list.d/armbian.list with new release (buster->bullseye)
    - apt update & full-upgrade
    - Should be done. 
     
    Take extra care for some new/renamed packages. armbian-bsp-cli-<BOARD> is new. Older armbian-root-* packages dont exist anymore (I think).
     
    For me this worked flawless, you might have to fix some dependency problems, and make sure at least some working version of armbian-image-* armbian-dtb-* is installed before rebooting.
  14. Like
    Heisath got a reaction from Werner in Armbian 22.02 (Pig) Release Thread   
    I would still go on with the February release, we skipped last one, lets get this one done.
     
    Am targeting 2022-01-29 (Saturday, 29 of January 2022) for release meeting, and then about 4 weeks later 2022-02-25 (Friday, 25 of February 2022) for actual release. 
    Release meeting earlier than 2022-01-25 is not possible from my calendar.
     
     
  15. Like
    Heisath got a reaction from lanefu in Armbian 22.02 (Pig) Release Thread   
    I would still go on with the February release, we skipped last one, lets get this one done.
     
    Am targeting 2022-01-29 (Saturday, 29 of January 2022) for release meeting, and then about 4 weeks later 2022-02-25 (Friday, 25 of February 2022) for actual release. 
    Release meeting earlier than 2022-01-25 is not possible from my calendar.
     
     
  16. Like
    Heisath got a reaction from balbes150 in Armbian 22.02 (Pig) Release Thread   
    Release Candidate Code Freeze Date: 2022-02-14
    Release Planning Meeting Date:  2022-01-29 14:00 UTC+1 
    Release Planning Meeting Location: Armbian IRC
    Release Date: 2022-02-28
    Release Branch Link: https://github.com/armbian/build/tree/v22.02
    Release Changelog:
     
     
    Release Coordinator: @Heisath and hopefully some new person on the team
     
    Already creating this release topic for 22.02, to discuss upcoming changes, no longer maintained boards and help new people get into the release / maintain flow.
     
    Current steps:
    - Refine supported/WIP/CSC/etc. board status
    - Update maintainer list
    - Onboard new maintainers / contributors
    - Move Jira issues to new release
    - Select release name 
     
    @Igor @Werner @TonyMac32 @martinayotte @piter75 @ning @Myy @balbes150 @sfx2000 @ebin-dev @chwe  @gprovost @aprayoga @lanefu @5kft @JMCC @going @jeanrhum @dolphs @jock @belfastraven @TRS-80 @Bozza @Rich Neese @sgjava @Mangix @tony013  @rpardini
     
    Pls. ping developers I forgot  
  17. Like
    Heisath got a reaction from lanefu in Armbian 22.02 (Pig) Release Thread   
    Release Candidate Code Freeze Date: 2022-02-14
    Release Planning Meeting Date:  2022-01-29 14:00 UTC+1 
    Release Planning Meeting Location: Armbian IRC
    Release Date: 2022-02-28
    Release Branch Link: https://github.com/armbian/build/tree/v22.02
    Release Changelog:
     
     
    Release Coordinator: @Heisath and hopefully some new person on the team
     
    Already creating this release topic for 22.02, to discuss upcoming changes, no longer maintained boards and help new people get into the release / maintain flow.
     
    Current steps:
    - Refine supported/WIP/CSC/etc. board status
    - Update maintainer list
    - Onboard new maintainers / contributors
    - Move Jira issues to new release
    - Select release name 
     
    @Igor @Werner @TonyMac32 @martinayotte @piter75 @ning @Myy @balbes150 @sfx2000 @ebin-dev @chwe  @gprovost @aprayoga @lanefu @5kft @JMCC @going @jeanrhum @dolphs @jock @belfastraven @TRS-80 @Bozza @Rich Neese @sgjava @Mangix @tony013  @rpardini
     
    Pls. ping developers I forgot  
  18. Like
    Heisath got a reaction from allen--smithee in Kobol Helios64 on Sale   
    Added to watchlist. If it stays cheap enough, I'll buy it. 
     
    Can't guarantee you "Supported" flag, but I will have it running edge and notice problems
     
     
  19. Like
    Heisath got a reaction from NZJon in 5v 2.5amp available inside the Helios64...?   
    Should be easy enough to grab 5V of the wiring harness for the HDDs. J8 is the place to go for your high power 12V or 5V needs. https://wiki.kobol.io/helios64/sata/#j8-pinout (there is even a picture with the wire harness). 
    The GPIO header is not the right place to get high current from .)
  20. Like
    Heisath got a reaction from jock in Armbian 22.02 (Pig) Release Thread   
    Release Candidate Code Freeze Date: 2022-02-14
    Release Planning Meeting Date:  2022-01-29 14:00 UTC+1 
    Release Planning Meeting Location: Armbian IRC
    Release Date: 2022-02-28
    Release Branch Link: https://github.com/armbian/build/tree/v22.02
    Release Changelog:
     
     
    Release Coordinator: @Heisath and hopefully some new person on the team
     
    Already creating this release topic for 22.02, to discuss upcoming changes, no longer maintained boards and help new people get into the release / maintain flow.
     
    Current steps:
    - Refine supported/WIP/CSC/etc. board status
    - Update maintainer list
    - Onboard new maintainers / contributors
    - Move Jira issues to new release
    - Select release name 
     
    @Igor @Werner @TonyMac32 @martinayotte @piter75 @ning @Myy @balbes150 @sfx2000 @ebin-dev @chwe  @gprovost @aprayoga @lanefu @5kft @JMCC @going @jeanrhum @dolphs @jock @belfastraven @TRS-80 @Bozza @Rich Neese @sgjava @Mangix @tony013  @rpardini
     
    Pls. ping developers I forgot  
  21. Like
    Heisath got a reaction from johanvdw in recommendations for low power sbc   
    Arduino solutions will be the only more efficent way going forward. I mean, reading RS232 to SD card is super simple. 
     
    Untested code below, it would watch Serial and SoftSerial for incoming data, write it to a file on sd card (in 100 char chunks or on every newline, syncing sd card after every chunk). 
    Should be simple enough to adjust for some power down mechanism (and maybe add a button to manually sync data before removing sd card)...
     
    #include <SoftwareSerial.h> #include <SD.h> char buffer[100]; int buffer_pos = 0; uint8_t sdavail; #define CurrentBaudrate 115200 SoftwareSerial softSerial = SoftwareSerial(5, 4, false); void setup() { sdavail = SD.begin(SDC_CS); setupScreen(); Serial.begin(CurrentBaudrate); softSerial.begin(CurrentBaudrate); softSerial.listen(); } uint32_t lastTouched = millis(); char msg; void loop() { while (Serial.available() || softSerial.available()) { msg = Serial.available() ? (char)Serial.read() : (char)softSerial.read(); buffer[buffer_pos++] = msg; if (buffer_pos >= sizeof(buffer)) break; } if (msg == '\n' || buffer_pos >= sizeof(buffer)) { writeBuffer(); } } void writeBuffer() { if (sdavail) { File dataFile = SD.open("datalog.txt", FILE_WRITE); if (dataFile) { dataFile.write(buffer, buffer_pos); dataFile.close(); } } buffer_pos = 0; }  
  22. Like
    Heisath got a reaction from freed00m in Kobol Helios64 on Sale   
    Added to watchlist. If it stays cheap enough, I'll buy it. 
     
    Can't guarantee you "Supported" flag, but I will have it running edge and notice problems
     
     
  23. Like
    Heisath got a reaction from IcerJo in Kobol Helios64 on Sale   
    Added to watchlist. If it stays cheap enough, I'll buy it. 
     
    Can't guarantee you "Supported" flag, but I will have it running edge and notice problems
     
     
  24. Like
    Heisath reacted to Pali in MVEBU - Clearfog PCIe struggles   
    Hello @Heisath! This is known problem. QCA98xx wifi chips are buggy, have timing and detection issues related to PCIe, which Qualcomm confirmed. Qualcomm recommendation is to increase PCIe pulse detection and for some (x86) motherboards, vendors released a new BIOS which do it. To make it worse, Marvell A38x SoC has also buggy PCIe which cause other issues and therefore combination of QCA98xx and A38x cause even more issues.
     
    I'm preparing patches for pci-mvebu.c kernel driver to fix some issues, but they are not ready yet.
     
    For QCA98xx I have prepared patch which are currently on linux-pci mailing list: https://lore.kernel.org/linux-pci/20210505163357.16012-1-pali@kernel.org/
     
    Could you test it and check if it helps with new kernel versions?
  25. Like
    Heisath reacted to tparys in initramfs-tools not fully installed on Debian Stretch with Armbian Linux 4.19.56-mvebu64   
    EspressoBin is currently in CSC support, so best to submit bugs/questions in in Peer to Peer Support.
     
    Also need to submit armbianmonitor output. It seems dumb, but there's a lot of necessary information in there.
     
     
    However, in this case, it tells you exactly what died. You've somehow uninstalled busybox (directly or indirectly), and initramfs-tools can't work properly without it.
     
     
    Not advisable. The initramfs-tools package generates the initrd file for the kernel, which is generally a required part of the boot process. You'll want to get this fixed, and probably not reboot in the meantime until you do.
×
×
  • Create New...