StuxNet

Lol. That's exactly what I meant. Leave the non automatable stuff for the users which leaves Armbian to devs That's why I chose X and Y because there are too many board variables out there to list them all! However at the end of the day Armbian would be able to choose X and Y fundraising campaigns. Just because it's the World Wide Web doesn't mean it has to be the Wild Wild West. Armbian could pick and choose which boards are more aesthetically/functionally appealing to the community (that put's their money where their mouth is) and then make that support/development a priority. I think we are already seeing a form of this happening with Olimex though. They seem to be open [reliant even] to the idea of Armbian support companies like FriendlyArm seem to maintain masquerading behind their own kernel, which probably has ties to Armbians 'openness'.

You seem to know what you're doing since you've provided PS and SD card verification.... but I've gotta ask. How are you writing the kernel to the SD card? I don't mind being the bad guy here and it's the only newb thing you don't specify.

This guy is experiencing the same exact detailed issue as you. Attempted to create kernel. Kernel doesn't boot. Kernel complains of Ethernet missing. End user wrote image with `dd` command. The only difference is that OP is using OPi Zero Plus, not OPi Zero.... big woop. Simply try with Etcher, report back. That might be hard though without a UART adapter... get MitchD to do it for ya xD Sup MitchD? Keep up the good work.

cyclic redundancy check I've never built my own kernel (I let Igor do that for me) but I know a bad 'hard drive' when I see one, from my computer repair days. BAD CRC = cyclic redundancy check error Make sure your SD card image writing software is 'approved' to work with armbian. ie: Etcher This is (as far as I know) the only Armbian 'approved' method. Likely because Etcher verifies the image after writing, by default. Whereas dd and Win32Disk Imager (uses dd) don't require verification, of what it just wrote. So..... bad SD card? Prove it is/isn't then come back asking for help. Otherwise, I've received bad CRC errors due to power cables going bad at pain points. I think. Might of been that I was writing using Win32 at the time xD IDK for sure because I immediately tried fixing both birds with one stone as opposed to troubleshooting individually. So double check that Power Supply if you haven't already. If you haven't already, see 0, 1 and 2 links in my signature. ;D

I don't know much about device tree overlays or kernel configs, since there hasn't been a compulsion for me to learn.... yet but I have been able to get i2c screens and Serial over USB via OTG working on the NanoPi NeoAir. And by 'I' Have, I mean others have lead the way and I've stood on their shoulders Don't know what exactly you wanna do with i2c/OTG on NPNA but maybe you'll find something useful here: https://github.com/BiTinerary/PocketServerPi It's the best I can offer, otherwise you'll have to wait for better, more experienced, specific direction. Good luck.

Yea dudes. It's called a UART cable. Buy one, it's worth $20 and costs you $2.... http://www.taydaelectronics.com/bte13-007-cp2102-serial-converter-usb-2-0-to-ttl-uart-ftdi.html You should really buy two while you're at it. It's worth it. @Matthai It took 3 posts for you to volunteer that not only do you not have the root/any password but you also don't have physical access to the machine? I'm done giving suggestions, as all others should be as well. Any advice is (by admission) filtered through someone else, both ways and IMO unreliable and divergent. You want root access to an offsite computer that you don't know the password to? Psshhh! Tell that to every malicious hacker ever and the 100+ daily [banned] script kiddies attacking my FTP. Real talk. SSH isn't granting you all out permissions over everything prolly because you need to set something up physically first. Full blown root access over SSH without keys and authentication would just be stupid. Tell your offsite buddy to delete the lines (as done) then take an extra 2 seconds to setup the 'first' default password and try again. Especially after generating some SSH keys. Also, if you knew anything about Armbian you'd know that you can't 'just pressed enter' as the default, root password. Again, that wouldn't be wise. I'm 3 sentences past done. Stux out.

Wanna reply with an attachment of the exact script you used? I've tried everything. Porting over the Friendly Arm script to toggle AP MODE (works flawlessly), manually config/installing, waiting months for Armbians automated AP Mode (armbian-config) etc... The furthest I could get was a SSID to show but I could never actually connect to it with a device. Granted it's been a while since I revisited it but looking to see if you have a quick easy solution that worked for you. Thanks.

Tinkering with API's is fun. Always wanted to allocate the scripts and tools made over time and allow quick access to the data they can provide. Never liked the idea of leaving a power hungry Desktop running to have access to it and am too paranoid to leave any SBC (FTP/WebServer) connected to the World Wild West for too long. As seen with the Mirai Botnet/DYN attacks. So my answer was to have something low power (SBC and armbian) that was at least 'secure enough' for me to let it interface with the world. So this was made: https://github.com/BiTinerary/PersonalAPI In a nutshell this is how it works: Scripts on an OPi Zero that make API calls, scrape web data or w/e. I want to collect this data, check a sensor, trigger... from my phone. SMS/MMS an email to users inbox containing a keyword. Weather, Beer, Water plants, etc... The script uses a dictionary.txt file to constantly check the inbox for keywords. When one is found, it executes the key's respective value. ie: Key = Forecast. Value = Weather API call. Any returned value or echoed statement is passed as a string and sent as a reply, back to my phone. The only security concern is that anyone can fire off one of these scripts by sending a spoofed message, as a specific address, containing a predefined keyword. This might be a big security concern for some but personally, it's negligible. Not only do you need to know the address to spoof, keyword to send, parameter to pass, syntax to use, etc... but you would only succeed in entering a sandbox that I control. Not to mention, SMS two factor authentication can be implemented later on and message content can be obfuscated to oblivion. The sky is periwinkle but the grass is still green. Anyways... Maybe someone can use the source code. Hopefully someone can use the source code. What are the thoughts of the community? Am I off my rocker? Suggestions on what you'd like to be add? Always looking for new ideas and projects.

Uh... I'm pretty sure that was answered. Boot up a linux box. Like from another Orangepi, SBC or computer and mount the SD card. Find that /etc/shadow file. No password necessary from a 3rd party machine. Remove the second field mentioned related to the user. On my machine, there's a field for root and for stuxnet sudoer. So... You can always change root password from a sudoer profile afterwards. Give the recommendation a try before questioning the recommendation. I don't even think you would have to "Make a copy in case things go south." because if you can't login, things have already gone south. However, it's simply good practice to make a backup of the file and is forward thinking. So do so.

I think paid/unpaid and branching is a fools errand. Anyone who expects to have full support for any rando board isn't going to know the reason for the difference (much less make the Redhat/Fedora association) because they didn't even bother to research into the board or it's kernel before purchase to really get a feel for it's abilities, limitations and current status. Stable/Experimental, in my mind, is more than sufficient. Keep it as a single branch. Do think things can get a little heated especially with Tech support but no different than any other forum and especially no different than real life tech support, believe me. I have some stories. I kinda zoomed through the past few comments but I liked the idea of offering a slightly tiered system in terms of payment. For instance, if I could donate towards Armbian dev on a specific board, that would be dope. I would throw several pretty pennies at NanoPiNeoAir. To be honest though, it probably wouldn't affect my donating habits, which is as much and as often as I can afford. W/e though, I'm a strange fruit ;D Maybe a trend could become visable though if hundreds of cheapos buy OPi Zeros and never donate to the dev of it. Something can be said for the demand and visibility to Armbian by supporting it but something can also be said for the willingness and ability to support. For instance: ~ "Donate here to support X feature of Y board" *Thermometer to goal* ~ Info graphic: Armbian on 9999 OPiZero boards. $50 donated. Armbian on 300 NanoPi Neo boards. $600 donated.

Do you (or the OP) really need to 'unbrick' it? To my understanding that process is for when you have a system that absolutely needs to be recovered. ie: You have spent hours installing/upgrading/customizing but after an update can't boot and didn't bother to make a backup image. If you don't care so much for the custom setup then just make a new image. Are you sure this >> https://docs.armbian.com/User-Guide_Getting-Started/#how-to-prepare-a-sd-card << isn't more applicable? Are you sure your SD card is actually good?

Do what Igor mentions. I'm pretty sure you can boot the board so here's my 2 cents. 1 day - 6 weeks is a helluva difference! If something hard/software was happening I would assume it would be at a much more regular interval than 1day - 6 weeks but absolutely don't rule it out. Just my gut but still a possibility. The computer technician in me says it's a local problem or user error. Both OPi's have the same defect? Unlikely. So here's what I mean and the ideas you ask for. Are you un/plugging devices on, in or around the device? What kind of power adapters are you using and are they both the same? Where are they powered? The same outlet? Try moving them to different locations or at least do different things to different boards and see if the issues remain, change or not. To quote Igor "Please describe your setup as best as possible so we know what your operating environment is like". This includes adapters, the 'buttons, leds' and webserver you're using, etc... I'm curious about this 1d-6wks thing. You mention your running python scripts so it wouldn't be hard for you at all to make a separate script that logs the uptime every second. When the device abruptly turns off you'll know how long the device was actually on. Then boot and run it again. Maybe this will give you a better idea of if it's actually 1d-6wks or if there's more of a pattern. In effect possibly determine what was being done around that time. Python sample script. Its coded to run. import time, subprocess def uptimeLog(uptime): with open('uptime.txt', 'w+') as log: log.write(uptime) while True: uptime = subprocess.check_output('uptime', shell=True) uptimeLog(uptime) time.sleep(1) To any haters: I realize it could probably be done in pure bash but.... I'm familiar with python enough to write working/simple code without debugging. Also .py might be overkill for such a simple task but once learned, good coding practices should always be used. ;D

What was the cause of the "Power Loss on [your] house"? Brown out? power surge? Weather? Was it the whole house? And how did you "fixted [your] Power Problems"? Reset a breaker/fuse? Wait for power to come back on? If you updated the bootloader, then you don't have a similar problem. (power outtage) In what manner did you update your bootloader?

I think mod approval should still be a thing, it's not meant to replace our work as mods. It should be stupid simple quiz asking the bare minimum questions that covers the most irritating topics. I agree, @tkaiser would be perfect to choose what this consists of Like 3-5 questions. Some might even only have one answer xD Perhaps more quizzes could be added later on, for ranks which comes with digital incentives. w/e. @TonyMac32 The quiz isn't meant to keep out bots. It's meant to force consumers to engage with the absolute Armbian basics in the most preschool of ways. @zador.blood.stained "better designed toubleshooting page in the documentation." This is true, but again. The quiz idea is mentioned to weed out the pompous loonies who post without grasping the basics. Especially those who aren't even going to read the troubleshooting page. The quiz, in my mind should forcefully, very briefly, engage the consumer. I agree that, that group of people might be slim to none comparatively. More experienced Mods would be more familiar with this than me. @Igor IF we ever decide to go the quiz route, I'll put my money where my mouth is and donate for a year (for the quote in your link) or I'll look into a MacGyver'd, free, alternative. I'm good at that ;D I take it the link you provided, is a quiz feature that directly hooks into the Armbian forum software? If that's the case, I'll throw down the scratch.

Important, small bit of info. Cheers for any frustration this might save others. "...at least in the slots used on Orange Pi board"... is an important detail too because I don't think this is necessarily the case with (at least) NanoPi NeoAir boards. I ordered a batch a while back and two had a faulty switch upon arrival. The fault prevented one SD card from fully engaging and prevented another from even ejecting. I absolutely didn't like the idea of potentially not being able to remove 32GB Micro SD cards (not to mention SD/NAND swapping was crucial to project) so I went ahead and removed the spring action arm, which in both cases were visibly defective and nand-sata-install still works like a charm. They just don't 'shoot' out like they used to

I know your issue with SPI has been solved, I ran into the spidev1.0 dealio myself but just thought I'd quick mention what SPI library I've used in the past, additionally what I will be testing/trying to get working in the future. I use this SPI library, specifically coded for OrangePiZero: https://github.com/rm-hull/OPi.GPIO So far as I can tell it's used practically verbatim to other SPI libraries I've seen. ie: pyA20.gpio, ports of RPi.GPIO, WiringOP and the such. I plan on also using the same authors libraries for using or testing OLED/LCD screens that I have. (SSD1306/PCD8544/ST7735/Etc...) https://github.com/rm-hull/luma.oled

Reading this made me realize that it would be pretty dope to have a mandatory 'quiz' for newcomers. At least a quiz before being allowed to post, PM or w/e. Cover the absolute basics that are.... Which IMG burning software is recommended by armbian? A.) Etcher B.) Win32 DiskImager? How do you know you have a proper power supply? A.) Cable? B.) Multimeter? C.) How can I possibly know? Redirecting newbs to a 3+ question quiz, that wouldn't even need correct answers, wouldn't be hard but I have no idea how you'd do that or if it would even be possible to integrate into the forum for granting posting permissions, etc.. I completely agree though, "You must FORCE us." Because personally, I rarely read every ReadMe/FAQs/Etc.... out of technical hubris and the fact that 9/10 I do just fine. As result I arguably save time just jumping right in as opposed to reading stuff I already know or will learn along the way or through osmosis. Like Bubba mentions though, every once in a blue moon that 1/10 times comes back to bite me. The difference is that I always keep an open mind to the stupid things. SD Card, New Micro USB, hardware, software, etc... And when I'm being bitten, I never take it out on the free community who gave it away in the first place while completely rejecting any free help. ie: I'm always left smacking myself in the head, not someone else. Anyways, that's a little winded to say, It sure would be nice to force newbs to educate themselves, more so if their posts content is going to be about the basics.

