Datasets:

---

clips

/

mqa

like 52

Follow

CLiPS 10

[ { "text": "You can choose a particular writer if you have been ordering from us and know the writing style. We will assign your order to a preferred writer if the person does not have an order in progress.   \n", "name": "", "is_accepted": true } ]

[ { "text": "Inform us about your ideas and the area of nursing you want to focus on your project. We have helped many to develop a good topic with relevance to the project.  \n \n", "name": "", "is_accepted": true } ]

[ { "text": " We have a rush order option for papers with a tight deadline. Send us your order instructions and length. We will evaluate and inform you of the shortest time it will take to complete your paper. \n ", "name": "", "is_accepted": true } ]

[ { "text": " Our professionalism dictates that we write orders from scratch. The researches data direct from sources are put in a citation for a reader to see we have acknowledged the source. A plagiarism test is mandatory for all orders before delivering them to customers. ", "name": "", "is_accepted": true } ]

[ { "text": "You will highlight them and inform the customer support agents. They will immediately notify the quality assurance department. QAD will recommend revisions if the writer did not follow all guidelines or made some mistakes. ", "name": "", "is_accepted": true } ]

[ { "text": "We have a money-back guarantee for all orders. it is unusual to get refund requests because we satisfy the customers, but we can refund in case of lateness, plagiarism or inability to meet the requirements ", "name": "", "is_accepted": true } ]

[ { "text": "Your sensitive data is completely secure with us. To avoid data theft, we use SSL (Secure Socket Layer) to encrypt it while transferring from your browser to our server. Besides, we don't share it with the writers, instead each of your order is assigned anonymous ID. ", "name": "", "is_accepted": true } ]

[ { "text": "Sure. We do our best to preserve your anonymity and ensure that our cooperation is totally confidential.\n ", "name": "", "is_accepted": true } ]

[ { "text": "You can freely use our sample papers in a number of ways, if properly referenced:\nAs a source of information for a research of your own\nAs additional materials to help you better understand the subject\nDirect citing\nStill, we suggest you consult with your college/university policies to make sure your do not act against them.", "name": "", "is_accepted": true } ]

[ { "text": "We deliver only papers free of any plagiarism. We check every paper a few times to assure full originality of the writer’s work. We do not cooperate with writers who tolerate plagiarism. We guarantee that you will get a unique paper.\n ", "name": "", "is_accepted": true } ]

[ { "text": "We provide a money-back guarantee in case you are not satisfied with the result. Take a look at our Refund Policy page to get more details.\n", "name": "", "is_accepted": true } ]

[ { "text": "You set the deadline yourself, and we always follow it. We are able to write some types of papers within 3 hours, but even if the deadline is not that tight, you'll most likely get the completed paper beforehand. We always try to spare some time for you to review the work and do revisions if needed.\n\n \n", "name": "", "is_accepted": true } ]

[ { "text": "We work with the writers from around the globe. What matters for us is not their country of origin, but their professionalism and expertise. So we hire only with writers who have experience in academic writing and major in at least one of the disciplines we offer services in.\n ", "name": "", "is_accepted": true } ]

[ { "text": "If you feel the paper does not fit your standards and requirements, you can request a revision. You will get free revisions within 10 days after the scheduled deadline. ", "name": "", "is_accepted": true } ]

[ { "text": "hi there,\n\ndepending on the amount of devices in your network, healing can take a really long time.\n\nalso when the heart can’t connect to sleeping devices it tries it 3 times, so see if you can wake them up when it’s their turn.\n\nmaybe the devices has lost it’s route, you can check it [this way.](https://talk.animushome.com/t/mesh-not-working/268/10)\n\nbut…", "name": "", "is_accepted": true } ]

[ { "text": "hi, if your device support s2, then the app will automatically guide you through the s2 process. there is also a good blog-post that i know of, showing some screens on how it looks in the app when adding s2 devices; [https://blog.animushome.com/2018/05/30/understanding-s0s2-and-the-newly-discovered-z…](https://blog.animushome.com/2018/05/30/understanding-s0s2-and-the-newly-discovered-z-wave-hack-z-shave/)", "name": "", "is_accepted": true } ]

[ { "text": "hi \nhad a similar support ticket. resolved by: \nremoving deleted devices from homekit requires some typing in the terminal. \nenter heart \nthen \nresetbundle “animus home homekit” \nthen i had to forget bridge in homekit and connect again to get everything working", "name": "", "is_accepted": true } ]

[ { "text": "i can get the battery from listening to the event sent by the door through the api, which is actually a preferred solution.\n\nsince idc about animus interface, as i have my own, this thread is resolved for me.\n\njust note that it doesn’t work in any way on the animus online interface nor on the animus…", "name": "", "is_accepted": true } ]

[ { "text": "thanks for your patience! :slightly\\_smiling\\_face: \nfinally, i gave up and rebooted the heart, now it works again.", "name": "", "is_accepted": true } ]

[ { "text": "hi, \nthere is an announcement here. everything should be back to normal.", "name": "", "is_accepted": true } ]

[ { "text": "that is what happened to me i believe. another restart fixed my issue, ie reloaded the z-wave package.", "name": "", "is_accepted": true } ]

[ { "text": "this shows that the node 1 and node 71 (endpoint2) will receive the messages from group 4. however does the oomi bulb have multiple endpoints? have you tried the command \n> associations 34 add 4 71", "name": "", "is_accepted": true } ]

[ { "text": "when the “fibaro plug” then the “virtual button”. i don’t really know the w, i’m using 7w. i think at standby it can be like 3-4w \n [[image]](https://d2lz8p2gj1hhp1.cloudfront.net/original/1x/243eb4f4f42271d77d4259ca2d6a6a4cd4ccb2ac.png \"image.png\")", "name": "", "is_accepted": true } ]

[ { "text": "hi [@mrdgriffon](/u/mrdgriffon), \nthe devices are loaded synchronously meaning each device initialization will block the other until it’s finished or timed out. i’m suspecting you have a device that can’t be reached on wifi that blocks for a while. after the timeout - every other remaining device is loaded. \ndevice …", "name": "", "is_accepted": true } ]

[ { "text": "like [@olsen](/u/olsen) mentions, you need to wake up the device first. battery-driven devices needs this if you are changing the parameters. \ne.g. push the button on the sensor once, then go into the settings, change the parameters and hit save. they should not disappear now.", "name": "", "is_accepted": true } ]

[ { "text": "hm, since events are generated in the log output of the web-terminal when clicking the button i assume that the device is asked for an update.", "name": "", "is_accepted": true } ]

[ { "text": "problem is now fixed. everything should be back to normal.", "name": "", "is_accepted": true } ]

[ { "text": "got a nice answer from support regarding this. most likely, it has to do with philips hue bridge having a hard time handling several instructions in a short amount of time. short hand solution is to add wait’s between the actions. a fix for this will be included in the coming release. :+1:", "name": "", "is_accepted": true } ]

[ { "text": "i found the code in the animus app!", "name": "", "is_accepted": true } ]

[ { "text": "got it to work now, instead of trying to add it from a distance of 30 cm i moved the sensor more or less 0 cm from the controller while pairing and now it works.", "name": "", "is_accepted": true } ]

[ { "text": "hi [@viklundjonas](/u/viklundjonas)\n\nthis is an ios bug. it has been fixed in the current (v2.1.0) beta release. if you have a desktop/laptop browser you can set it up through that browser.", "name": "", "is_accepted": true } ]

[ { "text": "problem is now fixed. everything should be back to normal.", "name": "", "is_accepted": true } ]

[ { "text": "looks like the generic google error that could mean everything. :face\\_with\\_raised\\_eyebrow:\n\nin my case, it was mostly related to network- especially wifi-issues, so there are tons of things you could try, like\n\ntemporarily deactivating 5ghz\n\nchecking your ipv6-settings\n\ntemporarily disabling any wifi…", "name": "", "is_accepted": true } ]

[ { "text": "many thanks [@olsen](/u/olsen) for your efforts to help me. today animus support answer me. they told me to do a main reset (pull the plug) and wait 5 minutes after power on. i did so and there were a node with no function, i did rebuild that node and now it is ok.", "name": "", "is_accepted": true } ]

[ { "text": "if i understand you correctly, it should be doable like this:\n\ncreate a virtual device named “timer on”.\n\ncreate a new automation and at when: “timer on” is on, and tick duration 2h, and tick trigger only on change (under advanced).\n\nat then do what you need when timer expires after two hours.\n\nso f…", "name": "", "is_accepted": true } ]

[ { "text": "ok, if you go into the “ljus och temp” entry, what have you set under the “advanced” area? if you want to use this as a one-time automation in the evening, perhaps the “trigger only on change” could be an option for you (with an optional reset value), or in case you have “false positives” maybe yo…", "name": "", "is_accepted": true } ]

[ { "text": "i had the same problem a while ago. the problem for me was a device named with just numbers, which obviously google sees as an issue. after renamning that device (adding a letter before the numbers) the connection worked.", "name": "", "is_accepted": true } ]

[ { "text": "had to click the “forget password” link, entered my old password again and it worked.", "name": "", "is_accepted": true } ]

[ { "text": "since you can see it on vlc you should have the correct port and other info. how did you input the info in the guide? don’t write the whole url. \nhere is an example screenshot i just made: \n [[add\\_camera\\_manually]](https://d2lz8p2gj1hhp1.cloudfront.net/original/1x/b16860c173e575c4ac2b7a5ad0ecc8b4be93ed10.png \"add_camera_manually.png\")\nand not until after you click “next” you will be asked to input user and password.", "name": "", "is_accepted": true } ]

[ { "text": "hi there, \na little more information would be helpful: \n\ndid you pair both devices with the heart?\nwhat is the “when”-condition in your automation?\nas far as i found out, the lmlt-711 is a push button, so which device is supposed to ring the bell when you open the door?", "name": "", "is_accepted": true } ]

[ { "text": "meanwhile the heart is running for the third day with z-wave debugging activated, so never mind.", "name": "", "is_accepted": true } ]

[ { "text": "nu funkar det igen. så något har blivit åtgärdat.", "name": "", "is_accepted": true } ]

[ { "text": "hi there,\n\nseems like you forgot to set the parameter size?\n\n[fib\\_ms]\n\nand don’t forget to wake up the sensor before saving.", "name": "", "is_accepted": true } ]

[ { "text": "why did you change from telldus to animus? just curious.", "name": "", "is_accepted": true } ]

[ { "text": "[image] olsen:\n\nassociation 4 {\n\nmax node count: 5\n\nnodes: 1 71.2\n\n}\n\nthis shows that the node 1 and node 71 (endpoint2) will receive the messages from group 4. however does the oomi bulb have multiple endpoints? have you tried the command\n\n> associations 34 add 4 71", "name": "", "is_accepted": true } ]

[ { "text": "one more mystery solved, as the presence problem occured again today, looking at the members i found that the heart, for whatever reason, has suddenly found my phone with it’s ipv6 adress again. \nlooking behind the scenes, it has been shown that the heart seems to use arping to detect presence, whic…", "name": "", "is_accepted": true } ]

[ { "text": "hi, \nthat sounds quite strange. may i ask how long you have the power cord out while trying the hard restart? \ni all else fails, i’d try a factory reset, but then you’ll lose all your configuration, and have to start from scratch again. \nshould that be neccessary, here is a link to the instructions…", "name": "", "is_accepted": true } ]

[ { "text": "i would initially suspect the trådfri bulbs firmaware… i have a few trådfri rgb e27 bulbs myself, and they work just fine, no workarounds needed. have you tried to update the firmware of the bulbs? you’ll need a trådfri gw or ask in your local ikea store for help with it (i’ve heard they should help…", "name": "", "is_accepted": true } ]

[ { "text": "maybe that why its less secured. you have to trust that its your device you are including. like one time authorization code. so only accept the code. \nfound this: \ns2 includes ‘unauthenticated s2’ and ‘authenticated s2’, where the authenticated devices has a unique authentication code on them.", "name": "", "is_accepted": true } ]

[ { "text": "polling-interval means that the heart asks a device for it’s status after a certain time, in this case every 600s, right. \ni completely disabled polling for all devices, to my opinion the only thing it does is jamming your network. \ni think it makes no sense to… \n\npoll battery powered devices since…", "name": "", "is_accepted": true } ]

[ { "text": "hi, \nthanks jesper, i finally solved this issue with a fibaro dimmer hard reset + rebuilding z-wave. this is something i need to do for random fibaro devices every time i stop the electricity. \nbest, \nnicklas", "name": "", "is_accepted": true } ]

[ { "text": "after a lot of diggin, i found the problem. \nmy profile had added a “second” phone on my profile for some reason[image] \nsince it was the “incorrect” one that was selected, it didn’t received any push notifications. however, the “burglar events” seems to trigger on all devices, and that’s why i reci…", "name": "", "is_accepted": true } ]

[ { "text": "ok, now it seems to work!\n\nnice", "name": "", "is_accepted": true } ]

[ { "text": "case solved… it was not the dimmer… it was the load that was not able to work with the dimmer.", "name": "", "is_accepted": true } ]

[ { "text": "today i’m not receiving the fault message. so i hope it was temporary.", "name": "", "is_accepted": true } ]

[ { "text": "ok, found solution:\n \n\n\n - restarted from scratch (*.img file -> usd),\n \n\n\n - connected \"real hdmi\" (some overscan) tv, keyboard,\n \n\n\n - gone trough initial config (root passwd, \"normal\" user),\n \n\n\n - configured wifi (had no wired eth at my neighbour) using nmtui,\n \n\n\n - now ssh works in both directions.\n \n\n\n  \n \n\n\n so conclusion is: the problem was / is (still no video on vga) with cheap hdmi->vga converter.\n \n", "name": "", "is_accepted": true }, { "text": "your issue report is not a valid bug report per the armbian bug reporting instructions (https://www.armbian.com/bugs).  with limited resources the armbian project is only able to spend time on issues where all the requested information has been provided and for only the boards/images/software that are supported.  your report is invalid for one or more of the following reasons (non-exhaustive list):\n \n\n\n  \n \n\n\n \n it is for an unsupported board or image (csc/eos/wip/edge)\n \n \n it is for software that is not supported (such as userspace modules installed on top of the core operating system)\n \n \n it has been logged in the wrong forum (for example requests for help that are not actual bug reports)\n \n \n it lacks requested data (armbianmonitor output)\n \n \n it could have been easily solved by a quick search and/or reading documentation\n \n\n\n\n  \n \n\n\n please review what you have submitted and the bug logging instructions (https://www.armbian.com/bugs) and either add the required information or open a new topic in the correct forum (such as common issues / peer to peer technical support or general chit chat)\n \n", "name": "", "is_accepted": false }, { "text": "can't find what i did wrong with this report, please clarify.\n \n\n\n i have no communication with the (new!) board, except green led flashing and red led lit. only signal of activity is gathering an ip from dhcp server.\n \n\n\n i am stuck on what to test next.\n \n", "name": "", "is_accepted": false }, { "text": "depending on how to interpret things:\n \n\n\n - board does not start -> topic in wrong place and no logs via uart provided\n \n\n\n - board does start (indicated by mentioned dhcp lease aquired) connecting via ssh should be possible. if not line above.\n \n\n\n  \n \n\n\n btw. rk is 1,5mbaud\n \n", "name": "", "is_accepted": false }, { "text": "thanks for claryfying, tomorrow will try \"live\" hdmi display, if not ok will connect serial (thx for speed indication) :)\n \n", "name": "", "is_accepted": false }, { "text": "ok, got it connected to \"real hdmi\", see attached picture.\n \n\n\n looks it is starting, nmap shows ssh port open (the only), but system refuses ssh connection (as no root password has been set?)\n \n\n\nssh [email protected]\nconnection reset by 192.168.1.153 port 22\n\n\n \n \n\n\n  \n \n\n\n what should i do next? connect to console or there is another (easier) way?\n \n\n\n  \n \n\n\n red led is solid, green flashes fast 2 times, then some space, and again.\n \n", "name": "", "is_accepted": false }, { "text": "put a keyboard to it and try login with the shell you see on hdmi. i think the login prompt is barely visible at the bottom due to overscan. try anyway\n \n", "name": "", "is_accepted": false }, { "text": "will do later on (as hdmi display is at my neighbour).\n \n\n\n what (if?) is the default root password? blank?\n \n", "name": "", "is_accepted": false }, { "text": "initial root password is always 1234. you are forced to change after first login.\n \n", "name": "", "is_accepted": false }, { "text": "logged as root using hdmi tv / usb keyboard, changed password, but stuck at new user creation stage, as there are too restrictive rules for password (used crtl-c). then useradd / passwd.\n \n\n\n  \n \n\n\n now i still get \"connection reset by xx.xx.xx.xx port 22.\n \n\n\n  \n \n\n\n 1). how to login on device by net?,\n \n\n\n 2). how to resume initial armbian setup process once logged?\n \n\n\n on my other pis i had no problem with this initial setup and got to gui w/o problem.\n \n", "name": "", "is_accepted": false } ]

