chwe

posting the tutorial might be worth.. doesn't seem to be an boardissue, rather an general debian/ubuntu issue.. @Igor can you rename 'Peer to peer technical support' or it's subtext so that we can move general linux questions also there? or hopefully others might get it that dev and tech support is likely the wrong place for it?

https://medium.com/@jeffreypbezos/no-thank-you-mr-pecker-146e3922310f seriously? As head of a crappy newspaper you write a mail to jeff bezos hopping that he gets silent once he knows that you've a dickpic of him? With a, whenever you talk about it we'll release the dickpic move in the end?? you better don't use amazon services for your newspapers it might have some 'maintenance shutdowns' the next days... But here's a blackmailer 101 course for you.. Your target has to believe that the issue is solved after it accepts your deal. Means he gets back the dickpic and is save for the future.. Claiming that you'll keep the pics anyway isn't a smart move.. Cause people don't want to fear that those pics are released in the future..

which will likely fail.. https://github.com/rockchip-linux/kernel/issues/125 https://github.com/rockchip-linux/kernel/issues/72 https://github.com/rockchip-linux/kernel/issues/98#issuecomment-396422765 I tried last weekend a quick one to get the ISP1 driver working on 4.4 for rk3399 and it looks quite similar to rk3288, seems that the ISP driver still messes with our kernelconfig.. be prepared..

https://github.com/armbian/build/pull/1151 going through this PR can give you a insight how to bring up a new board family. Is it the same SoC as on the EspressoBin?

please read this one again. https://forum.armbian.com/guidelines

nope.. it's csc only.. means no 'official support'

I had this in mind for quite a long time... E.g. have serial access to boards which hangs or to trigger a reboot.. Do you have the sourcecode laying around?

well, booting armbian was just more or less 'a joke'.. Don't get me wrong.. it works.. I would strip down an image quite a lot to make it usable for the v3s... But it would work under the sun8i family.. https://github.com/armbian/build/compare/master...chwe17:v3s (whereas the kernel-config is a left over from some funny ideas I had with this board.., just forget about it) But if you need the armbian buildscript as a lazy tool to crosscompile u-boot or kernel.. armbians current sunxi kernel works out of the box.. And debian stretch can boot from 64MB ram.. I don't know yet where it will end.. Likely that I solder SPI flash on it in the future.

'fixed' well it's not a nice fix but it does the job... https://github.com/armbian/build/commit/6d9ab1c07c16ac990f620885dd9f0a6812f2a573 btw. it doesn't' like ISP1 as well.. means the kernel crashes quite soon..

a bit of housekeeping.. https://github.com/armbian/build/commit/864de31d5cb3e02d950ff5d658d065be8bb31541 uboot was bumped to 2019.01 so that most of the u-boot patches are gone now.. reboot issue on eMMC is still there.. but at least we're not longer on an rc uboot version.

due to digging a bit around for the R2.. this one came up: https://cateee.net/lkddb/web-lkddb/DRM_FBDEV_LEAK_PHYS_SMEM.html https://patchwork.kernel.org/patch/10619843/

well.. my v3s sits around unsoldered as before.. don't have time to get familiar with kicad to design a board.. maybe in the future.. pine comes with an S3L... https://forum.pine64.org/showthread.php?tid=7093 so most of the 'nice ideas' I had in mind for my V3s

didn't you call a challenge for the first one who gets armbian to run on a V3s some months ago? _ _ _ ____ _ _____ | | (_) ___| |__ ___ ___| _ \(_) |__ /___ _ __ ___ | | | |/ __| '_ \ / _ \/ _ \ |_) | | / // _ \ '__/ _ \ | |___| | (__| | | | __/ __/ __/| | / /| __/ | | (_) | |_____|_|\___|_| |_|\___|\___|_| |_| /____\___|_| \___/ Welcome to ARMBIAN 5.74 user-built Debian GNU/Linux 9 (stretch) 4.20.2-sunxi System load: 1.90 0.67 0.24 Up time: 1 min Memory usage: 58 % of 50MB Zram usage: 36 % of 25Mb IP: Usage of /: 4% of 29G [ General system configuration (beta): armbian-config ] New to Armbian? Check the documentation first: https://docs.armbian.com Thank you for choosing Armbian! Support: www.armbian.com Creating a new user account. Press <Ctrl-C> to abort Please provide a username (eg. your forename): got one on Christmas.. didn't have time to dig into it.. but well.. here you are.. Armbian booting from a LicheePiZero Does it make sense? not really.. but hey.. who cares.. it boots.. in less than 30 seconds..

they should update their wiki.. https://wiki.alpinelinux.org/wiki/DIY_Fully_working_Alpine_Linux_for_Allwinner_and_Other_ARM_SOCs#Compiling_Kernel_with_.dtb_file but indeed, the u-boot stuff is nicely summed up.

probably not.. But you have at least to provide a bootlog from serial console to get a clue where it messes.. RockPi is in early stage of board bring up (wip). Bugs must be expected.. nope, therefore moved to the rockpi thread..

Appeler un chat un chat.. yes you are.. otherwise you wouldn't deal with boards like the RK3399 opi board.. Si nous parlons français: On ne peut pas faire une omelette sans casser des œufs. I assume my old french-teachers would kill me for that..

I would go for UART as well when possible. Even if your SBC is more or less 'dead' you get often an output from UART, whereas everything else gets silent.. So having a really 'low level debug' possibility might be helpful. Having g_ether might be helpful as well to reduce the cables needed inside.. Just double-check then the network config on the R2.. It already has a messed up network configuration...

call the first one "I don't care, I only trash everyone's spare-time" The thing with restrictions is.. People can spend an amazing large time to fool the restriction tool compared to think that those restrictions have a reason... Not sure if escalate those 'restriction-tool' is the way we want to go... Just getting ignored might be the most effective one.. Every tool we add to the forumsoftware opens just more workload (e.g. fear that all of those tools still work after a froum update etc.).. Configuration which isn't properly set/explained and ends then in such threads: even if igor doesn't want to have more 'not bug/armbian related questions' it might help to have a general linux/debian questions subforum which is also named this way. E.g.: and probably a few more if I would read more stuff there are not really armbian related questions.. I understand why those people are here.. Maybe we should give them some room to keep the tech. support subforum as clean as possible without much efforts..

nice to see that at least someone uses the work.. (tbh, mine is collecting dust since I'm low on time..) another option for you could be to run them all on NetworkD.. you can tell networkmanager to ignore interfaces.. and then it shouldn't touch it.. (assuming it's working correctly.. that's what we do on the R2 for all the wired interfaces).. if only serial is needed.. maybe you can use the pinheader or the R2? somehow similar to this one? last paragraph.. TBH, I never tested the pinheader on the R2. could be fun to test.. We 'need' a system which works 'reliable' on first boot. There are a bunch of people don't have an USB-UART to configure their Network after first boot.. Wifi on /etc/network/interfaces is also something only for masochists... Honestly.. I prefer NM on all of my machines.. especially the dispatcher is a great tool... But as with a lot of stuff.. if you've 3 people in a room, you get 4 opinions what's the perfect tool for the job..

well, I'm quite confident that they don't need 'our help' in those days to look stupid.. In case someone asks it's mostly the Austrians and the Germans fault why we can observe greenhouse gases (Boltzmann & Planck). For those wanna lock smarter as they are... A heretical explanation which 'works' is that every gas consisting more than two atoms is a greenhouse gas (e.g. the famous CO2). To be a greenhouse gas, a gas has to absorb near-IR radiation. If you dive now into quantum physics, only so called vibrational& vibrational-rotational transition which change the dipole moment of a molecule are allowed. If you compare now CO2 (greenhouse gas) and N2 (not a greenhouse gas): Carbon dioxide has two normal modes (2&3) which end in a change of the dipole moment (and one mode without such a change) whereas Nitrogen gas hasn't such a normal mode (only a symmetric stretch). But before we dive more into smart ass mode... I'm by no mean an expert in quantum mechanics I'm more like Dwayne Johnson in No pain no gain... Luckily, smarter people at Harvard rolled the topic better up that I could do it ever on myself from a quantum mechanical standpoint. Feel free to dive into it: http://acmg.seas.harvard.edu/people/faculty/djj/book/bookchap7.html They don't try to make up conclusions which their data doesn't cover.. They just try to explain it for people at least somehow able to understand quantum mechanics basically. Unfortunately there aren't as many 'scientific journalists' around the world to analyze and understand scientific papers to come to the right conclusion. In fact they mostly try to catch up some 'dramatic looking' sentences inside a publication to get some attention assuming that every sentence in a publication is so 'well-crafted' that it must be still valid if you change it a little bit. A *random expert* adds then some other dramatic sentences as well and there you get your 'it's the global warming, stupid'-article.. Small hint, not every scientific publication is on such a high level and it needs a lot of skills to break down such an article to make it understandable for the average joe and still being scientifically correct. Unfortunately it often ends in "reading A, thinking it means B and conclude C".. Maybe we could do better try to explain what our research tries to achieve in a manner that the 'average joe' also partly understands what we're doing... Not every detail, but at least partly..

happens when you take a nap during your statistic courses.. seeing A, thinking about B and conclude C.. Unfortunately, it's not only he who should be blamed for it.. Quite a long time we tried to fit every storm, hot weather period, *random climatic phenomena* into this 'climate change thing'.. Not as surprisingly people don't believe it anymore.. The worst thing you can do to a field of science is to steal its trustworthiness.. And at least for a (growing) fraction of the population we must conclude that we achieved this since a few years now.. Well done...

for whatever reason a 'clone gene-sequence into animal and express it' paper got some media attention: https://futurism.com/genetically-modified-chickens-cancer-drug/ https://www.bbc.com/news/science-environment-46993649 for those not so familiar with this.. it's not the first time.. people already cloned a spider gene coding for the fiber proteins into goats (no not tom brady :D).. and a few other.. The goal is always to produce *random proteins* cheaper as when you do it in cell cultures. Depending on which cells you must use for it, keeping them alive isn't as easy - people try to use cells like E. coli as often as possible, unfortunately those bacteria cells can't 'grow' everything, bacteria is a rather simple organism.. not able to do the same post-transnational modifications as eukaryotes.. Keeping eukaryotes alive in cell culture medium is expensive (e.g. a lot of work to keep everything sterile).. let an animal do the job might be cheaper as a 'living bioreactor'.. somehow similar to the vaccines and their first trials.

sounds like a perfect definition of SAP... I think the maintainers list flies around in our heads since a long time (couldn't find the thread anymore, or it was on pm.. no idea, probably in the project aims thread or here).. A starter could be SoC maintainers instead of board maintainers... e.g. every patch touching RK3399 needs at least your approval to be merged.. every H3 related needs igors approval etc. the more you work with a SoC, the more you know its faults.. and if this is a real concern: Guess why Igor and TK had in their signature, do not write me a PM for xyz. You would basically force exactly that. we could have 'who has which board list' private so that patches can be redirected to those people without floating their inboxes with 'support questions'.. but I'm quite sure it happens anyway.. people will notice who's doing such stuff and stalk them privately to solve their issues.. It doesn't need much to figure out who's good in *random topic*... For the 'individual roles'.. I think those roles aren't that clear.. most devs do u-boot, kernel and rootfs related stuff (and when needed also buildscript related stuff).. A proper review policy might help here.. (e.g. when touching nand-sata install @zador.blood.stained has to review it).. well they will be here.. to sort out if it's our issue or a debian issue isn't always easy.. best would be that such solutions would then end in a tutorial in the tutorial section.. as some sort of a 'contribute back', we might encourage people more to write such tutorials out of the help they got. someone able to fix a *random issue* might probably don't even spot it.. cause not reading every thread/post here.. things get out of track.. or the one catches the bug isn't able to solve it, but someone else is.. it's part of the basics things to keep track of the bugs your project has.. the 'nicest' web-page, project goals etc. is worthless without images of good quality coming out from the buildsystem (and the updates we provide over apt). Keeping the project maintainable is a basic requirement..

at least yes! I think we should keep an eye on this.. In case it produces more work than the behavior before we should revert it. I'm not a fan of restrictions.. People may just spam somewhere else in the forum to get 'post rights' in tech support and then floating it anyway. I assume it could be a 'feature' which we've to explain on a weekly basis cause people normally don't read those additional notes..

well which project do you think? Let's look at a few which have some similarities. Retropi: Raspian: https://www.raspberrypi.org/forums/viewtopic.php?t=208814#p1291227 OpenWRT: https://openwrt.org/bugs DietPi: mostly forum, a bit on GitHub ________________________________________________________________________________________- There's no project which is 100% similar, otherwise one of them would be obsolete.. A few of them scale bigger, some have a different focus. Some ideas: manual transfer: as soon as a experienced user/mod/maintainer realizes that the forum post is related to an issue he opens it, summarizes it and links to the related forum post. It's time consuming but we would keep track on all those bugs we spot through forum posts. As soon as we have an issue tracker outside forum or github, we've to train people once again to use it.. we've to maintain it.. and those not willing to register somewhere will still use the forum for that. The only idea which comes to my mind is either one on a well established platform so that the average user has it anyway (e.g. github) or mailing-list (I assume most people will still have a mailaccount ) but not sure if maintaining a mailing list would solve any problem - I would assume not. Maybe we can implement a bug Tag? once figured out that a thread is bug related mods/admins/devs could just add the bug tag to the related post/thread? Keeping an eye on threads with such a tag might be easier.. Still, the tag has to be removed once the bug is fixed, but it could be a starter.