[NanoPC T4 bluetooth (mainline kernel)]

13 hours ago, martinayotte said:

Really strange ...

As a workaround try to change that line /etc/fstab of the SSD :

UUID=6984f986-8788-4dc7-9e57-e5a27d39a7d6   /       ext4    defaults,noatime,nodiratime,commit=600,errors=remount-ro,x-gvfs-hide    0   1

with :

/dev/nvme0n1p1   /       ext4    defaults,noatime,nodiratime,commit=600,errors=remount-ro,x-gvfs-hide    0   1

 

I cannot test this right now, but my suspicion is, that it is caused by the modularization of the nvme driver. The modules are inside of the initrd, but might not be loaded properly.

 

$ grep -i nvme config-4.4.156-rk3399
CONFIG_BLK_DEV_NVME=y
CONFIG_NVMEM=y

 

$ grep -i nvme config-4.19.0-rk3399
# NVME Support
CONFIG_NVME_CORE=m
CONFIG_BLK_DEV_NVME=m
CONFIG_NVME_MULTIPATH=y
CONFIG_NVME_FABRICS=m
CONFIG_NVME_FC=m
CONFIG_NVME_TARGET=m
CONFIG_NVME_TARGET_LOOP=m
CONFIG_NVME_TARGET_FC=m
# CONFIG_NVME_TARGET_FCLOOP is not set
CONFIG_RTC_NVMEM=y

 

Adding the modules to /etc/modules and updating the initrd might help. I will test this as soon as I can.

 

Sorry for hijacking this thread. I installed the mainline-kernel to test bluetooth. What's the appropriate place to issue a bug report about this?

[NanoPC T4 bluetooth (mainline kernel)]

Yes, "6984f986-8788-4dc7-9e57-e5a27d39a7d6" is the root partition.

/etc/fstab:

# <file system>                 <mount point>   <type>  <options>                           <dump>  <pass>
tmpfs                       /tmp        tmpfs   defaults,nosuid                         0   0
UUID=53822d9c-1cb2-4a65-96e1-c20e030c4615   /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=6984f986-8788-4dc7-9e57-e5a27d39a7d6   /       ext4    defaults,noatime,nodiratime,commit=600,errors=remount-ro,x-gvfs-hide    0   1

 

 

[NanoPC T4 bluetooth (mainline kernel)]

54 minutes ago, martinayotte said:

If you got this message, it doesn't seems to match with /boot/armbianEnv.txt and /etc/fstab ...

Check it with the command "blkid" !

root@nanopct4:~# blkid
/dev/nvme0n1p1: UUID="6984f986-8788-4dc7-9e57-e5a27d39a7d6" TYPE="ext4" PARTLABEL="Linux filesystem" PARTUUID="85cf3890-e009-4640-b803-b868558967b1"
/dev/mmcblk1p1: UUID="53822d9c-1cb2-4a65-96e1-c20e030c4615" TYPE="ext4" PARTUUID="492db6dc-01"
/dev/nvme0n1: PTUUID="ccc5a30e-c5ff-463d-9514-dceb88c77f01" PTTYPE="gpt"
/dev/mmcblk1: PTUUID="492db6dc" PTTYPE="dos"
/dev/zram0: LABEL="log2ram" UUID="c13859e3-cb78-489a-89d0-e147116b6f8c" TYPE="ext4"
/dev/zram1: UUID="8346ad54-ee77-44ed-a14d-52cea05b4f10" TYPE="swap"
/dev/zram2: UUID="b96d2711-611b-4bb5-83b0-f43f6b235e72" TYPE="swap"
/dev/zram3: UUID="953d115a-07d3-4b62-83eb-f0d05bac59c8" TYPE="swap"
/dev/zram4: UUID="46fce07f-d5df-41d1-b833-2c673213d05b" TYPE="swap"

root@nanopct4:~# grep 6984f986-8788-4dc7-9e57-e5a27d39a7d6 /etc/fstab
UUID=6984f986-8788-4dc7-9e57-e5a27d39a7d6    /        ext4    defaults,noatime,nodiratime,commit=600,errors=remount-ro,x-gvfs-hide

root@nanopct4:~# grep 6984f986-8788-4dc7-9e57-e5a27d39a7d6 /boot/armbianEnv.txt
rootdev=UUID=6984f986-8788-4dc7-9e57-e5a27d39a7d6

 

It does exist when booting the stable kernel. After upgrading to linux-image-dev-rk3399 it doesn't find the device and halts with the alert. I tried it twice with the same result and had to switch back to stable kernel each time.

[NanoPC T4 bluetooth (mainline kernel)]

On 11/28/2018 at 3:37 PM, martinayotte said:

Check the UUID of your SSD and make sure that this UUID is the one used in both /boot/armbranEnv.txt and /etc/fstab.

It was. I made a copy of the files and checked. The error message was:

ALERT! UUID=69... does not exist. Dropping to a shell!

Rebooting automatically due to panic= boot argument

[NanoPC T4 bluetooth (mainline kernel)]

I tried to install mainline kernel yesterday and my nanopc-t4 stopped booting. It couldn't find the root-fs, which is on SSD. Could fix it with reverting back to stable. Edited to add: This was on a Ubuntu Bionic build.

[NanoPC T4]

On 11/2/2018 at 11:51 AM, Alexio said:

I see multiple people facing issues with the OS on eMMC. Is it safe to "Etcher" the ROM below to a SD card,  apt update && apt upgrade, followed by a nand-sata-install in the armbina-config utility?

ROM: OMV_4_NanoPC_T4.img.xz (2018-10-09) (source)

Or could I install the ROM directly onto the eMMC by following the proces 'Flash Image under Windows with Type-C Cable' (FriendlyARM wiki)? The wiki mentions "images-for-eflasher" so I'm unsure if the ROM needs to be specifically prepared to enable this flashing method.

 

I didn't have problems with eMMC-Installation. I booted from SD-Card and used armbian-config to install to eMMC. No need to use other flash methods.

[made some progress with the NanoPC-T4 today]

On 11/24/2018 at 11:08 PM, jerryn said:

I've got bluetooth working flawlessly. 

 

Can you give me a hint? Using the nightly build, bluetooth still doesn't start the daemon.

[NanoPC T4]

On 9/19/2018 at 10:39 AM, tkaiser said:

 

Boot priority with Rockchip boards is AFAIK always eMMC first then SD card. So once RK3399 finds a bootloader signature on the eMMC it will boot from there even if a bootable SD card is inserted. If you want to reflash eMMC in this situation you

• delete the bootloader on the eMMC (can be done from the running system: 'dd if=/dev/null of=/dev/mmcblk1 bs=1M count=64 ; sync')

 

This worked for me, when using the right device for the zero source

• 'dd if=/dev/zero of=/dev/mmcblk1 bs=1M count=64 ; sync'