Jump to content

Przemysław Sztoch

Members
  • Posts

    11
  • Joined

  • Last visited

Everything posted by Przemysław Sztoch

  1. Yes. I am using fresh u-boot made using armbian builder.
  2. I have similar problem with NanoPC T4, but with NVMe M.2 disk. 30% of boots are ok, but 70% of boot have problem with pcie. 1. If all is ok: # lspci │ 00:00.0 PCI bridge: Fuzhou Rockchip Electronics Co., Ltd RK3399 PCI Express Root Port │ 01:00.0 Non-Volatile memory controller: Sandisk Corp WD Blue SN550 NVMe SSD (rev 01) # dmesg | grep pcie [ 2.509212] rockchip-pcie f8000000.pcie: host bridge /pcie@f8000000 ranges: [ 2.509257] rockchip-pcie f8000000.pcie: MEM 0x00fa000000..0x00fbdfffff -> 0x00fa000000 [ 2.509279] rockchip-pcie f8000000.pcie: IO 0x00fbe00000..0x00fbefffff -> 0x00fbe00000 [ 2.510136] rockchip-pcie f8000000.pcie: no vpcie12v regulator found [ 2.857237] rockchip-pcie f8000000.pcie: host bridge /pcie@f8000000 ranges: [ 2.857281] rockchip-pcie f8000000.pcie: MEM 0x00fa000000..0x00fbdfffff -> 0x00fa000000 [ 2.857303] rockchip-pcie f8000000.pcie: IO 0x00fbe00000..0x00fbefffff -> 0x00fbe00000 [ 2.858166] rockchip-pcie f8000000.pcie: no vpcie12v regulator found [ 2.904718] rockchip-pcie f8000000.pcie: PCI host bridge to bus 0000:00 [ 2.924836] pcieport 0000:00:00.0: enabling device (0000 -> 0002) [ 2.925143] pcieport 0000:00:00.0: PME: Signaling with IRQ 91 [ 2.925531] pcieport 0000:00:00.0: AER: enabled with IRQ 91 2. If we have a problem lspci is empty and: # dmesg | grep pcie [ 2.510524] rockchip-pcie f8000000.pcie: host bridge /pcie@f8000000 ranges: [ 2.510567] rockchip-pcie f8000000.pcie: MEM 0x00fa000000..0x00fbdfffff -> 0x00fa000000 [ 2.510589] rockchip-pcie f8000000.pcie: IO 0x00fbe00000..0x00fbefffff -> 0x00fbe00000 [ 2.511432] rockchip-pcie f8000000.pcie: no vpcie12v regulator found [ 2.861623] rockchip-pcie f8000000.pcie: host bridge /pcie@f8000000 ranges: [ 2.861667] rockchip-pcie f8000000.pcie: MEM 0x00fa000000..0x00fbdfffff -> 0x00fa000000 [ 2.861688] rockchip-pcie f8000000.pcie: IO 0x00fbe00000..0x00fbefffff -> 0x00fbe00000 [ 2.862518] rockchip-pcie f8000000.pcie: no vpcie12v regulator found [ 3.387702] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout! [ 3.388630] rockchip-pcie: probe of f8000000.pcie failed with error -110 Could you explain what you had to do to solve problem?
  3. After upgrade to hirsute armbian builder works ok.
  4. I have similar problem if I want to build debian bullseye armbian image under virtualized ubuntu (host). Problem is in ldconfig arm64 binary launched by "Installing base system [ Stage 2/2 ]" (/debootstrap/debootstrap) There is not problem if I want to build image for debian buster.
  5. Can we add .editorconfig to https://github.com/armbian/build ?!
  6. Igor: Can I replace ntp by chrony? Old systems have been untouched. In new system users should use new config in /etc/chrony.
  7. In my opinion ntp should be replaced by chrony. Benefits of Chrony include: 1. Faster synchronization requiring only minutes instead of hours to minimize the time and frequency error, which is useful on desktops or systems not running 24 hours a day. 2. Better response to rapid changes in the clock frequency, which is useful for virtual machines that have unstable clocks or for power-saving technologies that don’t keep the clock frequency constant. 3. After the initial synchronization, it never steps the clock so as not to affect applications needing system time to be monotonic. 4. Better stability when dealing with temporary asymmetric delays, for example when the link is saturated by a large download. 5. Periodic polling of servers is not required, so systems with intermittent network connections can still quickly synchronize clocks. I can prepare patch and pull request, but I need initial confirmation.
  8. No. I want to use only "stretch" ditribution. I want to use armbian building script on my own, but in limited scope. In my configuration I put DISTROS=("stretch") I have to sign my packages with my key, because I have not got access to your Armbian key. This is the reason why I have to replace the ARMBIAN public key. I do not want to overwrite files from the original git repository (in example armbian.key...). A separate fork must then be maintained and merged.
  9. I need customization in configuration file for: a) DISTROS=("jessie" "xenial" "stretch" "bionic") b) ${SCRIPTPATH}config/armbian.key I want to make patch for it, but I need a few decisions: 1. Should I use lib.config as the configuration source? Maybe we prefer a separate file? 2. Can I unify RELEASE_LIST=("xenial" "jessie" "stretch" "bionic") from build-all and DISTROS=("jessie" "xenial" "stretch" "bionic") from repository.sh into one common parameter? 3. Do we accept the name for the parameter: GPG_PUBLIC_KEY=config/armbian.key?
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines