Jump to content

ravelo

Members
  • Posts

    18
  • Joined

  • Last visited

Everything posted by ravelo

  1. sorry, I do not understand if this question is an aswer or not.. Ok, I tend to understand that there is no such thing as a maintainer for ambian buster on tritium h5. So be it. I am willing to investigate and fix if I know how to, then publish the solution to the community. But to get started, I would need a small amout of info to know here to look at first.
  2. tks! I've see here https://github.com/armbian/build/blob/master/config/boards/tritium-h5.conf one config file where I see no visible issue, I assume that the device tree for this board is quite bug free nd complete, maybe that's an optimist assumption, so what woulkd you recommend us to do @usual user ?
  3. this distro (https://dl.armbian.com/tritium-h5/Buster_current) has been downloaded from https://www.armbian.com/tritium-h5/ where it is labelled "supported", so @Igor which maintainer could give us an advice, if not try to investigate this misbehaviour please ? tks
  4. hi, I encounter the same error message at boot time on my tritium H5 running armbian buster Linux tritium 5.4.43-sunxi64 #20.05.2 SMP Tue Jun 2 17:20:17 CEST 2020 aarch64 GNU/Linux @Igor, is my problem similar to OP's ? tks
  5. this was my command line (host=ubuntu 18) ./compile.sh docker BOARD=tritium-h5 BRANCH=current KERNEL_ONLY=yes KERNEL_CONFIGURE=yes after 89minutes, all ended ok apparently, and which are the relevant files among.. at boot time, no usb0 is created, and g_ether is not loaded, as per commands below.. raxy@tritium:~$ ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 02:01:e9:b0:da:21 brd ff:ff:ff:ff:ff:ff inet 192.168.200.17/24 brd 192.168.200.255 scope global dynamic noprefixroute eth0 valid_lft 863982sec preferred_lft 863982sec inet6 2a01:e0a:592:5030:f482:2a40:5939:2721/64 scope global dynamic noprefixroute valid_lft 86384sec preferred_lft 86384sec inet6 fe80::c8cb:661b:7238:e753/64 scope link noprefixroute valid_lft forever preferred_lft forever raxy@tritium:~$ lsmod|grep g_ether raxy@tritium:~$ so, i manually loaded g_ether... raxy@tritium:~$ sudo modprobe g_ether [sudo] password for raxy: raxy@tritium:~$ lsmod|grep g_ether g_ether 16384 0 usb_f_rndis 36864 1 g_ether u_ether 28672 2 usb_f_rndis,g_ether libcomposite 61440 3 usb_f_rndis,g_serial,g_ether but still no trace of eth0, wtf !? so, i made the module load at boot time like this (as root)... cd /etc/modules-load.d/ echo "g_ether" >> modules.conf sync; reboot after reboot, lsmod shows g_ether, fine, but still no usb0, and i have this error in dmesg.. [ 5.496280] udc-core: couldn't find an available UDC - added [g_ether] to list of pending drivers again, wtf !?
  6. Hi all, I've read on the forum that support for usb gadget using the µ-usb port on the libre computer tritium needed a kernel reconfigure & recompile. I tried to start with that, but during configuration, I've seen full support already. So, was it supposed to just work ? I target armbian buster server variant. my need is to use IP over an usb (and power) cable between a linux machine (x86 and then arm) and a tritium h5 Thanks in advance
  7. they could tell you youtube does not work in china
  8. 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
  9. 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 ?
  10. 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 ?
  11. 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
  12. @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 ?
  13. @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.
  14. thanks ! will test that , I'm new here, where do I find the instructions on how to flash it and boot it ?
  15. 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
  16. Ok, understood ! but why is SD card (and USB) the only supported way to deploy the image I could build ?
  17. hi @ning is your work applicable to vim1 ?
  18. 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
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines