martinayotte Posted December 29, 2019 Posted December 29, 2019 8 minutes ago, piter75 said: The patch is not needed in rockchip64-dev as it is already incorporated in ayufan's kernel sources we use for dev target. That's why it's being added to current target only with my PR. Right ! I was continuing searching, and figured out that it was even present in his old branches, such as 5.3.0-rc4-1118-ayufan or even very old one 4.20.0-1090-ayufan. And I've just figured out that "current" is not pointing to an ayufan branch anymore ... Also, it seems that @ayufan is busy elsewhere since he didn't create a 5.5.y branch yet ... (and his last commit was done on Aug 13th)
piter75 Posted December 29, 2019 Posted December 29, 2019 15 minutes ago, martinayotte said: Also, it seems that @ayufan is busy elsewhere since he didn't create a 5.5.y branch yet ... (and his last commit was done on Aug 13th) Right... I am thinking more and more often about switching rockchip64-dev's source to: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/ especially that now "current" is built using mainline. Consecutive kernel RCs that appear in this repo would be good candidates for dev builds.
martinayotte Posted December 30, 2019 Posted December 30, 2019 On 12/29/2019 at 5:19 PM, piter75 said: Right... So, should DEV reflect your works on CURRENT ? That would be the first time that will occurs ...
Nobby42 Posted December 30, 2019 Author Posted December 30, 2019 On 12/29/2019 at 9:04 PM, piter75 said: It was not there on rockchip64-current. I prepared a PR that adds it: https://github.com/armbian/build/pull/1699 I am using similar setup but with NVMe hat and I would call it very stable. One thing to mention is that I am using it as a server and not a desktop. I also use the NanoPi as a server. Could it possibly be due to the CPU frequency? The 5.4.6 kernel use 1,5/2Ghz and the 4.4.192 kernel 1,4/1,8Ghz. I'll test it tomorrow.
Nobby42 Posted December 31, 2019 Author Posted December 31, 2019 17 hours ago, Nobby42 said: I also use the NanoPi as a server. Could it possibly be due to the CPU frequency? The 5.4.6 kernel use 1,5/2Ghz and the 4.4.192 kernel 1,4/1,8Ghz. I'll test it tomorrow. The NanoPi don't boot from emmc with roots on SSD with the 5.4.6 kernel. I have attached the boot log. After the Pi found the ssd they do nothing. I have tested variuos SSD. Booting from only SD or only EMMC works fine. nanopi_log201911231_1.txt
piter75 Posted December 31, 2019 Posted December 31, 2019 2 hours ago, Nobby42 said: After the Pi found the ssd they do nothing. I have tested variuos SSD. Does the expected root partition (/dev/sda1) have the UUID of aeeacfab-958f-4131-b208-c9a6d1e7f2b7? You can verify it after attaching the drive to device booted with SD or eMMC and using: lsblk -f
Nobby42 Posted January 2, 2020 Author Posted January 2, 2020 On 12/31/2019 at 5:36 PM, piter75 said: Does the expected root partition (/dev/sda1) have the UUID of aeeacfab-958f-4131-b208-c9a6d1e7f2b7? You can verify it after attaching the drive to device booted with SD or eMMC and using: lsblk -f Happy new year. UUID looks good. Here they are from the last test. lsblk -f NAME FSTYPE LABEL UUID FSAVAIL FSUSE% MOUNTPOINT sda └─sda1 ext4 5a664488-9c46-46a8-92a8-73127b19c54b 215.3G 1% /media/ssd mmcblk2 └─mmcblk2p1 ext4 ddceb71a-f588-4aea-bdb0-2fc352dfef3d 13.3G 1% /media/mmc mmcblk2boot0 mmcblk2boot1 mmcblk1 └─mmcblk1p1 ext4 6afbab68-85eb-40bf-bb45-e469f4b615f5 13G 9% / zram0 41.7M 7% /var/log zram1 [SWAP] cat /media/mmc/boot/armbianEnv.txt verbosity=1 overlay_prefix=rockchip fdtfile=rockchip/rk3399-nanopi-m4v2.dtb rootdev=UUID=5a664488-9c46-46a8-92a8-73127b19c54b rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u cat /media/ssd/etc/fstab # <file system> <mount point> <type> <options> <dump><pass> tmpfs /tmp tmpfs defaults,nosuid 0 0 UUID=ddceb71a-f588-4aea-bdb0-2fc352dfef3d /media/mmcboot ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro,x-gvfs-hide 1 /media/mmcboot/boot /boot none bind 0 0 UUID=5a664488-9c46-46a8-92a8-73127b19c54b / ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro,x-gvfs-hide 1
piter75 Posted January 2, 2020 Posted January 2, 2020 8 hours ago, Nobby42 said: Happy new year. UUID looks good. Happy New Year to you too! I see that you used a Armbian's "nand-sata-install" way to install root to SSD. It looks good. I asked about UUID because I thought that maybe you used some manual steps to do it. I grabbed old EVO 850 drive and really old 2.5" usb enclosure and did the same procedure. It works fine: Spoiler [ 50.698560] usb 7-1.3: new high-speed USB device number 3 using xhci-hcd [ 50.849750] usb 7-1.3: New USB device found, idVendor=04fc, idProduct=0c25, bcdDevice= 1.03 [ 50.849766] usb 7-1.3: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 50.849779] usb 7-1.3: Product: USB to Serial-ATA bridge [ 50.849791] usb 7-1.3: Manufacturer: Sunplus Technology Inc. [ 50.849802] usb 7-1.3: SerialNumber: Samsung XXXXXXXXXXXXX [ 50.854027] usb-storage 7-1.3:1.0: USB Mass Storage device detected [ 50.854825] scsi host0: usb-storage 7-1.3:1.0 [ 50.862064] usbcore: registered new interface driver uas [ 50.974811] usb 8-1: new SuperSpeed Gen 1 USB device number 2 using xhci-hcd [ 50.996734] usb 8-1: New USB device found, idVendor=2109, idProduct=0817, bcdDevice= 0.50 [ 50.996753] usb 8-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 50.996768] usb 8-1: Product: USB3.0 Hub [ 50.996783] usb 8-1: Manufacturer: VIA Labs, Inc. [ 51.019993] hub 8-1:1.0: USB hub found [ 51.020208] hub 8-1:1.0: 4 ports detected [ 51.879358] scsi 0:0:0:0: Direct-Access Samsung SSD 850 EVO 500G B PQ: 0 ANSI: 2 [ 51.881411] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/466 GiB) [ 51.883802] sd 0:0:0:0: [sda] Write Protect is off [ 51.883819] sd 0:0:0:0: [sda] Mode Sense: 38 00 00 00 [ 51.885885] sd 0:0:0:0: [sda] No Caching mode page found [ 51.885899] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 51.914578] sda: sda1 [ 51.923484] sd 0:0:0:0: [sda] Attached SCSI disk [ 52.947291] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) root@nanopim4v2:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 465.8G 0 disk └─sda1 8:1 0 24G 0 part / mmcblk1 179:0 0 29.7G 0 disk └─mmcblk1p1 179:1 0 29.4G 0 part /media/mmcboot zram0 253:0 0 50M 0 disk /var/log zram1 253:1 0 1G 0 disk [SWAP] Of course it does not prove anything as my enclosure is using usb-storage mode and not uas
Nobby42 Posted January 3, 2020 Author Posted January 3, 2020 15 hours ago, piter75 said: Happy New Year to you too! I see that you used a Armbian's "nand-sata-install" way to install root to SSD. It looks good. I asked about UUID because I thought that maybe you used some manual steps to do it. I grabbed old EVO 850 drive and really old 2.5" usb enclosure and did the same procedure. It works fine: Reveal hidden contents [ 50.698560] usb 7-1.3: new high-speed USB device number 3 using xhci-hcd [ 50.849750] usb 7-1.3: New USB device found, idVendor=04fc, idProduct=0c25, bcdDevice= 1.03 [ 50.849766] usb 7-1.3: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 50.849779] usb 7-1.3: Product: USB to Serial-ATA bridge [ 50.849791] usb 7-1.3: Manufacturer: Sunplus Technology Inc. [ 50.849802] usb 7-1.3: SerialNumber: Samsung XXXXXXXXXXXXX [ 50.854027] usb-storage 7-1.3:1.0: USB Mass Storage device detected [ 50.854825] scsi host0: usb-storage 7-1.3:1.0 [ 50.862064] usbcore: registered new interface driver uas [ 50.974811] usb 8-1: new SuperSpeed Gen 1 USB device number 2 using xhci-hcd [ 50.996734] usb 8-1: New USB device found, idVendor=2109, idProduct=0817, bcdDevice= 0.50 [ 50.996753] usb 8-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 50.996768] usb 8-1: Product: USB3.0 Hub [ 50.996783] usb 8-1: Manufacturer: VIA Labs, Inc. [ 51.019993] hub 8-1:1.0: USB hub found [ 51.020208] hub 8-1:1.0: 4 ports detected [ 51.879358] scsi 0:0:0:0: Direct-Access Samsung SSD 850 EVO 500G B PQ: 0 ANSI: 2 [ 51.881411] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/466 GiB) [ 51.883802] sd 0:0:0:0: [sda] Write Protect is off [ 51.883819] sd 0:0:0:0: [sda] Mode Sense: 38 00 00 00 [ 51.885885] sd 0:0:0:0: [sda] No Caching mode page found [ 51.885899] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 51.914578] sda: sda1 [ 51.923484] sd 0:0:0:0: [sda] Attached SCSI disk [ 52.947291] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) root@nanopim4v2:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 465.8G 0 disk └─sda1 8:1 0 24G 0 part / mmcblk1 179:0 0 29.7G 0 disk └─mmcblk1p1 179:1 0 29.4G 0 part /media/mmcboot zram0 253:0 0 50M 0 disk /var/log zram1 253:1 0 1G 0 disk [SWAP] Of course it does not prove anything as my enclosure is using usb-storage mode and not uas Hi piter75, thanks for your support. I ran some tests yesterday. During the last test I made a mistake and forgot to remove the SD card and the Pi boots with all memory media. After booting I saw that the ROOTFS is on the device /dev/sda1. Why? It looks like it booted from a mix of SD and EMMC and rootfs on sda1 lsblk -f NAME FSTYPE LABEL UUID FSAVAIL FSUSE% MOUNTPOINT sda └─sda1 ext4 b1a869c6-23b1-4254-b604-6c8e9abe4440 215.3G 1% / mmcblk2 └─mmcblk2p1 ext4 71e19ca5-088d-4ecb-aa80-97d8e8445f20 13.3G 1% /media/mmcboot mmcblk2boot0 mmcblk2boot1 mmcblk1 └─mmcblk1p1 ext4 c2a23e0b-b4a8-475a-a890-a9f2f107f46a 13G 9% /media/sd-card zram0 39.5M 11% /var/log zram1 [SWAP] cat /media/mmcboot/boot/armbianEnv.txt verbosity=7 overlay_prefix=rockchip fdtfile=rockchip/rk3399-nanopi-m4v2.dtb rootdev=UUID=b1a869c6-23b1-4254-b604-6c8e9abe4440 rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u cat /media/sd-card/boot/armbianEnv.txt verbosity=1 overlay_prefix=rockchip fdtfile=rockchip/rk3399-nanopi-m4v2.dtb rootdev=UUID=c2a23e0b-b4a8-475a-a890-a9f2f107f46a rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u cat /media/sd-card/etc/fstab UUID=c2a23e0b-b4a8-475a-a890-a9f2f107f46a / ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro 0 1 tmpfs /tmp tmpfs defaults,nosuid 0 0 nobby@Viking:~$ ^C nobby@Viking:~$ cat /boot/armbianEnv.txt verbosity=7 overlay_prefix=rockchip fdtfile=rockchip/rk3399-nanopi-m4v2.dtb rootdev=UUID=b1a869c6-23b1-4254-b604-6c8e9abe4440 rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u cat /etc/fstab # <file system> <mount point> <type> <options> <dump> <pass> tmpfs /tmp tmpfs defaults,nosuid 0 UUID=71e19ca5-088d-4ecb-aa80-97d8e8445f20 /media/mmcboot ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro,x-gvfs-hide 0 1 /media/mmcboot/boot /boot none bind 0 0 UUID=b1a869c6-23b1-4254-b604-6c8e9abe4440 / ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro,x-gvfs-hide 0 1 Very mysterious. Here are the armbianmonitor output. http://ix.io/26eq When I boot from emmc I see this error. MMC: dwmmc@fe320000: 1, sdhci@fe330000: 0 Loading Environment from EXT4... ** File not found /boot/boot.env ** ** Unable to read "/boot/boot.env" from mmc0:1 ** Something wrong with the emmc? I have found this topic and will test it today. https://tinkerboarding.co.uk/forum/post-8800.html
martinayotte Posted January 3, 2020 Posted January 3, 2020 4 hours ago, Nobby42 said: Loading Environment from EXT4... ** File not found /boot/boot.env ** ** Unable to read "/boot/boot.env" from mmc0:1 ** This is not an error but a warning from u-boot. Armbrian doesn't need /boot/boot.env by default ...
piter75 Posted January 3, 2020 Posted January 3, 2020 5 hours ago, Nobby42 said: I ran some tests yesterday. During the last test I made a mistake and forgot to remove the SD card and the Pi boots with all memory media. After booting I saw that the ROOTFS is on the device /dev/sda1. Why? It looks like it booted from a mix of SD and EMMC and rootfs on sda1 Do I understand correctly that you first booted from SD with eMMC inserted and then chosen an option "Boot from eMMC - system on SATA" in "nand-sata-install"? Can you try doing it in two separate steps? 1. Install from SD to eMMC (option "Boot from eMMC - system on eMMC" in nand-sata-install) or write image straight to eMMC with adapter 2. Boot from eMMC (remember to remove SD card ;-)) and move rootfs to SATA (option "Boot from eMMC - system on SATA" in nand-sata-install) I will verify the SD straight to eMMC with SATA procedure on my side.
Nobby42 Posted January 3, 2020 Author Posted January 3, 2020 50 minutes ago, piter75 said: Do I understand correctly that you first booted from SD with eMMC inserted and then chosen an option "Boot from eMMC - system on SATA" in "nand-sata-install"? Can you try doing it in two separate steps? 1. Install from SD to eMMC (option "Boot from eMMC - system on eMMC" in nand-sata-install) or write image straight to eMMC with adapter 2. Boot from eMMC (remember to remove SD card ;-)) and move rootfs to SATA (option "Boot from eMMC - system on SATA" in nand-sata-install) I will verify the SD straight to eMMC with SATA procedure on my side. Hi piter75, I think I found the problem. The UAS. https://unix.stackexchange.com/questions/441668/debian-usb3-hdd-uas-i-o-errors After I add the USB-ID for my adapter in the armbianEnv.txt the SSD was black list für the UAS and the board booting with the rootfs on the SSD. [ 56.463044] hub 8-1:1.0: USB hub found [ 56.463741] hub 8-1:1.0: 4 ports detected [ 57.026120] usb 8-1.2: new SuperSpeed Gen 1 USB device number 3 using xhci-hcd [ 57.047008] usb 8-1.2: New USB device found, idVendor=174c, idProduct=55aa, bcdDevice= 1.00 [ 57.047771] usb 8-1.2: New USB device strings: Mfr=2, Product=3, SerialNumber=1 [ 57.048436] usb 8-1.2: Product: ASM1153USB3.0TOSATA [ 57.048886] usb 8-1.2: Manufacturer: ASM1153USB3.0TOSATA [ 57.049374] usb 8-1.2: SerialNumber: 123456789019 [ 57.051688] usb 8-1.2: UAS is blacklisted for this device, using usb-storage instead [ 57.052403] usb-storage 8-1.2:1.0: USB Mass Storage device detected [ 57.053572] usb-storage 8-1.2:1.0: Quirks match for vid 174c pid 55aa: c00000 [ 57.054428] scsi host0: usb-storage 8-1.2:1.0 [ 57.060247] usbcore: registered new interface driver uas [ 58.058774] scsi 0:0:0:0: Direct-Access ASM1153U ASM1153USB3.0TOS 0 PQ: 0 ANSI: 6 [ 58.062417] sd 0:0:0:0: [sda] 488397168 512-byte logical blocks: (250 GB/233 GiB) [ 58.064363] sd 0:0:0:0: [sda] Write Protect is off [ 58.065331] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 58.097560] sda: sda1 [ 58.104521] sd 0:0:0:0: [sda] Attached SCSI disk
piter75 Posted January 3, 2020 Posted January 3, 2020 1 hour ago, Nobby42 said: I think I found the problem. The UAS. Case closed... or at least worked around
Nobby42 Posted January 3, 2020 Author Posted January 3, 2020 36 minutes ago, piter75 said: Case closed... or at least worked around Yes ;-) Thanks for your support.
Igor Posted January 4, 2020 Posted January 4, 2020 @Nobby42 Welcome to add it to our defaults: https://github.com/armbian/build/blob/master/packages/bsp/common/usr/lib/armbian/armbian-hardware-optimization#L299 It can take some time before this gets upstream.
denni_isl Posted January 5, 2020 Posted January 5, 2020 nanopi-m4v2 - kernel 5.3.11 usb-storage not working and external usb sound card not detected and flickering screen after armbian-config firmware upgrade yesterday (4.jan) but usb network and keyboard working fine. The same with kernel 5.4.0 (all of them, also 19.11.5.365)
piter75 Posted January 5, 2020 Posted January 5, 2020 4 hours ago, denni_isl said: nanopi-m4v2 - kernel 5.3.11 5.3.x was never tested with this board. Support for the board was released mid cycle between Armbian releases and it probably got downgraded to 5.3.x version with "apt upgrade". Try downloading a current (19.11.5 / 5.4.7) image from here: https://dl.armbian.com/nanopim4v2/archive/ and see if it works better. This image should not downgrade by itself.
Nobby42 Posted January 5, 2020 Author Posted January 5, 2020 On 1/4/2020 at 2:24 PM, Igor said: @Nobby42 Welcome to add it to our defaults: https://github.com/armbian/build/blob/master/packages/bsp/common/usr/lib/armbian/armbian-hardware-optimization#L299 It can take some time before this gets upstream. Hi, I have no experience with GitHub, but I'll look into it. It may take a while.
Chad Posted April 26, 2020 Posted April 26, 2020 Dear all， Has anyone tested the GPIO on this V2 board? I tried to test the GPIO with ARMBianIO from the github : https://github.com/bitbank2/ArmbianIO/ , but failed. Thanks Chad
Recommended Posts