• Content Count

  • Joined

  • Last visited

About Jean-Marc

  • Rank

Profile Information

  • Gender
  • Location
    France, near PARIS
  • Interests
    ARM products

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi, Please could you give us more information about your Linux kernel version and driver used into your test. I am trying to use one Debian 5.10 standard kernel without capabilities to ping one external target connected on WAN port. At the same time, no problems encountered when connected (even with VLAN) on LAN port ? Thanks in advance for your help
  2. Igor, Thanks for your reply. I have tested many releases from Armbian, always with the same CLASS 10 from SANDISK ultra. It seems there is no issue for this point of view. Regards
  3. Hi, Please find log file on nanopir1 and Armbian. Not possible for me to boot the target with a tty connected on internal chip. U-Boot SPL 2019.10-armbian (Jan 05 2020 - 01:28:29 +0100) DRAM: 1024 MiB Trying to boot from MMC1 U-Boot 2019.10-armbian (Jan 05 2020 - 01:28:29 +0100) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: FriendlyARM NanoPi R1 DRAM: 1 GiB MMC: mmc@1c0f000: 0, mmc@1c11000: 1 Loading Environment from EXT4... ** File not found /boot/boot.env ** ** Unable to read "/boot/boot.env" from mmc0:1 ** In: serial Out: serial Err: serial Net
  4. Hi, I am trying to boot image Armbian_20.02.1_Nanopi-r1_buster_current_5.4.20.img, without success ... First, i am using following line to create SD ... ansible@solo:/mnt/backup$ sudo dd if=./Armbian_20.02.1_Nanopi-r1_buster_current_5.4.20.img of=/dev/mmcblk0 bs=1M status=progress ;sudo sync After connected my tty on internal pins on PCB, it is possible to connect to this tty and look at the first u-boot log ... Welcome to minicom 2.7.1 OPTIONS: I18n Compiled on May 6 2018, 08:02:47. Port /dev/tty-target-srv-nanopir1-170-position-, 20:34:41 Press CTRL-A Z for h
  5. Ok, thank for your reply. As a result, i have installed 4.19.62-sunxi kernel, and the target booting process is OK. But the bad news is that behavior is the same ..... root@srv-orangepir1-140:~# [10693.955976] EXT4-fs error (device dm-26): ext4_find_entry:1455: inode #12: comm apt: reading directory lblock 0 U-Boot SPL 2019.04-armbian (Jul 06 2019 - 00:26:54 +0200) DRAM: 256 MiB Trying to boot from MMC1 U-Boot 2019.04-armbian (Jul 06 2019 - 00:26:54 +0200) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi R1
  6. Hello, Sometimes, i have following errors on main syslog-ng server :
  7. Igor, Sorry, it was in the documentation (!) One Ethernet device gets random MAC
  8. Igor, Thanks for your reply. I have done new tests based on image: Armbian_19.11.3_Nanopi-r1_buster_current_5.3.9.7z test 1 : -------- Disconnect power, then reconnect power root@nanopi:~# armbianmonitor -u System diagnosis information will now be uploaded to Please post the URL in the forum where you've been asked for. test 2: ------- Disconnect power, then reconnect power root@nanopi:~# armbianmonitor -u System diagnosis information will now be uploaded to Please post the URL in the forum where y
  9. Hello, is there a user of orangepiR1 with traces of good operation of the 2 Ethernet interfaces simultaneously? In advance, please provide the boot log of the kernel and the DTB version number
  10. Hi, I am running Debian buster 10.1 with following kernel on nanopir1 (1Gb of RAM) Linux srv-nanopir1-170 5.3.9-sunxi #5.99.191113 SMP Wed Nov 13 08:12:49 CET 2019 armv7l GNU/Linux I have all services up on local LAN Ethernet port, but not possible for me to setup WAN Ethernet port . Packages installed are .... The boot sequence is ... My current network configuration in udev is .... As a result, r8152 kernel module is correctly installed After connected one RJ45 to external
  11. Thanks, Of course, you have right, not possible to boot this kernel . After creating a new sdcard with armbian last buster and update+upgrade, i have following error root@srv-orangepir1-150:~# [ 2201.407757] Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: mpage_map_and_submit_extent+0x5d5/0x5dc [ 2201.407757] [ 2201.408003] BUG: Bad rss-counter state mm:bc76d143 idx:0 val:15 [ 2201.412010] Unable to handle kernel paging request at virtual address cfa17500 [ 2201.412019] pgd = 0b15e16e [ 2201.412024] [cfa17500] *pgd=4fa1141e(bad) [ 2201.41
  12. ....but at the same time, on one another target (orangepiR1), but running Buster armbain & Debian, access is without any error? ansible@srv-orangepir1-150:~$ sudo grep -iR deb /etc/apt/sources* |grep -v "#" /etc/apt/sources.list.d/debian_apt_v_10_buster_backports.list:deb buster-backports main contrib non-free /etc/apt/sources.list.d/debian_apt_v_10_buster_previous.list:deb
  13. Hi, this day, always the same behaviour ????, but on target nanopiR1 for Debian stretch ansible@srv-nanopir1-170:~$ LANG=C LANGUAGE=C sudo apt-get update Hit:1 stretch-backports InRelease Ign:2 stretch InRelease Hit:3 stretch/updates InRelease Hit:5 stretch-updates InRelease Hit:6 buster InRelease Ign:4 stretch InRelease
  14. Very hard to reproduce. As a result, i am trying the same test with following Debian package .... linux-image-4.9.0-8-armmp-lpae armhf 4.9.110-3+deb9u6 ..... But target does not reboot on new kernel, it is always on 4.19.62-sunxi. After analysing /boot directory , it seems there is a bad link for zImage, because .... root@srv-orangepir1-150:~# LC_ALL=C ls -al /boot total 44176 drwxr-xr-x 4 root root 4096 Aug 11 20:32 . drwxr-xr-x 22 root root 4096 Aug 11 20:25 .. -rw-r--r-- 1 root root 0 Aug 4 17:25 .next -rw-r--r-- 1 root root 3299149 J