Datasets:

---

clips

/

mqa

like 52

Follow

CLiPS 10

[ { "text": "i have found the solution. the bus number must be 1, not 0 as explained everywhere. this will create the device /dev/spidev1.0 instead of spidev0.0 and applications must be adapted. but with this modification i can access the spi device.\n \n\n\n  \n \n\n\n so here's the relevant overlay configuration in /boot/armbianenv.txt:\n \n\noverlays=spi-spidev\nparam\\_spidev\\_spi\\_bus=1\n\n\n\n  \n \n\n\n and the spi interface can be used only under this path: /dev/spidev1.0\n \n\n\n  \n \n\n\n who knows where that bus number 0 leads to...\n \n", "name": "", "is_accepted": true }, { "text": "about forum operational status:https://status.armbian.com/785767245\n \n\n\n no idea where your issues come from.\n \n\n\n  \n \n\n\n about spi: maybe you need to set additional parameters:https://docs.armbian.com/user-guide\\_armbian\\_overlays/#notes-regarding-spi-and-i2s-overlays\n \n", "name": "", "is_accepted": false }, { "text": "i guess you mean the param\\_spidev\\_spi\\_bus parameter? sorry, i've pasted the complete file in the other response that never made it to the forum. here is the file /boot/armbianenv.txt:\n \n\n\n  \n \n\nverbosity=1\nlogo=disabled\nconsole=serial\ndisp\\_mode=1920x1080p60\noverlay\\_prefix=sun8i-h3\noverlays=spi-spidev usbhost2 usbhost3\nparam\\_spidev\\_spi\\_bus=0\nrootdev=uuid=4a65461e-d8ac-4d8f-94c0-05ecd12f6d58\nrootfstype=ext4\nusbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u\n\n\n  \n \n\n\n i used armbian-config to enable spi and also read that i need to manually add this parameter to the file. that's where i am now. i followed the pinout from this image (and many others which look the same): \n \n\n\n  \n \n\n\n i have now also verified that the pins work correctly as gpio with the spi overlay disabled. so it's not a hardware failure. the software just isn't sending any spi signal. sclk, mosi and cs0 remain low at all times when sending to spi.\n \n", "name": "", "is_accepted": false }, { "text": "glad you could figure it out. i have added a note regarding this to the documentation: https://github.com/armbian/documentation/commit/6b9bceedb28ff3b3d0590b21e9ca4a52487bb22b\n \n", "name": "", "is_accepted": false } ]

[ { "text": "@hsesyou can try archived images. https://armbian.hosthatch.com/archive/rockpi-4b/archive/ \n 5.8 should work. you can then update/upgrade. \n @igorall rk3399 images seem troubled. i'm waiting to release a video about the buster media script since no buster legacy image works on download page for rk3399. there are enough ways to make it work with either self build, archived or @balbes150 images. \n i hope the beast will soon flex its muscles  \n \n", "name": "", "is_accepted": true }, { "text": "fixed in sources - you need to build on your own or wait we refresh images.  when? when we find time. \n  \n \n\n\n\n\n \n ... is completely different hardware and not officially supported by armbian anymore.\n \n", "name": "", "is_accepted": false }, { "text": "and don't update u-boot ... since u-boot in repository is still broken. since this is manual procedure, this is not that problematic ...\n \n\n\n  \n \n\n\n\n\n \n maintaining legacy kernels is nightmare ... \n \n\n\n  \n \n\n\n\n\n \n you mean they work if you build them from sources, but not from the download section? time for another round of bufix upgrade ... i am working on stabilising 5.10.y builds on all images and so far we are close to go.\n \n", "name": "", "is_accepted": false }, { "text": "actually not. i build buster legacy for p1 with the desktop branche and there's no hdmi at boot. i used balbes image instead and this worked fine.  \n i've not tried m4/m4v2 builds. there it was another problem with the rockpi4 bt driver. that should be fixed. i'll try building buster legacy for m4v2 and see this works. the p1 isn't as important as the m4/m4v2/rockpi4.\n \n", "name": "", "is_accepted": false }, { "text": "that is expected. we don't support p1.\n \n\n\n  \n \n\n\n in the making\n \n\n\n https://github.com/armbian/build/pull/2508\n \n", "name": "", "is_accepted": false }, { "text": "good. i am also working on some multimedia kernel-related stuff for legacy rk3399's, i am planning to push the changes very soon too. btw, i understnad it is conveninet to make a jira issue for it, because that way it is easier to incorporate it into the changelog, correct?\n \n", "name": "", "is_accepted": false }, { "text": "indeed, that's why i find that less important.  \n i'm now building legacy buster for m4v2. too bad i don't have the rockpi4 anymore to test. \n i had this thought yesterday, but it might be too much work, or not work at all. i only can share my thought. \"it would be nice if after building an image, and confirm it working. that the user could upload this as \"user uploaded\". certainly for the new desktops this could be handy.\"   \n it would take up bandwidth and server space. just an idea...\n \n\n\n\n\n very nice to see. \n \n", "name": "", "is_accepted": false }, { "text": "correct.\n \n\n\n  \n \n\n\n\n\n  \n \n\n\n we tried that https://github.com/armbian/testings but it was not very useful. \n \n\n\n  \n \n\n\n we have better technology for this since it is at most important to have this information when we need it, but system needs more then one brain -> https://github.com/armbian/autotests to maintain it. i use it on a daily basis, but not on the level i would want. changing kernel is buggy which is why legacy kernels on rk3399 are not tested at all.\n \n", "name": "", "is_accepted": false }, { "text": "@igori can confirm that freshly build buster legacy on the m4v2 is working. i love the native arm build, so much faster than the rockpix and that's rk3399, haven't gotten n2+ to work yet.\n \n\n\n\n\n \n i do not know what the problem with the rockpi4 image is. \n it can't have been the same issue as m4v2. the discription makes me think it's also hdmi not working as with p1.\n \n", "name": "", "is_accepted": false }, { "text": "from master branch? \n \n\n\n  \n \n\n\n\n\n \n if you build on desktop branch / natively ... it can be anything. its known that at least 30% images can't be build since work is not done yet.\n \n", "name": "", "is_accepted": false }, { "text": "i did build from desktop branch on rk3399 and the image works. no issues at all, except a new bug in the media script. \n it would be good if rk3399 images are rebuild. if rockpi4 now doesn't work, we can't do anything wrong by uploading another non working image for it. we can only get a bit more feedback on the state of things.\n \n", "name": "", "is_accepted": false }, { "text": "rebuilding images with existing kernel? or from sources? that is much more problematic and not something i will do by the way without eating shit. which i already had enough today.\n \n\n\n  \n \n\n\n if froum sources - make a list - remove what doesn't need to be included https://github.com/armbian/build/blob/master/config/targets.conf \n \n", "name": "", "is_accepted": false }, { "text": "dear all - thank you for all info provided! @nicod link helped to run 5.8 debian cli version (on sd) first and easily update and upgrade. the only problem i have noticed is hdmi signal quality (?) - not as bad as in case of diet version for rockpi4 - but still not usable. screen \"shakes\" and it is not possible to work with (however it looks that system settings are ok for my samsung screen). the good thing is that it is possile to set basic configuration (i.e. wifi in my case) and go to ssh. my rockpi4 is planned for headless jobs anyway, thus i have to say - it works!! thanx!\n \n", "name": "", "is_accepted": false } ]

[ { "text": "for the todo queue\n \n", "name": "", "is_accepted": true } ]

[ { "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": "invalid link\n \n", "name": "", "is_accepted": false }, { "text": "thanks werner, i've uploaded it again:\n \n\n\n  \n \n\n\n http://ix.io/2pi6 \n  \n \n", "name": "", "is_accepted": false }, { "text": "unstable / insufficient powering would be 1st guess.\n \n", "name": "", "is_accepted": false }, { "text": "interesting, because i'm using the official power adapter from friendelec\n \n", "name": "", "is_accepted": false }, { "text": "5v powering via usb-c is on the edge (especially for hungry hw) if it comes via official or unofficial power adapter / cable.\n \n", "name": "", "is_accepted": false }, { "text": "mmm perhaps the cable is the problem... how could i check it? also i'm using a an adapter to fit from asia to europe \n \n\n\n  \n \n\n\n anyway, is there any other alternatives you can recommend me?\n \n", "name": "", "is_accepted": false }, { "text": "try different psu/cable. power via gpio\n \n\n\n measure voltages from psu output and on the board directly to get an idea about the voltage drop across all parasitic resistances.\n \n", "name": "", "is_accepted": false }, { "text": "thanks both, i’ll start replacing the cable.\n \n", "name": "", "is_accepted": false }, { "text": "the cable made something different, since the board was up almost 1.5 days, but it was rebooted again. \n \n\n\n  \n \n\n\n @werner i'm very noob, can you explain how can i power it up from gpio?  or which other psu could work? i read in the internet some guys are using raspberry's pi 4 psu, but reading the specs, are lower than the official from friendelec.\n \n\n\n  \n \n\n\n many thanks.\n \n", "name": "", "is_accepted": false }, { "text": "according to their wiki page https://wiki.friendlyarm.com/wiki/index.php/nanopi\\_m4v2\n \n\n\n put 5v and ground to pin 2 and 6.\n \n\n\n  \n \n\n\n\n\n they come with slight overvoltage of 5.3volts afaik. compensates for losses through connectors and cables. worth a try. however any psu featuring output slightly above 5v will do.\n \n", "name": "", "is_accepted": false }, { "text": "i've done a lot of tests with the m4v2 and powering and even at 4v it stayed stable. i've never had a crash running the legacy kernel.  \n best thing to check voltage is to use a usb voltage meter in the usb ports of the sbc. also at the input and see if the difference is big. using good cables is necessary. even most usb-c cables are not made for power. this sbc can use up to 2a, most cheap usb cables can't handle that.  \n a raspberry pi crashes quickly, and is very unstable with even 4.9v. but not the m4v2. \n \n what is connected to it? maybe a usb over voltage? you could also try a legacy kernel image to see if it's a kernel issue. also using uart connected to another device you'd probably be able to see what went wrong. \n \n", "name": "", "is_accepted": false }, { "text": "thanks all for the messages, i've tried with another one, 6.5v, and it's the same, it was rebooted 3.5hours ago. i don't know if it could be a kernel problem, i'm using also a m4v1 with sata hat, and kernel 5 and works flawless (up time:       27 days 1:15), so i think it is related to the psu/cable... \n \n my main problem here is i'm not good with electric stuff, meters etc, i have an standard meter, but i don't know even how to use it \n \n\n\n  \n \n\n\n sorry for asking @nicod with the usb meter, should be plug and see?  if so, i think even i could make it.\n \n\n\n  \n \n\n\n i'm going to look for a good usb cable... \n \n\n\n  \n \n\n\n thanks.\n \n", "name": "", "is_accepted": false }, { "text": "the new cable arrived. it supports up to 4a so fingers cross.\n \n", "name": "", "is_accepted": false }, { "text": "well, the cable is not the problem, the board rebooted 36 mins ago.... so frustrating.\n \n", "name": "", "is_accepted": false }, { "text": "you could also\n \n\n\n\n\n  \n \n\n\n i used to have a lot of hangs with older mainline kernels. since i am on the latest everything is running smoothly for me. you could try the latest kernel. you can't download this kernel from the website. you can download this kernel through armbian-config.\n \n\n\n  \n \n\n\n armbian 21.02.2 buster with linux 5.10.16-rockchip64\n \n", "name": "", "is_accepted": false }, { "text": "updated to the latest... let's see.\n \n", "name": "", "is_accepted": false }, { "text": "if it fails which i think it will... can you try this image? https://users.armbian.com/piter75/armbian\\_21.05.0-trunk\\_nanopim4v2\\_buster\\_current\\_5.10.18\\_minimal-stability-fix.img.xz\n \n\n\n it contains a fix/workaround to dvfs issues i found and makes all of my m4v2 units running stable. tested with hours of memtester running without failures. it failed pretty quick without the fix.\n \n", "name": "", "is_accepted": false }, { "text": "hello,\n \n\n\n  \n \n\n\n i recently got a nanopi m4v2 on which i installed armbian buster current and updated the system, including kernel.\n \n\n\n  \n \n\n\n after a few hours the board would crash, requiring a power cycle.\n \n\n\n  \n \n\n\n aftet reading this thread i decided to try a fixed frequency, so i left it at 2ghz. with a fixed clockspeed i ran stress tests, several runs of sbc-bench, browser benchmarks,  used it to open documents in libreoffice, watched videos using the browser, etc. and it was totally stable for over 5 days straight.\n \n\n\n  \n \n\n\n i only had problems with chromium crashing, but firefox (or equivalent) worked fine.\n \n\n\n  \n \n\n\n i changed the max and min clocks to defaults and it locked up about 4 hours later.\n \n\n\n  \n \n\n\n the board was working headlessly and i accessed it remotely using xrdp or dwservice.net.\n \n\n\n  \n \n\n\n i don't have it connected to uart at the moment because i don't have another computer nearby to connect it to where the board is placed, but if it helps i can find a way to connect it and give you the output.\n \n", "name": "", "is_accepted": false }, { "text": "hi @glock24 thanls for your message, could you please share your frequency settings? did you set with armbian-config right?\n \n", "name": "", "is_accepted": false }, { "text": "@i5js any constant frequency should do, switching cpufreq to performance profile also solved m4v2 stability issues in the past\n \n\n\n  \n \n\n\n @i5js @glock24 i would appreciate if you verified the image referred in the previous post. if it works without crashes and we merge the change into master we could finally have stable m4v2 in armbian current out of the box.\n \n\n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "hi @piter75 thanks! i'll check it, and if new reboots comes, i'll try that kernel. i've not changed any constant yet.\n \n", "name": "", "is_accepted": false }, { "text": "record!! up time:       1 day 2:26 \n \n\n\n  \n \n\n\n update: up time:       1 day 16:43 \n \n", "name": "", "is_accepted": false }, { "text": "just to confirm you are on this kernel right? linux 5.10.16-rockchip64\n \n", "name": "", "is_accepted": false }, { "text": "yes!\n \n\n\n  \n \n\n\n welcome to armbian 21.02.2 focal with linux 5.10.16-rockchip64\n \n\n\n  \n \n\n\n system load: 10%           up time:       1 day 23:13\n \n", "name": "", "is_accepted": false }, { "text": "time to test 5.10.18 image... it just rebooted. 2 days and a half up.\n \n\n\n @piter75 sorry for asking, how can install the image without reinstall the hole system?\n \n", "name": "", "is_accepted": false }, { "text": "hi @piter75, i've just applied the patch, and rebooted the pi\n \n\n\n  \n \n\n\ni5js@noldork3sn2:~$ dmesg | grep rk808-regulator.*buck\n[ 2.883990] rk808-regulator rk808-regulator: max buck steps per change: 4\n\n\n  \n \n\n\n i'll keep you posted.\n \n\n\n  \n \n\n\n thanks!\n \n", "name": "", "is_accepted": false }, { "text": "great. looking forward to hear about your results.\n \n", "name": "", "is_accepted": false }, { "text": "up time:       2 days 8:57 and counting  \n \n\n\n  \n \n\n\n looks promising.\n \n", "name": "", "is_accepted": false } ]

[ { "text": "after hours of investigation, and after having figured out that spi for h6 wasn't working since 5.7.x, i've found why : missing spi pins in dt ...\n \n\n\n  \n \n\n\n https://github.com/armbian/build/commit/e3ade9e9f4292c6b257ad10f676edc4055106d2a\n \n\n\n  \n \n", "name": "", "is_accepted": true }, { "text": "wow martin! thanks for the investigation and solution. \n i'll build a new version incorporating those changes and it will probably work. i'll reply the results here.\n \n\n\n thank you very much.\n \n", "name": "", "is_accepted": false }, { "text": "yep.\n \n\n\n  \n \n\n\n just confirming that it's working, building from sources.\n \n\n\n  \n \n\n\narmbian@orangepioneplus:~/spidev-test$ sudo ./spidev\\_test -v\n[sudo] password for armbian:\nspi mode: 0x0\nbits per word: 8\nmax speed: 500000 hz (500 khz)\ntx | ff ff ff ff ff ff 40 00 00 00 00 95 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff f0 0d | ......@....�..................�.\nrx | ff ff ff ff ff ff 40 00 00 00 00 95 ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff f0 0d | ......@....�..................�.\n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "i see the same behavior on orangepi 3 and i'm wondering if there might be a similar fix needed for this board. \n @martinayotte maybe?\n \n\n\n /boot/armbianenv.txt\n \n\n\n verbosity=1 console=both overlay\\_prefix=sun50i-h6 overlays=spi-spidev1 param\\_spidev\\_spi\\_bus=1 rootdev=uuid=b9dd15a3-53c5-44e1-96ed-816ea6eb4967 rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u\n \n\n\n working with this kernel:\n \n\n\n uname -a\n \n\n\n linux magicsky 5.4.88-sunxi64 #21.02.3 smp mon mar 8 08:07:33 utc 2021 aarch64 gnu/linux\n \n\n\n but not with latest buster 5.10.\n \n", "name": "", "is_accepted": false } ]

[ { "text": "it all depends on the device itself. you have shitty flash drives and good quality sd cards and vice versa.  so if you need endurance, you should stick to high endurance versions or flash drives, that use good quality 3d tlc flash.\n \n\n\n with ordinary cards, even with sandisk ultras, it's always a gamble, what kind of quality bin you will get. their purpose is to meet the speed spec, not endurance. it would not surprise me, if such card would die with a couple of 100s rewrites.\n \n\n\n  \n \n", "name": "", "is_accepted": true }, { "text": "i was afraid to hear that...  it is hard to learn what tech they are using on specific drives.\n \n\n\n i'll buy larger-than-necessary usb flash drives hoping the controller would distribute the wearing...\n \n\n\n at that time i used usb-2 flash'es, this time i'll get usb-3's, hoping to get better performance...\n \n\n\n  \n \n\n\n but to be able to put the device in a case, the \"fit\" labeled devices (sandisk or samsung) are best, and this will narrow my chances...\n \n\n\n  \n \n", "name": "", "is_accepted": false } ]

[ { "text": "block device names can vary especially on usb.... it's best practices to use uuids or labels to mount filesystems.\n \n", "name": "", "is_accepted": true }, { "text": "i used uuids to mount via fstab. you can see it in the snapshot and i suppose this info is also included in armbian-monitor dump included.\n \n", "name": "", "is_accepted": false }, { "text": "still odd nevertheless. one a block device is assigned it should be consistent across those very basic commands, shouldn't it?\n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "okay sorry i didn’t understand the issue exactly.\n \n\n\n  \n \n\n\n so i believe this is a technicality of using lsblk.   a btrfs subvolume isn’t going to trace back to a block device.   would be interesting to look at the output of \n \n\n\n  \n \n\n\n ls -l /dev/disk/by-uuid\n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "after mounting and unmounting several times both external units it seems to start working. now the mount point at /sda is consistent across all the commands. the outpus you asked, @lanefu, is:\n \n\n\nls -l /dev/disk/by-uuid \ntotal 0\nlrwxrwxrwx 1 root root 15 may 11 22:57 d4e4d15d-d587-4f5d-83d7-4cbb1700e7c5 -> ../../mmcblk0p1\nlrwxrwxrwx 1 root root 9 may 11 22:57 dcb5a19c-6bd2-4c5a-8fc4-9ed4adec7074 -> ../../sdb\nlrwxrwxrwx 1 root root 9 may 11 22:57 e6201983-bfd8-4eae-bf54-90575f09835f -> ../../sda\n\n\n  \n \n\n\n i also added a new screenshot. thanks for the help. and i'll keep an eye on this if it happens again.\n \n\n\n \n \n", "name": "", "is_accepted": false } ]

[ { "text": "in fact it is. starting with v197 systemd: \n https://access.redhat.com/documentation/en-us/red\\_hat\\_enterprise\\_linux/7/html/networking\\_guide/sec-understanding\\_the\\_predictable\\_network\\_interface\\_device\\_names\n \n\n\n  \n \n", "name": "", "is_accepted": true }, { "text": "but why do you want to compile the wifi-driver when already a working one is included in armbian?\n \n\n\n the ew-7811un is one of my oldest wifi-dongles from the beginning of the raspberry pi 1 area, because it was one of the first working donges on a rpi1\n \n\n\n  \n \n\n\n when i do insert my edimax - i get it listed in lsusb, get the firmware loaded in dmesg and do get a new wlan-device (wlan0/wlan1 depending on the sbc) which is normally useable: \n  \n \n\nlsusb\nbus 004 device 001: id 1d6b:0001 linux foundation 1.1 root hub\nbus 002 device 001: id 1d6b:0002 linux foundation 2.0 root hub\nbus 003 device 001: id 1d6b:0001 linux foundation 1.1 root hub\nbus 001 device 002: id 7392:7811 edimax technology co., ltd ew-7811un 802.11n wireless adapter [realtek rtl8188cus]\nbus 001 device 001: id 1d6b:0002 linux foundation 2.0 root hub\n\n\ndmesg\n[234675.296067] usb 1-1: new high-speed usb device number 2 using ehci-platform\n[234675.458033] usb 1-1: new usb device found, idvendor=7392, idproduct=7811, bcddevice= 2.00\n[234675.458084] usb 1-1: new usb device strings: mfr=1, product=2, serialnumber=3\n[234675.458099] usb 1-1: product: 802.11n wlan adapter\n[234675.458112] usb 1-1: manufacturer: realtek\n[234675.458124] usb 1-1: serialnumber: 00e04c000001\n[234675.612830] rtl8192cu: chip version 0x10\n[234675.719057] rtl8192cu: board type 0\n[234675.719387] rtl\\_usb: rx\\_max\\_size 15360, rx\\_urb\\_num 8, in\\_ep 1\n[234675.719571] rtl8192cu: loading firmware rtlwifi/rtl8192cufw\\_tmsc.bin\n[234675.719739] ieee80211 phy1: selected rate control algorithm 'rtl\\_rc'\n[234675.723064] usbcore: registered new interface driver rtl8192cu\n[234675.755713] usbcore: registered new interface driver rtl8xxxu\n[234675.816426] rtl8192cu: mac auto on okay!\n[234675.855924] rtl8192cu: tx queue select: 0x05\n\nifconfig\nwlan1: flags=4099<up,broadcast,multicast> mtu 1500\n ether 74:da:38:0e:3c:1a txqueuelen 1000 (ethernet)\n rx packets 0 bytes 0 (0.0 b)\n rx errors 0 dropped 0 overruns 0 frame 0\n tx packets 0 bytes 0 (0.0 b)\n tx errors 0 dropped 0 overruns 0 carrier 0 collisions 0\n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "@guidolthank you once again for reading and answering. since the problem \"receiver\" booting problem, i have 3 different sdcards in use (all 5.10.43), 2 buster trying setting something up like an \"vpn access point\" and 1 focal for testing desktop environments and xrdp. with your kindly provided output of your lsusb and dmesg i started today the \"focal\" sdcard. nothing else is installed on focal, just plain os, no openvpn and no further experiments. here is the output of my \"focal\" with plugged-in edimax.\n \n\n\n  \n \n\n\n root@deskpi:/# lsusb \n bus 005 device 001: id 1d6b:0001 linux foundation 1.1 root hub \n bus 003 device 001: id 1d6b:0002 linux foundation 2.0 root hub \n bus 004 device 001: id 1d6b:0001 linux foundation 1.1 root hub \n bus 002 device 003: id 7392:7811 edimax technology co., ltd ew-7811un 802.11n wireless adapter [realtek rtl8188cus] \n bus 002 device 001: id 1d6b:0002 linux foundation 2.0 root hub \n bus 001 device 001: id 1d6b:0002 linux foundation 2.0 root hub\n \n\n\n  \n \n\n\n root@deskpi:/# iwconfig \n lo        no wireless extensions.\n \n\n\n eth0      no wireless extensions.\n \n\n\n wlx74da387ed9f9  ieee 802.11  essid:off/any \n           mode:managed  access point: not-associated   tx-power=20 dbm \n           retry short limit:7   rts thr=2347 b   fragment thr:off \n           encryption key:off \n           power management:off\n \n\n\n  \n \n\n\n here is dmesg output: \n  \n \n\n\n\n\n  \n \n\n\n on this point in \"buster\" image, i decided to compile wlan driver, following the given advice in the how-to. even the example driver is the one i need.... \n i hope this answers your question, why i recompiled the driver. i'm a newbie, but not such a newbie, that \"wlx74da387ed9f9\" could be a valid network name.\n \n", "name": "", "is_accepted": false }, { "text": "@igor thanks you for the information. \n \n so, how it looks like: i am newbie, thinking that the first plugged-in device has to be wlan0. but now i got it: wlx<macadress> is valid network name. recompiling was useless. \n \n thank you for your help!\n \n", "name": "", "is_accepted": false }, { "text": "also for other reason. we keep well known and those a bit less known wireless drivers in best possible shape and bundled with kernels we provide. in theory - users should not need to compile exotic drivers that linux doesn't support (well enough) on their own, but all dependencies are ready (kernel headers, compilers) - so you can. for things we don't cover, can't bundle (zfs) or for experimenting ...\n \n\n\n  \n \n\n\n\n\n \n we all are \n \n\n\n  \n \n\n\n it is impossible to know everything, especially in this tech world full of complicated details.\n \n", "name": "", "is_accepted": false } ]

[ { "text": "actually it is, but perhaps not well exposed in documentation: \n  \n \n\n./compile.sh 'compile\\_uboot'\n\n\n  \n \n", "name": "", "is_accepted": true }, { "text": "there is no good way to only build uboot sorry. regarding the created uboot, i am pretty sure all variants are built. but ./cache/sources/ is not the right place to look for them.\n \n\n\n please check ./output/debs/ for a uboot deb archive. its should be named somewhat like these: https://beta.armbian.com/pool/main/l/linux-u-boot-clearfogbase-current/\n \n\n\n if you unpack the .deb you can find all variants of u-boot inside ./usr/lib/linux-u-boot.../   they should be named accordingly.\n \n\n\n  \n \n\n\n edit: just checked by building: said .deb gets created and contains all needed files. you can also abort the buildscript with ctrl-c after it is done with uboot (and has started the kernel) to not have to build everything all the time.\n \n", "name": "", "is_accepted": false }, { "text": "awesome igor, much appreciated. that has saved a whole lot of time rebuilding u-boot and i completely missed that in the documentation .... and i can now see the sata ssd:\n \n\nsmartctl -a /dev/sda\n\n=== start of information section ===\ndevice model: samsung mzmpa128hmfu-000h1\n\n\n fantastic, now i have plenty of storage for the router / mitm / docker host.\n \n", "name": "", "is_accepted": false } ]

[ { "text": "use regular `shasum` command (here with `--check` option):\n \n\n\n  \n \n\n\n$ shasum -c armbian\\_20.08.1\\_odroidxu4\\_buster\\_legacy\\_4.14.195.img.xz.sha \n\narmbian\\_20.08.1\\_odroidxu4\\_buster\\_legacy\\_4.14.195.img.xz: ok\n\n\n  \n \n", "name": "", "is_accepted": true } ]

[ { "text": "i've got no idea what's wrong. but it would help if you'd give a bit more information. \n on what are you trying to build? x86? virtual box? arm64? docker? ... \n did you try with a fresh build?\n \n", "name": "", "is_accepted": false }, { "text": "you are building this on what host? you have supplied not a single clue about that most important. there are also detailed logs in output/debug which might contain critical informations. \n \n we are rebuilding images upon upstream changes:\n \n\n\n https://github.com/armbian/build/actions/runs/963008795 \n https://github.com/armbian/build/actions/runs/961942368\n \n\n\n \n are you sure you are using our up-to-date build tools?\n \n\n\n \n full build log on my linux mint workstation: \n  \n \n\n\n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "hi nicod hi igor, \n i'mu building on on a native environment. latest buster running on a x86 (64 bit) pc with 16 gb of memory.\n \n\n\n wolli@localhost:/proc$ neofetch \n        \\_,met$$$$$gg.          wolli@localhost \n     ,g$$$$$$$$$$$$$$$p.       --------------- \n   ,g$$p\"     \"\"\"y$$.\".        os: debian gnu/linux 10 (buster) x86\\_64 \n  ,$$p'              `$$$.     host: 5864b24 thinkcentre m90p \n ',$$p       ,ggs.     `$$b:   kernel: 4.19.0-17-amd64 \n `d$$'     ,$p\"'   .    $$$    uptime: 4 mins \n  $$p      d$'     ,    $$p    packages: 1853 (dpkg) \n  $$:      $$.   -    ,d$$'    shell: bash 5.0.3 \n  $$;      y$b.\\_   \\_,d$p'      terminal: /dev/pts/0 \n  y$$.    `.`\"y$$$$p\"'         cpu: intel i7 870 (8) @ 2.927ghz \n  `$$b      \"-.\\_\\_              gpu: nvidia geforce 310 \n   `y$$                        memory: 502mib / 15976mib \n    `y$$. \n      `$$b. \n        `y$$b. \n           `\"y$b.\\_ \n               `\"\"\"\n \n\n\n i'm cloned the armbian-build 4 days ago so it should be one of the latest built versions. \n cat for the file version in my build dir gives:  21.08.0-trunk  is that good ? \n \n the headline of the semigraphic when execututing the ./compile.sh script shows: \n armbian building script, https;//www.armbian.com | autor: igor pecovnik\n \n\n\n  \n \n\n\n i'll try it today again and will check the output logs.\n \n\n\n  \n \n\n\n thanks wolfgang\n \n", "name": "", "is_accepted": false }, { "text": "unsupported build environment. https://docs.armbian.com/developer-guide\\_build-preparation/\n \n\n\n  \n \n\n\n   \n \n\n\n\n\n  \n \n\n\n yes\n \n", "name": "", "is_accepted": false }, { "text": "hi igor, \n i can't find the problem in the logs, here are the logs from today and the older onse. \n \n regards \n wollik\n \n\nlogs-25\\_06\\_2021-12\\_02\\_01.tgz \nlogs-23\\_06\\_2021-21\\_11\\_33.tgz ", "name": "", "is_accepted": false }, { "text": "hi werner, \n thanks for this hint, i setup not a docker environment on my debian buster system and give it a try.\n \n\n\n  \n \n\n\n reards \n wolfgang \n  \n \n", "name": "", "is_accepted": false }, { "text": "hi all, \n i got it compiled in the docker environment without problems. \n in debian buster some needed tools like: debootstrap, gaparted, losetup and maybe others are installed in /sbin, that is not in my path when i'm su. \n so i just added also the /sbin directory to my path before calling the ./compile.sh script and it also compiles without problems. \n \n the compile problems are now fixed, the questeion for this debootstrap problem is answered an this topic can marked as solved.\n \n\n\n  \n \n\n\n i'll give the newly created image a try later on.\n \n\n\n  \n \n\n\n many thanks to all fo you \n wollik\n \n", "name": "", "is_accepted": false } ]

[ { "text": "@igor and who also have an interest in this issue/topic\n \n\n\n \n after a long time - today ethnernet is since hours stable again on my nanopi neo (no network/eth0 down/up) \n but i didnt changed the software (armbian)\n \n\n\n \n yesterday my nanopi neo had down/up (also) with kernel 5.11.2-dev and debian buster and now today its stable since hours!\n \n\n\n  \n \n\n\n what i did? no it wasnt the software, nor the ethernet-cable, nor the power-supply, nor the eth0-setting.\n \n\n\n i have a 16-port-ethnernet-hub with 100mbit, but its optical devided in 2x(2x4):\n \n\n\n1st 2nd\n2x4 + 2x4 = 16 ports \n#### ####\n#### ####\n\n\n  \n \n\n\n the nanopi neo was in the 2nd 2x4 ports with the problem and after putting him in the 1st 2x4 port section the nanopi neo port did go stable.\n \n\n\n  \n \n\n\n in the 1st 2x4 ports are more or mostly (or only?) 100mbit devices and in the 2nd 2x4 are some/more 1gbit-devices.\n \n\n\n  \n \n\n\n i - personally - think the nanopi neo ethernet-phy didnt/doesnt tolerate some sort of ethernet-phy at the 2nd 2x4 port-part.\n \n\n\n at the 1st 2x4port-part it seems he found ethernet-phys he could tolerate.\n \n\n\n this is for today my \"absurd\" theory  - because it does work now for hours without a single up/down message in dmesg\n \n", "name": "", "is_accepted": true }, { "text": "also with kernel 5.4.1 on the orangepi r1 (h2+ cpu) \n changed network-cable, power-supply, dcard which do work without problems on other sbcs\n \n\n\n ssh-session is mostly unuseable \n i also deinstalled network-manager and do only use /etc/network/interfaces. \n maybe i will check tomorrow if connection via wifi is more \"stable\"!?\n \n\n\n  \n \n\n\n btw: i did also read about some sbcs other than h2/h3 who have network/ssh-problems since kernel 5.3/5.4.y,\n \n\n\n but they did show the error-message in the dmesg.\n \n\n\narmbian buster with linux 5.4.1-sunxi\npackage bsp-kernel[19.11.3.339] u-boot[19.11.3] dtb[19.11.3.339] \nfirmware[19.11.3.334] config[19.11.3.334] branch[dev]\n\n[ 33.781329] vcc3v0: disabling\n[ 33.781350] vcc5v0: disabling\n[ 59.349570] dwmac-sun8i 1c30000.ethernet eth0: link is down\n[ 67.541687] dwmac-sun8i 1c30000.ethernet eth0: link is up - 100mbps/full - flow control rx/tx\n[ 74.709525] dwmac-sun8i 1c30000.ethernet eth0: link is down\n[ 92.117671] dwmac-sun8i 1c30000.ethernet eth0: link is up - 100mbps/full - flow control rx/tx\n[ 113.621488] dwmac-sun8i 1c30000.ethernet eth0: link is down\n[ 115.669653] dwmac-sun8i 1c30000.ethernet eth0: link is up - 100mbps/full - flow control rx/tx\n[ 152.533554] dwmac-sun8i 1c30000.ethernet eth0: link is down\n[ 154.581720] dwmac-sun8i 1c30000.ethernet eth0: link is up - 100mbps/full - flow control rx/tx\n[ 169.941894] dwmac-sun8i 1c30000.ethernet eth0: link is down\n[ 171.990061] dwmac-sun8i 1c30000.ethernet eth0: link is up - 100mbps/full - flow control rx/tx\n[ 181.206113] dwmac-sun8i 1c30000.ethernet eth0: link is down\n[ 184.278327] dwmac-sun8i 1c30000.ethernet eth0: link is up - 100mbps/full - flow control rx/tx\n[ 188.374256] dwmac-sun8i 1c30000.ethernet eth0: link is down\n[ 191.446457] dwmac-sun8i 1c30000.ethernet eth0: link is up - 100mbps/full - flow control rx/tx\n[ 193.494356] dwmac-sun8i 1c30000.ethernet eth0: link is down\n[ 195.542543] dwmac-sun8i 1c30000.ethernet eth0: link is up - 100mbps/full - flow control rx/tx\n[ 219.094889] dwmac-sun8i 1c30000.ethernet eth0: link is down\n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "what is the u-boot version?\n ", "name": "", "is_accepted": false }, { "text": "@igor its for the opi r1\n \n\n\n u-boot spl 2019.10-armbian (dec 05 2019 - 19:02:23 +0300)\n \n\n\n dpkg -l|grep u-boot \n linux-u-boot-orangepi-r1-dev 19.11.3   armhf  uboot loader 2019.10\n \n\n\n  \n \n\n\n i also compiled a legacy image, but here i did also get uboot 2019.10:\n \n\n\n linux-u-boot-legacy-orangepi-r1\\_19.11.3\\_armhf.deb \n u-boot spl 2019.10-armbian (dec 06 2019 - 08:52:44 +0300) \n dpkg -l|grep u-boot \n linux-u-boot-orangepi-r1-legacy 19.11.3 armhf uboot loader 2019.10\n \n\n\n with the same problems: \n  \n \n\n\n\n\n  \n \n\n\n but also often: \n  \n \n\n\n[ 76.501287] ==> rtl8188e\\_iol\\_efuse\\_patch\n[ 81.373252] ==> rtl8188e\\_iol\\_efuse\\_patch\n[ 104.449252] ==> rtl8188e\\_iol\\_efuse\\_patch\n[ 137.369173] ==> rtl8188e\\_iol\\_efuse\\_patch\n[ 180.377180] ==> rtl8188e\\_iol\\_efuse\\_patch\n[ 233.373175] ==> rtl8188e\\_iol\\_efuse\\_patch\n[ 296.433174] ==> rtl8188e\\_iol\\_efuse\\_patch\n[ 359.465161] ==> rtl8188e\\_iol\\_efuse\\_patch\n[ 422.466610] ==> rtl8188e\\_iol\\_efuse\\_patch\n[ 485.403544] ==> rtl8188e\\_iol\\_efuse\\_patch\n[ 548.408481] ==> rtl8188e\\_iol\\_efuse\\_patch\n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "@igor interesting side-effect-information: its seems that only the onboard eth0 dwmac-sun8i 1c30000.ethernet\n \n\n\n is affected by the down/up-link syndrom\n \n\n\n  \n \n\n\n if i do use the second ethernetport of the opi r1 (which is connected onboard via usb) then i dont have this\n \n\n\n down/up-link syndrom: \n  \n \n\n\nenxc0742bffe8ff\n[ 2.815218] usbcore: registered new interface driver usb-storage\n[ 3.471264] usb 3-1: new usb device found, idvendor=0bda, idproduct=8152, bcddevice=20.00\n[ 6.781528] core: \\_opp\\_supported\\_by\\_regulators: opp minuv: 1400000 maxuv: 1400000, not supported by regulator\n[ 7.062463] usbcore: registered new interface driver r8152\n[ 7.429322] r8152 3-1:1.0 eth2: v1.10.10\n[ 7.611054] r8152 3-1:1.0 enxc0742bffe8ff: renamed from eth2\n\n\n also a external usb-ethernet device isnt affected by the down/up-link syndrom:\n \n\n\nenx00123455562b\n[ 7.107788] moschip usb-ethernet driver 4-1:1.0 eth1: register 'moschip usb-ethernet driver' at usb-1c1c000.usb-1, moschip 7830/7832/7730 usb-net adapter, 00:12:34:55:56:2b\n[ 7.108080] usbcore: registered new interface driver moschip usb-ethernet driver\n[ 7.568243] moschip usb-ethernet driver 4-1:1.0 enx00123455562b: renamed from eth1\n\n\n all 3 were connected to the same ethernet-cable running with the same os, power-supply and sdcard.\n \n", "name": "", "is_accepted": false }, { "text": "maybe its the rtl8211e phy which is used for eth0?\n \n\n\n  \n \n\n\n https://linux-sunxi.org/ethernet\n \n\n\n\n\n  \n \n\n\n see also https://forum.pine64.org/showthread.php?tid=5712 https://patchwork.ozlabs.org/patch/873752/ https://lkml.org/lkml/2017/8/22/9\n \n\n\n  \n \n\n\n and maybe here? https://lore.kernel.org/lkml/20170908142825.gc3037@red/t/\n \n", "name": "", "is_accepted": false }, { "text": "yes, it looks like somebody played with timings or we miss some patch adjusting this ... since we are changing release model, master will only be build ready, other things will be more fragile https://github.com/armbian/documentation/blob/master/docs/process\\_release-model.md (wip) users should stick to released branches. they should not have this problem since u-boot is old there ... \n ", "name": "", "is_accepted": false }, { "text": "my ./userpatches/config-default.conf defaults to branch master as lib\\_tag\n \n\n\n but i cant set branch=master at compile.sh because then i do get\n \n\n\n [ error ] kernel branch not defined for this board [ master ] \n  \n \n\n\n so i could use legacy, current and dev and maybe next \n which branch should i use to get an older u-boot?\n \n\n\n i think released branches are v19.08 and v19.11  (took the names from https://github.com/armbian/build )\n \n\n\n but i also do get\n \n\n\n [ error ] kernel branch not defined for this board [ v19.08 ] \n [ error ] kernel branch not defined for this board [ v19.11 ]\n \n\n\n  \n \n\n\n but also with legacy and next i do get only the new u-boot 2019.10 \n please give me a info what to try \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "your build directory is probably not clean and it does not change properly. hmm ... but there are older binaries in the https://apt.armbian.com/pool/main/l/ \n \n\n\n  \n \n\n\n install them + armbian-config -> system -> update boot loader (+ de-install older before)\n \n", "name": "", "is_accepted": false }, { "text": "first i did try to compile with clean\\_level=\"make,debs,oldcache,cache,alldebs\" - that cleaned many files/dirctorys, but also did try to compile u-boot 2019.10 instead of 2019.04\n \n\n\n  \n \n\n\n now i deleted my ./build-dirctory and cloned (again) the armbian-build - hope thats clean enough \n\n\n  \n \n\n\n i did also try to install bootloader via armbian-config\n \n\n\n on the opi r1 i did get:\n \n\n\n linux-u-boot-orangepi-r1-dev  19.11.3  armhf  uboot loader 2019.04\n \n\n\n  \n \n\n\n with this u-boot eth0 is (also) found - but cant be used \n \n\n\n  \n \n\n\n dmesg seems to be ok:\n \n\n\n[ 2.718770] libphy: fixed mdio bus: probed\n[ 2.719328] dwmac-sun8i 1c30000.ethernet: 1c30000.ethernet supply phy not found, using dummy regulator\n[ 2.719403] dwmac-sun8i 1c30000.ethernet: 1c30000.ethernet supply phy-io not found, using dummy regulator\n[ 2.719893] libphy: stmmac: probed\n[ 2.720380] dwmac-sun8i 1c30000.ethernet: found internal phy node\n[ 2.720477] libphy: mdio\\_mux: probed\n[ 2.720494] dwmac-sun8i 1c30000.ethernet: switch mux to internal phy\n[ 2.720502] dwmac-sun8i 1c30000.ethernet: powering internal phy\n[ 2.731395] libphy: mdio\\_mux: probed\n[ 3.134611] usb\\_phy\\_generic usb\\_phy\\_generic.0.auto: usb\\_phy\\_generic.0.auto supply vcc not found, using dummy regulator\n[ 8.052169] dwmac-sun8i 1c30000.ethernet eth0: phy [0.1:01] driver [generic phy]\n[ 8.053364] dwmac-sun8i 1c30000.ethernet eth0: no safety features support found\n[ 8.053380] dwmac-sun8i 1c30000.ethernet eth0: no mac management counters available\n[ 8.053390] dwmac-sun8i 1c30000.ethernet eth0: ptp not supported by hw\n[ 8.053403] dwmac-sun8i 1c30000.ethernet eth0: configuring for phy/mii link mode\n\n\n eth0 is blinking like a heartbeat with the yellow/green led at the same time \n \n\n\n  \n \n\n\n second onboard-ethernet-port via usb is working.\n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "with fresh git--cloned armbian-build-system compiled:\n \n\n\n armbian buster with linux 5.4.2-sunxi\n \n\n\n package bsp-kernel[19.11.3] u-boot[19.11.3] dtb[19.11.3] firmware[19.11.3] config[19.11.3] \n branch[dev] \n  \n \n\n\nlinux-u-boot-orangepi-r1-dev  19.11.3 armhf  uboot loader 2019.10\n\nlinux-dtb-dev-sunxi           19.11.3 armhf  linux dtb, version 5.4.2-sunxi\nlinux-image-dev-sunxi         19.11.3 armhf  linux kernel, version 5.4.2-sunxi\n\n\n \n  \n \n\n\n eth0 doenst work- but usb-ethernet\n \n\n\n current image only has the \"patched/buggy\" 5.3 kernel \n \n\n\n  \n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "strange - eth0 is working (with down/up-link-syndrom) when powered via microusb with org. raspberry pi power-supply, but not via the power-barrel-connector which is installed on my opi r1.\n \n\n\n\n\n \n this barrel-connector has now worked since 2 years and now it seems to get not enough power to the board for the normal eth0, bt for the usb-eth1?\n \n\n\n  \n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "probably there is a bug in the board dt or withing u-boot. close inspection and comparing to reality is needed.\n \n", "name": "", "is_accepted": false }, { "text": "i have the same problem on an orangepi one (h3) with armbian\\_20.02.0-rc0\\_orangepione\\_bionic\\_current\\_5.4.12. i changed the board, the sd-card and the patch cord, but not the power-supply. i also tried the last archived legacy image for the orangepi one. i always got the same problem. i fiddled around with ethtool and found that turning off the auto-negotiation for the ethernet-connection fixed it for me. i don't know whats going on in the background. as i understand it,  depending on the other side of the connection the connection could end as 10 mbps half duplex if the auto-negotiation is turned off. but in my case (fritzbox) the connection is rock-solid and the speed is also good. so maybe this solution that i found in some forum helps you too:\n \n\n\n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "so what should i do with this problem? this problem has been present for at least four years, on all kernels, on any armbian build. when will the solution appear?\n \n\n\n all tricks with ethtool doesen't work!\n \n", "name": "", "is_accepted": false }, { "text": "being rude does not solve issues faster. however there are ways to accomplish this. please consider studying the \"support\" section here: https://github.com/armbian/build#support\n \n", "name": "", "is_accepted": false }, { "text": "we have a commercial product running on armbian based on the opi zero platform. we occasionally get reports from customers of intermittent connectivity, which (looking at the dmesg log on affected devices) manifests itself as something that looks very much like the up/down syndrome reported here. in this case we advise customers to purchase a cheap switch (e.g. https://www.amazon.com/netgear-5-port-gigabit-ethernet-unmanaged/dp/b07s98ylhm/ref=sr\\_1\\_3?dchild=1&keywords=4+port+switch&qid=1614793487&sr=8-3) and put it between our product and their existing switch or router. we have found this always resolves the issue.\n \n\n\n  \n \n\n\n we still don't understand the cause, but at least we have a workaround (albeit not a perfect one).\n \n", "name": "", "is_accepted": false }, { "text": "@igor just one more \"repaired\" patient \n after getting at tuesday the nanopi neo working fine with his eth0 - i did gave my orange pi r1 a new \"ride\" today.\n \n\n\n  \n \n\n\n the last months (or year) i did think his eth0 is defective, because when ethernet there is inserted the orange-led blinks only on/off and isnt accessable when the orange pi r1 is booted. i could only use the second ethernet port (with the same cable) which is onboard conected via usb (enx-device)\n \n\n\n  \n \n\n\n today i put him on the same 1st 2x4 ports of my 16 port 100mbit hub - and the blinking orange led stays on and does work as eth0 \n \n\n\n  \n \n\n\n system diagnosis information has been uploaded to http://ix.io/2ruj\n \n\n\n  \n \n\n\n because i have no more feee ports i had to move another system from the 1st to the 2nd part of the ethernet-switch.\n \n\n\n  \n \n\n\n so also the orange pi r1 - like the nanopi neo - seems to have a difference on their eth0-port (phy?)  against other systems.\n \n\n\n strange for me was that the 2nd onboard-usb-connected ethernet-port did work on the same ethernet-cable (and switch-port), but not on the onboard chipset-included eth0.\n \n\n\n  \n \n\n\n so in the past we took that as some \"voodoo\" and many other people with other ethernet-switches.\n \n\n\n the \"solution\" of @adrian cable should be tested in future by such network problems \n \n", "name": "", "is_accepted": false }, { "text": "i had same problem on opi pc+ using the latest:  armbian\\_21.05.1\\_orangepipcplus\\_focal\\_current\\_5.10.34\n \n\n\n  \n \n\n\n i managed to get it to stay up (has been over 12 hrs so far) by doing the following.  perhaps this is a clue on what might be happening. \n \n\n\n  \n \n\n\n 1. blacklisted wifi since i don't use it.  not sure if this is part of the problem or not.  i added these lines to /etc/modprobe.d/blacklist.conf\n \n\n\n  \n \n\n\n blacklist 8189fs \n blacklist r8723bs\n \n\n\n  \n \n\n\n 2.  use nmtui to set mac address and static ipv4 address.\n \n\n\n  \n \n\n\n problem gone.\n \n\n\n  \n \n\n\n  \n \n\n\n  \n \n\n\n  \n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "interesting yeah started gettin some nic stuff on my pineh64 recently after i moved up my kernel.. haven't tried disabling wifi drive..  kept on thinking it was the clock rolling backwards. need to do more testing.. will look into module blacklikst tho\n \n", "name": "", "is_accepted": false }, { "text": "i am going to try putting back wifi but keep the static v4 address stuff.  could help steer in the right direction.  i do recall that blacklisting wifi alone did not fix the dropping.\n \n\n\n  \n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "been up for over an hour with wifi modules in place.  wifi not connected though.  would never stay up this long before.\n \n\n\n  \n \n\n\n so it has something to do with static vs dynamic address (either mac and/or ipv4). \n \n\n\n  \n \n\n\n knowing this, is there a particular log that i can take of the problem to help out?\n \n", "name": "", "is_accepted": false }, { "text": "hmmmmmmm \n \n https://askubuntu.com/questions/1288683/dhclient-doesnt-renew-lease-when-ntp-syncs-the-time-backwards \n \n /var/log/syslog and /var/log/kernel and /var/log/dmesg\n \n", "name": "", "is_accepted": false }, { "text": "yep! dhcp renewal seems to freak out chrony and caused the system clock to rollback....  been stable since i switched to static ip.. now to find a real fix....\n \n", "name": "", "is_accepted": false }, { "text": "spoke with @igor and issue may be related to u-boot.... will investigate more.. just making note here\n \n", "name": "", "is_accepted": false }, { "text": "this sounds very interesting. care to share some more? thank you!\n \n", "name": "", "is_accepted": false }, { "text": "i donr have the why but  downgrading the uboot package to an older one from our deb archive does seem to solve.\n \n", "name": "", "is_accepted": false }, { "text": "any more details so this is actionable by the community? version/commit numbers of u-boot for working vs. non-working would be a great start on the way to a git bisect.\n \n", "name": "", "is_accepted": false }, { "text": "put few thousands on our account if you have such ideas or hire someone to get you that information. we have shared all we know - we always do that. to get a better information, to find a bug, additional time has to be lost. perhaps a day is enough, perhaps a week wont. and we have other, much more important things to do. we would improve this service ... \n \n", "name": "", "is_accepted": false } ]

[ { "text": "looks like this helped in the end: \" rockpi-4a:~:# vnstat -i wg0 --update \" \n  \n \n\n\n\n\n  \n \n", "name": "", "is_accepted": true }, { "text": "nice catch. i have mitigated this problem this way: \n https://github.com/armbian/build/pull/2839/files\n \n\n\n and remove combinations at the end since i didn't find a better way \n https://github.com/armbian/build/pull/2848/files\n \n\n\n  \n \n\n\n well, all this has to be done automagically ...\n \n", "name": "", "is_accepted": false } ]

[ { "text": "@medapayne\n \n\n\n create a /etc/asound.conf to get the analog audio card as default.\n \n\n\n whats the output of\n \n\n\n aplay -l\n \n\n\n  \n \n\n\n mine: \n  \n \n\n\n \\_\\_\\_ \\_\\_\\_\\_ \\_ \\_\\_\\_\\_\\_\n / \\_ \\| \\_ \\(\\_) |\\_\\_ /\\_\\_\\_ \\_ \\_\\_ \\_\\_\\_\n| | | | |\\_) | | / // \\_ \\ '\\_\\_/ \\_ \\\n| |\\_| | \\_\\_/| | / /| \\_\\_/ | | (\\_) |\n \\\\_\\_\\_/|\\_| |\\_| /\\_\\_\\_\\_\\\\_\\_\\_|\\_| \\\\_\\_\\_/\n\nwelcome to armbian 20.08.9 buster with linux 5.9.1-sunxi\n\nroot@opi-zero(192.168.6.99):~# aplay -l\n**** list of playback hardware devices ****\ncard 0: codec [h3 audio codec], device 0: cdc pcm codec-0 [cdc pcm codec-0]\n subdevices: 1/1\n subdevice #0: subdevice #0\n\nroot@opi-zero(192.168.6.99):~# more /etc/asound.conf\npcm.!default {\n type hw\n card 0\n device 0\n}\n\nctl.!default {\n type hw\n card 0\n}\n\n\nand enable [*] analog-codec\nin armbian-config -> system -> hardware\n\n\n  \n \n", "name": "", "is_accepted": true }, { "text": "your support topic is lacking of important debugging information. please edit and fix!\n \n\n\n  \n \n\n\n please describe your setup as best as possible so we know what your operating environment is like.\n \n\n\n  \n \n\n\n \n name of your board with all details, version number, take a picture if you are not sure what you have\n \n \n name of the image you installed or logs if you can boot the board: armbianmonitor -u (paste url to your forum post)\n \n \n if your board does not boot, provide a log from serial console (uart) or at least make and attach a picture, where it stops.\n \n \n describe the problem the best you can and provide all necessary info that we can reproduce the problem.\n \n \n if anything is attached to the board, supply all details\n \n\n\n\n  \n \n\n\n tips:\n \n\n\n  \n \n\n\n \n use spoiler  when adding a long text,\n \n \n use  when adding a code,\n \n \n be concise.\n \n\n", "name": "", "is_accepted": false }, { "text": "it works great ... thx envoyé de mon iphone en utilisant tapatalk", "name": "", "is_accepted": false } ]

[ { "text": "you might want to look in this. it is old, and i don't know if it is still the way to go.\n \n\n\n\n  \n \n\n\n  \n \n", "name": "", "is_accepted": true }, { "text": "i know this topic's already marked solved, however wanted to add something interesting that i found in my travels.\n \n\n\n  \n \n\n\n if for some reason a software software controlled read-only switch isn't sufficient, it is actually possible to make a microsd card read-only.\n \n\n\n  \n \n\n\n https://github.com/bertoldvdb/sdtool\n \n\n\n  \n \n\n\n i'll still echo that overlayroot is generally the way to go. but in some applications that may not be sufficient.\n \n\n\n  \n \n\n\n and the permlock function does work as advertised.\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": "what is the problem with the pcie gigabit ethernet?\n \n", "name": "", "is_accepted": false }, { "text": "wow nice - this might become my new vpn / pihole setup,\n \n\n\n depending on $$$ as current opioneplus does its job well.\n \n\n\n suppose armbian images can be build soon for this board.\n \n\n\n @wernerthanks for your info!\n \n", "name": "", "is_accepted": false }, { "text": "this looks like a great board.\n \n\n\n  \n \n\n\n it would be great if it supported otg on the usb-c port. also, the horizontal orientation of the usb 3.0 ports and their proximity might not allow us to plug two larger usb devices (wi-fi adapter, usb to serial adapter) at the same time. \n \n\n\n  \n \n\n\n having said that, armbian would be my go to os for this board if/when available. \n \n", "name": "", "is_accepted": false }, { "text": "lots of board have similar issues. debt of compactness. thankfully you can get adapters for cheap.\n \n", "name": "", "is_accepted": false }, { "text": "i have been stockpiling wndr3800 which are nowadays inexpensive and able to run fully in freedom, but obviously this would be a much, much more powerful little board.\n \n\n\n  \n \n\n\n i seem to recall some past discussion of certain rk3399 boards being possible to run without blobs?  especially without graphics or wi-fi, i think makes this even more of a possibility.  also it's ddr3 (well the 1gb model anyway; as all ddr4 implementations so far also require blobs, to my understanding).\n \n\n\n  \n \n\n\n yeah, interested to see how this comes along.  thanks for sharing, werner.  any feedback on blobs, especially, i would be very interested in.\n \n", "name": "", "is_accepted": false }, { "text": "https://www.cnx-software.com/2020/12/01/buy-nanopi-r4s-sbc-optional-metal-case/\n \n\n\n  \n \n\n\n  \n \n\n\n 4gb version about 62€ including shipping and tax to germany\n \n", "name": "", "is_accepted": false }, { "text": "at this point roc-rk3399-pc is the only one with blob-less boot sequence by default but it's certainly possible with some others too \n \n\n\n https://github.com/armbian/build/blob/master/config/sources/families/rk3399.conf#l19\n \n\n\n and it's lpddr4 too...\n \n", "name": "", "is_accepted": false }, { "text": "i view all knowledge as \"provisional.\"  \n \n\n\n  \n \n\n\n which is why i keep asking, and re-stating what \"i think i know.\"  thanks a lot for valuable information, that can otherwise be hard to come by.  i think i am starting to get an idea where to look, however, so thanks for that, too.\n \n", "name": "", "is_accepted": false }, { "text": "ordered 1gb version incl housing just now ,\n \n\n\n let's hope at least wip status will appear next few months for this one.\n \n", "name": "", "is_accepted": false }, { "text": "i'm curios about the usb3 performance. if somebody has a chance to hook up a ssd and do some tests would be cool.\n \n", "name": "", "is_accepted": false }, { "text": "not sure what's to get excited about with the r4s until we get armbian so we can run openmediavault on the board - or am i missing something.\n \n\n\n https://tech.scargill.net/friendlyarm-nanopi-r4s-sbc/\n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "i think so.\n \n\n\n  \n \n\n\n https://forum.armbian.com/topic/6617-the-purpose-of-this-subforum/\n \n", "name": "", "is_accepted": false }, { "text": "device with housing arrived today, cannot wait to deploy armbian on it :-), but will need to have some more patience\n \n\n\n once image is ready ( to be build ) and entered matured state will swap it with my opioneplus as i'll solely use it for wireguard ( and ddclient / chrony ) \n \n", "name": "", "is_accepted": false }, { "text": "mine is still in transit between shanghai and row \n \n\n\n there are a few other things that need to be sorted out to get armbian working on it: https://github.com/armbian/build/pull/2415\n \n", "name": "", "is_accepted": false }, { "text": "board does now properly boot on current and dev branch.\n \n", "name": "", "is_accepted": false }, { "text": "can somebody verify that both usb connectors work with dev branch 5.10.4?\n \n\n\n on my board the one closer to the corner does not work.\n \n\n\n  \n \n\n\n works with friendlyelec 4.19.111\n \n", "name": "", "is_accepted": false }, { "text": "confirmed:\n \n\n\n  \n \n\n\n armbian 21.02.0-trunk focal with linux 5.9.16-rockchip64\n \n\n\n  \n \n\n\n the one in the middle works:\n \n\n\n  \n \n\n\n[ 922.891909] usb 6-1: new superspeed gen 1 usb device number 2 using xhci-hcd\n[ 922.913139] usb 6-1: new usb device found, idvendor=090c, idproduct=2000, bcddevice=11.00\n[ 922.913162] usb 6-1: new usb device strings: mfr=1, product=2, serialnumber=0\n[ 922.913178] usb 6-1: product: intenso flash line\n[ 922.913193] usb 6-1: manufacturer: smi corporation\n[ 922.915257] usb-storage 6-1:1.0: usb mass storage device detected\n[ 922.917468] scsi host0: usb-storage 6-1:1.0\n[ 922.969173] usbcore: registered new interface driver uas\n[ 924.022772] scsi 0:0:0:0: direct-access intenso flash line 1100 pq: 0 ansi: 6\n[ 924.024647] sd 0:0:0:0: [sda] 245760000 512-byte logical blocks: (126 gb/117 gib)\n[ 924.025007] sd 0:0:0:0: [sda] write protect is off\n[ 924.025029] sd 0:0:0:0: [sda] mode sense: 43 00 00 00\n[ 924.025382] sd 0:0:0:0: [sda] write cache: enabled, read cache: enabled, doesn't support dpo or fua\n[ 924.033101] sd 0:0:0:0: attached scsi generic sg0 type 0\n[ 924.058523] sda: sda1 sda2 sda3\n[ 924.060440] sd 0:0:0:0: [sda] attached scsi removable disk\n\n\n  \n \n\n\n the left one (corner) does not:\n \n\n\n  \n \n\n\n[ 463.509617] usb 6-1: usb disconnect, device number 2\n[ 463.515097] sd 0:0:0:0: [sda] synchronizing scsi cache\n[ 463.515366] sd 0:0:0:0: [sda] synchronize cache(10) failed: result: hostbyte=0x01 driverbyte=0x00\n\n\n  \n \n\n\n  \n \n\n\n  \n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "you can use \"dwc3-0-host\" overlay in /boot/armbianenv.txt to enable it now - it switches to port from otg to host mode.\n \n\n\n  \n \n\n\noverlays=dwc3-0-host\n\n\n  \n \n\n\n i will prepare some corrections to the device tree soon and will enable the host by default to make it consistent with vendor's configuration.\n \n", "name": "", "is_accepted": false }, { "text": "i recently received my nanopi r4s 4gb (my first sbc) and have been looking into running armbian on it (my first experience with it).\n \n\n\n  \n \n\n\n a few things i've noticed:\n \n\n\n - the official 20.11.6 build (buster) does not bring up the network properly. it pings but ssh never starts. 20.11.5 or a local build from trunk seem fine. just mentioning in case others wonder why the currently \"latest\" on the official page doesn't work\n \n\n\n - the gmac ethernet device naming seems unstable. it usually comes up as `eth1` but sometimes come up as `eth0`. it seems to depend on timing when the r8169 pci adapter is brought up (in the first case it's named `eth0` before being renamed to the stable `enp1s0`). is there precedent in armbian to force the integrated adapter to a more stable name such as `eno1` ?\n \n\n\n - the `armbian-hardware-optimization` script for `rk3399` seem to hardcode `eth0` for the gmac adapter, which causes errors when it ends up as eth1:\n \n\n\njan 13 01:35:46 nanopi-r4s armbian-hardware-optimization[638]: /usr/lib/armbian/armbian-hardware-optimization: line 234: /proc/irq/$(awk -f\":\" \"/eth0/ {print \\$1}\" </proc/interrupts | sed 's/\\ //g')/smp\\_affinity: no such file or directory\njan 13 01:35:46 nanopi-r4s armbian-hardware-optimization[638]: /usr/lib/armbian/armbian-hardware-optimization: line 235: /sys/class/net/eth0/queues/rx-0/rps\\_cpus: no such file or directory\njan 13 01:35:46 nanopi-r4s armbian-hardware-optimization[638]: /usr/lib/armbian/armbian-hardware-optimization: line 237: /sys/class/net/eth0/queues/rx-0/rps\\_flow\\_cnt: no such file or directory\n\n\n - when i first played with the official 20.11.05 build, i experienced the r8169 pci adapter sometimes not being detected on command line reboots (with cable plugged in if that makes a difference). i didn't see anything particular in the logs besides the device completely missing. i'll see if i can reproduce again and post the logs.\n \n\n\n - the built-in chrony seem to ignore my dhcp provided ntp server, and insists on using its built-in list. since this device will end up on an isolated vlan, it'll keep failing to synchronize clock. since this is not a desktop like device and i'm not particularly happy with networkmanager either (i need to build up a more complex vlan and bridge based topology), i'll probably just build a custom image without either and enable systemd's networkd and timesyncd.\n \n\n\n - the build scripts seem to pull an inordinate amount of dependencies (e.g. gcc for a bunch of platforms) even when simply building an image using \"prebuilt\" kernel and packages.  wondering if supporting a flow for \"light\" customization of images (mostly limited to package installation and adding configs) is something that was considered?\n \n", "name": "", "is_accepted": false }, { "text": "feel free to provide a pr that fixes this \n \n\n\n  \n \n\n\n\n\n issues with images that are not marked as supported are to be expected.\n \n", "name": "", "is_accepted": false }, { "text": "thank you for your notices. \n \n this hardware is new for us, we only made two builds and probably not a single run via our testing suite. things are not polished and will need a couple of weeks / months.\n \n\n\n  \n \n\n\n\n\n \n we can try this method:\n \n\n\n https://github.com/armbian/build/blob/master/config/sources/families/include/rockchip64\\_common.inc#l301-l307\n \n\n\n if it works for you, https://www.armbian.com/get-involved\n \n\n\n  \n \n\n\n\n\n  \n \n\n\n this script should be upgraded once to support multi adaptor. i think no other linux care about such optimisations, we lack of resources to keep up ... \n \n\n\n  \n \n\n\n\n\n \n all builds for r4s are experimental at this point and in case we have a realtek driver issue, it can take far longer to stabilise things. \n \n\n\n  \n \n\n\n\n\n \n network manager is here because its simple to get going for an average joe. we usually don't provide networking per board, sometimes yes. \n \n\n\n  \n \n\n\n old school ifconfig type of network settings is also operational - just define it and it will override network manager. if you need systemd networkd and timesyncd it should also work. you don't need to build custom images for that. just disable or configure networkmanager accordingly (i think it is doable without uninstalling it)\n \n\n\n  \n \n\n\n\n\n \n we are optimising build script round the clock. every day. making an image from pre-build kernel was added not long time ago, while refactoring and optimising build system to not download tools require significant work. since maintaining this tool is almost entirely our private costs and its not small, we can't really afford to pimp all \"nice to have\" features. we have constant flow of important, sometimes critical features / problems.\n \n\n\n  \n \n\n\n if you want to get this board to production levels faster and deeper - you need to https://www.armbian.com/get-involved we are already far over our limits and expects your help. not the other way around.\n \n\n\n  \n \n\n\n\n\n  \n \n\n\n we provide lots of features - just dive into \"developer guide\".\n \n\n\n https://docs.armbian.com/developer-guide\\_user-configurations/\n \n\n\n https://docs.armbian.com/developer-guide\\_build-preparation/\n \n", "name": "", "is_accepted": false }, { "text": "i definitely understand the lack of polish for such a new board, i already very grateful for where i got so far. as for latest being broken, i mainly wanted to make sure others looking could find the 20.11.5 build which boots fine,.\n \n\n\n  \n \n\n\n i managed to get networkd and timesyncd working, and found a way to get the gmac interface name stabilized using a systemd .link file targeting the device path. wondering if a udev method would be preferred? in this case i believe targeting by driver will not work, for some reason it seemed to be missing when i tried.\n \n\n\n  \n \n\n\n i was looking into rebuilding an image with these tweaks included, and so i could maybe contribute some of it back, but this is where i started struggling. the build environment is very picky, and while i have a few x64 linux systems around, none of them were full ubuntu or capable: synology nas with docker (lacking bin fmt tools), chromebook with linux crostini vm and docker (lacking loopback devices).  now that i finally got a build environment running, i'll try to see where i can help.\n \n\n\n  \n \n\n\n thanks for the pointers on the existing board customization. if you have any suggestions on how to improve the handling of multi adaptor boards in the scripts, i'll try to see what i can do.\n \n", "name": "", "is_accepted": false }, { "text": "yes.\n \n\n\n  \n \n\n\n\n\n  \n \n\n\n it runs well under docker if host is not too exotic ...\n \n\n\n  \n \n\n\n\n\n \n universal approach seems like a lot of work, but adding few bits for second nic here https://github.com/armbian/build/blob/master/packages/bsp/common/usr/lib/armbian/armbian-hardware-optimization#l245-l253 is already a good to go.\n \n", "name": "", "is_accepted": false }, { "text": "u-boot and device tree optimizing works wonders here - need to declare the interfaces before the kernel boots, otherwise it's going to grab the first one ready...\n \n", "name": "", "is_accepted": false }, { "text": "i'm running into the issue that @mathieuh described where enp1s0 comes up and the other interface either doesn't come up or shows up seemingly randomly as eth0 or eth1\n \n\n\n @mathieuhdid you ever find a fix for this?\n \n\n\n @sfx2000 do you have any pointers on u-boot and device tree optimization to resolve this?\n \n\n\n armbian on this board seems unreliable without resolving the network bringup consistency--what recommendations do people have to resolve this?\n \n", "name": "", "is_accepted": false }, { "text": "i didn't have this issue yet (at least on 5.10.21) but just in case i configured two networkd-based bridges, one with slave with name=enp* and another slave with name=eth*\n \n", "name": "", "is_accepted": false }, { "text": "i built my own armbian image from trunk (armbian\\_21.05.0-trunk\\_nanopi-r4s\\_focal\\_current\\_5.10.24.img) and it seems to work correctly.  it does not have the issues that i experienced using the pre-built image.\n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "hi, i have a question about the usb, it won't detect one of the usb port at the edge of the side.\n \n\n\n  \n \n\n\n i am currently using the latest armbian focal (armbian 21.02.3 focal) and i added `overlays=dwc3-0-host` at the `/boot/armbianenv.txt`\n \n\n\n i also upgraded the kernel to the latest\n \n\n\n but it still does not detect the usb port. i even upgrade the kernel to the latest `rockchip64\\_21.05.0`\n \n\n\n \n  \n \n\n\n[ 0.000000] kernel command line: root=uuid=907215a9-a8d9-4dac-8c3b-847a6c0a19ba rootwait rootfstype=ext4 console=ttys2,1500000 consoleblank=0 loglevel=1 ubootpart=07c8ce4c-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u cgroup\\_enable=cpuset cgroup\\_memory=1 cgroup\\_enable=memory swapaccount=1\n[ 1.251412] vcc5v0\\_usb1: supplied by vcc5v0\\_sys\n[ 1.251880] vcc5v0\\_usb2: supplied by vcc5v0\\_sys\n[ 1.256795] usbcore: registered new interface driver usbfs\n[ 1.256850] usbcore: registered new interface driver hub\n[ 1.256897] usbcore: registered new device driver usb\n[ 2.678800] usb usb1: new usb device found, idvendor=1d6b, idproduct=0002, bcddevice= 5.10\n[ 2.678812] usb usb1: new usb device strings: mfr=3, product=2, serialnumber=1\n[ 2.678821] usb usb1: product: xhci host controller\n[ 2.678829] usb usb1: manufacturer: linux 5.10.26-rockchip64 xhci-hcd\n[ 2.678837] usb usb1: serialnumber: xhci-hcd.0.auto\n[ 2.679982] usb usb2: we don't know the algorithms for lpm for this host, disabling lpm.\n[ 2.680128] usb usb2: new usb device found, idvendor=1d6b, idproduct=0003, bcddevice= 5.10\n[ 2.680138] usb usb2: new usb device strings: mfr=3, product=2, serialnumber=1\n[ 2.680147] usb usb2: product: xhci host controller\n[ 2.680156] usb usb2: manufacturer: linux 5.10.26-rockchip64 xhci-hcd\n[ 2.680163] usb usb2: serialnumber: xhci-hcd.0.auto\n[ 2.681192] usbcore: registered new interface driver usb-storage\n[ 2.733118] usbcore: registered new interface driver usbhid\n[ 2.733124] usbhid: usb hid core driver\n[ 3.776194] usb 2-1: new superspeed gen 1 usb device number 2 using xhci-hcd\n[ 3.797179] usb 2-1: new usb device found, idvendor=21c4, idproduct=0cd1, bcddevice=11.00\n[ 3.797201] usb 2-1: new usb device strings: mfr=1, product=2, serialnumber=3\n[ 3.797213] usb 2-1: product: usb flash drive\n[ 3.797224] usb 2-1: manufacturer: lexar\n[ 3.797236] usb 2-1: serialnumber: 04174mf5h7s9mplv\n[ 3.798801] usb-storage 2-1:1.0: usb mass storage device detected\n[ 3.806730] scsi host0: usb-storage 2-1:1.0\n[ 3.872408] usbcore: registered new interface driver uas\n\n\n  \n \n\n\nbus 002 device 002: id 21c4:0cd1 lexar usb flash drive\nbus 002 device 001: id 1d6b:0003 linux foundation 3.0 root hub\nbus 001 device 001: id 1d6b:0002 linux foundation 2.0 root hub\n\n\n  \n \n\n\n do you guys have any ideas?\n \n", "name": "", "is_accepted": false }, { "text": "have you developed an overlay???  i am not sure we have it - check with armbian-config -> system -> hardware\n \n\n\n  \n \n\n\n\n\n  \n \n\n\n why? we don't support this hardware and make no changes. you can check build system https://github.com/armbian/build and https://www.kernel.org/. why do you think this forum section (board bring up) exists?\n \n\n\n  \n \n\n\n there is no support (yet) for this hardware whatsoever and it might never be unless you start doing something. if you don't know much to help around this particular problem, you can trade your time in for https://forum.armbian.com/forum/54-help-wanted/ \n  \n \n\n\n\n\n \n we do, but no time to investigate them.\n \n", "name": "", "is_accepted": false } ]

[ { "text": "blerg.  the error is telling the truth.  most likely mirror sync.     mirror validation is something for us to work on next.\n \n", "name": "", "is_accepted": true }, { "text": "same issue with packages.bz2 but for buster\n \n\n\n  \n \n\n\n get:6 https://armbian.systemonachip.net/apt buster/main armhf packages [591 kb]                                          \n err:6 https://armbian.systemonachip.net/apt buster/main armhf packages                                                        \n   file has unexpected size (591174 != 590754). mirror sync in progress? [ip: 51.75.2.52 443]\n \n\n\n  \n \n\n\n e: failed to fetch https://armbian.systemonachip.net/apt/dists/buster/main/binary-armhf/packages.bz2  file has unexpected size (591174 != 590754). mirror sync in progress? [ip: 51.75.2.52 443]\n \n", "name": "", "is_accepted": false }, { "text": "also noticed yesterday. something is wrong there... @lanefu ?\n \n", "name": "", "is_accepted": false }, { "text": "this might help: \n \n\n\n  \n \n\n\nsudo apt-get -o acquire::forceipv4=true -o acquire::compressiontypes::order::=gz -o acquire::http::no-cache=true -o acquire::brokenproxy=true -o acquire::http::pipeline-depth=0 update\n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "sadly that didn't work for me - thank you for your efforts though.\n \n\n\n  \n \n\n\n i have one machine (nanopi neo2) that was built yesterday, running buster (armbian\\_20.11.3\\_nanopineo2\\_buster\\_current\\_5.9.14) that downloads 5 files under apt update and says all up to date. [i had successfully updated the machine already]\n \n\n\n i have a second machine (nanopi neo2) that was built today using the same image which fails.\n \n\n\n  \n \n\n\n i have tried the default and regional mirrors and get a mix of errors. the eu is an odd one as it says the mirror is not signed (seperate issue ?). i'm assuming that na is also the default as it's the same ip address.\n \n\n\n  \n \n\n\n apt-get -o acquire::forceipv4=true -o acquire::compressiontypes::order::=gz -o acquire::http::no-cache=true -o acquire::brokenproxy=true -o acquire::http::pipeline-depth=0 update\n \n\n\n ...\n \n\n\n reading package lists... done \n e: failed to fetch http://apt.armbian.com/dists/buster/main/binary-armhf/packages.gz  file has unexpected size (645768 != 645022). mirror sync in progress? [ip: 193.40.103.4 443] \n e: failed to fetch http://apt.armbian.com/dists/buster/main/binary-arm64/packages.gz  file has unexpected size (761502 != 758434). mirror sync in progress? [ip: 193.40.103.4 443] \n e: failed to fetch http://apt.armbian.com/dists/buster/main/contents-arm64.gz  file has unexpected size (11237461 != 11236778). mirror sync in progress? [ip: 193.40.103.4 443] \n e: failed to fetch http://apt.armbian.com/dists/buster/main/contents-armhf.gz  file has unexpected size (17272323 != 17272310). mirror sync in progress? [ip: 193.40.103.4 443] \n e: some index files failed to download. they have been ignored, or old ones used instead.\n \n\n\n \n apt-get -o acquire::forceipv4=true -o acquire::compressiontypes::order::=gz -o acquire::http::no-cache=true -o acquire::brokenproxy=true -o acquire::http::pipeline-depth=0 update \n ...\n \n\n\n reading package lists... done \n e: failed to fetch http://apt.armbian.com/region/na/dists/buster/main/binary-arm64/packages.gz  file has unexpected size (761502 != 758434). mirror sync in progress? [ip: 193.40.103.4 443] \n e: failed to fetch http://apt.armbian.com/region/na/dists/buster/main/binary-armhf/packages.gz  file has unexpected size (645768 != 645022). mirror sync in progress? [ip: 193.40.103.4 443] \n e: failed to fetch http://apt.armbian.com/region/na/dists/buster/main/contents-armhf.gz  file has unexpected size (17272323 != 17272310). mirror sync in progress? [ip: 193.40.103.4 443] \n e: failed to fetch http://apt.armbian.com/region/na/dists/buster/main/contents-arm64.gz  file has unexpected size (11237461 != 11236778). mirror sync in progress? [ip: 193.40.103.4 443] \n e: some index files failed to download. they have been ignored, or old ones used instead.\n \n\n\n  \n \n\n\n apt-get -o acquire::forceipv4=true -o acquire::compressiontypes::order::=gz -o acquire::http::no-cache=true -o acquire::brokenproxy=true -o acquire::http::pipeline-depth=0 update \n ...\n \n\n\n reading package lists... done \n w: gpg error: https://minio.k-space.ee/armbian/apt buster release: the following signatures were invalid: badsig 93d6889f9f0e78d5 igor pecovnik (ljubljana, slovenia) <[email protected]> \n e: the repository 'http://apt.armbian.com/region/eu buster release' is not signed. \n n: updating from such a repository can't be done securely, and is therefore disabled by default. \n n: see apt-secure(8) manpage for repository creation and user configuration details. \n  \n \n", "name": "", "is_accepted": false }, { "text": "working now - thank you\n \n", "name": "", "is_accepted": false }, { "text": "but i haven't change anything  that's what bothers us - we don't know why this is happening and there are lots of reports of other debian / ubuntu users reporting the same problem. its clearly not armbian specifics, but we would like to know why and get control over this ...\n \n", "name": "", "is_accepted": false }, { "text": "one thing i noticed - \n \n\n\n  \n \n\n\n when it failed\n \n\n\n  \n \n\n\n hit:1 http://security.debian.org buster/updates inrelease \n hit:2 http://deb.debian.org/debian buster inrelease \n hit:3 http://deb.debian.org/debian buster-updates inrelease \n hit:4 http://deb.debian.org/debian buster-backports inrelease \n get:5 https://armbian.systemonachip.net/apt buster inrelease [18.3 kb] \n get:6 https://armbian.systemonachip.net/apt buster/main armhf packages [645 kb] \n ign:6 https://armbian.systemonachip.net/apt buster/main armhf packages \n get:7 https://armbian.systemonachip.net/apt buster/main arm64 packages [758 kb] \n get:7 https://armbian.systemonachip.net/apt buster/main arm64 packages [758 kb] \n get:7 https://armbian.systemonachip.net/apt buster/main arm64 packages [758 kb] \n get:7 https://armbian.systemonachip.net/apt buster/main arm64 packages [758 kb] \n get:7 https://armbian.systemonachip.net/apt buster/main arm64 packages [758 kb] \n get:7 https://armbian.systemonachip.net/apt buster/main arm64 packages [758 kb] \n get:7 https://armbian.systemonachip.net/apt buster/main arm64 packages [758 kb] \n get:7 https://armbian.systemonachip.net/apt buster/main arm64 packages [758 kb] \n get:7 https://armbian.systemonachip.net/apt buster/main arm64 packages [758 kb] \n ign:7 https://armbian.systemonachip.net/apt buster/main arm64 packages \n get:16 https://armbian.systemonachip.net/apt buster/main arm64 contents (deb) [11.2 mb] \n ign:16 https://armbian.systemonachip.net/apt buster/main arm64 contents (deb) \n ign:16 http://apt.armbian.com/region/eu buster/main arm64 contents (deb) \n get:7 https://minio.k-space.ee/armbian/apt buster/main arm64 packages [758 kb] \n err:7 https://minio.k-space.ee/armbian/apt buster/main arm64 packages \n   file has unexpected size (761502 != 758434). mirror sync in progress? [ip: 193.40.103.4 443]\n \n\n\n  \n \n\n\n when it worked - \n \n\n\n  \n \n\n\n hit:1 http://security.debian.org buster/updates inrelease \n hit:2 http://deb.debian.org/debian buster inrelease \n hit:3 http://deb.debian.org/debian buster-updates inrelease \n hit:4 http://deb.debian.org/debian buster-backports inrelease \n get:5 https://mirrors.netix.net/armbian/apt buster inrelease [18.3 kb] \n get:6 https://mirrors.netix.net/armbian/apt buster/main arm64 packages [762 kb] \n get:7 https://mirrors.netix.net/armbian/apt buster/main armhf packages [646 kb] \n get:8 https://mirrors.netix.net/armbian/apt buster/main arm64 contents (deb) [11.2 mb] \n get:9 https://mirrors.netix.net/armbian/apt buster/main armhf contents (deb) [17.3 mb] \n get:10 https://mirrors.netix.net/armbian/apt buster/buster-utils arm64 packages [6,789 b] \n get:11 https://mirrors.netix.net/armbian/apt buster/buster-utils armhf packages [6,801 b] \n get:12 https://mirrors.netix.net/armbian/apt buster/buster-utils armhf contents (deb) [8,535 b] \n get:13 https://mirrors.netix.net/armbian/apt buster/buster-utils arm64 contents (deb) [8,531 b] \n get:14 https://mirrors.netix.net/armbian/apt buster/buster-desktop armhf packages [22.8 kb] \n get:15 https://mirrors.netix.net/armbian/apt buster/buster-desktop arm64 packages [20.9 kb] \n get:16 https://mirrors.netix.net/armbian/apt buster/buster-desktop arm64 contents (deb) [32.9 kb] \n get:17 https://mirrors.netix.net/armbian/apt buster/buster-desktop armhf contents (deb) [96.1 kb] \n fetched 29.9 mb in 52s (571 kb/s) \n reading package lists... done \n building dependency tree \n reading state information... done \n all packages are up to date.\n \n\n\n  \n \n\n\n it no longer reported ign for get 6 and get 7 and the file sizes were different. can you tell if a mirror sync was happening at the time ? \n \n", "name": "", "is_accepted": false }, { "text": "mirrors are pooling from our server.  i don't know and i don't know how this update is working - into the details. we already tried everything we could without deep investigation. for that time is needed.\n \n", "name": "", "is_accepted": false }, { "text": "could the issue be that every single file can be pulled from a different mirror? e.g. when packages list is pulled form one mirror, the content hashes from another one and the final package again from another one, it is easily possible that one does not match as for sure not all mirrors sync and have caches emptied exactly the same time. e.g. here my apt update which pulls from various different mirrors:\n \n\n\nget:5 https://minio.k-space.ee/armbian/apt buster inrelease [18.3 kb]\nget:6 https://minio.k-space.ee/armbian/apt buster/main armhf packages [591 kb]\nign:6 https://minio.k-space.ee/armbian/apt buster/main armhf packages\nget:7 https://minio.k-space.ee/armbian/apt buster/main arm64 packages [698 kb]\nign:7 https://minio.k-space.ee/armbian/apt buster/main arm64 packages\nign:7 https://apt.armbian.com buster/main arm64 packages\nign:7 https://apt.armbian.com buster/main arm64 packages\nget:8 https://minio.k-space.ee/armbian/apt buster/main arm64 contents (deb) [11.2 mb]\nign:8 https://minio.k-space.ee/armbian/apt buster/main arm64 contents (deb)\nget:9 https://minio.k-space.ee/armbian/apt buster/main armhf contents (deb) [17.3 mb]\nign:9 https://minio.k-space.ee/armbian/apt buster/main armhf contents (deb)\nget:6 https://us.mirrors.fossho.st/armbian/apt buster/main armhf packages [591 kb]\nerr:6 https://us.mirrors.fossho.st/armbian/apt buster/main armhf packages\n  file has unexpected size (591174 != 590754). mirror sync in progress? [ip: 23.237.182.68 443]\n  hashes of expected file:\n   - filesize:590754 [weak]\n   - sha512:bb903949666449552cda361ee24d4d0579baa72915b5fb3d7418acede319562ce4b93a15bf7605ae270bd9f0e59ececf622fea1365e8aa7a3d8339e2a2644f56\n   - sha256:d822f1c4a63ce566baa27d1f5c523057c1d295222f097b072dc8fbeb14a29bc3\n   - sha1:0f37871329a6a28cf7c53dd6ffd952342432c7ed [weak]\n   - md5sum:517fa48fb23e17f6c94248da6ce5b44b [weak]\n  release file created at: sat, 12 dec 2020 15:07:27 +0000\nget:7 https://armbian.systemonachip.net/apt buster/main arm64 packages [3941 kb]\nerr:7 https://armbian.systemonachip.net/apt buster/main arm64 packages\n\nget:8 https://mirrors.dotsrc.org/armbian-apt buster/main arm64 contents (deb) [11.2 mb]\nerr:8 https://mirrors.dotsrc.org/armbian-apt buster/main arm64 contents (deb)\n\nget:9 https://armbian.tnahosting.net/apt buster/main armhf contents (deb) [17.3 mb]\nerr:9 https://armbian.tnahosting.net/apt buster/main armhf contents (deb)\n\nfetched 18.3 kb in 55s (332 b/s)\nreading package lists... done\ne: failed to fetch https://us.mirrors.fossho.st/armbian/apt/dists/buster/main/binary-armhf/packages.bz2  file has unexpected size (591174 != 590754). mirror sync in progress? [ip: 23.237.182.68 443]\n   hashes of expected file:\n    - filesize:590754 [weak]\n    - sha512:bb903949666449552cda361ee24d4d0579baa72915b5fb3d7418acede319562ce4b93a15bf7605ae270bd9f0e59ececf622fea1365e8aa7a3d8339e2a2644f56\n    - sha256:d822f1c4a63ce566baa27d1f5c523057c1d295222f097b072dc8fbeb14a29bc3\n    - sha1:0f37871329a6a28cf7c53dd6ffd952342432c7ed [weak]\n    - md5sum:517fa48fb23e17f6c94248da6ce5b44b [weak]\n   release file created at: sat, 12 dec 2020 15:07:27 +0000\ne: failed to fetch https://armbian.systemonachip.net/apt/dists/buster/main/binary-arm64/packages\ne: failed to fetch https://mirrors.dotsrc.org/armbian-apt/dists/buster/main/contents-arm64.gz\ne: failed to fetch https://armbian.tnahosting.net/apt/dists/buster/main/contents-armhf.gz\ne: some index files failed to download. they have been ignored, or old ones used instead.\n\n\n the reported successful update from @dispo above was one case where everything was pulled from the same mirrors.netix.net mirror. \n \n i'm not sure how e.g. debian handles this, but it makes imo sense that somehow tie a client to a fixed mirror for a certain time. \n \n although i just compared the files of three mirrors and they all match, synced at 15-dec-2020 09:03. so not sure if this really is the issue.\n \n", "name": "", "is_accepted": false }, { "text": "sorry for the double post, i cannot edit my first post, it seems. i retried a few times and indeed the first successful update was when all got pulled from the same mirror:\n \n\n\nget:5 https://us.mirrors.fossho.st/armbian/apt buster inrelease [18.3 kb]\nget:6 https://us.mirrors.fossho.st/armbian/apt buster/main arm64 packages [701 kb]\nget:7 https://us.mirrors.fossho.st/armbian/apt buster/main armhf packages [591 kb]\nget:8 https://us.mirrors.fossho.st/armbian/apt buster/main armhf contents (deb) [17.3 mb]\nget:9 https://us.mirrors.fossho.st/armbian/apt buster/main arm64 contents (deb) [11.2 mb]\n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "exactly that is puzzling me. and after some time things go back to normal ... like some caching on client makes troubles.\n \n", "name": "", "is_accepted": false }, { "text": "it helps for me:\n \n\n\ndpkg-reconfigure ca-certificates\n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "i am getting this problem every time now on apt update on my armbian tinkerboard:\n \n\n\nhit:1 http://deb.debian.org/debian stable inrelease\nhit:2 http://deb.debian.org/debian stable-updates inrelease\nhit:3 http://deb.debian.org/debian-security stable/updates inrelease\nhit:4 http://ports.ubuntu.com focal inrelease\nhit:5 http://ports.ubuntu.com focal-security inrelease\nhit:6 https://download.docker.com/linux/debian buster inrelease\nhit:7 https://repos.influxdata.com/debian focal inrelease\nhit:8 http://ports.ubuntu.com focal-updates inrelease\nhit:9 http://ports.ubuntu.com focal-backports inrelease\nget:10 https://minio.k-space.ee/armbian/apt focal inrelease [18.2 kb]\nhit:11 https://packages.gitlab.com/runner/gitlab-runner/ubuntu focal inrelease\nget:12 https://minio.k-space.ee/armbian/apt focal/main armhf packages [645 kb]\nign:12 https://minio.k-space.ee/armbian/apt focal/main armhf packages\nget:12 https://us.mirrors.fossho.st/armbian/apt focal/main armhf packages [645 k b]\nerr:12 https://us.mirrors.fossho.st/armbian/apt focal/main armhf packages\n file has unexpected size (646150 != 645411). mirror sync in progress? [ip: 23. 237.182.68 443]\n hashes of expected file:\n - filesize:645411 [weak]\n - sha512:b1c4ae525ec721387a734673069af21268482d7324822871727d7b54f49a807cac2c e64b739b23cedbe309d3cd203af9ba297dee6042e4a9071cae5f986071c8\n - sha256:0ba674c754337dffa93851eb62e0f4841a4a29841ea708dd6bfde44ca2eedf3f\n - sha1:703b61507243cdddd410855b86e45d07955c53c9 [weak]\n - md5sum:e0745d84180e2a4deaa33c5ad469c24a [weak]\n release file created at: sat, 12 dec 2020 15:43:37 +0000\nfetched 18.2 kb in 4s (4,942 b/s)\nreading package lists... done\ne: failed to fetch https://us.mirrors.fossho.st/armbian/apt/dists/focal/main/binary-armhf/packages.gz file has unexpected size (646150 != 645411). mirror sync in progress? [ip: 23.237.182.68 443]\n hashes of expected file:\n - filesize:645411 [weak]\n - sha512:b1c4ae525ec721387a734673069af21268482d7324822871727d7b54f49a807cac2ce64b739b23cedbe309d3cd203af9ba297dee6042e4a9071cae5f986071c8\n - sha256:0ba674c754337dffa93851eb62e0f4841a4a29841ea708dd6bfde44ca2eedf3f\n - sha1:703b61507243cdddd410855b86e45d07955c53c9 [weak]\n - md5sum:e0745d84180e2a4deaa33c5ad469c24a [weak]\n release file created at: sat, 12 dec 2020 15:43:37 +0000\ne: some index files failed to download. they have been ignored, or old ones used instead.\n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "# sudo apt-get -o acquire::forceipv4=true -o acquire::compressiontypes::order::=gz -o acquire::http::no-cache=true -o acquire::brokenproxy=true -o acquire::http::pipeline-depth=0 update\nhit:1 http://deb.debian.org/debian stable inrelease\nhit:2 http://deb.debian.org/debian stable-updates inrelease\nhit:3 http://ports.ubuntu.com focal inrelease\nhit:4 http://deb.debian.org/debian-security stable/updates inrelease\nhit:5 http://ports.ubuntu.com focal-security inrelease\nhit:6 https://download.docker.com/linux/debian buster inrelease\nhit:7 https://repos.influxdata.com/debian focal inrelease\nhit:8 http://ports.ubuntu.com focal-updates inrelease\nhit:9 http://ports.ubuntu.com focal-backports inrelease\nget:10 https://armbian.tnahosting.net/apt focal inrelease [18.2 kb]\nhit:11 https://packages.gitlab.com/runner/gitlab-runner/ubuntu focal inrelease\nget:12 https://armbian.tnahosting.net/apt focal/main armhf packages [645 kb]\nign:12 https://armbian.tnahosting.net/apt focal/main armhf packages\nget:12 https://armbian.systemonachip.net/apt focal/main armhf packages [645 kb]\nerr:12 https://armbian.systemonachip.net/apt focal/main armhf packages\n file has unexpected size (646150 != 645411). mirror sync in progress? [ip: 51.75.2.52 443]\n hashes of expected file:\n - filesize:645411 [weak]\n - sha512:b1c4ae525ec721387a734673069af21268482d7324822871727d7b54f49a807cac2ce64b739b23cedbe309d3cd203af9ba297dee6042e4a9071cae5f986071c8\n - sha256:0ba674c754337dffa93851eb62e0f4841a4a29841ea708dd6bfde44ca2eedf3f\n - sha1:703b61507243cdddd410855b86e45d07955c53c9 [weak]\n - md5sum:e0745d84180e2a4deaa33c5ad469c24a [weak]\n release file created at: sat, 12 dec 2020 15:43:37 +0000\nreading package lists... done\ne: failed to fetch https://armbian.systemonachip.net/apt/dists/focal/main/binary-armhf/packages.gz file has unexpected size (646150 != 645411). mirror sync in progress? [ip: 51.75.2.52 443]\n hashes of expected file:\n - filesize:645411 [weak]\n - sha512:b1c4ae525ec721387a734673069af21268482d7324822871727d7b54f49a807cac2ce64b739b23cedbe309d3cd203af9ba297dee6042e4a9071cae5f986071c8\n - sha256:0ba674c754337dffa93851eb62e0f4841a4a29841ea708dd6bfde44ca2eedf3f\n - sha1:703b61507243cdddd410855b86e45d07955c53c9 [weak]\n - md5sum:e0745d84180e2a4deaa33c5ad469c24a [weak]\n release file created at: sat, 12 dec 2020 15:43:37 +0000\ne: some index files failed to download. they have been ignored, or old ones used instead.\n\n\n\n  \n \n\n\nhit:1 http://deb.debian.org/debian stable inrelease\nhit:2 http://deb.debian.org/debian stable-updates inrelease\nhit:3 http://deb.debian.org/debian-security stable/updates inrelease\nhit:4 http://ports.ubuntu.com focal inrelease\nhit:5 http://ports.ubuntu.com focal-security inrelease\nhit:6 https://download.docker.com/linux/debian buster inrelease\nhit:7 http://ports.ubuntu.com focal-updates inrelease\nhit:8 https://repos.influxdata.com/debian focal inrelease\nhit:9 http://ports.ubuntu.com focal-backports inrelease\nget:10 https://armbian.hosthatch.com/apt focal inrelease [18.2 kb]\nhit:11 https://packages.gitlab.com/runner/gitlab-runner/ubuntu focal inrelease\nget:12 https://armbian.hosthatch.com/apt focal/main armhf packages [645 kb]\nign:12 https://armbian.hosthatch.com/apt focal/main armhf packages\nget:12 https://mirrors.dotsrc.org/armbian-apt focal/main armhf packages [645 kb]\nerr:12 https://mirrors.dotsrc.org/armbian-apt focal/main armhf packages\n file has unexpected size (646150 != 645411). mirror sync in progress? [ip: 130.225.254.116 443]\n hashes of expected file:\n - filesize:645411 [weak]\n - sha512:b1c4ae525ec721387a734673069af21268482d7324822871727d7b54f49a807cac2ce64b739b23cedbe309d3cd203af9ba297dee6042e4a9071cae5f986071c8\n - sha256:0ba674c754337dffa93851eb62e0f4841a4a29841ea708dd6bfde44ca2eedf3f\n - sha1:703b61507243cdddd410855b86e45d07955c53c9 [weak]\n - md5sum:e0745d84180e2a4deaa33c5ad469c24a [weak]\n release file created at: sat, 12 dec 2020 15:43:37 +0000\nfetched 18.2 kb in 3s (6,143 b/s)\nreading package lists... done\ne: failed to fetch https://mirrors.dotsrc.org/armbian-apt/dists/focal/main/binary-armhf/packages.gz file has unexpected size (646150 != 645411). mirror sync in progress? [ip: 130.225.254.116 443]\n hashes of expected file:\n - filesize:645411 [weak]\n - sha512:b1c4ae525ec721387a734673069af21268482d7324822871727d7b54f49a807cac2ce64b739b23cedbe309d3cd203af9ba297dee6042e4a9071cae5f986071c8\n - sha256:0ba674c754337dffa93851eb62e0f4841a4a29841ea708dd6bfde44ca2eedf3f\n - sha1:703b61507243cdddd410855b86e45d07955c53c9 [weak]\n - md5sum:e0745d84180e2a4deaa33c5ad469c24a [weak]\n release file created at: sat, 12 dec 2020 15:43:37 +0000\ne: some index files failed to download. they have been ignored, or old ones used instead.\n\n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "and after trying around 20 times:\n \n\n\n # apt update\nhit:1 http://deb.debian.org/debian stable inrelease\nhit:2 http://deb.debian.org/debian stable-updates inrelease\nhit:3 http://ports.ubuntu.com focal inrelease\nhit:4 http://deb.debian.org/debian-security stable/updates inrelease\nget:5 http://ports.ubuntu.com focal-security inrelease [109 kb]\nhit:6 https://download.docker.com/linux/debian buster inrelease\nhit:7 https://repos.influxdata.com/debian focal inrelease\nget:8 http://ports.ubuntu.com focal-updates inrelease [114 kb]\nget:9 http://ports.ubuntu.com focal-backports inrelease [101 kb]\nhit:11 https://packages.gitlab.com/runner/gitlab-runner/ubuntu focal inrelease\nget:10 https://us.mirrors.fossho.st/armbian/apt focal inrelease [18.2 kb]\nget:12 https://us.mirrors.fossho.st/armbian/apt focal/main armhf packages [646 kb]\nfetched 988 kb in 4s (243 kb/s)\nreading package lists... done\nbuilding dependency tree\nreading state information... done\n25 packages can be upgraded. run 'apt list --upgradable' to see them.\n\n\n\n  \n \n\n\n and now its working every time after something like 2 days of failing.\n \n", "name": "", "is_accepted": false }, { "text": "failed -\n \n\n\n  \n \n\n\n get:6 https://minio.k-space.ee/armbian/apt buster/main arm64 packages [758 kb] \n \n\n\n ign:6 https://minio.k-space.ee/armbian/apt buster/main arm64 packages \n get:7 https://minio.k-space.ee/armbian/apt buster/main armhf packages [645 kb] \n ign:7 https://minio.k-space.ee/armbian/apt buster/main armhf packages\n \n\n\n  \n \n\n\n worked - \n \n\n\n \n get:6 https://us.mirrors.fossho.st/armbian/apt buster/main armhf packages [646 kb] \n get:7 https://us.mirrors.fossho.st/armbian/apt buster/main arm64 packages [762 kb]\n \n\n\n  \n \n\n\n edit: same machine, minutes apart but to a different mirror. \n  \n \n\n\n the file sizes are the same as yesterday in each case. i'm wondering where the failing mirror is getting the incorrect 645/758 from instead of the correct 646/762.\n \n\n\n i've tried to find detail of how this process work but didnt get very far. i have been avoiding searches via google though \n \n\n\n  \n \n\n\n it also always appears to be 'main armhf packages' that fails and occassionally 'main arm64 packages'\n \n", "name": "", "is_accepted": false }, { "text": "i feel like that might be the reason why ubuntu and debian don't do this kind of automatic mirror redirection. (at least i have never noticed it) \n maybe we should just choose a mirror manually like we do on debian and ubuntu. \n \n\n\n a good tool to do this with would probably be mintsources: \n screenshot.png\n \n", "name": "", "is_accepted": false }, { "text": "$ sudo apt update\nhit:1 http://ports.ubuntu.com focal inrelease\nhit:3 http://ports.ubuntu.com focal-security inrelease\nhit:4 http://ports.ubuntu.com focal-updates inrelease\nhit:5 http://ports.ubuntu.com focal-backports inrelease\nget:2 https://armbian.systemonachip.net/apt focal inrelease [18.2 kb]\nget:6 https://armbian.systemonachip.net/apt focal/focal-utils armhf packages [5,034 b]\nget:7 https://armbian.systemonachip.net/apt focal/main armhf packages [645 kb]\nget:7 https://armbian.systemonachip.net/apt focal/main armhf packages [645 kb]\nign:7 https://armbian.systemonachip.net/apt focal/main armhf packages\nget:7 https://us.mirrors.fossho.st/armbian/apt focal/main armhf packages [645 kb]\nerr:7 https://us.mirrors.fossho.st/armbian/apt focal/main armhf packages\n file has unexpected size (646150 != 645411). mirror sync in progress? [ip: 23.237.182.68 443]\n hashes of expected file:\n - filesize:645411 [weak]\n - sha512:b1c4ae525ec721387a734673069af21268482d7324822871727d7b54f49a807cac2ce64b739b23cedbe309d3cd203af9ba297dee6042e4a9071cae5f986071c8\n - sha256:0ba674c754337dffa93851eb62e0f4841a4a29841ea708dd6bfde44ca2eedf3f\n - sha1:703b61507243cdddd410855b86e45d07955c53c9 [weak]\n - md5sum:e0745d84180e2a4deaa33c5ad469c24a [weak]\n release file created at: sat, 12 dec 2020 15:43:37 +0000\nget:9 https://armbian.systemonachip.net/apt focal/main arm64 packages [759 kb]\nign:9 https://armbian.systemonachip.net/apt focal/main arm64 packages\nreading package lists... done \ne: failed to fetch https://us.mirrors.fossho.st/armbian/apt/dists/focal/main/binary-armhf/packages.gz file has unexpected size (646150 != 645411). mirror sync in progress? [ip: 23.237.182.68 443]\n hashes of expected file:\n - filesize:645411 [weak]\n - sha512:b1c4ae525ec721387a734673069af21268482d7324822871727d7b54f49a807cac2ce64b739b23cedbe309d3cd203af9ba297dee6042e4a9071cae5f986071c8\n - sha256:0ba674c754337dffa93851eb62e0f4841a4a29841ea708dd6bfde44ca2eedf3f\n - sha1:703b61507243cdddd410855b86e45d07955c53c9 [weak]\n - md5sum:e0745d84180e2a4deaa33c5ad469c24a [weak]\n release file created at: sat, 12 dec 2020 15:43:37 +0000\ne: some index files failed to download. they have been ignored, or old ones used instead.\n\n\n  \n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "could be. \n \n\n\n  \n \n\n\n\n\n \n we are looking into the way of minimise maintenance and provide better service - if it would work as designed. current way a dead mirror can be removed / added when comes back. also when we do update, new artefacts goes to the fastest server which become the only source until others are synched. it is possible that we will only change one problem with another ... this needs to be further researched to understand the decision why mint is having this solved this way. afaik debian used to have redirector running, but its down (for good) ... for some maintenance reasons. i don't recall this kind of issues.\n \n", "name": "", "is_accepted": false }, { "text": "i've been having this problem off and on for a while now as well.  the only solution that i found is simply to wait longer until more mirrors are updated and hope that one of the updated ones is selected.\n \n\n\n  \n \n\n\n @igorhave you tried this: https://apt-mirror-updater.readthedocs.io/en/latest/readme.html\n \n\n\n i realize it's still in beta but it may be worth testing.\n \n", "name": "", "is_accepted": false }, { "text": "this looks more like a solution for a (business) client. not server side trouble which we are looking for.  our system is combined with (currently in round robin mode, soon geo based) router https://github.com/armbian/dl-router and a script that delivers data to the rsyncd server where mirrors are pulling off. so far we are mitigating only \"file not found\" problem by delaying synching indexes. we wait until files are synched, then we push out index synching. but most likely here is the catch. we should disable all mirrors and enable them one by one as soon as indexes on those are synched. we think that is the solution. just need to test and implement. as always, time is the problem  \n \n thanks for the input.\n \n", "name": "", "is_accepted": false }, { "text": "hi sorry for the troubles.   i've added some quick documentation on how to manually choose a mirror.   hopefully this is an easy workaround for the short-term\n \n\n\n  \n \n\n\n https://docs.armbian.com/user-guide\\_fine-tuning/#choosing-an-apt-mirror\n \n", "name": "", "is_accepted": false }, { "text": "update-ca-certificates\n \n", "name": "", "is_accepted": false }, { "text": "thanks, this did the trick for me. a choose manually a mirror and worked.\n \n", "name": "", "is_accepted": false }, { "text": "update: \n \n we deployed geoip based redirecting over the weekend.   the defaults should likely send most to an appropriate mirror, but choosing a mirror or region is still a good thing to do.    not all ips match correctly.\n \n", "name": "", "is_accepted": false }, { "text": "this problem should be fixed by now.\n \n\n\n  \n \n\n\n one of our mirror is \"kubernetes native, high performance object storage amazon s3 compatible\" and there we had to use different sync method. we also synched from there further since host has a fast connection ... \n \n\n\n  \n \n\n\n tl;dr; wrong sync parameter \n \n", "name": "", "is_accepted": false }, { "text": "great, many thanks for identifying and fixing it!\n \n", "name": "", "is_accepted": false } ]

[ { "text": "now rtc patch for n2 in armbian build system.\n \n\n\n hope problem is solved.\n \n", "name": "", "is_accepted": true }, { "text": "i'm in the same boat, as it seems. can you use your gpio?\n ", "name": "", "is_accepted": false }, { "text": "odroid-n2 external rtc is attached on i2c3 which isn't enabled by default.\n \n\n\n to enable it, use this overlay source and compile it and load it.\n \n\n\n/dts-v1/;\n/plugin/;\n\n/ {\n compatible = \"amlogic,meson-g12b\";\n fragment@0 {\n target-path = \"/aliases\";\n \\_\\_overlay\\_\\_ {\n i2c3a = \"/soc/bus@ffd00000/i2c@1c000\";\n };\n };\n fragment@1 {\n target-path = \"/soc/bus@ffd00000/i2c@1c000\";\n \\_\\_overlay\\_\\_ {\n status = \"okay\";\n pinctrl-0 = <&i2c3\\_sda\\_a\\_pins>, <&i2c3\\_sck\\_a\\_pins>;\n pinctrl-names = \"default\";\n pcf8563: rtc@51 { /*i2c-bus slave address: read a3h and write a2h*/\n compatible = \"nxp,pcf8563\";\n reg = <0x51>;\n };\n };\n };\n};\n\n\n then, the i2c will appear as well as module for pcf8563 will be loaded, it will be hookup as /dev/rtc1, you can then set the clock and re-read it using :\n \n\n\nhwclock -w -f /dev/rtc1\nhwclock -f /dev/rtc1\n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "thank you for help.\n \n\n\n could you please point to faq, howto or something like it to read how to \"use this overlay source and compile it and load it\"? sorry, i am not \"in context\" for a while. but i will :)\n \n", "name": "", "is_accepted": false }, { "text": "install dt compiler from http://ftp.debian.org/debian/pool/main/d/device-tree-compiler/device-tree-compiler\\_1.4.7-3\\_arm64.deb\n \n\n\n then, compile the dts i've provided and then load it dynamically :\n \n\n\ndtc -@ -i dts -o dtb -o [email protected] [email protected]\nmkdir /sys/kernel/config/device-tree/overlays/i2c3a\ncat [email protected] > /sys/kernel/config/device-tree/overlays/i2c3a/dtbo\n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "it works!\n \n\n\n thank you!\n \n\n\n  \n \n\n\n do you think i have to ask armbian kernel builders to include your code into kernel image?\n \n", "name": "", "is_accepted": false }, { "text": "i'm one of the main armbian devs, so, yes, i will add the dt overlay in builds in the near future ...\n \n", "name": "", "is_accepted": false }, { "text": "what kernel  i have to install to got it work?\n \n\n\n linux-image-current, -dev, -legacy, other sources?\n \n", "name": "", "is_accepted": false }, { "text": "i've not done the commit yet, \"time is the missing ingredient\" ...\n \n\n\n but feel free to compile above dt overlay !\n \n", "name": "", "is_accepted": false }, { "text": "yes, i did it already... but i not understand how to avoid manual path creation and dt copying with manual hwclock run. to let it work as it should — set system clock at a boot time.\n \n", "name": "", "is_accepted": false }, { "text": "hi martinayotte,\n \n\n\n  \n \n\n\n thanks for providing quick fix via device tree overlay. also i am very happy to see we got armbian and a much more recent kernel running on hk odroid n2! thx for all your hard work!\n \n\n\n  \n \n\n\n do we lack full support for overlays atm? even if we do as described for allwiner based boards?\n \n\n\n 'cause i tried to use \"user\\_overlays\" and \"overlay\" options in \"armbianenv.txt\" as described here:\n \n\n\n https://docs.armbian.com/hardware\\_allwinner\\_overlays/\n \n\n\n but couldn't get it to work.\n \n\n\n just wanna know if i am missing something/ doing it wrong or it's known/intended\n \n\n\n  \n \n\n\n/boot/armbianenv.txt\n\nverbosity=1\nuser\\_overlays=odroid-n2-ic2@1c000\nusbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u <= autoadded so file seems to be found\n\n\n adding the entries and copying the files myself didn't change anything.\n \n\n\n adding useroverlay via armbian-add-overlay  => overlays are supported only on a10... => removing the allwiner sanity check from\n \n\n\n/usr/sbin/armbian-add-overlay line 38-41\n\n\n edits armbianenv.txt correctly by adding \"user\\_overlays\" option and copying the files to \"/boot/overlay-user/\" which seems be the desired location. but no pcf8563 modules are loaded after boot. \n \n\n\n i also tried adding the dtbo to /boot/dtb/overlay /boot/dtb/amlogic/overlays and so on.\n \n\n\n  \n \n\n\n your mentioned example rc.local works fine instead.\n \n\n\nmkdir /sys/kernel/config/device-tree/overlays/i2c3a\ncat /root/[email protected] > /sys/kernel/config/device-tree/overlays/i2c3a/dtbo\n\nsystemctl stop ntp\nntpd -qg\nsystemctl start ntp\nhwclock --systohc -f /dev/rtc1\n\n\n  \n \n\n\n tia\n \n", "name": "", "is_accepted": false }, { "text": "@martinayotte pleeease.\n \n\n\n so long present, but not in armbian trunk.\n \n\n\n @chewitt have same patches too, but not push.\n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "now i2c3 in armbian patches\n \n\n\n https://github.com/armbian/build/blob/master/patch/kernel/meson64-current/hardkernel-0007-n2-arm64-dts-add-i2c2-i2c3-node.patch\n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "reporting back\n \n\n\n working out of the box now with latest focal image. thanks for the effort\n \n", "name": "", "is_accepted": false } ]

[ { "text": "i just created the mentioned section.\n \n\n\n it is not visible to guests so if we choose to remove it again there will not be any seo impact whatsoever. does not make sense to make it public anways since it is dedicated to (long-term) members only.\n \n\n\n users need to be \"members\" and have some approved postings across the entire community.\n \n", "name": "", "is_accepted": true }, { "text": "i think the idea is great, the implementation might be a challenge. \n i'd say: leave it to up to someone else as even if armbian staff isn't involved, potential issues might reflect bad on the armbian project, especially coming from armbian.com.\n \n\n\n if the interest was really that high, there would already be a dedicated subreddit full of people selling sbcs. (/r/homelabsales might count)\n \n", "name": "", "is_accepted": false }, { "text": "limited to probably long term community members only should prevent that. we are not looking to become next ebay. just to give people place to get rid of stuff they don't need. perhaps also give away for free.\n \n\n\n  \n \n\n\n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "thinkpad forums have such a marketplace.  which in reality is just another subforum.  although they don't limit participation in any way.  instead they have one long feedback thread where everyone posts their results, e.g. \"igor sent the package on time and well wrapped\" etc. so people can just search in there themselves for \"buyer/seller feedback\" and there is not even any need of staff approving any one or limits of any kind.  completely caveat emptor, as they say.\n \n\n\n  \n \n\n\n if above way is deemed sufficient, the only \"loophole\" i could see would be people changing their user name.  so i just took a quick look around my own profile, and this does not seem to be possible?\n \n\n\n  \n \n\n\n in fact i acquired highly sought after flexview screen from guy halfway around the world through thinkpad marketplace.    but i am kind of person that doesn't mind dealing directly with people 1:1 via craigslist, etc.  other people like to have some mediator at least nominally involved (ebay, etc.) so this sort of thing would not be for those kind of people.\n \n", "name": "", "is_accepted": false } ]

[ { "text": "hi,\n \n\n\n i'm still unable to build the module correctly. the zfs kernel module is build for kernel '4.4.213-rockchip64' (the headers version name) but the kernel is '4.4.213-rk3399'.\n \n\n\n  \n \n\n\nspl: version magic '4.4.213-rockchip64 smp mod\\_unload aarch64' should be '4.4.213-rk3399 smp mod\\_unload aarch64'\n\n\n  \n \n\n\n i'm not sure this can be fixed without editing kernel headers, either : \n \n\n\n/usr/src/linux-headers-4.4.213-rockchip64/include/config/kernel.release\n/usr/src/linux-headers-4.4.213-rockchip64/include/generated/utsrelease.h\n\n\n  \n \n\n\n  \n \n\n\n @shadowdance are you using the \"current\" 5.9 kernel ? maybe this has been fixed for this kernel ?\n \n\n\n  \n \n\n\n btw as the procedure is a bit tiring to do by hand, i wrote some scripts to automate this (build module on ubuntu, utils on buster) : https://github.com/salamandar/armbian\\_zfs\\_compiler/\n \n\n\n  \n \n\n\n mod edit:  above is third party script, as always, make sure you understand what is going on before running it on your system.\n \n\n\n  \n \n\n\n having gotten that disclaimer out of the way, thanks for your contribution, @salamandar!\n \n\n\n  \n \n\n\n i took the liberty of marking this as solution.  i also made note of the link to refer others to, later.\n \n\n\n  \n \n\n\n cheers,\n \n\n\n trs-80\n \n", "name": "", "is_accepted": true }, { "text": "tried this?\n \n\n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "the suggestion igor made in that thread solves the 0.8.3 problems on 5.8 because certain kernel methods were flagged as gpl and the module won't compile.\n \n\n\n as others in that thread pointed out, using the newer 0.8.4 package works on focal but not buster.\n \n\n\n  \n \n\n\n 0.8.4 compiles correctly against the rockchip64 kernel on focal (gcc9) and bullseye (gcc10), but not with buster (gcc8).\n \n\n\n 2.0.0-rc follows the same pattern.\n \n\n\n  \n \n\n\n the rockchip64 kernel is built using the armbian toolchain, which is focal based and thus using gcc 9.\n \n\n\n  \n \n\n\n i haven't been able to come up with any other theory than how the compiler is detecting if it should use config\\_stackprotector or config\\_stackprotector\\_per\\_task.\n \n\n\n  \n \n\n\n it's only a theory, and i don't know how to prove or disprove it, short of building the same 5.8.13 kernel with gcc 8 and trying to build the module against it (which is probably my next step)\n \n", "name": "", "is_accepted": false }, { "text": "i am running armbian bionic and installed gcc-9 and gcc-10 from \"ppa:ubuntu-toolchain-r/test\". i tried both compilers with dkms and am still getting\n \n\n\nerror: modpost: \"\\_\\_stack\\_chk\\_guard\" [/root/zfs/module/zfs/zfs.ko] undefined!\n\n\n  \n \n\n\n i set the compiler version by exporting `cc`, but i don't see any mention of the compiler version in the dkms build output. the make.log does show different compiler warnings, so i'm pretty sure i am successfully setting the compiler version.\n \n", "name": "", "is_accepted": false }, { "text": "@brocklobsta sounds like you're setting gcc correctly, and the issue thats left is probably that the zfs-dkms module is too old (try finding 0.8.4+ per here)\n \n\n\n  \n \n\n\n for the issue on buster, i think i've nailed the problem down.\n \n\n\n  \n \n\n\n stackprotector\\_per\\_task is defined as such\n \n\n\nconfig cc\\_have\\_stackprotector\\_sysreg\n def\\_bool $(cc-option,-mstack-protector-guard=sysreg -mstack-protector-guard-reg=sp\\_el0 -mstack-protector-guard-offset=0)\n\nconfig stackprotector\\_per\\_task\n def\\_bool y\n depends on stackprotector && cc\\_have\\_stackprotector\\_sysreg\n\n\n  \n \n\n\n gcc in the focal build environment supports the options required for cc\\_have\\_stackprotector\\_sysreg\n \n\n\n$ gcc --version\ngcc (ubuntu 9.3.0-10ubuntu2) 9.3.0\n\n$ gcc -mstack-protector-guard=sysreg -mstack-protector-guard-reg=sp\\_el0 -mstack-protector-guard-offset=0\ngcc: fatal error: no input files\ncompilation terminated.\n\n\n  \n \n\n\n whereas the gcc version buster doesn't support these.\n \n\n\n$ gcc --version\ngcc (debian 8.3.0-6) 8.3.0\n\n$ gcc -mstack-protector-guard=sysreg -mstack-protector-guard-reg=sp\\_el0 -mstack-protector-guard-offset=0\ngcc: error: unrecognized command line option '-mstack-protector-guard=sysreg'; did you mean '-fstack-protector-strong'?\ngcc: error: unrecognized command line option '-mstack-protector-guard-reg=sp\\_el0'; did you mean '-fstack-protector-all'?\ngcc: error: unrecognized command line option '-mstack-protector-guard-offset=0'; did you mean '-fstack-protector-strong'?\ngcc: fatal error: no input files\ncompilation terminated.\n\n\n  \n \n\n\n since the kernel is built for both focal + buster, should features like this be disabled or are there some other workarounds?\n \n", "name": "", "is_accepted": false }, { "text": "@jbergler i am building the latest zfs release 0.8.5 with gcc-9 and gcc-10 on armbian bionic and the issue still occurs. have you tried a build with gcc-9/10?\n \n", "name": "", "is_accepted": false }, { "text": "i am using armbian bionic. i have upgraded the gcc from ppa:ubuntu-toolchain-r/test repo to gcc-10, but i was having the same error message until today:\n \n\n\n  \n \n\n\n error: modpost: \"\\_\\_stack\\_chk\\_guard\" [/root/zfs/zfs-0.8.5/module/zfs/zfs.ko] undefined! \n error: modpost: \"\\_\\_stack\\_chk\\_guard\" [/root/zfs/zfs-0.8.5/module/zcommon/zcommon.ko] undefined! \n ...\n \n\n\n  \n \n\n\n today armbian upgraded the kernel&header package (#20.08.8) and zfs compiles without any errors. i checked the changelog from https://docs.armbian.com/release\\_changelog/\n \n\n\n but could not see any related changes. most probably armbian is now building the kernel with a newer gcc version, because i did not change anything since the build failed.\n \n", "name": "", "is_accepted": false }, { "text": "@turkerali\n \n\n\n which kernel package are you using? linux-image-current-rockchip64? i am not able to compile with the \"current\" kernel, but the \"legacy\" kernel has always worked.\n \n", "name": "", "is_accepted": false }, { "text": "yes, i am using the linux-image-current-rockchip64 (5.8.x) on nanopc-t4.\n \n\n\n  \n \n\n\n there is one more possibility that might have resolved the issue for me. when you install the \"linux-headers\" package, apt runs \"make scripts\" command at the end of installation,\n \n\n\n which builds some helper utilities inside the linux-headers package. i believe these helper utilities are responsible for module compilation and the \"modpost\" errors.\n \n\n\n  \n \n\n\n as a workaround, before you install the linux-headers package, make sure to upgrade the gcc version to gcc-9 or gcc-10 from ppa:ubuntu-toolchain-r/test repo.\n \n\n\n then install the linux-headers package. if you do this, the binary utilites in the scripts folder will be built with the upgraded gcc, and will be able to build & link the zfs modules.\n \n\n\n  \n \n\n\n i may be wrong, but it's worth trying.\n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "thanks @turkerali! recompiling the kernel headers with gcc-10 fixed the issue.\n \n", "name": "", "is_accepted": false }, { "text": "@jberglerthanks again for the zfs module you shared on the helios64 support thread. it's been running for days without any problems.\n \n\n\n if it's not too much trouble, would you mind sharing the process you used to build it?\n \n", "name": "", "is_accepted": false }, { "text": "yes, that would be much appreciated.\n \n\n\n and thanks again @jbergler for your work\n \n", "name": "", "is_accepted": false }, { "text": "these won't be exact instructions, since i decided to switch to focal (mostly for other reasons).\n \n\n\n  \n \n\n\nmkdir zfs-scratch\ncd zfs-scratch\n\napt-get download linux-headers-current-rockchip64\ngit clone -b zfs-0.8.5 https://github.com/openzfs/zfs.git \n\ndocker run --rm -it -v $(pwd):/scratch ubuntu:focal\n\n# inside the container\ncd /scratch\napt update\napt install build-essential autoconf automake bison flex libtool gawk alien fakeroot dkms libblkid-dev uuid-dev libudev-dev libssl-dev zlib1g-dev libaio-dev libattr1-dev libelf-dev python3 python3-dev python3-setuptools python3-cffi libffi-dev\ndpkg -i linux-headers-current-*.deb\n\ncd zfs\nsh autogen.sh\n./configure\nmake -s -j$(nproc) deb\n\n\n  \n \n\n\n at that point you can exit the container (it'l vanish because of the --rm) and inside zfs-scratch/zfs you should have a bunch of debian packages you can install\n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "@jberglerthank you very much for that. the steps just needed a small tweak, but it works perfectly. running on kernel 5.8.16 right now!\n \n\n\n the small tweak is just to also install flex and bison before installing the kernel headers package (or run apt-get install -f if already installed).\n \n", "name": "", "is_accepted": false }, { "text": "hey i was able to build zfs zfs-2.0.0-rc6 from sources using @jbergler instructions on my helios64 . debian (inside docker ubuntu container) \n \n\n\n  \n \n\n\n root@helios64:~# uname -a\n \n\n\n linux helios64 5.9.10-rockchip64 #trunk.39 smp preempt sun nov 22 10:36:59 cet 2020 aarch64 gnu/linux\n \n\n\n root@helios64:~#\n \n\n\n  \n \n\n\n but now im stuck with old glibc version.\n \n\n\nroot@helios64:~/zfs\\_deb# zfs\nzfs: /lib/aarch64-linux-gnu/libm.so.6: version `glibc\\_2.29' not found (required by /lib/aarch64-linux-gnu/libzfs.so.4)\nroot@helios64:~/zfs\\_deb# zfs --version\nzfs: /lib/aarch64-linux-gnu/libm.so.6: version `glibc\\_2.29' not found (required by /lib/aarch64-linux-gnu/libzfs.so.4)\nroot@helios64:~/zfs\\_deb#\n\nroot@helios64:~/zfs\\_deb# ldd --version\nldd (debian glibc 2.28-10) 2.28\ncopyright (c) 2018 free software foundation, inc.\nthis is free software; see the source for copying conditions.  there is no\nwarranty; not even for merchantability or fitness for a particular purpose.\nwritten by roland mcgrath and ulrich drepper.\n\n\n  \n \n\n\n i also installed kmod-zfs instead of zfs-dkms\\_2.0.0-0\\_arm64.deb package. \n \n\n\n when i tried to install zfs-dkms i got errors: \n \n\n\n  \n \n\n\nsetting up libnvpair1 (2.0.0-0) ...\nsetting up libuutil1 (2.0.0-0) ...\nsetting up libzfs2-devel (2.0.0-0) ...\nsetting up libzfs2 (2.0.0-0) ...\nsetting up libzpool2 (2.0.0-0) ...\nsetting up python3-pyzfs (2.0.0-0) ...\nsetting up zfs-dkms (2.0.0-0) ...\nwarning: /usr/lib/dkms/common.postinst does not exist.\nerror: dkms version is too old and zfs was not\nbuilt with legacy dkms support.\nyou must either rebuild zfs with legacy postinst\nsupport or upgrade dkms to a more current version.\ndpkg: error processing package zfs-dkms (--install):\ninstalled zfs-dkms package post-installation script subprocess returned error exit status 1\nsetting up zfs-dracut (2.0.0-0) ...\nsetting up zfs-initramfs (2.0.0-0) ...\nsetting up zfs-test (2.0.0-0) ...\nsetting up zfs (2.0.0-0) ...\nprocessing triggers for libc-bin (2.28-10) ...\nprocessing triggers for systemd (241-7~deb10u4) ...\nprocessing triggers for man-db (2.8.5-2) ...\nerrors were encountered while processing:\nzfs-dkms\n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "@grek it's a bit of a dilemma. you must use compatible libs to build the zfs tools, in your case you must build them on debian buster, but the module build will fail due to old gcc. you can work around this by using the kernel modules (kmod) from a build using newer gcc (by building on e.g. ubuntu focal, debian bullseye/sid, etc) and building the tools separately on buster. to achieve this we must force the build on buster to either skip building the kmod or to trick it into building it \"successfully\". after a bunch of head-scratching, i found the latter to be easier.\n \n\n\n  \n \n\n\n here's a set of steps that should work for building the tools (sans functioning kmod) (based largely on the steps posted earlier by jbergler):\n \n\n\nmkdir /tmp/zfs-build; cd $\\_\napt-get download linux-headers-current-rockchip64\ndocker pull debian:buster-slim\ndocker run -it --rm -v $(pwd):/build debian:buster-slim\n\n# inside docker.\ncd /build\n\napt-get update\napt-get install --yes alien autoconf automake bison build-essential dkms fakeroot flex gawk libaio-dev libattr1-dev libblkid-dev libelf-dev libffi-dev libssl-dev libtool libudev-dev python3 python3-cffi python3-dev python3-setuptools uuid-dev zlib1g-dev\n\ndpkg -i linux-headers-*.deb\n# disable all stackprotect options incompatible with gcc, this means the\n# built kernel module (kmod) will be non-functional. that's ok since \n# we're only interested in building the tools.\nsed -i -e 's/\\(.*stackprotect.*=\\)y/\\1n/' /usr/src/linux-headers-$(uname -r)/.config\n# ignore the error(s) from the following:\n(cd /usr/src/linux-headers-$(uname -r); make prepare)\n\napt-get install --no-install-recommends --yes git\ngit clone https://github.com/openzfs/zfs.git\n\ncd zfs\ngit clean -xdf\ngit checkout zfs-2.0.0-rc6\nsh autogen.sh\n./configure --with-linux=/usr/src/linux-headers-$(uname -r)\nmake -s -j$(nproc)\nmake deb\n\nmkdir ../zfs-2.0.0-rc6-buster\nmv *.deb ../zfs-2.0.0-rc6-buster\n\n\n then go ahead and install:\n \n\n\n# cleanup packages (if installed).\nmodprobe -r zfs zunicode zzstd zlua zcommon znvpair zavl icp spl\napt remove --yes zfsutils-linux zfs-zed zfs-initramfs\napt autoremove --yes\n\n# install new packages.\ndpkg -i /path/to/working/kmod-zfs-$(uname -r)*.deb\ndpkg -i /tmp/zfs-build/zfs-2.0.0-rc6-buster/{libnvpair1,libuutil1,libzfs2,libzpool2,python3-pyzfs,zfs}\\_*.deb\n\n\n and that should do it, until the next kernel update.\n \n\n\n  \n \n\n\n ps. i only tested zfs-2.0.0-rc5 when setting up my helios64 the first time, currently using zfs-0.8.5 so can't speak for the reliability.\n \n", "name": "", "is_accepted": false }, { "text": "@salamandar yes, i've been using 5.8/5.9 since the get-go. you probably need the `linux-headers-legacy-rk3399` package (modify the apt-get download stage). good job automating the process .\n \n", "name": "", "is_accepted": false }, { "text": "@shadowdance crap, i didn't even see those headers were available ! i already implemented the modification of the headers version ! let's roll back.\n \n\n\n  \n \n\n\n thanks, feel free to open issues if needed.\n \n", "name": "", "is_accepted": false }, { "text": "any idea how to compile zfs in the tree? i was playing a bit with that idea. if we can do it, we could perhaps ship zfs with kernel? (or rather not? ) \n \n this way we cover 3rd party drivers: \n https://github.com/armbian/build/blob/master/lib/compilation-prepare.sh\n \n", "name": "", "is_accepted": false }, { "text": "@shadowdance i've got an error when i was trying to build the 2.0.0 release using your instructions, getting the following error on \"make deb\" : \n  \n \n\n\nkmodtool error: don't know how to handle 5.9.11 -- /lib/modules/5.9.11/build/makefile not found\n\n\n \n i've tried to change the kernel version to \"5.9.11-rockchip64\" directly on the makefile but the build it fails anyways. \n the right path should be /lib/modules/5.9.11-rockchip64/build/makefile\n \n", "name": "", "is_accepted": false }, { "text": "@manman hmm, the configure step should’ve taken care of that. you could try to specify the correct path manually via:\n \n\n\n\n\n if that still doesn’t help, see if you have any other linux-headers installed and remove them all.\n \n", "name": "", "is_accepted": false }, { "text": "what do you mean by \"in the tree\" ? do you mean in /usr/src/zfs where the zfs-dkms module installs the sources ?\n \n\n\n  \n \n\n\n right now the build is done inside the source directory of zfs, and i'm looking into building it out-of-source (i'm gonna read the dkms scripts, i think they build out-of-source).\n \n", "name": "", "is_accepted": false }, { "text": "that we compile it together with kernel. like we do for other drivers - wireguard (for older kernels) and selection of wireless drivers.\n \n", "name": "", "is_accepted": false } ]

[ { "text": "this is the problem and the solution: \n  \n \n\n\n\n  \n \n", "name": "", "is_accepted": true }, { "text": "thank you.  the easiest for me would be to manipulate the sd card in a computer and then hope that it will not enter a bootloop, again.\n \n\n\n can you tell me which files i need to revert?\n \n\n\n the manipulated files from the update in the /boot directory are\n \n\n\n uinitrd-5.10.43-sunxi (with uinitrd sym-linked to it)\n \n\n\n initrd.img-5.10.43-sunxi\n \n\n\n  \n \n\n\n can i download the files for the a20 processor somewhere without having to burn another sd card?\n \n", "name": "", "is_accepted": false }, { "text": "none of them.. read the topic mentioned above again for suggestions to solve.\n \n", "name": "", "is_accepted": false }, { "text": "i really appreciate your help, but i am not getting it (or at least i am not sure what is happening, the solution is really not that 'easy' to go through for me).\n \n\n\n  \n \n\n\n the boot.scr file hast a datestamp of may 7 which likely was the initial installation when i etched the sd card (so ok, it's 8 weeks ;)). \n \n\n\n that apparently did not change, yesterday (as are boot.cmd, boot.bmp)\n \n\n\n  \n \n\n\n does this mean the old boot.bmp does not \"fit\" to the newly created initrd.img.... file (which has a datestamp of july 30, i.e. yesterday)\n \n\n\n would locking this to \"bootbranch='tag:v2020.10'\" as suggested in the patch of the solution remedy it and avoid this in the future?\n \n\n\n  \n \n\n\n so a possible solution would be to adopt the boot.* files.  i found / am finding this confusing because they did not change.\n \n\n\n  \n \n\n\n best\n \n\n\n matthias\n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "in short term, yes. this is the workaround for the issue. however somewhen we need to move forward again. most likely when this issue is solved upstream.\n \n\n\n  \n \n\n\n you can try to build a recent u-boot package from scratch using our build tools and then follow this guide:\n \n\n\n  https://docs.armbian.com/user-guide\\_recovery/\n \n", "name": "", "is_accepted": false }, { "text": "thanks again.\n \n\n\n sorry if i am stuck again.\n \n\n\n in addition, the environment i had on my virtualbox crashed completely and i set a new one, based on x64 debian.\n \n\n\n compile.sh as suggested here:https://docs.armbian.com/developer-guide\\_build-preparation,\n \n\n\n  \n \n\n\n i get an error \n \n\nrunning this tool on non x86-x64 build host is not supported \n\n\n  \n \n\n\n but i do have the an i386 processor (mac).   dpkg --print-architechture gives 'i386'\n \n\n\n  \n \n\n\n the code lines in general.sh 1013ff however suggest that only arm64 and amd64 are accepted.  can i build it on a i386 processor with virtualization, at all?\n \n", "name": "", "is_accepted": false }, { "text": "ok, i am giving up and will reinstall a new card with a working image.   it will be faster and only take half a day to get everything re-installed....\n \n\n\n i would appreciate if someone could give me any hints on what i need to do that the next \"apt upgrade\" is not bricking the device, again.\n \n\n\n  \n \n\n\n do i need to choose a different bootloader with armbian-config, before?\n \n\n\n  \n \n\n\n best\n \n\n\n matthias\n \n", "name": "", "is_accepted": false }, { "text": "no.\n \n\n\n  \n \n\n\n\n\n use\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 to freeze firmware and wait until 21.08 is released. expected by end of august.\n \n", "name": "", "is_accepted": false }, { "text": "thanks, everything back up and running.  the firmware freeze held back the correct updates and a run of apt update/upgrade on the new installation worked well without breaking  the boot process\n \n\n\n matthias\n \n", "name": "", "is_accepted": false } ]

[ { "text": "bananapi m1 with armbian 21.02: how to enable tv output through the composite connector\n \n\n\n  \n \n\n\n a banana pi m1 set up as in the previous post, when connected to a display via \n the composite connector, will display only early boot messages.\n \n\n\n  \n \n\n\n when the linux kernel is started, the display at the composite connector will \n go dark, and video will only be output through hdmi.\n \n\n\n  \n \n\n\n to prevent this, blacklist the hdmi output module:\n \n\n\n  \n \n\n\necho blacklist sun4i\\_drm\\_hdmi | sudo tee /etc/modprobe.d/composite.conf\n\n\n \n however, in the current kernel, the hdmi output not compiled as a module, and therefore cannot be effectively blocked in this way.\n \n\n\n  \n \n\n\n but it was compiled as a module in armbian kernel version 5.8.6. use\n \n\n\nsudo armbian-config\n\n\n to install this kernel version (under system -> other) and reboot. the screen (console) will now show on the screen attached to the composite output.\n \n\n\n  \n \n\n\n security-wise, changing to an older kernel is probably a bad move. for devices that need to access the internet, it may be better to recompile the current kernel instead after configuring that the above driver is compiled as a module. as this is not a concern for me, i have not tried this.\n \n\n\n  \n \n", "name": "", "is_accepted": true }, { "text": "bananapi m1 with armbian 21.02: how to enable dallas one-wire temperature sensor\n \n\n\n  \n \n\n\n the following step-by-step guide may be too detailed:\n \n\n\n  \n \n\n\n 1) write the armbian image for banana pi to sd card.\n \n\n\n  \n \n\n\nxzcat <~/downloads/armbian\\_21.02.3\\_bananapi\\_buster\\_current\\_5.10.21.img.xz | sudo dd of=/dev/mmcblk0 bs=1m\n\n\n  \n \n\n\n 2) set host name of the banana pi\n \n\n\n  \n \n\n\n \n pop out sd card out of the laptop / pc and push back in. \n # replace occurrences of bananapi with desired hostname.\n \n\n\nsudo sed -i s/bananapi/test-w1/ /media/*/*f*/etc/host{s,name}\n\n\n \n # umount sdcard, put in banana pi, connect banana pi to network, power on\n \n\n\n  \n \n\n\n 3) ssh to banana pi and configure 1wire\n \n\n\nssh root@test-w1\n# follow instructions to change password and create user. reconnect as user.\nsudo armbian-config\n# navigate: system -> hardware. select w1-gpio. save. back. reboot.\n# reconnect after reboot as user.\ndmesg | grep wire\n[ 8.560693] driver for 1-wire dallas network protocol.\n[ 8.581436] gpio-271 (onewire@0): enforced open drain please flag it properly in dt/acpi dsdt/board file\n[ 60.628063] w1\\_master\\_driver w1\\_bus\\_master1: attaching one wire slave 00.800000000000 crc 8c\n\ncat /sys/kernel/debug/pinctrl/*/pinmux-pins\npinmux settings per pin\nformat: pin (name): ...\n...\npin 259 (pi3): (mux unclaimed) (gpio unclaimed)\n...\npin 271 (pi15): onewire@0 1c20800.pinctrl:271 function gpio\\_in group pi15\n...\n\n\n gpio 271 does not seem to be available on the gpio header of the bananapi.\n \n\n\n  \n \n\n\n for linux, gpio seem to either have a (high) number, or a name like ph8 or pi15.\n \n\n\n i have only found one source that shows the location of these type of pin names on the \n banana pi's gpio header: the table at the bottom of this page: http://www.elektronik-kompendium.de/sites/raspberry-pi/1907101.htm\n \n\n\n if gives this mapping for the banana pi m1 gpio header to these names:\n \n\n\n\n3v3 1 2 5v\npb21 3 4 5v\npb20 5 6 gnd\npi03 7 8 ph00\ngnd 9 10 ph01\npi19 11 12 ph02\npi18 13 14 gnd\npi17 15 16 ph20\n3v3 17 18 ph21\npi12 19 20 gnd\npi13 21 22 pi16\npi11 23 24 pi10\ngnd 25 26 pi14\n\n\n\n this shows that  pi3 (which is the same as pi03) is available at pin 7.\n \n\n\n  \n \n\n\n in order to use this pin for one-wire, edit file /boot/armbianenv.txt \n on the banana pi. add a line:\n \n\n\n  \n \n\n\nparam\\_w1\\_pin=pi3\n\n\n\n  \n \n\n\n save and reboot. connect a temperature sensor to 3v3, gnd, pin 7, and a \n suitable resistor.  then the temperature can be read by\n \n\n\ncat /sys/bus/w1/devices/w1\\_bus\\_master*/28-*/temperature\n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "i think this opens new problem, but i can't recall what is the reason. it was as a module, but we have to change it https://github.com/armbian/build/commit/4a57ba0189d831953bad6ea56b65ba487d0149b4#diff-6207111e1940f2332b7a21e4459e1bccd91f7c4c66003ce20bf51a9b0ac71509\n \n", "name": "", "is_accepted": false } ]

[ { "text": "are you sure you need to containerize the wireguard installation?  because wireguard should basically \"just work\" in recent kernels...\n \n", "name": "", "is_accepted": true }, { "text": "correct.  no dkms modules needed.  no container needed.\n \n\n\n  \n \n\n\n  armbian has shipped with native wireguard support for probably 2 years.   wg and wg-quick are already installed.\n \n", "name": "", "is_accepted": false }, { "text": "thank you for the quick replies!\n \n\n\n i apologize but i have a limit of 1 post post per day  and i couldn't answer before...(i don't know if that's normal or if i should do anything to remove it).\n \n\n\n  \n \n\n\n anyway, i wanted to containerize wireguard just because i have omv installed and i'm running already different services in docker (nginx, pihole, qbittorrent, ...).\n \n\n\n i honestly didn't even think to use it directly from armbian (i'm so noob).\n \n\n\n  \n \n\n\n yesterday i sshed in the odroid and configured wireguard. like you said, nothing needed to be installed: wg and wg-quick are already available. i tested it with my phone and the link is working.\n \n\n\n  \n \n\n\n thank you very much!!!\n \n", "name": "", "is_accepted": false }, { "text": "being a noob is not a problem, mate.  only nasty / entitled attitudes are.  and expecting people to do things for you.  neither of which i see here (in fact you seem grateful, which is proper imo).  as long as you are making some sort of effort to learn, more experienced people will (generally) be happy to help (see also \"how to ask questions\" link in my sig for more on this).\n \n\n\n  \n \n\n\n some more strategic level things are also not immediately apparent to the newcomer.  but we were all there at one point.  just keep trying to learn as much as you can.  lurking the forums (and/or irc) is really good for that, studying ancient scrolls of wisdom (man pages, documentation, wikis, etc.) you will learn a lot.\n \n\n\n  \n \n\n\n wireguard is pretty low level kernel networking stuff.  i don't know as much as lanefu about containerization, but the sense i get is that wireguard will need to (or maybe because of permissions it is easier to) configure directly on the host, because of those low level kernel networking permissions.  and i feel like it's harder to containerize that.  i could be wrong of course.\n \n\n\n  \n \n\n\n anyway, good luck with it, and have fun!  \n \n", "name": "", "is_accepted": false } ]

[ { "text": "i already explained in my 1st reply. copy https://github.com/armbian/build/blob/master/packages/bsp/common/usr/lib/armbian/armbian-firstlogin#l297-l304 exchange $realusername with your username and paste.\n \n", "name": "", "is_accepted": true }, { "text": "moved to common issues / peer to peer technical support\n \n", "name": "", "is_accepted": false }, { "text": "need to check armbian-config, but you can try  this in the mean time: \n https://github.com/armbian/build/blob/master/packages/bsp/common/usr/lib/armbian/armbian-firstlogin#l297-l304\n \n\n\n  \n \n\n\n\n\n  \n \n\n\n this is now / since some time / the defaults.\n \n", "name": "", "is_accepted": false }, { "text": "thanks @igor\n \n\n\n hmm.. file (22-armbian-autologin.conf) looks not present now\n \n\n\n  \n \n\n\nchristos@orangepipc:/etc/lightdm/lightdm.conf.d$ ls -l\ntotal 4\n-rw-r--r-- 1 root root 110 jan 15 18:39 11-armbian.conf\nchristos@orangepipc:/etc/lightdm/lightdm.conf.d$\n\n\n  \n \n\n\n i added the file manually with the indicated contents and now it does work and autologin is ok.\n \n\n\n  \n \n\n\n did though a new install and seen that the specific autologin config file is there present..\n \n\n\n i'm gonna use another microsd just in case, it a first to have such issue (using sandisk a1 16gb) but who knows.\n \n\n\n  \n \n\n\n thanks\n \n\n\n christos\n \n\n\n  \n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "that is expected. later on a timer starts which delete this file: \n https://github.com/armbian/build/blob/master/packages/bsp/common/usr/lib/armbian/armbian-firstlogin#l318-l319\n \n\n\n  \n \n\n\n we figured out that it's best to provide autologin only at first run. if you want to have it always, you have to enable it manually by creating such file or that used to work fine via armbian-config, but it needs to be checked and fixed if it doesn't work anymore.\n \n", "name": "", "is_accepted": false }, { "text": "ohh.. ok @igor,\n \n\n\n  \n \n\n\n so its not a gremlin :-))\n \n\n\n it got really weird but now its explained, thanks.\n \n\n\n  \n \n\n\n so, what is the appropriate procedure if someone wants to have the autologin always enabled?\n \n\n\n you mentioned armbian-config but i could not find any relevant option there to use, could it be removed at some time or should i look better?\n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "thanks @igor ,\n \n\n\n  \n \n\n\n i thought based on what you said  that there is some other method with armbian-config, ok no worries.\n \n\n\n  \n \n\n\n i got it now, it seems that the remove auto login service is a one-off, so it runs once after 10mins and removes the auto login and it never runs again so if we put again back the deleted file everything will be ok.\n \n\n\n  \n \n\n\n thanks again\n \n\n\n christos\n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "imho earlier, in all armbian builds, autologin was enabled by default and all users are used to this behavior, so it is advisable to keep this in new versions (i.e. make autologin enabled by default and disable autologin yourself, through the armbian-config setting). for many users, this will preserve the usual behavior and at the same time allow you to disable autologin (if necessary).\n \n", "name": "", "is_accepted": false } ]

[ { "text": "there is https://github.com/vsergeev/python-periphery which is somehow related to https://github.com/sgjava/java-periphery, the developer of the latter (@sgjava) is regular around here and i know at least his software is actively developed.\n \n", "name": "", "is_accepted": true }, { "text": "thanks, that looks very promising. now i just need something to read the adc (none of the above seems to handle adc?) pin...\n \n", "name": "", "is_accepted": false } ]

[ { "text": "try perhaps this: \n \n\n\napt install slick-greeter\n\n\n + reboot.\n \n", "name": "", "is_accepted": true }, { "text": "hi igor, thanks for the heads up, this fixed it.\n \n\n\n  \n \n\n\n just out of curiosity, as lightdm worked until the upgrade. has the slick-greeter been added recently to armbian? i did not remove it intentionally.\n \n", "name": "", "is_accepted": false }, { "text": "i faced the same issue on rock pi 4c and installing slick-greeter also solved the problem.\n \n", "name": "", "is_accepted": false }, { "text": "@igor i also got lightdm-problems while installing my ordroid c2 from scratch \n (2 times once with current and once with edge)\n \n\n\n after trying different soutions from the net it didnt worked....but with a simple \"enable desktop\" from armbian-config -> system-settings and the desktop did start again without any problems \n \n", "name": "", "is_accepted": false }, { "text": "after lightdm fails on my pinebook pro, i simply logon to the terminal and\n \n\n\n  \n \n\n\nstartx\n\n\n\n\n  \n \n\n\n but i will try slick-greeter.\n \n\n\n  \n \n\n\n i could not find the \"enable desktop\" from armbian-config -> system-settings, which i assume is an applications menu hierarchy.\n \n\n\n  \n \n\n\n thanks!\n \n", "name": "", "is_accepted": false }, { "text": "thanks igor, guidol. installing slick-greeter worked for me too.\n \n", "name": "", "is_accepted": false }, { "text": "this happened to me as well on a pine64 yesterday. installing slick-greeter solved it as well. thanks.\n \n", "name": "", "is_accepted": false } ]

[ { "text": "i've configured and connected to a wifi network just fine, but i want to change the config non-interactively.\n \n\n\n  \n \n\n\n the config isn't in /etc/wpa\\_supplicant/wpa\\_supplicant.conf or anywhere else i'd expect, and https://github.com/armbian/config/ only mentions hostapd.\n \n\n\n  \n \n\n\n where's the config stored?\n \n\n\n  \n \n\n\n  \n \n\n\n edit: /etc/networkmanager/system-connections/[my ssid]\n \n", "name": "", "is_accepted": true }, { "text": "from what i read in the source i assume the whole wifi stuff is handled via hostapd. did you take a look at its config files?\n \n", "name": "", "is_accepted": false }, { "text": "yes, and no, hostapd only handles access points, not connecting to wifi as a client.\n \n", "name": "", "is_accepted": false } ]

[ { "text": "sorry i made a mistake. although i can't find the device on lsusb.\n \n\n\n but i actually tried communicating with it and it works,\n \n", "name": "", "is_accepted": true }, { "text": "i just found out that, it works with arduino nano. but not arduino micro.... weird.\n \n", "name": "", "is_accepted": false }, { "text": "hi after much detail testing, still doesn't work. it works with arduino nano but just don't work with micro no matter if its with or without usb hub.\n \n\n\n  \n \n\n\n i found the problem lies with the cable. i am able to communicate using the arduino provided cable. but not with other cables.\n \n", "name": "", "is_accepted": false } ]

[ { "text": "you could test the options from this page:\n \n\n\n https://unix.stackexchange.com/questions/387502/disable-bluetooth-at-boot\n \n\n\n  \n \n\n\n - via /etc/bluetooth/main.conf \n            autoenable=false \n - rfkill \n            sudo rfkill block bluetooth \n - lsmod / blacklist the modules\n \n", "name": "", "is_accepted": true }, { "text": "thanks! lsmod / blacklist the modules resolves the issue.\n \n", "name": "", "is_accepted": false } ]

[ { "text": "https://www.armbian.com/bananapi-m3/\n \n\n\n  \n \n\n\n but there is no desktop variant for this hardware so you need to:\n \n\n\n - download cli and enable xfce desktop via armbian-config -> system -> enable desktop\n \n\n\n - build desktop image with https://github.com/armbian\n \n\n\n - only armbian. we don't provide debian ...\n \n\n\n  \n \n\n\n and this board is not supported. which means we don't know how good or bad it works ... i know it boots, but that's about it.\n \n", "name": "", "is_accepted": true } ]

[ { "text": "i'm not an expert in this area whatsoever, but this problem looks like an upstream kernel issue, and perhaps is related to this fallback deadlock fix?  https://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6.git/commit/?id=a2715fbdc6fc387e85211df917a4778761ec693d\n \n\n\n  \n \n\n\n the posted fix patch is only applicable to kernel v5.10; just in case you want to give it a try, i've uploaded a tot test build of v5.10-rc3 with this kernel patch applied:  https://drive.google.com/file/d/1eg\\_cn3beysrfz3vrp9mc0fxjjpreczcw/view.  again, i'm not sure if this will fix the problem, but there are a number of changes in cryptodev here compared to kernel v5.9, so it might be worth a try.\n \n", "name": "", "is_accepted": true }, { "text": "my first guess will be dvfs which is causing us troubles for some time and has been reworked a few times. not sure if we are stable with it yet and certainly this is a guess with bleeding edge 5.9.y ... which was not tested much. a possible workaround is to set fixed cpu speed (you can use armbian-config) or changing its governor. anything else would require much more investigation.\n \n\n\n  \n \n\n\n is the same happening with official builds from the download section?\n \n", "name": "", "is_accepted": false }, { "text": "i tested my opi r1 these days with kernel 5.10.0-rc2 and got problems with eth0 like on some versions in the past.\n \n\n\n  \n \n\n\n you could see this issue in dmesg showing the eth0-device-link going down/up serveral times \n (eth0 ist the ethernet-port near the serial-ttl-port, the other enx-ethernet is connectec via usb)\n \n\n\n  \n \n\n\n my enx-ethernet device is working here fine, but now my eth0 device has stopped working completly \n i use /etc/network/interfaces for setting the ip. armbian does set the ip but eth0 cant use the net \n \n  \n \n\n\n \\_\\_\\_ \\_\\_\\_\\_ \\_ \\_\\_\\_\\_ \\_\n / \\_ \\| \\_ \\(\\_) | \\_ \\/ |\n| | | | |\\_) | | | |\\_) | |\n| |\\_| | \\_\\_/| | | \\_ <| |\n \\\\_\\_\\_/|\\_| |\\_| |\\_| \\\\_\\\\_|\n\nwelcome to armbian 20.11.0-trunk buster with linux 5.10.0-rc2-sunxi\n\nno end-user support: built from trunk\n\npackage bsp-kernel[20.11.0-trunk] u-boot[20.11.0-trunk] dtb [20.11.0-trunk]\nfirmware [20.11.0-trunk] config[20.11.0-trunk] branch[dev]\n\nroot@opi-r1-101(192.168.6.101):~# ifconfig\nenxc0742bffe8ff: flags=4163<up,broadcast,running,multicast> mtu 1500\n inet 192.168.6.101 netmask 255.255.255.0 broadcast 192.168.6.255\n ether c0:74:2b:ff:e8:ff txqueuelen 1000 (ethernet)\n rx packets 247 bytes 17017 (16.6 kib)\n rx errors 0 dropped 0 overruns 0 frame 0\n tx packets 90 bytes 9447 (9.2 kib)\n tx errors 0 dropped 0 overruns 0 carrier 0 collisions 0\n\n\n\n  \n \n\n\n system diagnosis information has been uploaded to http://ix.io/2ddi \n \n", "name": "", "is_accepted": false }, { "text": "also got the problem with the official download-image armbian\\_20.08.1\\_orangepi-r1\\_buster\\_current\\_5.8.5.img\n \n\n\n  \n \n\n\n eth0 orange/green led does lit , orange stays, green blink for some seconds, both goes off: \n like last year: \n \n\n\n\n[ 33.780717] vcc3v0: disabling\n[ 33.780731] vcc5v0: disabling\n[ 33.877210] dwmac-sun8i 1c30000.ethernet eth0: link is up - 100mbps/full - flow control rx/tx\n[ 34.901031] dwmac-sun8i 1c30000.ethernet eth0: link is down\n[ 37.973216] dwmac-sun8i 1c30000.ethernet eth0: link is up - 100mbps/full - flow control rx/tx\n[ 38.996979] dwmac-sun8i 1c30000.ethernet eth0: link is down\n[ 40.021229] dwmac-sun8i 1c30000.ethernet eth0: link is up - 100mbps/full - flow control rx/tx\n[ 41.044983] dwmac-sun8i 1c30000.ethernet eth0: link is down\n[ 42.069337] dwmac-sun8i 1c30000.ethernet eth0: link is up - 100mbps/full - flow control rx/tx\n[ 43.093067] dwmac-sun8i 1c30000.ethernet eth0: link is down\n\n\n\n or here: \n https://serverfault.com/questions/585442/eth0-nic-link-is-down-repeating-message-in-kernel-log\n \n\n\n  \n \n\n\n  \n \n\n\n usb/enx-ether is ok:\n \n\n\n[ 432.833832] ipv6: addrconf(netdev\\_change): enxc0742bffe8ff: link becomes ready\n[ 432.834587] r8152 3-1:1.0 enxc0742bffe8ff: carrier on\n\n\n\n  \n \n\n\n power is enough/good from a original rpi-powersupply (5.1v) \n  \n \n", "name": "", "is_accepted": false }, { "text": "i think that more research is needed here, as the problem is non-obvious.  unfortunately i can't reproduce any issues on my orangepi r1 with either 5.8.5 or 5.9.5.  @igor this doesn't appear to be dvfs related; the dts are correct and the board is correctly maxed at 1ghz (but it can support 1.3ghz via the overclocking overlay).  i can successfully run all of \"openssl speed -multi 4\", throttling is fine, etc.\n \n\n\n  \n \n\n\n using iperf3 testing, i can't reproduce any issues on my board with the ethernet interfaces either; both eth0 and enxc0742bfffa39 work properly for me...  i'm seeing 94mbps on both eth0 and enxc0742bfffa39 (for testing, i purged network-manager and statically set the ips in /etc/network/interfaces.d/) - here is the iperf3 server output for the two runs from the r1:\n \n\n\n  \n \n\n\n\n\n  \n \n\n\n of course this is not to say that there isn't a problem, but with this simple/quick iperf3 testing i can't reproduce anything on my board.  @ford\\_prefect i think it would be interesting to see what your serial console shows.  @guidol would it be possible to get serial console output for your situation as well?\n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "which serial ouput do you need/mean? \n from the boot-process while using eth0?\n \n", "name": "", "is_accepted": false }, { "text": "hi,\n \n\n\n  \n \n\n\n first of all, this all happens only when i use ipsec it seems - if i transfer large amounts of data directly, the enpxxx interface (usb)  and the  internal attached eth0 everything works fine.\n \n\n\n  \n \n\n\n i also set the gouvernor to \"performance\" and highest cpu frequency.\n \n\n\n  \n \n\n\n i attached the serial port and found out the following:\n \n\n\n  \n \n\n\n the raspi does not freeze, the usb enpxxx interface seizes operation nearly instantaniously....\n \n\n\n  \n \n\n\n via serial port i  the device itself worked just fine, but the ethernet port crashed....\n \n\n\n  \n \n\n\n is there any workaround?  i mean.... using a 2 port sbc and attaching an  additional usb ethernet nic  is not really my goal here....;-)\n \n\n\n  \n \n\n\n  \n \n\n\n 19.234179] sun8i-ce 1c15000.crypto: fallback for ecb-aes-sun8i-ce is ecb-aes-neonbs\n[ 19.853360] ipv6: addrconf(netdev\\_change): enxc0742bffecdb: link becomes ready\n[ 19.862969] r8152 3-1:1.0 enxc0742bffecdb: carrier on\n[ 33.779552] vcc3v0: disabling\n[ 33.779566] vcc5v0: disabling\n[ 84.442046] ipsec xfrm device driver\n[ 93.795697] sun8i-ce 1c15000.crypto: fallback for cbc-des3-sun8i-ce is cbc(des3\\_ede-generic)\n[ 93.817912] sun8i-ce 1c15000.crypto: fallback for cbc-aes-sun8i-ce is cbc-aes-neonbs\n[ 93.818110] sun8i-ce 1c15000.crypto: fallback for cbc-aes-sun8i-ce is cbc-aes-neonbs\n[ 93.818189] sun8i-ce 1c15000.crypto: fallback for cbc-aes-sun8i-ce is cbc-aes-neonbs\n[ 93.818269] sun8i-ce 1c15000.crypto: fallback for ecb-aes-sun8i-ce is ecb-aes-neonbs\n[ 93.818333] sun8i-ce 1c15000.crypto: fallback for ecb-aes-sun8i-ce is ecb-aes-neonbs\n[ 93.818397] sun8i-ce 1c15000.crypto: fallback for ecb-aes-sun8i-ce is ecb-aes-neonbs\n[ 93.947310] sun8i-ce 1c15000.crypto: fallback for cbc-des3-sun8i-ce is cbc(des3\\_ede-generic)\n[ 93.947424] sun8i-ce 1c15000.crypto: fallback for cbc-aes-sun8i-ce is cbc-aes-neonbs\n[ 93.947493] sun8i-ce 1c15000.crypto: fallback for cbc-aes-sun8i-ce is cbc-aes-neonbs\n[ 93.947559] sun8i-ce 1c15000.crypto: fallback for cbc-aes-sun8i-ce is cbc-aes-neonbs\n[ 93.947624] sun8i-ce 1c15000.crypto: fallback for ecb-aes-sun8i-ce is ecb-aes-neonbs\n[ 93.947686] sun8i-ce 1c15000.crypto: fallback for ecb-aes-sun8i-ce is ecb-aes-neonbs\n[ 93.947780] sun8i-ce 1c15000.crypto: fallback for ecb-aes-sun8i-ce is ecb-aes-neonbs\n[ 138.039764] sun8i-ce 1c15000.crypto: fallback for cbc-des3-sun8i-ce is cbc(des3\\_ede-generic)\n[ 138.039876] sun8i-ce 1c15000.crypto: fallback for cbc-aes-sun8i-ce is cbc-aes-neonbs\n[ 138.039993] sun8i-ce 1c15000.crypto: fallback for cbc-aes-sun8i-ce is cbc-aes-neonbs\n[ 138.040070] sun8i-ce 1c15000.crypto: fallback for cbc-aes-sun8i-ce is cbc-aes-neonbs\n[ 138.040137] sun8i-ce 1c15000.crypto: fallback for ecb-aes-sun8i-ce is ecb-aes-neonbs\n[ 138.040200] sun8i-ce 1c15000.crypto: fallback for ecb-aes-sun8i-ce is ecb-aes-neonbs\n[ 138.040260] sun8i-ce 1c15000.crypto: fallback for ecb-aes-sun8i-ce is ecb-aes-neonbs\n[ 138.450617] sun8i-ce 1c15000.crypto: fallback for cbc-aes-sun8i-ce is cbc-aes-neonbs\n[ 138.451559] sun8i-ce 1c15000.crypto: fallback for cbc-aes-sun8i-ce is cbc-aes-neonbs\n[ 141.806447] nohz: local\\_softirq\\_pending 08\n[ 142.498226] sun8i-ce 1c15000.crypto: fallback for cbc-aes-sun8i-ce is cbc-aes-neonbs\n[ 142.498636] sun8i-ce 1c15000.crypto: fallback for cbc-aes-sun8i-ce is cbc-aes-neonbs\n[ 142.660627] sun8i-ce 1c15000.crypto: fallback for cbc-aes-sun8i-ce is cbc-aes-neonbs\n[ 142.660959] sun8i-ce 1c15000.crypto: fallback for cbc-aes-sun8i-ce is cbc-aes-neonbs\n[ 142.831695] sun8i-ce 1c15000.crypto: fallback for cbc-aes-sun8i-ce is cbc-aes-neonbs\n[ 142.832064] sun8i-ce 1c15000.crypto: fallback for cbc-aes-sun8i-ce is cbc-aes-neonbs\n[ 143.809585] nohz: local\\_softirq\\_pending 08\n[ 144.810432] nohz: local\\_softirq\\_pending 08\n[ 145.813047] nohz: local\\_softirq\\_pending 08\n[ 146.814295] nohz: local\\_softirq\\_pending 08\n[ 147.815793] nohz: local\\_softirq\\_pending 08\n[ 148.817676] nohz: local\\_softirq\\_pending 08\n[ 149.818676] nohz: local\\_softirq\\_pending 08\n[ 150.820421] nohz: local\\_softirq\\_pending 08\n[ 151.821924] nohz: local\\_softirq\\_pending 08\n[...]\n[ 143.809585] nohz: local\\_softirq\\_pending 08\n[ 144.810432] nohz: local\\_softirq\\_pending 08\n[ 145.813047] nohz: local\\_softirq\\_pending 08\n[ 146.814295] nohz: local\\_softirq\\_pending 08\n[ 147.815793] nohz: local\\_softirq\\_pending 08\n[ 148.817676] nohz: local\\_softirq\\_pending 08\n[ 149.818676] nohz: local\\_softirq\\_pending 08\n[ 150.820421] nohz: local\\_softirq\\_pending 08\n[ 151.821924] nohz: local\\_softirq\\_pending 08\n[ 206.542170] rcu: info: rcu\\_sched self-detected stall on cpu\n[ 206.542193] rcu: 0-....: (5249 ticks this gp) idle=06a/1/0x40000004 softirq=6817/6817 fqs=2590 \n[ 206.542199] (t=5251 jiffies g=11233 q=139)\n[ 206.542205] nmi backtrace for cpu 0\n[ 206.542215] cpu: 0 pid: 309 comm: 1c15000.crypto- tainted: g c 5.9.1-sunxi #20.08.14\n[ 206.542219] hardware name: allwinner sun8i family\n[ 206.542250] [<c010d415>] (unwind\\_backtrace) from [<c01097a5>] (show\\_stack+0x11/0x14)\n[ 206.542265] [<c01097a5>] (show\\_stack) from [<c0574801>] (dump\\_stack+0x75/0x84)\n[ 206.542280] [<c0574801>] (dump\\_stack) from [<c0579d33>] (nmi\\_cpu\\_backtrace+0x6b/0x94)\n[ 206.542292] [<c0579d33>] (nmi\\_cpu\\_backtrace) from [<c0579e15>] (nmi\\_trigger\\_cpumask\\_backtrace+0xb9/0xe0)\n[ 206.542307] [<c0579e15>] (nmi\\_trigger\\_cpumask\\_backtrace) from [<c01706ab>] (rcu\\_dump\\_cpu\\_stacks+0xab/0xc8)\n[ 206.542320] [<c01706ab>] (rcu\\_dump\\_cpu\\_stacks) from [<c016fb23>] (rcu\\_sched\\_clock\\_irq+0x5e3/0x7ac)\n[ 206.542333] [<c016fb23>] (rcu\\_sched\\_clock\\_irq) from [<c0176641>] (update\\_process\\_times+0x29/0x70)\n[ 206.542345] [<c0176641>] (update\\_process\\_times) from [<c0184b57>] (tick\\_sched\\_timer+0x37/0x74)\n[ 206.542357] [<c0184b57>] (tick\\_sched\\_timer) from [<c0177089>] (\\_\\_hrtimer\\_run\\_queues+0xf1/0x250)\n[ 206.542368] [<c0177089>] (\\_\\_hrtimer\\_run\\_queues) from [<c0177ab1>] (hrtimer\\_interrupt+0xcd/0x1fc)\n[ 206.542383] [<c0177ab1>] (hrtimer\\_interrupt) from [<c07a9c7b>] (arch\\_timer\\_handler\\_phys+0x27/0x2c)\n[ 206.542398] [<c07a9c7b>] (arch\\_timer\\_handler\\_phys) from [<c0165acb>] (handle\\_percpu\\_devid\\_irq+0x53/0x1a0)\n[ 206.542414] [<c0165acb>] (handle\\_percpu\\_devid\\_irq) from [<c01611b5>] (generic\\_handle\\_irq+0x29/0x34)\n[ 206.542426] [<c01611b5>] (generic\\_handle\\_irq) from [<c0161671>] (\\_\\_handle\\_domain\\_irq+0x41/0x80)\n[ 206.542438] [<c0161671>] (\\_\\_handle\\_domain\\_irq) from [<c058628f>] (gic\\_handle\\_irq+0x3b/0x70)\n[ 206.542449] [<c058628f>] (gic\\_handle\\_irq) from [<c0100b65>] (\\_\\_irq\\_svc+0x65/0x94)\n[ 206.542455] exception stack(0xcc97fa20 to 0xcc97fa68)\n[ 206.542465] fa20: cb8d2660 000064b2 000064b1 000064b1 cdf2b0c0 cb8d2640 00000000 00000032\n[ 206.542474] fa40: 00000000 00000002 cb8d2660 00000000 00000004 cc97fa70 c08d6bd3 c0953d84\n[ 206.542478] fa60: 800d0133 ffffffff\n[ 206.542492] [<c0100b65>] (\\_\\_irq\\_svc) from [<c0953d84>] (\\_raw\\_spin\\_lock+0x28/0x38)\n[ 206.542507] [<c0953d84>] (\\_raw\\_spin\\_lock) from [<c08d6bd3>] (xfrm\\_input+0x137/0xce0)\n[ 206.542519] [<c08d6bd3>] (xfrm\\_input) from [<c08cb1cb>] (xfrm4\\_esp\\_rcv+0x27/0x38)\n[ 206.542532] [<c08cb1cb>] (xfrm4\\_esp\\_rcv) from [<c0877a0f>] (ip\\_protocol\\_deliver\\_rcu+0x27/0x214)\n[ 206.542544] [<c0877a0f>] (ip\\_protocol\\_deliver\\_rcu) from [<c0877c37>] (ip\\_local\\_deliver\\_finish+0x3b/0x40)\n[ 206.542554] [<c0877c37>] (ip\\_local\\_deliver\\_finish) from [<c0877cd5>] (ip\\_local\\_deliver+0x99/0xa4)\n[ 206.542563] [<c0877cd5>] (ip\\_local\\_deliver) from [<c0877d5f>] (ip\\_rcv+0x7f/0x84)\n[ 206.542577] [<c0877d5f>] (ip\\_rcv) from [<c0815295>] (\\_\\_netif\\_receive\\_skb\\_core+0x41d/0xa78)\n[ 206.542590] [<c0815295>] (\\_\\_netif\\_receive\\_skb\\_core) from [<c0815c6b>] (\\_\\_netif\\_receive\\_skb\\_list\\_core+0x97/0x130)\n[ 206.542600] [<c0815c6b>] (\\_\\_netif\\_receive\\_skb\\_list\\_core) from [<c0815e33>] (netif\\_receive\\_skb\\_list\\_internal+0x12f/0x1e0)\n[ 206.542609] [<c0815e33>] (netif\\_receive\\_skb\\_list\\_internal) from [<c0815fc9>] (gro\\_normal\\_list.part.0+0x15/0x24)\n[ 206.542618] [<c0815fc9>] (gro\\_normal\\_list.part.0) from [<c0816939>] (napi\\_complete\\_done+0x85/0x160)\n[ 206.542654] [<c0816939>] (napi\\_complete\\_done) from [<bf8d4dd5>] (r8152\\_poll+0x4a9/0x51c [r8152])\n[ 206.542686] [<bf8d4dd5>] (r8152\\_poll [r8152]) from [<c0816ad1>] (net\\_rx\\_action+0xbd/0x2c4)\n[ 206.542696] [<c0816ad1>] (net\\_rx\\_action) from [<c0101367>] (\\_\\_do\\_softirq+0xcf/0x260)\n[ 206.542707] [<c0101367>] (\\_\\_do\\_softirq) from [<c0120df5>] (irq\\_exit+0x79/0x98)\n[ 206.542717] [<c0120df5>] (irq\\_exit) from [<c0161675>] (\\_\\_handle\\_domain\\_irq+0x45/0x80)\n[ 206.542727] [<c0161675>] (\\_\\_handle\\_domain\\_irq) from [<c058628f>] (gic\\_handle\\_irq+0x3b/0x70)\n[ 206.542737] [<c058628f>] (gic\\_handle\\_irq) from [<c0100b65>] (\\_\\_irq\\_svc+0x65/0x94)\n[ 206.542741] exception stack(0xcc97fdf8 to 0xcc97fe40)\n[ 206.542747] fde0: 000000c3 00000000\n[ 206.542756] fe00: c9aca488 00000004 00000020 cb8d2640 00000000 00000004 00000002 00000002\n[ 206.542765] fe20: cb8d2660 00000000 cb9c7c50 cc97fe48 c08d9353 c085fab2 400d0033 ffffffff\n[ 206.542778] [<c0100b65>] (\\_\\_irq\\_svc) from [<c085fab2>] (netlink\\_has\\_listeners+0x4a/0x58)\n[ 206.542791] [<c085fab2>] (netlink\\_has\\_listeners) from [<c08d9353>] (xfrm\\_replay\\_advance+0x3b/0x68)\n[ 206.542804] [<c08d9353>] (xfrm\\_replay\\_advance) from [<c08d6e25>] (xfrm\\_input+0x389/0xce0)\n[ 206.542819] [<c08d6e25>] (xfrm\\_input) from [<bf86d075>] (crypto\\_finalize\\_request+0x31/0x7c [crypto\\_engine])\n[ 206.542838] [<bf86d075>] (crypto\\_finalize\\_request [crypto\\_engine]) from [<bf878afd>] (sun8i\\_ce\\_handle\\_cipher\\_request+0x295/0x5b4 [sun8i\\_ce])\n[ 206.542852] [<bf878afd>] (sun8i\\_ce\\_handle\\_cipher\\_request [sun8i\\_ce]) from [<bf86d407>] (crypto\\_pump\\_work+0x123/0xd1c [crypto\\_engine])\n[ 206.542866] [<bf86d407>] (crypto\\_pump\\_work [crypto\\_engine]) from [<c01347c7>] (kthread\\_worker\\_fn+0x6f/0x13c)\n[ 206.542879] [<c01347c7>] (kthread\\_worker\\_fn) from [<c01354f3>] (kthread+0xeb/0x10c)\n[ 206.542888] [<c01354f3>] (kthread) from [<c0100159>] (ret\\_from\\_fork+0x11/0x38)\n[ 206.542893] exception stack(0xcc97ffb0 to 0xcc97fff8)\n[ 206.542899] ffa0: 00000000 00000000 00000000 00000000\n[ 206.542907] ffc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000\n[ 206.542914] ffe0: 00000000 00000000 00000000 00000000 00000013 00000000\n[ 269.559043] rcu: info: rcu\\_sched self-detected stall on cpu\n[ 269.559067] rcu: 0-....: (21003 ticks this gp) idle=06a/1/0x40000004 softirq=6817/6817 fqs=10441 \n[ 269.559073] (t=21005 jiffies g=11233 q=456)\n[ 269.559079] nmi backtrace for cpu 0\n[ 269.559089] cpu: 0 pid: 309 comm: 1c15000.crypto- tainted: g c 5.9.1-sunxi #20.08.14\n[ 269.559092] hardware name: allwinner sun8i family\n[ 269.559122] [<c010d415>] (unwind\\_backtrace) from [<c01097a5>] (show\\_stack+0x11/0x14)\n[ 269.559136] [<c01097a5>] (show\\_stack) from [<c0574801>] (dump\\_stack+0x75/0x84)\n[ 269.559152] [<c0574801>] (dump\\_stack) from [<c0579d33>] (nmi\\_cpu\\_backtrace+0x6b/0x94)\n[ 269.559164] [<c0579d33>] (nmi\\_cpu\\_backtrace) from [<c0579e15>] (nmi\\_trigger\\_cpumask\\_backtrace+0xb9/0xe0)\n[ 269.559178] [<c0579e15>] (nmi\\_trigger\\_cpumask\\_backtrace) from [<c01706ab>] (rcu\\_dump\\_cpu\\_stacks+0xab/0xc8)\n[ 269.559192] [<c01706ab>] (rcu\\_dump\\_cpu\\_stacks) from [<c016fb23>] (rcu\\_sched\\_clock\\_irq+0x5e3/0x7ac)\n[ 269.559205] [<c016fb23>] (rcu\\_sched\\_clock\\_irq) from [<c0176641>] (update\\_process\\_times+0x29/0x70)\n[ 269.559217] [<c0176641>] (update\\_process\\_times) from [<c0184b57>] (tick\\_sched\\_timer+0x37/0x74)\n[ 269.559229] [<c0184b57>] (tick\\_sched\\_timer) from [<c0177089>] (\\_\\_hrtimer\\_run\\_queues+0xf1/0x250)\n[ 269.559241] [<c0177089>] (\\_\\_hrtimer\\_run\\_queues) from [<c0177ab1>] (hrtimer\\_interrupt+0xcd/0x1fc)\n[ 269.559255] [<c0177ab1>] (hrtimer\\_interrupt) from [<c07a9c7b>] (arch\\_timer\\_handler\\_phys+0x27/0x2c)\n[ 269.559270] [<c07a9c7b>] (arch\\_timer\\_handler\\_phys) from [<c0165acb>] (handle\\_percpu\\_devid\\_irq+0x53/0x1a0)\n[ 269.559287] [<c0165acb>] (handle\\_percpu\\_devid\\_irq) from [<c01611b5>] (generic\\_handle\\_irq+0x29/0x34)\n[ 269.559299] [<c01611b5>] (generic\\_handle\\_irq) from [<c0161671>] (\\_\\_handle\\_domain\\_irq+0x41/0x80)\n[ 269.559310] [<c0161671>] (\\_\\_handle\\_domain\\_irq) from [<c058628f>] (gic\\_handle\\_irq+0x3b/0x70)\n[ 269.559322] [<c058628f>] (gic\\_handle\\_irq) from [<c0100b65>] (\\_\\_irq\\_svc+0x65/0x94)\n[ 269.559327] exception stack(0xcc97fa20 to 0xcc97fa68)\n[ 269.559336] fa20: cb8d2660 000064b2 000064b1 000064b1 cdf2b0c0 cb8d2640 00000000 00000032\n[ 269.559345] fa40: 00000000 00000002 cb8d2660 00000000 00000004 cc97fa70 c08d6bd3 c0953d84\n[ 269.559350] fa60: 800d0133 ffffffff\n[ 269.559363] [<c0100b65>] (\\_\\_irq\\_svc) from [<c0953d84>] (\\_raw\\_spin\\_lock+0x28/0x38)\n[ 269.559379] [<c0953d84>] (\\_raw\\_spin\\_lock) from [<c08d6bd3>] (xfrm\\_input+0x137/0xce0)\n[ 269.559391] [<c08d6bd3>] (xfrm\\_input) from [<c08cb1cb>] (xfrm4\\_esp\\_rcv+0x27/0x38)\n[ 269.559403] [<c08cb1cb>] (xfrm4\\_esp\\_rcv) from [<c0877a0f>] (ip\\_protocol\\_deliver\\_rcu+0x27/0x214)\n[ 269.559414] [<c0877a0f>] (ip\\_protocol\\_deliver\\_rcu) from [<c0877c37>] (ip\\_local\\_deliver\\_finish+0x3b/0x40)\n[ 269.559424] [<c0877c37>] (ip\\_local\\_deliver\\_finish) from [<c0877cd5>] (ip\\_local\\_deliver+0x99/0xa4)\n[ 269.559433] [<c0877cd5>] (ip\\_local\\_deliver) from [<c0877d5f>] (ip\\_rcv+0x7f/0x84)\n[ 269.559448] [<c0877d5f>] (ip\\_rcv) from [<c0815295>] (\\_\\_netif\\_receive\\_skb\\_core+0x41d/0xa78)\n[ 269.559461] [<c0815295>] (\\_\\_netif\\_receive\\_skb\\_core) from [<c0815c6b>] (\\_\\_netif\\_receive\\_skb\\_list\\_core+0x97/0x130)\n[ 269.559471] [<c0815c6b>] (\\_\\_netif\\_receive\\_skb\\_list\\_core) from [<c0815e33>] (netif\\_receive\\_skb\\_list\\_internal+0x12f/0x1e0)\n[ 269.559481] [<c0815e33>] (netif\\_receive\\_skb\\_list\\_internal) from [<c0815fc9>] (gro\\_normal\\_list.part.0+0x15/0x24)\n[ 269.559490] [<c0815fc9>] (gro\\_normal\\_list.part.0) from [<c0816939>] (napi\\_complete\\_done+0x85/0x160)\n[ 269.559525] [<c0816939>] (napi\\_complete\\_done) from [<bf8d4dd5>] (r8152\\_poll+0x4a9/0x51c [r8152])\n[ 269.559547] [<bf8d4dd5>] (r8152\\_poll [r8152]) from [<c0816ad1>] (net\\_rx\\_action+0xbd/0x2c4)\n[ 269.559557] [<c0816ad1>] (net\\_rx\\_action) from [<c0101367>] (\\_\\_do\\_softirq+0xcf/0x260)\n[ 269.559569] [<c0101367>] (\\_\\_do\\_softirq) from [<c0120df5>] (irq\\_exit+0x79/0x98)\n[ 269.559578] [<c0120df5>] (irq\\_exit) from [<c0161675>] (\\_\\_handle\\_domain\\_irq+0x45/0x80)\n[ 269.559588] [<c0161675>] (\\_\\_handle\\_domain\\_irq) from [<c058628f>] (gic\\_handle\\_irq+0x3b/0x70)\n[ 269.559598] [<c058628f>] (gic\\_handle\\_irq) from [<c0100b65>] (\\_\\_irq\\_svc+0x65/0x94)\n[ 269.559602] exception stack(0xcc97fdf8 to 0xcc97fe40)\n[ 269.559607] fde0: 000000c3 00000000\n[ 269.559616] fe00: c9aca488 00000004 00000020 cb8d2640 00000000 00000004 00000002 00000002\n[ 269.559626] fe20: cb8d2660 00000000 cb9c7c50 cc97fe48 c08d9353 c085fab2 400d0033 ffffffff\n[ 269.559639] [<c0100b65>] (\\_\\_irq\\_svc) from [<c085fab2>] (netlink\\_has\\_listeners+0x4a/0x58)\n[ 269.559652] [<c085fab2>] (netlink\\_has\\_listeners) from [<c08d9353>] (xfrm\\_replay\\_advance+0x3b/0x68)\n[ 269.559665] [<c08d9353>] (xfrm\\_replay\\_advance) from [<c08d6e25>] (xfrm\\_input+0x389/0xce0)\n[ 269.559679] [<c08d6e25>] (xfrm\\_input) from [<bf86d075>] (crypto\\_finalize\\_request+0x31/0x7c [crypto\\_engine])\n[ 269.559696] [<bf86d075>] (crypto\\_finalize\\_request [crypto\\_engine]) from [<bf878afd>] (sun8i\\_ce\\_handle\\_cipher\\_request+0x295/0x5b4 [sun8i\\_ce])\n[ 269.559710] [<bf878afd>] (sun8i\\_ce\\_handle\\_cipher\\_request [sun8i\\_ce]) from [<bf86d407>] (crypto\\_pump\\_work+0x123/0xd1c [crypto\\_engine])\n[ 269.559724] [<bf86d407>] (crypto\\_pump\\_work [crypto\\_engine]) from [<c01347c7>] (kthread\\_worker\\_fn+0x6f/0x13c)\n[ 269.559736] [<c01347c7>] (kthread\\_worker\\_fn) from [<c01354f3>] (kthread+0xeb/0x10c)\n[ 269.559746] [<c01354f3>] (kthread) from [<c0100159>] (ret\\_from\\_fork+0x11/0x38)\n[ 269.559750] exception stack(0xcc97ffb0 to 0xcc97fff8)\n[ 269.559756] ffa0: 00000000 00000000 00000000 00000000\n[ 269.559765] ffc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000\n[ 269.559772] ffe0: 00000000 00000000 00000000 00000000 00000013 00000000\nroot@orangepi-r1:~# \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "hi,\n \n\n\n thanks for your work,\n \n\n\n i tested your kernel packages yesterday and everything works flawlessly now. i get about 40 to 50 mbps throughput with ipsec now without stalling and \"breaking\" the interface.\n \n\n\n  \n \n\n\n i am happy, thanks alot!\n \n\n\n  \n \n\n\n cheers\n \n\n\n  \n \n\n\n ford prefect\n \n\n\n  \n \n\n\n", "name": "", "is_accepted": false }, { "text": "wonderful - this is great to hear!   it is a new patch, so keep an eye on the pull requests for the kernels regarding this change, i'm sure it will get pulled into v5.10 soon (and hopefully backported to v5.9 as well).\n \n", "name": "", "is_accepted": false }, { "text": "strange thing happened.... even i have pinned the current kernel in apt  (and it is still there)  after some apt upgrades the same thing happens again as in the beginning....\n \n\n\n  \n \n\n\n the device was powered on 24/7 since november 12th and worked flawlessly...... and now this....\n \n\n\n  \n \n\n\n cannot explain why :-/\n \n\n\n  \n \n\n\n cheers\n \n\n\n  \n \n\n\n ford\n \n", "name": "", "is_accepted": false }, { "text": "if we look together into the logs, we might spot the problem: \n  \n \n\n\narmbianmonitor -u\n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "hi,\n \n\n\n  \n \n\n\n i just got some time and attached my serial port again....:\n \n\n\n  \n \n\n\n  \n \n\n\nroot@orangepi-r1:~# ping 192.168.202.1\nping 192.168.202.1 (192.168.202.1) 56(84) bytes of data.\n64 bytes from 192.168.202.1: icmp\\_seq=1 ttl=64 time=26.2 ms\n64 bytes from 192.168.202.1: icmp\\_seq=2 ttl=64 time=25.2 ms\n64 bytes from 192.168.202.1: icmp\\_seq=3 ttl=64 time=27.0 ms\n^c\n--- 192.168.202.1 ping statistics ---\n3 packets transmitted, 3 received, 0% packet loss, time 2003ms\nrtt min/avg/max/mdev = 25.205/26.143/27.000/0.735 ms\nroot@orangepi-r1:~# iperf3 -c 192.168.202.1\nconnecting to host 192.168.202.1, port 5201\n[ 5] local 192.168.202.2 port 51956 connected to 192.168.202.1 port 5201\n[ id] interval transfer bitrate retr cwnd\n[ 5] 0.00-1.00 sec 517 kbytes 4.23 mbits/sec 1 1.22 kbytes \n[ 5] 1.00-2.00 sec 0.00 bytes 0.00 bits/sec 0 1.22 kbytes \n[ 5] 2.00-3.00 sec 0.00 bytes 0.00 bits/sec 0 1.22 kbytes \n[ 5] 3.00-4.00 sec 0.00 bytes 0.00 bits/sec 0 1.22 kbytes \n[ 5] 4.00-5.00 sec 0.00 bytes 0.00 bits/sec 0 1.22 kbytes \n\nctrl-a z for help | 115200 8n1 | nor | minicom 2.7.1 | vt102 | offline | ttyusb0 \n\n\n  \n \n\n\n  \n \n\n\n i used the kernel from november 11th  which 5kft has kindly provided and worked flawlessly untile a couple of days when apt meant he has to update uboot an the kernel to a newer version despite i set it \"on hold\".... but even a downgrade does not change anything.\n \n\n\n  \n \n\n\nlinux orangepi-r1 5.10.0-rc3-sunxi #trunk smp wed nov 11 15:03:40 utc 2020 armv7l gnu/linux\nroot@orangepi-r1:~# \n\n\n  \n \n\n\n since armbianmonitor -u still does not hide my personal ipv6 prefix  i uploaded the edited  output  here:\n \n\n\n  \n \n\n\n http://104.168.35.206/ietooyai\n \n\n\n  \n \n\n\n  \n \n\n\n  \n \n\n\n edit:\n \n\n\n wait..... logging in via ssh  and let the serial console open for a dmesg -w i got this, whet simply pinging over my xfrm ipsec tunnel:\n \n\n\n  \n \n\n\n[ 268.956055] sun8i-ce 1c15000.crypto: fallback for ecb-aes-sun8i-ce is ecb-aes-neonbs\n[ 268.956194] sun8i-ce 1c15000.crypto: fallback for ecb-aes-sun8i-ce is ecb-aes-neonbs\n[ 268.956332] sun8i-ce 1c15000.crypto: fallback for ecb-aes-sun8i-ce is ecb-aes-neonbs\n[ 395.756162] sun8i-ce 1c15000.crypto: fallback for cbc-aes-sun8i-ce is cbc(aes-generic)\n[ 395.756973] sun8i-ce 1c15000.crypto: fallback for cbc-aes-sun8i-ce is cbc(aes-generic)\n[ 400.555283] nohz tick-stop error: non-rcu local softirq work is pending, handler #08!!!\n[ 401.556432] nohz tick-stop error: non-rcu local softirq work is pending, handler #08!!!\n[ 402.562189] nohz tick-stop error: non-rcu local softirq work is pending, handler #08!!!\n[ 403.559759] nohz tick-stop error: non-rcu local softirq work is pending, handler #08!!!\n[ 404.560813] nohz tick-stop error: non-rcu local softirq work is pending, handler #08!!!\n[ 405.017837] sun8i-ce 1c15000.crypto: fallback for cbc-aes-sun8i-ce is cbc(aes-generic)\n[ 405.018398] sun8i-ce 1c15000.crypto: fallback for cbc-aes-sun8i-ce is cbc(aes-generic)\n[ 405.562329] nohz tick-stop error: non-rcu local softirq work is pending, handler #08!!!\n[ 406.563600] nohz tick-stop error: non-rcu local softirq work is pending, handler #08!!!\n[ 407.565302] nohz tick-stop error: non-rcu local softirq work is pending, handler #08!!!\n[ 408.566290] nohz tick-stop error: non-rcu local softirq work is pending, handler #08!!!\n[ 409.570524] nohz tick-stop error: non-rcu local softirq work is pending, handler #08!!!\n\n\n\n\n  \n \n\n\n  \n \n\n\n when starting my iperf3 test to the other site of the ipsec tunnel  this happenens...:\n \n\n\n\n[ 540.338679] sched: rt throttling activated\n \n\n\n[ 560.110930] rcu: info: rcu\\_sched self-detected stall on cpu\n[ 560.110977] rcu: 2-....: (5250 ticks this gp) idle=9f6/1/0x40000004 softirq=10405/10406 fqs=2582 \n[ 560.110994] (t=5251 jiffies g=16009 q=76)\n[ 560.111009] nmi backtrace for cpu 2\n[ 560.111032] cpu: 2 pid: 321 comm: 1c15000.crypto- tainted: g c 5.10.0-rc3-sunxi #trunk\n[ 560.111043] hardware name: allwinner sun8i family\n[ 560.111098] [<c010cbbd>] (unwind\\_backtrace) from [<c010966d>] (show\\_stack+0x11/0x14)\n[ 560.111131] [<c010966d>] (show\\_stack) from [<c0977aff>] (dump\\_stack+0x75/0x82)\n[ 560.111166] [<c0977aff>] (dump\\_stack) from [<c0592063>] (nmi\\_cpu\\_backtrace+0x8f/0xb0)\n[ 560.111198] [<c0592063>] (nmi\\_cpu\\_backtrace) from [<c0592139>] (nmi\\_trigger\\_cpumask\\_backtrace+0xb5/0xe0)\n[ 560.111227] [<c0592139>] (nmi\\_trigger\\_cpumask\\_backtrace) from [<c0972609>] (rcu\\_dump\\_cpu\\_stacks+0xab/0xc8)\n[ 560.111260] [<c0972609>] (rcu\\_dump\\_cpu\\_stacks) from [<c0171a65>] (rcu\\_sched\\_clock\\_irq+0x5c5/0x794)\n[ 560.111294] [<c0171a65>] (rcu\\_sched\\_clock\\_irq) from [<c0178bc7>] (update\\_process\\_times+0x4f/0x78)\n[ 560.111325] [<c0178bc7>] (update\\_process\\_times) from [<c018723b>] (tick\\_sched\\_timer+0x37/0x74)\n[ 560.111356] [<c018723b>] (tick\\_sched\\_timer) from [<c01795b7>] (\\_\\_hrtimer\\_run\\_queues+0xdf/0x224)\n[ 560.111387] [<c01795b7>] (\\_\\_hrtimer\\_run\\_queues) from [<c0179fa5>] (hrtimer\\_interrupt+0xcd/0x200)\n[ 560.111422] [<c0179fa5>] (hrtimer\\_interrupt) from [<c07c532f>] (arch\\_timer\\_handler\\_phys+0x27/0x2c)\n[ 560.111456] [<c07c532f>] (arch\\_timer\\_handler\\_phys) from [<c0166763>] (handle\\_percpu\\_devid\\_irq+0x53/0x184)\n[ 560.111486] [<c0166763>] (handle\\_percpu\\_devid\\_irq) from [<c0161f1d>] (generic\\_handle\\_irq+0x29/0x34)\n[ 560.111513] [<c0161f1d>] (generic\\_handle\\_irq) from [<c01623d9>] (\\_\\_handle\\_domain\\_irq+0x41/0x80)\n[ 560.111542] [<c01623d9>] (\\_\\_handle\\_domain\\_irq) from [<c059e5db>] (gic\\_handle\\_irq+0x63/0x74)\n[ 560.111570] [<c059e5db>] (gic\\_handle\\_irq) from [<c0100b65>] (\\_\\_irq\\_svc+0x65/0x94)\n[ 560.111584] exception stack(0xcbab1aa0 to 0xcbab1ae8)\n[ 560.111609] 1aa0: ca9546e0 00000a01 00000a00 00000a00 cd337600 ca9546c0 00000000 00000032\n[ 560.111632] 1ac0: 00000000 00000002 ca9546e0 00000000 00000007 cbab1af0 c08f5673 c09818cc\n[ 560.111645] 1ae0: 800f0133 ffffffff\n[ 560.111676] [<c0100b65>] (\\_\\_irq\\_svc) from [<c09818cc>] (\\_raw\\_spin\\_lock+0x28/0x38)\n[ 560.111705] [<c09818cc>] (\\_raw\\_spin\\_lock) from [<c08f5673>] (xfrm\\_input+0x137/0xce4)\n[ 560.111736] [<c08f5673>] (xfrm\\_input) from [<c08e9b33>] (xfrm4\\_esp\\_rcv+0x27/0x38)\n[ 560.111769] [<c08e9b33>] (xfrm4\\_esp\\_rcv) from [<c0895a97>] (ip\\_protocol\\_deliver\\_rcu+0x27/0x214)\n[ 560.111799] [<c0895a97>] (ip\\_protocol\\_deliver\\_rcu) from [<c0895cbf>] (ip\\_local\\_deliver\\_finish+0x3b/0x44)\n[ 560.111827] [<c0895cbf>] (ip\\_local\\_deliver\\_finish) from [<c0895d1d>] (ip\\_local\\_deliver+0x55/0xbc)\n[ 560.111855] [<c0895d1d>] (ip\\_local\\_deliver) from [<c0895e0b>] (ip\\_rcv+0x87/0x94)\n[ 560.111884] [<c0895e0b>] (ip\\_rcv) from [<c08301ab>] (\\_\\_netif\\_receive\\_skb\\_core+0x3cb/0xaac)\n[ 560.111912] [<c08301ab>] (\\_\\_netif\\_receive\\_skb\\_core) from [<c0830c0f>] (\\_\\_netif\\_receive\\_skb\\_list\\_core+0x97/0x130)\n[ 560.111937] [<c0830c0f>] (\\_\\_netif\\_receive\\_skb\\_list\\_core) from [<c0830dd7>] (netif\\_receive\\_skb\\_list\\_internal+0x12f/0x1e4)\n[ 560.111963] [<c0830dd7>] (netif\\_receive\\_skb\\_list\\_internal) from [<c0830f61>] (gro\\_normal\\_list.part.0+0x15/0x24)\n[ 560.111988] [<c0830f61>] (gro\\_normal\\_list.part.0) from [<c08318cd>] (napi\\_complete\\_done+0x85/0x160)\n[ 560.112054] [<c08318cd>] (napi\\_complete\\_done) from [<bf962dd9>] (r8152\\_poll+0x4a9/0x51c [r8152])\n[ 560.112117] [<bf962dd9>] (r8152\\_poll [r8152]) from [<c0831a65>] (net\\_rx\\_action+0xbd/0x2bc)\n[ 560.112143] [<c0831a65>] (net\\_rx\\_action) from [<c0101367>] (\\_\\_do\\_softirq+0xcf/0x26c)\n[ 560.112169] [<c0101367>] (\\_\\_do\\_softirq) from [<c0120799>] (irq\\_exit+0x79/0x98)\n[ 560.112195] [<c0120799>] (irq\\_exit) from [<c01623dd>] (\\_\\_handle\\_domain\\_irq+0x45/0x80)\n[ 560.112222] [<c01623dd>] (\\_\\_handle\\_domain\\_irq) from [<c059e5db>] (gic\\_handle\\_irq+0x63/0x74)\n[ 560.112247] [<c059e5db>] (gic\\_handle\\_irq) from [<c0100b65>] (\\_\\_irq\\_svc+0x65/0x94)\n[ 560.112261] exception stack(0xcbab1e70 to 0xcbab1eb8)\n[ 560.112278] 1e60: 00000000 00000000 ca855f88 0000000c\n[ 560.112301] 1e80: cd337b40 ca9546c0 00000000 00000004 00000002 00000002 ca9546e0 00000000\n[ 560.112322] 1ea0: c9fc6250 cbab1ec0 c08f78bd c08f58c4 000f0033 ffffffff\n[ 560.112347] [<c0100b65>] (\\_\\_irq\\_svc) from [<c08f58c4>] (xfrm\\_input+0x388/0xce4)\n[ 560.112379] [<c08f58c4>] (xfrm\\_input) from [<bf89a075>] (crypto\\_finalize\\_request+0x31/0x7c [crypto\\_engine])\n[ 560.112420] [<bf89a075>] (crypto\\_finalize\\_request [crypto\\_engine]) from [<bf952b6f>] (sun8i\\_ce\\_cipher\\_run+0x27/0x2c [sun8i\\_ce])\n[ 560.112456] [<bf952b6f>] (sun8i\\_ce\\_cipher\\_run [sun8i\\_ce]) from [<bf89a407>] (crypto\\_pump\\_work+0x123/0xd1c [crypto\\_engine])\n[ 560.112489] [<bf89a407>] (crypto\\_pump\\_work [crypto\\_engine]) from [<c013421b>] (kthread\\_worker\\_fn+0x6f/0x13c)\n[ 560.112519] [<c013421b>] (kthread\\_worker\\_fn) from [<c0134f3b>] (kthread+0xeb/0x10c)\n[ 560.112545] [<c0134f3b>] (kthread) from [<c0100159>] (ret\\_from\\_fork+0x11/0x38)\n[ 560.112558] exception stack(0xcbab1fb0 to 0xcbab1ff8)\n[ 560.112575] 1fa0: 00000000 00000000 00000000 00000000\n[ 560.112597] 1fc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000\n[ 560.112616] 1fe0: 00000000 00000000 00000000 00000000 00000013 00000000\n\n\n\n---> and there it hangs \n\n\n  \n \n\n\n  \n \n\n\n  \n \n\n\n  \n \n\n\n  \n \n\n\n cheers\n \n\n\n  \n \n\n\n ford\n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "btw:  i tried to use the ethernet devices vice versa and still, the same happens...\n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "it might be worth trying to reinstall the original posted -rc3 version again (esp. the dtb and image debs), just to see if that helps?  (just force an install via dpkg -i *.deb)\n \n", "name": "", "is_accepted": false }, { "text": "hi 5kft,\n \n\n\n  \n \n\n\n i did.....  and i also  uninstalled \n \n\n\nii armbian-config 21.11.4 all armbian configuration utility\nii armbian-firmware 21.02.0-trunk.29 all linux firmware\n\nii linux-buster-root-current-orangepi-r1 21.02.0-trunk.30 armhf armbian tweaks for buster on orangepi-r1 (current branch)\nii linux-dtb-current-sunxi 21.02.0-trunk.24 armhf linux dtb, version 5.9.15-sunxi\narmhf\nii linux-image-current-sunxi 21.02.0-trunk.24 armhf linux kernel, version 5.9.15-sunxi\nii linux-libc-dev:armhf 5.9.11-1 armhf linux support headers for userspace development\nii linux-u-boot-orangepi-r1-current 21.02.0-trunk.12 armhf uboot loader 2020.10\n\n\nso currently these are installed, and no change :-( \n\nii linux-image-dev-sunxi 20.11.0-trunk armhf linux kernel, version 5.10.0-rc3-sunxi\nii linux-dtb-dev-sunxi 20.11.0-trunk armhf linux dtb, version 5.10.0-rc3-sunxi\nii linux-headers-dev-sunxi 20.11.0-trunk armhf linux kernel headers for 5.10.0-rc3-sunxi on \n\n\n  \n \n\n\n  \n \n\n\n wonder what i am missing? something else must have been broken when doing a apt upgrade...\n \n\n\n  \n \n\n\n cheers,\n \n\n\n  \n \n\n\n ford \n \n\n\n  \n \n\n\n  \n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "unfortunately i'm not an expert in rcu stalls (https://www.kernel.org/doc/documentation/rcu/stallwarn.txt).  do you have other processes running on the device that could be impacting the system?  e.g., what does \"top\" show while you try to use networking?\n \n", "name": "", "is_accepted": false }, { "text": "there is nothing despite 'normal background processes' running in the background.\n \n\n\n  \n \n\n\n this device is only connecting to my ipsec gateway and - if it works, should do some basic routing.\n \n\n\n  \n \n\n\n currently  the device is not running, but the most cpu intense background activity might be autoupdate apt or  an updatedb of locate....\n \n\n\n  \n \n\n\n nearly all cpu power is going in the encryption in that moment.\n \n\n\n  \n \n\n\n  \n \n\n\n cheers,\n \n\n\n  \n \n\n\n fp\n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "hi,\n \n\n\n  \n \n\n\n has no one an idea what i could try?   installing \"the old\" dtb's and kernels does not make any difference.   changing to a nightly build doesn't change anything either.\n \n\n\n  \n \n\n\n regaring arm based cpus you don't find too much information about the 'cpu stalled' problem, though :-(\n \n\n\n  \n \n\n\n cheers + happy new year\n \n\n\n  \n \n\n\n  \n \n\n\n ford.\n \n\n\n  \n \n\n\n  \n \n", "name": "", "is_accepted": false } ]

[ { "text": "you've forgot to define \"param\\_spidev\\_spi\\_bus\" which is mandatory ...\n \n", "name": "", "is_accepted": true }, { "text": "thank you very much, should the armbian-config have set this option ?\n \n\n\n  \n \n\n\n sorry i didn't find it in overlay documentation that this flag is needed ^^\n \n", "name": "", "is_accepted": false }, { "text": "look at this doc file : /boot/dtb/overlay/readme.sun8i-h3-overlays\n \n", "name": "", "is_accepted": false } ]

[ { "text": "problem was fixed, but you need to apt upgrade and reboot.\n \n", "name": "", "is_accepted": true }, { "text": "interesting.\n \n\n\n you can try to install them manually for now.\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 apt install linux-headers-current-rockchip64\n \n", "name": "", "is_accepted": false }, { "text": "thank you very much igor.\n \n\n\n  \n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "thanks!\n \n", "name": "", "is_accepted": false } ]

[ { "text": "i just did a quick test on le potato, increasing cma to 512 mb was very easy following the above instructions with the /boot/dtb/amlogic/meson-gxl-s905x-libretech-cc.dtb device tree.  the property yo uwant to change is right at the top of the file as a handle under \"reserved-memory\"\n \n\n\n  \n \n\n\n any value that is 0x400000 aligned should be valid, so you can experiment.\n \n\n\n  \n \n\n\n  \n \n", "name": "", "is_accepted": true }, { "text": "uniformbuffer\n \n\n\n\n\n hi uniformbuffer, what mpv.conf arguments that are you using?\n \n\n\n hwdec =auto?\n \n\n\n  \n \n\n\n thanks\n \n", "name": "", "is_accepted": false }, { "text": "hi, \n i don't got any particular mpv conf, i have only added \"ytdl-format=bestvideo[height<=?720][fps<=?60][vcodec!=?vp9]+bestaudio/best\" to get video from youtube directly with the resolution of my monitor, nothing more. \n your question make me some tests: unfortunatly i don't get hardware acceleration from youtube videos (maybe i have to change something), but i'm sure to got it from local video. \n running a vp9 video of my self recorded desktop i got from \"mpv --hwdec=yes ./myvid.mkv\": \n ``` \n  (+) video --vid=1 (*) (vp9 1280x800) \n [vaapi] libva: vagetdrivernamebyindex() failed with unknown libva error, driver\\_name = (null) \n failed to open vdpau backend libvdpau\\_nvidia.so: cannot open shared object file: no such file or directory \n using hardware decoding (v4l2m2m-copy). \n vo: [gpu] 1280x800 nv12 \n v: 00:00:01 / 00:00:18 (10%) \n .... \n ```\n \n\n\n youtube videos do not use nv12, so maybe this make mpv do not enable hardware acceleration (i do not got \"using hardware decoding (v4l2m2m-copy).\").\n \n\n\n \"vo: [gpu]\" should means that the \"video output is gpu accelerated\", but i don't think means also hardware acceleration, i have to check this. if i make them accelerated i will send you a message \n \n\n\n  \n \n\n\n ps: don't get my words for the truth, i'm a beginner on this topic and i'm experimenting to get some knowledge\n \n\n\n  \n \n\n\n  \n \n\n\n edit: got it. using \"mpv --hwdec=yes --hwdec-codecs=vp9 *youtube video address*\" gives hardware decoding, but unfortunatly the performance are wrost than software decoding. anyway i'm glad that something start working, good job armbian team, i know this is not easy!\n \n", "name": "", "is_accepted": false }, { "text": "i tried with balbes latest image ver 20200828 kernel 5.7.16 but i only got output  pollerr so hardware decoding failed with all videos even mp4\n \n", "name": "", "is_accepted": false }, { "text": "that's strange, what is your mesa version? mine is 20.1.5 currently. also my kernel is the 5.7.15 that currently use armbian by default.\n \n", "name": "", "is_accepted": false }, { "text": "its from ppa:oibaf/graphics-drivers\n \n", "name": "", "is_accepted": false }, { "text": "i personally don't use ppa repositories, so i don't know what version they are providing. you can check what is your by simply running\n \n\n\nglxinfo | grep \"opengl version\"\n\n\n mine gives \"opengl version string: 2.1 mesa 20.1.5\"\n \n\n\n  \n \n\n\n my drivers are a bit updated than standard because i set debian sid as additional repository, so i get very cutting edge updates.\n \n\n\n also, just to be sure, do you have \"meson\\_vdec\" module enabled? it is the kernel module that enable the hardware decoding. by default meson\\_vdec should be enabled, but who knows?\n \n\n\n to check you can run \"lsmod\" and search among them for meson\\_vdec.\n \n\n\n if you don't have it enabled, you can enable with\n \n\n\nsudo modprobe meson-vdec\n\n\n (notice that when enabling, the module is called \"meson-vdec\", not \"meson\\_vdec\")\n \n\n\n this will enable it for current session, so do not survive rebooting. to make it load on every boot, add \"meson-vdec\" to /etc/modules\n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "hi,\n \n\n\n i'm making some test to make meson\\_vdec working. currently i got v4l2m2m hardware decoding on both xorg and wayland, but the video stutter a lot. while playing i have noticed that on dmesg i got some errors like:\n \n\n\n\n\n  \n \n\n\n from what i have read, it has something to do with cma and looking at \"cat /proc/meminfo\" i got:\n \n\n\n\n\n if you notice, i got only 2 mb of free cma memory, so i can suppose that the reason of bad playback performance could be not having enough memory, so i would like to ask, again, if someone know a way to change the cma size.\n \n\n\n like i said in the previous posts, setting it from kernel parameters using armbianenv.txt do not work. maybe the cma size has been hardcoded on kernel config?\n \n", "name": "", "is_accepted": false }, { "text": "hello uniformbuffer,\n \n\n\n  \n \n\n\n    the cma memory is set by a device tree entry, so that would be the only way to change it to my knowledge.  the drivers are extremely unoptimized presently for the vdec/venc, and the recommended setting is over 800 mb.  this is an obvious problem for a general-purpose distribution, it renders the la frite 512 mb boards unbootable, and leaves no real room for any working tasks on the 1 gb ones.  it may be possible to implement this as an overlay, but in the meantime modifying the device tree is the only route:\n \n\n\n  \n \n\n\n https://github.com/armbian/build/blob/cc7ab6a6b1d91977bd9e154245307e85f7f76519/patch/kernel/meson64-current/0302-arm64-dts-meson-set-dma-pool-to-896mb.patch\n \n\n\n  \n \n\n\n this patch gives you the handle and value to get the required 896 mb cma pool.\n \n", "name": "", "is_accepted": false }, { "text": "thanks for the answer, this explain why the using hardware decoding stutter so much. unfortunately i'm not so skilled to recompile the kernel, i'm scared to make device unbootable (that happened a lot of time). also i don't have a an x86 machine to use armbian tools. since, like you said, increasing so much the cma make the board useless for any other purpose, i will wait for some improvements. thanks anyway for the answer!\n \n\n\n  \n \n\n\n ps: i would like to ask a question for my personal curiosity: do you know if exist a board that have hardware decoding enabled on mainline kernel? as far as i know, even allwinner devices, that have been completely reverse engineered, have trouble to enable it because applications need to support v4l2\\_request api. seems like find a unicorn is much more easy. this is absolutely not a critique, i know that is very difficult to get it working, i would simply like to know if exist some other board supported by armbian that have it enabled because i would like to use it as general purpose/media device, and.... i would like to avoid android as much as possible.\n \n\n\n  \n \n\n\n thanks for the attention,\n \n\n\n have a good day\n \n", "name": "", "is_accepted": false }, { "text": "thankfully the kernel does not need recompiled for this, only the device tree.  see the post below, i b elieve this is still accurate as far as device tree decompile/recompile method, can be done on the device (use the correct device tree for your board )\n \n\n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "thanks for the info, like i said i'm not very skilled with kernel things, but thanks to your guide i was able to change cma allocation from 256m to 512m.\n \n\n\n i have also tried to set 1gb with 0x40000000, that should be aligned with 0x400000, but after setting it i got no monitor output (from leds pattern i can say it was working, sysreq magic keys also worked, so the kernel was on).\n \n\n\n anyway, that's not foundamental, i have also tried to set the cma with the same value of the patch you linked (0x38000000) and it worked, making the cma 896mb.\n \n\n\n  \n \n\n\n i have tested some h264 and vp9 videos and the performance it's still choppy (after increasing to 512mb it become a little better).\n \n\n\n i have tried mpv with `mpv --hwdec=yes video.mkv` and ffplay with `ffplay -vcodec h264\\_v4l2m2m video\\_h264.mkv` and `ffplay -vcodec vp9\\_v4l2m2m video\\_vp9.webm` .\n \n\n\n for now i got the best performance with vp9 format using ffplay.\n \n\n\n a strange thing is that ffplay perform better than mpv, but mpv use ffmpeg like ffmplay, so they should have more or less the same performance. \n \n\n\n anyway the low performance seems to be related to a very single threaded behavior. after increasing cma to 512mb i got some free cma left (40-80mb) and increasing again to 896mb increase the free cma proportionally, so it seems that meson\\_vdec does not get advantage from memory after ~512mb.\n \n\n\n  \n \n\n\n anyway, even if there are some problems, i'm happy to be able to see progresses with my eyes! \n \n\n\n thanks again for the help and for your hard work \n \n", "name": "", "is_accepted": false } ]

[ { "text": "never mind, i just did a regular `apt update && apt upgrade` and got the new fixed kernel up and running, and confirmed this issue is now completely gone!  \n \n", "name": "", "is_accepted": true }, { "text": "you could probably downgrade the kernel to a version lower than 5.10.60 using armbian-config and wait until 5.10.62 is available.\n \n", "name": "", "is_accepted": false }, { "text": "iirc rockchip64 sources are directly attached to mainline so you could also simply use the build script and create your own kernel package with current branch which then should contain .62 or newer if available.\n \n", "name": "", "is_accepted": false }, { "text": "https://github.com/armbian/build/actions/workflows/build.yml \n or by using nightly kernels which are 24h old in worst case.\n \n", "name": "", "is_accepted": false }, { "text": "please do forgive my ignorance, but i opened `armbian-config`, and on the other kernel i see this:\n \n\n\n  \n \n\n\n  \n \n\n\n  \n \n\n\n would the highlighted image do the job?\n \n\n\n  \n \n\n\n from what i understand that one has the 5.10.63 kernel, so it should have this issue fixed!\n \n", "name": "", "is_accepted": false } ]

[ { "text": "looks there is a problem with one of my routers, not opi3... small change in routing scheme and i get www from ip webcam on phone. \n \n", "name": "", "is_accepted": true }, { "text": "please confirm ip forwarding is enabled\n \n\n\n  \n \n\n\n https://linuxconfig.org/how-to-turn-on-off-ip-forwarding-in-linux\n \n", "name": "", "is_accepted": false }, { "text": "@laurentppol  :  asking just out of curiosity , can you elaborate more on your this \"surveillance server\" ? which type of external storage attached to opi3 for ip camera videos/images ? which open source surveillance software used and its configuration ? number  of ip camera(s) used and their types ?  and about over all performance and satisfaction level for this whole setup ? \n \n", "name": "", "is_accepted": false }, { "text": "storage - external usb->sata hdd, 320gb, about 2gb/24h @ 1fps, software: motion, set to permanently record at 1fps from ip webcam on old android phone (xperia l), image set 1280x1024. plus cron replica to remote storage every 10min (wifi link). separate wifi network (different channel from other apps for performance reasons, this is why i have set up opi3 as ap and want routing). satisfaction level: very high :).\n \n\n\n  \n \n\n\n lanefu: thx very much.\n \n", "name": "", "is_accepted": false }, { "text": "ooops, not so fast:\n \n\n\n httping works (to telephone, android does not respond to ping), but using browser i get to.... opi3 http server, not phone.\n \n\n\n iptables are just clear.\n \n\n\n  \n \n\n\n how to solve this?\n \n\n\n  \n \n\n\nroot@orangepi3:~# iptables-save | more\nroot@orangepi3:~# route -n\nkernel ip routing table\ndestination gateway genmask flags metric ref use iface\n0.0.0.0 192.168.1.60 0.0.0.0 ug 100 0 0 eth0\n169.254.0.0 0.0.0.0 255.255.0.0 u 1000 0 0 wlan0\n192.168.1.0 0.0.0.0 255.255.255.0 u 100 0 0 eth0\n192.168.2.0 0.0.0.0 255.255.255.0 u 100 0 0 eth0\n192.168.10.0 192.168.1.30 255.255.255.0 ug 100 0 0 eth0\n192.168.15.0 0.0.0.0 255.255.255.0 u 600 0 0 wlan0\n\n\n  \n \n", "name": "", "is_accepted": false } ]

[ { "text": "i usually do the noob way finding the trigger files for leds \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 du -a /sys | grep led | grep trigger\n \n\n\n  \n \n\n\n i don't know what trigger is needed for mmc but heartbeat is self-explaining.\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 echo heartbeat > trigger\n \n\n\n  \n \n\n\n  \n \n", "name": "", "is_accepted": true }, { "text": "pssst ... if you cat the trigger file, it'll tell you the valid options, and which one is currently selected.\n \n\n\n  \n \n\ntparys@laptop:~$ cat /sys/class/leds/input4\\:\\:capslock/trigger \nnone usb-gadget usb-host rfkill-any rfkill-none kbd-scrolllock kbd-numlock [kbd-capslock]\nkbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock\nkbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock acad-online bat0-charging-or-full\nbat0-charging bat0-full bat0-charging-blink-full-solid disk-activity disk-read disk-write\nide-disk mtd nand-disk cpu cpu0 cpu1 cpu2 cpu3 cpu4 cpu5 cpu6 cpu7 panic mmc0 rfkill0\nphy0rx phy0tx phy0assoc phy0radio rfkill1 audio-mute audio-micmute \n\n\n  \n \n\n\n i'd wager the correct trigger is \"mmc0\", unless there's a both a sd card and emmc slot on that board?\n \n", "name": "", "is_accepted": false }, { "text": "on my bananapi m1 i can only control the green led, but for that usage i do use the following command-line:\n \n\necho 'mmc0' > /sys/class/leds/bananapi:green:usr/trigger\n\n\nonly green led available:\n# ls -l /sys/class/leds/\n\nlrwxrwxrwx 1 root root 0 sep 11 22:11 bananapi:green:usr -> ./../devices/platform/leds/leds/bananapi:green:usr\n\n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "thank-you.  i have got a lot to learn and at the moment my learning curve is as steep as a saturn 5 rocket blasting off and going into orbit.  i am self-educating way more than i am asking questions.\n \n\n\n  \n \n\necho heartbeat > /sys/devices/platform/leds/leds/bananapro:blue:usr/trigger\necho mmc0 > /sys/devices/platform/leds/leds/bananapro:green:usr/trigger\n\n\n\n  \n \n\n\n erm.....  {sheepish look to my face and batting eyelids . . . .}  how do i get this to persist across reboots, or the file i need to alter to make this the default.  :-)\n \n\n\n  \n \n\n\n edit: i think i found answer to my question.  https://smallbusiness.chron.com/run-command-startup-linux-27796.html  is this correct?\n \n", "name": "", "is_accepted": false }, { "text": "simply use /etc/rc.local and put the commands you posted above into that file\n \n", "name": "", "is_accepted": false }, { "text": "and before the\n \n\n\n exit 0\n \n\n\n in /etc/rc.local\n \n", "name": "", "is_accepted": false }, { "text": "thank-you everyone. i would mark multiple solutions, but the board only allows me to mark one. \n \n i got it working. used the cron @reboot method on user root.  the leds are useful where on the screen it may look like it's got stuck, the leds will at least show if there is some activity and if the soc is still got a heartbeat.  i'm still a noob on the higher technical issues of linux.  i have one more question to ask and that will be in another thread.    (yes, i will donate!  i've seen the donate link on the armbian home page, but as you all know, the budget that keeps the roof over the head, electricity supplied, food on the table, etc... is priority. shall donate what i can, when i can.)\n \n\n\n  \n \n\n\n edit: i finally ended up using the /etc/rc.local method.  thank-you @werner and @guidol.\n \n", "name": "", "is_accepted": false }, { "text": "yes. i knew this.  what happened is that i totally forgot about the /sys folder and then i remember that it's quite a large tree. didn't think about using du and grep that way.\n \n", "name": "", "is_accepted": false }, { "text": "yep, working perfectly.  [now only if i could get xdrp, x and xfce4 play nicely. that's another thread.]\n \n", "name": "", "is_accepted": false } ]

[ { "text": "most of the stuff in modern mainline kernels has to be developed from scratch (or ported). asus has nothing to do with that. also we developed many enhancement and fixes for their private legacy kernel. you don't need, it's a waste of time, to deal with outdated & unsupported tinkeros in any way.\n \n\n\n  \n \n\n\n but i can't tell if we will develop overlays for rockchip armhf family or tinkerboard specifically. we have to plan according to available resources. which are very limited / expensive.\n \n", "name": "", "is_accepted": true }, { "text": "just did another build with the 'legacy' kernel v4.4.213 (instead of the 'current' that i did previously) and the /boot/dtb/overlay folder exists.\n \n\n\n armbian\\_21.05.0-trunk\\_tinkerboard\\_focal\\_legacy\\_4.4.213\\_xfce\\_desktop.img\n \n\n\n  \n \n\n\n so, in new 5.x tinkerboard kernels, by choosing 'current' there is no /boot/dtb/overlay folder but exist in legacy kernel 4.4.213.\n \n\n\n is that 'by design' or is simply the build system broken for tinkerboard with 5.x kernel ?\n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "ok @igor , thanks for the answer.\n \n\n\n  \n \n\n\n i know and understand, no worries.\n \n\n\n  \n \n\n\n i've seen that the 'legacy' works just fine and it gives me the features that i need, eg to have the ability to create and test my own driver additions and overlays in a well proven way that is universal in all armbian images.\n \n\n\n  \n \n\n\n thanks again.\n \n\n\n  \n \n", "name": "", "is_accepted": false } ]

[ { "text": "bug is actually outside armbian domain - we are 1000 x too small to be able to fix bugs in community maintained packages -\n \n\n\n https://www.google.com/search?q=lightdm-gtk-greeter+bug - fixed in desktop build scenario, forgotten to fix in armbian-config.\n \n\n\n  \n \n\n\n we have replaced buggy greeter with slick-greeter which is why desktop still works just fine.\n \n", "name": "", "is_accepted": true }, { "text": "tested new image (21.08.01 buster / 5.10.60) with preinstalled xfce desktop. works without any problems. so, i will use this one, if any desktop needed.\n \n\n\n  \n \n\n\n the problem in the server image, discribed above, still exits (broken lightdm)\n \n\n\n  \n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "we probably need to remove the desktop-install feature from armbian-config.. we have new code for our more complex desktops and its not in armbian config.\n \n", "name": "", "is_accepted": false }, { "text": "thx for explaining a newbie, what is causing the bug. i suppose in the next release, you'll drop the armbian desktop support for server images (by removing the menu entry in armbian-config). when this bug is finally fixed, you'll turn it on again. meanwhile you provide two desktop images, that's plenty of work for such small team and more than enough for a workaround! you really do a great job!\n \n\n\n  \n \n\n\n i think, that this bug a general problem and will occur on every board, not only on my bpi m1. armbian-config is great, enduser-friendly utiliy which helps beginners / noobs / newbies to do their first steps in a new os, gathering experience, ending up with a well working device. even an experienced admin saves a lot of time / command lines at the cli, using armbian-config. somehow it seems to me, that i'm the only one who uses armbian-config, otherwise this bug would be reported before.\n \n", "name": "", "is_accepted": false } ]

[ { "text": "i finally managed to get this work. things i was doing wrong:\n \n\n\n \n not using the opi.gpio replacement library - others aren't compatible with the nanopi m4;\n \n \n din lcd pin was connected to the sbc rxd instead of txd;\n \n \n passed wrong pin numbers to the libraries (should be the real physical pins numers);\n \n \n mistaking spi port with device...\n \n\n\n\n here the full guide on how to it properly. start by installing:\n \n\n\n  \n \n\napt-get install python3 python3-pip python3-pil libjpeg-dev zlib1g-dev libfreetype6-dev liblcms2-dev libopenjp2-7 libtiff5 -y\npip3 install luma.oled\napt-get remove python3-rpi.gpio rpi.gpio-common\npip3 install --upgrade opi.gpio\n\n\n  \n \n\n\n wire up your lcd as:\n \n\n\n  \n \n\nmiso > gpio1\\_b0 > spi1\\_txd > 19 > lcd din | blue \nsck > gpio1\\_b1 > spi1\\_clk > 23 > lcd clk | yellow\ncs > gpio1\\_b2 > spi1\\_csn0 > 24 > lcd cs | orange\n\nrst > gpio1\\_a1(3v) > m4 pin 11 > lcd rst pin | white\ndc > gpio1\\_a3(3v) > m4 pin 13 > lcd dc pin | green\n\n\n  \n \n\n\n download an run an example:\n \n\n\n  \n \n\ngit clone https://github.com/rm-hull/luma.examples.git\n\npython3 luma.examples/examplebounce.py \n--display=ssd1351 \\\n--interface=spi \\\n--width=128 --height=128 \\\n--spi-bus-speed=50000000 \\\n--spi-device=0 \\\n--spi-port=1 \\\n--gpio-reset=11 \\\n--gpio-data-command=13 \\\n--gpio opi.gpio \\\n--gpio-mode nanopi.m4.board\n\n\n  \n \n\n\n and you should get something like this:\n \n\n\n  \n \n\n\n \n \n\n\n  \n \n\n\n it seems to be able to drive the display up to around 45fps without noises like i've experienced before in an arduino.\n \n\n\n  \n \n\n\n enjoy.\n \n\n\n  \n \n", "name": "", "is_accepted": true }, { "text": "so the m4v2 is a supported board. that the spi isn't working is probably worth a post by itself in the rockchip 3399 subforum.\n \n\n\n  \n \n\n\n at a glance, i tried turning on the spi on my m4v2 and didn't see any spidev devices pop up, but might need to pull out the serial console to see if u-boot is throwing any warnings about the overlay.\n \n\n\n  \n \n\n\n taking a look at the overlay, i'm not sure it looks correct, as it looks like even if it applies the spi channel is disabled.\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  \n \n", "name": "", "is_accepted": false }, { "text": "thank you for your feedback!\n \n", "name": "", "is_accepted": false }, { "text": "@piter75,\n \n\n\n  \n \n\n\n \n \n\n\n\n  \n \n\n\n 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\n\n param\\_spidev\\_spi\\_bus=1\nparam\\_spidev\\_max\\_freq=100000000\n\n\n\n  \n \n\n\n now the spi shows up:\n \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\n also passes the spidev\\_test (https://raw.githubusercontent.com/torvalds/linux/master/tools/spi/spidev\\_test.c)\n \n\n\n ~# ./spidev\\_test\nspi mode: 0x0\nbits per word: 8\nmax speed: 500000 hz (500 khz)\n\n\n\n  \n \n\n\n (had to adjust the path)\n \n\n\n  \n \n\n\n thank you for the tip!\n \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 display: https://www.ebay.com/itm/203101646517\n \n\n\n datasheet: https://www.waveshare.com/w/upload/5/5b/1.5inch\\_rgb\\_oled\\_module\\_user\\_manual\\_en.pdf\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\n\n ls -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\n now i tried the luma-oled examples (running as root):\n \n\n\n  \n \n\n\n python3 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\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\n\n apt-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  \n \n", "name": "", "is_accepted": false }, { "text": "following my lack of knowledge of the subject i found out another gpio implementation that seems to have mappings for the nanopi m4 called opi.gpio.\n \n\n\n  \n \n\n\n rewired the lcd, i was unsure about the gpio pin i picked for the dc pin:\n \n\n\n  \n \n\nmosi > gpio1\\_a7 > spi1\\_rxd > m4 pin 21 > lcd din pin (blue)\nsck > gpio1\\_b1 > spi1\\_clk > m4 pin 23 > lcd clk pin (yellow)\ncs > gpio1\\_b2 > spi1\\_csn0 > m4 pin 24 > lcd cs pin (orange)\n\nrst > gpio1\\_a1(3v) > m4 pin 11 > lcd rst pin (white)\ndc > gpio1\\_a3(3v) > m4 pin 13 > lcd dc pin (green)\n\n\n  \n \n\n\n installed and run the thing without much success:\n \n\n\n  \n \n\npip3 install --upgrade opi.gpio\n\nls /dev/spi*\n/dev/spidev1.0\n\npython3 luma.examples/examples/3d\\_box.py \\\n--display=ssd1351 \\\n--interface=spi \\\n--width=128 --height=128 \\\n--spi-bus-speed=16000000 \\\n--bgr \\\n--spi-device=1 --spi-port=0 \\\n--gpio-reset=35 \\\n--gpio-data-command=33 \\\n--gpio opi.gpio \\\n--gpio-mode nanopi.m4.board\n\ntraceback (most recent call last):\n file \"luma.examples/examples/3d\\_box.py\", line 129, in <module>\n device = get\\_device()\n file \"/root/luma.examples/examples/demo\\_opts.py\", line 61, in get\\_device\n device = cmdline.create\\_device(args)\n file \"/usr/local/lib/python3.7/dist-packages/luma/core/cmdline.py\", line 246, in create\\_device\n device = device(serial\\_interface=interface(), **params)\n file \"/usr/local/lib/python3.7/dist-packages/luma/core/cmdline.py\", line 161, in spi\n gpio=self.gpio or gpio)\n file \"/usr/local/lib/python3.7/dist-packages/luma/core/interface/serial.py\", line 299, in \\_\\_init\\_\\_\n bitbang.\\_\\_init\\_\\_(self, gpio, transfer\\_size, reset\\_hold\\_time, reset\\_release\\_time, dc=gpio\\_dc, rst=gpio\\_rst)\n file \"/usr/local/lib/python3.7/dist-packages/luma/core/interface/serial.py\", line 187, in \\_\\_init\\_\\_\n self.\\_dc = self.\\_configure(kwargs.get(\"dc\"))\n file \"/usr/local/lib/python3.7/dist-packages/luma/core/interface/serial.py\", line 200, in \\_configure\n self.\\_gpio.setup(pin, self.\\_gpio.out)\n file \"/usr/local/lib/python3.7/dist-packages/opi/gpio.py\", line 470, in setup\n pin = get\\_gpio\\_pin(\\_mode, channel)\n file \"/usr/local/lib/python3.7/dist-packages/opi/pin\\_mappings.py\", line 80, in get\\_gpio\\_pin\n return \\_pin\\_map[mode][channel]\nkeyerror: 33\n\n\n  \n \n\n\n from what i understand of https://github.com/rm-hull/opi.gpio/blob/master/nanopi/m4.py my physical pin 11 maps to gpio 33 and physical pin 13 to gpio 35. is this even correct?\n \n\n\n  \n \n\n\n either way it still fails.\n \n", "name": "", "is_accepted": false } ]

[ { "text": "did you use the w same image for rock pi 4c and 4b?\n \n\n\n  \n \n\n\n 4c needs different images for all usb ports to work properly.\n \n\n\n  \n \n\n\n you could also adjust the currently burnt image by editing fdtfile setting in /boot/armbianenv.txt.\n \n\n\n make sure fdtfile contains 4c and not 4b and reboot.\n \n\n\n all usb ports should be working after the reboot.\n \n", "name": "", "is_accepted": true }, { "text": "thanks! i will try that!\n \n", "name": "", "is_accepted": false }, { "text": "let us know if this solved your issue so the topic can be marked appropriately \n \n", "name": "", "is_accepted": false }, { "text": "solved! thanks! i didn't tough they were require different dtbs. it should appear on the armbian site bc all the boards appear as the same (rockpi4b/a/c). \n \n", "name": "", "is_accepted": false } ]

[ { "text": "20138 hi linux-dtb-dev-sunxi 5.97 armhf linux dtb, version 5.2.14-sunxi\n\n\n try using\n \n\n\n a) an actual supported branch and\n \n\n\n b) up-to-date packages\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": "pi@retrorangepi:~$ armbianmonitor -u\n\nnetwork/firewall problem detected. not able to upload debug info.\nplease fix this or use \"-u\" instead and upload whole output manually\n\n\n \n  \n \n", "name": "", "is_accepted": false }, { "text": "so\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 armbianmonitor -u\n \n", "name": "", "is_accepted": false }, { "text": "using sudo is also a good idea if some resources used by armbianmonitor needs root privileges.\n \n\n\n if i remember well it solves this issue last time i tried.\n \n", "name": "", "is_accepted": false }, { "text": "sudo armbianmonitor -u | pastebinit\n/usr/bin/armbianmonitor: line 388: read: read error: 0: invalid argument\n/usr/bin/armbianmonitor: line 389: [: -ge: unary operator expected\n/usr/bin/armbianmonitor: line 388: read: read error: 0: invalid argument\n/usr/bin/armbianmonitor: line 389: [: -ge: unary operator expected\n/usr/bin/armbianmonitor: line 388: read: read error: 0: invalid argument\n/usr/bin/armbianmonitor: line 389: [: -ge: unary operator expected\n/usr/bin/armbianmonitor: line 388: read: read error: 0: invalid argument\n/usr/bin/armbianmonitor: line 389: [: -ge: unary operator expected\n/usr/bin/armbianmonitor: line 388: read: read error: 0: invalid argument\n/usr/bin/armbianmonitor: line 389: [: -ge: unary operator expected\n/usr/bin/armbianmonitor: line 388: read: read error: 0: invalid argument\n/usr/bin/armbianmonitor: line 389: [: -ge: unary operator expected\n/usr/bin/armbianmonitor: line 388: read: read error: 0: invalid argument\n/usr/bin/armbianmonitor: line 389: [: -ge: unary operator expected\n/usr/bin/armbianmonitor: line 388: read: read error: 0: invalid argument\n/usr/bin/armbianmonitor: line 389: [: -ge: unary operator expected\n/usr/bin/armbianmonitor: line 388: read: read error: 0: invalid argument\n/usr/bin/armbianmonitor: line 389: [: -ge: unary operator expected\n/usr/bin/armbianmonitor: line 388: read: read error: 0: invalid argument\n/usr/bin/armbianmonitor: line 389: [: -ge: unary operator expected\nhttp://paste.ubuntu.com/p/42stcf2nhs/\n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "apt-get install linux-dtb-dev-sunxi\n\ndpkg -l | grep linux-dtb-dev-sunxi\nii linux-dtb-dev-sunxi 20.11.7 armhf linux dtb, version 5.10.4-sunx\n\n\n \n solved the problem\n \n\n\n thanks\n \n", "name": "", "is_accepted": false } ]

[ { "text": "by opening a ticket https://armbian.atlassian.net/browse/ar-776 my job is done. i have other troubles to deal with.\n \n", "name": "", "is_accepted": true }, { "text": "which image exactly? (how to properly report a problem https://www.armbian.com/bugs/ )\n \n", "name": "", "is_accepted": false }, { "text": "the image i restore is a backup made using win32diskimager of my tinkerboard emmc done on 21 december 2020.\n \n\n\n information i can find are ( i just restored it once again right now ):\n \n\n\n  \n \n\n\n linux tinkerboardbuanderie4\\_4 4.4.213-rockchip #3 smp fri dec 11 21:57:14 cet 2020 armv7l armv7l armv7l gnu/linux\n \n\n\n welcome to armbian 20.11.3 bionic with linux 4.4.213-rockchip\n \n\n\n  \n \n\n\n the apt-get upgrade says it can upgrade : \n \n\n\n  \n \n\n\n  \n \n\n\n the following packages have been kept back: \n   armbian-config linux-bionic-root-legacy-tinkerboard sunxi-tools ttf-mscorefonts-installer \n the following packages will be upgraded: \n   apt apt-transport-https apt-utils armbian-bionic-desktop armbian-firmware bind9-host binutils binutils-arm-linux-gnueabihf binutils-common ca-certificates chromium-browser chromium-codecs-ffmpeg-extra curl dirmngr distro-info-data dnsutils firefox \n   ghostscript gir1.2-appindicator3-0.1 gir1.2-gst-plugins-base-1.0 gir1.2-gstreamer-1.0 git git-man gnupg gnupg-l10n gnupg-utils gnupg2 gpg gpg-agent gpg-wks-client gpg-wks-server gpgconf gpgsm gpgv gstreamer1.0-plugins-base gstreamer1.0-plugins-good \n   gstreamer1.0-pulseaudio hostapd initramfs-tools initramfs-tools-bin initramfs-tools-core iproute2 isc-dhcp-client libappindicator3-1 libapt-inst2.0 libapt-pkg5.0 libaudit-common libaudit1 libbind9-160 libbinutils libcaca0 libcurl3-gnutls libcurl4 \n   libdjvulibre-text libdjvulibre21 libdns-export1100 libdns1100 libexiv2-14 libglib2.0-0 libglib2.0-bin libglib2.0-data libglib2.0-dev libglib2.0-dev-bin libgs9 libgs9-common libgstreamer-gl1.0-0 libgstreamer-plugins-base1.0-0 \n   libgstreamer-plugins-good1.0-0 libgstreamer1.0-0 libhogweed4 libirs160 libisc-export169 libisc169 libisccc160 libisccfg160 libjavascriptcoregtk-4.0-18 libldap-2.4-2 libldap-common libldb1 liblwres160 liblz4-1 libmysqlclient20 libnettle6 \n   libnginx-mod-http-geoip libnginx-mod-http-image-filter libnginx-mod-http-xslt-filter libnginx-mod-mail libnginx-mod-stream libnss-myhostname libp11-kit0 libpam-modules libpam-modules-bin libpam-runtime libpam-systemd libpam0g libproxy1v5 libpython2.7 \n   libpython2.7-minimal libpython2.7-stdlib libpython3.6 libpython3.6-dev libpython3.6-minimal libpython3.6-stdlib libsasl2-2 libsasl2-modules-db libseccomp2 libsmbclient libssl-dev libssl1.0.0 libssl1.1 libsystemd0 libtiff5 libudev1 libwavpack1 \n   libwbclient0 libwebkit2gtk-4.0-37 libx11-6 libx11-data libx11-dev libx11-xcb1 libzstd1 linux-dtb-legacy-rockchip linux-image-legacy-rockchip linux-libc-dev linux-u-boot-tinkerboard-legacy nginx nginx-common nginx-core openssl openvpn p11-kit \n   p11-kit-modules python-apt-common python2.7 python2.7-minimal python3-apport python3-apt python3-httplib2 python3-problem-report python3-xdg python3.6 python3.6-dev python3.6-minimal samba-libs screen sudo systemd systemd-sysv tar tzdata u-boot-tools \n   ubuntu-keyring udev wpasupplicant xdg-utils xserver-common xserver-xorg-core\n \n\n\n  \n \n\n\n  \n \n\n\n reading that, i have the feeling that not upgrading linux-bionic-root-legacy-tinkerboard  might be in conflict with upgrading some other parts of the low level system such as linux-u-boot-tinkerboard-legacy ?\n \n\n\n currently my kernel packages are :\n \n\n\n  \n \n\n\n root@tinkerboardbuanderie4\\_4:~# apt list --installed | grep -i tinker\n \n\n\n warning: apt does not have a stable cli interface. use with caution in scripts.\n \n\n\n linux-bionic-root-legacy-tinkerboard/bionic,now 20.11.3 armhf [installed,upgradable to: 21.05.1] \n linux-u-boot-tinkerboard-legacy/bionic,now 20.11.3 armhf [installed,upgradable to: 21.05.1]\n \n\n\n  \n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "if it so hard to follow https://www.armbian.com/bugs/ and provide logs we are requesting? things you thinks that are important, might not be enough. \n \n\n\n  \n \n\n\n tl;dr;\n \n\n\n without logs, you are alone dealing with this problem.\n \n", "name": "", "is_accepted": false }, { "text": "and i dealt with my problem !\n \n\n\n i avoid doing apt-get update for now and my system is up and running.\n \n\n\n  \n \n\n\n but i also got back from storage an usb serial cable, and i will check serial communication using my second board and an sd running the same issue i had on the emmc version.\n \n\n\n  \n \n\n\n and don't be condescendant, i am a 50 years old it coder, since i am 11. i checked your link after i sent the answer, and what i provided is important.\n \n\n\n if users never come here to tell what's wrong, would you be able to find all issues by yourself ?\n \n\n\n  \n \n\n\n  \n \n\n\n  \n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "this project is supported only with 1/1000 of needed resources. it is not possible to fix all issues you find. not even close. people doesn't know what is our work or what not and there are \"1000 people\" before you asked for something. we don't know if that is a problem of our work or just something in 3rd party part.\n \n \n it is impossible to diagnose troubles without logs. i am sure we agree on that, but since this support is paid from our pocket, dealing with you is my direct expense, we choose what you need to provide or we pull out our scarce resource to problems where our time is respected. i need to see bigger picture then what you are giving me.\n \n \n support is not granted, but only our good will. currently i don't know if this is our problem or problem made by you or some 3rd party software. i can't afford to spent a day findiong that out. not possible. the moment i found out, its not our problem, i tune myself out in any case.\n \n\n\n\n\n\n  \n \n\n\n likewise.\n \n", "name": "", "is_accepted": false }, { "text": "so i made progress\n \n\n\n serial is working ont ttys2\n \n\n\n i mounted the sd card not booting as usb media.\n \n\n\n  \n \n\n\n i have an error message saying :\n \n\n\n ** file not found /boot/dtb/rk3288-tinker-s.dtb **\n \n\n\n  \n \n\n\n in the dtb folder, i have no rk3288-tinker-s.dtb  file\n \n\n\n i only have : rk3288-tinker.dtb\n \n\n\n  \n \n\n\n on a working 5.9.14 kernal armbian, i have in dtb folder :\n \n\n\n -rwxr-xr-x 1 root root 55821 déc.  11 22:00 rk3288-tinker-s.dtb\n \n\n\n  \n \n\n\n on a working 4.4.213, on which i did not do an apt-get upgrade i have :\n \n\n\n  \n \n\n\n -rw-r--r-- 1 root root 70323 dec 11 21:57 rk3288-tinker.dtb\n \n\n\n and no -s\n \n\n\n  \n \n\n\n command load ${devtype} ${devnum} ${fdt\\_addr\\_r} ${prefix}dtb/${fdtfile} in boot.cmd might be the issue :\n \n\n\n  \n \n\n\n it seems that \"apt-get upgraded 4.4.13 kernel\" finds my board to be a tinker-s, even it is not really a tinker-s\n \n\n\n the tinker i am testing on is not a tinker-s, no emmcs on it.\n \n\n\n and the working 'not apt-get upgraded' 4.4.13 is a tinker-s but has only rk3288-tinker.dtb and is booting fine.\n \n\n\n  \n \n\n\n copying rk3288-tinker.dtb to rk3288-tinker-s.dtb fixed the issue.\n \n\n\n  \n \n\n\n and regarding third party software ,  i have none, i am running python scripts i wrote on this armbian device. and node.js running  javascript. nothing that goes into u-boot\n \n\n\n  \n \n\n\n  \n \n\n\n complete bootup text is :\n \n\n\n  \n \n\n\n u-boot 2018.11-armbian (may 06 2021 - 19:47:58 +0000)\n \n\n\n model: tinker-rk3288 \n dram:  2 gib \n mmc:   dwmmc@ff0c0000: 1, dwmmc@ff0f0000: 0 \n loading environment from ext4... card did not respond to voltage select! \n in:    serial \n out:   serial \n err:   serial \n model: tinker-rk3288 \n net:   eth0: ethernet@ff290000 \n hit any key to stop autoboot:  0 \n switch to partitions #0, ok \n mmc1 is current device \n scanning mmc 1:1... \n found u-boot script /boot/boot.scr \n 3395 bytes read in 2 ms (1.6 mib/s) \n ## executing script at 00000000 \n boot script loaded from mmc 1 \n 210 bytes read in 0 ms \n 7233242 bytes read in 319 ms (21.6 mib/s) \n 8580280 bytes read in 378 ms (21.6 mib/s) \n ** file not found /boot/dtb/rk3288-tinker-s.dtb ** \n libfdt fdt\\_check\\_header(): fdt\\_err\\_badmagic \n no fdt memory address configured. please configure \n the fdt address via \"fdt addr <address>\" command. \n aborting! \n 286 bytes read in 3 ms (92.8 kib/s) \n applying kernel provided dt overlay rockchip-i2c1.dtbo \n no fdt memory address configured. please configure \n the fdt address via \"fdt addr <address>\" command. \n aborting! \n 286 bytes read in 0 ms \n applying kernel provided dt overlay rockchip-i2c4.dtbo \n no fdt memory address configured. please configure \n the fdt address via \"fdt addr <address>\" command. \n aborting! \n 311 bytes read in 1 ms (303.7 kib/s) \n applying kernel provided dt overlay rockchip-spi2.dtbo \n no fdt memory address configured. please configure \n the fdt address via \"fdt addr <address>\" command. \n aborting! \n 537 bytes read in 2 ms (261.7 kib/s) \n applying kernel provided dt overlay rockchip-spidev2.dtbo \n no fdt memory address configured. please configure \n the fdt address via \"fdt addr <address>\" command. \n aborting! \n 287 bytes read in 1 ms (280.3 kib/s) \n applying kernel provided dt overlay rockchip-uart1.dtbo \n no fdt memory address configured. please configure \n the fdt address via \"fdt addr <address>\" command. \n aborting! \n 287 bytes read in 1 ms (280.3 kib/s) \n applying kernel provided dt overlay rockchip-uart2.dtbo \n no fdt memory address configured. please configure \n the fdt address via \"fdt addr <address>\" command. \n aborting! \n error applying dt overlays, restoring original dt \n ** file not found /boot/dtb/rk3288-tinker-s.dtb ** \n ## loading init ramdisk from legacy image at 21000000 ... \n    image name:   uinitrd \n    image type:   arm linux ramdisk image (gzip compressed) \n    data size:    7233178 bytes = 6.9 mib \n    load address: 00000000 \n    entry point:  00000000 \n    verifying checksum ... ok \n error: did not find a cmdline flattened device tree \n could not find a valid device tree \n script failed: continuing... \n starting usb... \n usb0:   usb1:   scanning bus 0\n \n\n\n  \n \n\n\n  \n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "you have perhaps jumped between legacy and modern kernels?\n \n", "name": "", "is_accepted": false }, { "text": "i have 2 tinkerboard, one s and one not s.\n \n\n\n i have several sd cards with 4.4.213 and 5.9.14\n \n\n\n  \n \n\n\n  \n \n\n\n how could i have done that ? you mean upgrading to 5.9.14 and downgrading to 4.4.213 ?\n \n\n\n i am not able to that\n \n\n\n i had issues with a small lcd panel with 5.9.14.\n \n\n\n so i made a lot of tests with 5.9.14 but never managed to have it work fine.\n \n\n\n so i reversed back to 4.4.213\n \n\n\n but i only download ambian images, write them to sd or emmc, and then apt-get upgrade them.\n \n\n\n i am not good enough on linux kernel to try to make any change on them or something a bit 'clever'\n \n\n\n  \n \n\n\n and how could my current working 4.4.213 version, just applying a apt-get upgrade, got some 5.9.14 update for u-boot ?\n \n\n\n  \n \n\n\n what i find to be installed as u-boot packages before apt-get update are :\n \n\n\n linux-u-boot-tinkerboard-legacy/bionic,now 20.11.3 armhf [installed,upgradable to: 21.05.1] \n u-boot-tools/now 2019.07+dfsg-1ubuntu4~18.04.1 armhf [installed,upgradable to: 2020.10+dfsg-1ubuntu0~18.04.2]\n \n\n\n  \n \n\n\n and after apt-get upgrade still on 4.4.213:\n \n\n\n linux-u-boot-tinkerboard-legacy/bionic,now 21.05.1 armhf  [installé] \n u-boot-tools/bionic-updates,now 2020.10+dfsg-1ubuntu0~18.04.2 armhf  [installé]\n \n\n\n  \n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "yes. but if you haven't, its something else. trying to reason why this happened. it looks like you are missing device tree package, which comes in a separate package: linux-dtb-legacy-rockchip ... if you install that package or copy the content to your failed session, it should boot up.\n \n\n\n  \n \n\n\n tinker or tinker s can use same settings, from s model.\n \n", "name": "", "is_accepted": false }, { "text": "u-boot version 4.4213 once  updated with apt-get install tries to find the file /boot/dtb/rk3288-tinker-s.dtb. it acts as the 5.9.14 version.\n \n\n\n if i copy /boot/dtb/rk3288-tinker.dtb to /boot/dtb/rk3288-tinker.dtb , yes ,it boots\n \n\n\n  \n \n\n\n i will try another test : download current 4.4.213 version of armbian, and check it. before apt-get upgrade and after.\n \n\n\n  \n \n\n\n  \n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "i flashed file armbian\\_21.05.1\\_tinkerboard\\_buster\\_legacy\\_4.4.213\\_xfce\\_desktop.img.xz to sd\n \n\n\n i booted and followed boot log through serial , log above\n \n\n\n  \n \n\n\n i got the error : ** file not found /boot/dtb/rk3288-tinker-s.dtb **\n \n\n\n  \n \n\n\n so i get to the conclusion that the current 4.4.213 build for tinkerboard is broken.\n \n\n\n do you agree ?\n \n\n\n  \n \n\n\n ----------------------------------------------------------------------------------------------------------\n \n\n\n  \n \n\n\n  \n \n\n\n  \n \n\n\n u-boot 2018.11-armbian (may 06 2021 - 19:47:58 +0000)\n \n\n\n model: tinker-rk3288 \n dram:  2 gib \n mmc:   dwmmc@ff0c0000: 1, dwmmc@ff0f0000: 0 \n loading environment from ext4... card did not respond to voltage select! \n in:    serial \n out:   serial \n err:   serial \n model: tinker-rk3288 \n net:   eth0: ethernet@ff290000 \n hit any key to stop autoboot:  0 \n switch to partitions #0, ok \n mmc1 is current device \n scanning mmc 1:1... \n found u-boot script /boot/boot.scr \n 3395 bytes read in 1 ms (3.2 mib/s) \n ## executing script at 00000000 \n boot script loaded from mmc 1 \n 161 bytes read in 1 ms (157.2 kib/s) \n 5829234 bytes read in 2450 ms (2.3 mib/s)\n \n\n\n 8580280 bytes read in 3588 ms (2.3 mib/s) \n ** file not found /boot/dtb/rk3288-tinker-s.dtb ** \n libfdt fdt\\_check\\_header(): fdt\\_err\\_badmagic \n no fdt memory address configured. please configure \n the fdt address via \"fdt addr <address>\" command. \n aborting! \n 286 bytes read in 1 ms (279.3 kib/s) \n applying kernel provided dt overlay rockchip-i2c1.dtbo \n no fdt memory address configured. please configure \n the fdt address via \"fdt addr <address>\" command. \n aborting! \n 286 bytes read in 1 ms (279.3 kib/s) \n applying kernel provided dt overlay rockchip-i2c4.dtbo \n no fdt memory address configured. please configure \n the fdt address via \"fdt addr <address>\" command. \n aborting! \n 311 bytes read in 1 ms (303.7 kib/s) \n applying kernel provided dt overlay rockchip-spi2.dtbo \n no fdt memory address configured. please configure \n the fdt address via \"fdt addr <address>\" command. \n aborting! \n 537 bytes read in 2 ms (261.7 kib/s) \n applying kernel provided dt overlay rockchip-spidev2.dtbo \n no fdt memory address configured. please configure \n the fdt address via \"fdt addr <address>\" command. \n aborting! \n 287 bytes read in 1 ms (280.3 kib/s) \n applying kernel provided dt overlay rockchip-uart1.dtbo \n no fdt memory address configured. please configure \n the fdt address via \"fdt addr <address>\" command. \n aborting! \n 287 bytes read in 1 ms (280.3 kib/s) \n applying kernel provided dt overlay rockchip-uart2.dtbo \n no fdt memory address configured. please configure \n the fdt address via \"fdt addr <address>\" command. \n aborting! \n error applying dt overlays, restoring original dt \n ** file not found /boot/dtb/rk3288-tinker-s.dtb ** \n ## loading init ramdisk from legacy image at 21000000 ... \n    image name:   uinitrd \n    image type:   arm linux ramdisk image (gzip compressed) \n    data size:    5829170 bytes = 5.6 mib \n    load address: 00000000 \n    entry point:  00000000 \n    verifying checksum ... ok \n error: did not find a cmdline flattened device tree \n could not find a valid device tree \n script failed: continuing... \n starting usb... \n usb0:   usb1:   scanning bus 0 for devices... cannot reset port 1!? \n cannot reset port 3!? \n 5 usb device(s) found \n scanning bus 1 for devices... 1 usb device(s) found \n        scanning usb for storage devices... 0 storage device(s) found\n \n\n\n device 0: unknown device \n ethernet@ff290000 waiting for phy auto negotiation to complete....... done \n speed: 1000, full duplex \n bootp broadcast 1 \n bootp broadcast 2 \n *** unhandled dhcp option in offer/ack: 125 \n *** unhandled dhcp option in offer/ack: 125 \n dhcp client bound to address 192.168.1.113 (457 ms) \n *** warning: no boot file name; using 'c0a80171.img' \n using ethernet@ff290000 device \n tftp from server 192.168.1.1; our ip address is 192.168.1.113 \n filename 'c0a80171.img'. \n load address: 0x800800 \n loading: t t t t t t t t t t \n retry count exceeded; starting again \n missing environment variable: pxeuuid \n missing environment variable: bootfile \n retrieving file: pxelinux.cfg/01-2c-4d-54-42-b1-16 \n speed: 1000, full duplex \n using ethernet@ff290000 device \n tftp from server 192.168.1.1; our ip address is 192.168.1.113 \n filename 'pxelinux.cfg/01-2c-4d-54-42-b1-16'. \n load address: 0x100000 \n loading: t t t\n \n\n\n  \n \n\n\n  \n \n", "name": "", "is_accepted": false }, { "text": "aha, i see. problem was introduced here: https://github.com/armbian/build/pull/2791 even there was a lot of testings.\n \n", "name": "", "is_accepted": false }, { "text": "ok, thanks, i will follow the next steps on your link \n \n", "name": "", "is_accepted": false } ]

[ { "text": "traffic ticket practice is a specialty practice. traffic ticket lawyers do not exist in small towns or rural areas because there is simply not enough business to support such a practice. thus, they only exist in larger urban areas.\r\nlike any profession, the more one limits their expertise to a certain area, the more competent they should be in that area.\r\nit is impossible for the average non-lawyer or lawyer to get up to speed in the intricacies of traffic ticket law and procedure for the occasional ticket.\r\ntraffic lawyers get cases dismissed for reasons other than whether you are innocent. that is why the good ones get good reviews. you do not have to know anything more than how and when to get to court and how to dress. and we will give you this information, too.\r\ntraffic lawyers take the worry out of getting the ticket in the first place, and in going to court. you will have some one trained and knowledgeable speaking and negotiating on your behalf.\r\nnot every case gets dismissed without any court costs. but many do, depending on the particular court, the particular prosecutor, the particular judge, the particular police officer, and the skills of your ticket attorney. over a lifetime of driving, clients tend to stick with their traffic lawyer for a reason. in the long run, the same money and time.", "name": "", "is_accepted": true }, { "text": "traffic ticket practice is a specialty practice. traffic ticket lawyers do not exist in small towns or rural areas because there is simply not enough business to support such a practice. thus, they only exist in larger urban areas.\r\nlike any profession, the more one limits their expertise to a certain area, the more competent they should be in that area.\r\nit is impossible for the average non-lawyer or lawyer to get up to speed in the intricacies of traffic ticket law and procedure for the occasional ticket.\r\ntraffic lawyers get cases dismissed for reasons other than whether you are innocent. that is why the good ones get good reviews. you do not have to know anything more than how and when to get to court and how to dress. and we will give you this information, too.\r\ntraffic lawyers take the worry out of getting the ticket in the first place, and in going to court. you will have some one trained and knowledgeable speaking and negotiating on your behalf.\r\nnot every case gets dismissed without any court costs. but many do, depending on the particular court, the particular prosecutor, the particular judge, the particular police officer, and the skills of your ticket attorney. over a lifetime of driving, clients tend to stick with their traffic lawyer for a reason. in the long run, the same money and time.", "name": "", "is_accepted": false } ]

[ { "text": "whilst i'm sorry to hear this, yes it is possible, however it is subject to the terms of service as with everything else. specifically section 21:-\n \n\n\n \n \n\n\n\n\n you can do this yourself by going to account settings > overview > deactivate your account, or follow this link to go directly to it.\n \n\n\n please note that per the terms of service as they are laid out above, you will not be able to delete your account, you can however deactivate it or set a leave of absence, which you can do from account settings > leave of absence, or follow this link to go directly to it. \n \n\n\n either way, should you want to come back to ecchidreams - which as of right now you're more than welcome to, you will not be allowed to make a new account. you will need to re-activate your account or set it back to active. \n \n\n\n i hope that answers your question.\n \n", "name": "", "is_accepted": true } ]

[ { "text": "ши из найс энд кинд. хёр найм из роза. ши из файв ёарс олд....", "name": "", "is_accepted": false } ]

[ { "text": "                        &nbs...", "name": "", "is_accepted": false } ]

[ { "text": "они и так в настоящем времени)...", "name": "", "is_accepted": false } ]

[ { "text": "1) ( 4 целых 5/12 - 3 целых 7/18 ): 9,25 + 5/6=17/184 5/12-3 7/18=4 15/36 - 3 14/36=1 1/361 1/36: 9...", "name": "", "is_accepted": false } ]

[ { "text": "мне кстати тоже нужен ...", "name": "", "is_accepted": false } ]

[ { "text": "если это не ,то завтра сделаю все,сейчас оч спать хочется ,а пока сразу смогу ответить на первый в...", "name": "", "is_accepted": false } ]

[ { "text": "my favourite holidayмой любимый праздникmy name is alexandra, i’m thirteen years old. my favourite h...", "name": "", "is_accepted": false } ]

[ { "text": "listen and teachers never talk not about the lesson and go hard, try not to bully and not to fight. ...", "name": "", "is_accepted": false } ]

[ { "text": "точный  ответ твоего -  щипцы....", "name": "", "is_accepted": false } ]

[ { "text": "2к 6...", "name": "", "is_accepted": false } ]

[ { "text": "день является одним из самых любимых праздников в соединенных штатах. каждый четвертый четверг октя...", "name": "", "is_accepted": false } ]

[ { "text": "валфавите 26 букв: a b c d e f g h i j k l m n o p q r s t u v w x y z. значит, возьмите тетрадку 4...", "name": "", "is_accepted": false } ]

[ { "text": "are british people?...", "name": "", "is_accepted": false } ]

[ { "text": "почему твои одноклассники отсутствую на уроке ?   перевод ...", "name": "", "is_accepted": false } ]

[ { "text": "измени вопросы, используя пример....", "name": "", "is_accepted": false } ]

[ { "text": "no his you person is like...", "name": "", "is_accepted": false } ]

[ { "text": "найти разницу, сравнить две фотографии и узнать разницу...", "name": "", "is_accepted": false } ]

[ { "text": "yes , i love going to the movies with her friends , and what to answer your question exactly , only ...", "name": "", "is_accepted": false } ]

[ { "text": "i,he,she,it me, his, her we, they you, it...", "name": "", "is_accepted": false } ]

[ { "text": "dear friend, sorry for not writing for a long time i was a little bit busy. i hope you're doing well...", "name": "", "is_accepted": false } ]

[ { "text": "зе бест еа эвер так нужно...", "name": "", "is_accepted": false } ]

[ { "text": "теперь прочитайте еще раз и ответьте на вопросы....", "name": "", "is_accepted": false } ]

[ { "text": "если перевод нужен вот держи  4. читать. вот описание работы. если у вас нет подработки, помню...", "name": "", "is_accepted": false } ]

[ { "text": "заголовок(название) автор (имя автора,год) содержание  текст о основная мысль автор начинае...", "name": "", "is_accepted": false } ]

[ { "text": "хай тед! найс ту мит ю хай лоу! найс ту мит ю хелоу,сйу! хав ар ю айм файн, лоу. енд хав ар ю?...", "name": "", "is_accepted": false } ]

[ { "text": "патрик, даниэль софи и tamsin и завершили факты файлы о своих странах и городах....", "name": "", "is_accepted": false } ]

[ { "text": "да уж не смогу.....", "name": "", "is_accepted": false } ]

[ { "text": "there is not a way to do this simply within tc. however, you can do this from your file manager.\n\nyou need to close tc\n\nthen locate the translationcore folder on your laptop (should be in your home directory)\n\nwithin that is a projects folder and an archive folder.\n\nif there is no archive fold…", "name": "", "is_accepted": true } ]

[ { "text": "the documentation for ts is at <https://ts-info.readthedocs.io/en/latest/index.html>.\n\ndirect link to the desktop (windows, mac, linux) documentation is here: <https://ts-info.readthedocs.io/en/latest/desktop.html>.\n\nthe android docs here: <https://ts-info.readthedocs.io/en/latest/tablet.html>.", "name": "", "is_accepted": true } ]

[ { "text": "\nwe are going to talk about migrating from oracle to postgresql using ora2pg.After installing ora2pg tool, we will see how to configure and to run it to migrate our data. We are using an oracle 12C database and a postgresql edb 9.6, The server is runing on OEL 7.2,The oracle database and the postgresql server are running on the same server. \n\n \n\nwe are going to talk about migrating from oracle to postgresql using ora2pg open source tool \n\nbefore migrating you need to know little bit knowledge of functions,procedure,trigger and  [Difference between oracle vs postgresql data types](http://www.tutorialdba.com/2018/04/oracle-vs-postgresql-data-types.html)\n\n\n\n**See more details :** <https://www.tutorialdba.com/2018/04/migrating-from-oracle-to-postgresql.html>\n \n\n\n\n\n", "name": "", "is_accepted": true } ]

[ { "text": "\nThis script can be used to check on mariaDB, apache2, or whatever service you want. This is not meant to be a SOLUTION to services that are crashing, but rather a notification and a temporary restart until you can solve the real issue.\n\n\nThe script will check the status of each service. If the service is stopped, it tries to restart the service. If the service starts, it sends you an email saying the service stopped but was restarted.\n\n\nIf the service does not start for some reason, it sends you an email telling you it was not started.\n\n\nAfter that, it will continue to try and start, but not send any more emails until the service is finally started.\n\n\nNOTE*: This script should be run as your root user, so it would be added to the crontab like so:\n\n\n1. put it into your scripts folder\n2. set your email address\n3. set the services you want to keep an eye on (by default it has MariaDB and apache2..you can add or take away whatever you need)\n4. save your changes\n5. create a cronjob as root (sudo crontab -e) and add something like this, which runs every minute (adjust to your needs):\n\n\n\n```\n#check on services\n*/1 * * * * sh /root/script/dbalert.sh\n```\n\n\n```\n################### DOWN DB server######################\n#!/bin/bash\n#ver. 2\n\n##this script will check whatever services\n##you want to keep an eye on\n##if that service is not running\n##it will (try to) start the service and send\n##an email to you\n\n##set your email address\nEMAIL=\"[email protected]\"\n\n##list your services you want to check\n##you can add as many as you like\nSERVICES=('mysql')\n\n#### DO NOT CHANGE anything BELOW ####\n\n\n for i in \"${SERVICES[@]}\"\n do\n ###IF SERVICE IS NOT RUNNING####\nif ([[ \"$(service $i status)\" =~ \"not running\" ]] || [[ \"$(service $i status)\" =~ \"is stopped\" ]] || [[ $\"$(service $i status)\" =~ \"stop/waiting\" ]])\n\n then\n ##TRY TO RESTART THAT SERVICE###\n service $i start\n\n ##IF RESTART WORKED###\nif ([[ \"$(service $i status)\" =~ \"MariaDB running\" ]] || [[ \"$(service $i status)\" =~ \"is started\" ]] || [[ $\"$(service $i status)\" =~ \"start\" ]])\nthen\n ##SEND AN EMAIL###\n MESSAGE=\"$(tail -15 /var/lib/mysql/publishman.com.err)\"\n SUBJECT=\"MariaDB down But restarted Successfully on $(date) \"\n echo -e \" LOGS : \\n$MESSAGE \" | mail -s \"$SUBJECT\" \"$EMAIL\"\n else\n\n ##IF RESTART DID NOT WORK SEND A DIFFERENT EMAIL###\n MESSAGE=\"$(tail -15 /var/lib/mysql/publishman.com.err)\"\n SUBJECT=\"MariaDB down, Restarted did not work on $(date) \"\n echo -e \" LOGS : \\n$MESSAGE . \\n>>>>> Script tried to restart but it did not work\" | mail -s \"$SUBJECT\" \"$EMAIL\"\n\n fi\n fi\n\ndone\n\n ################### DOWN APACHE server######################\n#!/bin/bash\n#ver. 2\n\n##this script will check whatever services\n##you want to keep an eye on\n##if that service is not running\n##it will (try to) start the service and send\n##an email to you\n\n##set your email address\nEMAILA=\"[email protected]\"\n\n##list your services you want to check\n##you can add as many as you like\nSERVICESA=('httpd')\n\n#### DO NOT CHANGE anything BELOW ####\n\n\n for a in \"${SERVICESA[@]}\"\n do\n ###IF SERVICE IS NOT RUNNING####\nif ([[ \"$(service $a status)\" =~ \"not running\" ]] || [[ \"$(service $a status)\" =~ \"is stopped\" ]] || [[ $\"$(service $a status)\" =~ \"stop/waiting\" ]])\n\n#if [[ \"$(service $a status)\" =~ \"$a is stopped\" ]]\n\n then\n ##TRY TO RESTART THAT SERVICE###\n service $a start\n\n ##IF RESTART WORKED###\n#if [[ \"$(service $a status)\" =~ \"is running\" ]]\nif ([[ \"$(service $a status)\" =~ \"is running\" ]] || [[ \"$(service $a status)\" =~ \"is started\" ]] || [[ $\"$(service $a status)\" =~ \"start\" ]])\n then\n ##SEND AN EMAIL###\n MESSAGEA=\"$(tail -15 /var/log/apache2/error\\_log)\"\n SUBJECTA=\"APACHE SERVER down But restarted successfully on $(date) \"\n echo -e \" LOGS : \\n$MESSAGEA \" | mail -s \"$SUBJECTA\" \"$EMAILA\"\n else\n\n ##IF RESTART DID NOT WORK SEND A DIFFERENT EMAIL###\n MESSAGEA=\"$(tail -15 /var/log/apache2/error\\_log)\"\n SUBJECTA=\"APACHE SERVER down restarted did not work on $(date) \"\n echo -e \" LOGS: \\n$MESSAGEA . \\n>>>>> Script tried to restart but it did not work\" | mail -s \"$SUBJECTA\" \"$EMAILA\"\n\n fi\n fi\ndone\n\n```\n\n \n\n\n", "name": "", "is_accepted": false } ]

[ { "text": "\n \n\n\nIn this tutorial I will explained how to take logical backup from PostgreSQL Slave server here i used PostgreSQL 10.3 and redhat 7.3 plateform.\n\n\n\n```\n **POSTGRESQL 9.6** **POSTGRESQL 10** \nselect pg\\_xlog\\_replay\\_pause(); select pg\\_wal\\_replay\\_pause(); #Pauses recovery immediately\nselect pg\\_is\\_xlog\\_replay\\_paused(): select pg\\_is\\_wal\\_replay\\_paused(); #True if recovery is paused.\nselect pg\\_xlog\\_replay\\_resume(); select pg\\_wal\\_replay\\_resume(); # Restarts recovery if it was paused\n\n```\n\n \n\n\n**Step 1: issue the pg\\_wal\\_replay\\_pause() or pg\\_xlog\\_replay\\_pause()  function on slave** \n\n**select pg\\_wal\\_replay\\_pause();** \n\n \n\n**Step 2:insert some data into master or restore the data then check the slave whether replicated or not**\n\n\n\n```\n**On master:**\ncreate table t3(id int,name varchar);\nCREATE TABLE\n\n**On slave:**\npostgres=# \\dt t3\nDid not find any relation named \"t3\".\n```\n\n**Step 3:pg\\_start\\_backup(\"label\") is not possible on slave\\_2 but you can use pg\\_dump,pg\\_dumpall**\n\n\n\n```\n**On slave:**\nselect pg\\_start\\_backup('label');\nERROR: recovery is in progress\nHINT: WAL control functions cannot be executed during recovery.\n\n**TAKING BACKUP FROM SLAVE:**\ncd /usr/bin/pg\\_dump -d postgres -f /BACKUP/nijam.dump\n```\n\n**AFTER BACKUP RESUME THE STREAMING REPLICATION THEN CHECK THE TABLE T3 WHETHER REPLICATED OR NOT**\n\n\n\n```\npostgres=# select pg\\_wal\\_replay\\_resume();\n pg\\_wal\\_replay\\_resume \n----------------------\n \n(1 row)\n\npostgres=# \\dt\n List of relations\n Schema | Name | Type | Owner \n--------+------+-------+----------\n public | t | table | postgres\n public | t1 | table | postgres\n public | t3 | table | postgres\n```\n\n \n\n\nMore Info:<https://www.tutorialdba.com/2017/11/oracle-and-postgresql-dba-related.html>\n\n\n", "name": "", "is_accepted": false } ]

[ { "text": "I think here pganalyze tools will helpful to take report like awr oracle", "name": "", "is_accepted": false } ]

[ { "text": "\nYou can drop domain data type using following command\n\n\n\n```\npostgres=# drop domain us\\_postal\\_code;\nERROR: cannot drop type us\\_postal\\_code because other objects depend on it\nDETAIL: table us\\_snail\\_addy column postal depends on type us\\_postal\\_code\nHINT: Use DROP ... CASCADE to drop the dependent objects too.\n\npostgres=# drop domain us\\_postal\\_code casecade;\nERROR: syntax error at or near \"casecade\"\nLINE 1: drop domain us\\_postal\\_code casecade;\n```\n\n\n```\npostgres=# drop domain us\\_postal\\_code cascade; \nNOTICE: drop cascades to table us\\_snail\\_addy column postal\nDROP DOMAIN\n```\n\n", "name": "", "is_accepted": false } ]

[ { "text": "\n--Let us take the sales table for using WHERE CLAUSE \n\n \n\n\n\n```\npostgres=# select * from sales;\n id | sales\\_info \n----+----------------------------------------------------------------------------------\n 1 | { \"customer\": \"NIJAM\", \"PRODUCTS\": {\"product\\_name\": \"choclate\",\"total\\_item\": 6}}\n 2 | { \"customer\": \"ABU\", \"PRODUCTS\": {\"product\\_name\": \"badam\",\"total\\_item\": 5}}\n 3 | { \"customer\": \"UMAR\", \"PRODUCTS\": {\"product\\_name\": \"mobile\",\"total\\_item\": 1}}\n(3 rows) \n```\n\n--To find out what are the products  bought customer UMAR I use the following query \n\n \n\n\n\n```\npostgres=# SELECT sales\\_info ->>'customer' as customer\\_name,sales\\_info ->>'PRODUCTS' ->>'product\\_name' \nas name\\_of\\_product from sales where sales\\_info ->>'customer'='UMAR';\nERROR: operator does not exist: text ->> unknown\nLINE 1: ...stomer' as customer\\_name,sales\\_info ->>'PRODUCTS' ->>'produc...\n ^\nHINT: No operator matches the given name and argument type(s). You might need to add explicit type casts. \n```\n\n**SOLUTION:**\n\n\n* FIRST TIME WE SPECIFIED sales\\_info ->>'PRODUCTS' ->>'product\\_name' SO WE NEED TO GIVE  sales\\_info ->'PRODUCTS' ->>'product\\_name'\n* ```\npostgres=# SELECT sales\\_info ->>'customer' as customer\\_name,sales\\_info ->'PRODUCTS' ->>'product\\_name' \nas name\\_of\\_product from sales where sales\\_info ->>'customer'='UMAR';\n customer\\_name | name\\_of\\_product \n---------------+-----------------\n UMAR | mobile\n(1 row) \n```\n\n\n* Defaulty FROM above example First  sales\\_info -> 'PRODUCTS'  returns  as JSON objects. And then 'PRODUCTS' ->>'product\\_name' returns all products as text.\n* when you call json nested data first you call like ->(json object key format)then Finally  you need to call ->>(text format or json object key format).\n* if you specify firstly json field as text(->>) format when calling nested node ,after that if you specify -> or ->> values  json will not know first text format(->>) value that is why it throw error.\n* JSON displayed  text format but actually json work as json object key(->) format .\n* ```\npostgres=# SELECT sales\\_info ->>'customer' as customer\\_name,sales\\_info ->'PRODUCTS' ->'product\\_name' \nas name\\_of\\_product from sales where sales\\_info ->>'customer'='UMAR';\n customer\\_name | name\\_of\\_product \n---------------+-----------------\n UMAR | \"mobile\"\n(1 row) \n```\n\n\n* HERE i specified first json object(->) format finnaly i called json object format (->) this is not a problem.\n* other wise if you specify firstly as json text format (->>) finally if you give json object format (->) or  json text format (->>) what ever it is json will not know fist values surely it will throw error.\n\n\n", "name": "", "is_accepted": false } ]

[ { "text": "\nyou can change the priority of running process owned by particular user, forr user nijam, using command:\n\n\n\n```\n# renice -n -20 -u sk\n```\n\n", "name": "", "is_accepted": false } ]

[ { "text": "\nHere we are creating array table using json data type and and also explained how to   retrieve the array data from json table and how to understand the array data. \n\n \n\n\n\n```\npostgres=# create table TAB\\_ARRAY (id INT,BOOKS json);\nCREATE TABLE \n```\n\n--Let us inserting array  values \n\n \n\n\n\n```\ninsert into tab\\_array values (1, '{\n \"book\\_name\": \"story\",\n \"book\\_id\": [\"111\", \"232\", \"353\", \"484\"] }' \n );\n\ninsert into tab\\_array values (2, '{\n \"book\\_name\": \"the king\",\n \"book\\_id\": [\"1231\", \"78\", \"7\", \"9\"] }' \n ); \n```\n\n \n\n\n--List down the tab\\_array table \n\n \n\n\n\n```\npostgres=# select * from tab\\_array;\n id | books \n----+---------------------------------------------\n 1 | { +\n | \"book\\_name\": \"story\", +\n | \"book\\_id\": [\"111\", \"232\", \"353\", \"484\"] }\n 2 | { +\n | \"book\\_name\": \"the king\", +\n | \"book\\_id\": [\"1231\", \"78\", \"7\", \"9\"] }\n(2 rows) \n```\n\n--filter the json data \n\n \n\n\n\n```\npostgres=# select id, books->'book\\_id'->>2 from tab\\_array;\n id | ?column? \n----+----------\n 1 | 353\n 2 | 7\n(2 rows)\n\npostgres=# select id, books->'book\\_id'->>0 from tab\\_array where id=1;\n id | ?column? \n----+----------\n 1 | 111\n(1 row) \n```\n\n**Note:**Array start from 0 ...N you will undestand json array below example\n\n\n**[\"111\", \"232\", \"353\", \"484\"]**     ------>array values\n\n\n**0        1         2        3**       ------> array start from 0...3\n\n\n**from above notes**\n\n\nif u give  where id=1 and books->'book\\_id'->>1 means it return 232\n\n\nif u give  where id=1 and books->'book\\_id'->>2 means it return 353\n\n\nif u give  where id=1 and books->'book\\_id'->>3 means it return 484\n\n\nif u give  where id=1 and books->'book\\_id'->>0 means it return 111\n\n\n \n\n\n", "name": "", "is_accepted": false } ]

[ { "text": "\nAugust 2008 proved towards be a enormous thirty day period inside of the record of the Eco-friendly Bay Packers and an unreconcilable thirty day period concerning the franchise and their mythical quarterback Brett Favre. Just after retiring and unretiring, Favre eventually manufactured a vacation up toward Eco-friendly Bay towards pay a visit to the employees. Pleasure amongst followers more than a confident option hardly ever arrived in the direction of fruition - as an alternative they have been make any difference in direction of open up discussion in between possibly facets within just the media that just tarnished the partnership further more [Kingsley Keke Jersey](https://www.gbfanstore.com/Kingsley_Keke_Jersey-63).In times, Favre was traded out of Inexperienced Bay and the Aaron Rodgers generation started off.As the fresh saga involving the Packers and Rodgers proceeds upon this summertime, the expect is that this August, looming significantly less than 2 weeks absent, will be just one remembered for completely option scenarios. Nonetheless, the background driving Favre introduction back again within Eco-friendly Bay proves that interaction in between the 2 aspects ought to stay as private as likely.Even though silence, specially upon Rodgersfacet, consists of been annoying for admirers trying to find alternatives this offseason, it incorporates been a as a substitute commendable characteristic of both equally events hence much [Simon Stepaniak Jersey](https://www.gbfanstore.com/Simon_Stepaniak_Jersey-105). Upon draft working day, Rodgers was radio quiet the moment the reaking newswas unveiled, and even as soon as pressed via Kenny Mayne upon ESPN, he remained politically acceptable within his voicing of dissent. Whilst in general supervisor Brian Gutekunst incorporates been the thought make any difference of Rodgersdispleasure [Aaron Rodgers Jersey](https://www.gbfanstore.com/Aaron_Rodgers_Jersey-41), there had been no names and no exclusive circumstances publicly spelled out. By means of maintaining it this direction, Rodgers includes still left his window towards return open up with out unrepairable harm upon the back again conclusion.The Packers, equally, comprise been been very careful toward confess their individual blunders within former conversation with Rodgers although currently being steadfast within just their general public demand from customers toward deliver him back again into the fold <https://www.gbfanstore.com/Kurt_Benkert_Jersey-168>. They incorporate additionally uncovered their visits in direction of watch Rodgers during the offseason without having divulging the information and facts. Though the staff can be internally discouraged by way of the circumstance, the full small business should stroll a great line with its phrases and phrasings with the drive. Regrettably, Mark Murphy not long ago proven that line with suggestions in excess of the rift dividing the supporter foundation in just a column, though echoing the sentiment that emotions need to be held toward them selves within just the exact same breath:e are operating in direction of dedication the scenario and fully grasp that the much less equally aspects say publicly, the improved.he make any difference with this is that Murphy really should heed his personalized guidance. In just the final 7 days, Murphy ongoing down a slippery slope, speaking to Rodgers sophisticated fellaand it will be crucial that All those model of feedback stop as performing exercises camp nears and the problem methods an unavoidable tipping issue. Transferring again in just period, it was a deficiency of take care of that drove a wedge among Inexperienced Bay and Favre over that exact year.Inside a Refreshing York Moments posting recapping the narrative within legitimate-season that fateful August, a few of responses towards both of those aspects with regards to interaction stood out.hey have to have toward notice if I focused, nonetheless I need to have towards recognize if theye 100 % focused. The trouble is that there been a great deal of destruction performed, and I can ignore it. Things incorporates been mentioned, reviews planted, that simply just aren accurate. Can I just take more than all that? I question it. Therefore they can say they welcome me back again however, occur upon, the route theye handled me tells oneself the fact. They don need me back again, hence let stream upon.~ Brett Favrehe he-reported, she-claimed issue undoubtedly took a toll upon Brett, there no question more than it. We both equally agreed upon this: We both of those motivation elements experienced been dealt with in another way. Yet that the destination that wee inside of.~ Mike McCarthyWhile the Packers and Rodgers might or may perhaps not be in a position in the direction of occur towards an settlement that retains the All-Specialist within just a inexperienced and gold uniform [Eric Stokes Jersey](https://www.gbfanstore.com/Eric_Stokes_Jersey-154), Those estimates give a lesson that believe in, primarily based intensely upon interaction, will shift a prolonged path in just discovering a approach. Equally aspects come across by themselves inside an eerily equivalent point as the one particular with Favre within wanting for the motivation point of the other and it would be clever for the shut-doorway discussions in the direction of dwell that direction. Certainly inside of the scenario of Favre, phrases might not be unsaid and routines may possibly not be undone, in particular if the workers alone was in direction of flow in advance devoid of a year-very long, annoying distraction.Potentially an aged adage effectively sums up the circumstance for both of those aspects within discovering a joyful finishing: if oneself don include just about anything positive in the direction of say, don say it at all. Even though each individual occasion contains been predominantly worthwhile in just carrying out thus therefore considerably, the accurate check is still in the direction of appear as the summer season arrives in direction of a end.\n\n\n", "name": "", "is_accepted": false } ]

[ { "text": "This command is used for enabling compilation of all libraries and applications. This process generally slows down the system and it also increases the binary file size. Debugging symbols are present which can assist developers in noticing bugs and problems associated with their script.", "name": "", "is_accepted": false } ]

[ { "text": "Check the any killing idle script are running or not ,if Postgresql 9.6 means check it any idle\\_in\\_transaction are set \n\nIf set means disable that if idle connection is running means change the time", "name": "", "is_accepted": false } ]

[ { "text": "\n1. Download the mySQL Software from below link.\n\n\n<https://dev.mysql.com/downloads/mysql/5.7.html#downloads>\n\n\n2. Download & extract the bundle mysql tart file .\n\n\n\n\n\n3. Installing RPMs.\n\n\n\n```\ntar -xvf mysql-5.7.27-1.sles12.x86\\_64.rpm-bundle.tar\n\nrpm -ivh mysql-community-client-5.7.27-1.sles12.x86\\_64.rpm --nodeps\nrpm -ivh mysql-community-common-5.7.27-1.sles12.x86\\_64.rpm --nodeps\nrpm -ivh mysql-community-devel-5.7.27-1.sles12.x86\\_64.rpm --nodeps\nrpm -ivh mysql-community-embedded-5.7.27-1.sles12.x86\\_64.rpm --nodeps\nrpm -ivh mysql-community-embedded-devel-5.7.27-1.sles12.x86\\_64.rpm --nodeps\nrpm -ivh mysql-community-libs-5.7.27-1.sles12.x86\\_64.rpm --nodeps\nrpm -ivh mysql-community-server-5.7.27-1.sles12.x86\\_64.rpm --nodeps\nrpm -ivh mysql-community-test-5.7.27-1.sles12.x86\\_64.rpm --nodeps\n```\n\n4. Start the MySQL server with the following command:\n\n\n\n```\nsudo service mysql start\n```\n\nYou can check the status of the MySQL server with the following command:\n\n\n\n```\nsudo service mysql status\n```\n\n \n\n\n5. Getting  default MySQL root password .\n\n\n*MySQL Server Initialization (for MySQL 8.0 and later):* When the server is started for the first time, the server is initialized, and the following happens (if the data directory of the server is empty when the initialization process begins):\n\n\n* The SSL certificate and key files are generated in the data directory.\n* The [validate\\_password plugin](https://dev.mysql.com/doc/refman/8.0/en/validate-password.html) is installed and enabled.\n* A superuser account `'root'@'localhost'` is created. A password for the superuser is set and stored in the error log file. To reveal it, use the following command:\n\n\n\n```\n# sudo grep 'temporary password' /var/log/mysql/mysqld.log\n\n2019-08-05T12:59:29.208767Z 1 [Note] A temporary password is generated for root@localhost: 20Tgcf;ZAB)! \n```\n\n6. Change the root password as soon as possible by logging in with the generated, temporary password and set a custom password for the superuser account:\n\n\n\n```\n# mysql -uroot -p\n```\n\n\n```\nmysql> ALTER USER 'root'@'localhost' IDENTIFIED BY 'MyNewPass4!';\n```\n\n7. Securing the MySQL Installation (for MySQL 5.6 only)\n\n\nThe program **mysql\\_secure\\_installation** allows you to perform important operations like setting the root password, removing anonymous users, and so on. Always run it to secure your MySQL installation:\n\n\n\n```\n# mysql\\_secure\\_installation\n```\n\nIt is important to remember the root password you set. See [**mysql\\_secure\\_installation** — Improve MySQL Installation Security](https://dev.mysql.com/doc/refman/8.0/en/mysql-secure-installation.html) for details.\n\n\nDo not run **mysql\\_secure\\_installation** after an installation of MySQL 5.7 or 8.0, as the function of the program has already been performed by the SLES repository installation.\n\n\n \n\n\n \n\n\n \n\n\n \n\n\n \n\n\n", "name": "", "is_accepted": false } ]

[ { "text": "Some very useful queries for Oracle DBA \n\n#database #oracledba \n\n \n\n1.How to identify who loged in? \n\nAnswer: \n\nselect username, osuser,program,module,machine, \n\nterminal,process, \n\nto\\_char(logon\\_time, 'YYYY-MM-DD HH24:MI:SS') as logon\\_time, \n\nstatus, \n\nCASE status when 'ACTIVE' THEN NULL \n\n            ELSE last\\_call\\_et \n\nEND as idle\\_time \n\nfrom v$session \n\nwhere type='USER' \n\norder by status; \n\n \n\n2.What all sessions are consuming resources? \n\nAnswer: \n\nselect s.sid,s.username,s.osuser, \n\nto\\_char(sm.begin\\_time,'HH24:MI:ss') as interval\\_start, \n\nto\\_char(sm.end\\_time, 'HH24:MI:ss') as interval\\_end, \n\ns.machine,s.process,s.program,s.module, \n\nsm.cpu,sm.pga\\_memory,sm.logical\\_reads,sm.physical\\_reads, \n\nsm.hard\\_parses,sm.soft\\_parses, \n\ns.logon\\_time \n\nfrom v$session s \n\ninner join v$sessmetric sm \n\non sm.session\\_id=s.sid \n\nwhere s.type='USER' \n\norder by sm.cpu desc; \n\n \n\n3.What all statements consume Most Resources? \n\nAnswer: \n\nselect * from \n\n(select sql\\_id,sql\\_text,executions, \n\nelapsed\\_time,cpu\\_time,buffer\\_gets,disk\\_reads, \n\nelapsed\\_time / executions as avg\\_elapse\\_time, \n\ncpu\\_time / executions as avg\\_cpu\\_time, \n\nbuffer\\_gets / executions as avg\\_buffer\\_gets, \n\ndisk\\_reads / executions as avg\\_disk\\_reads \n\nfrom v$sqlstats \n\nwhere executions >0 \n\norder by elapsed\\_time / executions desc \n\n) \n\nwhere rownum <=25;", "name": "", "is_accepted": false } ]

[ { "text": "\n**Kampala International University (KIU)** founded in 2001 is a private chartered University in the Republic of Uganda. It is a member of the Association of Commonwealth Universities, the Association of Africa Universities as well as the Inter University-Council of East Africa. KIU offers a variety of programs in Health Sciences, Science and Technology, Engineering, Business and Management, Law, Humanities and Education.\n\n\n<https://kiu.ac.ug>\n\n\n", "name": "", "is_accepted": false }, { "text": "Kampala International University (KIU) founded in 2001 is a private chartered University in the Republic of Uganda. It is a member of the Association of Commonwealth Universities, the Association of Africa Universities as well as the Inter University-Council of East Africa. KIU offers a variety of programs in Health Sciences, Science and Technology, Engineering, Business and Management, Law, Humanities and Education.", "name": "", "is_accepted": false }, { "text": "\nKampala International University (KIU) founded in 2001 is a private chartered University in the Republic of Uganda. It is a member of the Association of Commonwealth Universities, the Association of Africa Universities as well as the Inter University-Council of East Africa.\n\n\n<https://kiu.ac.ug>\n\n\n", "name": "", "is_accepted": false } ]

[ { "text": "\nFollowing simple Two steps you can connect the postgresql database automatically without any password prompt\n\n\n**Step 1.** create the bash\\_profile:\n\n\n\n```\n[[email protected]]# cat .bash\\_profile\nexport PGPASSWORD=\"tcs@12345\"\nexport PGHOST=\"10.0.1.109\"\nexport PGUSER=\"enterprisedb\"\nexport PGPORT=\"5444\"\n/opt/edb/as9.6/bin/psql -d edb\n```\n\n**Step 2.** Run the bash\\_profile by using sh or . you will see the following postgres sql prompt\n\n\n\n```\n[[email protected]]# sh .bash\\_profile\npsql.bin (9.6.2.7)\nType \"help\" for help.\n\nedb=# \\dt\n List of relations\n Schema | Name | Type | Owner\n--------+---------+-------+--------------\n public | dept | table | enterprisedb\n public | emp | table | enterprisedb\n public | jobhist | table | enterprisedb\n public | test | table | enterprisedb\n(4 rows)\n\n```\n\n \n\n\n", "name": "", "is_accepted": false } ]

[ { "text": "\nChange the password for a role:\n\n\n\n```\nALTER ROLE daria WITH PASSWORD 'passwd123';\n\n```\n\nChange a password expiration date:\n\n\n\n```\nALTER ROLE scott VALID UNTIL 'May 4 12:00:00 2015 +1';\n\n```\n\nMake a password valid forever:\n\n\n\n```\nALTER ROLE luke VALID UNTIL 'infinity';\n\n```\n\nGive a role the ability to create other roles and new databases:\n\n\n\n```\nALTER ROLE joelle CREATEROLE CREATEDB;\n\n```\n\nGive a role a non-default setting of the `maintenance_work_mem` parameter:\n\n\n\n```\nALTER ROLE admin SET maintenance_work_mem = 100000;\n\n```\n\nAssign a role to a resource queue:\n\n\n\n```\nALTER ROLE sammy RESOURCE QUEUE poweruser;\n\n```\n\nGive a role permission to create writable external tables:\n\n\n\n```\nALTER ROLE load CREATEEXTTABLE (type='writable');\n\n```\n\nAlter a role so it does not allow login access on Sundays:\n\n\n\n```\nALTER ROLE user3 DENY DAY 'Sunday';\n\n```\n\nAlter a role to remove the constraint that does not allow login access on Sundays:\n\n\n\n```\nALTER ROLE user3 DROP DENY FOR DAY 'Sunday';\n```\n\n", "name": "", "is_accepted": true } ]

[ { "text": "It will come​ around 13-17 GB", "name": "", "is_accepted": false } ]

[ { "text": "\nThis issue is fixed by upgrading to below mentioned point releases and restarting your PostgreSQL server.\n\n\n**Below are the new point releases to fix the vulnerability.**\n\n\nPostgreSQL version 9.6.15\n\n\nPostgreSQL version 10.10\n\n\nPostgreSQL version 11.5\n\n\n", "name": "", "is_accepted": false } ]

[ { "text": "./initdb -D /new\\_path \n\nchange port number  , it should not been same as existing port number. \n\n \n\nstarting the new cluster: \n\n./pg\\_ctl -D /new\\_path -l logfile start \n\n \n\nRestoring cluster backup into the new cluster: \n\npsql -d dbname -f /path/hnfdjkhf.dmp \n\n \n\nTaking particular database backup from new cluster: \n\npg\\_dump -d dbname -f /path/dbname.dmp \n\n \n\nRestoring database backup to old cluster: \n\nexport port=old\\_port \n\npsql -c \"create database dbname\"; \n\npsql -d dbname -f /path/hnfdjkhf.dmp", "name": "", "is_accepted": false } ]

[ { "text": "Yes you need to check all logs of cluster Cssd,crs log ,Probably it generates one trace file once trace file location Open that file,If your node evicted then check all evmd CTS are ok,Cssd will take everything It will add the evicted node", "name": "", "is_accepted": false } ]

[ { "text": "\nRama:\n\n\nUse pg\\_restore  -h option to mention the ip\n\n\n\n```\nIP1/bin/Pg\\_restore -h IP2 -d Databasename -U username -f /ip1location/dump.sql\n```\n\nBefore that check the IP1 & IP2 connection establishment happened or not ?\n\n\nConfirm the destination db name & port name \n\n\n", "name": "", "is_accepted": false } ]

[ { "text": "\nGreenplum is a massive parallel processing data store, and data is distributed across segments as per the definition of the distribution strategy.\n\n\n**Greenplum Table Distribution uses the two types of distribution they are :**\n\n\n1. Hash\n2. Random.\n\n\nWhen you create or alter tables you will have to tell the system which distribution it should use. By default, Greenplum database data distribution uses the hash algorithm.\n\n\n\n\n\n \n\n\n1. **Column Oriented/Hash Distribution:** Distributes data evenly across all segment using the column specified in DISTRIBUTED BY (Column\\_Name)\n\t* See: [How Greenplum Hash Distribution Works?](https://discuss.tutorialdba.com/814/distributed-using-algorithm?show=814#q814)\n2. **Random Distribution:** Distributes data randomly across all segments using round-robin distribution. In this type of distribution, there won’t be any skew on the segments. It is specified by DISTRIBUTED RANDOMLY.\n\t* Table will never be collocated in case of random distribution. Either redistribute or broadcast operations require performing a table join.\n\t* Read: [Greenplum Data Loading Options](https://discuss.tutorialdba.com/871/greenplum-data-loading-options)\n\t* Random distribution should be used for small tables and when a Hash distribution method is not feasible due to significant data skew\n\n\nTable distribution can be modified at any given point of the time. If the table has unique key or primary key, that key is must be used to distribute the data. In case if you miss to provide the distribution key, Greenplum database uses the default strategy. By default, it distributes data on first column using hash strategy. You should avoid using default distribution as it may cause the skew.\n\n\n \n\n\n### **Choosing the Greenplum Table Distribution Key**\n\n\nConsider the following best practices when deciding on a distribution strategy:\n\n\n* Commonly used joined tables should be distributed on same key. This allows the Greenplum to perform the location operations hence increasing performance.\n* An Integer column when possible. Hash joins works better on the integers hence integer is better choice for distribution key.\n* A column that does not allow NULL, or minimum NULL values. Null values will hash to the same distribution and potentially cause skew.\n* Explicitly define a column or random distribution for all tables. Do not use the default as it may cause skew on segments.\n* You should use a single best suited column that will distribute data across all segments evenly. You should distribute data on unique or primary key columns.\n* Do not distribute on columns that will be used in the WHERE clause of a query. You should partition the data on the column that is used in WHERE clause.\n* Do not distribute on dates or timestamps. Distributing data on date or timestamp may case poor system performance.\n* The distribution key column data should contain unique values or very high cardinality.\n* If a single column cannot achieve an even distribution, use a multi-column distribution key, but no more than two columns. Additional columns in distribution require additional time in the hashing process.\n* In case if a two-column distribution key cannot achieve an even distribution of data, use a random distribution. Multi-column distribution keys in most cases require motion operations to join tables, so they offer no advantages over a random distribution.\n\n\n### **Redistribute and Broadcast Motions**\n\n\nWhen two tables are distributed on same key and that key is used in the join operation than system performs all the operations locally as required data is available within segment. Such tables are called co-located tables.\n\n\nWhenever system cannot perform the local join, then it performs either *redistribute* or *broadcast* motion to co-locate table.\n\n\n* **Redistribute Motions:** In order to perform a local join, rows must be located together on the same segment and in case if absence of which, a dynamic redistribution of the needed rows from one of the segment instance to another segment instance will be performed. This operation might be quite expensive in case of large fact tables.\n* **Broadcast Motions:** In the broadcast motion, every segment will sends the copy of table to all segment instances. Optimizer always picks only small table for broadcast motions.\n\n\n**Greenplum Table Distribution: Syntax.**\n\n\n\n```\nCREATE TABLE tablename (\nCol1 data\\_type,\nCol2 data\\_type,\nCol3 data\\_type …)\n[DISTRIBUTE BY (column\\_name)] -- Used for Hash distribution\n[DISTRIBUTED RANDOMLY] -- Used for Random distribution, distributes on round robin fashion\n```\n\n**View Greenplum Table Distribution**\n\n\nTo see the data distribution of a table’s rows, you can run a query such as:\n\n\n\n```\ntraining=# SELECT gp\\_segment\\_id, count(*) FROM table\\_name GROUP BY gp\\_segment\\_id;\n```\n\nThis query will return the number of rows on each segment.\n\n\n", "name": "", "is_accepted": false } ]

[ { "text": "\nThe MySQL logs are determined by the global variables such as:\n\n\n* [`log_error`](http://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_log_error) for the error message log;\n* [`general_log_file`](http://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_general_log_file) for the general query log file (if enabled by `general_log`);\n* [`slow_query_log_file`](http://dev.mysql.com/doc/refman/5.7/en/server-system-variables.html#sysvar_slow_query_log) for the slow query log file (if enabled by `slow_query_log`);\n\n\n**To see the settings and the logs' locations, run this shell command:**\n\n\n\n```\nmysql -se \"SHOW VARIABLES\" | grep -e log_error -e general_log -e slow_query_log\n```\n\n", "name": "", "is_accepted": false } ]

[ { "text": "\n\n```\n##list your services you want to check\n##you can add as many as you like\nSERVICES=('MySQL')\n\n#### DO NOT CHANGE anything BELOW ####\n\n\n for i in \"${SERVICES[@]}\"\n do\n ###IF SERVICE IS NOT RUNNING####\n\nif [[ \"$(service $i status)\"=~\"not\" ]]\n\n then\n ##TRY TO RESTART THAT SERVICE###\nmv /var/lib/mysql/ib\\_logfile* /tmp/\n service $i start\n\n ##IF RESTART WORKED###\nif [[ \"$(service $i status)\"=~\"$i running\" ]]\n\n then\n ##SEND AN EMAIL###\n MESSAGE=\"$(tail -10 /var/lib/mysql/vps.publishman.com.err)\"\n SUBJECT=\"$i down -but restarted- on $(hostname) $(date) \"\n echo \" $i $MESSAGE \" | mail -s \"$SUBJECT\" \"$EMAIL\"\n else\n\n ##IF RESTART DID NOT WORK SEND A DIFFERENT EMAIL###\n MESSAGE=\"$(tail -10 /var/lib/mysql/vps.publishman.com.err)\"\n SUBJECT=\"$i down on $(hostname) $(date) \"\n echo \" $i $MESSAGE . I tried to restart but it did not work\" | mail -s \"$SUBJECT\" \"$EMAIL\"\n\n fi\n fi\n\n\n\n ################### DOWN APACHE server######################\n#!/bin/bash\n#ver. 2\n\n##this script will check whatever services\n##you want to keep an eye on\n##if that service is not running\n##it will (try to) start the service and send\n##an email to you\n\n##set your email address\nEMAILA=\"[email protected]\"\n\n##list your services you want to check\n##you can add as many as you like\nSERVICESA=('httpd')\n\n#### DO NOT CHANGE anything BELOW ####\n\n\n for a in \"${SERVICESA[@]}\"\n do\n ###IF SERVICE IS NOT RUNNING####\n\nif [[ \"$(service $a status)\"=~\"$a is stopped\" ]]\n\n then\n ##TRY TO RESTART THAT SERVICE###\n service $a start\n\n ##IF RESTART WORKED###\nif [[ \"$(service $a status)\"=~\"is running\" ]]\n\n then\n ##SEND AN EMAIL###\n MESSAGEA=\"$(tail -10 /var/log/apache2/error\\_log)\"\n SUBJECTA=\"$a down -but restarted- on $(hostname) $(date) \"\n echo \" $a $MESSAGEA \" | mail -s \"$SUBJECTA\" \"$EMAILA\"\n else\n\n ##IF RESTART DID NOT WORK SEND A DIFFERENT EMAIL###\n MESSAGEA=\"$(tail -10 /var/log/apache2/error\\_log)\"\n SUBJECTA=\"$a down on $(hostname) $(date) \"\n echo \" $a $MESSAGEA . I tried to restart but it did not work\" | mail -s \"$SUBJECTA\" \"$EMAILA\"\n\n fi\n fi\n\n done\nexit 0;\n```\n\n", "name": "", "is_accepted": false } ]

[ { "text": "Table restore from rman backup is a feature of enterprise edition . in this case our database edition is standard . so we can not restore table from rman backup directly . we have only available option as below . \n\n1)    Restore entire prod database to a non-prod  server \n\n2)    Take  export backup of  required table t1) in Non-PROD Server \n\n3)    Take the export backup of the table (t1) in PROD \n\n4)    Restore the table back ( from export backup dump file taken in Non-Prod server)  to the production database \n\n5)    Verify the data , If no issues noticed then proceed with next steps else cleanup the table and import backup dump file taken from PROD. \n\n6)    Drop the database which was restored at non prod server .", "name": "", "is_accepted": false } ]

[ { "text": "Present running version 12c only synching will happen automatically,Other version Move the archive logs  manually to DR location will it not happen automatically", "name": "", "is_accepted": false } ]