Yea I was referring to that thread. Don't get me wrong though. I could care less what you decide to do with your time, just wanna see Armbian succeed. I'm not sure how pivotal your role is/n't (not trying to trivialize what you do) in the various aspects of development but I know it's important enough to not have to deal with those snide remarks. If you honestly thinks it's water off a tutles back and in defense of other, future Google searches. That's some promotional SEO forethought. More power to you. As far as the quote above goes, you mentioned how it's a good example for mods a couple times. It didn't go unnoticed. ;D Not exacty sure what you mean by "I'm resigning here now since I feel it's still too much »Igor's image« than »Armbian« but maybe that will change in the future." but at least I'm aware of the context that the "Common Problem" you link, refers to. xD

As mentioned, that's where you would break it out to manufacturer, not necessarily each board. It's a good point nonetheless and speaks on the 'hardcoded' issue of doing it they way I mentioned. The forum links is a good point I overlooked. The downloads page does link to the specified boards subforum, it wasn't always like that ;D Perhaps I'll just use that as navigation. This kinda helps me realize though that my issue is mostly with when you get to that page. It's just every post, ever. Maybe breaking that out one more time to topics? Bluetooth, Wifi, making the pins better, recently asked questions, etc... Slimming down from 16 pins to 1-5 which condense the FAQs, technicals to one place. As TonyMac32 mentions, maybe have those pins just be an aggregate of schematics, images, diagrams, static info, etc... to me this means one thing especially since "diagrams and images are realistically impossible in this format." Pin >> Github >> Markup >> Schematics, pics, pinout, w/e. Maybe I'll start collecting all the schematics I can find, breaking them out to boards and provide it as an example of what I'm talking about. That might actually be a nice 'laid back' project for me. I know Armbian has the 'Wiki' section but I'm thinking more along the lines of those colored schematics, not just tables. Also perhaps how certain periphs (SPI, i2C) connect to the corresponding GPIO for certain boards.

