count-doku

Members
  • Content Count

    70
  • Joined

  • Last visited


Reputation Activity

  1. Like
    count-doku reacted to lanefu in Armbian 20.02 (Chiru) Release Thread   
    Release Candidate Code Freeze Date: 2020-01-25
    Release Date: 2020-02-??  (will update thread)
    Current Release Candidate Branch Link: v20.02-rc1
    Release Changelog: (will update)
    Release Coordinator: @lanefu
    Testing Tracking Sheet: https://bit.ly/2TGaeZN  (google sheets)
     
    The goal 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.  Our Hotfix process for completed releases is TBD.
     
    First of all I'm sorry I'm kicking this off so late.  I should have started a few weeks ago.  I'll continue to update this post with more information.  I will also update release process documentation as we progress.
     
    I am going to go ahead and cut a release branch to learn and further document the process, but the official release branch won't be cut until the Release Candidate Code Freeze Date.
     
    Tagging a few devs here from memory.. please tag others....  @Igor @gprovost @martinayotte @chwe @TonyMac32 @count-doku @balbes150 @Tido
     
     
  2. Like
    count-doku reacted to Igor in Armbian 20.02 (Chiru) Release Thread   
    My two cents.
     
    - once we made a fork from a master branch, version must be adjusted accordingly (also on master)
    - master remains the place for new contribution and we merge them into 
    - when we are satisfied with the state of the build, RCx -> .1
    - hot-fix releases. For now IMO, using master branch and just going up with the number. Unless we have resources which will stay behind and tinkle old releases, send fix to master, merge back, bump version and tell me what to build
     
    I do plan to create a Jenkins server for this one day, that you will be able to push things up without me in the loop.
  3. Like
    count-doku reacted to lanefu in Armbian 20.02 (Chiru) Release Thread   
    I've added some more detail here on merge policy and release process.  Keep an eye on it. I'll be updating it as we go through this process https://github.com/armbian/documentation/blob/master/docs/Process_Release-Model.md#release-coordinating
     
    and to clarify.. I have cut an rc0 branch, but it's just to test the process.   rc1 will be the first official rc branch and will happen on our freeze date.
     
  4. Like
    count-doku reacted to gprovost in Armbian 20.02 (Chiru) Release Thread   
    Adding @aprayoga
  5. Like
    count-doku got a reaction from aprayoga in Armbian 20.02 (Chiru) Release Thread   
    Looks good, I like the definitive freeze / release dates. 
     
    I will do remaining work (mostly testing recent mvebu changes on Helios4) today.
     
    Another dev: @aprayoga
     
    EDIT:
    Not worth the extra post, I completed testing on Helios4 and Clearfog looks good:
    mvebu-legacy
        Helios4 lk 4.14.y u-boot 2018.11-armbian
       http://ix.io/27Ou
     
        Clearfog (Pro) lk 4.14.y u-boot 2018.01-armbian
        * SFP working but only up to 1Gbps    
       http://ix.io/27OL
     
    mvebu-current
        Helios4 lk 4.19.y u-boot 2019.04-armbian
       http://ix.io/27Ox  
     
        Clearfog (Pro) lk 4.19.y u-boot 2018.01-armbian
        * SFP working but only up to 1Gbps
       http://ix.io/27OM
  6. Like
    count-doku got a reaction from gounthar in GPIO and Armbian for OrangePi Zero.   
    Hi,
     
    these PIN Names are possibly considered "general knowledge" once you worked with some microprocessors or similiar. Most are just abbreviations. And the different functions on a pin.
     
    I'll try to explain some of them based on the linked OrangePi Extension header table (from their wiki):

    3.3V -> obviously 3.3V output
    TWI0_SDA / PA12 / GPIO12:
    TWI0_SDA -> Two Wire Interface also known as I²C | SDA -> Serial Data
    PA12 -> Pin from internal pin register a, number 12
    GPIO -> General Purpose Input/Output Pin Number 12
    the last two are essentially the same with the first one based on the internal registers and the other one just numerated over all pins.
     
    TWI0_SCK / PA11 / GPIO11:
    TWI0_SCK -> Two Wire Interface (i2c) | SCK -> Serial Clock
     
    GND -> ground, minus, (-), return or whatever you're gonna call it.
     
    UART2_RX -> Universial Asynchronous Receiver and Transmitter 2 -> also known as Serial Port (RS232 like) | RX -> Receiving or Receiver. This pin is read by software.
    UART2_TX -> see above, TX -> Transmitter. This pin gets set by software (and sends the data)
    UART2_CTS -> see above, CTS -> Clear to Send. Used for flow control, to tell the partner you are ready to receive. (or they are cleared to send) 
    (Googling for UART, USART or RS232 will probably give good explanations on this)
     
    SPI1_MOSI:
    SPI -> Serial Peripheral Interface -> Another kind of serial port. -> google.
    MOSI -> Master Out / Slave In -> this is the transmitting port for a master perspective
    SPI1_MISO -> Master In / Slave Out -> receiving port
    SPI1_CLK -> the clock signal. 
    Just search for spi for more info.
     
    SIM_CLK / PA_EINT7:
    SIM_CLK -> can probably attach a SIM Card here (then this will be the clock line). I don't know stuff about sim cards though.
    PA_EINT7 -> Internal Port Register A, External Interrupt 7. Read about Hardware Interrupts for microprocessors for more info. Essentially a software component can be instantly triggered on some predefined signal on this pin.
     
    The rest has the same prefixes, so you can probably deduce the meaning by using the internet. If something remains unclear, just ask.
     
    Kind regards,
    count-doku
  7. Like
    count-doku got a reaction from gprovost in Helios64 Annoucement   
    Looks good! Congrats to the Kobol team for designing another interesting NAS board.
     
    Is the 12V 10A power supply neccessary though? I mean thats 120W, with that much power one can easily run a real x86... 
    How much does the board itself consume? 
     
     
  8. Like
    count-doku got a reaction from Igor in Clearfogpro : lost PCIe sata card after update   
    @Igor 
    This is not a problem on deb2016 side. This is a general problem.
     
    You posted some armbian-monitor link above, of your setup:
     
     
    Did you read the results? Because if you check your 'lspci' output, you would realise that your 4x marvell sata card is not detected in linux:
     
    ### lspci: 00:02.0 PCI bridge: Marvell Technology Group Ltd. Device 6828 (rev 04) 00:03.0 PCI bridge: Marvell Technology Group Ltd. Device 6828 (rev 04) 02:00.0 Network controller: Qualcomm Atheros QCA986x/988x 802.11ac Wireless Network Adapter  
    So this is the same problem @deb2016 is facing.
     
    In my opinion this is a big problem (maybe even with the drivers for 88se9215 (which is probably your sata card)) and we should try to fix this together with current work on mvebu. See also github issue. 
    https://github.com/armbian/build/issues/1426
     
  9. Like
    count-doku got a reaction from gprovost in Helios4 Support   
    One other thing to check if the disks are faulty / just doing the clicking -> connect them to some computer. Listen there.
     
     
  10. Like
    count-doku reacted to Vlado in NanoPC T3+ boot troubles   
    PCB is same.
    FriendlyArm img. 2GB RAM 32bit work OK. So 2GB !!!
    PSU 2.4A
  11. Like
    count-doku got a reaction from Technicavolous in SOLVED - Clearfog Pro PCI-e card only detected in slot 2 in Armbian   
    Excuse this double post / push.
     
    But I think I found your problem Techni and a simple solution.
     
    I built a new armbian image using newest kernel and debian and made sure to check the ath10k pci driver option.
     
    Then burned it to my sd card and booted my clearfog -> voila same error as yours in dmesg. And no firmware files in /lib/firmware/ath10k!
     
    A simple apt install firmware-atheros got me the firmware and after a reboot the card is detected and available in ifconfig.
     
    So just try it using lan and install the atheros firmware.
     
    I will also provide my testimage (login: root and 1234) in case you have no network connectivity.
    (Upload will take some time, will update this with link when its done...)
    EDIT: couldnt get a running image resized from my 64GB SD Card in time. Will try again if you need it...
     
    Greetings,
    count-doku
     
  12. Like
    count-doku got a reaction from Technicavolous in Clearfog Pro 4.14.14 Network Manager fails   
    You don't need additional packages (except ifupdown) for a manual network configuration.
     
    Just edit /etc/network/interfaces, you can check here for reference https://wiki.debian.org/NetworkConfiguration
    Or have a look at my config attached to this post.
     
    Greets,
    count-doku
     
     
    # Bring up automatically: auto lo auto eth0 auto eth1 lan1 lan2 lan3 lan4 lan5 lan6 br0 # Configure loopback interface iface lo inet loopback # Configure eth0, my outgoing public interface allow-hotplug eth0 iface eth0 inet dhcp post-up iptables-restore < /etc/iptables.up.rules post-up ip6tables-restore < /etc/ip6tables.up.rules # Bring up eth1 manual w/o ip config. This is neccessary to communicate with the switch / dsa iface eth1 inet manual # address 169.254.100.100 # netmask 255.255.255.255 # Do with the SFP Port whatever you want iface eth2 inet manual # Set all switched lan ports to manual iface lan1 inet manual iface lan2 inet manual iface lan3 inet manual iface lan4 inet manual iface lan5 inet manual iface lan6 inet manual # Create bridge over all lanports and ip config them iface br0 inet static bridge_ports lan1 lan2 lan3 lan4 lan5 lan6 address 192.168.1.1 netmask 255.255.255.0 network 192.168.1.0 broadcast 192.168.1.255