ravelo

Members
  • Content Count

    12
  • Joined

  • Last visited

About ravelo

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. they could tell you youtube does not work in china
  2. in patch_mainline_kernel() in https://pastebin.com/BZLCyg5Q , the changes needed for 4.12 were not so heavy regarding emmc, i will try to apply the same to 5.3
  3. so, once armbian is written into EMMC and boots from it, how do we upgrade , later, just the kernel (example from 5.3rcx to 5.3.y) without reflashing the full distro ?
  4. once armbian would boot from SD, then writes itself entirely on the EMMC, does it replace change amlogic/khadas' EMMC "android" partitionning table to something more common like GPT ?
  5. afaik, the official khadas ubuntu booted from the EMMC does use a single partition to host all files, here are a few command results maybe confirming my intuition.. could I be wrong ? The fact is that the mainline kernels cannot read the EMMC's partitions as of now (maybe some patches can solve that, as they did sometime in the past when we had made an ubuntu image based on a customized mainline kernel 4.12 that was directly burnt into the EMMC using the amlogic tools; and it booted and run fine) khadas@Khadas:~$ sudo blkid [sudo] password for khadas: /dev/rootfs: LABEL="ROOTFS" UUID="eb0ce16e-cb91-4523-9ed4-987eb7055203" TYPE="ext4" /dev/zram1: UUID="187ab012-22a1-4ca3-a131-2510250ab3a6" TYPE="swap" /dev/zram2: UUID="d52c3310-b45a-428e-886b-7cb98b2cbbbc" TYPE="swap" /dev/zram3: UUID="00e4ba55-8230-4200-8e2f-e4be338cb6ba" TYPE="swap" /dev/zram4: UUID="03039fa4-a3a7-46bf-9206-34fed389840d" TYPE="swap" khadas@Khadas:~$ mount sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /dev type devtmpfs (rw,nosuid,relatime,size=781856k,nr_inodes=195464,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=203572k,mode=755) /dev/rootfs on / type ext4 (rw,relatime,data=writeback) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) cgroup on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd) pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) cgroup on /sys/fs/cgroup/schedtune type cgroup (rw,nosuid,nodev,noexec,relatime,schedtune) cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb) cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) cgroup on /sys/fs/cgroup/debug type cgroup (rw,nosuid,nodev,noexec,relatime,debug) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=24,pgrp=1,timeout=0,minproto=5,maxproto=5,direct) mqueue on /dev/mqueue type mqueue (rw,relatime) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime) debugfs on /sys/kernel/debug type debugfs (rw,relatime) fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime) configfs on /sys/kernel/config type configfs (rw,relatime) tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=203568k,mode=700,uid=1000,gid=1000) khadas@Khadas:~$ cat /proc/partitions major minor #blocks name 179 0 15267840 mmcblk0 179 1 4096 mmcblk0p1 179 2 65536 mmcblk0p2 179 3 8192 mmcblk0p3 179 4 8192 mmcblk0p4 179 5 32768 mmcblk0p5 179 6 15083520 mmcblk0p6 179 96 4096 mmcblk0rpmb 179 64 4096 mmcblk0boot1 179 32 4096 mmcblk0boot0 251 1 254464 zram1 251 2 254464 zram2 251 3 254464 zram3 251 4 254464 zram4
  6. @TonyMac32 I see armbian has an option to install itself totally in EMMC, once it has booted from an SD card. in that case, what kind of emmc partition structure did you choose to use and how different (and better?) is it compared to that android structure you mentionned ?
  7. @TonyMac32 this tool https://androidpctv.com/amlogic-usb-burning-tool-v2170/ is maybe able to burn android firmwares to ATV boxes, I never used it for such a purpose, we do use it to flash official (and custom) ubuntu firmwares to VIM1's EMMC, and it works ok for that task; afaik, there is also a linux based binary that can do almost the same, from a shell command line.
  8. thanks ! will test that , I'm new here, where do I find the instructions on how to flash it and boot it ?
  9. for an amlogic board that comes natively with some EMMC and because amlogic provides tools for flashing firmware images on said EMMC, I expect that we can build some mainline based kernel firmware image that we would directly flash to said EMMC
  10. Ok, understood ! but why is SD card (and USB) the only supported way to deploy the image I could build ?
  11. hi @ning is your work applicable to vim1 ?
  12. hi all, i'm ravelo fom the khadas forum, does an armbian distro image with mainline 5.3 kernel exists and that is flashable on vim1's emmc using the window amlogic burning tool ? (or using dd) thanks a lot