[ { "text": "doing this should probably trigger it.  https://github.com/armbian/build/blob/master/lib/distributions.sh#l157 \n \n also take a look at  \n \n https://github.com/armbian/build/blob/master/lib/distributions.sh#l372-l379 \n \n  \n \n\n\n\n\n \n might be related to https://github.com/armbian/build/blob/master/packages/bsp/common/lib/systemd/system/armbian-firstrun-config.service#l9\n \n\n\n  \n \n\n\n\n\n \n probably best to keep conversation here for now.  mostly we use issues in github for major bugs / problems\n \n", "name": "", "is_accepted": true }, { "text": "after a couple of days, this seems to be a stumper.\n \n\n\n i'd wish that this, an essential piece of armbian configuration and operation, were documented as well as the image building process!\n \n", "name": "", "is_accepted": false }, { "text": "you can help make this wish become reality. everybody can contribute to make the documentation better: https://github.com/armbian/documentation\n \n\n\n the lack of (human) resources is a big issue for the armbian project so community contributions are more than welcome. \n \n", "name": "", "is_accepted": false }, { "text": "i agree. i'm very much in favor of making contributions, and not shy about being detailed. when the linux world revolved around howtos, not reddit subs and siloed vendor forums, i was particularly active. \n \n here's a case where i'd gladly supply documentation, were i not faced with ambiguous outcomes, and a lack of authoritative information to begin! \n thanks!\n \n\n\n — jeremiah\n \n", "name": "", "is_accepted": false }, { "text": "can you just give me some quick bullet points on what you're waiting to achieve... i may have an answer.\n \n", "name": "", "is_accepted": false }, { "text": "thanks! very kind.\n \n\n\n \n i am looking to re-set the firstboot state for a derived image, after customization and out-of-band additions.\n \n \n my efforts extend to re-enabling systemd unit files for armbian-firstrun, armbian-firstrun-config, and armbian-resize-filesystem.\n \n \n results: new ssh keys are generated, and new uuid appended to /etc/armbian-image-release - no other config tasks are run (update root pw, create normal user, choose logon environment, etc)\n \n\n\n\n observation: /usr/lib/systemd/system/armbian-firstrun-config is deleted after being enabled, on next boot.\n \n\n\n \n is this expected behavior?\n \n \n is it an error in how symlinks under /etc/systemd are handled?\n \n \n would an issue on the git repository be well received? \n \n\n\n\n i'd like the unit disabled, and maybe a re-settable flag written to the image, preventing accidental firstrun.\n \n\n\n  \n \n\n\n my main question is still why this isn't working as expected. does behavior change, if /etc/armbian-image-release already exists? there's something i'm missing!\n \n\n\n  \n \n\n\n when i understand this fully, i'll be in a better position to offer contributions.\n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "yeah first run has a few distributed touchpoint.. kind of needs to be consolidated and more intuitive to manage as you describe.. i know many have interest in being able to bundle in cloud-init to the image.. and making the first-riun and first-login components a little more polished would help with that.\n \n", "name": "", "is_accepted": false }, { "text": "really thanks for this. it gives me a lot more to go on. \n i'll do more work in the next day or so, and be back with some updates - hopefully with some guidance to offer others, if successful!\n \n\n\n  \n \n\n\n the \"\"${sdcard}\"/root/.not\\_logged\\_in\\_yet\" is a great hint!\n \n\n\n it's the opposite of touching a flag in the file system, so of course finding it in a configured system is impossible! i'd have taken a long time, before i got to it in the script sources.\n \n\n\n  \n \n\n\n — jeremiah\n \n", "name": "", "is_accepted": false }, { "text": "as a possible out-of-the-box solution. have you tried directly mounting the original image, and just rsync'ing that to your partitions?\n \n\n\n  \n \n\n\n# mkdir /dev/shm/{original,current}\n\n# kpartx -av armbian\\_21.02.1\\_nanopim4v2\\_focal\\_current\\_5.10.12\\_desktop.img\nadd map loop9p1 (253:0): 0 7258112 linear 7:9 32768\n\n# mount /dev/mapper/loop9p1 /dev/shm/original\n\n# mount /dev/mmcblk0p1 /dev/shm/current\n\n# rsync -av --delete /dev/shm/{original,current}/\n\n# umount /dev/shm/original\n# umount /dev/shm/current\n# sync\n\n\n  \n \n\n\n i didn't try it (for obvious reasons), but that should reset pretty much all logs, passwords, user files, ssh keys, etc ..\n \n\n\n  \n \n\n\n the verbose option should list everything that it's doing.\n \n\n\n  \n \n\n\n your mileage may vary. you might need to adjust if your build has two partitions. it may delete important things ...\n \n", "name": "", "is_accepted": false }, { "text": "that's a good idea. i'd have to be more selective - as there are changes to my images i'd need preserved, such as apt changes, dselect selections, dpkg options, for a start. i also do the unthinkable, and change contents of /etc/armbian-release and /etc/armbian-image-release, because the platforms aren't yet build targets, and i am playing doctor frankenstein with the parts. lol\n \n\n\n  \n \n\n\n thanks, \n — jeremiah\n \n", "name": "", "is_accepted": false }, { "text": "make your changes to the image before you call rsync? /dev/shm/original is mounted rw unless you tell it otherwise.\n \n\n\n  \n \n\n\n\n\n  \n \n\n\n you monster\n \n", "name": "", "is_accepted": false }, { "text": "this is it!\n \n\n\n touching /root/.not\\_logged\\_in\\_yet gets the desired, correctly reset behavior for the armbian-firstrun-config systemd unit. i knew it was some small, critical configuration i'd been missing.\n \n\n\n i now have what's needed for a community, unsupported armbian khadas vim3 image that's functionally equivalent to odroid n2+, and have plans for similar with 32-bit apt/userspace, which enables access to an armhf ecosystem of commercial audio software, and snap images.\n \n\n\n  \n \n\n\n this also means that the vim3 twister os image that i have some good interest in from users, can be updated to use this firstrun logic - with an addition that will hardlink the new user to the \"pi\" account on which twister os scripts and configurations depend.\n \n\n\n  \n \n\n\n in the background are plans for ready-to-run armbian vim images with budgie desktop and elementary os, pre-built. being unsupported, some of these may advance from focal to groovy or hirsute. \n  \n \n\n\n thanks!\n \n", "name": "", "is_accepted": false }, { "text": "well, at least for function, and not capriciously!\n \n\n\n — jeremiah\n \n", "name": "", "is_accepted": false }, { "text": "btw have you played with https://github.com/armbian/build.  we have budgie i there, and would gladly take help there as well \n \n ..but you're doing 32bit userspace?   \n \n", "name": "", "is_accepted": false }, { "text": "budgie is on my list - as i get kinks worked out with clean, vanilla armbian. i am doing hybrid arm64 kernels and armhf userspace because of audio-plugins. this worked well for me in pinebook pro, etc. \n \n i'd do more with pure arm64, if i can solve some gaps with carla, and when there's a 64-bit linux widevine. that's when google decides they need a 64-bit chromebook, i guess.\n \n\n\n  \n \n\n\n — jeremiah\n \n", "name": "", "is_accepted": false }, { "text": "ha i love the idea of mounting to /dev/shm .. clever.. i always just made a dummy folder from /mnt\n \n", "name": "", "is_accepted": false }, { "text": "fyi keep an eye on this pr from @rpardini  provides more customization opportunities. (i know this doesn't address the 32bit use space stuff, but seemed relevant to share  ) \n \n https://github.com/armbian/build/pull/2799\n \n", "name": "", "is_accepted": false }, { "text": "reason i do that is that i've used this technique to backup (or obliterate) full os images. if i rsync from an image that doesn't have that new directory, it'll wipe out the mount.\n \n\n\n  \n \n\n\n if i have the mount in a tmpfs at a known location, that shouldn't happen.\n \n", "name": "", "is_accepted": false }, { "text": "hey @jeremiah cornelius \n \n\n\n i've been working on something similar it seems, thanks to @lanefu for making the connection.\n \n\n\n although the path i took was directly modifying the armbian build scripts, instead of modifying a live image and then re-packing it.\n \n\n\n  \n \n\n\n my fork of armbian is quite complex, but i'm slowly splitting and reorganising things (and sometimes writing a metaprogramming bash framework in the process ) \n \n\n\n a few points that may be of interest to you:\n \n\n\n  \n \n\n\n - onboarding replaced by cloud-init, instead of any interactive onboarding, i configure cloud-init to read some yaml files from /boot.\n \n\n\n   /boot/network-config can configure all aspects of networking (including wifi), /boot/meta-data is just that, and /boot/user-data can do almost anything, create users, passwords, import ssh keys, install packages, run scripts, resize rootfs, create ssh host keys, etc.\n \n\n\n   cloud-init is of course focused on cloud images, but actually can be used on any environment, if you can stomach its yaml and hammer on its config.\n \n\n\n   with cloud-init comes netplan.io (in place of networkmanager) and some other stuff that may not be appropriate for your use-case so take with a grain of salt.\n \n\n\n   also my implementation is not bullet-proof yet, but it aims to work just like the ubuntu raspberrypi 4 \"server\" image (also has cloud-init out of the box).\n \n\n\n   most of it is done in https://github.com/rpardini/armbian-build/blob/rpardini-fragments/userpatches/fragments/cloud-init/cloud-init.sh (including the .not\\_logged\\_in\\_yet thing)\n \n\n\n   some other related stuff in https://github.com/rpardini/armbian-build/blob/rpardini-fragments/userpatches/fragments/more\\_like\\_ubuntu\\_cloud.sh (which disables a bunch of stuff in the bsp,  during bsp-generation, so that reinstalls/upgrades of the bsp package do not ruin everything).\n \n\n\n  \n \n\n\n - a trick i call rootfs-in-rootfs, during the image build process, i capture an e2image ext4 dump of the produced ext4 rootfs and then include it in the rootfs.  a bit like having a directory full of files, creating a .zip of it, then including that .zip file inside itself  but without the compression.\n \n\n\n   then boot the sd card (which includes the rootfs dump inside) and run \"e2image -racp /root/rootfs.ext4.e2img /dev/sda2\" for example.\n \n\n\n   the nice thing is that e2image (part of e2fsprogs) can do a \"smart\" copy (-c), knowing that reading is cheaper than writing, it can read both the source and destination and only write the changed blocks to the target. this allows for a very, very fast version of \"nand\\_sata\\_install\",  especially on the 2nd+ \"flash\".\n \n\n\n   more speed comes from reading/writing some hundred-thousand whole blocks instead of possibly millions of files that rsync would need to inspect individually.\n \n\n\n   the relevant code fragment is https://github.com/rpardini/armbian-build/blob/rpardini-fragments/userpatches/fragments/rootfs\\_e2img\\_inside\\_rootfs.sh\n \n\n\n  \n \n\n\n hopefully these will be of some help,\n \n\n\n ricardo\n \n\n\n  \n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "oh, man. thanks. this information is a goldmine! \n i won't be able to dig in very deeply until the weekend, but i am champing at the bit, a bit. ;-)\n \n", "name": "", "is_accepted": false } ]

[ { "text": "try this. \n https://forum.armbian.com/topic/15981-box86-on-the-rk3399-with-armbian-reforged/ \n doesn't work with everything, but you might be able to run your program if it ain't too fancy. \n  \n \n", "name": "", "is_accepted": true }, { "text": "moved to common issues / peer to peer technical support\n \n", "name": "", "is_accepted": false }, { "text": "il try it thank you\n \n\n\n  \n \n\n\n bydeway does the build with download link:\n \n\n\n https://drive.google.com/file/d/1gqtgwz2ph2tx9qs\\_bcdu9zn7w4edfcvf/view?fbclid=iwar0srsc8m\\_1\\_qm825n4bd7bqjlmo30qtpfo73qqqga-tc\\_lruc2bvfcgzku\n \n\n\n come with preinstalled accelerate gpu drivers (hardware decoding)for browsers/media players?\n \n", "name": "", "is_accepted": false }, { "text": "gpu drivers yes, not vpu drivers for video.\n \n", "name": "", "is_accepted": false }, { "text": "sounds like a good reason to revisit that code and make it work across platforms.\n \n", "name": "", "is_accepted": false } ]

[ { "text": "for anybody reading this: most of the debugging for your setup routines can be done just by looking inside generated image file.\n \n\n\n of course i have to burn the sd-card and run on actual device at the end...\n \n\n\n  \n \n", "name": "", "is_accepted": true }, { "text": "if you will be able to run your app on debian / ubuntu it will also run on armbian. virtualbox / kvm with standard install should do.\n \n\n\n  \n \n\n\n if you are talking about testing hardware features, then, we do it this way:\n \n\n\n https://github.com/armbian/autotests\n \n\n\n  \n \n\n\n also we are developing a hardware to make a complete test automatically:\n \n\n\n\n first version of the board: \n \n \n", "name": "", "is_accepted": false }, { "text": "thank you igor, i already had examined them briefly. very nice work indeed... but not applicable for my case (i think)... i'm not bulk-producing...\n \n\n\n  \n \n\n\n what i'm trying to do (for now) is simply adding some drivers, adding some scripting to customize-image.sh, such as additions to motd, several users/groups/rights management, pre-installing some additional software through apt-get, adding some custom scripts under /usr/local/bin etc.\n \n\n\n  \n \n\n\n testing this would require installation of the customized armbian and checking the logs etc.\n \n\n\n  \n \n\n\n is there a working armhf emulator for x32-64? that would ease the burden alot... i found qemu just now, did you try it?\n \n\n\n my development environment is on win 10 and i don't mind speed loss caused by emulation.\n \n\n\n  \n \n\n\n or i'm really missing the point :/\n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "yes its is. but. the only image that i manage to boot - didn't really put much efforts to see if any else - was cubieboard 1.  but that was long time ago ...\n \n", "name": "", "is_accepted": false }, { "text": "yes, they only have cubieboard and rpi 2 included in base.  i wonder if people have created others.\n \n\n\n  \n \n\n\n i can guess that it will fail at kernel level if a board is not modeled.\n \n\n\n  \n \n\n\n i'll stick with writing better code and testing all in one for now...\n \n\n\n  \n \n", "name": "", "is_accepted": false } ]

[ { "text": "here are the logs and the meeting summary.\n \n\n\n https://werner.armbian.de/\\_meetbot/\n \n", "name": "", "is_accepted": true }, { "text": "everything works without this patch.\n \n\n\n  \n \n\n\n https://github.com/armbian/build/blob/master/patch/u-boot/u-boot-rockchip64-mainline/general-support-recovery-button.patch\n \n", "name": "", "is_accepted": false }, { "text": "can you post the log of the boot process captured with serial?\n \n\n\n can you also try if booting with \"boot\" button pressed is successful? - to rule out any incompatibilities between the u-boot in emmc and sd\n \n", "name": "", "is_accepted": false }, { "text": "specify which button you are writing about.\n \n", "name": "", "is_accepted": false }, { "text": "sori, it seems the reason is in a different patch. i had to remove all patches (except changing the order of sd \\ emmc). and now you need to check all the patches to find which one breaks the download from the sd card.\n \n", "name": "", "is_accepted": false }, { "text": "strange behavior. if you use the latest night image t4 from the site (from the download page from 17 10 2020), the sd card does not work. if i start building an image for t4 from the latest master, and then take the u-boot files from the received package and manually write them to the sd card, everything starts working.\n \n", "name": "", "is_accepted": false }, { "text": "replaced the sd cards and all images from the site worked. for some reason, only sandisk works, other cards  give do not predictable behavior. on my builds with u-boot-20.10, all cards work without problems.\n \n", "name": "", "is_accepted": false }, { "text": "is anybody interested in doing a kind of hackathon in irc on a weekend for testing and bug fixes?  \n \n", "name": "", "is_accepted": false }, { "text": "i assume the upcoming 7th one? \n \n are we able to sqeeze upgrade to 5.9.y ... 5.8.y just got eol-ed.\n \n", "name": "", "is_accepted": false }, { "text": "i could imagine this weekends saturday night (saturday night in utc so afternoon for americans). would try to get 5.9 for mvebu. \n \n\n\n  \n \n\n\n not sure if it is worth it to try squeezing all boards in. depends on ppl. participating w/ testing.\n \n", "name": "", "is_accepted": false }, { "text": "all boards received test - build - from trunk - for testing. this is the last bug hunting release candidate. we will fix what we can and write down what we have found and what we were not been able to fix.\n \n", "name": "", "is_accepted": false }, { "text": "bugs yet do be fixed or documented (will be added later):\n \n\n\n \n machine / reporter \n \n pinebook - no screen @martinayotte @igor\n \n\n\n opi3 - networking issues  @lanefu\n \n\n\n orangepi r1 freezing under certain condition\n \n\n\n odroid c2 - sd card corruption happen pretty quickly\n \n\n\n\n\n \n nanopi neo3 @igor\n \n\n\n odroid n2 hangs on reboot sometimes\n \n\n\n orangepi win sometimes powers off on stress @igor\n \n\n\n ubuntu bionic allwinner h6 doesn't boot @igor\n \n\n\n mvebu and mvebu family will stay at 5.8.y @heisath and will be moved up after.\n \n\n\n  \n \n\n\n other boards are surviving stressing https://beta.armbian.com/autotest.html  \n \n there is a general idea to make this release with kernel 5.8.y where we have troubles with the kernel. otherwise we will not catch this train.\n \n\n\n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "during my latest tests for pinebook-a64, if i remember correctly, i've took from latest working build 5.7.6 the dtb and i tried to boot in either 5.8.0 or 5.9.1 images, screen is working during first phase of the boot, but then it switch to blank screen, either if it is a desktop or plain text image. so, it is not a dtb issue, but probably a kernel issue ... i tried to compare \".config\" between 5.7.6 and other builds, but i didn't figure out what is missing, it maybe also be in the kernel code itself too...\n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "btw, i've found another glitch :\n \n\n\n  \n \n\n\n i've built a 5.9.8 dev pinebook-pro desktop image and i didn't have wifi working. i've figured out that no firmware were present in the image, i've copied them from previous 5.8.1 image...\n \n", "name": "", "is_accepted": false }, { "text": "yeah. firmware was broken .... but it should be fixed now.\n \n", "name": "", "is_accepted": false }, { "text": "i tried the latest night image of focal 5.9.8 from november 13, running from an sd card. in startup mode with sd \\ emmc, i didn't find any problems with rebooting (i rebooted many times).\n \n", "name": "", "is_accepted": false }, { "text": "i am getting kernel panic on my rockpi-4b legacy, both with the images i build and also when i switch to nightly from a 20.8 image. am i the only one?\n \n\n\n  \n \n\n\n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "okay, kernel panic also happens with 20.08.14. but board boots perfectly with 20.08.1\n \n", "name": "", "is_accepted": false }, { "text": "what revision of the board you have?\n \n\n\n is it 1.4 with spi or 1.3 without it?\n \n", "name": "", "is_accepted": false }, { "text": "rev 1.3\n \n", "name": "", "is_accepted": false }, { "text": "i will build and share an image with a possible fix for you to verify.\n \n", "name": "", "is_accepted": false }, { "text": "if you don't mind, buster would be best for the image, so i can test also the multimedia stuff on it.\n \n", "name": "", "is_accepted": false }, { "text": "that's my primary choice too \n \n\n\n current minimal was the fastest to build (to assess if the panic on boot is gone): https://users.armbian.com/piter75/armbian\\_20.11.0-trunk\\_rockpi-4b\\_buster\\_current\\_5.9.8\\_minimal.img.xz\n \n\n\n  \n \n\n\n legacy desktop is being built right now.\n \n", "name": "", "is_accepted": false }, { "text": "perfect, thank you very much. (edit: i mean, i tested it and works)\n \n\n\n  \n \n\n\n let me know when you push the fix, so i can tinker with the kernel. i discovered that vpu was failing, and it will probably need some patch.\n \n", "name": "", "is_accepted": false }, { "text": "i took a shortcut and enabled spi by default for rock pi 4.\n \n\n\n i verified it with spi clk shorted on v1.4 but obviously it was not enough \n \n\n\n the fix is in master.\n \n", "name": "", "is_accepted": false }, { "text": "do we have solution, patch or workaround for any of? probably pushing out new build by the next weekend? reordered by priority.\n \n", "name": "", "is_accepted": false }, { "text": "in the message log from u-boot-2015. i am testing c2 with the latest nightly builds (u-boot-2020.04) and have not found the specified failures yet.\n \n\n\n  \n \n\n\n if your sample has been used extensively, is it possible that the card reader or sd card may have worn out ?\n \n", "name": "", "is_accepted": false }, { "text": "thank you for testing. i can easily reproduce by upgrading stable build to nightly. probably the same if you just reinstall kernels and u-boot.\n \n\n\n  \n \n\n\n i will re-do testing again to make sure. \n  \n \n", "name": "", "is_accepted": false }, { "text": "write down what order of steps you need to check, and i'll try to reproduce it myself. by the way, with intensive use of the system, sd cards get very hot and when they cool down (if the card reader is worn out), failures may occur (contacts are broken not predictably).\n \n", "name": "", "is_accepted": false }, { "text": "its easy. download latest stable image for c2. change apt.armbian.com to beta.armbian.com /etc/apt/sources.list.d/armbian.list ... apt update , apt upgrade, reboot ... this fails for me.\n \n", "name": "", "is_accepted": false }, { "text": "when updating, the uinitrd is not generated (it is completely absent). there may be an error in the kernel package.\n \n\n\n  \n \n\n\n the sd card is fine, i used desktop and updating a large number of packages did not cause problems. which kernel package is currently used for the upgrade ?\n \n", "name": "", "is_accepted": false } ]

[ { "text": "it seems that both problems are solved as of the 21.05.1 update.\n \n\n\n  \n \n\n\n big thanks to the devlopers, and also to all who helped me.\n \n", "name": "", "is_accepted": true }, { "text": "i think stack trace and the other error is not related. stack trace probably stems from some display error, simple framebuffer thing. it may help to share dts.\n \n\n\n  \n \n\n\n i know this is not a bright idea but if you're able to compile your kernel, you can try disabling config\\_module\\_sig and/or alike for the sake of suppressing the error.\n \n", "name": "", "is_accepted": false }, { "text": "thanks for the reply.\n \n\n\n  \n \n\n\n now i see what you're talking about - it does seem like two seperate issues.\n \n\n\n  \n \n\n\n so perhaps i should focus on the kmod signatures:\n \n\n\n i don't think i want to circumvent the problem - i would prefer that the modules pass the verification.\n \n\n\n  \n \n\n\n to me it seems that the kernel is misconfigured such that it does not have a certificate to match the autogenerated key used for kmod signing.\n \n\n\n is there a way for me to check this on-board?\n \n", "name": "", "is_accepted": false } ]

[ { "text": "check you have the same netmask on router, bridge and dhcp config.\n \n\n\n  \n \n\n\n check router arp tables and messages to see if it receive requests.\n \n\n\n  \n \n\n\n check if interfaces are really added to the bridge with brctl and that some nasty software has not added addresses to wlan0 and eth0 with ifconfig.\n \n", "name": "", "is_accepted": true }, { "text": "stupid me bridged eth0 instead of eth0.vlan\n \n\n\n sorry guys.\n \n", "name": "", "is_accepted": false }, { "text": "stupid us !\n \n\n\n  \n \n\n\n for me configuring is like programing. we need to check live parameters to debug configuration or design mistakes.\n \n\n\n  \n \n\n\n i wish i would know how to debug efficiently some declarative languages ...\n \n", "name": "", "is_accepted": false } ]

[ { "text": "@i5js you can download these packages and install them with apt/dpkg: https://users.armbian.com/piter75/nanopim4v2-stability-fix/\n \n\n\n you need both of them for the fix.\n \n\n\n  \n \n\n\n when they are correctly installed and the board is rebooted you should see this message in your dmesg:\n \n\n\npiter@nanopim4v2-4:~$ dmesg | grep rk808-regulator.*buck\n[ 2.840331] rk808-regulator rk808-regulator: max buck steps per change: 4\n\n\n the last \"4\" means you have the fix. no message or \"8\" means you don't have a fix.\n \n", "name": "", "is_accepted": true }, { "text": "glad to hear that.\n \n\n\n  \n \n\n\n btw the fix is now included in armbian v21.02.3 images \n \n", "name": "", "is_accepted": false }, { "text": "up time:       3 days 4:01\n \n\n\n new record... \n \n", "name": "", "is_accepted": false }, { "text": "@piter75 i've had no issues with my m4v2 since setting the governor to \"userspace\" and max and min speeds set to \"1416000\" (and by no issues, i mean no crashes at all and i have an uptime of 20 days now), but i wonder if your fix is for the issues we've seen with the governor set to \"ondemand\"?\n \n", "name": "", "is_accepted": false }, { "text": "with that setting you are actually disabling the dvfs after the short period of time during boot - before cpufrequtils kicks in.\n \n\n\n my experience is that you could also set it to min/max 2ghz and it would be just as good.\n \n\n\n  \n \n\n\n\n\n yes, this mod/tweak/hack ;-) fixes the behaviour of my boards with ondemand governor.\n \n\n\n  \n \n\n\n it seems that the instability of little core's voltage during the voltage change was the issue.\n \n\n\n rockchip has already limited max change per single step for this regulator to 100mv (because of \"overshooting\") and i did limit it further to 50mv (75mv was still unstable).\n \n\n\n it takes a bit longer to switch between frequencies now (at least 456us vs at least 196us for full swing between 408mhz and 1512mhz) but it is stable.\n \n", "name": "", "is_accepted": false } ]

[ { "text": "usual way: apt update ; apt upgrade\n \n\n\n  \n \n\n\n update was pushed up a day ago but perhaps not all mirrors are in sync yet. waiting or manual hacking https://imola.armbian.com/apt/pool/main/l/linux-5.10.4-sunxi64/\n \n", "name": "", "is_accepted": true }, { "text": "edit: ifconfig on eth shows 0 incoming packets / bytes, there are some values on tx.\n \n\n\n on wifi numbers looks as expected.\n \n\n\n leds on eth blinks like there were packet and connection.\n \n", "name": "", "is_accepted": false }, { "text": "debug console as the bug reporting guide would have told you if you would have followed it. therefore the issue report is invalid.\n \n\n\n  \n \n\n\n besides of that broken ethernet on opi3 is a known issue (search function....) and a fix has been merged. make sure you are on 5.10.y kernel.\n \n\n\n you can either wifi of the board or a different machine to grab debs and put the to a stick for example.\n \n", "name": "", "is_accepted": false }, { "text": "ok, i have 5.9.14. how to upgrade to 5.10.y? are there somewhere packages ready to install (how)?\n \n", "name": "", "is_accepted": false }, { "text": "easy way: link wifi and apt update\n \n\n\n  \n \n\n\n moderate way: get on a computer and grab image and dtb packages (headers are optional, depending if you need them) containing current in name from the link  @igor mentioned and put them to an usb stick.\n \n\n\n plug into your sbc, mount and install all of them using\n \r\ncode {\r\n font-family: consolas,\"courier new\";\r\n color: crimson;\r\n background-color: rgba(0, 0, 0, 0.2);\r\n padding: 2px;\r\n font-size: 105%;\r\n} \n sudo dpkg -i *.deb\n \n\n\n reboot, verify ethernet working again.\n \n", "name": "", "is_accepted": false }, { "text": "great thanks igor, \"manual way\" worked - downloaded  -current- debs, put it on usb stick, mounted on opi3, then issue dpkg --install *.deb.\n \n\n\n in time of installation there was a message about \"kernel configuration invalid\", but after a reset it looks to work normally.\n \n", "name": "", "is_accepted": false } ]

[ { "text": "armbian is (probably) the the only distribution that doesn't use u-boot from 2015. all others are still using stock private hardkernel boot loader ... we try to get rid of vendors dirty security hazardous code as soon as possible and problems as such is the price that we need to pay.\n \n\n\n  \n \n\n\n currently we use u-boot based on 2020.xx, but it looks like it's possible that we need the one from 2021 as this is the case with c2. some emmc needs this. mine obviously don't since it works without any intervention.\n \n\n\n\n try this image: \n https://users.armbian.com/igorp/images/armbian\\_21.02.0-trunk\\_odroidc4\\_focal\\_current\\_5.10.12.img.xz\n \n", "name": "", "is_accepted": true }, { "text": "in preparation for my internet being locked down, i made a backup image of my existing odroid c4 armbian operating system serving emby.\n \n\n\n i then use that image and wrote it to an emmc module, inserted it into another odroid c4 and i can get emby to work using localhost but networking is hosed.  any suggestions?\n \n\n\n i don't have direct access to the internet through the c4 but i do have access to the internet via a windows 10 laptop.\n \n\n\n thanks\n \n", "name": "", "is_accepted": false }, { "text": "i am also having problems booting a c4 from emmc. the armbian image i am using is the latest, \"armbian\\_20.11.10\\_odroidc4\\_focal\\_current\\_5.9.14\\_desktop\". so, what i am wondering, even it sounds like a silly question to myself, what is the correct way of installing and booting armbian to/from emmc?\n \n\n\n  \n \n\n\n i used to do it the following way, which is working on e.g. my nanopi neo plus2.\n \n\n\n \n etch the armbian image to a sd card\n \n \n boot from sd, initial setup with root pwd, user\n \n \n do an apt update and apt upgrade\n \n \n install/update the bootloader\n \n \n shutdown sbc\n \n \n insert emmc and boot\n \n \n using armbian-config/system/install, copy system to emmc using \"boot from emmc - system on emmc\"\n \n \n shutdown sbc\n \n \n remove sd card\n \n \n (try to) boot\n \n\n\n\n  \n \n\n\n and here the boot process gets stuck. the c4 tries to boot at first emmc which cannot be found, i guess. see screenshot below. then it is trying usb and then ethernet and gets stuck after some retries. what am i missing here or doing wrong? if i re-insert the sd card, the c4 boots from sd card, and the emmc can be mounted. afaik, booting should be possible w/o sd card and only emmc.\n \n\n\n  \n \n\n\n i also tried to etch the image directly to mmc with an adapter, but this is also not working/booting.(btw, is this process supported at all?)\n \n\n\n  \n \n\n\n  \n \n\n\n \n \n", "name": "", "is_accepted": false }, { "text": "fyi. running c4 from emmc http://ix.io/2nlx\n \n", "name": "", "is_accepted": false }, { "text": "@igorto be honest, i do not get your answer. is this proof that it should work to boot from emmc w/o sd card inserted.\n \n\n\n  \n \n\n\n that is what i expected, but how to install armbian to emmc. what is the correct procedure? obviously for me and @2020it is not working with the latest image or what am i doing wrong?\n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "if you burn latest image to emmc attached to the adaptor and attach it to the board, it works. \n \n\n\n  \n \n\n\n\n\n \n no idea.\n \n", "name": "", "is_accepted": false }, { "text": "thanks @igor, then i will keep trying. at least i know now what should actually work \n \n", "name": "", "is_accepted": false }, { "text": "i tried armbian\\_21.02.0-trunk.80\\_odroidc4\\_focal\\_current\\_5.10.10\\_xfce\\_desktop and it is not booting, same problem.\n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "this i tried: https://imola.armbian.com/dl/odroidc4/archive/armbian\\_20.11.10\\_odroidc4\\_focal\\_current\\_5.9.14.img.xz\n \n\n\n  \n \n\n\n burned directly to emmc and without any sd card in the slot. running low on ideas .\n \n", "name": "", "is_accepted": false }, { "text": "some updates.\n \n\n\n  \n \n\n\n i tried the same process of burning (flash image using etcher on a winsucks laptop with emmc connected using adapter) the hardkernel ubuntu mate (ubuntu-20.04-4.9-mate-odroid-c4-hc4-20201020.img.xz) image and this is booting the c4 from emmc without an sd card inserted with no problems.\n \n\n\n  \n \n\n\n so, this tells me, the way i am doing it is basically right and also my hardware, the adapter and emmc is working as it should. but no armbian image is booting. and i tried current focal mainline desktop, current focal mainline minimal, nightly/test build xfce, and legacy.\n \n\n\n  \n \n\n\n is there any way to debug this on my side to get more information about this problem?\n \n\n\n  \n \n\n\n another question, the output you can see on the pictures above from me and 2020, is this output of u-boot?\n \n", "name": "", "is_accepted": false }, { "text": "tested this morning!\n \n\n\n i tried with other os with the same methode direct on my usb emmc module writer attached to my ubuntu computer.\n \n\n\n  \n \n\n\n ubuntu-20.04-4.9-minimal-odroid-c4-hc4-20201212: ok\n \n\n\n dietpi\\_odroidc4-armv8-buster: ok\n \n\n\n coreelec-amlogic-ng.arm-9.2.5-odroid\\_c4: ok\n \n\n\n selfinstall-odroidc4-49-64bit-20210108: ok\n \n\n\n manjaro arm 20.12: ok\n \n\n\n archlinuxarm image generator: fail\n \n\n\n armbian\\_20.11.10\\_odroidc4\\_focal\\_current\\_5.9.14: fail\n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "it works, :-)\n \n", "name": "", "is_accepted": false }, { "text": "great!!! \n \n", "name": "", "is_accepted": false }, { "text": "i can confirm that it works on my c4 with the orange 32 gig emmc v0.5 as well.\n \n", "name": "", "is_accepted": false } ]

[ { "text": "ok, i come from a time when 1.3.17 was the stable kernel version and slackware was the distribution of choice. i have done my share of kernel hacking over the years, but... device trees and overlays are still magic to me. it turns out i had to seek my answer in that corner: audio-codec had to be enabled in armbian-config (which changes the overlays in armbianenv.txt).\n \n", "name": "", "is_accepted": true }, { "text": "it seems i did not look properly when looking up which versions (bullseye, buster, etc) are supported for this one. i may have ended up on the wrong page and concluded 'buster' was the safest one. now, browsing on armbian.com i see that 'focal' is the first choice and 'buster' is not even mentioned. i am going to build focal now. this will not give me a different kernel, though.\n \n", "name": "", "is_accepted": false }, { "text": "likewise  \n \n\n\n \n my distribution of choice was also slackware - iirc v1.0 / there was not much choices at that time - in my case, linux kernel has not even 1.0 \n \n\n\n  \n \n\n\n a lot has change since.\n \n\n\n  \n \n\n\n\n\n \n with totally limited resources we are trying to make this very complicated, purpose driven and diverse ecosystem as simple as possible.\n \n\n\n  \n \n\n\n\n\n \n https://docs.armbian.com/user-guide\\_faq/\n \n\n\n https://docs.armbian.com/#what-is-armbian\n \n", "name": "", "is_accepted": false }, { "text": "and i think you are doing a wonderful job. \n \n\n\n  \n \n\n\n for the purpose i am using the opi0+2, a debian-like setup is too bloated, so my rootfs comes from buildroot. however, it is my experience that the kernel and uboot i get from armbian are much more stable, so i use those. also when i want to figure out how something works (for instance, analog audio ) i immediately revert to armbian.\n \n", "name": "", "is_accepted": false } ]

[ { "text": "confirmed. it is fixed in linux nanopi-r4s 5.10.43-rockchip64 #21.05.4.\n \n", "name": "", "is_accepted": true }, { "text": "i'm having the same issue with interfaces and did some digging, it looks like systemd/udev v197 will solve this https://www.freedesktop.org/wiki/software/systemd/predictablenetworkinterfacenames/\n \n", "name": "", "is_accepted": false }, { "text": "after adding \"extraargs=net.ifnames=0\" to /boot/armbianenv.txt you should have both eth interfaces as eth0 and eth1. wan becomes eth0 and unfortunately it is associated to the lan port (lan led) instead of the wan one.\n \n\n\n  \n \n\n\n other issue that has been mentioned here: only the middle usb port works as usb 2.0, the other port doesn't work. any luck with this issue anyone?\n \n\n\n$ lsusb -t\n/: bus 02.port 1: dev 1, class=root\\_hub, driver=xhci-hcd/1p, 5000m\n/: bus 01.port 1: dev 1, class=root\\_hub, driver=xhci-hcd/1p, 480m\n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "confirmed.\n \n\n\n use armbian-config to switch to 5.10.16 kernel for now if you need this working.\n \n", "name": "", "is_accepted": false }, { "text": "it will be fixed with https://github.com/armbian/build/pull/2877\n \n", "name": "", "is_accepted": false } ]

[ { "text": "final feedback and solution \n the issue happened again, and at the same time i was seated at my desk: \n setup: \n macbook pro /w kensington desktop hub to provide displayport and ethernet \n hp desktop pc with windows 7 \n polycom desktop phone\n \n\n\n hp laserjet pro\n \n\n\n wifi access point \n \n all the above are on the same network switch\n \n\n\n  \n \n\n\n event\n \n\n\n i disconnected the kensington device from my mac (usb-c) \n i noticed something was wrong when my phone reported no network (it makes a chime when this happens) \n my windows 7 box was doing a download and then said the internet was disconnected with high cpu usage.... hmmm.... \n my phone complained about no internet (whatsapp went offline). had to use the regular mobile lte network. \n \n root cause \n when the kensington unit is disconnected, it goes into a state where it jams the upstream network switch, it appears to flood the lan with rubbish packets... the switch falls over or locks up. also other devices see (and receive) these packets. \n left to happen long enough, the orangepi will crash as i have described. my colleagues have been able to reproduce this, and we've decided to throw the kensington unit out. \n it is not a bug! the desktop phone also eventually crashes, and it takes out my ubuntu 18.04 lts file server eventually. the hp printer locks up completely and i have to power cycle it at the mains socket. \n \n so there we have it.. finally. rogue device.\n \n", "name": "", "is_accepted": true }, { "text": "did u try to fix the cpu frequency to for example on one speed? i had sam problem, andnafter this it is perfectly stabile. sent from my mi 6 using tapatalk ", "name": "", "is_accepted": false }, { "text": "for the cpu speed i keep everything as standard as possible. i haven't done that no.\n \n\n\n to put it this way, this is stock armbian with one item installed... rabbitmq. we thought we had a problem with rabbitmq and we found that buster addressed it somehow, so that's unrelated.\n \n", "name": "", "is_accepted": false }, { "text": "try what i suggested you..its 1mij of job.. sent from my mi 6 using tapatalk ", "name": "", "is_accepted": false }, { "text": "i have had a similar experience with networkmanager.\n \n\n\n the solution was to set a fixed ip.\n \n\n\n all problems solved!\n \n\n\n  \n \n\n\n some history.\n \n\n\n =============\n \n\n\n my orange pi pc was running an old armbian 5.11 (debian 8.11).\n \n\n\n had been running rock sold since installation date, with a fixed ip.\n \n\n\n a wd 500gb sata disk is attached (usb docking station: jmicron, jms579) to store files (approx. 50 gb/day). \n \n\n\n  \n \n\n\n i did a fresh install: \"armbian 20.05.2 orangepipc debian buster\" with dhcp enabled (ip reservation on the router).\n \n\n\n result: random halting of the system (runs headless in a remote location).\n \n\n\n sometimes after an hour, sometimes after a few hours, sometimes a bit longer.\n \n\n\n even checksums of the files were sometimes (1 à 2%) calculated wrong!\n \n\n\n files got sometimes corrupted (5-10%) when transferred over the wired connection.\n \n\n\n recent syslog etc were missing when the system halted.\n \n\n\n installing watchdog was not a real solution of course but would most of the time reboot the system (not always).\n \n\n\n setting a fixed ip solved all the problems.\n \n\n\n  \n \n\n\n the orange pi pc was and is running at max 1008mhz (soc runs between 480 and 1008mhz using conservative governor).\n \n\n\n i also installed a fan to keep things cooler:  max 54°c under full load (stress @ 4cpus).\n \n\n\n but this did not solve the problems.\n \n\n\n only setting a fixed ip solved al other issues.\n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "hi\n \n\n\n i have some feedback regarding this issue.\n \n\n\n  \n \n\n\n i am using armbian focal (current version) and the issue persisted, until, i found out where it was coming from.\n \n\n\n i have been able to repeatedly generate the system crash at will, it takes a few hours but it can be guaranteed to happen.\n \n\n\n  \n \n\n\n the cause is a particular windows 7 host that has not been updated in years. it runs windows 7 sp1 and the windows update was last run 3 years ago.\n \n\n\n other windows 7 machines have been updated and they have no effect on this board running armbian focal. \n \n so i guess there is some network bug in old windows 7 versions (which microsoft has since patched, most likely) such that when the host browses the smb share or even does a host lookup on the armbian host, it sends something that upsets the network stack, because in this condition, while the orangepi is technically unresponsive, it still, surprisingly responds to icmp requests. \n \n what i have done is to remove the particular windows 7 host from the network (unplugged the lan cable) and the problem has disappeared. i am now on 6 days of uptime on armbian. therefore i am fully convinced the windows 7 host has a network stack bug, sends garbage to the orangepi board and this somehow upsets the tcp stack in armbian.\n \n\n\n  \n \n\n\n neither another machine running the same windows 7 copy (but it is updated until microsoft stopped rolling out patches in march 2020), or a windows 10 machine, nor several ubuntu machines, nor a macbook pro affect this orangepi. \n solid as a rock. \n \n i will investigate the issue further if i have time, to pinpoint the exact cause but honestly, its easier to get rid of windows at this point. the machine in question is used for dtp uses i.e. corel draw and other software that's not available on mac or linux. \n  \n \n", "name": "", "is_accepted": false }, { "text": "i think i know what the problem is\n \n\n\n  \n \n\n\n the windows machine also runs nordvpn, which is used for accessing censored content outside of my country (certain necessary software updates are blocked by our government) \n recently, nordvpn changed the underlying network transport driver, which has not only broken a few things on the machine itself, it seems that when nordvpn is allowed to run on the machine and the machine has access to the orangepi, that's when things go horribly wrong. other devices accessed in a similar way have also shown odd symptoms.. an android media player locked up and froze... so some combination of my software is either no good or there's a bug in windows 7 that has since been patched. \n \n i am enjoying 9 days of uptime on the orangepi and have elected to rather format the windows 7 machine, reinstall all the software and keep it updated this time. nordvpn stuff will be done on a different machine now.\n \n", "name": "", "is_accepted": false }, { "text": "cve-2020-10730 in samba possibly culprit.\n \n", "name": "", "is_accepted": false }, { "text": "i am inclined to agree... but whatever i did the system is still up.\n \n", "name": "", "is_accepted": false } ]

[ { "text": "for those who may have the crashing problem with vlc in tinkerboards.\n \n\n\n        tools>pref>input/codecs/hardware-accelerateddecodeing select va-api video decoder via drm  \n \n\n\n correction....\n \n\n\n        tool>pref>video>output>xvideooutput  worked with 1080p\n \n", "name": "", "is_accepted": true }, { "text": "renamed so it can be catched easier \n \n\n\n  \n \n", "name": "", "is_accepted": false } ]

[ { "text": "hello, i neither have the boards you have nor the ap6212 wifi chip in any of my boards, but i can tell you that bluetooth is generally quite a beast.\n \n\n\n i have had experience with ap6330 and ap6334 (a clone, actually) and spent countless hours trying to sort things out.\n \n\n\n  \n \n\n\n first of all, the bluetooth adapter on the same chip of the wifi, but is actually a separate device. the wifi part is connected to the system via sdio bus, but the bluetooth is connected via a simpler uart serial port.\n \n\n\n the dmesg logs you provided are not showing anything related to the bluetooth hardware part, but just some software modules/components, you should provide the complete dmesg log (please put them in a spoiler section), because things happen in out-of-order fashion when device are initialized.\n \n\n\n  \n \n\n\n anyway, if you are very very lucky, running hciattach is everything you need:\n \n\n\n/usr/bin/hciattach /dev/ttys0 bcm43xx 1500000\n\n\n the program will not put itself in background, and you need to keep it running if you want to access bluetooth device. in case it works, you may want to create a systemd service or a script that runs at boot.\n \n\n\n change ttys0 with the serial port your bluetooth adapter is internally connected.\n \n\n\n you may need to put the right firmware file in /lib/firmware/brcm, i don't know which one is required so you have to discover it by yourself. maybe it is already there.\n \n\n\n  \n \n\n\n in case this does not work, debugging may take ten minutes to several hours/days and unfortunately requires quite a knownledge to deal with.\n \n", "name": "", "is_accepted": true }, { "text": "hi \n i'm adding details to my question, if somebody can help it would be very appreciated. \n to resume, my problem is that i have a orange pi zero plus2 h3 with armbian buster mainline based kernel 5.10.y, and bluetooth is not working (hciconfig -a does not report any controller); \n i also have a orange pi zero plus2 h5 (64bit) with linux orangepizeroplus2 4.17.2-sunxi64: here bluetooth is working correctly, with hciconfig -a reporting a controller with its parameters. \n \n here is the h5 dmesg output for the part related to bluetooth:\n \n\n\n \n  \n \n\n\n[...]\n\n[    4.789119] cfg80211: loading compiled-in x.509 certificates for regulatory database\n[    4.797546] cfg80211: loaded x.509 cert 'sforshee: 00b28ddf47aef9cea7'\n[    4.851379] brcmfmac: brcmf\\_fw\\_alloc\\_request: using brcm/brcmfmac43430-sdio for chip bcm43430/1\n[    4.879043] ext4-fs (mmcblk0p1): re-mounted. opts: commit=600,errors=remount-ro\n[    4.982040] brcmfmac: brcmf\\_fw\\_alloc\\_request: using brcm/brcmfmac43430-sdio for chip bcm43430/1\n[    4.982127] brcmfmac mmc1:0001:1: direct firmware load for brcm/brcmfmac43430-sdio.clm\\_blob failed with error -2\n[    4.982135] brcmfmac: brcmf\\_c\\_process\\_clm\\_blob: no clm\\_blob available (err=-2), device may have limited channels available\n[    4.982808] brcmfmac: brcmf\\_c\\_preinit\\_dcmds: firmware: bcm43430/1 wl0: mar 30 2016 11:30:56 version 7.45.77.h8.4 fwid 01-ee8a6268\n[    9.044878] systemd-journald[519]: received request to flush runtime journal from pid 1\n[...]\n[    9.058327] systemd-journald[519]: failed to open system journal: no space left on device\n[    9.058534] systemd-journald[519]: file /var/log/journal/40ce618d730f448b85f3daed6c5b8022/system.journal corrupted or uncleanly shut down, renaming and replacing.\n[   10.593343] random: crng init done\n[   10.593356] random: 7 urandom warning(s) missed due to ratelimiting\n[...]\n[   14.253974] systemd-journald[519]: failed to open system journal: no space left on device\n[   14.551745] bluetooth: core ver 2.22\n[   14.551831] net: registered protocol family 31\n[   14.551835] bluetooth: hci device and connection manager initialized\n[   14.551855] bluetooth: hci socket layer initialized\n[   14.551864] bluetooth: l2cap socket layer initialized\n[   14.551890] bluetooth: sco socket layer initialized\n[   15.727058] ipv6: addrconf(netdev\\_up): wlan0: link is not ready\n[   15.766873] ipv6: addrconf(netdev\\_up): wlan0: link is not ready\n[   16.021134] ipv6: addrconf(netdev\\_up): wlan0: link is not ready\n[   17.221116] ipv6: addrconf(netdev\\_change): wlan0: link becomes ready\n[   17.684839] mass storage function, version: 2009/09/11\n[   17.684856] lun: removable file: (no medium)\n[   18.094789] configfs-gadget gadget: high-speed config #1: c\n[   18.137450] bluetooth: hci uart driver ver 2.3\n[   18.137461] bluetooth: hci uart protocol h4 registered\n[   18.137464] bluetooth: hci uart protocol bcsp registered\n[   18.137467] bluetooth: hci uart protocol ath3k registered\n[   18.137470] bluetooth: hci uart protocol three-wire (h5) registered\n[   18.137621] bluetooth: hci uart protocol intel registered\n[   18.137625] bluetooth: hci uart protocol qca registered\n[   18.137628] bluetooth: hci uart protocol ag6xx registered\n[   18.137630] bluetooth: hci uart protocol marvell registered\n[   18.379092] bluetooth: bnep (ethernet emulation) ver 1.3\n[   18.379101] bluetooth: bnep filters: protocol multicast\n[   18.379120] bluetooth: bnep socket layer initialized\n\n\n \n here is the h3 dmesg: \n \n  \n \n\n\n[...]\n\n[    7.549941] cfg80211: loading compiled-in x.509 certificates for regulatory database\n[    7.645538] cfg80211: loaded x.509 cert 'sforshee: 00b28ddf47aef9cea7'\n[    7.663242] zram: added device: zram0\n[    7.677707] zram: added device: zram1\n[    7.682907] zram: added device: zram2\n[    7.709055] brcmfmac: brcmf\\_fw\\_alloc\\_request: using brcm/brcmfmac43430-sdio for chip bcm43430/1\n[    7.731474] brcmfmac mmc2:0001:1: direct firmware load for brcm/brcmfmac43430-sdio.xunlong,orangepi-zero-plus2-h3.txt failed with error -2\n[    7.731492] brcmfmac mmc2:0001:1: falling back to sysfs fallback for: brcm/brcmfmac43430-sdio.xunlong,orangepi-zero-plus2-h3.txt\n[    7.791392] asoc-simple-card sound: i2s-hifi <-> 1c22800.i2s mapping ok\n[    7.805223] zram1: detected capacity change from 0 to 241106944\n[    7.947163] brcmfmac: brcmf\\_fw\\_alloc\\_request: using brcm/brcmfmac43430-sdio for chip bcm43430/1\n[    7.949352] brcmfmac: brcmf\\_c\\_process\\_clm\\_blob: no clm\\_blob available (err=-11), device may have limited channels available\n[    7.950344] brcmfmac: brcmf\\_c\\_preinit\\_dcmds: firmware: bcm43430/1 wl0: oct  8 2016 15:31:47 version 7.46.57.4.ap.r4 (a1 station/p2p) fwid 01-3621395e es6.c5.n4.a3\n[    8.918383] adding 235452k swap on /dev/zram1.  priority:5 extents:1 across:235452k ssfs\n[    9.040297] zram0: detected capacity change from 0 to 52428800\n[   11.240959] ext4-fs (zram0): mounted filesystem without journal. opts: discard\n[   11.241006] ext4 filesystem being mounted at /var/log supports timestamps until 2038 (0x7fffffff)\n[   13.191644] random: crng init done\n[   13.191661] random: 7 urandom warning(s) missed due to ratelimiting\n[   17.097053] ipv6: addrconf(netdev\\_change): wlan0: link becomes ready\n\n\n  \n \n\n\n nb: here the dmesg outputs stops. there is no hci module loading. but even if i make it by hand: \n  \n \n\n\nmodprobe -v hci\\_uart\n\n\n \n i have this output:\n \n\n\n  \n \n\n\ninsmod /lib/modules/5.4.35-sunxi/kernel/crypto/ecc.ko \ninsmod /lib/modules/5.4.35-sunxi/kernel/crypto/ecdh\\_generic.ko \ninsmod /lib/modules/5.4.35-sunxi/kernel/net/bluetooth/bluetooth.ko \ninsmod /lib/modules/5.4.35-sunxi/kernel/drivers/bluetooth/btbcm.ko \ninsmod /lib/modules/5.4.35-sunxi/kernel/drivers/bluetooth/btrtl.ko \ninsmod /lib/modules/5.4.35-sunxi/kernel/drivers/bluetooth/hci\\_uart.ko \n\n\n \n \n and dmesg shows appended to the previous output:\n \n\n\n[  153.461277] bluetooth: core ver 2.22\n[  153.461478] net: registered protocol family 31\n[  153.461486] bluetooth: hci device and connection manager initialized\n[  153.461527] bluetooth: hci socket layer initialized\n[  153.461546] bluetooth: l2cap socket layer initialized\n[  153.461591] bluetooth: sco socket layer initialized\n[  153.488789] bluetooth: hci uart driver ver 2.3\n[  153.488812] bluetooth: hci uart protocol h4 registered\n[  153.488820] bluetooth: hci uart protocol bcsp registered\n[  153.488945] bluetooth: hci uart protocol ll registered\n[  153.488954] bluetooth: hci uart protocol ath3k registered\n[  153.489224] bluetooth: hci uart protocol three-wire (h5) registered\n[  153.489685] bluetooth: hci uart protocol broadcom registered\n\n\n \n  \n \n\n\n but hciconfig -a still does not show any controller. \n \n can somebody help or has some hint? \n thank you in advance\n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "thank you very much jock,\n \n\n\n i still don't have all needed knowledge, but i am lucky to have the h5 working, so before reading your answer i tried two script that are in my h5 and not in the h3 image, such as /etc/default/ap6212 and /etc/init.d/ap6212-bluetooth. especially the last is invoking, among the other things, just the hciattach you were mentioning, and also devmem2* and rfkill that were missing in the h3 environment (very strange the rfkill missing!) \n now, invoking ap6212-bluetooth by hand, i finally had the bluetooth working, but wifi stopped working and i had to relaunch it via armbian-config (deactivate/reactivate with my wifi essid).\n \n\n\n  \n \n\n\n now the last missing piece of the puzzle is: who and when should launch /etc/init.d/ap6212-bluetooth at startup, especially in order not to mess up bluetooth and wifi?** \n i'm continuing to investigate, anyway thanks a lot for the very useful overview\n \n\n\n  \n \n\n\n *: i took it from here https://github.com/henla464/wiroc-startupscripts/blob/master/devmem2 , thanks to henrik larsson\n \n\n\n **: update: i found how it works and used  \n sudo update-rc.d ap6212-bluetooth defaults\n \n\n\n that makes the correct links for the boot execution levels described in the script header. \n now everything works, bluetooth+wifi. \n thank you for having triggered the right path of searching!\n \n\nap6212 \nap6212-bluetooth ", "name": "", "is_accepted": false }, { "text": "glad to hear you solved the issue \n \n", "name": "", "is_accepted": false } ]

[ { "text": "it's working finally.  i guess update or a fresh install did it.\n \n\n\n this new installed asked me to update my firmware on the board. i said yes.\n \n\n\n i ran    sudo armbian-config   then installed the desktop. that is where it asked to update the firmware.\n \n\n\n  \n \n\n\n thanks for your help.\n \n\n\n  \n \n\n\n also the below stopped my vlc crashing.\n \n\n\n  \n \n\n\n        tool>pref>video>output>xvideooutput  worked with 1080p\n \n\n\n  \n \n", "name": "", "is_accepted": true }, { "text": "providing logs with \n \n\n\narmbianmonitor -u\n\n\n  helps with troubleshooting and significantly raises chances that issue gets addressed.\n \n", "name": "", "is_accepted": false }, { "text": "all the info you need is here.\n \n\n\n\n  \n \n", "name": "", "is_accepted": false } ]

[ { "text": "hi @rein we don't support any raspberry pi boards.   we focus on alternate sbcs that have less attention and community.\n \n\n\n  \n \n\n\n https://docs.armbian.com/quick\\_facts/#what-is-armbian-linux\n \n", "name": "", "is_accepted": true }, { "text": "thank you lanefu. \n \n", "name": "", "is_accepted": false } ]

[ { "text": "there is no \"special\" boot configuration since u-boot rely on the 3 symbolic links which point to proper image/uinitrd/dts .\n \n\n\n\n\n it is possible, but then you have to manually install every things and create the symbolic links as well as creating uinitrd using \"mkimage\".\n \n\n\n it is much more easier to use armbian debs ...\n \n", "name": "", "is_accepted": true }, { "text": "if you used armbian build scripts, it will produce a linux-image-*.deb, and when installed using \"dpkg -i\", it will take care of changing symbolic links in /boot and create new uinitrd file.\n \n", "name": "", "is_accepted": false }, { "text": "sir, i appreciate your reply.\n \n\n\n does that deb file include a proper boot configuration to boot the kernel within?\n \n\n\n and what if i built a kernel individually out of armbian building environment, how can i make it work with existing armbian system?\n \n\n\n  \n \n\n\n thank you.\n \n", "name": "", "is_accepted": false }, { "text": "hi, martinayotte,\n \n\n\n  \n \n\n\n thank you for helping me clear things out.\n \n\n\n i will see what i can do with this kernel. \n \n\n\n consider this topic closed. \n \n", "name": "", "is_accepted": false } ]

[ { "text": "good! we cleared out the libcec part.\n \n\n\n  \n \n\n\n now, let us try some kernel tweaks. install these kernel+dtb packages, reboot and try kodi again: https://users.armbian.com/jmcc/packages/kernel-rk64/\n \n", "name": "", "is_accepted": true }, { "text": "are you referring to the following (just announced today in fact!) or his previous version of same?\n \n\n\n  \n \n\n\n rk3399 legacy multimedia framework\n \n", "name": "", "is_accepted": false }, { "text": "i'm referring to this newer one (that i installed as soon as i saw jmcc's post), although i was never able to soft reboot using legacy kernels no matter which one i used (and i don't think the use of this tool, either the old or the new one, would have made any difference on this matter anyway)..\n \n\n\n  \n \n\n\n in fact i had already given up trying to make a server with kodi work with a legacy kernel. mainly because of this reboot issue, but also because of the lack of hdmi-cec support, that tried to enable on a customized kernel as described at the armbian documentation, but wasn't successful. so i just gave up...\n \n\n\n  \n \n\n\n then i saw the new tool jmcc released and decided to give it another try, imagining that maybe any new kernel release would have solved the cec and the reboot stuff, but apparently they're still not working.\n \n", "name": "", "is_accepted": false }, { "text": "aah, sorry to hear that.  yes this was my hope for you as well.\n \n\n\n  \n \n\n\n i had similar issue some time ago with some different board.  i had seriously considered plugging power supply into something like tasmota or other internet controlled switched outlet as a hacky work-around in the meantime, but then the problem must have gone away because it never really became a priority to implement that.  just an idea (especially if that's something you have laying around or might be interested in anyway)?\n \n", "name": "", "is_accepted": false }, { "text": "i am not sure about the reboot issue, since i don't own a rockpro64. but i tested the cec issue in my rockpi4, and it is not working either. i will look into it with god's favor.\n \n", "name": "", "is_accepted": false }, { "text": "in fact i'd never heard of these internet controlled switches. i appreciate the suggestion and i'll google it to see if i may adapt it to my needed. thank you for your interest. \n \n", "name": "", "is_accepted": false }, { "text": "believe me, it would be perfect if you could find a solution.\n \n\n\n  \n \n\n\n i tried to compile the kernel myself with cec as you suggested on the other thread (i still have the resulting generated deb files) but although it got installed without errors it made no difference. in fact a \"uname -a\" run after the installation and reboot showed what appeared to be the exact same kernel, as if no changes were made.. it was probably some mistake i made due to inexperience...\n \n\n\n  \n \n\n\n again, a working cec support on these rp64 would be amazing.\n \n", "name": "", "is_accepted": false }, { "text": "beside your current problem, they are super cool, anyway!  i mean, if you are into sbc, maybe you are (or will get) into these, too.  many of us are doing home automation stuff, as well, with our sbcs!  \n \n\n\n  \n \n\n\n there is a whole world of different radios you can use, but for this the wi-fi based ones (searching tasmota will get you started, but there are others, too) will probably fit your need best.\n \n\n\n  \n \n\n\n wi-fi switches (tasmota especially) are even quite easy to get working these days, there is a pretty big community around them, etc.\n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "can you please post the output of\n \n\n\napt install cec-utils -y -qq\nls -l /dev/cec*\ncec-client -l\n\n\n -\n \n", "name": "", "is_accepted": false }, { "text": "sure. i'd already tried to install this cec-utils before, btw.\n \n\n\n  \n \n\n\n and sorry i didn't post it with the correct code indentation. i'm using the smartphone and it's kind of hard to write...\n \n\n\n  \n \n\n\n root@nostromo:~# ls -l /dev/cec* \n crw-rw---- 1 root video 249, 0 dez 17 19:17 /dev/cec0\n \n\n\n  \n \n\n\n root@nostromo:~# cec-client -l \n libcec version: 4.0.4, compiled on linux-4.9.0-8-arm64 ... , features: p8\\_usb, drm, p8\\_detect, randr, exynos, aocec \n found devices: none\n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "it looks like it is a userspace problem, with buster libcec not supporting the rockchip interface. can you please install the packages from here: https://users.armbian.com/jmcc/packages/libcec/\n \n\n\n  \n \n\n\n then do the following tests, with your cec monitor/tv plugged:\n \n\n\nsudo cec-client -l\n\nsudo apt install v4l-utils -y -qq\nsudo cec-compliance -v -t -d0\n\n(if the above fails with \"missing logical address\", try the following and then repeat):\nsudo cec-ctl --phys-addr=2.0.0.0 --playback\nsudo cec-compliance -v -t -d0\n\n\n  \n \n\n\n for last, enable cec in kodi, and see if it works.\n \n\n\n thanks.\n \n", "name": "", "is_accepted": false }, { "text": "hello,\n \n\n\n  \n \n\n\n followed your instructions, but it still doesn't work.\n \n\n\n  \n \n\n\n not sure what i should have expected, but what happens is that after doing what you told i both restarted just the kodi proccess (systemctl restart kodi-gbm) and then reboot the board itself, but there's no option on input peripheral to configure (which means that kodi doesn't 'see' cec). also the tv hdmi configurations shows no hdmi device connect (when i'm using libreelec i can see my device listed).\n \n\n\n  \n \n\n\n as i said i'm accessing my board remotely via smartphone and it's kinda hard to copy / paste, etc, so im attaching the output of each of your suggested commands in separate files (in the order you told to do).\n \n\n\n  \n \n\n\n the weird part is that it doesn't seem to have error messages, which means that apparently it should be working...\n \n\n\n  \n \n\n\n thanks for taking the time to look into problem.\n \n\n\n  \n \n\n01\\_cec-ctl \n02\\_cec-compliance\\_after \n00\\_cec\\_compliance\\_before ", "name": "", "is_accepted": false }, { "text": "you forgot the output of \"cec-client -l\", that one is important! \n \n\n\n  \n \n\n\n install the new packages i created (file names are the same, but they are different):  https://users.armbian.com/jmcc/packages/libcec/\n \n\n\n  \n \n\n\n then, post the output of\n \n\n\nsudo cec-client -l\nsudo cec-compliance -v -t -d0\n\n\n  \n \n\n\n and try kodi again.\n \n\n\n  \n \n\n\n we are making baby steps, in order to identify the problem. sorry, i don't own the board nor any cec-capable monitor, so i cannot test myself. if it still doesn't work this time, don't worry, we still have two more steps that we need to check.\n \n", "name": "", "is_accepted": false }, { "text": "just to you to know, each time i install the packages you asked to (dpkg -i *.deb) i got the following message:\n \n\n\n  \n \n\n\nldconfig: /lib/aarch64-linux-gnu/libgl.so.1 is not a symbolic link\n\n\n  \n \n\n\n  \n \n\n\n and here you have it:\n \n\n\n  \n \n\n\nroot@nostromo:/home/leonardocaldas# cec-client -l\nlibcec version: 4.0.7, git revision: libcec-4.0.7+4-d6c8709~dirty, compiled on 2020-07-09 22:37:00 by root@localhost on linux 5.4.0-52-generic (aarch64), features: p8\\_usb, drm, p8\\_detect, randr, exynos, linux, aocec, 'i.mx6'\ncec-client: symbol lookup error: /lib/aarch64-linux-gnu/libcec.so.4: undefined symbol: \\_zn3cec27ctda995xcecadapterdetection11findadapterev\n\nroot@nostromo:/home/leonardocaldas# cec-compliance -v -t -d0\n cec\\_adap\\_g\\_caps returned 0 (success)\ncec-compliance sha : not available\n cec\\_adap\\_g\\_phys\\_addr returned 0 (success)\n cec\\_adap\\_g\\_log\\_addrs returned 0 (success)\ndriver info:\n driver name : dwhdmi-rockchip\n adapter name : dw\\_hdmi\n capabilities : 0x0000000e\n logical addresses\n transmit\n passthrough\n driver version : 4.4.213\n available logical addresses: 4\n physical address : 1.0.0.0\n logical address mask : 0x0010\n cec version : 2.0\n vendor id : 0x000c03 (hdmi)\n osd name : playback\n logical addresses : 1 (allow rc passthrough)\n\n logical address : 4 (playback device 1)\n primary device type : playback\n logical address type : playback\n all device types : playback\n rc tv profile : none\n device features :\n none\n\ncompliance test for device /dev/cec0:\n\n the test results mean the following:\n ok supported correctly by the device.\n ok (not supported) not supported and not mandatory for the device.\n ok (presumed) presumably supported. manually check to confirm.\n ok (unexpected) supported correctly but is not expected to be supported for this device.\n ok (refused) supported by the device, but was refused.\n fail failed and was expected to be supported by this device.\n\nfind remote devices:\n msg\\_poll: sequence: 181 tx timestamp: 29337.413s length: 1\n status: tx, not acknowledged (2), max retries\n msg\\_poll: sequence: 182 tx timestamp: 29337.472s length: 1\n status: tx, not acknowledged (2), max retries\n msg\\_poll: sequence: 183 tx timestamp: 29337.533s length: 1\n status: tx, not acknowledged (2), max retries\n msg\\_poll: sequence: 184 tx timestamp: 29337.592s length: 1\n status: tx, not acknowledged (2), max retries\n msg\\_poll: sequence: 185 tx timestamp: 29337.592s length: 1\n status: tx, not acknowledged (1), max retries\n msg\\_poll: sequence: 186 tx timestamp: 29337.652s length: 1\n status: tx, not acknowledged (2), max retries\n msg\\_poll: sequence: 187 tx timestamp: 29337.711s length: 1\n status: tx, not acknowledged (2), max retries\n msg\\_poll: sequence: 188 tx timestamp: 29337.771s length: 1\n status: tx, not acknowledged (2), max retries\n msg\\_poll: sequence: 189 tx timestamp: 29337.830s length: 1\n status: tx, not acknowledged (2), max retries\n msg\\_poll: sequence: 190 tx timestamp: 29337.889s length: 1\n status: tx, not acknowledged (2), max retries\n msg\\_poll: sequence: 191 tx timestamp: 29337.949s length: 1\n status: tx, not acknowledged (2), max retries\n msg\\_poll: sequence: 192 tx timestamp: 29338.008s length: 1\n status: tx, not acknowledged (2), max retries\n msg\\_poll: sequence: 193 tx timestamp: 29338.068s length: 1\n status: tx, not acknowledged (2), max retries\n msg\\_poll: sequence: 194 tx timestamp: 29338.127s length: 1\n status: tx, not acknowledged (2), max retries\n msg\\_poll: sequence: 195 tx timestamp: 29338.186s length: 1\n status: tx, not acknowledged (2), max retries\n polling: ok\n\nnetwork topology:\n\ntotal: 1, succeeded: 1, failed: 0, warnings: 0\n\n\n  \n \n\n\n as you can see, there's an error in the output of the first command that wasn't happening with the first bunch of packages i installed a couple of hours ago.\n \n\n\n  \n \n\n\n edit: and by the way, now kodi stopped working. i rebooted with no success...\n \n", "name": "", "is_accepted": false }, { "text": "okay, new bunch of packages. please do the same tests\n \n", "name": "", "is_accepted": false }, { "text": "whatever you did now it's almost working!\n \n\n\n  \n \n\n\n i mean, i got a different message to the first command:\n \n\n\nroot@nostromo:/mnt/dados# sudo cec-client -l\nlibcec version: 4.0.7, git revision: libcec-4.0.7+4-f9bb94a~dirty, compiled on 2020-07-09 22:37:00 by root@localhost on linux 5.4.0-52-generic (aarch64), features: p8\\_usb, drm, p8\\_detect, randr, exynos, linux, aocec\nfound devices: 1\n\ndevice: 1\ncom port: linux\nvendor id: 0000\nproduct id: 0000\nfirmware version: 0\ntype: linux\n\n\n  \n \n\n\n  \n \n\n\n so now when i start kodi-gbm it now shows the popup telling that the cec pulse8 peripheral was detected and also there's the option to configure the cec options (this is the very first time i'm able to use this option on a armbian legacy kernel).\n \n\n\n  \n \n\n\n and here goes the output of the second command:\n \n\n\n  \n \n\n\nleonardocaldas@nostromo:~$ sudo cec-compliance -v -t -d0\n cec\\_adap\\_g\\_caps returned 0 (success)\ncec-compliance sha : not available\n cec\\_adap\\_g\\_phys\\_addr returned 0 (success)\n cec\\_adap\\_g\\_log\\_addrs returned 0 (success)\ndriver info:\n driver name : dwhdmi-rockchip\n adapter name : dw\\_hdmi\n capabilities : 0x0000000e\n logical addresses\n transmit\n passthrough\n driver version : 4.4.213\n available logical addresses: 4\n physical address : 1.0.0.0\n logical address mask : 0x0002\n cec version : 1.4\n vendor id : 0x001582 (pulse-eight)\n osd name :\n logical addresses : 1 (allow fallback to unregistered)\n\n logical address : 1 (recording device 1)\n primary device type : record\n logical address type : record\n\ncompliance test for device /dev/cec0:\n\n the test results mean the following:\n ok supported correctly by the device.\n ok (not supported) not supported and not mandatory for the device.\n ok (presumed) presumably supported. manually check to confirm.\n ok (unexpected) supported correctly but is not expected to be supported for this device.\n ok (refused) supported by the device, but was refused.\n fail failed and was expected to be supported by this device.\n\nfind remote devices:\n msg\\_poll: sequence: 1464 tx timestamp: 812.724s length: 1\n status: tx, not acknowledged (2), max retries\n msg\\_poll: sequence: 1466 tx timestamp: 812.725s length: 1\n status: tx, not acknowledged (1), max retries\n msg\\_poll: sequence: 1467 tx timestamp: 812.842s length: 1\n status: tx, not acknowledged (2), max retries\n msg\\_poll: sequence: 1468 tx timestamp: 812.902s length: 1\n status: tx, not acknowledged (2), max retries\n msg\\_poll: sequence: 1469 tx timestamp: 812.962s length: 1\n status: tx, not acknowledged (2), max retries\n msg\\_poll: sequence: 1470 tx timestamp: 813.021s length: 1\n status: tx, not acknowledged (2), max retries\n msg\\_poll: sequence: 1471 tx timestamp: 813.080s length: 1\n status: tx, not acknowledged (2), max retries\n msg\\_poll: sequence: 1472 tx timestamp: 813.140s length: 1\n status: tx, not acknowledged (2), max retries\n msg\\_poll: sequence: 1473 tx timestamp: 813.200s length: 1\n status: tx, not acknowledged (2), max retries\n msg\\_poll: sequence: 1474 tx timestamp: 813.265s length: 1\n status: tx, not acknowledged (2), max retries\n msg\\_poll: sequence: 1475 tx timestamp: 813.325s length: 1\n status: tx, not acknowledged (2), max retries\n msg\\_poll: sequence: 1476 tx timestamp: 813.384s length: 1\n status: tx, not acknowledged (2), max retries\n msg\\_poll: sequence: 1477 tx timestamp: 813.444s length: 1\n status: tx, not acknowledged (2), max retries\n msg\\_poll: sequence: 1478 tx timestamp: 813.503s length: 1\n status: tx, not acknowledged (2), max retries\n msg\\_poll: sequence: 1479 tx timestamp: 813.563s length: 1\n status: tx, not acknowledged (2), max retries\n polling: ok\n\nnetwork topology:\n\ntotal: 1, succeeded: 1, failed: 0, warnings: 0\n\n\n  \n \n\n\n the only thing is that although kodi detects the cec structure, the remote still doesn't work.\n \n\n\n  \n \n\n\n i've tried to make a couple of changes both using that command line which changes the hdmi physical address and trying to change them (both the hdmi physical address and port) on the kodi config options. but it didn't work. in fact, in the case of kodi no matter which physical address i fill as soon as i restart it comes back to what i imagine is the default (1000).\n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "it worked! as soon as i rebooted after installing this new kernel it immediately worked!\n \n\n\n  \n \n\n\n thank you so very much for your invaluable help! after months of unsuccessful trials it's finally working. \n \n\n\n  \n \n\n\n is there a way these modifications you did (the kernel and the other patched packages) may become available by default on the rockpro64 armbian image? it would make the kodi part of your multimedia project even more complete and attractive to people with this specific board.\n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "that was the intention, and the purpose of all the testing we did \n \n", "name": "", "is_accepted": false }, { "text": "module dw-hdmi-cec is not enabled by default in legacy kernel for rk3399 chips. after enable this option in kernel, cec starts working.\n \n\n\n # config\\_drm\\_dw\\_hdmi\\_cec is not set\n \n", "name": "", "is_accepted": false }, { "text": "there are two different kernels for rk3399, which one are you talking about? i guess it is the rk3399, not he rockchip64. what is the board? enviado desde mi moto g(6) plus mediante tapatalk ", "name": "", "is_accepted": false }, { "text": "yes, it is rk3399. my board is nanopct4.\n \n", "name": "", "is_accepted": false }, { "text": "misunderstanding. @jmccasked for the kernel, not the soc. just look for\n \r\ncode {\r\n font-family: consolas,\"courier new\";\r\n color: crimson;\r\n background-color: rgba(0, 0, 0, 0.2);\r\n padding: 2px;\r\n font-size: 105%;\r\n} \n uname -a if the output states rockchip64 or rk3399\n \n", "name": "", "is_accepted": false }, { "text": "it's ok, nanopct4 has rk3399 kernel. it is good to know that it only needs kernel configs to be enabled, unlike the rockpi and rockpro64 that needed dt patches in the rockchip64 kernel enviado desde mi moto g(6) plus mediante tapatalk ", "name": "", "is_accepted": false }, { "text": "hello jmcc,\n \n\n\n  \n \n\n\n i've been using the legacy kernel with kodi and your multimedia solution and it's been working very well (apart from that reboot problem, but... well... i just sort of got used to it, and all).\n \n\n\n  \n \n\n\n the issue i have is about lots of kernel error messages i'm getting. i sincerely don't remember if they already existed on the old kernel, although i believe not, since they are so many that would certainly got my attention, and i'm afraid it may be somehow corrupting data.\n \n\n\n  \n \n\n\n at first i get these messages:\n \n\n\n[ 656.941038] zram: decompression failed! err=-22, page=12547\n[ 656.941050] zram: decompression failed! err=-22, page=12547\n[ 656.942641] zram: decompression failed! err=-22, page=12616\n[ 656.942656] zram: decompression failed! err=-22, page=12616\n[ 656.946072] zram: decompression failed! err=-22, page=3109\n[ 656.946370] zram: decompression failed! err=-22, page=3109\n[ 656.946378] zram: decompression failed! err=-22, page=3109\n\n\n  \n \n\n\n they keep repeating to the point that there's nothing more on dmesg but them.\n \n\n\n  \n \n\n\n then, after a while i also get these messages:\n \n\n\n[283017.217836] ext4-fs error (device zram0) in ext4\\_ext\\_truncate:4688: filesystem failed crc\n[283055.643907] ext4-fs error (device zram0): ext4\\_find\\_extent:916: inode #22: comm sshd: pblk 1635 bad header/extent: extent tree corrupted - magic f30a, entries 69, max 340(340), depth 0(0)\n[283055.645528] ext4-fs error (device zram0): ext4\\_ext\\_remove\\_space:2999: inode #22: comm sshd: pblk 1635 bad header/extent: extent tree corrupted - magic f30a, entries 69, max 340(340), depth 0(0)\n[283055.646503] ext4-fs error (device zram0) in ext4\\_ext\\_truncate:4688: filesystem failed crc\n\n\n  \n \n\n\n and finally it gets to the point that the disk gets unavailable and only works if a reboot.\n \n\n\n  \n \n\n\n the messages refer to an external usb 3 disk and i know that it's working fine because if i switch to the libreelec sd card it never show these error messages.\n \n\n\n  \n \n\n\n a appreciate any help you could give me.\n \n\n\n  \n \n\n\n i believe it's somehow related to zram. i have the zram-tools package installed, but it's probably some issue on the kernel level.\n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "arre you talking about the tweaked kernel i linked above? that was just for testing. now, the relevant changes are merged into the build script. so, if you are still using the testing version, just install a recently built kernel: either build your own debs with the build script, download it from beta, or wait for the next stable release.\n \n\n\n  \n \n\n\n the errors you show are not critical, it seems like probably ext4 debug was enabled on that kernel. if after switching to the official kernel the problem persists, we'll look into it.\n \n", "name": "", "is_accepted": false } ]

[ { "text": "this problem should be resolved. cdn needs several hours ... so perhaps not right now.\n \n", "name": "", "is_accepted": true }, { "text": "most likely reason:\n \n\n\n\n edit: i tested manually on beta repository by changing nothing - and index is signed.\n \n", "name": "", "is_accepted": false }, { "text": "unfortunatelly i have same situation:\n \n\n\n  \n \n\nigor@ovpngw:~$ sudo apt update\n[sudo] password for igor: \nhit:1 http://ppa.launchpad.net/ultradvorka/ppa/ubuntu bionic inrelease\nhit:2 http://ports.ubuntu.com bionic inrelease \nhit:4 http://ports.ubuntu.com bionic-security inrelease \nhit:5 http://ports.ubuntu.com bionic-updates inrelease\nhit:6 http://ports.ubuntu.com bionic-backports inrelease \nign:3 https://armbian.hosthatch.com/apt bionic inrelease \nget:7 https://armbian.systemonachip.net/apt bionic release [17,5 kb] \nign:8 https://armbian.systemonachip.net/apt bionic release.gpg \nreading package lists... done\ne: the repository 'http://apt.armbian.com bionic release' is no longer signed.\nn: updating from such a repository can't be done securely, and is therefore disabled by default.\nn: see apt-secure(8) manpage for repository creation and user configuration details.\n\n\n please, what can i do to fix this (if i can anything at all)?\n \n", "name": "", "is_accepted": false }, { "text": "probably our repository has to be reindexed properly. then it has to be distributed to the cdn. 24-48h is needed after its fixed.\n \n\n\n  \n \n\n\n but ... i am currently too busy to check and fix this problem and we have no backup for this particular task. if 3rd party tooling is the cause of this problem, then i might need several days just to dig in and fix. i have no knowledge of aptly which we use for repository management. and tbh no interest to learn its internals. \n \n", "name": "", "is_accepted": false }, { "text": "ok, than i need just wait. no problem, this is not such a big issue.\n \n", "name": "", "is_accepted": false }, { "text": "here's what i did to get around the issue in the meantime: \n \n\n\n  \n \n\n$ cat /etc/apt/sources.list.d/armbian.list\ndeb [trusted=yes] http://apt.armbian.com bionic main bionic-utils bionic-desktop\n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "oh, that is good.  i have one machine which really need kernel update, because it was offline last six months. thank you very much.\n \n", "name": "", "is_accepted": false }, { "text": "hey, i have the same issue and would love if the fix will be available soon.\n \n\n\n  \n \n\n\n thank you very much in advance!\n \n", "name": "", "is_accepted": false }, { "text": "same issue replicated.\n \n", "name": "", "is_accepted": false }, { "text": "i looked again, aptly is signing, but repository is unsigned. just bionic. others are signed. no idea why ... another workaround is upgrading to focal.\n \n\n\n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "the work around [trusted=yes] no longer works. as igor said, bionic one is not signed. \n \n\n\n  \n \n\n\n if you must, \n \n\n\n  \n \n\n\n $ sudo apt update -o acquire::allowinsecurerepositories=true -o acquire::allowdowngradetoinsecurerepositories=true\n \n\n\n  \n \n\n\n for the time being while it's being solved (hopefully, it is).\n \n\n\n  \n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "\"... another workaround is upgrading\" == a one line command becomes an all day project. \n \n\n\n  \n \n\n\n [trusted=yes] is working here...for now.\n \n", "name": "", "is_accepted": false }, { "text": "it's working for me now. thanks igor.\n \n", "name": "", "is_accepted": false }, { "text": "to normal updating need reinstall key:\n \n\n\n 1. download key \n \n\nwget https://armbian.hosthatch.com/apt/armbian.key\n\n\n 2. install key \n \n\napt-key add armbian.key\n\n\n 3. upadte\n \n\napt update\n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "hello,\n \n\n\n  \n \n\n\n i am still facing the\n \n\ne: the repository 'http://apt.armbian.com bionic release, is no longer signed.\n\n\n  \n \n\n\n  error message when attempting a\n \n\napt update\n\n\n  \n \n\n\n so far, i have tried:\n \n\n\n  \n \n\n\n 1. waiting\n \n\n\n 2. re-adding the repository key as suggested by user \"favorit800\" in this thread.\n \n\n\n 3. setting the repository as \"trusted\" as suggested by \"jerry jyrer\" in this thread.\n \n\n\n  \n \n\n\n none of the above have worked, i am running: \n  \n \n\n~$ cat /etc/armbian-release\n# please do not edit this file\nboard=rock64\nboard\\_name=\"rock 64\"\nboardfamily=rockchip64\nbuild\\_repository\\_url=https://github.com/armbian/build\nbuild\\_repository\\_commit=baaefaf69-dirty\ndistribution\\_codename=bionic\ndistribution\\_status=csc\nversion=21.05.4\nlinuxfamily=rockchip64\narch=arm64\nimage\\_type=user-built\nboard\\_type=csc\ninitrd\\_arch=arm64\nkernel\\_image\\_type=image\nbranch=current\n\n\n\n~$ uname -a\nlinux rock64 5.10.43-rockchip64 #21.05.4 smp preempt wed jun 16 08:02:12 utc 2021 aarch64 aarch64 aarch64 gnu/linux\n\n\n  \n \n\n\n any eta regarding the repository signing ?\n \n\n\n  \n \n\n\n regards!\n \n", "name": "", "is_accepted": false }, { "text": "i'm having the same problem on my orange pi and i've tried all the posted answers as well.\n \n", "name": "", "is_accepted": false }, { "text": "it was fixed for a day or two but it broke again. this means quick fix doesn't work well, while serious and expensive time slot to tear down this complicated mechanism can't be allocated just like that. if you want that things works smoothly, you should not leave also costs of maintenance on our shoulders. we already blow too much on r&d and are crying for help, repository management tool authors as well, ...\n \n\n\n  \n \n\n\n\n\n \n even this is unrelated to the problem from the topic - your hardware (rock64 due to quality issues) and software (armbian bionic is old lts) and the way it was build (user-built / support is only for digitally signed releases) is not eligible for support we / armbian maintainers pay for you. we can't cover.\n \n\n\n  \n \n\n\n\n\n  \n \n\n\n no eta. it is urgent matter and will be fixed accordingly. with another quick fix, i am on vacations.\n \n", "name": "", "is_accepted": false }, { "text": "another try. hopefully it will last forever and after.\n \n", "name": "", "is_accepted": false }, { "text": "good for you, you deserve it.\n \n\n\n  \n \n\n\n no wonder your tone is more calm than usual.  \n \n", "name": "", "is_accepted": false }, { "text": "i have a large number of distributed orangepi (plus2e and zero) systems running armbian stretch, and am building a few more. \n \n\n\n i do not want to attempt remote dist upgrades to buster, because if there are upgrade failures it may result in downtime, or worse - require a trip to the site.\n \n\n\n i also want all my systems on roughly the same version to simplify support issues.\n \n\n\n  \n \n\n\n i also understand you do not want to support stretch into the future; but, could the \"last\" versions of your stretch packages still be available from your package server, even though they are no longer updated/maintained? this would allow me to set up new stretch systems to match the existing systems in the field.\n \n\n\n  \n \n\n\n i have also had to comment out the /etc/apt/sources.list.d/armbian.list content so that 'apt update' does not error out on all the deployed systems.\n \n\n\n  \n \n\n\n the day will come where i will devise some reliable procedure to upgrade all deployed systems to a current distribution/kernel; however, i do not currently have the resources to make that happen - something that i expect you guys at armbian can appreciate.\n \n\n\n  \n \n\n\n thank you,\n \n\n\n kevin\n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "most of this is a flaw in how we've managed apt repos to this point, but it does seem reasonable to keep old packages. \n \n\n\n  \n \n\n\n let me talk to @igor\n \n", "name": "", "is_accepted": false }, { "text": "okay so unfortunately not a quick fix.     \n \n we had some major repository issues a while back, and the tool we use to generate is broken.  see this thread for a little more context. \n \n are you familiar with ansible?   the `lineinfile` module could probably clean this up quickly if you have ssh access. \n \n or the `copy` modules to just replace the armbian sources file\n \n", "name": "", "is_accepted": false }, { "text": "@lanefu i have added - lets see if it doesn't break anything  https://github.com/armbian/build/pull/3087\n \n", "name": "", "is_accepted": false }, { "text": "archives for old packages are simply necessary. i have 3 pcs of opi zero, on the old kernel with oc armbian xenial (since i use tv out). and, if i have to add opi zero, i won't be able to do it, so i won't get an update of armbian xenial packages. thanks!\n \n", "name": "", "is_accepted": false }, { "text": "last change in legacy kernel is several years old -  if there are no changes to kernel sources for years, there is no point in building and updating packages with newer versions.\n \n", "name": "", "is_accepted": false }, { "text": "how i download kernel headrs for old kernel - armbian xenial?\n \n", "name": "", "is_accepted": false }, { "text": "firmware packages do not depend on userspace. all flavors (e.g. focal, buster and so on) share the same kernel packages.\n \n\n\n search apt. if it is not there what you are looking for then the package is probably too old and has been removed.\n \n", "name": "", "is_accepted": false }, { "text": "first of all, thank you - i no longer get errors on \"apt update\" when i have the /etc/apt/sources.list.d/armbian.list content un-commented for my stretch systems. much appreciated.\n \n\n\n  \n \n\n\n one thing i expected to get with this was package updates related to armbian versions, such as:\n \n\nlinux-dtb-next-sunxi/now 5.83 armhf [installed,local]\nlinux-image-next-sunxi/now 5.83 armhf [installed,local]\nlinux-libc-dev/now 5.70 armhf [installed,local]\nlinux-stretch-root-next-orangepiplus2e/now 5.83 armhf [installed,local]\nlinux-u-boot-orangepiplus2e-next/now 5.83 armhf [installed,local]\n\n\n to be clear(er), i initially install with the armbian 5.83 image (the last one with the 4.19.x kernel, specifically 4.19.38-sunxi). then i apt update/upgrade. this had brought my earlier systems up to armbian 5.90 with kernel 4.19.62-sunxi. but even with the stretch support re-added to the repo server, that is no longer happening.\n \n\n\n  \n \n\n\n it is likely i am confused about where those linux packages were coming from, and perhaps i'm splitting hairs about dealing with two old kernel versions. but i'd thought it was worth asking about.\n \n\n\n \n thanks again for the timely response\n \n\n\n kevin\n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "https://forum.armbian.com/topic/12210-armbian-1911y-release-notes/\n \n", "name": "", "is_accepted": false } ]

[ { "text": "there is nothing wrong on our side - we just don't build and publish our package upgrades for stretch repository anymore. (automatically) only for those marked as supported: https://github.com/armbian/build/tree/master/config/distributions support from debian ended 01 jan 2020 and i assume kernel upgrades, which are anyway coming from us, are at stretch going to die june 2022 (this info is extracted from quick search on the net, so its not official)\n \n", "name": "", "is_accepted": true }, { "text": "yes, but the the lts support for jessie is till end of june 2022!\n \n\n\n  \n \n\n\n https://www.debian.org/releases/stretch/ \"debian 9 has been superseded by debian 10 (buster). security updates have been discontinued as of july 6th, 2020.\n \n\n\n however, stretch benefits from long term support (lts) until the end of june 2022. the lts is limited to i386, amd64, armel, armhf and arm64. all other architectures are no longer supported in stretch. for more information, please refer to the lts section of the debian wiki.\" --> \"debian long term support (lts) is a project to extend the lifetime of all debian stable releases to (at least) 5 years. debian lts is not handled by the debian security team, but by a separate group of volunteers and companies interested in making it a success.\n \n\n\n thus the debian lts team takes over security maintenance of the various releases once the debian security team stops its work.\"\n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "this does not necessarily mean that armbian activly supports stretch or jessie as userspace. not possible due to lack of ressources.\n \n", "name": "", "is_accepted": false }, { "text": "ok, thanks. i did not realize i was on stretch \n \n\n\n  \n \n\n\n i did this:\n \n\nsudo sed -i 's|stretch|buster|g' /etc/apt/sources.list\nsudo sed -i 's|stretch|buster|g' /etc/apt/sources.list.d/armbian.list\nsudo sed -i 's|stretch|buster|g' /etc/apt/sources.list.d/nodesource.list\nsudo apt update && sudo apt -y upgrade && sudo apt -y dist-upgrade\n\n\n  \n \n\n\n then rebooted and run the update again.\n \n\n\n  \n \n\nsudo apt-get update && sudo apt-get full-upgrade\nsudo apt autoremove\nsudo apt autoclean\n\n\n  \n \n\n\n seems to work!\n \n\n\n  \n \n\n\n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "hate to necro something that was already answered, but is there any way for someone to get (or build themselves) the previous stretch repo?  i have a device that is unfortunately stuck on stretch for the at least the next several months and the missing repo is causing a few problems.  happy to provide the resources myself, but not sure where to look to get the old repo files...\n \n", "name": "", "is_accepted": false }, { "text": "will be provided for the future https://github.com/armbian/build/pull/3087 \n \n\n\n  \n \n\n\n\n\n \n repository rebuild time is prolonged at each update and one block (stretch buster focal) takes approximately the same time to re-publish. now - perhaps its not coded well, but we have no time to diagnose the tool and/or our implementation - or switch to another tool. too complicated.\n \n\n\n  \n \n\n\n better hardware also won't help here, since its already running on a threadripper 3990 and it its run is barely noticed.\n \n\n\n \n if you want to help: https://forum.armbian.com/forum/54-help-wanted/ if you have some solid hardware / vm with 32gb and many recent cores we could use it for build runner to get down with images rebuilt time.\n \n", "name": "", "is_accepted": false } ]

[ { "text": "i had cloned a different branch. i guess the issue is fixed.\n \n\n\n  \n \n\n\n the build is failing while downloading the tool chain but it could be a different issue.\n \n\n\n  \n \n\n\n -r\n \n", "name": "", "is_accepted": true }, { "text": "the branch parameter is a little misleading in compile.  choices are typically legacy,current,dev\n \n\n\n  \n \n\n\n take a look at the docs there should be a kernel\\_branch parameter\n \n", "name": "", "is_accepted": false } ]

[ { "text": "https://armbian.hosthatch.com/archive/orangepizero/archive/\n \n", "name": "", "is_accepted": true }, { "text": "hello,\n \n\n\n  \n \n\n\n of course, this is where i went first, but wanted older versions.\n \n\n\n i found an alternative, it's good\n \n\n\n  \n \n\n\n good evening to you @nicod (alias mr impolite )\n \n", "name": "", "is_accepted": false }, { "text": "well, would you care to share, for the benefit of others who may come along later?\n \n\n\n  \n \n\n\n\n\n  \n \n\n\n not sure what to make of this, maybe you guys know each other and this is some kind of inside joke?  maybe just trying to be funny?  i try to assume good intent, however...  otherwise i think uncalled for towards someone who is trying to help you?\n \n", "name": "", "is_accepted": false }, { "text": "sorry to try to help... ???\n \n", "name": "", "is_accepted": false } ]

[ { "text": "success! \n \n\n\n  \n \n\n\n \n% uname -a\nlinux miki 5.10.21-rockchip64 #21.02.3 smp preempt mon mar 8 01:05:08 utc 2021 aarch64 aarch64 aarch64 gnu/linux\n\n% dpkg -l | grep -v ^rc | grep -e \"linux-dtb-current|linux-image-current\"\nii  linux-dtb-current-rockchip64            21.02.3                              arm64        linux dtb, version 5.10.21-rockchip64\nii  linux-image-current-rockchip64          21.02.3                              arm64        linux kernel, version 5.10.21-rockchip64\n\n \n\n% aplay -l\n**** list of playback hardware devices ****\nxcb\\_connection\\_has\\_error() returned true\ncard 0: realtekrt5651co [realtek,rt5651-codec], device 0: ff890000.i2s-rt5651-aif1 rt5651-aif1-0 [ff890000.i2s-rt5651-aif1 rt5651-aif1-0]\n  subdevices: 0/1\n  subdevice #0: subdevice #0\ncard 1: hdmisound [hdmi-sound], device 0: ff8a0000.i2s-i2s-hifi i2s-hifi-0 [ff8a0000.i2s-i2s-hifi i2s-hifi-0]\n  subdevices: 1/1\n  subdevice #0: subdevice #0\n\n \n\n% grep -ie \"name|linux|version\" /etc/armbian-release\nboard\\_name=\"nanopi m4v2\"\ndistribution\\_codename=focal\nversion=21.02.3\nlinuxfamily=rockchip64\n\n \n\n\n  \n \n\n\n patched .dts: \n \n--- a/dt-bindings/clock/rk3399-cru.h\n+++ b/dt-bindings/clock/rk3399-cru.h\n@@ -19,6 +19,7 @@\n #define armclkb                9\n\n /* sclk gates (special clocks) */\n+#define sclk\\_i2sout\\_src        64\n #define sclk\\_i2c1            65\n #define sclk\\_i2c2            66\n #define sclk\\_i2c3            67\ndiff --git a/rk3399-som-rk3399v2.dts b/rk3399-som-rk3399v2.dts\nindex 2626e27..6c708f8 100644\n--- a/rk3399-som-rk3399v2.dts\n+++ b/rk3399-som-rk3399v2.dts\n@@ -75,6 +75,35 @@\n             };\n         };\n     };\n+\n+    rt5651\\_card: rt5651-sound {\n+        status = \"okay\";\n+        compatible = \"simple-audio-card\";\n+        pinctrl-names = \"default\";\n+        pinctrl-0 = <&hp\\_det>;\n+\n+        simple-audio-card,name = \"realtek,rt5651-codec\";\n+        simple-audio-card,format = \"i2s\";\n+        simple-audio-card,mclk-fs = <256>;\n+        simple-audio-card,hp-det-gpio = <&gpio4 28 gpio\\_active\\_high>;\n+\n+        simple-audio-card,widgets =\n+            \"microphone\", \"mic jack\",\n+            \"headphone\", \"headphone jack\";\n+        simple-audio-card,routing =\n+            \"mic jack\", \"micbias1\",\n+            \"in2p\", \"mic jack\",\n+            \"in3p\", \"mic jack\",\n+            \"headphone jack\", \"hpol\",\n+            \"headphone jack\", \"hpor\";\n+\n+        simple-audio-card,cpu {\n+            sound-dai = <&i2s1>;\n+        };\n+        simple-audio-card,codec {\n+            sound-dai = <&rt5651>;\n+        };\n+    };\n };    // root/ node\n\n &vcc3v3\\_sys {\n@@ -114,3 +143,44 @@\n         };\n     };\n };\n+\n+&i2c1 {\n+    status = \"okay\";\n+    i2c-scl-rising-time-ns = <300>;\n+    i2c-scl-falling-time-ns = <15>;\n+    clock-frequency = <200000>;\n+\n+    rt5651: rt5651@1a {\n+        #sound-dai-cells = <0>;\n+        compatible = \"realtek,rt5651\";\n+        reg = <0x1a>;\n+        clocks = <&cru sclk\\_i2s\\_8ch\\_out>;\n+        clock-names = \"mclk\";\n+        status = \"okay\";\n+    };\n+};\n+\n+&i2s1 {\n+    assigned-clocks = <&cru sclk\\_i2sout\\_src>;\n+    assigned-clock-parents = <&cru sclk\\_i2s1\\_8ch>;\n+    pinctrl-names = \"default\";\n+    pinctrl-0 = <&i2s\\_8ch\\_mclk>,<&i2s1\\_2ch\\_bus>;\n+    rockchip,playback-channels = <2>;\n+    rockchip,capture-channels = <2>;\n+    #sound-dai-cells = <0>;\n+    status = \"okay\";\n+};\n+\n+&pinctrl {\n+    i2s1 {\n+        i2s\\_8ch\\_mclk: i2s-8ch-mclk {\n+            rockchip,pins = <4 rk\\_pa0 1 &pcfg\\_pull\\_none>;\n+        };\n+    };\n+\n+    headphone {\n+        hp\\_det: hp-det {\n+            rockchip,pins = <4 28 rk\\_func\\_gpio &pcfg\\_pull\\_up>;\n+        };\n+    };\n+};\n\n \n\n\n  \n \n\n\n funny thing is that clk\\_parent will change after audio player is started: \n \n% cat /sys/kernel/debug/clk/clk\\_i2sout\\_src/clk\\_parent\nclk\\_i2s1\n% mpv <audiofile>\n% cat /sys/kernel/debug/clk/clk\\_i2sout\\_src/clk\\_parent\nclk\\_i2s0\n \n but in both cases sound works on my som-rk3399v2 sbc :)\n\n", "name": "", "is_accepted": true }, { "text": "this may be related to issues going on in a different thread: https://forum.armbian.com/topic/16401-77666669616-rockchip-i2s-ff890000i2s-fail-to-set-mclk-22/\n \n\n\n  \n \n\n\n basically, it looks like the i2s devices &i2s1 and &i2s2 aren't being initialized with the correct clock.\n \n\n\n  \n \n\n\n at a glance, i don't see anything glaring in the dtb for the i2s devices @ ff89000 and ff8a0000, but something is definitely off.\n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "so, been poking at this, not really making any progress, but did have some thoughts.\n \n\n\n  \n \n\n\n first, i realized later that you're missing the output of \"armbianmonitor -u\". recommend you upload and put at the top of your post. you'll probably get more interest if folks know more about your environment.\n \n\n\n  \n \n\n\n second, there are some substantial differences between the friendlyelec and armbian dtb's. the friendlyelec dtb provides a \"status = okay\" on both \"/rt5651-sound\" and \"&rt5651\". it also provides a number of \"assigned-clocks\" and \"reset\" definitions as well. none of those are in the armbian dtb. the armbian dtb does define \"&i2s1\" as having 8 playback and capture channels, which i doesn't look like it's correct. however, attempts as using an overlay to tweak the dtb to look more like the friendlyelec version has not resulted in a working audio channel.\n \n", "name": "", "is_accepted": false }, { "text": "more digging.\n \n\n\n  \n \n\n\n looks like folks have gotten the m4 (v1) headphone jack working in the past. at minimum, you may have to fiddle with alsa settings a bit before it does much: https://forum.armbian.com/topic/9605-sound-problems-with-nanopi-m4/?do=findcomment&comment=72701\n \n\n\n  \n \n\n\n i was not able to get the headphone jack working, but hdmi is working for me. so at least most of the audio subsystem is intact. had to set the default audio device to hdmi via pactl before i got anything out of it though.\n \n\n\n  \n \n\n\n both i2s controllers on ff890000 and ff8a0000 are still screaming into the system log though. guess it's not a fatal error though?\n \n", "name": "", "is_accepted": false }, { "text": "armbianmonitor uploaded\n \n\n\n booted into friendlyelec distribution and gather some logs:\n \n\n\n \n\nlinux som-rk3399v2 4.4.179 #2 smp tue sep 15 15:59:49 cst 2020 aarch64 aarch64 aarch64 gnu/linux\n\n \n\nroot@som-rk3399v2:~# aplay -l\n**** list of playback hardware devices ****\ncard 0: realtekrt5651co [realtek,rt5651-codec], device 0: ff890000.i2s-rt5651-aif1 rt5651-aif1-0 []\n  subdevices: 1/1\n  subdevice #0: subdevice #0\ncard 1: rockchiphdmi [rockchip,hdmi], device 0: ff8a0000.i2s-i2s-hifi i2s-hifi-0 []\n  subdevices: 1/1\n  subdevice #0: subdevice #0\n\n \n\nroot@som-rk3399v2:~# dmesg | grep -i i2s\n[    1.858450] asoc-simple-card rt5651-sound: rt5651-aif1 <-> ff890000.i2s mapping ok\n[    1.875441] asoc-simple-card hdmi-sound: i2s-hifi <-> ff8a0000.i2s mapping ok\n\nroot@som-rk3399v2:~# dmesg | grep rt5651\n[    1.838498] of\\_get\\_named\\_gpiod\\_flags: parsed 'simple-audio-card,hp-det-gpio' property of node '/rt5651-sound[0]' - status (0)\n[    1.838522] of\\_get\\_named\\_gpiod\\_flags: can't parse 'simple-audio-card,mic-det-gpio' property of node '/rt5651-sound[0]'\n[    1.856077] asoc-simple-card rt5651-sound: asoc: dapm unknown pin headphones\n[    1.858450] asoc-simple-card rt5651-sound: rt5651-aif1 <-> ff890000.i2s mapping ok\n[    1.859230] asoc-simple-card rt5651-sound: asoc: no source widget found for micbias1\n[    1.859959] asoc-simple-card rt5651-sound: asoc: failed to add route micbias1 -> direct -> mic jack\n[    1.861239] rt5651 1-001a: asoc: mux inl1 mux has no paths\n[    1.861783] rt5651 1-001a: asoc: mux inr1 mux has no paths\n[    1.862294] rt5651 1-001a: asoc: mux inl2 mux has no paths\n[    1.862830] rt5651 1-001a: asoc: mux inr2 mux has no paths\n[    1.870625] input: realtek,rt5651-codec headphones as /devices/platform/rt5651-sound/sound/card0/input3\n[    2.006432] asoc-simple-card rt5651-sound: asoc: dapm unknown pin headphones\n[    2.023786]   #0: realtek,rt5651-codec\n\n \n\nroot@som-rk3399v2:~# cat /etc/modules\n<nothing specified>\n\n \n\nroot@som-rk3399v2:~# lsmod | grep snd\n<nothing>\n\n \n\nroot@som-rk3399v2:~# cat /etc/asound.conf\ncat: /etc/asound.conf: no such file or directory\n\n\nroot@som-rk3399v2:~# amixer\nsimple mixer control 'mono adc',0\n  capabilities: cvolume\n  capture channels: front left - front right\n  limits: capture 0 - 127\n  front left: capture 47 [37%] [0.00db]\n  front right: capture 47 [37%] [0.00db]\nsimple mixer control 'mono dac',0\n  capabilities: pvolume\n  playback channels: front left - front right\n  limits: playback 0 - 175\n  mono:\n  front left: playback 170 [97%] [-18.75db]\n  front right: playback 170 [97%] [-18.75db]\nsimple mixer control 'adc',0\n  capabilities: cvolume cswitch\n  capture channels: front left - front right\n  limits: capture 0 - 127\n  front left: capture 47 [37%] [0.00db] [on]\n  front right: capture 47 [37%] [0.00db] [on]\nsimple mixer control 'adc boost gain',0\n  capabilities: volume\n  playback channels: front left - front right\n  capture channels: front left - front right\n  limits: 0 - 3\n  front left: 0 [0%]\n  front right: 0 [0%]\nsimple mixer control 'adc if2 data',0\n  capabilities: enum\n  items: 'normal' 'swap' 'left copy to right' 'right copy to left'\n  item0: 'normal'\nsimple mixer control 'dac if2 data',0\n  capabilities: enum\n  items: 'normal' 'swap' 'left copy to right' 'right copy to left'\n  item0: 'normal'\nsimple mixer control 'dac l2 mux',0\n  capabilities: enum\n  items: 'if1' 'if2'\n  item0: 'if2'\nsimple mixer control 'dac mixl inf1',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [on]\nsimple mixer control 'dac mixl stereo adc',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [off]\nsimple mixer control 'dac mixr inf1',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [on]\nsimple mixer control 'dac mixr stereo adc',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [off]\nsimple mixer control 'dac r2 mux',0\n  capabilities: enum\n  items: 'if1' 'if2'\n  item0: 'if2'\nsimple mixer control 'dac1',0\n  capabilities: pvolume\n  playback channels: front left - front right\n  limits: playback 0 - 175\n  mono:\n  front left: playback 169 [97%] [-22.50db]\n  front right: playback 169 [97%] [-22.50db]\nsimple mixer control 'dac2',0\n  capabilities: pswitch\n  playback channels: front left - front right\n  mono:\n  front left: playback [on]\n  front right: playback [on]\nsimple mixer control 'dd mixl dac l1',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [off]\nsimple mixer control 'dd mixl dac l2',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [off]\nsimple mixer control 'dd mixl dac r2',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [off]\nsimple mixer control 'dd mixr dac l2',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [off]\nsimple mixer control 'dd mixr dac r1',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [off]\nsimple mixer control 'dd mixr dac r2',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [off]\nsimple mixer control 'dmic asrc',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [off]\nsimple mixer control 'hp',0\n  capabilities: pvolume\n  playback channels: front left - front right\n  limits: playback 0 - 39\n  mono:\n  front left: playback 16 [41%] [-22.50db]\n  front right: playback 16 [41%] [-22.50db]\nsimple mixer control 'hpo l',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [on]\nsimple mixer control 'hpo mix dac1',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [off]\nsimple mixer control 'hpo mix hpvol',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [on]\nsimple mixer control 'hpo r',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [on]\nsimple mixer control 'hpovol l',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [on]\nsimple mixer control 'hpovol r',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [on]\nsimple mixer control 'if1 asrc',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [off]\nsimple mixer control 'if2 adc',0\n  capabilities: enum\n  items: 'if1 adc1' 'if1 adc2'\n  item0: 'if1 adc1'\nsimple mixer control 'if2 asrc',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [off]\nsimple mixer control 'in',0\n  capabilities: cvolume\n  capture channels: front left - front right\n  limits: capture 0 - 31\n  front left: capture 23 [74%] [0.00db]\n  front right: capture 23 [74%] [0.00db]\nsimple mixer control 'in1 boost',0\n  capabilities: volume volume-joined\n  playback channels: mono\n  capture channels: mono\n  limits: 0 - 8\n  mono: 0 [0%]\nsimple mixer control 'in2 boost',0\n  capabilities: volume volume-joined\n  playback channels: mono\n  capture channels: mono\n  limits: 0 - 8\n  mono: 2 [25%]\nsimple mixer control 'lout l',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [off]\nsimple mixer control 'lout mix dac l1',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [off]\nsimple mixer control 'lout mix dac r1',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [off]\nsimple mixer control 'lout mix outvol l',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [off]\nsimple mixer control 'lout mix outvol r',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [off]\nsimple mixer control 'lout r',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [off]\nsimple mixer control 'out',0\n  capabilities: pvolume\n  playback channels: front left - front right\n  limits: playback 0 - 39\n  mono:\n  front left: playback 31 [79%] [0.00db]\n  front right: playback 31 [79%] [0.00db]\nsimple mixer control 'out mixl bst1',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [off]\nsimple mixer control 'out mixl bst2',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [off]\nsimple mixer control 'out mixl dac l1',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [on]\nsimple mixer control 'out mixl inl1',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [off]\nsimple mixer control 'out mixl rec mixl',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [off]\nsimple mixer control 'out mixr bst1',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [off]\nsimple mixer control 'out mixr bst2',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [off]\nsimple mixer control 'out mixr dac r1',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [on]\nsimple mixer control 'out mixr inr1',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [off]\nsimple mixer control 'out mixr rec mixr',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [off]\nsimple mixer control 'outvol l',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [off]\nsimple mixer control 'outvol r',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [off]\nsimple mixer control 'pdm l mux',0\n  capabilities: enum\n  items: 'dd mix' 'stereo dac mix'\n  item0: 'dd mix'\nsimple mixer control 'pdm r mux',0\n  capabilities: enum\n  items: 'dd mix' 'stereo dac mix'\n  item0: 'dd mix'\nsimple mixer control 'recmixl bst1',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [off]\nsimple mixer control 'recmixl bst2',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [on]\nsimple mixer control 'recmixl bst3',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [off]\nsimple mixer control 'recmixl inl1',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [off]\nsimple mixer control 'recmixr bst1',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [off]\nsimple mixer control 'recmixr bst2',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [on]\nsimple mixer control 'recmixr bst3',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [off]\nsimple mixer control 'recmixr inr1',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [off]\nsimple mixer control 'rt5651 asrc',0\n  capabilities: enum\n  items: 'disable' 'enable'\n  item0: 'disable'\nsimple mixer control 'stereo dac mixl dac l1',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [on]\nsimple mixer control 'stereo dac mixl dac l2',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [off]\nsimple mixer control 'stereo dac mixl dac r1',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [off]\nsimple mixer control 'stereo dac mixr dac l1',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [off]\nsimple mixer control 'stereo dac mixr dac r1',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [on]\nsimple mixer control 'stereo dac mixr dac r2',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [off]\nsimple mixer control 'stereo1 adc l1 mux',0\n  capabilities: enum\n  items: 'dd mix' 'adc'\n  item0: 'adc'\nsimple mixer control 'stereo1 adc l2 mux',0\n  capabilities: enum\n  items: 'dmic' 'dd mix'\n  item0: 'dd mix'\nsimple mixer control 'stereo1 adc mixl adc1',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [on]\nsimple mixer control 'stereo1 adc mixl adc2',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [off]\nsimple mixer control 'stereo1 adc mixr adc1',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [on]\nsimple mixer control 'stereo1 adc mixr adc2',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [off]\nsimple mixer control 'stereo1 adc r1 mux',0\n  capabilities: enum\n  items: 'dd mix' 'adc'\n  item0: 'adc'\nsimple mixer control 'stereo1 adc r2 mux',0\n  capabilities: enum\n  items: 'dmic' 'dd mix'\n  item0: 'dd mix'\nsimple mixer control 'stereo2 adc l1 mux',0\n  capabilities: enum\n  items: 'dd mixl' 'adcl'\n  item0: 'adcl'\nsimple mixer control 'stereo2 adc l2 mux',0\n  capabilities: enum\n  items: 'dmic l' 'dd mixl'\n  item0: 'dd mixl'\nsimple mixer control 'stereo2 adc mixl adc1',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [off]\nsimple mixer control 'stereo2 adc mixl adc2',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [off]\nsimple mixer control 'stereo2 adc mixr adc1',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [off]\nsimple mixer control 'stereo2 adc mixr adc2',0\n  capabilities: pswitch pswitch-joined\n  playback channels: mono\n  mono: playback [off]\nsimple mixer control 'stereo2 adc r1 mux',0\n  capabilities: enum\n  items: 'dd mixr' 'adcr'\n  item0: 'dd mixr'\nsimple mixer control 'stereo2 adc r2 mux',0\n  capabilities: enum\n  items: 'dmic r' 'dd mixr'\n  item0: 'dmic r'\n\n\nroot@som-rk3399v2:~# cat /sys/kernel/debug/clk/clk\\_i2sout\\_src/clk\\_parent\nclk\\_i2s1\n\n\n \n\n\n  \n \n\n\n i2s clock is indeed i2s1 (mine under armbian is i2s0).\n \n\n\n tried various alsamixer commands (from your link and from others on the forum) without success.\n \n", "name": "", "is_accepted": false }, { "text": "managed to get sound working on 4.4 armbian legacy kernel with stock rk3399-nanopi-m4v2.dtb from linux-dtb-legacy package.\n \n\n\n  \n \n\n\n \n\n% uname -a\n\nlinux miki 4.4.213-rk3399 #1 smp tue apr 6 02:35:05 cdt 2021 aarch64 aarch64 aarch64 gnu/linux\n\n \n\n% dpkg -l | grep -v ^rc | grep -e \"linux-dtb-legacy|linux-image-legacy\"\n\nii  linux-dtb-legacy-rk3399                 21.05.0-trunk                        arm64        linux dtb, version 4.4.213-rk3399\nii  linux-image-legacy-rk3399            21.05.0-trunk                        arm64        linux kernel, version 4.4.213-rk3399\n\n \n\n% aplay -l\n**** list of playback hardware devices ****\nxcb\\_connection\\_has\\_error() returned true\ncard 0: dummy [dummy], device 0: dummy pcm [dummy pcm]\n  subdevices: 8/8\n  subdevice #0: subdevice #0\n  subdevice #1: subdevice #1\n  subdevice #2: subdevice #2\n  subdevice #3: subdevice #3\n  subdevice #4: subdevice #4\n  subdevice #5: subdevice #5\n  subdevice #6: subdevice #6\n  subdevice #7: subdevice #7\ncard 1: loopback [loopback], device 0: loopback pcm [loopback pcm]\n  subdevices: 8/8\n  subdevice #0: subdevice #0\n  subdevice #1: subdevice #1\n  subdevice #2: subdevice #2\n  subdevice #3: subdevice #3\n  subdevice #4: subdevice #4\n  subdevice #5: subdevice #5\n  subdevice #6: subdevice #6\n  subdevice #7: subdevice #7\ncard 1: loopback [loopback], device 1: loopback pcm [loopback pcm]\n  subdevices: 8/8\n  subdevice #0: subdevice #0\n  subdevice #1: subdevice #1\n  subdevice #2: subdevice #2\n  subdevice #3: subdevice #3\n  subdevice #4: subdevice #4\n  subdevice #5: subdevice #5\n  subdevice #6: subdevice #6\n  subdevice #7: subdevice #7\ncard 2: realtekrt5651co [realtek,rt5651-codec], device 0: ff890000.i2s-rt5651-aif1 rt5651-aif1-0 [ff890000.i2s-rt5651-aif1 rt5651-aif1-0]\n  subdevices: 1/1\n  subdevice #0: subdevice #0\ncard 3: rockchiphdmi [rockchip,hdmi], device 0: ff8a0000.i2s-i2s-hifi i2s-hifi-0 [ff8a0000.i2s-i2s-hifi i2s-hifi-0]\n  subdevices: 1/1\n  subdevice #0: subdevice #0\n\n \n\n% cat /etc/asound.conf\npcm.!default {\n    type hw\n    card 2\n    device 0\n}\n\nctl.!default {\n    type hw\n    card 2\n}\n\n \n\n% cat /sys/kernel/debug/clk/clk\\_i2sout\\_src/clk\\_parent\n\nclk\\_i2s1\n\n\n \n", "name": "", "is_accepted": false }, { "text": "there appears to be a lot of good looking information in this post, though do have some questions on what you did, while i'm unpacking everything in this post ...\n \n\n\n  \n \n\n\n\n\n  \n \n\n\n your post references \"rk3399-som-rk3399v2\", but the armbian default u-boot setup uses \"rk3399-nanopi-m4v2\". there's also a number of duplicate sections. your \"rt5651\\_card:  \" already exists on the armbian dts as \"/rt5651-sound\" and shouldn't need to be added. i'm curious what file you started with, and a little puzzled what needs to be fixed in the existing builds.\n \n\n\n  \n \n\n\n also your edits appear to edit the top level rk3399 dts, where i'm uncertain whether those changes are appropriate to all boards that use it.\n \n", "name": "", "is_accepted": false }, { "text": "https://github.com/armbian/build/blob/master/patch/kernel/archive/rockchip64-5.11/rk3399-add-sclk-i2sout-src-clock.patch\n \n\n\n  \n \n\n\n so i dont know wich  distro he is using but he just could copy the patches from armbian\n \n\n\n  \n \n\n\n ony thig he had to do is choose a dtb or adjust it nothing more\n \n\n\n  \n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "i not sure about this. on nanopc-t4 (which also equipped with rt5651) there is same issue, which same errors messages in dmesg. so maybe something else (besides rk3399-add-sclk-i2sout-src-clock.patch) is missing in armbian?\n \n\n\n  \n \n\n\n actually, can you check if 3.5mm jack output works for you on rk3399 boards with rt5651?\n \n", "name": "", "is_accepted": false }, { "text": "i use since long time pure mainline kernel for rt5651 support. the kernel hack that armbian is still applying is not really required. if you like, i can upload a kernel for a quick test to see if it is also working for you. or even easier, try this image for your nanopc-t4, it should already have everything in place.\n \n", "name": "", "is_accepted": false }, { "text": "i was using linux 5.11 vanilla dts (from torvalds' github) for nanopi m4v2 and using that as base for my custom dts without overlays. \n also u-boot was built (and patched) by me - learning new things and so on \n my idea was to share my experience in hope if someone decided to do something similar, but this is armbian forum where people are using armbian stuff without compiling their own so...\n \n\n\n  \n \n\n\n now i have reinstalled fresh armbian for nanopc t4 (u-boot, kernel and ramdisk are on sd card, rootfs is on nvme but it shouldn't matter).\n \n\n\n image i dd-ed to sd card (from 12.06.2021.): https://mirrors.netix.net/armbian/dl/nanopct4/archive/armbian\\_21.05.1\\_nanopct4\\_focal\\_current\\_5.10.35\\_xfce\\_desktop.img.xz \n nvme doesn't work in u-boot (works in linux) for my board but that's another topic\n \n\n\n  \n \n\n\n i am using armbian u-boot with /boot/dtb/rockchip/rk3399-nanopc-t4.dtb. \n after dts overlay i have sound on my som-rk3399v2 (which should be pretty similar to t4).\n \n\n\n  \n \n\n\n \n# dmesg | grep rt5651\n[    5.727048] rt5651 1-001a: failed to reguest irq 0: -22\n\n \n\n# uname -a\nlinux miki 5.10.35-rockchip64 #21.05.1 smp preempt fri may 7 13:53:11 utc 2021 aarch64 aarch64 aarch64 gnu/linux\n\n \n\n# grep -e  \"snd\\_soc\\_rockchip\\_i2s|snd\\_soc\\_rt5651\" /boot/config-5*\nconfig\\_snd\\_soc\\_rockchip\\_i2s=m\nconfig\\_snd\\_soc\\_rockchip\\_i2s\\_tdm=m\nconfig\\_snd\\_soc\\_rt5651=m\n\n \n\n# i2cdetect -y 1\n     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f\n00:          -- -- -- -- -- -- -- -- -- -- -- -- --\n10: -- -- -- -- -- -- -- -- -- -- uu -- -- -- -- --\n20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --\n30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --\n40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --\n50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --\n60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --\n70: -- -- -- -- -- -- -- --\n\n \n\n# cat /etc/modules\n<empty>\n\n \n\n# lsmod | grep snd\nsnd\\_soc\\_hdmi\\_codec     20480  1\nsnd\\_soc\\_simple\\_card    24576  3\nsnd\\_soc\\_simple\\_card\\_utils    28672  1 snd\\_soc\\_simple\\_card\nsnd\\_soc\\_rt5651         98304  1\nsnd\\_soc\\_rl6231         20480  1 snd\\_soc\\_rt5651\nsnd\\_soc\\_rockchip\\_spdif    16384  0\nsnd\\_soc\\_rockchip\\_i2s    24576  4\nsnd\\_soc\\_core          237568  6 snd\\_soc\\_rt5651,snd\\_soc\\_hdmi\\_codec,snd\\_soc\\_rockchip\\_spdif,snd\\_soc\\_simple\\_card\\_utils,snd\\_soc\\_rockchip\\_i2s,snd\\_soc\\_simple\\_card\nsnd\\_pcm\\_dmaengine      20480  1 snd\\_soc\\_core\nsnd\\_pcm               118784  4 snd\\_soc\\_rt5651,snd\\_soc\\_hdmi\\_codec,snd\\_soc\\_core,snd\\_pcm\\_dmaengine\nsnd\\_timer              40960  1 snd\\_pcm\nsnd                    90112  10 snd\\_soc\\_hdmi\\_codec,snd\\_timer,snd\\_soc\\_core,snd\\_pcm\nsoundcore              16384  1 snd\n\n \n\n# aplay -l\n**** list of playback hardware devices ****\ninvalid mit-magic-cookie-1 keyxcb\\_connection\\_has\\_error() returned true\ncard 0: realtekrt5651co [realtek,rt5651-codec], device 0: ff890000.i2s-rt5651-aif1 rt5651-aif1-0 [ff890000.i2s-rt5651-aif1 rt5651-aif1-0]\n  subdevices: 1/1\n  subdevice #0: subdevice #0\ncard 1: hdmisound [hdmi-sound], device 0: ff8a0000.i2s-i2s-hifi i2s-hifi-0 [ff8a0000.i2s-i2s-hifi i2s-hifi-0]\n  subdevices: 1/1\n  subdevice #0: subdevice #0\n\n \n\n# cat /etc/asound.conf\n<empty>\n\n \n\n# cat /proc/asound/pcm\n00-00: ff890000.i2s-rt5651-aif1 rt5651-aif1-0 : ff890000.i2s-rt5651-aif1 rt5651-aif1-0 : playback 1 : capture 1\n01-00: ff8a0000.i2s-i2s-hifi i2s-hifi-0 : ff8a0000.i2s-i2s-hifi i2s-hifi-0 : playback 1\n\n# cat /sys/kernel/debug/clk/clk\\_i2sout\\_src/clk\\_parent\nclk\\_i2s1\n\n \n\n# dpkg -l | grep -v ^rc | grep -e \"linux-dtb-|linux-image-\"\nii  linux-dtb-current-rockchip64          21.05.1                              arm64        linux dtb, version 5.10.35-rockchip64\nii  linux-image-current-rockchip64        21.05.1                              arm64        linux kernel, version 5.10.35-rockchip64\n\n \n\n# grep -ie \"name|linux|version\" /etc/armbian-release\nboard\\_name=\"nanopc t4\"\ndistribution\\_codename=focal\nversion=21.05.2\nlinuxfamily=rockchip64\n\n \n\n\n  \n \n\n\n i still have these messages in syslog but sound works nonetheless: \n \njun 13 21:28:31 miki kernel: [   28.822975] rockchip-i2s ff8a0000.i2s: fail to set mclk -22\njun 13 21:28:31 miki kernel: [   28.823485] rockchip-i2s ff8a0000.i2s: asoc: error at snd\\_soc\\_dai\\_set\\_sysclk on ff8a0000.i2s: -22\njun 13 21:39:50 miki kernel: [  708.376058] rockchip-i2s ff890000.i2s: fail to set mclk -22\njun 13 21:39:50 miki kernel: [  708.376576] rockchip-i2s ff890000.i2s: asoc: error at snd\\_soc\\_dai\\_set\\_sysclk on ff890000.i2s: -22\n\n \n\n\n  \n \n\n\n this is overlay which i have used: \n \n#include <dt-bindings/pinctrl/rockchip.h>\n#include <dt-bindings/gpio/gpio.h>\n#include <dt-bindings/clock/rk3399-cru.h>\n\n/dts-v1/;\n/plugin/;\n\n/ {\n    compatible = \"rockchip,rk3399\";\n\n    fragment@0 {\n        target = <&rt5651>;\n        \\_\\_overlay\\_\\_ {\n            status = \"okay\";\n        };\n    };\n\n    fragment@1 {\n        target = <&i2s1>;\n        \\_\\_overlay\\_\\_ {\n            assigned-clocks = <&cru sclk\\_i2sout\\_src>;\n            assigned-clock-parents = <&cru sclk\\_i2s1\\_8ch>;\n            pinctrl-0 = <&i2s\\_8ch\\_mclk>,<&i2s1\\_2ch\\_bus>;\n            status = \"okay\";\n        };\n    };\n\n    fragment@2 {\n        target = <&pinctrl>;\n        \\_\\_overlay\\_\\_ {\n            i2s1 {\n                i2s\\_8ch\\_mclk: i2s-8ch-mclk {\n                    // gpio4\\_a0 - rk3399 i2s\\_clk\n                    rockchip,pins = <4 rk\\_pa0 1 &pcfg\\_pull\\_none>;\n                };\n            };\n\n            headphone {\n                hp\\_det: hp-det {\n                    // gpio4\\_d4 - hp\\_det\\_h pin on som-rk3399v2\n                    rockchip,pins = <4 rk\\_pd4 rk\\_func\\_gpio &pcfg\\_pull\\_up>;\n                };\n            };\n        };\n    };\n};\n\n \n", "name": "", "is_accepted": false }, { "text": "unfortunately, this image does not load on my t4, get stuck here.\n \n", "name": "", "is_accepted": false }, { "text": "looks like the clocking set up by uboot for hdmi is not suitable for setting up the native video mode that the monitor wants to set through the kernel. either drop in an uboot without hdmi support and lose the uboot display support or set up a native hdmi mode for linux. it is known that manline rockchip is limited in selecting video modes, only native hdmi modes are suported for sure. there are several patches floating around to enable more modes for a particular clocking, but nothing finaly decided.\n \n", "name": "", "is_accepted": false } ]

[ { "text": "ahem.  it veeeeeerrrrks!  \n \n\n\n  \n \n\n\n in the end, i had to dd the u-boot into place (i got the location from sunxi wiki):\n \n\n\n  \n \n\n\n# dd if=u-boot-sunxi-with-spl.bin of=/dev/mmcblk1 bs=1024 seek=8\n\n\n  \n \n\n\n i got the file from https://apt.armbian.com/pool/main/l/linux-u-boot-cubietruck-current/ (of course, if you are reading later, yours may be different).\n \n\n\n  \n \n\n\n the advice here was very helpful.  but i still would have never got there without a little help in irc.\n \n\n\n  \n \n\n\n special thanks to @igor, @lanefu, @tonymac32, and @archetech, who all helped me in one way or another.  cheers (i am actually having a cold one right now)!  \n \n", "name": "", "is_accepted": true }, { "text": "@trs-80\n \n\n\n  \n \n\n\n can you post the ls -la of /boot and contents of /boot/boot.cmd\n \n\n\n  \n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "i just noticed that mkimage command at the bottom.  do i need to run that?\n \n", "name": "", "is_accepted": false }, { "text": "@lanefu,\n \n\n\n  \n \n\n\n ok, so that recent test image booted!\n \n\n\n  \n \n\n\n what now?\n \n", "name": "", "is_accepted": false }, { "text": "someone recently reworked our outdated troubleshooting guide. check if it helps for quick restoration: https://docs.armbian.com/user-guide\\_advanced-features/\n \n", "name": "", "is_accepted": false }, { "text": "thanks for the pointer, igor, i had not seen that before.\n \n\n\n  \n \n\n\n i am reading how to unbrick the system (section at the provided link) and the first paragraph states:\n \n\n\n  \n \n\n\n\n\n  \n \n\n\n however, the list of (4) packages provided shortly thereafter does not actually appear to contain the u-boot:\n \n\n\n  \n \n\n\n\n\n  \n \n\n\n out of those 4 packages, i understand kernel, dtb, and firmware, but what is 'root'?\n \n\n\n  \n \n\n\n further, looking in https://apt.armbian.com/pool/main/l/ i see a lot of linux-u-boot-* packages.\n \n\n\n  \n \n\n\n sorry if these are dumb questions, i'm really out of my depth here and just don't want to go flashing random stuff without understanding.  i will be happy to update the docs (if appropriate) once i actually understand what is going on here.\n \n\n\n  \n \n\n\n particularly as further diagnosis (late last night) seemed to indicate that my u-boot might be the problem.  i was able to boot a more recent image on a different sd card.  in fact tony was suggesting i grab a newer u-boot and dd it onto the old card (following instruction here).\n \n\n\n  \n \n\n\n which of course leaves the issue of how it got like that in the first place (sd card corruption, starting to wear out, etc.).  but first things first.\n \n\n\n  \n \n\n\n so i guess in the meantime i will at least do the filesystem check as outlined here.\n \n", "name": "", "is_accepted": false }, { "text": "ok, i did the file system check.\n \n\n\n  \n \n\n\n i tried many combinations:\n \n\n\n  \n \n\n\n$ sudo fsck /dev/mmcblk1 -f\n$ sudo fsck /dev/mmcblk1 -f -b 8193\n$ sudo fsck /dev/mmcblk1 -f -b 32768\n$ sudo e2fsck -b 8193 /dev/mmcblk1\n$ sudo e2fsck -b 32768 /dev/mmcblk1\n\n\n  \n \n\n\n they all return the same result:\n \n\n\n  \n \n\n\nfsck from util-linux 2.33.1\ne2fsck 1.44.5 (15-dec-2018)\nfsck.ext2: bad magic number in super-block while trying to open /dev/mmcblk1\n\nthe superblock could not be read or does not describe a valid ext2/ext3/ext4\nfilesystem. if the device is valid and it really contains an ext2/ext3/ext4\nfilesystem (and not swap or ufs or something else), then the superblock\nis corrupt, and you might try running e2fsck with an alternate superblock:\n e2fsck -b 8193 <device>\n or\n e2fsck -b 32768 <device>\n\nfound a dos partition table in /dev/mmcblk1\n\n\n  \n \n\n\n what does it mean?  corrupted or bad sd card?  or just that i borked something somewhere along the way?\n \n\n\n  \n \n\n\n it's a 64gb samsung evo from known good source (b&h photo & video), which i did thorough test (according to armbian recommended method) when it was new, however otoh it is few years old now, been in service the whole time...\n \n\n\n  \n \n\n\n besides that, someone in irc (+rneese) answered my question from above.  the 'root' package is apparently the root filesystem?  if that is true, then my assumption from above that those instructions do not actually replace u-boot is correct?  i think this is relevant, as i suspect i need to replace u-boot.\n \n\n\n  \n \n\n\n i know, i know.  sd card.  however i am not convinced that is the problem.  unless above (fsck results) clearly shows that without a doubt (i am not sure)?  because everything was fine until i tried to upgrade my kernel through armbian-config.  i still think that i need to \"surgically replace u-boot\" as tony so succinctly put it in irc.  but i welcome feedback from anyone with more experience.\n \n", "name": "", "is_accepted": false }, { "text": "a couple things to follow up.\n \n\n\n  \n \n\n\n first, there was still something we were speculating about in irc: does armbian upgrade u-boot some times upon upgrades?  some thought maybe yes.  but i would not even know where to look for such information.\n \n\n\n  \n \n\n\n also, i am still a little worried about the results of fsck from above.  i'm too tired right now, but i think tomorrow i will try it again, now that i have a working u-boot, just to see if i get same error.  as i have nagging worry in the back of my mind still about sd card.\n \n", "name": "", "is_accepted": false }, { "text": "it only upgrade package that is containing u-boot but flashing must be done via armbian-config or manually. as you did. i think this part of the information is missing in the manual.\n \n", "name": "", "is_accepted": false }, { "text": "you referenced the raw device by \"/dev/mmcblk1\" where mbr , u-boot and partitions reside. \n you need to reference a partition by \"/dev/mmcblk1px\" where a suitable filesystem resides. \n replace \"x\" with the number of the partition you want to check.\n \n", "name": "", "is_accepted": false } ]

[ { "text": "another option is to boot images from archive.\n \n", "name": "", "is_accepted": true }, { "text": "regression in u-boot. will be fixed in sources when this https://github.com/armbian/build/pull/3036 is merged. images and updates are going to be updated soon. if you need faster.\n \n", "name": "", "is_accepted": false } ]

[ { "text": "userland (apt, packages, etc.) is all debian (or ubuntu, depending on what you install).  armbian is focused on low level stuff particular to these little boards (boot, kernel, dtb, firmware, etc.).\n \n\n\n  \n \n\n\n so, i imagine you would have to petition some debian maintainer, or the ksmbd project directly?\n \n\n\n  \n \n\n\n i am debian user, but still not to the point of packaging, yet.  i suppose it's only a matter of time...  but i digress.\n \n\n\n  \n \n\n\n anyway, that might take a while.  in the meantime you could build it yourself, looks like...\n \n", "name": "", "is_accepted": true }, { "text": "hmm i thought there were specific armbian packages. ok then.\n \n", "name": "", "is_accepted": false }, { "text": "@mangix,\n \n\n\n  \n \n\n\n there are a few, like armbian particular tools for instance:\n \n\n\n  \n \n\n\n┌─[ 2020-11-27 13:16 trs-80@cubietruck:~ ]\n└─▶ $ dpkg-query -l '*armbian*'\n\ndesired=unknown/install/remove/purge/hold\n| status=not/inst/conf-files/unpacked/half-conf/half-inst/trig-await/trig-pend\n|/ err?=(none)/reinst-required (status,err: uppercase=bad)\n||/ name version architecture description\n+++-=====================-============-============-=================================\nun armbian-bsp <none> <none> (no description available)\nii armbian-config 20.08.22 all armbian configuration utility\nii armbian-firmware 20.08.22 all linux firmware\nun armbian-firmware-full <none> <none> (no description available)\nun armbian-hostapd <none> <none> (no description available)\nun armbian-tools <none> <none> (no description available)\nun armbian-tools-buster <none> <none> (no description available)\nii armbian-tools-jessie 5.60 armhf armbian tools, cubie bt utils\nun armbian-u-boot <none> <none> (no description available)\n\n\n\n  \n \n\n\n also i noticed, while poking around in armbian repositories it seems we package our (hardware specific) kernels, u-boot, and some other things as debian packages.  which i think is a quite good idea, although i could see how it might lead to some confusion as in the case of your op. \n \n\n\n  \n \n\n\n but other than those few things above which are particular to hardware or the armbian project itself, all the other packages are just straight from vanilla debian (or ubuntu) repos.  which to me is one of the great strengths of armbian.\n \n", "name": "", "is_accepted": false } ]

[ { "text": "@user-2020-12-7,\n \n\n\n  \n \n\n\n to be honest this has been bothering me ever since your op.  fwiw i had put this in my own personal issue tracker to follow up on until now.\n \n\n\n  \n \n\n\n so when some discussion came up today in irc about this, and another user confirm that it's working again (i specifically ask him about screen), it made me think about this again.\n \n\n\n  \n \n\n\n i know it's stated in other thread you linked already, but apparently there was some issue with newer kernel, and therefore pinebook a64 was rolled back to legacy (5.4.y) in the meantime, which works well enough apparently.  as i am sure you are aware by now.\n \n\n\n  \n \n\n\n however i realize your op was more about the term \"supported\" on the download page.  i think misunderstanding may have come from not understanding what \"supported\" means in terms of armbian, so i will try to expand a bit on what has already been written at that link.\n \n\n\n  \n \n\n\n supported is a more general and longer term condition, based on a lot of factors mentioned in linked article above.  and so, just because something breaks (even something so important as display on a laptop) does not mean that device suddenly becomes \"not supported.\"  if situation were impossible, or constant breakage, etc. then that would be a different story.\n \n\n\n  \n \n\n\n so i hope i help clear that up a bit and again i thank you for your concern and your report.  cheers!\n \n\n\n  \n \n\n\n i am taking the liberty to mark my own post as solution in this case.\n \n\n\n  \n \n\n\n  \n \n", "name": "", "is_accepted": true }, { "text": "i appreciate your effort in bringing this to our attention.\n \n\n\n  \n \n\n\n however (speaking generally here), problem is often times not that we are unaware, but rather there are not enough resources available to solve all problems all the time right away.  overall i think we do pretty well, considering what we have to work with.\n \n\n\n  \n \n\n\n personally, i don't know specifics on pinebook well enough to know whether your option a or b would be more appropriate.  i just try and help out around forums to try and take some pressure off devs so they can focus on other things (development).\n \n\n\n  \n \n\n\n i guess we have to wait for someone with specific knowledge.  unless in the meantime you feel up for taking your involvement to next level, which of course would be even more greatly appreciated!  \n \n", "name": "", "is_accepted": false } ]

[ { "text": "https://github.com/armbian/build/pull/2377 tested to fix the issue.\n \n", "name": "", "is_accepted": true }, { "text": "small update:\n \n\n\n  \n \n\n\n going back to armbian 20.08.17 buster with linux 5.4.62-sunxi64 \"solves\" the problem.\n \n\n\n http://ix.io/2eyt\n \n\n\n can anyone confirm this behavior?\n \n\n\n  \n \n\n\n daniel\n \n", "name": "", "is_accepted": false }, { "text": "i didn't checked yet, but i read on openhab forum that their zram implementation is failing. on rpi. which makes me believe the problem comes from the upstream.\n \n", "name": "", "is_accepted": false }, { "text": "could you try to switch the zram algorithm to zstd to try out?\n \n\n\n  \n \n\n\n this seems to be fixing issue when i try to port armbian to pinecube.\n \n", "name": "", "is_accepted": false }, { "text": "thanks for the info, is there any work around?\n \n\n\n  \n \n\n\n switching to zstd caused the same error and crashed the board while benchmarking. after a reboot: http://ix.io/2f3t  - interestingly it says:\n \n\n\n ### activated 1 lzo-rle zram swap devices with 491 mb each\n \n\n\n  \n \n\n\n while\n \n\n\n root@orangepizero:~# zramctl\n \n\n\n name       algorithm disksize  data  compr total streams mountpoint\n \n\n\n /dev/zram1 zstd        491,6m    4k    58b    4k       4 [swap]\n \n\n\n /dev/zram0 zstd           50m  1,4m 184,1k  572k       4 /var/log\n \n\n\n  \n \n\n\n daniel\n \n", "name": "", "is_accepted": false }, { "text": "@igorseems to be https://lore.kernel.org/linux-mm/[email protected]/ .\n \n\n\n  \n \n\n\n by the way in mainline kernel the \"fix\" seems to be dropping zsmalloc\\_pgtable\\_mapping , see https://www.spinics.net/lists/stable/msg428110.html (it's already in linux-next).\n \n", "name": "", "is_accepted": false }, { "text": "awesome guys, when will the change be in the current build?\n \n\n\n  \n \n\n\n out of curiosity: what is “zsmalloc\\_pgtable\\_mapping“ actually doing?\n \n", "name": "", "is_accepted": false } ]

[ { "text": "i think your assessment of that page is pretty spot on.  i started working on improving the docs recently, so i will add this to the list.\n \n\n\n  \n \n\n\n i could swear i read this somewhere before, but i will try and give a brief summary (and if nothing else, use it as genesis for improving docs):\n \n\n\n  \n \n\n\n legacy is the kernel that comes from the mfr at the time the board is released.  some times it can include certain drivers (particularly multimedia) that can make it better for certain use-cases (i.e., desktop).  some times, with passage of time, the kernel gets older and older for various reason (some times not receiveing good ongoing support from the mfr, poor documentation so community can not write f/loss drivers (and thus get them into mainline kernel), etc.).\n \n\n\n  \n \n\n\n current is based on current mainline kernel, and therefore includes whatever is supported in mainline.  this is best for long term support, and things which have good f/loss drivers (or even good docs from mfr) will often end up well supported here for a long time.  however until all that is working well there is some period of time where you might be better off on legacy (and particularly for certain use-cases).\n \n\n\n  \n \n\n\n which is better for someone's needs?  hopefully you can appreciate it's not such a clear cut decision.  it also varies per board and over time.  hopefully that was at least a little bit helpful, i will work on polishing that up and getting it back into the docs.\n \n\n\n  \n \n\n\n whatever is on the download page for a particular device is the currently recommended kernel to use.  this is periodically re-evaluated, but basically it is the current consensus of developers what to recommend at this time.  and so, this is why werner is recommending that one.  if they are not recommending 5.x current, there is probably some reason for that.  but you would have to go digging through some threads to find out why (fwiw, i also have an odroid-xu4 and i am not even sure the full reasoning).  having said that, maybe you try 5.x and it works great for you.  if so, please report back your findings.  make sure and back up any important data (as always).\n \n\n\n  \n \n\n\n these single board computers (sbcs) are quite a niche (and complicated) area within the broader gnu/linux community, and a lot of what is done here at armbian is quite cutting edge.  i really do not think you will find better support (for sbcs, at least) within the broader community.  fact is, without armbian, we would actually even be much worse off (if you can believe that).  i don't think it will probably ever be anything like a macos sort of experience, but i agree some things could surely stand improvement.  which is why (personally) i try and contribute what and where i can.  because i really enjoy these little devices.  there is no company, no business model, no nothing behind armbian.  just a handful of interested hackers and frens spread all over the world.  i'm actually amazed some times we accomplish what we already do on such limited resources.  but that is the reality (to keep things in perspective).\n \n", "name": "", "is_accepted": true }, { "text": "i think wireguard kernel modules were not included until 5.6.  prior to that you have to use dkms (wireguard-dkms package in debian) which might be pulled in if you install wireguard itself.  if you are on buster, you should install from backports repository.\n \n", "name": "", "is_accepted": false }, { "text": "https://github.com/armbian/build/blob/faedda310275334d4fe9b84ef50f99a5480f4910/config/kernel/linux-odroidxu4-legacy.config#l1858\n \n\n\n \r\ncode {\r\n font-family: consolas,\"courier new\";\r\n color: crimson;\r\n background-color: rgba(0, 0, 0, 0.2);\r\n padding: 2px;\r\n font-size: 105%;\r\n} \n config\\_tun is there. you dont need to upgrade to 5.4 or later. just get the latest 4.14 and you should be good to go.\n \n", "name": "", "is_accepted": false }, { "text": "my comment was in general about debian, as i am long time wireguard user and dealt with these problems before.  but op also did not state how he installed (softy? tailscale?) and i think armbian includes some extra things already nowadays on top of vanilla kernel modules.  so perhaps werner answer is more relevant.  or maybe we need some more information from op, or maybe i am just misunderstanding.\n \n", "name": "", "is_accepted": false }, { "text": "i should add that it was working. then i ran an update & upgrade from armbian-config and after that i couldn't boot. so i restored from a backup and i think that is when the issue started.\n \n\n\n  \n \n\n\n now i am unsure how to proceed. @werner are you saying i should use armbian-config to change to 4.14.202?\n \n", "name": "", "is_accepted": false }, { "text": "yeah. however i still wonder if 187 is that old because if you check blame this has been added two years ago...\n \n\n\n https://github.com/armbian/build/blame/faedda310275334d4fe9b84ef50f99a5480f4910/config/kernel/linux-odroidxu4-legacy.config#l1858\n \n\n\n  \n \n\n\n if you are unsure make a full backup of your system beforehand.\n \n", "name": "", "is_accepted": false }, { "text": "to be honest werner, i'm not sure what that shows.\n \n", "name": "", "is_accepted": false }, { "text": "this shows the default legacy kernel configuration used for the xu4 which is 4.14.x at the moment.\n \n\n\n blame does not only allow to see who modified a file at a specific date but also allows to do that for each and every single line in a file. that is why i can now tell that\n \r\ncode {\r\n font-family: consolas,\"courier new\";\r\n color: crimson;\r\n background-color: rgba(0, 0, 0, 0.2);\r\n padding: 2px;\r\n font-size: 105%;\r\n} \n config\\_tun has not recently modified but two years ago from igor. so this must have been there for quite some time now and it is hard to believe that your kernel is that old that it does not include it yet.\n \n", "name": "", "is_accepted": false }, { "text": "i only set up this server during june this year. i am pretty sure i used armbian\\_5.83\\_odroidxu4\\_ubuntu\\_bionic\\_next\\_4.14.111 which means i should have config-tun.\n \n\n\n so something has happened between the bad upgrade and the restore.  \n i just restored my sd card, yet the system os is residing on my data drive. is there a way i can restore the kernel configuration?\n \n", "name": "", "is_accepted": false }, { "text": "then i have no idea where you dug out this old image. armbian has new versioning since november '19...\n \n", "name": "", "is_accepted": false }, { "text": "yes, i wonder...\n \n\n\n the two most prominently displayed images on the download page are 4.14\n \n\n\n you have to scroll further down to find others with more recent kernels.\n \n\n\n can i upgrade the os on my sata drive without overwriting current configuration and user files?\n \n\n ", "name": "", "is_accepted": false }, { "text": "@j\\_\\_\\_r on the page for the hc1 is written that it is a down-stripped version of the odroid xu4, so you can check the download-directory of the xu4:\n \n\n\n https://uk.mirrors.fossho.st/armbian/dl/odroidxu4/archive/\n \n\n\n  \n \n\n\n but i think you cant upgrade this via armbian-config from 4.1.4 to kernel 5.4.x \n \n", "name": "", "is_accepted": false }, { "text": "it is not recommended either since 4.14.x is running more stable.\n \n\n\n if you run\n \r\ncode {\r\n font-family: consolas,\"courier new\";\r\n color: crimson;\r\n background-color: rgba(0, 0, 0, 0.2);\r\n padding: 2px;\r\n font-size: 105%;\r\n} \n armbian-config which kernels can you choose from? btw. did you do a causal\n \r\ncode {\r\n font-family: consolas,\"courier new\";\r\n color: crimson;\r\n background-color: rgba(0, 0, 0, 0.2);\r\n padding: 2px;\r\n font-size: 105%;\r\n} \n apt update && apt upgrade recently?\n \n", "name": "", "is_accepted": false }, { "text": "not sure what you mean by causal? \n \n\n\n i did a firmware upgrade via armbian-config and couldn't boot afterward. that was why i restored the sd card from a backup. it seems like the fstab file had been changed in the upgrade.\n \n", "name": "", "is_accepted": false }, { "text": "this is not good news.\n \n\n\n\n\n yes, i knew this. they should probably all be bundled together for this reason. having said that, like the hc1 downloads page the two most prominent downloads for the xu4 as show on the page are both for the 4.14 kernel. see the note *kernel 5.4 is still considered experimental.\n \n\n\n if it is so old why is it being presented as the main option?\n \n\n\n perhaps i should've gone with a ubuntu image direct from hardkernel?\n \n\n ", "name": "", "is_accepted": false }, { "text": "there are a few additional 4.14 variants not visible in the screenshot\n \n\n\n  \n \n\n ", "name": "", "is_accepted": false }, { "text": "i suggest do choose the most recent 4.14 kernel, 202 to say.\n \n\n\n even though these kernel switches are usually safe it is always good practice to create a backup of your current configuration (simply create an image of your sd card via\n \r\ncode {\r\n font-family: consolas,\"courier new\";\r\n color: crimson;\r\n background-color: rgba(0, 0, 0, 0.2);\r\n padding: 2px;\r\n font-size: 105%;\r\n} \n dd)\n \n", "name": "", "is_accepted": false }, { "text": "so it is true there is no upgrade path beyond 4.14?\n \n\n\n is this true with all types of linux distributions?\n \n\n\n my studies will end soon for summer. perhaps i am best to start over with ubuntu or something very mainstream?\n \n", "name": "", "is_accepted": false }, { "text": "i think you might not be understanding difference between legacy and current (and dev).  unfortunately only link i could quickly find was here and it's not what i was expecting (and i think about writing something better).  it seems to me this has been addressed better somewhere, but i can't seem to put my finger on it at the moment.\n \n\n\n  \n \n\n\n also not sure what you mean by \"start over with ubuntu or something very mainstream\" as that could be interpreted couple different ways?\n \n\n\n  \n \n\n\n there are some particulars of these little boards that need to be learned, this ecosystem is not exactly the same as x86 gnu/linux.  however it is worth it imo, for the benefits one gets in return (small. low power, inexpensive, etc.).\n \n", "name": "", "is_accepted": false }, { "text": "i do find it not very clear. that page you linked to for example describes current as 'fully supported', but then states that kernel support is dependent on the board family - fair enough, this is a resourcing issue and completely understandable.  it then recommends to use a legacy kernel if there are problems - so are legacy kernel images more or less supported than current?\n \n\n\n it then goes on to say - confusingly in my opinion - that testing images are, somehow, simultaneously, 'made from stable branches' but also 'not very well tested'.\n \n\n\n  \n \n\n\n i guess what i desire is to be on a stable version but to also have the ability to upgrade to a more recent version when that newer version has matured and is considered suitable for non-testing, non-experimental machines.  this is what i am used to i suppose in the macos environment. i am not interested in the bleeding edge at all but i am now in a situation where a software service that i was using is now - for reasons i don't understand - no longer working, and it seem i have no path to  upgrade to a more modern kernel version to try and get that software service working again. \n i started out with a legacy kernel, because i wanted stability (see my posts above about the prominence on the download pages of the images with the 4.14 kernel. but now i find myself in a bind because of this decision with werner seeming to imply that i had made a bad decision in one post by saying \n \n\n\n\n\n  \n \n\n\n and then a few posts later saying (about upgrading to the newer version).\n \n\n\n\n\n  \n \n\n\n  \n \n\n\n by starting over with ubuntu i thought might get me that ability, backed by a larger community, wouldn't see me having to deal with these issues.\n \n\n\n i think also that for non-professional users such as myself the linux realm suffers from not having a clearly defined path to knowledge. there is a lot of assumed knowledge among those who deal with this stuff everyday which is natural in any niche industry but it does make it difficult for others.\n \n\n\n  \n \n\n\n  \n \n\n\n  \n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "thanks for your response and explanation.\n \n\n\n i performed the backup and upgraded the kernel to 4.14.202 and it has gone smoothly.\n \n\n\n and, tailscale is back to it's happy self again.\n \n\n\n  \n \n\n\n i really enjoy these little devices too, so i will continue to try and learn more and more about them and linux but sometimes it seems bottomless. \n i appreciate the efforts of the contributors.\n \n\n\n  \n \n\n\n jon\n \n\n\n  \n \n\n ", "name": "", "is_accepted": false }, { "text": "thanks for reporting back.  i'm glad to hear it worked out!\n \n\n\n  \n \n\n\n to whatever extent you are able/willing, please consider helping out.  armbian is just us, mate.\n \n\n\n  \n \n\n\n cheers!\n \n\n\n  \n \n\n\n edit: because title of op was about kernel education, i took the liberty to mark my own answer as the solution, instead of one right above this, as thread was not directly about getting tailscale itself working (rather that's a symptom).\n \n", "name": "", "is_accepted": false }, { "text": "this is possible on a time/energy basis. not exactly sure what i could contribute- probably documentation & design focussed. \n \n", "name": "", "is_accepted": false }, { "text": "anything is appreciated.\n \n\n\n  \n \n\n\n i started working on docs recently, it's a little bit of set up with git and markdown, maybe not for everybody.  even if you notice something, make a post about or send me pm.\n \n\n\n  \n \n\n\n newer people often think they can't contribute anything valuable but that's not true.  newer people have the unique perspective of being new.  and thus if things are unclear (docs, etc.) please say so, as you are \"target market\" (for lack of better term) for these docs.  not the devs who already know much more.  in that vein, you already gave me some good feedback which is what we need to make docs better toward new users.  so, if you have any more just make note, send me a note, start a new thread, come to irc or whatever.\n \n\n\n  \n \n\n\n this goes for everybody!\n \n", "name": "", "is_accepted": false } ]

[ { "text": "our system only publish packages for supported distributions. xenial is eol from our maintaining perspective. we have to cut what is not important, but eats resources.\n \n", "name": "", "is_accepted": true }, { "text": "i consider that a xenial repository should be maintained since i have installed systems running ubuntu 16 and i have problems for not being able to update package.\n \n\n\n  \n \n\n\n best regards,\n \n\n\n  \n \n\n\n nelson\n \n", "name": "", "is_accepted": false }, { "text": "are you willing to pay for the cost?\n \n\n\n check personalized support here: https://github.com/armbian/build#support\n \n", "name": "", "is_accepted": false }, { "text": "you also should support us before telling what we should and should not do. perhaps just this way. otherwise fork the project, leave your daily job and start maintaining it. perhaps you will get help, perhaps not. everyday you will bump into a person which expects you will work free of charge hours in their interest ...\n \n", "name": "", "is_accepted": false }, { "text": "@igor, is there any xenial repository backup? i would like to mantain it for armbian.\n \n", "name": "", "is_accepted": false }, { "text": "@lvmc as far as i know there is no backup of the armbian-part of xenial.\n \n\n\n for your \n /etc/apt/sources.list \n you should use as a part of the url\n \n\n\n http://ports.ubuntu.com/dists/xenial/\n \n\n\n because only at this server there are armhf  and arm64 packages available.\n \n\n\n  \n \n\n\n ckeck / add these xenial-source-directorys which does include newer files:\n \n\n[dir] xenial-backports/ 2021-08-30 18:14 -\n[dir] xenial-proposed/ 2021-08-30 18:33 -\n[dir] xenial-security/ 2021-08-30 18:13 -\n[dir] xenial-updates/ 2021-08-30 18:14 -\n\n\n\n[dir] xenial/ 2016-04-21 07:43 \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "@guidol, i was talking with @igor these days and i think the main issue is how slow (and prone to errors) is the repository generator scripts for generating packages for all releases... it's time consuming and requires a lot of efforts from him. i'm taking a look at the scripts to see if i find a way to optimize it. older releases must be support as `csc` i think.\n \n\n\n  \n \n\n\n and yes, i'm using exactly the repositories you suggested, thanks: \n  \n \n\ndeb http://ports.ubuntu.com/ xenial main restricted universe multiverse\n#deb-src http://ports.ubuntu.com/ xenial main restricted universe multiverse\n\ndeb http://ports.ubuntu.com/ xenial-security main restricted universe multiverse\n#deb-src http://ports.ubuntu.com/ xenial-security main restricted universe multiverse\n\ndeb http://ports.ubuntu.com/ xenial-updates main restricted universe multiverse\n#deb-src http://ports.ubuntu.com/ xenial-updates main restricted universe multiverse\n\ndeb http://ports.ubuntu.com/ xenial-backports main restricted universe multiverse\n#deb-src http://ports.ubuntu.com/ xenial-backports main restricted universe multiverse\n\n\n  \n \n\n\n by the way now it's clearly that the affected packages are only the ones that are build by armbian, not the packages that are provided by the official ubuntu repositories.\n \n", "name": "", "is_accepted": false }, { "text": "i doubt that this is the same case, but i had the same error on an orangepi pc so for future reference i comment here.\n \n\n\n i had upgraded to buster from strech but it seems that the command lsb\\_release did not work and probably armian.config could not choose the appropriate debian release. then the list (/etc/apt/sources.list.d/armbian.list) contained no release info, and i was getting the same error. just adding the release solved the issue.\n \n\n\n  \n \n\nroot@orangepipc:~# cat /etc/apt/sources.list.d/armbian.list\n#deb http://apt.armbian.com main -utils\ndeb http://apt.armbian.com buster main buster-utils\n\n\n  \n \n", "name": "", "is_accepted": false } ]

[ { "text": "best to move to vivaldi browser.  chromium is history.\n \n\n\n vivaldi is working very good.  one of the members recommended it.  i installed it and i really like it.\n \n\n\n i copied the old chromium files over to it and got all my stuff back.\n \n", "name": "", "is_accepted": true }, { "text": "are they google or api related? google stopped support for a lot of fetures on chromium recently -\n \n\n\n https://www.debugpoint.com/2021/02/chromium-losing-private-api-support/\n \n", "name": "", "is_accepted": false }, { "text": "well that is bad.\n \n\n\n  \n \n\n\n i have my chromium folder from my old tinkerboard backed up.  what do is just copy it over to a new installation and all my addons show up. not this time.\n \n\n\n there is one very important to me.  it is a huge lose.\n \n\n\n  \n \n\n\n is there something i can do?\n \n\n\n i don't know how the api works yet. maybe not use it.\n \n\n\n i don't need to add any more addons.  all i need is to use my chromium back up from the .config hidden folder.\n \n", "name": "", "is_accepted": false }, { "text": "chromium in armbian addons is disabled.\n \n\n\n i copied my older chromium folder in tinkerboard and pasted it in the .config folder on armbian and the addons are disabled.\n \n\n\n i copied the same chromium folder in the .config folder on my pclinuxos and the addons are all there and the addons is fully enabled.\n \n\n\n  \n \n\n\n why does armbian have the addons disabled?  is there some way to enable it?\n \n\n\n i don't believe that it could be google doing it since pclinuxos is just fine.\n \n", "name": "", "is_accepted": false }, { "text": "this is all what armbian does regarding chromium and iirc in a last three years this would be the one and only complain about this problem. since we don't maintain chromium and since we have no means to oppose (one of the) biggest tech corporation on the world or support their products, armbian scarce resources will do exactly nothing. most likely its related to things you were already informed about. i don't see other explanation since it was fine until now. which means you/we can't do nothing about and this is not armbian fault.\n \n\n\n  \n \n\n\n\n\n  \n \n\n\n and i don't believe this has anything to do with armbian. beside, support goes this way: https://github.com/armbian/build#support\n \n\n\n  \n \n\n\n pclinuxos uses google chrome which is not limited but exists only for x86. \n https://chromium.googlesource.com/chromium/src/+/master/docs/chromium\\_browser\\_vs\\_google\\_chrome.md\n \n", "name": "", "is_accepted": false } ]

[ { "text": "how come, usb type-c port will magically start working if there is no proper support for this in the mainline kernel for this board family? even if kernel version is declared as stable, this doesn't mean that 100% of the \"expected\" functionality will work on 100% of the platforms. if you decided to base your work on the mainline kernel versions for this board, you should already know about hardware limitations related to the presence of proprietary vendor's drivers that are not really maintained by the vendor.\n \n", "name": "", "is_accepted": true }, { "text": "the usb-c port is not working at all on 5.7.15 either. i'm specifically concerned about storage. works fine with ubuntu 18 and 4.4 kernel. \n \n", "name": "", "is_accepted": false }, { "text": "according to the support contract, this is not a problem.\n \n\n\n  \n \n\n\n porting features from fixed private to the mainline kernel is far from cheap and simple. its expensive work which you cover in exactly 0%. hire someone to do this job and share the work. why would we need to do that? \n \n", "name": "", "is_accepted": false }, { "text": "i think you misunderstood the tone. it wasn't a demand, it was an observation. \n \n although ... it would be nice if there were some sort of release notes or faq entries for each build (bionic, buster, focal and kernels 4.4.x, 5.x.x) outlining what works and what doesn't. users could then make an educated decision beforehand, instead of discovering later that <hardware thing> doesn't work yet in a specific release/kernel.\n \n", "name": "", "is_accepted": false }, { "text": "sure that would be nice. but stuff is changing frequently and there are simply not enough ressources to keep track and test each and every feature of each and every board over and over....\n \n", "name": "", "is_accepted": false }, { "text": "for start cover what you have now. we invest 20-30-50h per day and when its release time, i have to stop all my other activities (work for food, dealing with kids and supreme commander) for several days. \n \n https://www.armbian.com/get-involved/ \n doing whatever useful for the project helps solving this problem.\n \n", "name": "", "is_accepted": false }, { "text": "i can understand why you're frustrated doing all this for (essentially) free.  let me see what i can do to help.  can you answer some questions for me? \n \n i do know c and i am a software engineer, but i've never worked with the kernel before and my low level/device driver knowledge isn't so good.  is the learning curve for this type of work too steep to have this be my first project? \n \n > it's expensive work \n \n if it is too difficult to learn, do you have any idea how expensive this would be? \n \n i do appreciate you keeping the lights on man. i know this project wouldn't exist without your help.\n \n", "name": "", "is_accepted": false }, { "text": "please try displayport kernel for nanopc-t4 published here. displayport function does not work, but there is good chances that at least ethernet adapters or flash-drives could work. patches used for building this kernel is published here, so please redirect your feedback regarding this kernel to oleksii thread.\n \n", "name": "", "is_accepted": false }, { "text": "usb type-c port will work as usb 3.0 port in host only mode (which, as it appeared, is enough for the vast majority). and the only needed and sufficient change for this:\n \n\n\n  \n \n\n\n &usbdrd\\_dwc3\\_0 { \n     dr\\_mode = \"host\"; \n };\n \n\n\n  \n \n\n\n is to be added to the dtb\n \n", "name": "", "is_accepted": false }, { "text": "same problem for me: i upgraded my nanopc t4 and spent a lot of time to configure everything. at the end i noticed usb-c is not working to connect my essential backup drive. i spent many hours for nothing, because i thought a \"stable\" release means that at least basic i/o functionality was tested. i understand that testing takes manpower and money. but if it is missing the releases should me called \"stable\" for a referenced device. i do not know how many other users run into the same problem and waste their time.\n \n", "name": "", "is_accepted": false }, { "text": "you waste our time not giving us the data we need to be able to help. \n sudo armbianmonitor -u \n what image? what kernel? \n \n mainline is still in development. things are added, and other things break. that's just a fact of life. \n we can't test every single thing. \n use legacy if it fits your goal. thank you for wasting my time too. \n if you're not happy buy an x86 sbc and buy windows for it. then go complain to microsoft like that. please.\n \n", "name": "", "is_accepted": false }, { "text": "buster server 5.8y on nanopc t4\n \n", "name": "", "is_accepted": false }, { "text": "thanks to @oleksii for figuring out that the issue is that the usb-c controller is set to otg mode rather than host mode.\n \n\n\n  \n \n\n\n this is illustrated by the rk3399-nanopc-t4.dtb which, when decompiled, contains the following:\n \n\n\n  \n \n\n\n usb@fe800000 {\n compatible = \"rockchip,rk3399-dwc3\";\n #address-cells = < 0x02 >;\n #size-cells = < 0x02 >;\n ranges;\n clocks = < 0x08 0x81 0x08 0x83 0x08 0xf6 0x08 0xf8 0x08 0xf4 0x08 0xf9 >;\n clock-names = \"ref\\_clk\\0suspend\\_clk\\0bus\\_clk\\0aclk\\_usb3\\_rksoc\\_axi\\_perf\\0aclk\\_usb3\\0grf\\_clk\";\n resets = < 0x08 0x125 >;\n reset-names = \"usb3-otg\";\n status = \"okay\";\n phandle = < 0xd6 >;\n\n usb@fe800000 {\n compatible = \"snps,dwc3\";\n reg = < 0x00 0xfe800000 0x00 0x100000 >;\n interrupts = < 0x00 0x69 0x04 0x00 >;\n clocks = < 0x08 0x81 0x08 0xf6 0x08 0x83 >;\n clock-names = \"ref\\0bus\\_early\\0suspend\";\n dr\\_mode = \"otg\";\n phys = < 0x33 0x34 >;\n phy-names = \"usb2-phy\\0usb3-phy\";\n phy\\_type = \"utmi\\_wide\";\n snps,dis\\_enblslpm\\_quirk;\n snps,dis-u2-freeclk-exists-quirk;\n snps,dis\\_u2\\_susphy\\_quirk;\n snps,dis-del-phy-power-chg-quirk;\n snps,dis-tx-ipgap-linecheck-quirk;\n power-domains = < 0x1a 0x18 >;\n status = \"okay\";\n phandle = < 0xd7 >;\n };\n };\n\n\n  \n \n\n\n so, as @oleksii pointed out, dr\\_mode is set to \"otg\" rather than \"host\", and that is why the usb-c port is treated as a usb peripheral rather than a usb host, and why you can't get any device plugged onto that port to be recognized.\n \n\n\n  \n \n\n\n the solution is fairly simple:\n \n\n\n \n create a rockchip-usb-c-host.dts file in /boot/dtb/rockchip/overlay with the following content:\n\n \n/dts-v1/;\n/plugin/;\n\n/ {\n compatible = \"rockchip,rk3399\";\n fragment@0 {\n target = <&usbdrd\\_dwc3\\_0>;\n \\_\\_overlay\\_\\_ {\n dr\\_mode = \"host\";\n };\n };\n};\n \n \n issue the command:\n \narmbian-add-overlay rockchip-usb-c-host.dts\n \n \n reboot as asked. devices plugged into the usb-c port should now be detected. you can also verify that the usb-c port is set to host mode by issuing:\n \ncat /sys/firmware/devicetree/base/usb@fe800000/usb@fe800000/dr\\_mode\n\n \n which should now report host rather than otg.\n \n \n\n\n\n i'll see if i can create a pull request to generate this .dtbo in https://github.com/armbian/build/blob/master/patch/kernel/rockchip64-dev/general-rockchip-overlays.patch.\n \n", "name": "", "is_accepted": false }, { "text": "good work! although, it solves some problem for you, i want to mention additionally: what you did and what i suggested - is just a very specific workaround rather than permanent fix .  this port configuration is set to otg by default in the master (board family) dtb file purposely, and imho this is right, not a mistake anyway. because this board supports dual mode on usb type-c port, if you have proper support in all concerned drivers and enabled dual mode in kernel, of course. real actual role of the port should be determined by the system automatically, based on the negotiation with other party (i purposely simplify things a lot ). this port capabilities detection and further toggling is performed by the driver of a dedicated programmable pd chip (fusb302), which then should notify all other concerned underlaying drivers about the new role decision. my conclusion, after some intensive research performed, makes me confident to state, that current mainline fusb302 driver still misses a lot of desired functionality to support needed interaction with dwc3 driver e.g. in a right fashion  if there are experts around who may argue and confirm that i'm not right, i'll be only happy to hear this! \n \n", "name": "", "is_accepted": false }, { "text": "yes, i fully agree with your analysis that the proper solution is to have upstream kernel properly fixed to perform autonegotiation. but in the absence of someone actively working on that, and considering that many nanopc-t4 users are looking for a solution that'll let them use usb-c in host mode, we might as well provide a workaround through an overlay for the time being. i have therefore submitted a pull request for this in https://github.com/armbian/build/pull/2299.\n \n\n\n  \n \n\n\n  \n \n", "name": "", "is_accepted": false } ]

[ { "text": "perhaps you should try another psu or check your cables : your voltage drop low at 960 mhz and you got sata errors and reset.\n \n\n\n  \n \n\n\n try : cat /sys/devices/platform/sunxi-i2c.0/i2c-0/0-0034/axp20-supplyer.28/power\\_supply/ac/voltage\\_now  while transferring files.\n \n", "name": "", "is_accepted": true }, { "text": "thanks for responding.\n \n\n\n it was indeed a faulty powersupply. transferring files is now without any problems.\n \n\n\n  \n \n\n\n cat /sys/devices/platform/sunxi-i2c.0/i2c-0/0-0034/axp20-supplyer.28/power\\_supply/ac/voltage\\_now is not present om my banana pi.\n \n\n\n now that the powersupply problem is solved:\n \n\n\n is there a (webbased) possibility to monitor a bananapi m1 (or any other board with armbian) ?\n \n\n\n  \n \n\n\n regards,\n \n\n\n andré\n \n", "name": "", "is_accepted": false }, { "text": "cat /sys/devices/platform/sunxi-i2c.0/i2c-0/0-0034/axp20-supplyer.28/power\\_supply/ac/voltage\\_now is not present om my banana pi.\n \n\n\n  \n \n\n\n well my kernel is outdated. you can find the correct path in armbianmonitor script.\n \n", "name": "", "is_accepted": false }, { "text": "afaik rpi-monitor works, if the device is reachable  \n \n\n\n i'm using https://uptimerobot.com/ for a couple of hosted sites in different places and my own devices, offers ping/port and cron if the device has internet but is not reachable itself, just to see when something is going down\n \n", "name": "", "is_accepted": false } ]

[ { "text": "attached is jernej's patch, slightly modified to work with 5.10.13, sorry for posting it here. the overscan issue can be fixed with this tool, https://projects.nwrk.biz/projects/allwinner-tvout/wiki, this was described in this forum but i don't have the link. the washed out (hardware) issue has also been described here and can be easily fixed with a resistor. there are also drm properties for dealing with tv offsets and sizing issues but i have not figured out where to put them in the user level device tree, does anyone know? (i tried put them under the tve node but didn't work.) the properties are described here: https://www.kernel.org/doc/html/v4.12/gpu/drm-kms.html?highlight=drm tv#existing-kms-properties\n \n\n\n zzzz-tv-cvbs.patch\n \n\n\n  \n \n\n\n patch was tested to work with zero, and neo...\n \n", "name": "", "is_accepted": true }, { "text": "moved to common issues / peer to peer technical support\n \n", "name": "", "is_accepted": false }, { "text": "iirc, av out used to work with the old legacy kernel. you can try this image, and in case it is disabled by default, you can probably enable it by editing the fdt file: https://archive.armbian.com/orangepipc/archive/armbian\\_5.90\\_orangepipc\\_ubuntu\\_xenial\\_default\\_3.4.113\\_desktop.7z enviado desde mi moto g(6) plus mediante tapatalk ", "name": "", "is_accepted": false }, { "text": "@jmcc\n \n\n\n  \n \n\n\n thanks for your suggestion. i would write the image to another sdcard asap and would get back with the results. so, do you confirm to me that av out doesn't work on the newest versions? that's a pity... maybe it's necessary to compile a kernel with the support for it but i don't know from where to begin should this be the case! \n \n\n\n just another confirmation. i've found some discordant av out cable pinouts, the most common to be found being this one:\n \n\n\n  \n \n\n\n https://descubriendolaorangepi.wordpress.com/2017/01/10/salidas-de-audio-y-video-hdmi-y-rca/\n \n\n\n  \n \n\n\n is it actually the right one? i'd like to rule out issues with the cable otherwise it could well be that everything could be up and running while misleaded by just a wrong cable. thanks again and have a nice day! \n \n", "name": "", "is_accepted": false }, { "text": "this thread seems to give a working solution for recent kernels (pay attention to the post from jernej dating of today, 2021/01/18):\n \n\n\n\n  \n \n\n\n you can try the old image, which should work easily with a small modification in the boot files. use this method: https://docs.armbian.com/hardware\\_allwinner/#fex-outdatedunsupported-informational-only\n \n\n\n if it works, then you can try to make an image with a patched current kernel.\n \n\n\n  \n \n\n\n\n\n no idea, i've never used av out on my opi+2e. however, i remember some reports that in certain opi models the image is too bright/washed out, because of a missing filter in the schematics. that can be solved by adding a 50 ohm resistor in your cable. not sure if it applies also to your board. reference: http://www.orangepi.org/orangepibbsen/forum.php?mod=viewthread&tid=3404\n \n", "name": "", "is_accepted": false }, { "text": "@jmcc\n \n\n\n  \n \n\n\n i don't really know how to thank you! what a knowledge! my sincere compliments... i've much to read, much to do. i'll do my best to come back with some updates asap. have a nice day! \n \n", "name": "", "is_accepted": false }, { "text": "i apologize for not coming back before but downgrading back to 5.90 has caused me issues with the wifi connection (discussed in another thread i've recently started) and i couldn't go on with the 'quest' about tv out. i've made all the modifications suggested here to script.bin with the aid of bin2fex and fex2bin:\n \n\n\n  \n \n\n\n[disp\\_init]\ndisp\\_init\\_enable = 1\ndisp\\_mode = 1\nscreen0\\_output\\_type = 3\nscreen0\\_output\\_mode = 5\nscreen1\\_output\\_type = 2\nscreen1\\_output\\_mode = 14\nfb0\\_format = 0\nfb0\\_width = 0\nfb0\\_height = 0\nfb1\\_format = 0\nfb1\\_width = 0\nfb1\\_height = 0\n\n[hdmi\\_para]\nhdmi\\_used = 0\nhdmi\\_power = \"vcc-hdmi-18\"\n\n[tv\\_para]\ntv\\_used = 1\ntv\\_dac\\_used = 1\ntv\\_dac\\_src0 = 0\n\n\n  \n \n\n\n i've then rebooted but nothing. i've also added (as still suggested in that thread) a line with\n \n\n\n  \n \n\n\ntv\n\n\n  \n \n\n\n at the end of /etc/modules but still no signal on tv out. now, maybe i'm missing something or the pinout i'm using (this one) isn't the right one. i don't know. please note that i haven't installed any additional package: i just expect to get the cli on my television and it could well be i'm being misleaded by this assumption. have a nice day! \n \n", "name": "", "is_accepted": false }, { "text": "i would try two things:\n \n\n\n \n manually insert the module with \"modprobe tv\", just ot see it it there.\n \n \n in the thread you link, the user mentions that his tv out works with jernej's openelec, by doing these modifications to the fex file. you can try that, just to make sure your cable works.\n \n \n for last, you can try directly with our current mainline kernel, using the suggestions in the thread linked above\n \n\n", "name": "", "is_accepted": false }, { "text": "btw, i just reworked cvbs patch so it works with 5.10:\n \n\n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "i've tried the\n \n\n\n  \n \n\n\nmodprobe tv\n\n\n  \n \n\n\n command and it ran fine so i've started to think about a wrong pinout and i can definitively confirm that the one given here is wrong while the right one is given here.\n \n\n\n using that pinout everything went fine (at least for video output, i haven't still had the chance to check audio but i would come back with a confirmation about it too) so i can also confirm that all the changes outlined in my previous post (got from that other thread i've mentioned, not my own findings) are just enough to get tv-out working on an opi pc on armbian 5.90 ubuntu xenial 3.4.113-sun8i. the only 'issue' is that, as already reported by others, the image goes beyond the screen area, probably because the right resolution is 720x480 (i recall having read something like that but i don't remember where). i need to study the necessary modifications and apply them too. it may also be that i just need to set\n \n\n\n  \n \n\n\nscreen1\\_output\\_mode = 11\n\n\n  \n \n\n\n as said here. if i recall well from my extensive research, 14 is ntsc while pal is 11 so the problem could just reside there.\n \n\n\n i'd also like to apply jernej's patch to be able to get back to armbian focal 5.10.4-sunxi still with a working tv-out but i really don't know from where to start. i need to read back (and maybe elsewhere too) and see what to do. still a lot of work to do for me but in the meantime i wanted to get back to avoid someone else using that wrong pinout and scrambling his mind without reason.\n \n\n\n a slight off topic to say that i couldn't succeed in finding any downloadable openelec image indeed all the links given here are dead including this one on mega wich contains only empty folders but it doesn't matter now. a nice day to all of you! \n \n", "name": "", "is_accepted": false }, { "text": "small update: changing screen1\\_output\\_mode to 11 (indeed pal as i recalled) didn't solve the problem with the screen margins. i've also tried to apply the other workaround suggested by many (here for example but even in the thread linked above by jernej) adding the kernel parameter:\n \n\n\n  \n \n\n\nvideo=composite-1:720x480\n\n\n  \n \n\n\n at the end of /etc/sysctl.conf (the only way i'm aware to do it but i may be wrong), still to no avail. no changes at all, even minimal, the reason probably being the fact that it seems my modification isn't just taken into account given that checking the resolution i still get 720x576.\n \n\n\n better to leave this alone for the moment and check how to apply jernej's patch and get a latest image with tv-out (in spite of the fact i don't think it would be that easy, probably involving setting up a whole toolchain).\n \n", "name": "", "is_accepted": false }, { "text": "what? why don't you use the armbian build script? that is what all this project is about! \n \n\n\n  \n \n\n\n applying a patch is as easy as putting it on the corresponding folder under \"userpatches\", or either use the command line option \"create\\_patches=yes\" in case you want to apply it manually.\n \n", "name": "", "is_accepted": false }, { "text": "@jmcc\n \n\n\n  \n \n\n\n thanks as always! your help is precious... following the very well laid down guides, i could easily set everything up. i've immediately tried to build an image but it failed when downloading two packages, them being https://redirect.armbian.com/\\_toolchain/gcc-linaro-arm-linux-gnueabihf-4.8-2014.04\\_linux.tar.xz and https://redirect.armbian.com/\\_toolchain/gcc-arm-9.2-2019.12-x86\\_64-arm-none-linux-gnueabihf.tar.xz.\n \n\n\n probably it was just a problem linked with my connection but those two errors were regularly repeating. i've manually downloaded the both of them by wget (from exactly the same addresses which were constantly failing inside the script) inside the folder cache/toolchains and this was just enough to get round the problem. it has taken a while (more than four hours on a 3rd gen i7, not exactly an up to date configuration!) but i've then been able to successfully build an image (not tried to flash it though).\n \n\n\n now the only problem that remains is that i really don't know how to apply jernej's modifications. i'm not a programmer so it's my fault but i don't really know where to start from. usually, i search and learn but i don't even know what to search for... i've made a couple of educate guesses and i've found something about \"cherry picking\" a commit but i couldn't go on: it goes beyond my knowledge. thanks again and have a nice day! \n \n", "name": "", "is_accepted": false }, { "text": "first generate patch from that commit like this and then put it in appropriate folder according to documentation.\n \n", "name": "", "is_accepted": false }, { "text": "hi and first of all thanks for your help. i've downloaded the .patch file by wget inside userpatches/kernel/sunxi-current. it should be the right place but it is only my guess because i haven't understood what the documentation says about that. it seems that the patching process should be something separate than what's being done by the compile.sh script or by the way i couldn't get the output shown in the documentation in any way nor i've found other scripts, maybe one purposedly intended for patching. i've also tried to check the compile.sh script in search for an hint but i haven't found anything relevant there. before starting another four hours build process, i'd like to be certain about what i'm doing.\n \n\n\n thanks for giving me the direct link to the patch but, if i can ask, how can i generate that .patch file by myself? i've made a lot of research and it seems that what's needed is git format-patch using the commit-sha which in our case should be ad153ef6ee5be33531187f97d5fa0c07455dc795 but i'm still missing a lot and i'm not going anywhere. still my fault. when it is only a matter of downloading some sources and compile them then i'm quite fine but this is too much for me, at least by now.\n \n\n\n  \n \n\n\n edit: i've tried to build again with the modifications said above. in the end, i've thought that with just a few modifications, the compilation should have taken a lot less so i've tried but i've got this error:\n \n\n\n  \n \n\n\n[ error ] error in function compile\\_kernel [ compilation.sh:413 ]\n[ error ] kernel was not built [ @host ]\n[ o.k. ] process terminated\n\n\n  \n \n\n\n i've checked the script compilation.sh (found in lib/) and at line 413 there is just the error printing but the conditional check that arises it is just at the line before:\n \n\n\n  \n \n\n\nif [[ ${pipestatus[0]} -ne 0 || ! -f arch/$architecture/boot/$kernel\\_image\\_type ]]; then\n exit\\_with\\_error \"kernel was not built\" \"@host\"\n\n\n  \n \n\n\n i'm surely on the wrong path and i haven't applied that patch as i should have done.\n \n", "name": "", "is_accepted": false }, { "text": "the build script, after git checking out the kernel sources, will apply the patches. all of the applied patches will appear in order, with a green indicator when they are applied ok and yellow or red when there is some problem. though, since the text moves so fast, you probably didn't notice it.\n \n\n\n  \n \n\n\n the easiest way to check how the patches are applied is to add the option create\\_patches=yes to compile.sh. it will make the script pause twice, first after applying the u-boot patches and then after the kernel patches. you can see if your patch was applied correctly, and troubleshoot if not.\n \n\n\n  \n \n\n\n\n\n simply open the commit in github, and then at the address bar add \".patch\" at the end.\n \n", "name": "", "is_accepted": false }, { "text": "a little more detailed explanation about create\\_patches: https://zuckerbude.org/armbian-using-create-patches/\n \n", "name": "", "is_accepted": false }, { "text": "great! you're teaching me a lot. so plain simple while i was trying to shoot an ant with a shotgun! \n \n\n\n  \n \n\n\n\n\n  \n \n\n\n as above, thanks!\n \n\n\n  \n \n\n\n\n\n  \n \n\n\n thanks!\n \n\n\n  \n \n\n\n you all are helping me a lot. i would try to understand better what's going on with the error described in my previous post and how to handle everything better. i really appreciate the efforts of you all! \n \n\n\n  \n \n\n\n edit: adding create\\_patches=yes has given better control indeed. previously i've put the patch inside userpatches/kernel/sunxi-current getting the error described above. now, according to what seems to be suggested by the compile.sh script, i've moved it inside cache/sources/linux-mainline/orange-pi-5.10 getting exactly the same error. what is even stranger if possible is the fact that after hitting enter to resume the script execution it says (both cases) that there isn't anything to patch like if the patch is ignored but this shouldn't be the case given that as soon as i've deleted it the build ended successfully. i don't know. \n \n", "name": "", "is_accepted": false }, { "text": "hello again. reading the guide suggested by werner, i've understood that my assumptions were somewhat (let's say totally) wrong. the create\\_patches=yes switch has something to do only when i've actually modified the code and eventually it generates all the necessary .patch files inside output/patch. the fact it says there isn't anything to patch doesn't mean it is ignoring jernej's patch but it hasn't anything to do because there isn't any modification to the code.\n \n\n\n if i continue reading that guide, it says that the right place to put the patch i'm trying to apply is actually userpatches/kernel/sunxi-current/ as i've already done. i don't know why it fails with the error described above then, it seems i'm not doing anything wrong...\n \n", "name": "", "is_accepted": false }, { "text": "as i said above, you must look at the list of applied patches, and see jernej's patch at the end, if it applied ok or failed. patches from the userpatches directory are applied at the end, and the script marks them with a \"u\" in the output. the message you read later is simply saying that you did not make any additional changes after applying the provided patches, and therefore it will continue. on the contrary, when you make some additional changes, it will create a new patch with the changes you made. enviado desde mi moto g(6) plus mediante tapatalk ", "name": "", "is_accepted": false }, { "text": "@jmcc\n \n\n\n  \n \n\n\n yes, exactly. what i had already understood thanks to the guide suggested by werner and tried to explain in my previous post. everything seems in its place but it keeps failing, certainly because i'm doing something wrong but i can't even imagine what.\n \n\n\n here is the full log of my last build attempt but jernej's patch is applied fine according to this line:\n \n\n\n  \n \n\n\n[ o.k. ] * [u][c] ad153ef6ee5be33531187f97d5fa0c07455dc795.patch\n\n\n  \n \n\n\n in the end i get this:\n \n\n\n  \n \n\n\n[ error ] error in function compile\\_kernel [ compilation.sh:413 ]\n[ error ] kernel was not built [ @host ]\n[ o.k. ] process terminated\n\n\n  \n \n\n\n and i can't achieve a successful build while if i just delete the patch everything goes fine. my compile.sh parameters are these:\n \n\n\n  \n \n\n\n/compile.sh board=orangepipc branch=current release=focal build\\_minimal=no build\\_desktop=yes kernel\\_only=no kernel\\_configure=no compress\\_outputimage=sha,gpg,img\n\n\n  \n \n\n\n i don't know what i'm still missing and i apologize for all the time lost on this.\n \n", "name": "", "is_accepted": false }, { "text": "you are not missing anything. that is the normal process for kernel developing, things don't work at the first try normally.\n \n\n\n  \n \n\n\n you already saw that the patch applied correctly, but the changes made by the patch are causing some compilation error. it worked when jernej applied it, but now there is something causing trouble.  so the next step is look at the logs under output/debug, see what failed, and try to fix it. have fun!\n \n", "name": "", "is_accepted": false }, { "text": "thanks for your effort on this, i got it working on 5.10.12 using pi-zero; the only changes needed were to remove the other definition of sun8i\\_h3\\_mixer1\\_cfg,  added back the tve.dts file from the original patch, as well add it to armbianenv.txt for invocation as described in the original patch.\n \n\n\n  \n \n\n\n it is running in dual screen pi-zero; the top screen is a 4.3 inch car monitor, the bottom is a 3.2\" ili9341. i haven't tried the panfrost bit - shouldn't it work on the top screen? kodi does come up on the top screen.\n \n\n\n  \n \n\n ", "name": "", "is_accepted": false }, { "text": "h3 doesn't use panfrost but lima. if you want to run kodi efficiently, you'll need to pick a lot of kernel and ffmpeg patches from libreelec, manually compile ffmpeg and use kodi without desktop. oh, and you need kodi 19 rc1, that probably means compiling kodi too.\n \n", "name": "", "is_accepted": false }, { "text": "what a mess! i really fear all of this is beyond my knowledge but i don't give up... i was using libreelec before (your work too) with great satisfaction but, at least by what i've understood from my extensive research, tv out is impossible to get working there and my hdmi is gone because of the design flaw with the opi pc. \n \n\n\n i would try to apply yam1 advices (though i don't still get the whole of them because of my aforementioned limits) at least to get a succesful build with working av out (though it seems i wouldn't ever get kodi working again). maybe i could also succeed in compiling kodi and ffmpeg but i really don't know what patches to pick so i don't even dare to start on that. isn't opi zero h2 based? maybe i recall it wrong...\n \n", "name": "", "is_accepted": false }, { "text": "thanks for your teaching as always! i've checked under output/debug and i've found what i thought to be a descriptive name: patching.log. i've started from there but unfortunately it just gives confirmation that the patch has been applied successfully. i've checked also output.log which doesn't make me gain any better insight. the relevant file is the .tgz with the timestamp in its name. i've extracted it and found a file called compilation.log. the answers (if i can find them), are almost certainly there... i'll search for them at my best (not that much unfortunately!) bearing in mind the modifications inside jernej's patch and yam1 advices and i'll get back should i succeed in finding anything relevant.\n \n\n\n  \n \n\n\n edit: nothing relevant in the logs (at least not to me). i've also tried to follow yam1's hints but i couldn't get anywhere. i'm starting to think that, considering that kodi wouldn't work well anyway, it isn't worth the effort. i give up: i would keep my opi pc in a drawer for an unlikely to happen future project, no use for it under the current conditions. i'd like to thank all of you for your help and advices. i've learnt a lot! \n \n", "name": "", "is_accepted": false }, { "text": "that's what all of this sbc thing is about.  \n \n", "name": "", "is_accepted": false }, { "text": "i'm actually considering adding tv out support to libreelec. you would only need to specify overlay for enabling tv out. would that work for you?\n \n", "name": "", "is_accepted": false }, { "text": "that would be great! thank you! in spite of the fact that by what you've explained i've understood that it is almost impossible to have a satisfactory kodi experience on armbian, i still can't accept the defeat... while waiting for let's say libreelec 'tv-out capable', i would keep scrambling my mind on the reason why i can't succeed building armbian. have a nice day! \n \n", "name": "", "is_accepted": false }, { "text": "incorrect. you can have an excellent kodi experience on armbian, if it is compiled properly. we have it working for rockchip and odroid xu4 so far with the legacy kernels. sunxi mainline is in the to-do list.\n \n", "name": "", "is_accepted": false } ]

[ { "text": "thank you for the tip. i currently solved this without cheating:\n \n\n\n 1) i use a shared folder on virtualbox\n \n\n\n 2) on the main bash i'm running, after the compilation is done i create myapp folder, and move from the output/images folder renaming 3 files generated.\n \n\n\n simple solution for my dumb question :/\n \n\n\n  \n \n\n\n  \n \n", "name": "", "is_accepted": true }, { "text": "ok, after a weeks effort, i (quick-)examined the code, found some related posts and got help from @werner, thank you for breaking the \"you are on your own\" rule .\n \n\n\n  \n \n\n\n the structure above needs major revising, if we go step by step:\n \n\n\n  \n \n\n\n 1) i have to write the variables in the outher bash to some .sh file (e.g. under userpatches/overlay/myapp) to be copied to chroot environment to be sourced.\n \n\n\n 2 & 3) i cannot do this, because in \"image-helpers.sh\" customize\\_image routine only one file, \"customize-image.sh\" is copied to $sdcard. so i must combine everything into that file.\n \n\n\n 3) in customize-image.sh, i need to source the file i've saved in step 1 to get my variables back\n \n\n\n 4) is ok, but can only be used for setting variables.\n \n\n\n  \n \n\n\n and finally how i can include my own files... see:\n \n\n\n\n now i have to test this whole thing.\n \n\n\n cheers\n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "we like to help but we simply do not have time to do so. we do have a constant lack of human ressources \n \n\n\n those who help, including myself, are volunteers to the project and do this in their free time. the primary goal for years now is to raise funds to hire fulltime professionals but we are still not even close to get there...\n \n", "name": "", "is_accepted": false }, { "text": "we like to help but we simply do not have time to do so. we do have a constant lack of human ressources \n \n\n\n those who help, including myself, are volunteers to the project and do this in their free time. the primary goal for years now is to raise funds to hire fulltime professionals but we are still not even close to get there...\n \n", "name": "", "is_accepted": false }, { "text": "i fully understand this, that quote was attribute to \"no end-user support: built from trunk\" wording in motd \n \n\n\n  \n \n\n\n i learned linux playing with these sbc's, mainly armbian and it is a hobby for me. i have several installations at my home-office as hobby projects. if i ever earn some money from these stuff i'll donate it. but for this or helping others on the forums, i need to learn first  \n \n\n\n  \n \n\n\n things like chroot environment, kernel parameters, kernel compiling are very new to me. the build script is very high quality code from my perspective. last week, by examining it i learned a lot. for example the \"wait\\_for\\_package\\_manager\" function in general.sh provides solution for some of my problems. kudos for @igor and everybody contributed.\n \n\n\n  \n \n\n\n i'll try to \"document\" my adventure for other newbies.\n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "so a cheat to let customize image see the board would be for the script to source sdcard/etc/armbian-release\n \n\n\n  \n \n\n\n then you'll have a board var etc.  sorry typing on my phone otherwise if provide a better example \n \n", "name": "", "is_accepted": false } ]

[ { "text": "iirc there were some issues on debian user land and 3d acceleration and i assume they still exists (buster is too old for fancy stuff). its known that it works on focal  / hirsute. since we just started on adding 3d support, this is certainly not present on images that are currently available. its coming with a next release 21.08 / this month. we only have packages for ubuntu based builds - they came from here. we have no plans to support 3d on debian desktops since this represent extra work and maintenance burden.\n \n\n\n  \n \n\n\n as i notice https://github.com/armbian/build/blob/master/config/targets.conf#l522-l530 we didn't enable on 32bit probably because we need someone to test if it works. build from sources is needed at this point. and remember to enable 3d since its not enabled by default.\n \n", "name": "", "is_accepted": true }, { "text": "many other things can be wrong - like lack of most important data for example. @werner have provided you link to some page where you have to go trough few steps to understand what is minimum requirements to ask for technical oriented help on this forum. ofc you can also choose to provide no data, data you think is relevant or just vague description of the problem.\n \n\n\n  \n \n\n\n tl;dr; there is too little information about software you are using, so nobody with competence can give you valuable data. if you count on our supernatural skills of mind reading - don't know anyone around to have that \n \n\n\n  \n \n\n\n welcome!\n \n", "name": "", "is_accepted": false }, { "text": "you are right! i've been searching for help on too many places for too many time. totally forgot this isn't the project forum. i'm sorry for the initial lack of information. i made an update to this topic giving some background and details about everything. is there anything else i could be doing to make things easier?\n \n", "name": "", "is_accepted": false }, { "text": "general rules:  we only try to support our builds / work. that is already close to impossible due to lack of resources. when you are using custom build, support costs goes sky high and its again problematic to ask for support. too much resources to understand what was changed. iirc 3d support works oob on focal user land or higher. if you build image with our tools and enable 3d, it should work but i am not sure if there are 32bit packages for this. i know it works on 64bit. that's all i can help you here.\n \n", "name": "", "is_accepted": false }, { "text": "it is the local image downloaded from armbian site. it's only using an preemptive kernel. linuxcnc software is just a package isntalled later. putting this aside, let's assume i'm running a completely clean image (actually it is armbian\\_21.02.3\\_orangepipc\\_buster\\_current\\_5.10.21\\_xfce\\_desktop\\_h3) the problem is exactly the same. it's not anyone else build. i'm missing something?\n \n", "name": "", "is_accepted": false } ]

[ { "text": "hello,\n \n\n\n sorry, my mistake, i was writing about hc4...\n \n\n\n  \n \n\n\n finally i had to recover data from my last ddfull backup, so it is working now, booting from sd card again with no problem...\n \n\n\n  \n \n\n\n initial instalation was done 6 months ago, from this source https://www.armbian.com/odroid-hc4\n \n\n\n vicc\n \n", "name": "", "is_accepted": true }, { "text": "################### logwatch 7.4.3 (04/27/16) #################### \n processing initiated: fri sep 3 07:37:59 2021\n date range processed: yesterday\n ( 2021-sep-02 )\n period is day.\n detail level of output: 0\n type of output/format: mail / text\n logfiles for host: \n ################################################################## \n \n --------------------- dpkg status changes begin ------------------------ \n\n upgraded:\n armbian-bsp-cli-odroidhc4:arm64 21.05.8 => 21.08.1\n armbian-config:all 21.05.8 => 21.08\n armbian-firmware:all 21.05.8 => 21.08\n armbian-zsh:all 21.05.8 => 21.08\n linux-dtb-current-meson64:arm64 21.05.8 => 21.08.1\n linux-libc-dev:arm64 21.05.8 => 21.08.1\n openmediavault:all 5.6.13-1 => 5.6.14-1\n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "this doesn't looks like stock armbian (we don't use extlinux kernel loading on this device) and title is hc2 while bsp files shows hc4.\n \n", "name": "", "is_accepted": false } ]

[ { "text": "good.\n \n\n\n\n\n also good. its minimal so even this is not included by default\n \n\n\n\n\n not our issue. seems like the debian mirror has issues. simply retry later.\n \n", "name": "", "is_accepted": true }, { "text": "is the debconf package installed?\n \n\n\n if not this should be added to minimal package list.\n \n\n\n or better make armbian-config depend on it.\n \n", "name": "", "is_accepted": false }, { "text": "probably better, yes. minimal image should stay as minimal as possible.\n \n", "name": "", "is_accepted": false }, { "text": "@technicavolous https://github.com/armbian/build/pull/2689 \n \n\n\n do you have a chance to test this change?\n \n", "name": "", "is_accepted": false }, { "text": "fresh download just now of minimal image.\n \n\n\n debconf is present.\n \n\n\n still no armbian-config until\n \n\n\n apt install armbian-config\n \n\n\n  \n \n\n\n during install\n \n\n\n not found 151.101.6.132\n \n\n\nfailed to fetch http://deb.debian.org/debian/pool/main/u/unzip/unzip\\_6.0-23+deb10u1\\_armhf.deb 404 not found 151.101.6.132\n\n\n  \n \n\n\n couldn't get a wired or wireless connection to do armbianmonitor -u\n \n\n\n  \n \n\n\n second time pretty much the same\n \n\n\n  \n \n\n\n downloaded again and burned image\n \n\n\n debconf is present\n \n\n\n no armbian config\n \n\n\n nmtui to set network\n \n\n\n apt install armbian-config\n \n\n\n not found 151.101.6.132\n \n\n\n armbian-config install fails\n \n\n\n sudo apt update\n \n\n\n sudo apt upgrade\n \n\n\n n: inrelease changed version from 10.7 to 10.8\n \n\n\n  \n \n\n\n still no armbian-config\n \n\n\n apt install armbian-config  works\n \n\n\n armbianmonitor -u states there is a network problem\n \n\n\n armbian-config runs and is able to forget and then activate again wifi\n \n\n\n can ping yahoo.com but armbianmonitor -u reports network error\n \n\n\n  \n \n\n\n @wernerplease educate me on how to properly test your fix. i am coming up fast but haven't done that yet... but i do have a build system running.\n \n\n\n  \n \n\n\n  \n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "was not a problem after apt update and apt upgrade.\n \n", "name": "", "is_accepted": false }, { "text": "makes sense but i'm spoiled by armbian-config and *assumed* it would be there. maybe a note on the download page that it really is minimal lol\n \n\n\n  \n \n\n\n thanks!\n \n", "name": "", "is_accepted": false } ]

[ { "text": "after a short break i just want to update that i’ve managed to enable the i2c-3 on boot. the truth is that it was too simple… (later i’ll explain what was the mistake).\n \n\n\n all i’ve needed to do is:\n \n\n\n  \n \n\n\n 1.  update the boot device tree (cache/sources/u-boot/v2019.04/arch/arm/dts/sun7i-a20-lamobo-r1.dts) with:\n \n\n\n&i2c3 {\n pinctrl-names = \"default\";\n pinctrl-0 = <&i2c3\\_pins\\_a>;\n status = \"okay\";\n};\n\n\n \n i guess that instead of updating the boot device tree, i could also just update /boot/armbianenv.txt with:\n \n\n\n\noverlays=i2c3\n\n\n  \n \n\n\n 2. update lamobo\\_r1\\_deconfig file with:\n \n\n\nconfig\\_i2c0\\_enable=y\nconfig\\_i2c1\\_enable=y\nconfig\\_i2c2\\_enable=y\nconfig\\_i2c3\\_enable=y\n\n\n \n when i just added config\\_i2c3\\_enable=y it didn’t work. i didn’t figure why...\n \n\n\n\n the awkward reason i failed to do it in the beginning was because i’m using a script that updates my board on remote (without using sd card). but when i did the burning with sd - it worked !!\n \n\n\n the difference between the remote burning script and the burning with sd script is that in the remote script i’m not burning all /dev/mmcblk1, but just /dev/mmcblk1p1 and /dev/mmcblk1p2.\n \n\n\n and now i’m only guessing (so you are all welcome to correct my assumption), that the configuration of the i2c on boot is written into mmcblk1boot, and that is why it didn’t work when i used the remote burning script.\n \n\n\n  \n \n\n\n thanks to all for the help and support.\n \n", "name": "", "is_accepted": true }, { "text": "did you added also config\\_cmd\\_i2c=y to recompile u-boot with i2c related commands ?\n \n", "name": "", "is_accepted": false }, { "text": "light up a single bus - if you're looking for device detect - otherwise don't do this, and let the kernel sort it once booted with device tree...\n \n\n\n  \n \n\n\n what problem are you trying to solve?\n \n", "name": "", "is_accepted": false }, { "text": "yes i did, but the compilation still fail. i guess i'm using the wrong configuration.\n \n\n\n however, when i add config\\_spl\\_dm=y, the compilation seems to work but later fails on:\n \n\n\n u-boot-spl section `.data' will not fit in region `.sram' \n region `.sram' overflowed by 820 bytes \n  \n \n\n\n maybe i should try a different approach.\n \n\n\n i've noticed that if i run \"dm tree\", i don't see the i2c in the device tree,\n \n\n\n but if i call \"i2c bus\", i get:\n \n\n\n bus 0:  twsi0 \n and if i call \"i2c dev 0\", i get: \n \n\n\n setting bus to 0 \n valid chip addresses: 34\n \n\n\n  \n \n\n\n however, when i call \"i2c dev 1\" (or 2, or 3...), i get:\n \n\n\n invalid bus 1\n \n\n\n i2c - i2c sub-system \n  \n \n\n\n something here is weird. i don't see i2c0 (or any other i2c bus) at the device tree, but i do see it with the command \"i2c dev 0\".\n \n\n\n so why is that i can't see the other bus (1, 2 or 3) with \"i2c dev\" command ?\n \n", "name": "", "is_accepted": false }, { "text": "i need to use an external led device (not the leds that are on the board), and i need to be able control this device both from boot and linux (and in order to control this device i'm must enable the i2c3 bus).\n \n\n\n the weird thing is that at the boot stage i do have access to i2c0 bus (which is used to control the axp209), although i can't see it the device tree with \"dm tree\" (however i2c0 and i2c3 are defined in \"sun7i-a20-lamobo-r1.dts\").\n \n\n\n  \n \n\n\n any ideas how to enable the i2c3 bus ?\n \n\n\n (i though about trying to do the same as implemented with i2c0 for the axp209, but i still didn't figure it out)\n \n", "name": "", "is_accepted": false }, { "text": "be aware that u-boot and kernel don't use the same dt file, you need to verify the one used in u-boot build ...\n \n", "name": "", "is_accepted": false }, { "text": "yes, of course. my i've modified the dt file that is located here: ../../../armbian/cache/sources/u-boot/v2019.04/arch/arm/dts/sun7i-a20-lamobo-r1.dts\n \n\n\n anyway to verify the u-boot does use this dt file ?\n \n", "name": "", "is_accepted": false }, { "text": "stop u-boot using <spacebar> during usb can, then do \"printenv\" command and check the value of \"fdtfile\"\n \n", "name": "", "is_accepted": false }, { "text": "thanks!\n \n\n\n \n i did it, and i see that: fdtfile=sun7i-a20-lamobo-r1.dtb \n i've also validate it with ${fdtfile} and it prints sun7i-a20-lamobo-r1.dtb\n \n\n\n i noticed that ${efi\\_fdtfile} prints nothing. is that ok? \n  \n \n\n\n dm tree prints the following:\n \n\n\n class index probed driver name\n-----------------------------------------------------------\n root 0 [ + ] root\\_driver root\\_driver\n simple\\_bus 0 [ + ] generic\\_simple\\_bus |-- soc@1c00000\n phy 0 [ + ] sun4i\\_usb\\_phy | |-- phy@1c13400\n usb 0 [ + ] ehci\\_generic | |-- usb@1c14000\n usb\\_hub 0 [ + ] usb\\_hub | | `-- usb\\_hub\n usb 1 [ + ] ohci\\_generic | |-- usb@1c14400\n usb\\_hub 1 [ + ] usb\\_hub | | `-- usb\\_hub\n usb 2 [ + ] ehci\\_generic | |-- usb@1c1c000\n usb\\_hub 2 [ + ] usb\\_hub | | `-- usb\\_hub\n usb\\_dev\\_ge 0 [ + ] usb\\_dev\\_generic\\_drv | | `-- generic\\_bus\\_2\\_dev\\_2\n clk 0 [ + ] sun4i\\_a10\\_ccu | |-- clock@1c20000\n reset 0 [ + ] sunxi\\_reset | | `-- reset\n gpio 0 [ + ] gpio\\_sunxi | |-- pinctrl@1c20800\n gpio 1 [ + ] gpio\\_sunxi | | |-- pa\n gpio 2 [ + ] gpio\\_sunxi | | |-- pb\n gpio 3 [ + ] gpio\\_sunxi | | |-- pc\n gpio 4 [ + ] gpio\\_sunxi | | |-- pd\n gpio 5 [ + ] gpio\\_sunxi | | |-- pe\n gpio 6 [ + ] gpio\\_sunxi | | |-- pf\n gpio 7 [ + ] gpio\\_sunxi | | |-- pg\n gpio 8 [ + ] gpio\\_sunxi | | |-- ph\n gpio 9 [ + ] gpio\\_sunxi | | `-- pi\n serial 0 [ + ] ns16550\\_serial | |-- serial@1c28000\n serial 1 [ ] ns16550\\_serial | |-- serial@1c28c00\n serial 2 [ ] ns16550\\_serial | |-- serial@1c29c00\n eth 0 [ + ] eth\\_designware | `-- ethernet@1c50000\n clk 1 [ + ] fixed\\_rate\\_clock |-- clk@1c20050\n clk 2 [ + ] fixed\\_rate\\_clock |-- clk@0\n clk 3 [ ] fixed\\_rate\\_clock |-- clk@1\n clk 4 [ ] fixed\\_rate\\_clock `-- clk@2\n\n\n\n  \n \n\n\n i  don't see any i2c bus in here.\n \n\n\n however i2c bus give: \n \n\n\nbus 0: twsi0\n\n\n  \n \n\n\n is that make sense?\n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "did you checked all the possible configs in your cache/source/u-boot/v2019.04/.config\n \n\n\n  \n \n\n\n by default, \"grep -i i2c\" is showing :\n \n\n\n  \n \n\n\n# config\\_i2c0\\_enable is not set\n# config\\_i2c1\\_enable is not set\n# config\\_i2c2\\_enable is not set\n# config\\_spl\\_i2c\\_support is not set\n# config\\_cmd\\_i2c is not set\n# i2c support\n# config\\_dm\\_i2c is not set\n# config\\_sys\\_i2c\\_dw is not set\n# config\\_sys\\_i2c\\_imx\\_lpi2c is not set\n# config\\_sys\\_i2c\\_mxc is not set\n# config\\_i2c\\_edid is not set\n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "i did checked it,\n \n\n\n and configs in your cache/source/u-boot/v2019.04/.config\n \n\n\n and cache/sources/u-boot/v2019.04/arch/arm/dts/sun7i-a20-lamobo-r1.dts\n \n\n\n seems to hold the same configuration...\n \n\n\n  \n \n\n\n perhaps i'm not defining the device tree correct at u-boot ? (this is the same as i did to the device tree in linux - and in linux it work)\n \n\n\n  \n \n\n\n&i2c3 {\n pinctrl-names = \"default\";\n pinctrl-0 = <&i2c3\\_pins\\_a>;\n status = \"okay\";\n};\n\n\n  \n \n\n\n jkjhk\n \n", "name": "", "is_accepted": false }, { "text": "but the \".config\" i've provided is \"default = no i2c\", you need to turn most of those to \"=y\" instead of \"is not set\" ...\n \n", "name": "", "is_accepted": false }, { "text": "first i must to correct my mistake:\n \n\n\n i meant that cache/source/u-boot/v2019.04/configs/lamobo\\_r1\\_defconfig and cache/source/u-boot/v2019.04/.config holds the same configuration.\n \n\n\n (i was afraid that maybe my modifications on lamobo\\_r1\\_defconfig doesn't set on .config)\n \n\n\n  \n \n\n\n in both lamobo\\_r1\\_defconfig and .config these are my modifications, but the i2c still doesn't work (or presented on the device tree) on u-boot:\n \n\n\n config\\_i2c0\\_enable=y\n \n\n\n config\\_i2c1\\_enable=y\n \n\n\n config\\_i2c2\\_enable=y\n \n\n\n config\\_i2c3\\_enable=y\n \n\n\n config\\_i2c4\\_enable=y\n \n\n\n config\\_dm=y \n config\\_dm\\_i2c=y \n config\\_dm\\_i2c\\_compat=y\n \n\n\n config\\_cmd\\_i2c=y   \n \n\n\n  \n \n\n\n i will keep digging, and share my results after solving the issue. i'm sure it will help to someone else in the future.\n \n\n\n ideas and suggestions are still very welcome (i'm sure it is possible. i'm not the first one that's trying it).\n \n\n\n thanks !!\n \n", "name": "", "is_accepted": false } ]

[ { "text": "@tcb13 i am a bit late to the party but i figured it may still be needed ;-)\n \n\n\n  \n \n\n\n spi-spidev is a special / dynamic overlay. besides enabling it you need to also configure it and armbian-config cannot currently do that.\n \n\n\n  \n \n\n\n for configuration options have a look here:\n \n\n\n https://github.com/armbian/build/blob/master/patch/kernel/archive/rockchip64-5.10/general-rockchip-overlays.patch#l98-l126\n \n\n\n you can also consult the local readme file located in: /boot/dtb/rockchip/overlay/readme.rockchip-overlays\n \n", "name": "", "is_accepted": true }, { "text": "your issue report is not a valid bug report per the armbian bug reporting instructions (https://www.armbian.com/bugs).  with limited resources the armbian project is only able to spend time on issues where all the requested information has been provided and for only the boards/images/software that are supported.  your report is invalid for one or more of the following reasons (non-exhaustive list):\n \n\n\n  \n \n\n\n \n it is for an unsupported board or image (csc/eos/wip/edge)\n \n \n it is for software that is not supported (such as userspace modules installed on top of the core operating system)\n \n \n it has been logged in the wrong forum (for example requests for help that are not actual bug reports)\n \n \n it lacks requested data (armbianmonitor output)\n \n \n it could have been easily solved by a quick search and/or reading documentation\n \n\n\n\n  \n \n\n\n please review what you have submitted and the bug logging instructions (https://www.armbian.com/bugs) and either add the required information or open a new topic in the correct forum (such as common issues / peer to peer technical support or general chit chat)\n \n", "name": "", "is_accepted": false }, { "text": "i'm sorry but...\n \n\n\n \n it is for an unsupported board or image (csc/eos/wip/edge) > it's a supported board\n \n \n it is for software that is not supported (such as userspace modules installed on top of the core operating system) > no\n \n \n it has been logged in the wrong forum (for example requests for help that are not actual bug reports) > no, its a bug.\n \n \n it lacks requested data (armbianmonitor output) > not relevant in this case.\n \n \n it could have been easily solved by a quick search and/or reading documentation > ??\n \n\n", "name": "", "is_accepted": false }, { "text": "okay, you win i'll provide the file asap.\n \n", "name": "", "is_accepted": false }, { "text": "@werner this image might send a wrong message. there is still absolutely no warranty that any support will be provided even board is declared as supported.\n \n\n\n  \n \n\n\n\n\n \n if a few days will be needed to solve this problem, what you will do?\n \n", "name": "", "is_accepted": false }, { "text": "i'll wait patiently for some news. it's not a life or death situation \n \n", "name": "", "is_accepted": false }, { "text": "fyi. a few days of debugging costs few thousand eur. we have 0 eur budget per year for that. patiently waiting for donation that will cover the time dealing with this problem so we can hire someone to fix this for you. if this is not life and death, this will not be a problem. i can afford only a few minutes per bug or per \"client\". usually less then 1m. for debugging help - my first available pro bono days are not this year ... wrote on mobile ", "name": "", "is_accepted": false }, { "text": "i think there is a misunderstanding here, i never requested support in \"record time\" and i certainly didn't said that it needs to happen fast. i just said i would upload my log file as soon as i can.\n \n\n\n  \n \n\n\n i'm happy with the \"few minutes\" whenever you guys have some spare time!\n \n", "name": "", "is_accepted": false }, { "text": "agree.\n \n\n\n  \n \n\n\n\n\n  \n \n\n\n all support requests are denied by default. there is no support the way you imagine. check your contract terms: \n https://github.com/armbian/build#support\n \n", "name": "", "is_accepted": false }, { "text": "as entertaining as this thread is so far, i suggested to @tcb13 to post here to get more eyes on the problem.\n \n\n\n  \n \n\n\n i can confirm that enabling the overlay in question didn't do the expected thing. and \"armbianmonitor -u\" is here: http://ix.io/3ns8\n \n\n\n  \n \n\n\n interestingly, the overlay seems to be disabling the spidev?\n \n\n\n  \n \n\n\n fragment@4 {\n target = <0xffffffff>;\n\n \\_\\_overlay\\_\\_ {\n #address-cells = <0x01>;\n #size-cells = <0x00>;\n\n spidev {\n compatible = \"spidev\";\n status = \"disabled\";\n reg = <0x00>;\n spi-max-frequency = <0x989680>;\n };\n };\n };\n\n\n  \n \n\n\n offhand, i'm not sure what's required to switch between multi-function pins, but figured there would be far more eyes on the problem here rather than peer to peer support.\n \n", "name": "", "is_accepted": false }, { "text": "never late to the party! thank you for your tips.\n \n\n\n  \n \n\n\n btw, for future reference fro anyone going about the same path, page 11 of the nanopi m4v2 schematic contains a definition of the spi1 that can be easily between the overlay and physical pins.\n \n\n\n  \n \n\n\n schematic: http://wiki.friendlyarm.com/wiki/images/c/cc/nanopi-m4v2\\_1908\\_schematic.pdf\n \n\n\n physical pin assignment: https://wiki.friendlyarm.com/wiki/index.php/nanopi\\_m4v2#diagram.2c\\_layout\\_and\\_dimension\n \n\n\n  \n \n\n\n \n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "your comment was crucial to fix my \"issue\". i enabled the overlay and then as described on the file edited `/boot/armbianenv.txt` in order to include:\n \n\n\n  \n \n\nparam\\_spidev\\_spi\\_bus=1\nparam\\_spidev\\_max\\_freq=100000000\n\n\n  \n \n\n\n now the spi shows up:\n \n\n~# ls -la /dev/spi*\ncrw------- 1 root root 153, 0 sep 16 18:51 /dev/spidev1.0\n\n\n  \n \n\n\n also passes the spidev\\_test (https://raw.githubusercontent.com/torvalds/linux/master/tools/spi/spidev\\_test.c)\n \n\n~# ./spidev\\_test\nspi mode: 0x0\nbits per word: 8\nmax speed: 500000 hz (500 khz)\n\n\n  \n \n (had to adjust the path)\n \n\n\n\n  \n \n\n\n thank you for the tip!\n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "now unfortunately luma-oled seems to be yet another problem. i wired up my lcd as:\n \n\n\n \n mosi > gpio1\\_a7 > spi1\\_rxd > m4 pin 21   > lcd din pin (blue) \n sck > gpio1\\_b1 > spi1\\_clk > m4 pin 23     > lcd clk pin (yellow) \n cs > gpio1\\_b2  > spi1\\_csn0 > m4 pin 24    > lcd cs pin (orange)\n \n\n\n  \n \n\n\n dc > gpio1\\_a0(3v) > m4 pin 7        >   lcd dc pin (green)\n \n\n\n rst > gpio1\\_a1(3v) > m4 pin 11    >   lcd rst pin (white)\n \n\n\n  \n \n\n\n from my understanding i had to get gpio1\\_a0 and gpio1\\_a1 in the system so the lib could use them.\n \n\n\n according to this https://hev.cc/2927.html gpio mapping i tried:\n \n\n\n  \n \n\nls -la /dev/spi*\ncrw------- 1 root root 153, 0 sep 16 18:51 /dev/spidev1.0\n\necho 32 > /sys/class/gpio/export\necho 33 > /sys/class/gpio/export\n\nls -la /sys/class/gpio/\ntotal 0\ndrwxr-xr-x 2 root root 0 jan 18 2013 .\ndrwxr-xr-x 76 root root 0 jan 18 2013 ..\n--w--w---- 1 root dialout 4096 sep 16 20:51 export\nlrwxrwxrwx 1 root root 0 sep 16 20:50 gpio32 -> ../../devices/platform/pinctrl/gpiochip1/gpio/gpio32\nlrwxrwxrwx 1 root root 0 sep 16 20:50 gpio33 -> ../../devices/platform/pinctrl/gpiochip1/gpio/gpio33\nlrwxrwxrwx 1 root root 0 jan 18 2013 gpiochip0 -> ../../devices/platform/pinctrl/gpio/gpiochip0\nlrwxrwxrwx 1 root root 0 jan 18 2013 gpiochip128 -> ../../devices/platform/pinctrl/gpio/gpiochip128\nlrwxrwxrwx 1 root root 0 jan 18 2013 gpiochip32 -> ../../devices/platform/pinctrl/gpio/gpiochip32\nlrwxrwxrwx 1 root root 0 jan 18 2013 gpiochip64 -> ../../devices/platform/pinctrl/gpio/gpiochip64\nlrwxrwxrwx 1 root root 0 jan 18 2013 gpiochip96 -> ../../devices/platform/pinctrl/gpio/gpiochip96\n--w--w---- 1 root dialout 4096 sep 16 19:19 unexport\n\n\n  \n \n\n\n now i tried the luma-oled examples (running as root):\n \n\n\n  \n \n\npython3 3d\\_box.py --display ssd1351 --interface spi --spi-port 0 --spi-device 1 --gpio-reset 33 --gpio-data-command 32 --width 128 --height 128\nusage: 3d\\_box.py >(....)\n3d\\_box.py: error: gpio access not available\n\n\n  \n \n\n\n i'm not even sure if this part \"--gpio-reset 33 --gpio-data-command 32\" is correct. i've tried both the virtual pin number and the hardware number without luck.\n \n\n\n  \n \n\n\n also tried to install https://github.com/friendlyarm/rpi.gpio\\_np without much luck:\n \n\n\n  \n \n\napt-get update\napt-get install python-dev\ngit clone https://github.com/friendlyarm/rpi.gpio\\_np\ncd rpi.gpio\\_np\npython3 setup.py install\npython3 setup.py install\n\npython3 luma.examples/examples/3d\\_box.py --display=ssd1351 --interface=spi --width=128 --height=128 --spi-bus-speed=16000000 --bgr --spi-device=1 --spi-port=0 --gpio-reset=33 --gpio-data-command=32 --gpio rpi.gpio\n\ntraceback (most recent call last):\n(...)\nruntimeerror: it is not nanopi based board.\n\n\n  \n \n", "name": "", "is_accepted": false } ]

[ { "text": "attached is jernej's patch, slightly modified to work with 5.10.13, sorry for posting it here. the overscan issue can be fixed with this tool, https://projects.nwrk.biz/projects/allwinner-tvout/wiki, this was described in this forum but i don't have the link. the washed out (hardware) issue has also been described here and can be easily fixed with a resistor. there are also drm properties for dealing with tv offsets and sizing issues but i have not figured out where to put them in the user level device tree, does anyone know? (i tried put them under the tve node but didn't work.) the properties are described here: https://www.kernel.org/doc/html/v4.12/gpu/drm-kms.html?highlight=drm tv#existing-kms-properties\n \n\n\n zzzz-tv-cvbs.patch\n \n\n\n  \n \n\n\n patch was tested to work with zero, and neo...\n \n", "name": "", "is_accepted": true }, { "text": "i apologize. yes, jernej hasn't actually said what i've instead said but just that there is a lot of work (optimizations) to do. i've said it my way which is the wrong way because linked with my very very limited knowledge, not armbian fault nor its developers. you're absolutely right and i can only apologize.\n \n", "name": "", "is_accepted": false }, { "text": "the thing is that everything is in state of flux. cedrus driver was first one which introduced new kernel api for video decoding, which is now also supported with rkvdec and hantro. you can imagine that a lot of stuff needed to be written. only now interface is becoming stable and thus we can now start upstreaming changes. but that takes time...\n \n\n\n  \n \n\n\n it's certainly possible to have great kodi experience on armbian, if you know what to patch. but currently it takes a couple dozens of patches at least for kernel and ffmpeg to achieve that, so i wouldn't recommend to do it yourself, except if you really want to learn how things work. good thing is that with every kernel iteration, amount of patches is lowered.\n \n", "name": "", "is_accepted": false }, { "text": "...and a different api than amlogic meson vdec, correct? and all the developers that were working on the meson driver are off the grid since early 2020, is that correct too?\n \n\n\n  \n \n\n\n i'm asking this just to evaluate the challenges i'll have to face before moving on to create a unified kodi for armbian mainline, which was my original idea once i brush up the last details for the legacy kodi's.\n \n\n\n  \n \n\n\n btw, you mentioned it is necessary to use kodi patches too. i was aware of the ffmpeg and kernel patches, but thought that vanilla matrix would work. what are these patches related to?\n \n\n\n  \n \n\n\n (sorry for hijacking the thread, i can move these posts to a different one if it gets too messy)\n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "yes, meson uses stateful whereas cedrus and rkvdec use stateless (request api).\n \n\n\n\n\n actually only one really worked on this driver but stopped working on most (all?) things due to real-life issues.\n \n\n\n\n\n vanilla kodi will work for video decoding, but if you want hw deinterlacing, that will need kodi patch and additional one for ffmpeg.\n \n", "name": "", "is_accepted": false }, { "text": "i'd really like to, a lot! unfortunately, i fear there aren't guides to be found online on this, just books which need to be studied from the beginning to the end and they're still not enough. what really matters is a lot of experience, the one you both have.\n \n\n\n you both aren't hijacking anything. seeing people who know what they're talking about sharing their thoughts to find solutions is a pleasure. gaining just one thousandth of your knowledge would make me pride. what i think is that you and all the developers are doing a great work which deserves to be praised.\n \n", "name": "", "is_accepted": false }, { "text": "hello again. i've made some very little progress... i've tried to undestand at my best the advices given by yam1 here. what i've done is removing these lines from jernej's patch:\n \n\n\n  \n \n\n\nstatic const struct regmap\\_config sun8i\\_mixer\\_regmap\\_config = {\n@@ -560,6 +585,15 @@ static const struct sun8i\\_mixer\\_cfg sun8i\\_h3\\_mixer0\\_cfg = {\n .vi\\_num = 1,\n };\n \n+static const struct sun8i\\_mixer\\_cfg sun8i\\_h3\\_mixer1\\_cfg = {\n+ .ccsc = 1,\n+ .mod\\_rate = 432000000,\n+ .scaler\\_mask = 0x3,\n+ .scanline\\_yuv = 2048,\n+ .ui\\_num = 1,\n+ .vi\\_num = 1,\n+};\n+\n\n\n  \n \n\n\n which is downloadable here. what i believe to be the original patch yam1 is talking about should be this one but honestly speaking i haven't understood what to do with it so i've tried to build again with just the aforementioned modification. to my surprise, this time the build has gone fine and i've got an image (without desktop as adviced by jernej given that my purpose is using kodi). i've had some issues transferring the image from my vagrant vm to the host but finally i've solved it thanks to the guide i've found here (something more learnt!). i haven't still had the chance to test that image so i can't say anything more than this but i'm quite doubtful it would work. at least, this way the patch has been taken up fine without causing an unsuccessful build like before, a small achievement!\n \n", "name": "", "is_accepted": false }, { "text": "i made patch for clean kernel source. if that part fails for some reason, i would recommend to remove any other which would have that...\n \n", "name": "", "is_accepted": false }, { "text": "i need to admit i hadn't bet a penny on this but i can confirm that just making that modification to jernej's patch was enough to get a working tv out on my opi pc, currently on armbian\\_21.02.0-trunk\\_focal\\_current with kernel 5.10.13-sunxi. the video is washed out (while it was perfect before with the ancient armbian 5.90 xenial, i don't know why) and the resolution is wrong so there is still plenty of work to do and even much more to come to get kodi working in a satisfactory way (probably i wouldn't ever be able to achieve that goal) but by now at least a little result gained!\n \n\n\n  \n \n\n\n edit: i attach a picture of the image. the quality is really bad while it was fine before as already said. maybe it has something to do with the lines i've removed from the patch, i don't know. i've also tried to modify the resolution editing /boot/armbianenv.txt setting disp\\_mode=576x480p60 but it seems the change isn't even taken into account.\n \n\n\n  \n \n\n\n \n \n", "name": "", "is_accepted": false }, { "text": "@yam1\n \n\n\n  \n \n\n\n thanks for the modified version of the patch along with all the other advices. i knew the resistor thing (jmcc had already told me that in this thread) but what made me think was the fact that, maybe i hadn't noticed it being under x11 instead of cli, it seemed to me the issue wasn't present while i was under armbian 5.90 xenial. i repeat, probably i haven't just noticed it.\n \n\n\n  \n \n\n\n in the meantime, just to 'play' a bit, here is what i've done (everything made as root user):\n \n\n\n  \n \n\n\napt-get update && apt-get install kodi xorg xterm\n\n\n  \n \n\n\n then, following this very well done guide, i've issued:\n \n\n\n  \n \n\n\nxinit kodi $* -- :1\n\n\n  \n \n\n\n and i've seen the kodi interface again on my opi pc! just a quick and dirty approach, i know. there is much more work to do... thanks to the all of you! \n \n", "name": "", "is_accepted": false }, { "text": "drm properties are not meant to be used in device tree. first, driver must register them and use them(which sun4i\\_tv driver does not) and then user space app must set them via drm ioctl, but that usually goes through libdrm. useful tool for drm properties is modetest app, which is part of libdrm test tools.\n \n\n\n  \n \n\n\n @guybrushthreepwood you'll be limited to sw decoding approach that way...\n \n", "name": "", "is_accepted": false }, { "text": "i can confirm that allwinner\\_tvout\\_manipulator works like a charm. i've downloaded the latest version, built it and solved the overlay issue. thanks to yam1 for pointing it out! this should be the thread on the forum where it was mentioned with a detailed usage explanation too.\n \n\n\n unfortunately, i can also confirm that the resolution can't be changed by just editing disp\\_mode in /boot/armbianenv.txt because, no matter what value i input there, i get no changes at all nor the .fex approach which was valid for the older kernels applies (but i knew that since the opening post of this thread). i need to go deeper on that.\n \n\n\n  \n \n\n\n @jernej\n \n\n\n  \n \n\n\n yes, you're completely right and this was the reason why i've written i was just playing. bearing in mind what you've already told me in the previous posts, this is the fartest thing from an enjoyable kodi experience and unfortunately i know that. still a lot to do...\n \n\n\n 'just' a question... you've talked about the heavy need for patching, both on kernel side and on the sources for kodi and ffmpeg and this has already been done for libreelec: does this mean that digging on the forum there i could scour some hints? i'm not asking for the links to the threads, just if it is actually the right place to search. if, instead, the answers are inside the sources for libreelec, then it is definitively beyond my knowledge unfortunately.\n \n", "name": "", "is_accepted": false }, { "text": "probably, but even more by looking at the libreelec sources on github. documentation is minimal, but the sources are very intuitive.\n \n\n\n  \n \n\n\n but, before that, you must read the docs about kodi compilation at the xbmc github.\n \n", "name": "", "is_accepted": false }, { "text": "not sure what kind of hints you want, but yes, i think i mentioned already which patches needs to be taken and which ffmpeg config options needs to be used. but as jmcc said, it's best if you check le sources on gh directly. patches are regularly updated.\n \n", "name": "", "is_accepted": false }, { "text": "@jmcc@jernej\n \n\n\n  \n \n\n\n thanks to the both of you! \n \n\n\n  \n \n\n\n\n\n  \n \n\n\n already done! i'm a bit familiar with that stuff, the problem is what comes before having something to compile... have a nice day.\n \n\n\n  \n \n\n\n   \n \n\n\n\n\n  \n \n\n\n mainly on what does need to be patched but, as you both confirm to me, the answers are inside the sources. a nice day to you too.\n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "i created kodi packages for v4l2-request, tested on orange pi+2e (allwinner h3) running armbian bullseye with the current 5.10.y kernel.\n \n\n\n  \n \n\n\n so far, hw video playing works fine with mpeg2 and h.264 up to 1080p. kernel patches are needed to improve resolution and codec support. gui performance is just enough, but it can probably be also improved with kernel patches.\n \n\n\n  \n \n\n\n so the userspace part is now working, the kernel improvements remain in the to-do list.\n \n\n\n  \n \n\n\n packages can be found here: https://users.armbian.com/jmcc/packages/kodi-mainline/\n \n\n\n  \n \n\n\n these should still be considered wip, although fully functional already. instructions:\n \n\n\n \n download the packages for your architecture, and install them with \"dpkg -i\".\n\n \n \n only kodi-mainline and kodi-mainline-bin are essential, the others are optional.\n \n \n \n \n run \"apt -f install\"\n \n \n make sure there is no x server running, and start kodi from console typing \"kodi\"\n \n\n\n\n @balbes150 you may be interested in this. they should also work in rockchip, but i haven't tested yet.\n \n", "name": "", "is_accepted": false }, { "text": "@jmcc\n \n\n\n  \n \n\n\n thanks for your great effort! it has taken me a while to come back because my image was ubuntu based and, at least by what i know, installing debian packages on ubuntu isn't a good practice. i've therefore built a new image based on ubuntu buster (i don't know why bullseye isn't an option: maybe it's still the testing branch and there is another way i'm not aware of to build it), still with tv-out enabled, just applying the same changes discussed before. i've then added the repositories for debian bullseye and this way i've been able to install all the needed dependencies for the two 'base' packages kodi-mainline and kodi-mainline-bin.\n \n\n\n here come the issues, probably if not certainly due to my dirty approach of creating an 'hybrid' buster/bullseye system. as a remote i use my smartphone with yatse: i can configure and connect it to my opi pc just fine but then it works erratically: sometimes i can control it, sometimes not in spite of the fact the connection is always reported as being fine. with kore, no issues at all.\n \n\n\n another issue is tvheadend server. if i try to just install the kodi-pvr-hts package by apt-get it replaces jmcc's kodi with the matrix version from the repositories so i've tried to build it by myself but i've failed because of issues related to ffmpeg as anticipated both by jmcc and jernej. i could easily add support for my xbox one tuner but without tvheadend it's just pointless.\n \n\n\n the worst problem so far is that, in spite of the fact that kodi reports a successful connection to the internet, i can't manage to install anything from the repositories, not the official one nor the kodi nerds one i've tried to add. no connection to either of them. we're completely going off topic here though, i know and i apologize.\n \n", "name": "", "is_accepted": false } ]

[ { "text": "thanks for your reply. i realized that docker was also installed when installing home assistant so i completely removed docker (by \"apt remove docker-ce*\") and did a \"find\" with *hass*. afterward i removed all found *hass*-files manually. worked fine.\n \n", "name": "", "is_accepted": true }, { "text": "you will have to check the home-assistant documentation on how to remove it completely.   \n \n\n\n armbian-config/softy does not have a remove feature build in.\n \n\n\n  \n \n\n\n see also:\n \n\n\n\n  \n \n\n\n  \n \n", "name": "", "is_accepted": false } ]

[ { "text": "embedded in the message above.\n \n\n\n  \n \n\n\n and implemented.\n \n\n\n marking as solved (again) \n \n", "name": "", "is_accepted": true }, { "text": "what about using forum messaging / email system? register at https://www.ipfire.org/ and you will see what i mean by that. its effective and imo overall less disturbing.\n \n\n\n  \n \n\n\n\n\n  \n \n\n\n most of people are nice. they do deserve to be handled this way ... until we have to deal with damaging ass-hole.  \n\n\n \n a lot of people are too lazy to use search ... we can improve that with proper communication and with tagging and merging.\n \n", "name": "", "is_accepted": false }, { "text": "i suppose i would think some sort of canned reply welcome message to be less personal. i did not register at ipfire so maybe they are doing something different than what i am expecting.\n \n\n\n  \n \n\n\n plus my thought was to create a culture of welcoming people. by doing so publicly, it may catch on, become self-perpetuating (to an extent)... which, i suppose would be good or bad depending on your viewpoint...\n \n\n\n  \n \n\n\n yes i am aware of \"takers\" and \"help vampires\" who do not contribute and therefore do not add to the community. not saying to blanket send everyone the same message, which would be the same as an impersonal canned reply, but rather (and especially) when someone first post is contributing good information, data points, etc. to welcome those sort of people to the community. you never know where the next contribur may eventually come from...\n \n\n\n  \n \n\n\n others who clearly have not read the most basic of things would still get a different sort of \"greeting\"...\n \n", "name": "", "is_accepted": false }, { "text": "try and wait few days. you can feel someone worked on that. perhaps that is some ready made welcome, build-in forum which i hardly believe ... but still, its nice.\n \n\n\n  \n \n\n\n\n\n  \n \n\n\n if this will level up the forum culture while not making more pressure on developers and maintainers ... why not. i mean, how would we get anywhere without changing anything. make a plan, let's discuss it - consider my suggestions as from any regular user and then put into action.\n \n\n\n  \n \n\n\n\n\n \n i am sometimes too emotional and get pissed off - you, on the other hand, can be more detach and act more politically correct in term of pure abuse from the users side. my tolerance is low to be nice and friendly when i see that ...\n \n", "name": "", "is_accepted": false }, { "text": "ok, maybe i will give ipfire a test just to see what you are talking about.\n \n\n\n  \n \n\n\n on your last two points, yes this is sort of what i am getting at. trying to promote a culture of contribution and helping each other, and being a buffer so you guys can go off and do your wizard stuff and not spending all your time (and perhaps more importantly, emotional energy) on support. i think the carrot is just as important as the stick (not sure if that phrase translates culturally?). you know, positive reinforcement. and just plain being friendly. especially to people who are contributing!\n \n\n\n  \n \n\n\n one of the things attracting me to this community initially was the clearly high level of technical competence and no-nonsense approach and honestly i think we should keep that. but at the end of the day we are all human beings, i don't see the harm (for someone like me, who is more focused on the \"community\" via forums (and irc)) to try and be a little more welcoming. overall i don't want to change the existing culture, which i see as good. i just want to allow some of my innate friendliness to come through, and welcome newcomers. cheers! \n \n", "name": "", "is_accepted": false }, { "text": "imho in technical themes do not need \"empty\" greetings. create a separate topic (or section) for \"universal\" communication and \"greetings\". to evaluate the usefulness of a message, there is a mechanism for likes, which shows the user well the value of his message to others.\n \n\n\n  \n \n\n\n ps i do not impose my point of view on anyone, you can do as you see fit.\n \n", "name": "", "is_accepted": false }, { "text": "i already decided several days ago (maybe almost a week by now) not to publicly do this (unless i am already replying to their post otherwise).\n \n\n\n  \n \n\n\n if i feel their first post was good enough (contributing especially) i will often send a pm telling them so and welcoming them to the forum.\n \n\n\n  \n \n\n\n thanks everyone for feedback.\n \n", "name": "", "is_accepted": false }, { "text": "to give this in the meantime a bit aged idea a new bump i'd suggest to use the \"profile completion\" feature for that purpose. it is indeed not exactly the same but offers us the opportunity to get some text boxes to new users and suggest them to do something. like this:\n \n\n\n  \n \n\n\n \n \n", "name": "", "is_accepted": false }, { "text": "and my 2c in this context: \n  \n \n\n\n\n\n \n https://invisioncommunity.com/files/file/7449-auto-welcome/\n \n", "name": "", "is_accepted": false }, { "text": "i usually prefer trying to solve things with the possibilities we have but in this case this seems the best solution, also because it is a free addon that seem to get frequent updates with is an important factor. bring it on \n \n", "name": "", "is_accepted": false }, { "text": "aight since i finally had a chance to make some thought about this here is me configuration suggestion:\n \n\n\n a dummy account ( @welcome bot ) is created to send a personal message one hour after registration. unfortunately it is not possible to trigger this by post count, only by validation status which is impractial for us since this period can be quite long (waiting time after first approval or become donator or get a like).\n \n\n\n the content as first draft:\n \n\n\n  \n \n\n\n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "enabled. now lets see if it works.\n \n", "name": "", "is_accepted": false }, { "text": "great!\n \n\n\n  \n \n\n\n perhaps mention - in a proper tone - that they are entering trial mode with certain limitations for one week and what to do to speed things up?\n \n", "name": "", "is_accepted": false }, { "text": "i'll think about that.\n \n", "name": "", "is_accepted": false }, { "text": "how's that?\n \n", "name": "", "is_accepted": false }, { "text": "good. i would only add a link to search where it is mentioned. perhaps to the general armbian.com/search\n \n", "name": "", "is_accepted": false }, { "text": "in order to minimise questions \"why i am limited to one post per day\" ... adding that info here and showing it on the forum as a notice - as an advertisement to all users in a group validating? and perhaps question the limits all over again. are they too strict? should we adjust them a bit?\n \n", "name": "", "is_accepted": false }, { "text": "i think they could be lifted a bit. does not look too bad atm.\n \n", "name": "", "is_accepted": false } ]

[ { "text": "the 'desktop-image' doc i was comparing the '.asc-doc' against was not a desktop image. changed it and it worked. \n \n\n\n  \n \n\n\n thx\n \n", "name": "", "is_accepted": true }, { "text": "for example, those links always redirect you to the latest version: \n https://redirect.armbian.com/orangepiplus2e/bionic\\_current\n \n\n\n https://redirect.armbian.com/orangepiplus2e/bionic\\_current.sha\n \n\n\n  \n \n\n\n while actual files are changing. paired sha should always fit. \n \n\n\n  \n \n\n\n is this the problem?\n \n", "name": "", "is_accepted": false }, { "text": "hi igor, thanks. but i'm not sure i understand. i'm using buster and those links are for bionic. but i will test what i think you may be trying to say. \n \n\n\n  \n \n\n\n my guess is that the best thing is to verify the checksum signature.  i thought there was a link on armbian.com for that, but don't seem to be able to find it. \n \n\n\n  \n \n\n\n i also recall having some trouble figuring out how to do it. anyway, could you provide a link for instructions?\n \n\n\n thanks\n \n", "name": "", "is_accepted": false }, { "text": "sorry, i mixed but its the same. replace bionic with buster in the url and try.\n \n\n\n  \n \n\n\n\n\n  \n \n\n\n first is data integrity checking\n \n\n\n https://docs.armbian.com/user-guide\\_getting-started/#how-to-check-download-integrity\n \n\n\n , while signature is authenticity checking - if image was made by us: \n https://docs.armbian.com/user-guide\\_getting-started/#how-to-check-download-authenticity\n \n", "name": "", "is_accepted": false }, { "text": "thanks igor. \n \n\n\n  \n \n\n\n as for trying to verify the signature - i'm getting closer, but apparently still doing something incorrect. \n \n\n\n  \n \n\n\n i have in the same directory: the \".img\" and the \".asc\", and nothing else. i open a terminal there and then run the following:\n \n\n\n  \n \n\n\n $ sudo gpg --verify armbian\\_20.05.2\\_orangepiplus2e\\_buster\\_current\\_5.4.43.img.xz.asc [sudo] password for b:\n \n\n\n  \n \n\n\n output: gpg: no signed data gpg: can't hash datafile: no data \n \n\n\n  \n \n\n\n or is the output for signature telling me the checksum is not valid? \n \n\n\n  \n \n\n\n =========================================================================== \n \n\n\n  \n \n\n\n downloading your public key: (i don't know why, but your public key almost never downloads/imports; i got lucky importing it once out of many tries; wish i knew why...)\n \n\n\n  \n \n\n\n # download public key from the database \n \n\n\n sudo gpg --keyserver ha.pool.sks-keyservers.net --recv-key df00faf1c577104b50bf1d0093d6889f9f0e78d5\n \n\n\n  \n \n\n\n output: sudo gpg --keyserver ha.pool.sks-keyservers.net --recv-key df00faf1c577104b50bf1d0093d6889f9f0e78d5 gpg: /root/.gnupg/trustdb.gpg: trustdb created gpg: key 93d6889f9f0e78d5: public key \"igor pecovnik <[email protected]>\" imported gpg: total number processed: 1 gpg: imported: 1\n \n\n\n  \n \n\n\n thanks. \n \n", "name": "", "is_accepted": false }, { "text": "not a problem of my public key, but a problem of public key server. \n \n\n\n  \n \n\n\n\n\n \n after you loaded key or before?\n \n", "name": "", "is_accepted": false }, { "text": "hi igor. i loaded the key before anything else, your key ...import, if that's what you mean. \n \n\n\n  \n \n\n\n after i import your key with the command line, is there anything else i need to do, such as with my 'key management - kgpg' .... \"import keys\". \n \n\n\n  \n \n\n\n the command said it was imported, but i don't know where to check to see if yours is there; not sure if i'm supposed to be able to see it...?\n \n\n\n  \n \n\n\n thanks. \n \n", "name": "", "is_accepted": false }, { "text": "i don't know what you are doing wrong. i just recreated on a clean build: \n  \n \n\n\ngpg --keyserver ha.pool.sks-keyservers.net --recv-key df00faf1c577104b50bf1d0093d6889f9f0e78d5\ngpg: directory '/root/.gnupg' created\ngpg: keybox '/root/.gnupg/pubring.kbx' created\ngpg: /root/.gnupg/trustdb.gpg: trustdb created\ngpg: key 93d6889f9f0e78d5: public key \"igor pecovnik <[email protected]>\" imported\ngpg: total number processed: 1\ngpg: imported: 1\n\nwget https://redirect.armbian.com/odroidn2/bionic\\_current\\_desktop\nwget https://redirect.armbian.com/odroidn2/bionic\\_current\\_desktop.asc\n\ngpg --verify bionic\\_current\\_desktop.asc \ngpg: assuming signed data in 'bionic\\_current\\_desktop'\n\ngpg: signature made tor 01 sep 2020 20:30:24 cest\ngpg: using rsa key df00faf1c577104b50bf1d0093d6889f9f0e78d5\ngpg: good signature from \"igor pecovnik <[email protected]>\" [unknown]\ngpg: aka \"igor pecovnik (ljubljana, slovenia) <[email protected]>\" [unknown]\ngpg: warning: this key is not certified with a trusted signature!\ngpg: there is no indication that the signature belongs to the owner.\nprimary key fingerprint: df00 faf1 c577 104b 50bf 1d00 93d6 889f 9f0e 78d5\n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "to clarify: actually, the 'formula' ran and gave a typical output whereas before it did not, so that was a success in itself. however, i did get a 'bad signature'. but at least i am now comfortable checking the signature, so it was still a success \n \n", "name": "", "is_accepted": false } ]