guidol

  • Content Count

    1702
  • Joined

  • Last visited

8 Followers

About guidol

  • Rank
    IT-DInosaur

Profile Information

  • Gender
    Male
  • Location
    Mudanya

Recent Profile Visitors

6430 profile views
  1. @Igor just one more "repaired" patient After getting at Tuesday the NanoPi Neo working fine with his eth0 - I did gave my Orange Pi R1 a new "ride" today. The last months (or year) I did think his eth0 is defective, because when ethernet there is inserted the orange-led blinks only on/off and isnt accessable when the Orange Pi R1 is booted. I could only use the second ethernet port (WITH THE SAME cable) which is onboard conected via USB (enx-device) Today I put him on the same 1st 2x4 ports of my 16 port 100MBit Hub - and the blinking orange led stays on and does wor
  2. Some "strange" behaviour: I compiled a fresh dev-version, which has u-boot "U-Boot 2021.01-armbian (Mar 03 2021 - 14:32:21 +0300) odroid-c2" and flashed it on a new sdcard: ___ _ _ _ ____ ____ / _ \ __| |_ __ ___ (_) __| | / ___|___ \ | | | |/ _` | '__/ _ \| |/ _` | | | __) | | |_| | (_| | | | (_) | | (_| | | |___ / __/ \___/ \__,_|_| \___/|_|\__,_| \____|_____| Welcome to Armbian 21.05.0-trunk Buster with Linux 5.10.19-meson64 No end-user support: built from trunk package bsp-kernel[21.05.0-trunk] u-boot[21.05.0-trunk] dtb [21.05.0-trunk] f
  3. @Elclaudio @Igor for your and my security here is the u-boot U-Boot 2019.01-armbian (Mar 25 2019 - 18:08:02 +0300) odroid-c2 root@npi-neo2-24(192.168.6.24):/mnt/sdb1/usr/lib/linux-u-boot-dev-odroidc2_5.77_arm64# strings ./u-boot.bin | grep 'U-Boot 20' U-Boot 2019.01-armbian (Mar 25 2019 - 18:08:02 +0300) odroid-c2 out of my archive Armbian_5.77_Odroidc2_Debian_stretch_dev_5.0.4.img.zip (isnt armbian 5.95, but near/close for the u-boot ) This u-boot is currently installed/working on my C2 in mmcblk0 So if we want to test a newer version we can go bac
  4. Yes its seems also like a 2019-version (didnt changed the count - becaus it isnt a backup - only to get version: root@odroid-c2 : /home/guido# dd if=/dev/mmcblk0 of=./installed_uboot.bin skip=97 count=1376 1376+0 records in 1376+0 records out 704512 bytes (705 kB, 688 KiB) copied, 0.0463896 s, 15.2 MB/s root@odroid-c2 : /home/guido# strings ./installed_uboot.bin | grep "U-Boot 20" U-Boot 2019.10-armbian (Dec 01 2019 - 09:31:42 +0300) odroid-c2
  5. but I dont know if the content of u-boot.bin is installed in my mmcblk0 And I dont want to install the newer one, when my eth0 may be stop to work
  6. The command strings /dev/mmcblk0 | grep 'U-Boot 20' gives me U-Boot 2019.10-armbian (Dec 01 2019 - 09:31:42 +0300) odroid-c2 # U-Boot 2020.04 Configuration Compiled with U-Boot 2019.01+dfsg-7 # U-Boot 2021.01 Configuration # U-Boot 2021.01 Configuration # U-Boot 2019.10 Configuration U-Boot 2013.10-rc2-08400-g0490093 (Oct 11 2013 - 00:40:21) Allwinner Technology U-Boot 2011.09-rc1-00000-geb98797 (Dec 13 2017 - 15:44:38) Allwinner Technology U-Boot 2011.09-rc1-00000-gc1cb2f9 (May 30 2014 - 10:19:03) Allwinner Technology U-Boot 2021.01-armbian (Feb 11 2021 - 21:19:38 +0300) odr
  7. Is there any way (away from serial TTL boot-log) to found out which u-boot is installed on mmcblk0? I know I got the u-boot package linux-u-boot-odroidc2-dev 21.02.1 arm64 Uboot loader 2021.01 on my C2, but doent know if this is with the .deb installed on mmcblk0. Because the C2 hasnt a standard pin-header (and I think 3.3V? ) I didnt got the chance for a serial boot-log on my C2 and I often do update the u-boot-packages (u-boot, kernel-image, dtb, firmware etc) but didnt flash a new image for this to the card there could be a chance that Iam using an olde
  8. @Igor and who also have an interest in this issue/topic After a long time - today Ethnernet is since hours stable again on my NanoPi Neo (no Network/eth0 down/up) BUT I didnt changed the software (armbian) Yesterday my NanoPi Neo had down/up (also) with Kernel 5.11.2-dev and debian buster and now today its stable since hours! What I did? No it wasnt the software, nor the ethernet-cable, nor the Power-Supply, nor the eth0-setting. I have a 16-port-Ethnernet-Hub with 100MBit, but its optical devided in 2x(2x4): 1st 2nd 2x4 + 2x4 = 16 ports #### #### ##
  9. from the extracted (example) u-boot.deb there are 2 directorys under /usr/lib/ with 5 files, but I think it isnt a good idea to change them by hand. I think the best way would be via a "u-boot" .deb-file (and the kernel/dtb and so on - created via the armbian-build-system)
  10. Yes - thats because I only got a 5-port GBit-Switch. There is my primary-PC and the Samba-Servers. The other part of my Network is on a 24-port 100MBit-Switch - and my C2 as DNS-Filter doenst need 1GBit
  11. I disabled the module in the "path" not in the "patch" (corrected this now) - so it shouldnt be present. Thanks for your commit
  12. NPi K1 Plus is now on current. Started with 5.10.12 and is now after update at 5.10.16 - and all is working again (I dont use WiFi ) System diagnosis information will now be uploaded to http://ix.io/2RdP [EDIT] After build-update (u-boot build packages) I did get 5.10.18-trunk: _ _ ____ _ _ ___ ____ _ | \ | | _ \(_) | |/ / | | _ \| |_ _ ___ | \| | |_) | | | ' /| | | |_) | | | | / __| | |\ | __/| | | . \| | | __/| | |_| \__ \ |_| \_|_| |_| |_|\_\_| |_| |_|\__,_|___/ Welcome to Armbian 21.02.2 Buster with Linux 5.10.18-sunxi64 p
  13. actual current image does work on my C2: ___ _ _ _ ____ ____ / _ \ __| |_ __ ___ (_) __| | / ___|___ \ | | | |/ _` | '__/ _ \| |/ _` | | | __) | | |_| | (_| | | | (_) | | (_| | | |___ / __/ \___/ \__,_|_| \___/|_|\__,_| \____|_____| Welcome to Armbian 21.02.1 Buster with Linux 5.10.12-meson64 System load: 2% Up time: 6 min Memory usage: 6% of 1.85G IP: 192.168.6.150 CPU temp: 37°C Usage of /: 6% of 29G root@odroidc2:/home/guido# dmesg|grep -i phy [ 0.000000] Booting Linux on physical CPU
  14. @martinayotte My OPi One with Pihole & Kernel 5.11.1 does work - so its up to a problem with the NPI K1 Plus ans 5.11.1, but not only the WiFi-module For now I will go back to current (have to check kernel No) with the NPi K1 Plus
  15. I disabled the module on my NPi K1 Plus in the sunxi64 path, but with the new created 5.11.1-dev image the NPi K1 Plus doenst give me a right login. It try to give me a automatic login, but there is no prompt and the heartbeat led is blinking very fast Starting kernel ... nanopik1plus login: root (automatic login) Last login: Sun Feb 28 15:14:43 UTC 2021 on tty1 Login timed out after 60 seco nanopik1plus login: root (automatic login) Last login: Sun Feb 28 15:15:58 UTC 2021 on tty1 Login timed out after 60 s nanopik1plus login: root (automatic login) Last login: Sun Fe