chwe

  • Posts

    1432
  • Joined

  • Last visited

Reputation Activity

  1. Like
    chwe got a reaction from aaditya in RK3399 -Smart Technologies AM40 iQ "Module"   
    it was highly overpriced with 400-600$ (IMO still 100$ are too much for it) it is mostly undocumented what you got is a 4GB ddr3 rk3399 'TV box' with 2x2 wifi over mPCIe and 32GB eMMC with a 'connector' I've not seen any specification what's populated on it
    . which may or may not work with a 'generic DT' (generic means here any rk3399 dt file we have most of them are quite similar cause they follow more or less the reference design) for rk3399 boards. You can also (try to) 'extract' the dtb file from 'whatever is preloaded' on this box.. decompile it and follow all the phadles to see how nodes are connected to each other.. to adjust a working DT to match the box better or write one from plain.. (you can also use this blob directly on any sort 'armbian' and see if it is compatible).
     
    at least it has a debug UART populated (likely 3v3 but who knows, you should check that first)
     
    Is it worth it.. well that's up to you.. if you're interested in going down the rabbit hole and learn new things.. maybe it is (you can spend a lot of time with bootloaders, device tree etc. on it.. IIRC ddr3 should be supported with mainline u-boot, and what they have labeled 'service only' looks like a SD-card holder, so you can likely do your 'try and error attempts' to get something 'armbian a like' booting on this board without corrupting the OS which is currently preflashed on the eMMC.
    likely similar to that stuff here:http://wiki.t-firefly.com/en/Firefly-RK3399/adb_use.html
     
    So to summarize you currently got a paperweight and it's up to you to transform it in something useful. Even then I don't see much of a reason to provide support on such a board. It has a 'unknown' availability (you got it cheap from ebay, but as soon as this sellers run out of stock, it's likely never appearing again). For 100$ you get the nanopi m4v2 with a case which offers known schematics, support from the boardvendor, known connectors (including eMMC, PCIe, hdmi, camera and display interfaces) and the vendor known in SBC marked for years (they may not do everything perfect but you mostly know what you get, and in general those boards work as they should). This box might be nice if you plan to learn and dig into what can make it a pain to support random boxes with 'somehow' proper working images. But you may have to build your images on your own for a long time in case non of the images we provide for rk3399 will work out of the box (I would focus on images built for ddr3 ram type boards).
  2. Like
    chwe got a reaction from piter75 in rk3399-bluetooth.service is still present in "systemctl list-jobs"   
    IMO the easiest way is ./compile.sh KERNEL_CONFIGURE=yes make your changes when menuconfig pops up and you get your new config in output/config after compilation. It's even named the way it should be..
  3. Like
    chwe got a reaction from mar0ni in NanopiM4v2 booting. this is weird   
    https://github.com/armbian/build/blob/9be143c2e4788deae6faf26d8ecfd921cfd52deb/patch/u-boot/u-boot-rk3399/add-board-nanopi-m4v2.patch#L29
     
    https://lists.denx.de/pipermail/u-boot/2017-April/285942.html
     
    should explain most of it..
     
    this whole mess should be cleaned once we've moved all boards to upstream u-boot for rk3399 boards...
  4. Like
    chwe got a reaction from TRS-80 in Process for adding CSC boards?   
    blobs:
    https://github.com/armbian/build/tree/master/packages/blobs/mt7623n
    https://github.com/armbian/build/blob/909be0239d8f3a9d6e2dae9da94d18b65e350320/config/sources/families/meson-gxl.conf#L18-L27
    ends then in: https://github.com/armbian/odroidc2-blobs
     
    so we even already dealt with bootblobs we've no clue what they're doing.. especially meson-glx
     
    still needs the blobs to chainload UEFI (https://github.com/tianocore/edk2-platforms/tree/master/Platform/RaspberryPi/RPi3):
     
     
    the only serious attempt to avoid this was done by christinaa (https://github.com/christinaa/rpi-open-firmware) but more or less dead since months/years. So no there's no change that the RPi relies on bootblobs to get up and running
     
    Cause the bootloader (bootcode.bin) only understands FAT you also need some tweaks here and there in the buildscript.. But most of the needed features are there cause we support(ed?) having /boot on FAT. According to jamesh from the RPi forum their engineers don't see a reason that a bootloader should understand something like ext4 (I would have to search in my posts in their forum to get you a quote for that).. But safest bet for a more or less "sane" implementation would be bootcode chainloads u-boot and u-boot then properly loads a kernel sitting in a ext4 partition.
     
    IMO that doesn't fit to the 3b+ at all.. Maybe partly to the 4. In most when not all parts a rk3399 based on will outperform even the RP4 and for sure the RPi3
     
    what do you mean with ROCK? means RockPi? then there you go:https://www.seeedstudio.com/PoE-HAT-for-ROCK-Pi-4-p-4143.html currently out of stock but allnet has it:
    https://shop.allnetchina.cn/products/rock-pi-4b-poe-hat
     
    I guess something like this will do the trick: https://www.aliexpress.com/item/33057941535.html?spm=a2g0o.productlist.0.0.38d222ebEfaAc9&algo_pvid=ebc883c9-19fd-4f58-ae77-add76220ba26&algo_expid=ebc883c9-19fd-4f58-ae77-add76220ba26-3&btsid=1071dcd7-b020-4d15-ab51-f383395eff93&ws_ab_test=searchweb0_0,searchweb201602_9,searchweb201603_53
    obviously untested I don't deal with POE atm. Just make sure that you don't run into:
    RK3399 tends to be power-hungry..
     
    but back to topic:
    have a sane implementation dealing with the bootstuff when possible don't add additional kernel sources (means build your kernel on top of mainline) Make sure that basic functionality even when you're not interested in works (e.g. USB/HDMI/UART or it's clearly that it doesn't work - well UART must work otherwise it's a pain to debug)  
  5. Like
    chwe got a reaction from lanefu in Proposed Forum Structure Change   
    more subforums add just more subforums I'll ignore.. and there are quite some atm. And it seems we have this discussion like once a year or so... And yes I started such a thread as well must be gone somewhere by one of our forum rearrangements...
     
    we have a:
     
    where all the not armbian related software questions can go as well..
     
    and we have a
    and chit chat.. IMO chit chat is the place where everything goes in nobody wants to deal with..
    The more subforums you have the higher the chance that people choose the wrong one.. means after its more moderation work and as you said time is valuable..
    In a perfect world I would not want to moderate at all cause people don't mess stuff up.. For me moderating is splitting/merge topics on request or when they're obviously not related to each other/connected to each other. Locking stuff down when it goes out of control... which happens from time to time when people get frustrated.. Otheerwise I see myself just a normal user/dev doing dev stuff or spaming in the chit chat about chit chat stuff:
     
    that's what this subforum is for... As well as asking which TV box may or may not be a good pick can have a living there.
     
    If the new structure ends in more moderating we do things wrong, if it ends in less moderating we do stuff right.. as simple as it is.. The same reason I had a iphone for years and not an android phone.. I just had to think less where I find what I need. This got better in android world but I'm not sure if it got better in the forum over time but I don't think a more fine grained forum will help here. I can be wrong on that but people tend to post fast and think less means if they don't find the topic it will fit within page one they'l post it wherever they are at this moment..  Ask yourself.. when did you last go to page 3 or page 4 on a googlesearch? The same happens on forums.. And that's why I mostly refuse to answer to posts where the solution can be found within the first two pages of a googlesearch.. or if I do, I'll use something like https://lmgtfy.com/ to remind those people that things are easy as hell if you use the right search terms. I guess this behavior is now called being toxic - I somehow missed this change in social moves from "it's being a dickmove to waste someone else' time if it can be found with a random search engine" to "every stupid question is worth an answer an how dare you are if it's not written super welcoming and inclusive to everyone"... Back to topic:
    That may sound hard but: for your own sake, better learn to deal with it.
     
    Users are interested in:
    a working SBC with all the features a boardmaker claims (and mostly he sums up the capability of the SoC - mostly this features are based on what works on android and have barely something to do with what works on debian/ubuntu having a recent debian/ubuntu cause nobody wants to deal with something like trusty anymore but they mostly don't care about stuff like bootloader and kernel at all as long as it has the features they need. We still have a bunch of users using the 3.4 bsp kernel on allwinner and we soon ran into the same nightmare with rockchip 4.4 (at least in rockchips case there is a chance that they forward port this to a more recent kernel once android requires a newer kernel) using the most crappy powersupply they have somewhere laying around getting support ASAP cause their problem is for sure the most important one on the world Developers are interested in:
    solving some interesting parts which didn't work before dealing as less as possible with users cause their mess there nice: everything works world up and soak up the time for development having a few users for testing cause testing is boring bringing new boards up, cause board bring up is a way more interesting than board maintenance.. So you see your point: having a well organized forum doesn't really affect both of the mayor groups we're dealing here with.. There are only a few people interested in maintaining the forum and from those few even less are interested in reorganize stuff cause this means more maintenance work and explaining the users why things have changed and how it is supposed to work now. There is this nice little saying: Rome wasn't built in one day, I would add but Nero burned it down in one. To explain that a bit more, if a change breaks the current state may make sense but break existing behavior hence ends in more rebuilding/moderating. This may work as long as you have the fresh "spirit" of moderating things.. but can you keep this over time (means for years not only months)? Cause that's what is needed if we decide to moving around things or moderate more stuff. It's not a change things and everything will be fine, people will still post on the wrong threads and people will still have a wrong assumption what armbian is (a spare time project which tries to do it's best to support a variety of boards as good as possible with a recent kernel with flavors of ubuntu/debian with some tweaks here and there to make debian more useful on such boards e.g nand-sata-install, and tweaks around zram due to limited ram on most of this boards).
    Or to summarize most of it related to your new job as moderator.. be patient and accept that changes might need their time. And right reorganization of the forum might not be on high priory during a release. Especially that this release model is something we're more or less doing "the first time". Or at least it's done the first time that way as we do/try to do it yet. There's for sure a bunch of stuff I forgot to write up.. 
     
    Disclaimer: as often.. this post may contain some sarcasm, some rants etc. (I may should have this in my signature for the future)...
  6. Like
    chwe got a reaction from gounthar in Orange pi 4   
    I had time to test my newly written DT for the orangepi4:
     
    sound still doesn't work (even when I replaced the bits to use rt5651) I guess some of the mic/headphone definitions in the DT are still wrong.. wifi works with network manager ethernet works as well both USB2 are tested and working (I've the NPU version so I didn't try to look at USB3 atm, may or may not work who knows) dmesg shows still some errors to wifi but I've no idea if this is related to the opi at all or just fall out from the normal driver situation here hdmi is untested yet (i've no spare device for doing it) actually the DT should also support eDP over USB-C as far as I've saw in the schematics the opi4 should do it as well.. this should be possible and it's done similar to the pinebook, obviously I've also no spare eDP over usb-c display...
     
    so for @piter75 if you want to mess with it.. here is an updated version of it.. And for the less experienced ones.. you might not wanna mess with it yet.. at least on the powertree there's nothing horrible wrong so that the board would not boot up..
    opi4b_dts_v1.dts
  7. Like
    chwe got a reaction from Werner in Proposed Forum Structure Change   
    more subforums add just more subforums I'll ignore.. and there are quite some atm. And it seems we have this discussion like once a year or so... And yes I started such a thread as well must be gone somewhere by one of our forum rearrangements...
     
    we have a:
     
    where all the not armbian related software questions can go as well..
     
    and we have a
    and chit chat.. IMO chit chat is the place where everything goes in nobody wants to deal with..
    The more subforums you have the higher the chance that people choose the wrong one.. means after its more moderation work and as you said time is valuable..
    In a perfect world I would not want to moderate at all cause people don't mess stuff up.. For me moderating is splitting/merge topics on request or when they're obviously not related to each other/connected to each other. Locking stuff down when it goes out of control... which happens from time to time when people get frustrated.. Otheerwise I see myself just a normal user/dev doing dev stuff or spaming in the chit chat about chit chat stuff:
     
    that's what this subforum is for... As well as asking which TV box may or may not be a good pick can have a living there.
     
    If the new structure ends in more moderating we do things wrong, if it ends in less moderating we do stuff right.. as simple as it is.. The same reason I had a iphone for years and not an android phone.. I just had to think less where I find what I need. This got better in android world but I'm not sure if it got better in the forum over time but I don't think a more fine grained forum will help here. I can be wrong on that but people tend to post fast and think less means if they don't find the topic it will fit within page one they'l post it wherever they are at this moment..  Ask yourself.. when did you last go to page 3 or page 4 on a googlesearch? The same happens on forums.. And that's why I mostly refuse to answer to posts where the solution can be found within the first two pages of a googlesearch.. or if I do, I'll use something like https://lmgtfy.com/ to remind those people that things are easy as hell if you use the right search terms. I guess this behavior is now called being toxic - I somehow missed this change in social moves from "it's being a dickmove to waste someone else' time if it can be found with a random search engine" to "every stupid question is worth an answer an how dare you are if it's not written super welcoming and inclusive to everyone"... Back to topic:
    That may sound hard but: for your own sake, better learn to deal with it.
     
    Users are interested in:
    a working SBC with all the features a boardmaker claims (and mostly he sums up the capability of the SoC - mostly this features are based on what works on android and have barely something to do with what works on debian/ubuntu having a recent debian/ubuntu cause nobody wants to deal with something like trusty anymore but they mostly don't care about stuff like bootloader and kernel at all as long as it has the features they need. We still have a bunch of users using the 3.4 bsp kernel on allwinner and we soon ran into the same nightmare with rockchip 4.4 (at least in rockchips case there is a chance that they forward port this to a more recent kernel once android requires a newer kernel) using the most crappy powersupply they have somewhere laying around getting support ASAP cause their problem is for sure the most important one on the world Developers are interested in:
    solving some interesting parts which didn't work before dealing as less as possible with users cause their mess there nice: everything works world up and soak up the time for development having a few users for testing cause testing is boring bringing new boards up, cause board bring up is a way more interesting than board maintenance.. So you see your point: having a well organized forum doesn't really affect both of the mayor groups we're dealing here with.. There are only a few people interested in maintaining the forum and from those few even less are interested in reorganize stuff cause this means more maintenance work and explaining the users why things have changed and how it is supposed to work now. There is this nice little saying: Rome wasn't built in one day, I would add but Nero burned it down in one. To explain that a bit more, if a change breaks the current state may make sense but break existing behavior hence ends in more rebuilding/moderating. This may work as long as you have the fresh "spirit" of moderating things.. but can you keep this over time (means for years not only months)? Cause that's what is needed if we decide to moving around things or moderate more stuff. It's not a change things and everything will be fine, people will still post on the wrong threads and people will still have a wrong assumption what armbian is (a spare time project which tries to do it's best to support a variety of boards as good as possible with a recent kernel with flavors of ubuntu/debian with some tweaks here and there to make debian more useful on such boards e.g nand-sata-install, and tweaks around zram due to limited ram on most of this boards).
    Or to summarize most of it related to your new job as moderator.. be patient and accept that changes might need their time. And right reorganization of the forum might not be on high priory during a release. Especially that this release model is something we're more or less doing "the first time". Or at least it's done the first time that way as we do/try to do it yet. There's for sure a bunch of stuff I forgot to write up.. 
     
    Disclaimer: as often.. this post may contain some sarcasm, some rants etc. (I may should have this in my signature for the future)...
  8. Like
    chwe got a reaction from lanefu in Orange pi 4   
    I'll happily move your posts here then:
    https://forum.armbian.com/forum/31-sd-card-and-psu-issues/
     

     
    sorry I couldn't resist.. I use the goat PSU called RPi USB-C PSU for most of my USB-C boards at the moment, until yet I didn't figure out a board which doesn't work as it should with it (my dirt cheap IKEA charger does also well but that one is used productive atm). 
     
    btw is the bq25700 from page 3 really populated on the board? It might have some interesting features to mess with.. http://www.ti.com/product/BQ25700A
    (Input and Battery Current Monitor)
  9. Like
    chwe got a reaction from Igor in Proposed Forum Structure Change   
    more subforums add just more subforums I'll ignore.. and there are quite some atm. And it seems we have this discussion like once a year or so... And yes I started such a thread as well must be gone somewhere by one of our forum rearrangements...
     
    we have a:
     
    where all the not armbian related software questions can go as well..
     
    and we have a
    and chit chat.. IMO chit chat is the place where everything goes in nobody wants to deal with..
    The more subforums you have the higher the chance that people choose the wrong one.. means after its more moderation work and as you said time is valuable..
    In a perfect world I would not want to moderate at all cause people don't mess stuff up.. For me moderating is splitting/merge topics on request or when they're obviously not related to each other/connected to each other. Locking stuff down when it goes out of control... which happens from time to time when people get frustrated.. Otheerwise I see myself just a normal user/dev doing dev stuff or spaming in the chit chat about chit chat stuff:
     
    that's what this subforum is for... As well as asking which TV box may or may not be a good pick can have a living there.
     
    If the new structure ends in more moderating we do things wrong, if it ends in less moderating we do stuff right.. as simple as it is.. The same reason I had a iphone for years and not an android phone.. I just had to think less where I find what I need. This got better in android world but I'm not sure if it got better in the forum over time but I don't think a more fine grained forum will help here. I can be wrong on that but people tend to post fast and think less means if they don't find the topic it will fit within page one they'l post it wherever they are at this moment..  Ask yourself.. when did you last go to page 3 or page 4 on a googlesearch? The same happens on forums.. And that's why I mostly refuse to answer to posts where the solution can be found within the first two pages of a googlesearch.. or if I do, I'll use something like https://lmgtfy.com/ to remind those people that things are easy as hell if you use the right search terms. I guess this behavior is now called being toxic - I somehow missed this change in social moves from "it's being a dickmove to waste someone else' time if it can be found with a random search engine" to "every stupid question is worth an answer an how dare you are if it's not written super welcoming and inclusive to everyone"... Back to topic:
    That may sound hard but: for your own sake, better learn to deal with it.
     
    Users are interested in:
    a working SBC with all the features a boardmaker claims (and mostly he sums up the capability of the SoC - mostly this features are based on what works on android and have barely something to do with what works on debian/ubuntu having a recent debian/ubuntu cause nobody wants to deal with something like trusty anymore but they mostly don't care about stuff like bootloader and kernel at all as long as it has the features they need. We still have a bunch of users using the 3.4 bsp kernel on allwinner and we soon ran into the same nightmare with rockchip 4.4 (at least in rockchips case there is a chance that they forward port this to a more recent kernel once android requires a newer kernel) using the most crappy powersupply they have somewhere laying around getting support ASAP cause their problem is for sure the most important one on the world Developers are interested in:
    solving some interesting parts which didn't work before dealing as less as possible with users cause their mess there nice: everything works world up and soak up the time for development having a few users for testing cause testing is boring bringing new boards up, cause board bring up is a way more interesting than board maintenance.. So you see your point: having a well organized forum doesn't really affect both of the mayor groups we're dealing here with.. There are only a few people interested in maintaining the forum and from those few even less are interested in reorganize stuff cause this means more maintenance work and explaining the users why things have changed and how it is supposed to work now. There is this nice little saying: Rome wasn't built in one day, I would add but Nero burned it down in one. To explain that a bit more, if a change breaks the current state may make sense but break existing behavior hence ends in more rebuilding/moderating. This may work as long as you have the fresh "spirit" of moderating things.. but can you keep this over time (means for years not only months)? Cause that's what is needed if we decide to moving around things or moderate more stuff. It's not a change things and everything will be fine, people will still post on the wrong threads and people will still have a wrong assumption what armbian is (a spare time project which tries to do it's best to support a variety of boards as good as possible with a recent kernel with flavors of ubuntu/debian with some tweaks here and there to make debian more useful on such boards e.g nand-sata-install, and tweaks around zram due to limited ram on most of this boards).
    Or to summarize most of it related to your new job as moderator.. be patient and accept that changes might need their time. And right reorganization of the forum might not be on high priory during a release. Especially that this release model is something we're more or less doing "the first time". Or at least it's done the first time that way as we do/try to do it yet. There's for sure a bunch of stuff I forgot to write up.. 
     
    Disclaimer: as often.. this post may contain some sarcasm, some rants etc. (I may should have this in my signature for the future)...
  10. Like
    chwe reacted to balbes150 in Censorship 2020   
    Because this "one person" is responsible for the performance of a special version of Armbian for TV boxes and knows for sure that this shitty model will not work properly with Armbian, and will require those who buy it for use with Armbian to spend more money (obviously more than if they bought another model with a normal configuration of iron), in order to somehow make this stuff work. And buyers will regularly distract and spend forum resources to ask the same questions about why this shit doesn't work. Neither any justification, they say that this model can be used for other systems, not relevant here, want to discuss the launch of the other systems on this shit, use the appropriate forums. Unlike you, other users regularly ask questions on different TV boxes about the possibility of using them, and no one behaves so aggressively, trying to impose a discussion of this shit on everyone. They get an answer (by the way, not only from me, but also from other experienced users), about the suitability of using a particular equipment, and then decide what to do, without hysterics and screams on the forum, if they were told that the selected device is not recommended to take.
  11. Like
    chwe got a reaction from OrangePee in Censorship 2020   
    feel free
     
    even the last one didn't bother me.. but in case you want that people take you serious something *less creative* might work better.. explore your creativity where it's worth it and that might not be forum name nicknames..
     
    well that could be a field of your research not? How much he contributed to get armbian running on all those tv boxes no other dev even looks at. I don't think this subforum would even exist without him maintaining it more or less on his own. If you show up again with actual research done not only trying to convince others that they should do the research for you write me a pm an I'll happily reopen your thread.
     
    it's good to value your own time and how you spend it, therefore upon proven otherwise, I just decided to no longer waste my time in answering to your posts..
  12. Like
    chwe got a reaction from balbes150 in Censorship 2020   
    well that one escalated quickly.. and due to all the notifications popping up I had to follow most of the crap happened here.. And first before I even try to sum this up. I suppose you change your nick immediately to something else.
     
    You started with a thread about a dirt cheap TV box which you already bought and then tried to convince others to buy it as well cause it's cheap and somehow in the hope armbian will run on it.. This one got deleted by @TRS-80 . Which might be an overreaction. Depending on how you read the rules he had the right to do it.. I would probably just moved it to TV boxes so that it get read by the right persons namely @balbes150 who more or less maintains 'armbian on TV boxes' on his own. Most others doing development are for good reasons not interested in TV boxes (even with schematics it's mostly a pain if things like a proper DT don't exist from the vendor.. But instead of trying to get this in a better shape you tried to find every possible sub-forum to tell everyone that you're pissed-off that he deleted your first post here and there.. since he set you back that everything must be approved it just bloated my messegeboard more with stuff I actually have no passion to deal with.. After seeing that you bloat around everywhere, it was probably the right decision to revoke your post right upon approval by a moderator.. I'm not a fan of such actions cause it's just more work for me to approve x posts more per day..
     
    A small hint the few bucks you spend for an SBC or for TV box is nothing compared to the $ you spend for support. If balbes thinks it's not even worth to have a briefer look at a box he will have likely good reasons for that (I don't even waste my time for TV boxes anymore.. you don't know what you get, things can change cause the vendor runs out of something and replaces it with something else e.g. another wifi chip other ram other whatever he runs out... and then he has to deal with the fall out of that cause people show up here that their similar looking TV box doesn't work as expected). Who will then dive into it to fix it? Will you be around and fixing all this stuff? Or is it then up to him to explain the new users that "this batch works" and this batch doesn't cause component x changed and there's no support for it? It's mostly the second.. And why should he do that for a TV box he's not interested in at all? He answered quite polite that it's a boring TV box he's not interested in.. After that you tried to convince that this is somehow valuable for armbian for whatever reason. I don't think it is.. people here around know that the W905 variants are mostly well supported in the kernel a well supported SoC doesn't give you a well supported TV box/SBC.. As you both figured out the only network connection on this board is crap and due to limited other options (only 2 USB2 every other possibility e.g. attaching network over USB will limit a limited TV box even more making it a wasted 18$ for everyone who buys this box based on that thread in the hope that enough pressure on balbes will convince him to look at it). And that around a time you didn't even tried to get your research done if and how this thing can be re-flashed, that might be your starting point https://lmgtfy.com/?q=amlogic+s905+firmware+update+over+USB ) and then from the picture:

    you see on the right side VCC RX TX GND? that's likely your debug UART and 'most likely' it's 3V or 3v3 so setting up your debug UART see what comes out use google or bing or whatever searchengine you prefer. so that you get a clue what is there if people already did something with the bootloader there or a similar one (if it's u-boot and you can interrupt it printenv gives you some nice hints) post your finding and your guesses and maybe someone will give you a hint here and there how you should progress. That would show @balbes150 that you're actually interested in doing something not just soak up his time, maybe not cause I think he has enough valid points to declare this box as a waste of time.. And the TV box subforum is still a forum about armbian on TV boxes not elec"something" on TV boxes.. If you want that ask the guys there to support your new paperweight maybe they're willing maybe they're not - that's then their decision. But except the confirmation that there's a crap wifi IMO your thread provided nothing of value to armbian. Well at least those involved in the whole TV boxes stuff now can honestly say that you shouldn't buy this one if someone asks for advice which TV box he should buy (and if you want something which works without much pain it's a good idea to do your research first and then buy).
     
    Why should it get deleted? Maybe cause it's not about censorship here? If this would be about censorship we would have deleted your account all your posts and it would look like you were never here. That's censorship.. Locking a discussion where everything is said and all needed persons made clear that support for it wont happen isn't. It's just keeping the forum somehow readable. Tagging randomly people to waste their time as well is just bad taste. If Igor thinks that someone acted not the way it is acceptable he would already made this clear. Moderator rights already got revoked if someone didn't had a common sense how he should act like.. Was everything perfect ofc not -  or at least I would maybe solved things different, but mistakes happen and from what I saw no major mistake happened.. You got your thread back after things clarified even the restrictions got revoked. The only stuff which is 'censored' from you is where you entered a thread which was used by proved spammers to get the first mod approval just to bloat the forum after its with spam IMO that whole thread can go to trash cause it doesn't add any value to armbian but let others decide that. And your answers there honestly were just a try to make people angry so that you get a reaction nothing of value for ambian as well.. just another thread which wastes peoples time.
     
    So if you really wanna do some research (this here got the research tag removed by myself cause it's ranting not research) you could spend some time to get something out of your paperweight and see how far you get. likely this time is better spent as starting another discussion about random claims and insults to people here. Even when I think balbes is right and this box is a waste of time, it might be a good one to learn things on your own instead of pushing other people to do the work for you. And even when not.. at least you only wasted your time and not everyone else' time.
     
     
  13. Like
    chwe got a reaction from umiddelb in Censorship 2020   
    well that one escalated quickly.. and due to all the notifications popping up I had to follow most of the crap happened here.. And first before I even try to sum this up. I suppose you change your nick immediately to something else.
     
    You started with a thread about a dirt cheap TV box which you already bought and then tried to convince others to buy it as well cause it's cheap and somehow in the hope armbian will run on it.. This one got deleted by @TRS-80 . Which might be an overreaction. Depending on how you read the rules he had the right to do it.. I would probably just moved it to TV boxes so that it get read by the right persons namely @balbes150 who more or less maintains 'armbian on TV boxes' on his own. Most others doing development are for good reasons not interested in TV boxes (even with schematics it's mostly a pain if things like a proper DT don't exist from the vendor.. But instead of trying to get this in a better shape you tried to find every possible sub-forum to tell everyone that you're pissed-off that he deleted your first post here and there.. since he set you back that everything must be approved it just bloated my messegeboard more with stuff I actually have no passion to deal with.. After seeing that you bloat around everywhere, it was probably the right decision to revoke your post right upon approval by a moderator.. I'm not a fan of such actions cause it's just more work for me to approve x posts more per day..
     
    A small hint the few bucks you spend for an SBC or for TV box is nothing compared to the $ you spend for support. If balbes thinks it's not even worth to have a briefer look at a box he will have likely good reasons for that (I don't even waste my time for TV boxes anymore.. you don't know what you get, things can change cause the vendor runs out of something and replaces it with something else e.g. another wifi chip other ram other whatever he runs out... and then he has to deal with the fall out of that cause people show up here that their similar looking TV box doesn't work as expected). Who will then dive into it to fix it? Will you be around and fixing all this stuff? Or is it then up to him to explain the new users that "this batch works" and this batch doesn't cause component x changed and there's no support for it? It's mostly the second.. And why should he do that for a TV box he's not interested in at all? He answered quite polite that it's a boring TV box he's not interested in.. After that you tried to convince that this is somehow valuable for armbian for whatever reason. I don't think it is.. people here around know that the W905 variants are mostly well supported in the kernel a well supported SoC doesn't give you a well supported TV box/SBC.. As you both figured out the only network connection on this board is crap and due to limited other options (only 2 USB2 every other possibility e.g. attaching network over USB will limit a limited TV box even more making it a wasted 18$ for everyone who buys this box based on that thread in the hope that enough pressure on balbes will convince him to look at it). And that around a time you didn't even tried to get your research done if and how this thing can be re-flashed, that might be your starting point https://lmgtfy.com/?q=amlogic+s905+firmware+update+over+USB ) and then from the picture:

    you see on the right side VCC RX TX GND? that's likely your debug UART and 'most likely' it's 3V or 3v3 so setting up your debug UART see what comes out use google or bing or whatever searchengine you prefer. so that you get a clue what is there if people already did something with the bootloader there or a similar one (if it's u-boot and you can interrupt it printenv gives you some nice hints) post your finding and your guesses and maybe someone will give you a hint here and there how you should progress. That would show @balbes150 that you're actually interested in doing something not just soak up his time, maybe not cause I think he has enough valid points to declare this box as a waste of time.. And the TV box subforum is still a forum about armbian on TV boxes not elec"something" on TV boxes.. If you want that ask the guys there to support your new paperweight maybe they're willing maybe they're not - that's then their decision. But except the confirmation that there's a crap wifi IMO your thread provided nothing of value to armbian. Well at least those involved in the whole TV boxes stuff now can honestly say that you shouldn't buy this one if someone asks for advice which TV box he should buy (and if you want something which works without much pain it's a good idea to do your research first and then buy).
     
    Why should it get deleted? Maybe cause it's not about censorship here? If this would be about censorship we would have deleted your account all your posts and it would look like you were never here. That's censorship.. Locking a discussion where everything is said and all needed persons made clear that support for it wont happen isn't. It's just keeping the forum somehow readable. Tagging randomly people to waste their time as well is just bad taste. If Igor thinks that someone acted not the way it is acceptable he would already made this clear. Moderator rights already got revoked if someone didn't had a common sense how he should act like.. Was everything perfect ofc not -  or at least I would maybe solved things different, but mistakes happen and from what I saw no major mistake happened.. You got your thread back after things clarified even the restrictions got revoked. The only stuff which is 'censored' from you is where you entered a thread which was used by proved spammers to get the first mod approval just to bloat the forum after its with spam IMO that whole thread can go to trash cause it doesn't add any value to armbian but let others decide that. And your answers there honestly were just a try to make people angry so that you get a reaction nothing of value for ambian as well.. just another thread which wastes peoples time.
     
    So if you really wanna do some research (this here got the research tag removed by myself cause it's ranting not research) you could spend some time to get something out of your paperweight and see how far you get. likely this time is better spent as starting another discussion about random claims and insults to people here. Even when I think balbes is right and this box is a waste of time, it might be a good one to learn things on your own instead of pushing other people to do the work for you. And even when not.. at least you only wasted your time and not everyone else' time.
     
     
  14. Like
    chwe got a reaction from OrangePee in Censorship 2020   
    well that one escalated quickly.. and due to all the notifications popping up I had to follow most of the crap happened here.. And first before I even try to sum this up. I suppose you change your nick immediately to something else.
     
    You started with a thread about a dirt cheap TV box which you already bought and then tried to convince others to buy it as well cause it's cheap and somehow in the hope armbian will run on it.. This one got deleted by @TRS-80 . Which might be an overreaction. Depending on how you read the rules he had the right to do it.. I would probably just moved it to TV boxes so that it get read by the right persons namely @balbes150 who more or less maintains 'armbian on TV boxes' on his own. Most others doing development are for good reasons not interested in TV boxes (even with schematics it's mostly a pain if things like a proper DT don't exist from the vendor.. But instead of trying to get this in a better shape you tried to find every possible sub-forum to tell everyone that you're pissed-off that he deleted your first post here and there.. since he set you back that everything must be approved it just bloated my messegeboard more with stuff I actually have no passion to deal with.. After seeing that you bloat around everywhere, it was probably the right decision to revoke your post right upon approval by a moderator.. I'm not a fan of such actions cause it's just more work for me to approve x posts more per day..
     
    A small hint the few bucks you spend for an SBC or for TV box is nothing compared to the $ you spend for support. If balbes thinks it's not even worth to have a briefer look at a box he will have likely good reasons for that (I don't even waste my time for TV boxes anymore.. you don't know what you get, things can change cause the vendor runs out of something and replaces it with something else e.g. another wifi chip other ram other whatever he runs out... and then he has to deal with the fall out of that cause people show up here that their similar looking TV box doesn't work as expected). Who will then dive into it to fix it? Will you be around and fixing all this stuff? Or is it then up to him to explain the new users that "this batch works" and this batch doesn't cause component x changed and there's no support for it? It's mostly the second.. And why should he do that for a TV box he's not interested in at all? He answered quite polite that it's a boring TV box he's not interested in.. After that you tried to convince that this is somehow valuable for armbian for whatever reason. I don't think it is.. people here around know that the W905 variants are mostly well supported in the kernel a well supported SoC doesn't give you a well supported TV box/SBC.. As you both figured out the only network connection on this board is crap and due to limited other options (only 2 USB2 every other possibility e.g. attaching network over USB will limit a limited TV box even more making it a wasted 18$ for everyone who buys this box based on that thread in the hope that enough pressure on balbes will convince him to look at it). And that around a time you didn't even tried to get your research done if and how this thing can be re-flashed, that might be your starting point https://lmgtfy.com/?q=amlogic+s905+firmware+update+over+USB ) and then from the picture:

    you see on the right side VCC RX TX GND? that's likely your debug UART and 'most likely' it's 3V or 3v3 so setting up your debug UART see what comes out use google or bing or whatever searchengine you prefer. so that you get a clue what is there if people already did something with the bootloader there or a similar one (if it's u-boot and you can interrupt it printenv gives you some nice hints) post your finding and your guesses and maybe someone will give you a hint here and there how you should progress. That would show @balbes150 that you're actually interested in doing something not just soak up his time, maybe not cause I think he has enough valid points to declare this box as a waste of time.. And the TV box subforum is still a forum about armbian on TV boxes not elec"something" on TV boxes.. If you want that ask the guys there to support your new paperweight maybe they're willing maybe they're not - that's then their decision. But except the confirmation that there's a crap wifi IMO your thread provided nothing of value to armbian. Well at least those involved in the whole TV boxes stuff now can honestly say that you shouldn't buy this one if someone asks for advice which TV box he should buy (and if you want something which works without much pain it's a good idea to do your research first and then buy).
     
    Why should it get deleted? Maybe cause it's not about censorship here? If this would be about censorship we would have deleted your account all your posts and it would look like you were never here. That's censorship.. Locking a discussion where everything is said and all needed persons made clear that support for it wont happen isn't. It's just keeping the forum somehow readable. Tagging randomly people to waste their time as well is just bad taste. If Igor thinks that someone acted not the way it is acceptable he would already made this clear. Moderator rights already got revoked if someone didn't had a common sense how he should act like.. Was everything perfect ofc not -  or at least I would maybe solved things different, but mistakes happen and from what I saw no major mistake happened.. You got your thread back after things clarified even the restrictions got revoked. The only stuff which is 'censored' from you is where you entered a thread which was used by proved spammers to get the first mod approval just to bloat the forum after its with spam IMO that whole thread can go to trash cause it doesn't add any value to armbian but let others decide that. And your answers there honestly were just a try to make people angry so that you get a reaction nothing of value for ambian as well.. just another thread which wastes peoples time.
     
    So if you really wanna do some research (this here got the research tag removed by myself cause it's ranting not research) you could spend some time to get something out of your paperweight and see how far you get. likely this time is better spent as starting another discussion about random claims and insults to people here. Even when I think balbes is right and this box is a waste of time, it might be a good one to learn things on your own instead of pushing other people to do the work for you. And even when not.. at least you only wasted your time and not everyone else' time.
     
     
  15. Like
    chwe got a reaction from Igor in [Moderation] Resources, Tips, Guidance   
    will likely end in me ignoring this queue even more means more work for the newcomer mods here.
     
    people will then just ask somewhere else.. and someone remembers this post?
    veni vidi vici... and I remember I unlocked this post back then. at least devs not really tied (yet) to armbian may only post a few stuff here to let us know hot to fix things. We should not make it harder for them to contribute. IMO I prefer to deal with more annoying questions than with missing good contributions which I've to search then in someones gist or on someone else's github repo.. cause we scared him away..
     
    you think this survives the usual add blocker most people have installed? test it and if it works why not..
     
    those who want will find each other no matter how much a thread is messed.. e.g. the rockchip guys here have a >2500 posts long PM thread talking to each other (and yes Igor you're out there on purpose, I didn't wanna float you back then with all the OT stuff and it all started with a discussion about beer back then.. ). If I think it's 'important' that someone is aware of my post I just highlight them in the thread. If I'm just frustrated about rockchip again I rant in PMs so that only those which shouldn't get disturbed get disturbed..
    Another example those guys here:
    found each other and share the pain to get an RTD SoC working. They had barley support from our side (me being the only one having the W2 board and honestly I didn't spend much time with it - just to much pain to deal with atm)
     
    I think we should avoid 'overmoderating' the forum. It is a 'technical' forum and it's driven by development around armbian but there will always be people which just come with 'please support my random petproject' and I think we have to deal with those. Somehow.. The forum is a melting pot of people around arm some are more experienced some less (I started with some dirt cheap orange pi boards - zero and 2g-IoT - with no clue about booting on arm at all and now mostly focused on u-boot/kernel related stuff)... You don't wanna push those guys who can evolve out by being a dick in the first term... I'd rather just ignore those only requesting features without meaningful contribution, they might see that nobody cares about their petproject and move on or evolve to getting things done on their own. We're not super welcoming like it is the new 'trend' around the internet and that's IMO fine (good contributors like @piter75 find their way into the community without getting a 'warm welcome' with his first post ). 
     
    For the development/boardbring up.. We once had a dedicated sub-forum for that:
    https://forum.armbian.com/forum/22-board-bring-up/
     
    somehow one of the few examples where this was used was for mt7623/BPi R2 or RTD 1295 (both didn't really made it) but at least the threads were mostly focused on development not on bloating.. Maybe something like this can work? And maybe such a thread can then be moderated a bit more to keep it focused on development and not random features request/petproject support who knows..
     
     
  16. Like
    chwe got a reaction from TRS-80 in [Moderation] Resources, Tips, Guidance   
    will likely end in me ignoring this queue even more means more work for the newcomer mods here.
     
    people will then just ask somewhere else.. and someone remembers this post?
    veni vidi vici... and I remember I unlocked this post back then. at least devs not really tied (yet) to armbian may only post a few stuff here to let us know hot to fix things. We should not make it harder for them to contribute. IMO I prefer to deal with more annoying questions than with missing good contributions which I've to search then in someones gist or on someone else's github repo.. cause we scared him away..
     
    you think this survives the usual add blocker most people have installed? test it and if it works why not..
     
    those who want will find each other no matter how much a thread is messed.. e.g. the rockchip guys here have a >2500 posts long PM thread talking to each other (and yes Igor you're out there on purpose, I didn't wanna float you back then with all the OT stuff and it all started with a discussion about beer back then.. ). If I think it's 'important' that someone is aware of my post I just highlight them in the thread. If I'm just frustrated about rockchip again I rant in PMs so that only those which shouldn't get disturbed get disturbed..
    Another example those guys here:
    found each other and share the pain to get an RTD SoC working. They had barley support from our side (me being the only one having the W2 board and honestly I didn't spend much time with it - just to much pain to deal with atm)
     
    I think we should avoid 'overmoderating' the forum. It is a 'technical' forum and it's driven by development around armbian but there will always be people which just come with 'please support my random petproject' and I think we have to deal with those. Somehow.. The forum is a melting pot of people around arm some are more experienced some less (I started with some dirt cheap orange pi boards - zero and 2g-IoT - with no clue about booting on arm at all and now mostly focused on u-boot/kernel related stuff)... You don't wanna push those guys who can evolve out by being a dick in the first term... I'd rather just ignore those only requesting features without meaningful contribution, they might see that nobody cares about their petproject and move on or evolve to getting things done on their own. We're not super welcoming like it is the new 'trend' around the internet and that's IMO fine (good contributors like @piter75 find their way into the community without getting a 'warm welcome' with his first post ). 
     
    For the development/boardbring up.. We once had a dedicated sub-forum for that:
    https://forum.armbian.com/forum/22-board-bring-up/
     
    somehow one of the few examples where this was used was for mt7623/BPi R2 or RTD 1295 (both didn't really made it) but at least the threads were mostly focused on development not on bloating.. Maybe something like this can work? And maybe such a thread can then be moderated a bit more to keep it focused on development and not random features request/petproject support who knows..
     
     
  17. Like
    chwe got a reaction from aaditya in RK3399 Stable? Move subforum from Development to Bug Tracker?   
    IMO there's no reason to rush here.. before we haven't cleaned some of the mess in bootloaders I don't see much of a reason to change things. Yes the boards run surprisingly stable, but there are still odds here and there. I think most of the overlay features are not fully tested (compile log at least indicates that some of them might need some inspection as well) and we still have various kernel sources for the bsp kernel which needs to be cleaned first, and as just noticed, the odds regarding rebooting starting again with the pinebook.. There isn't much of a difference between the bugtracker forums and the dev forum at all. 
     
    And 4.4 kernel gets old (no matter it is supported well or not), so might hit the fallout of this with the next versions of debian/ubuntu. So the same thing happened with 3.4 on sunxi shouldn't bite us again (kernel to old for recent ubuntu/debian but a bunch of interesting features are only available there).
     
    they could be marked, "potential harmful to your family" and people would still use it productive... our "supported" definition is so generic (https://docs.armbian.com/#what-is-supported) that it means in fact nothing.. (I'll burn in hell for that statement I know).. At least when people run into problems they should be aware that things are working progress right now. Most basic seem to work without major issues, but for everything a bit more fancy (camera, display etc) there's not much tested and proved to work right now. Multimedia works only on half of the boards (those belong to rk3399).
  18. Like
    chwe got a reaction from piter75 in Armbian 20.02 (Chiru) Release Thread   
    well you've no chance I already set up the pinebook in rk3399 with u-boot 2020:
     
    U-Boot 2020.01-armbian (Jan 21 2020 - 23:08:47 +0100) Model: Pine64 Pinebook Pro DRAM: 3.9 GiB PMIC: RK808 MMC: dwmmc@fe320000: 1, sdhci@fe330000: 0 In: serial@ff1a0000 Out: serial@ff1a0000 Err: serial@ff1a0000 Model: Pine64 Pinebook Pro ## Error: Can't overwrite "serial#" ## Error inserting "serial#" variable, errno=1 rockchip_dnl_key_pressed: adc_channel_single_shot fail! Net: No ethernet found. Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 2940 bytes read in 6 ms (478.5 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1 143 bytes read in 6 ms (22.5 KiB/s) 7118384 bytes read in 752 ms (9 MiB/s) 20722176 bytes read in 2178 ms (9.1 MiB/s) 72693 bytes read in 17 ms (4.1 MiB/s) 2698 bytes read in 9 ms (292 KiB/s) Applying kernel provided DT fixup script (rockchip-fixup.scr) ## Executing script at 39000000 ## Loading init Ramdisk from Legacy Image at 06000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 7118320 Bytes = 6.8 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 01f00000 Booting using the fdt blob at 0x1f00000 Loading Ramdisk to f5853000, end f5f1cdf0 ... OK Loading Device Tree to 00000000f57d8000, end 00000000f5852fff ... OK Starting kernel ... [ 2.647157] Internal error: Oops: 96000004 [#1] PREEMPT SMP  
    it seems it doesn't like my new DT.. but u-boot works fine and blobfree..
  19. Like
    chwe got a reaction from TonyMac32 in Armbian 20.02 (Chiru) Release Thread   
    well you've no chance I already set up the pinebook in rk3399 with u-boot 2020:
     
    U-Boot 2020.01-armbian (Jan 21 2020 - 23:08:47 +0100) Model: Pine64 Pinebook Pro DRAM: 3.9 GiB PMIC: RK808 MMC: dwmmc@fe320000: 1, sdhci@fe330000: 0 In: serial@ff1a0000 Out: serial@ff1a0000 Err: serial@ff1a0000 Model: Pine64 Pinebook Pro ## Error: Can't overwrite "serial#" ## Error inserting "serial#" variable, errno=1 rockchip_dnl_key_pressed: adc_channel_single_shot fail! Net: No ethernet found. Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 2940 bytes read in 6 ms (478.5 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1 143 bytes read in 6 ms (22.5 KiB/s) 7118384 bytes read in 752 ms (9 MiB/s) 20722176 bytes read in 2178 ms (9.1 MiB/s) 72693 bytes read in 17 ms (4.1 MiB/s) 2698 bytes read in 9 ms (292 KiB/s) Applying kernel provided DT fixup script (rockchip-fixup.scr) ## Executing script at 39000000 ## Loading init Ramdisk from Legacy Image at 06000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 7118320 Bytes = 6.8 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 01f00000 Booting using the fdt blob at 0x1f00000 Loading Ramdisk to f5853000, end f5f1cdf0 ... OK Loading Device Tree to 00000000f57d8000, end 00000000f5852fff ... OK Starting kernel ... [ 2.647157] Internal error: Oops: 96000004 [#1] PREEMPT SMP  
    it seems it doesn't like my new DT.. but u-boot works fine and blobfree..
  20. Like
    chwe got a reaction from TRS-80 in [Moderation] Resources, Tips, Guidance   
    I wouldn't think 3 lines is a bloated footer (I've 3 lines I didn't update in a while - maybe I should)..
     
    A few thoughts about moderating (and I probably do mostly a bad job here cause I didn't do much moderating in a while - well I got that job somehow by mistake ).. I'm a fan of "as less as possible as much as needed". If someone chooses a obviously wrong title maybe change it.. If the title is not best, he'll learn from lack of attention that he might do better next time.
     
    I don't deal much with unfamiliar hardware anymore.. E.g. there are some parts in the forum you won't find me. Mostly Armada and amlogic. We have people knowing the odds of those boards so they can deal better with it than me. Moderators moderate first responders help. For some platforms I'm both (e.g. rockchkip) for others I just unlock topics and have a quick view if there's something odd about it (e.g. hidden shit in links). But different mods will have different styles, and as long as it is not harmful to the community at all people need to deal with it. Depending on which moderator you get you might get a different style of answer. It's not that we have to follow some cooperate guidelines how an answer should look like.
     
    If you split, merge or delete you might inform people by leaving a short post why you did it and where the other part can be found. If you move things I mostly let the checkbox with the 'simlink' so that the guy sees where his post is now.
     
     
  21. Like
    chwe got a reaction from aaditya in Rock PI 4 A not starting   
    blind-shot to try to debug doesn't make sense. Without the (full) console log it doesn't make sense to step into this. So first, make sure you connect to the right UART to get the debug output.
    For the bootorder:
    https://lists.denx.de/pipermail/u-boot/2017-April/285493.html
    http://rockchip.wikidot.com/boot-sequence
    (even when I'm not sure the second one is fully complete, I guess it's mostly achieved over the choosen node)
     
    if you look at the sources of radxas bootloader, and we assume that's the one which is on your eMMC:
    https://github.com/radxa/u-boot/blob/6d910b7f12318e5a5bb8d1b2093fe5a9ba17dfce/arch/arm/dts/rockpi-4b-linux.dts#L26
    chosen { stdout-path = &uart2; u-boot,spl-boot-order = &sdhci, &sdmmc; };  
    in their u-boot eMMC should have priority over SD card. If you now look on our bootloader:
    chosen { stdout-path = &uart2; }; it's not as clear anymore.. according to rockchip it should look in SD-Card first. But I could be that they achieve this over the choosen node, no idea what happens then if it's not defined there. Also their docs rely on their u-boot. We used a patched one based on theirs.. So another option where things can change. A bunch of variables and things go messy.
     
     
    debugging your issue without a bootlog isn't a option for us. So either you can provide a full bootlog (and that starts a way earlier than when the kernel takes over) or you've to follow @martinayotte recommendation and remove the eMMC.
     
    BTW for the rockchip maintainers here (adding @TonyMac32 @piter75) It might make sense to add a proper choosen node to all our DTS files to get a predictable bootorder for all RK3399 boards.
  22. Like
    chwe got a reaction from piter75 in NanoPI 4MV2   
    there's a tool to test this:
     
    https://github.com/ayufan-rock64/linux-build/blob/02fae982767ca242009baaf995f7ce64b5d82469/recipes/gmac-delays-test/range-test
     
    @tkaiser wrote one too back then.. but I can't remember where I have it anymore.. Nevermind
    https://github.com/ayufan-rock64/linux-build/blob/02fae982767ca242009baaf995f7ce64b5d82469/recipes/gmac-delays-test/range-test#L3
    https://github.com/armbian/build/issues/546
     
     
  23. Like
    chwe got a reaction from Jack953 in Orange pi 4   
    for those interested in a board bring up
     
    the kernel DT can be found here (it's the commit bringing the board up, so rk3399-orangepi.dts is the most important here):
    https://github.com/orangepi-xunlong/OrangePiRK3399_kernel/commit/ca6af5e3a951938bcd2516ed410e1a3173d640d2#diff-a6cab00e04d1f9f954107a5555ea160a
     
    this is (likely) the used defconfig for u-boot:
    https://github.com/orangepi-xunlong/OrangePiRK3399_uboot/blob/6f4a1947dd2e648c36d53dd1410679865c6b257b/configs/rk3399_defconfig
     
    this might also be of interest for the first stage loaders:
    https://github.com/orangepi-xunlong/OrangePiRK3399_scripts/blob/a62950cafa093437f55eb0ed5a846963edbf006f/lib/compilation.sh#L40-L45
     
    it seems xunlong did quite some cleaning of their sources to build proper images.
  24. Like
    chwe got a reaction from gounthar in Orange pi 4   
    for those interested in a board bring up
     
    the kernel DT can be found here (it's the commit bringing the board up, so rk3399-orangepi.dts is the most important here):
    https://github.com/orangepi-xunlong/OrangePiRK3399_kernel/commit/ca6af5e3a951938bcd2516ed410e1a3173d640d2#diff-a6cab00e04d1f9f954107a5555ea160a
     
    this is (likely) the used defconfig for u-boot:
    https://github.com/orangepi-xunlong/OrangePiRK3399_uboot/blob/6f4a1947dd2e648c36d53dd1410679865c6b257b/configs/rk3399_defconfig
     
    this might also be of interest for the first stage loaders:
    https://github.com/orangepi-xunlong/OrangePiRK3399_scripts/blob/a62950cafa093437f55eb0ed5a846963edbf006f/lib/compilation.sh#L40-L45
     
    it seems xunlong did quite some cleaning of their sources to build proper images.
  25. Like
    chwe reacted to karabek in OPi Zero: XR819 wifi broken in new builds   
    Users wanting to use debian builds with NetworkManager/wpa_supplicant should add the following lines to /etc/NetworkManager/NetworkManager.conf:
    [device] wifi.scan-rand-mac-address=no Ubuntu builds (bionic, focal) already contain these lines.
     
    This seems to solve the current issue on systems with the xradio wifi chip (opi zero, nanopi duo etc.)