+2 points for chill. I'm kind of drawn to a 'cool down,' especially given the linked threads. Tkaiser, you're a dev right? It would be way cooler if you spent that time developing rather than getting into it with someone who can't be helped. I'm not gunna tell you what to do though. Just my thoughts. Also, you can't spend all your time behind a terminal and lines of code, so I get it. The idea of discussing the layout of the forums is interesting. It's way confusing to newbs (myself included). The only way I can navigate this place is via search. 16 pins in a subforum is a bit much but navigation as a whole is more important IMO. I couldn't tell you off the top of my head which one of my boards, (NanoPi Air, Orangepi PC+, OPi Zero, Orangepi, NanoPi Neo, etc...) corresponds to what Allwinner chip. Now granted, all of these boards are listed as sub forums, after you click on a random chip. However my point is, first impressions to the forum aren't good. I've got to go 3 clicks deep to get to the board I'm interested in. Where I'm then greeted with every single post ever made for every board that uses that chip. I don't think it's necessarily a question of condensing/renaming forums, subforums, etc... so much as it is allowing each board to have it's place. Similar to the https://www.armbian.com/download/ page. That minimalist design is sick and immediately understandable. Perhaps we should consider something similar for the forum? Tech support Allwinner H2/H3 Orangepi PC+ Nano Pi Neo Air Chip B Board X, Y, Z Projects and Services Software Post Scripts, Python, Shell, ruby... Dev, Build root, overlays, etc... Hardware Mods Porting modules from raspi, etc... Development Whatever you guys want. Granted the idea of having subforums for boards which will inevitably become deprecated isn't intriguing (hardcode == bad). Eventually (if not already) there will be so many boards out there it might get too cluttered. When that happens though we could always reorganize to Manufacturers, then to boards. Instead of boards directly. At least this way to a layman entering the forum they know 2 things immediately. Exactly how to navigate it and can at least see if the solution has been found for the specific board, then broaden their search from there. As opposed to... *click* *click* *everything ever!* The forum probably makes more sense coming from a dev's perspective but this is coming more from a users perspective. Who's only dev is tied up in personal scripting. This might not even be possible and I have a tendency to be really OCD about these kinda things so... idk. Just my thoughts. Lemme know.

