piknew

Members
  • Content count

    59
  • Joined

  • Last visited

  1. So far tried: 1. dd - dump emmc to SD card and boot from SD card wich was 1:1 image of emmc - OK: U-Boot SPL 2017.11-armbian (Jan 25 2018 - 07:58:02) DRAM: 2048 MiB Trying to boot from MMC1 U-Boot 2017.11-armbian (Jan 25 2018 - 07:58:02 +0100) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi Plus / Plus 2 DRAM: 2 GiB MMC: SUNXI SD/MMC: 0, SUNXI SD/MMC: 1 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: phy interface7 eth0: ethernet@1c30000 starting USB... USB0: USB EHCI 1.00 USB1: USB EHCI 1.00 scanning bus 0 for devices... 2 USB Device(s) found scanning bus 1 for devices... Device NOT ready Request Sense returned 02 3A 00 2 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3708 bytes read in 149 ms (23.4 KiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 21 bytes read in 171 ms (0 Bytes/s) 4578312 bytes read in 459 ms (9.5 MiB/s) 6972808 bytes read in 537 ms (12.4 MiB/s) Found mainline kernel configuration 33781 bytes read in 491 ms (66.4 KiB/s) 401 bytes read in 146 ms (2 KiB/s) Applying user provided DT overlay ds1307.dtbo ** File not found /boot/dtb/overlay/-fixup.scr ** ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 4578248 Bytes = 4.4 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 Loading Ramdisk to 49ba2000, end 49fffbc8 ... OK reserving fdt memory region: addr=43000000 size=6e000 Loading Device Tree to 49b31000, end 49ba1fff ... OK Starting kernel ... Loading, please wait... Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems done. Begin: Will now check root file system ... fsck from util-linux 2.25.2 [/sbin/fsck.ext4 (1) -- /dev/mmcblk0p1] fsck.ext4 -a -C0 /dev/mmcblk0p1 /dev/mmcblk0p1: clean, 81229/918720 files, 466019/3781376 blocks done. done. Begin: Running /scripts/local-bottom ... done. Begin: Running /scripts/init-bottom ... done. Welcome to Debian GNU/Linux 8 (jessie)! Expecting device dev-ttyS0.device... [ OK ] Reached target Remote File Systems (Pre). [ OK ] Reached target Paths. [ OK ] Set up automount Arbitrary Executable File Formats F...utomount Point. [ OK ] Reached target Encrypted Volumes. [ OK ] Created slice Root Slice. [ OK ] Listening on Delayed Shutdown Socket. [ OK ] Listening on /dev/initctl Compatibility Named Pipe. [ OK ] Listening on Journal Socket (/dev/log). [ OK ] Created slice User and Session Slice. [ OK ] Listening on udev Control Socket. 2. When running from SD - as below. Seems to be exactly the same as on legacy. root@PKBACKUP:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT mmcblk1boot0 179:16 0 4M 1 disk mmcblk1 179:8 0 14.6G 0 disk └─mmcblk1p1 179:9 0 14.4G 0 part mmcblk1boot1 179:24 0 4M 1 disk mmcblk0 179:0 0 14.9G 0 disk └─mmcblk0p1 179:1 0 14.4G 0 part / root@PKBACKUP:~# 3. When running from SD move armbian to EMMC by nand-sata-install. Boot from emmc (after message saying "now poweroff ...") - FAILED as before: U-Boot SPL 2017.11-armbian (Jan 25 2018 - 07:58:02) DRAM: 2048 MiB Trying to boot from MMC2 U-Boot 2017.11-armbian (Jan 25 2018 - 07:58:02 +0100) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi Plus / Plus 2 DRAM: 2 GiB MMC: SUNXI SD/MMC: 0, SUNXI SD/MMC: 1 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: phy interface7 eth0: ethernet@1c30000 starting USB... USB0: USB EHCI 1.00 USB1: USB EHCI 1.00 scanning bus 0 for devices... 2 USB Device(s) found scanning bus 1 for devices... Device NOT ready Request Sense returned 02 3A 00 2 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc1(part 0) is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 3708 bytes read in 134 ms (26.4 KiB/s) ## Executing script at 43100000 U-boot loaded from eMMC or secondary SD Boot script loaded from mmc 21 bytes read in 154 ms (0 Bytes/s) MMC: no card present mmc_init: -123, time 2 ** Bad device mmc 0 ** 4578312 bytes read in 464 ms (9.4 MiB/s) 6972808 bytes read in 559 ms (11.9 MiB/s) Found mainline kernel configuration 33781 bytes read in 645 ms (50.8 KiB/s) 401 bytes read in 188 ms (2 KiB/s) Applying user provided DT overlay ds1307.dtbo ** File not found /boot/dtb/overlay/-fixup.scr ** ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 4578248 Bytes = 4.4 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 Loading Ramdisk to 49ba2000, end 49fffbc8 ... OK reserving fdt memory region: addr=43000000 size=6e000 Loading Device Tree to 49b31000, end 49ba1fff ... OK Starting kernel ... Loading, please wait... Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. done. Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/mmcblk0p1 does not exist. Dropping to a shell! Rebooting automatically due to panic= boot argument [ 44.940297] reboot: Restarting system U-Boot SPL 2017.11-armbian (Jan 25 2018 - 07:58:02) DRAM: 2048 MiB Trying to boot from MMC2 U-Boot 2017.11-armbian (Jan 25 2018 - 07:58:02 +0100) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi Plus / Plus 2 DRAM: 2 GiB
  2. On legacy it was always first device - either SD or EMMC (if SD was not present). And yes - my fstab was referring directly to /dev/mmcblk0p1. I have updated it to correct UUID=... but still the same. BTW. My armbianEnv.txt is basically empty. It has only one line for DT user overlay (RTC). Any more suggestions? Meanwhile I will try to dump my EMMC onto SD card and try to boot from it.
  3. I am trying to switch legacy kernel to "next". I did it successfully with armbian-config for OrangePiPC (obviously Armbian was installed on SD card). Once I attempted to do the same with Orange Pi Plus and system installed onto internal EMMC then after reboot... nothing. I am wondering also if the issue is related to platform or the fact that Armbian was installed on EMMC. I have connected TTL2USB and following is the result (seems to be indefinite loop): U-Boot SPL 2017.11-armbian (Jan 25 2018 - 07:58:02) DRAM: 2048 MiB Trying to boot from MMC2 U-Boot 2017.11-armbian (Jan 25 2018 - 07:58:02 +0100) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi Plus / Plus 2 DRAM: 2 GiB MMC: SUNXI SD/MMC: 0, SUNXI SD/MMC: 1 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: phy interface7 eth0: ethernet@1c30000 starting USB... USB0: USB EHCI 1.00 USB1: USB EHCI 1.00 scanning bus 0 for devices... 2 USB Device(s) found scanning bus 1 for devices... Device NOT ready Request Sense returned 02 3A 00 2 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc1(part 0) is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 3708 bytes read in 141 ms (25.4 KiB/s) ## Executing script at 43100000 U-boot loaded from eMMC or secondary SD Boot script loaded from mmc 21 bytes read in 161 ms (0 Bytes/s) MMC: no card present mmc_init: -123, time 2 ** Bad device mmc 0 ** 4578312 bytes read in 446 ms (9.8 MiB/s) 6972808 bytes read in 526 ms (12.6 MiB/s) Found mainline kernel configuration 33781 bytes read in 473 ms (69.3 KiB/s) 401 bytes read in 137 ms (2 KiB/s) Applying user provided DT overlay ds1307.dtbo ** File not found /boot/dtb/overlay/-fixup.scr ** ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 4578248 Bytes = 4.4 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 Loading Ramdisk to 49ba2000, end 49fffbc8 ... OK reserving fdt memory region: addr=43000000 size=6e000 Loading Device Tree to 49b31000, end 49ba1fff ... OK Starting kernel ... Loading, please wait... Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done. Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems done. Begin: Waiting for root file system ... Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. done. Gave up waiting for root device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Check root= (did the system wait for the right device?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/mmcblk0p1 does not exist. Dropping to a shell! Rebooting automatically due to panic= boot argument [ 44.940355] reboot: Restarting system U-Boot SPL 2017.11-armbian (Jan 25 2018 - 07:58:02) DRAM: 2048 MiB Trying to boot from MMC2 U-Boot 2017.11-armbian (Jan 25 2018 - 07:58:02 +0100) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi Plus / Plus 2 DRAM: 2 GiB MMC: SUNXI SD/MMC: 0, SUNXI SD/MMC: 1 *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Net: phy interface7 eth0: ethernet@1c30000 starting USB... USB0: USB EHCI 1.00 USB1: USB EHCI 1.00 scanning bus 0 for devices... 2 USB Device(s) found scanning bus 1 for devices... Device NOT ready Request Sense returned 02 3A 00 2 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc1(part 0) is current device
  4. piknew

    30-sysinfo get_ip_addresses()

    Proposal: root@PKSERVER:~# grep -n ewr /etc/update-motd.d/30-sysinfo 109: if [[ $intf =~ ^[ewr].* ]] || (grep $intf /etc/conf.d/30-sysinfo-net-interfaces 1>/dev/null 2>&1); then root@PKSERVER:~# cat /etc/conf.d/30-sysinfo-net-interfaces bond0 root@PKSERVER:~#
  5. piknew

    30-sysinfo get_ip_addresses()

    So, basically the way would be explicit list of prefixes: eth, bond, wlan, ra, ... Or explicit list of interfaces.
  6. Is it possible to make small adjustment into line 109 of /etc/update-motd.d/30-sysinfo file (I made the change myslef, but once packages are upgraded - change is overwritten)? Original line is: if [[ $intf =~ ^[ewr].* ]]; then Changed line would be (please note additional letter "b"): if [[ $intf =~ ^[ewrb].* ]]; then You may see the reason - I guess "bond" is the common prefix when binding ethernet devices: admin@PKSERVER:~$ grep -n ewr /etc/update-motd.d/30-sysinfo 109: if [[ $intf =~ ^[ewrb].* ]]; then admin@PKSERVER:~$ sudo ifconfig bond0 Link encap:Ethernet HWaddr 08:00:00:00:02:10 inet addr:192.168.10.210 Bcast:192.168.10.255 Mask:255.255.255.0 inet6 addr: fe80::a00:ff:fe00:210/64 Scope:Link UP BROADCAST RUNNING MASTER MULTICAST MTU:1500 Metric:1 RX packets:171152 errors:0 dropped:0 overruns:0 frame:0 TX packets:163786 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:59535359 (56.7 MiB) TX bytes:90682136 (86.4 MiB) eth0 Link encap:Ethernet HWaddr 08:00:00:00:02:10 UP BROADCAST RUNNING SLAVE MULTICAST MTU:1500 Metric:1 RX packets:171152 errors:0 dropped:0 overruns:0 frame:0 TX packets:163786 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:59535359 (56.7 MiB) TX bytes:90682136 (86.4 MiB) Interrupt:114 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:90328 errors:0 dropped:0 overruns:0 frame:0 TX packets:90328 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:43909407 (41.8 MiB) TX bytes:43909407 (41.8 MiB) wlan0 Link encap:Ethernet HWaddr da:f9:d4:00:43:7b UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
  7. piknew

    RTC 1307 / 3232

    Thanks! As following: root@PKHELPER:/boot/overlay-user# ll total 8 -rw-r--r-- 1 root root 473 May 13 16:45 ds1307.dts -rw-r--r-- 1 root root 401 May 13 16:46 ds1307.dtbo root@PKHELPER:/boot/overlay-user# cat ds1307.dts /dts-v1/; /plugin/; / { compatible = "brcm,bcm2708"; fragment@0 { target = <&i2c0>; __overlay__ { #address-cells = <1>; #size-cells = <0>; status = "okay"; ds1307@68 { compatible = "ds1307"; reg = <0x68>; status = "okay"; }; }; }; }; root@PKHELPER:/boot/overlay-user# dmesg | grep ds1307 [ 8.348114] rtc-ds1307 0-0068: registered as rtc1 root@PKHELPER:/boot/overlay-user# hwclock -r -f /dev/rtc1 Sun 13 May 2018 04:49:25 PM CEST -0.422132 seconds root@PKHELPER:/boot/overlay-user#
  8. piknew

    RTC 1307 / 3232

    Unfortunately device is no longer detected on i2c bus: root@PKHELPER:~# i2cdetect -y 0 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- UU -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- --
  9. piknew

    RTC 1307 / 3232

    rtc module is standard 1307/3231. Registered with command: /bin/echo ds1307 0x68 1>/sys/class/i2c-adapter/i2c-0/new_device
  10. piknew

    RTC 1307 / 3232

    Hi, after upgrade to next kernel: my rtc-i2c stopped working. Here is the result for "Linux ... 3.4.113-sun8i #18 SMP PREEMPT Wed Jan 24 22:10:49 CET 2018 armv7l GNU/Linux" [ 6.008219] rtc-ds1307 0-0068: rtc core: registered ds1307 as rtc1 [ 6.008241] rtc-ds1307 0-0068: 56 bytes nvram [ 6.008277] i2c i2c-0: new_device: Instantiated device ds1307 at 0x68 Here is for "Linux ... 4.14.18-sunxi #24 SMP Fri Feb 9 16:24:32 CET 2018 armv7l GNU/Linux" [ 6376.740796] i2c i2c-0: new_device: Instantiated device ds3232 at 0x68 and nothing else (btw the same is for ds1307). Device rtc1 is not registered. Can anybody suggest how to force device /dev/rtc1 to be registered?
  11. piknew

    Problems with 5.38 update

    Done "just in case" (on already up & running opi+2): root@PKHELPER:/boot# ll total 14276 -rw-r--r-- 1 root root 6944 Jun 5 2016 boot.bmp -rw-r--r-- 1 root root 2372 Jun 5 2016 boot.cmd -rw-r--r-- 1 root root 2444 Jun 5 2016 boot.scr lrwxrwxrwx 1 root root 20 Aug 4 23:09 script.bin -> bin/orangepiplus.bin -rwxr-xr-x 1 root root 4752384 Jan 24 22:10 vmlinuz-3.4.113-sun8i -rw-r--r-- 1 root root 2056747 Jan 24 22:10 System.map-3.4.113-sun8i -rw-r--r-- 1 root root 97199 Jan 24 22:10 config-3.4.113-sun8i drwxr-xr-x 2 root root 4096 Jan 29 17:57 bin lrwxrwxrwx 1 root root 21 Jan 29 17:59 zImage -> vmlinuz-3.4.113-sun8i -rw-r--r-- 1 root root 3839674 Jan 29 17:59 initrd.img-3.4.113-sun8i -rw-r--r-- 1 root root 3839738 Jan 29 17:59 uInitrd-3.4.113-sun8i lrwxrwxrwx 1 root root 21 Jan 29 17:59 uInitrd -> uInitrd-3.4.113-sun8i root@PKHELPER:/boot# wget https://raw.githubusercontent.com/armbian/build/master/config/bootscripts/boot-sunxi.cmd --2018-01-30 17:32:16-- https://raw.githubusercontent.com/armbian/build/master/config/bootscripts/boot-sunxi.cmd Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 151.101.112.133 Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|151.101.112.133|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 3636 (3.6K) [text/plain] Saving to: ‘boot-sunxi.cmd’ boot-sunxi.cmd 100%[=======================================================================================>] 3.55K --.-KB/s in 0.001s 2018-01-30 17:32:16 (6.88 MB/s) - ‘boot-sunxi.cmd’ saved [3636/3636] root@PKHELPER:/boot# ll total 14280 -rw-r--r-- 1 root root 6944 Jun 5 2016 boot.bmp -rw-r--r-- 1 root root 2372 Jun 5 2016 boot.cmd -rw-r--r-- 1 root root 2444 Jun 5 2016 boot.scr lrwxrwxrwx 1 root root 20 Aug 4 23:09 script.bin -> bin/orangepiplus.bin -rwxr-xr-x 1 root root 4752384 Jan 24 22:10 vmlinuz-3.4.113-sun8i -rw-r--r-- 1 root root 2056747 Jan 24 22:10 System.map-3.4.113-sun8i -rw-r--r-- 1 root root 97199 Jan 24 22:10 config-3.4.113-sun8i drwxr-xr-x 2 root root 4096 Jan 29 17:57 bin lrwxrwxrwx 1 root root 21 Jan 29 17:59 zImage -> vmlinuz-3.4.113-sun8i -rw-r--r-- 1 root root 3839674 Jan 29 17:59 initrd.img-3.4.113-sun8i -rw-r--r-- 1 root root 3839738 Jan 29 17:59 uInitrd-3.4.113-sun8i lrwxrwxrwx 1 root root 21 Jan 29 17:59 uInitrd -> uInitrd-3.4.113-sun8i -rw-r--r-- 1 root root 3636 Jan 30 17:32 boot-sunxi.cmd root@PKHELPER:/boot# mv boot-sunxi.cmd boot.cmd root@PKHELPER:/boot# mkimage -C none -A arm -T script -d boot.cmd boot.scr Image Name: Created: Tue Jan 30 17:33:53 2018 Image Type: ARM Linux Script (uncompressed) Data Size: 3644 Bytes = 3.56 kB = 0.00 MB Load Address: 00000000 Entry Point: 00000000 Contents: Image 0: 3636 Bytes = 3.55 kB = 0.00 MB root@PKHELPER:/boot# ll total 14276 -rw-r--r-- 1 root root 6944 Jun 5 2016 boot.bmp lrwxrwxrwx 1 root root 20 Aug 4 23:09 script.bin -> bin/orangepiplus.bin -rwxr-xr-x 1 root root 4752384 Jan 24 22:10 vmlinuz-3.4.113-sun8i -rw-r--r-- 1 root root 2056747 Jan 24 22:10 System.map-3.4.113-sun8i -rw-r--r-- 1 root root 97199 Jan 24 22:10 config-3.4.113-sun8i drwxr-xr-x 2 root root 4096 Jan 29 17:57 bin lrwxrwxrwx 1 root root 21 Jan 29 17:59 zImage -> vmlinuz-3.4.113-sun8i -rw-r--r-- 1 root root 3839674 Jan 29 17:59 initrd.img-3.4.113-sun8i -rw-r--r-- 1 root root 3839738 Jan 29 17:59 uInitrd-3.4.113-sun8i lrwxrwxrwx 1 root root 21 Jan 29 17:59 uInitrd -> uInitrd-3.4.113-sun8i -rw-r--r-- 1 root root 3636 Jan 30 17:32 boot.cmd -rw-r--r-- 1 root root 3708 Jan 30 17:33 boot.scr root@PKHELPER:/boot# Device is still booting - OK ...
  12. piknew

    Problems with 5.38 update

    Thanks, for me solution with manual download and "dd" to emmc works as well. Opi+2 is up & running now. For Opi+2e - tomorrow I will try (have a little more issues with physical access to device).
  13. piknew

    Problems with 5.38 update

    In my case - both Orange Pi+ 2 and Orange Pi+ 2e are using emmc. Currently I am not able to provide any output from serial as I have no physical access to my devices (btw. I do not have serial/usb cable to investigate it ). Information (common for both devices, also the same for 2 devices which have no issues: Orange Pi PC and Orange Pi Zero 512MB H2+): - upgrade from 5.35 to 5.36 was OK - upgrade from 5.36 to 5.37 was OK (I have seen this upgrade was very minor, only 1 package has been updated) - upgrade from 5.37 to 5.38 failed for Opi+2 and Opi+2e (actually I am able to confirm for 100% that I am not able to connect to devices and I am 100% sure that this is not an issue related to e.g. different hwaddres, IP etc.) - either device hasn't booted at all or network interfaces are down (this one can be confirmed by anybody who can check by serial interface) - upgrade from 5.37 to 5.38 was OK for OpiPC and OpiZero - there ware no issues during upgrade process - it was completed without any warnings/errors. - Opi+2 and Opi+2e are using eMMC as main boot device - OpiPC and OpiZero are using SD cards as main boot device (obviously) - All 4 platforms are running with legacy kernel I will have physical access to both devices on Friday, 02.02.2018. I have "tool" SD card which will allow me to boot both devices and if there is any suggestion from this forum - I will be able to make necessary corrections (eg. "dd" new file to emmc boot sectors etc.).
  14. piknew

    Problems with 5.38 update

    Confirmed - both of my Opi+ and Opi+2e are not booting after upgrade to 5.38. OpiPC and OpiZero - no issues.
  15. piknew

    RTC on Banana Pro

    Hi, what you need to do is just check this parameters (do not touch others): BUS="0" ADAPTER=/sys/class/i2c-adapter/i2c-$BUS For example in my Orange Pis (all) it is: root@PKSERVER:~# ls -l /sys/class/i2c-adapter/i2c-0 lrwxrwxrwx 1 root root 0 Jan 1 1970 /sys/class/i2c-adapter/i2c-0 -> ../../devices/platform/twi.0/i2c-0 I do not know Banana SBCs, so that's why I suggested to check and correct path (which is given by two variables as above). BTW. Have you tried running the script without any change? Then try to run script as suggested. Expected result is that your rtc on i2c bus will be registered as /dev/rtc1 (please note that script is not changing original symlink which is /dev/rtc - it is explicitly running hwclock with /dev/rtc1)