PINE64
RockPro64 powerful enough as a Plex Media Server? - Printable Version

+- PINE64 (https://forum.pine64.org)
+-- Forum: ROCKPRO64 (https://forum.pine64.org/forumdisplay.php?fid=98)
+--- Forum: General Discussion on ROCKPRO64 (https://forum.pine64.org/forumdisplay.php?fid=99)
+--- Thread: RockPro64 powerful enough as a Plex Media Server? (/showthread.php?tid=6394)

Pages: 1 2

RE: RockPro64 powerful enough as a Plex Media Server? - Takenover83 - 09-16-2018

Hmm. I tried setting a default by adding "default kernel-4.18" to the extlinux.conf. But it's still booting 4.4. Care to share what your extlinux.conf looks like? Thanks for the help.

Code:
timeout 10 menu title select kernel default kernel-4.18 label kernel-4.18    kernel /boot/vmlinuz-4.18.0-rc8-1060-ayufan-g45828c4db727    initrd /boot/initrd.img-4.18.0-rc8-1060-ayufan-g45828c4db727    devicetreedir /boot/dtbs/4.18.0-rc8-1060-ayufan-g45828c4db727    append rw panic=10 init=/sbin/init coherent_pool=1M ethaddr=${ethaddr} eth1addr=${eth1addr} serial=${serial#} cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 root=LABEL=linux-root rootwait rootfstype=ext4 label kernel-4.18.0-rc8-1060-ayufan-g45828c4db727-memtest    kernel /boot/vmlinuz-4.18.0-rc8-1060-ayufan-g45828c4db727    initrd /boot/initrd.img-4.18.0-rc8-1060-ayufan-g45828c4db727    devicetreedir /boot/dtbs/4.18.0-rc8-1060-ayufan-g45828c4db727    append rw panic=10 init=/sbin/init coherent_pool=1M ethaddr=${ethaddr} eth1addr=${eth1addr} serial=${serial#} cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 root=LABEL=linux-root rootwait rootfstype=ext4 memtest label kernel-4.4.132-1075-rockchip-ayufan-ga83beded8524     kernel /boot/vmlinuz-4.4.132-1075-rockchip-ayufan-ga83beded8524     initrd /boot/initrd.img-4.4.132-1075-rockchip-ayufan-ga83beded8524     devicetreedir /boot/dtbs/4.4.132-1075-rockchip-ayufan-ga83beded8524     append rw panic=10 init=/sbin/init coherent_pool=1M ethaddr=${ethaddr} eth1addr=${eth1addr} serial=${serial#} cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 root=LABEL=linux-root rootwait rootfstype=ext4 label kernel-4.4.132-1075-rockchip-ayufan-ga83beded8524-memtest     kernel /boot/vmlinuz-4.4.132-1075-rockchip-ayufan-ga83beded8524     initrd /boot/initrd.img-4.4.132-1075-rockchip-ayufan-ga83beded8524     devicetreedir /boot/dtbs/4.4.132-1075-rockchip-ayufan-ga83beded8524     append rw panic=10 init=/sbin/init coherent_pool=1M ethaddr=${ethaddr} eth1addr=${eth1addr} serial=${serial#} cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 root=LABEL=linux-root rootwait rootfstype=ext4 memtest


RE: RockPro64 powerful enough as a Plex Media Server? - dukla2000 - 09-17-2018

I do not claim full expertise in this area, but for whatever reason I believe the default line has to be first line. (Otherwise it is ignored and the first entry is used - in your case is 4.18 so you should be booting 4.18 either way!!) Did you boot 4.18 after the install? 

Mine is

Code:
$ cat /boot/extlinux/extlinux.conf default kernel-4.4.138 timeout 10 menu title select kernel label kernel-4.18.0     kernel /boot/vmlinuz-4.18.0-rc8-76686-g45828c4db727-dirty     initrd /boot/initrd.img-4.18.0-rc8-76686-g45828c4db727-dirty     devicetreedir /boot/dtbs/4.18.0-rc8-76686-g45828c4db727-dirty     append rw panic=10 init=/sbin/init coherent_pool=1M ethaddr=${ethaddr} eth1addr=${eth1addr} serial=${serial#} cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 root=LABEL=MySM961 rootwait rootfstype=ext4 label kernel-4.18.0-rc8-1060-ayufan-g45828c4db727     kernel /boot/vmlinuz-4.18.0-rc8-1060-ayufan-g45828c4db727     initrd /boot/initrd.img-4.18.0-rc8-1060-ayufan-g45828c4db727     devicetreedir /boot/dtbs/4.18.0-rc8-1060-ayufan-g45828c4db727     append rw panic=10 init=/sbin/init coherent_pool=1M ethaddr=${ethaddr} eth1addr=${eth1addr} serial=${serial#} cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 root=LABEL=MySM961 rootwait rootfstype=ext4 label kernel-4.4.138     kernel /boot/vmlinuz-4.4.138-1094-rockchip-ayufan-gf13a8a9a4eee     initrd /boot/initrd.img-4.4.138-1094-rockchip-ayufan-gf13a8a9a4eee     devicetreedir /boot/dtbs/4.4.138-1094-rockchip-ayufan-gf13a8a9a4eee     append rw panic=10 init=/sbin/init coherent_pool=1M ethaddr=${ethaddr} eth1addr=${eth1addr} serial=${serial#} cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 root=LABEL=MySM961 rootwait rootfstype=ext4 label kernel-4.4.132-1075-rockchip-ayufan-ga83beded8524     kernel /boot/vmlinuz-4.4.132-1075-rockchip-ayufan-ga83beded8524     initrd /boot/initrd.img-4.4.132-1075-rockchip-ayufan-ga83beded8524     devicetreedir /boot/dtbs/4.4.132-1075-rockchip-ayufan-ga83beded8524     append rw panic=10 init=/sbin/init coherent_pool=1M ethaddr=${ethaddr} eth1addr=${eth1addr} serial=${serial#} cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 root=LABEL=MySM961 rootwait rootfstype=ext4 chris@rpro64:~$ uname -a Linux rpro64.dukla.net 4.4.138-1094-rockchip-ayufan-gf13a8a9a4eee #1 SMP Thu Aug 9 20:29:55 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux

<Mine is slightly complicated as I have my rootfs on my NVMe drive, which also means I have to maintain it on both the SDcard that is used for cold boot as well as the NVMe which is used for reboot!>

RE: RockPro64 powerful enough as a Plex Media Server? - Bullet64 - 09-17-2018

From my sd-card

/boot/extlinux/extlinux.conf

Code:
timeout 10 menu title select kernel label kernel-4.18.0-rc8-1060-ayufan-g45828c4db727    kernel /boot/vmlinuz-4.18.0-rc8-1060-ayufan-g45828c4db727    initrd /boot/initrd.img-4.18.0-rc8-1060-ayufan-g45828c4db727    devicetreedir /boot/dtbs/4.18.0-rc8-1060-ayufan-g45828c4db727    append rw panic=10 init=/sbin/init coherent_pool=1M ethaddr=${ethaddr} eth1addr=${eth1addr} serial=${serial#} cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 root=LABEL=linux-root rootwait rootfstype=ext4 label kernel-4.18.0-rc8-1060-ayufan-g45828c4db727-memtest    kernel /boot/vmlinuz-4.18.0-rc8-1060-ayufan-g45828c4db727    initrd /boot/initrd.img-4.18.0-rc8-1060-ayufan-g45828c4db727    devicetreedir /boot/dtbs/4.18.0-rc8-1060-ayufan-g45828c4db727    append rw panic=10 init=/sbin/init coherent_pool=1M ethaddr=${ethaddr} eth1addr=${eth1addr} serial=${serial#} cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 root=LABEL=linux-root rootwait rootfstype=ext4 memtest label kernel-4.4.138-1094-rockchip-ayufan-gf13a8a9a4eee    kernel /boot/vmlinuz-4.4.138-1094-rockchip-ayufan-gf13a8a9a4eee    initrd /boot/initrd.img-4.4.138-1094-rockchip-ayufan-gf13a8a9a4eee    devicetreedir /boot/dtbs/4.4.138-1094-rockchip-ayufan-gf13a8a9a4eee    append rw panic=10 init=/sbin/init coherent_pool=1M ethaddr=${ethaddr} eth1addr=${eth1addr} serial=${serial#} cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 root=LABEL=linux-root rootwait rootfstype=ext4 label kernel-4.4.138-1094-rockchip-ayufan-gf13a8a9a4eee-memtest    kernel /boot/vmlinuz-4.4.138-1094-rockchip-ayufan-gf13a8a9a4eee    initrd /boot/initrd.img-4.4.138-1094-rockchip-ayufan-gf13a8a9a4eee    devicetreedir /boot/dtbs/4.4.138-1094-rockchip-ayufan-gf13a8a9a4eee    append rw panic=10 init=/sbin/init coherent_pool=1M ethaddr=${ethaddr} eth1addr=${eth1addr} serial=${serial#} cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 root=LABEL=linux-root rootwait rootfstype=ext4 memtest label kernel-4.4.132-1075-rockchip-ayufan-ga83beded8524    kernel /boot/vmlinuz-4.4.132-1075-rockchip-ayufan-ga83beded8524    initrd /boot/initrd.img-4.4.132-1075-rockchip-ayufan-ga83beded8524    devicetreedir /boot/dtbs/4.4.132-1075-rockchip-ayufan-ga83beded8524    append rw panic=10 init=/sbin/init coherent_pool=1M ethaddr=${ethaddr} eth1addr=${eth1addr} serial=${serial#} cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 root=LABEL=linux-root rootwait rootfstype=ext4 label kernel-4.4.132-1075-rockchip-ayufan-ga83beded8524-memtest    kernel /boot/vmlinuz-4.4.132-1075-rockchip-ayufan-ga83beded8524    initrd /boot/initrd.img-4.4.132-1075-rockchip-ayufan-ga83beded8524    devicetreedir /boot/dtbs/4.4.132-1075-rockchip-ayufan-ga83beded8524    append rw panic=10 init=/sbin/init coherent_pool=1M ethaddr=${ethaddr} eth1addr=${eth1addr} serial=${serial#} cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 root=LABEL=linux-root rootwait rootfstype=ext4 memtest

Sys is booting into 4.18.0

Code:
rock64@rockpro64v_2_1:/boot/extlinux$ uname -a Linux rockpro64v_2_1 4.18.0-rc8-1060-ayufan-g45828c4db727 #1 SMP PREEMPT Thu Aug 9 19:41:21 UTC 2018 aarch64 aarch64 aarch64 GNU/Linux


RE: RockPro64 powerful enough as a Plex Media Server? - Takenover83 - 09-17-2018

Interesting enough. Even if I remove all 4.4 entries from /boot/extlinux.conf, I am still booting into 4.4 on the dietpi distro. Maybe something to do with my work around I am doing just to boot my emmc? Not sure. Will have to backup, flash to sd, and reboot to see if the problem persist.

Edit: Sure enough. Booted straight to 4.18 once I switched from emmc to sd.

RE: RockPro64 powerful enough as a Plex Media Server? - dukla2000 - 09-18-2018

I think what is happening on your system is as follows:

1) Although you have both eMMC & SDcard installed the initial uboot feed is from the SDcard as your eMMC boot0 and boot1 segments are not properly "loaded". So the /boot/extlinux/extlinux.conf on your SDcard is what counts.

2) Both your SDcard partition 7 and your eMMC partition 7 will have a label "linux-root". This can be checked with sudo blkid - if so although uboot picks up extlinux.conf from the SDcard the loader will then find p7 on your eMMC as linux-root and use that. so df -h will show /dev/mmcblk1p7 mounted as rootfs.

3) In this setup, when you install 4.18 the extlinux.conf on the eMMC will be updated (because that is where linux is working with rootfs), but on reboot you will be back to step 1 and so you still booted 4.4. The necessary extra step is to keep the /boot/ directory on both the SDcard and eMMC synchronised so you get expected results.

You probably do want your rootfs on the eMMC as it is faster than SDcard. So until you sort the eMMC ability to boot on its own, you need to keep repeating the synchronisation of /boot/ directories. I have to do exactly this as I use NVMe for rootfs: so I have a little script to run after each time I modify my extlinux.conf and before I reboot:

Code:
$cat syncsd sudo mount /dev/mmcblk0p7 /mnt/ sudo rsync -ax --delete /boot/ /mnt/boot/ cat /mnt/boot/extlinux/extlinux.conf