Couldn't agree more about just being polite and the whole fact about how Armbian not directly profiting from board sales. As I mentioned before regarding the alligator clips. Granted I think he's using them for AV to the TV not power if he is though, wow... In any case, I know the v1.4 board has PWR/GND pins directly next to each other. No reason a slipped clip can't short em out.

So what are we arguing about? All those videos prove is that it's hardware. Not software. Which is what we've been saying all along. I find it really curious that you show the OpiZero fully booted, swap everything over, then very briefly show it (not even the TV output) before cutting the video. Then you fully record the bootup and even login of the Raspi. Not to mention your issues up until now were with multiple boards not just the OpiZero. The name of this thread is, problems with OPi PC+, after all but w/e. Here's what I think happened. You shorted a couple/several pins, using your sketchy aligator clips on a brand new OPiZero that you waiting several weeks to get. Now you're upset and looking to put the blame on someone. Even if that's not true, it still remains that you might have accidentally. Alligator clips can be slippery, next time use proper connectors. It's not software. Have you ever even bothered trying a UART as suggested multiple times? You never did answer my question as to why (if it wasn't hardware) it would be working for literally everyone else. P.s. Lol, regards? Yea right dude. Good day.

I'm not sure the bluetooth is fully functional on the Win+ or not but the entire kernel is experimental as a whole. So expect bugs. That's why when you downloaded it, it was under 'Work in progress' and mentiones 'No end user support' See here:

I'm in agreement with tkaiser, fundamentally, not emotionally I'm inclined to go ahead and lock this thread but since I literally was made a mod two days ago I don't wanna outstep my bounds. I encourage someone else to though. OP. I don't care about the attitude. I refuse to believe that you bought all those boards and they are all bad. I refuse to believe that the issue is with Armbian since I have all of the same boards as you and they work for me, well beyond the issues you describe. Years of professional IT experience tell me you're the problem. (No insult intended) By that I mean you're the common denominator, you're the variable. Your network setup, SD card, a cable, something else or a combination of the above is the issue, which isn't at all farfetched seeing as how you know a thing or two about tech otherwise you wouldn't have purchased the boards. Sometimes things don't work for techies because we tinkered with the wrong thing. If you can't admit that possibility, then that's very telling. We're all going above and beyond trying to help you, your attitude aside. Can you explain to me how all of my boards would be working fine if the issue was software with Armbian? P.s. Why is "you dont know difference between armbian and chineese default rom hohohoho" annoying if that's literally what you expressed?