• Content Count

  • Joined

  • Last visited

Reputation Activity

  1. Like
    pfeerick reacted to tkaiser in Very bad joke   
    Exactly and that's the reason I will only recommend Etcher from now on. It's absurd to waste time on 'bug reports' all the time that are caused by broken burning processes or SD cards.
    As soon as other burning tools implement a mandatory verify after burning I'm open for other suggestions again.
  2. Like
    pfeerick reacted to tkaiser in [Example] Support proposal for ROCK64   
    In my opinion NOT since this thread here contains a lot of confusing discussions that are Armbian internal and only reflect a specific situation now. I'll repost soon in new 'Board Bring Up' subforum, copy&paste the hardware part, the software support part and try to summarize dev thoughts on current situation as neutral as possible.
    IMO it's important to keep 'Board Bring Up' threads focused on the board if we want to use this later as 'landing pages' for users (Google is pretty fast: 'armbian banana pi r2' search already lists new thread as hit N° 2)
  3. Like
    pfeerick reacted to Xalius in ROCK64   
    Yeah I am following the mainlining process for some time now, and some new things went into 4.12.x , we'll see at what pace that continues. As for the documentation there are only the datasheets (SOC+RK805), Part 1 of the user manual and the schematics right now. Tl is trying to get the Part 2 of the user manual released, but I am not sure what is actually in there. RK just today provided some more patches for the 4.4.x BSP, maybe the Rock64 can now stay up longer than 20 minutes :-)
    On the hardware front Tl was looking for last suggestions regarding schematic changes or board layout changes, I think the plan is to go into production as soon it is confirmed that 933Mhz DRAM works on all three (1/2/4GB) variants...
    @TonyMac32 I can ask Tl if he can send you a board sample if you like
  4. Like
    pfeerick reacted to TonyMac32 in ROCK64   
    The mainlining (is that a word?) looks like it just started not too long ago, and given the 4.4 kernel is the one directly from Rockchip, and the... unique coding style I've come across for some of their workarounds, I'd agree for now.  At the very least for mainline the RK805 needs supported, it's a non-start without it.
    If given a board I'd help support if/when the time comes, as much as I'd like to I don't think purchasing one is on my radar just yet, and it would be hard to justify having 2 SBC's that don't actually do anything but absorb my working time...  ;-)
    As a note to Mods, should this be put in the "Board Bring-up" sub-forum?
  5. Like
    pfeerick reacted to zador.blood.stained in [Example] Support proposal for ROCK64   
    Speaking of vendors changing hardware, we have Beelink X2 listed as a "supported" device even though if I remember correctly they changed wireless chip model in later revisions.
    Getting back on topic, I received the Rock64 some time ago (thanks TL Lim), but current software situation to me looks like "blobs, blobs everywhere" + not a lot of low-level documentation + not a lot of mainlining progress, so I probably won't try to integrate it in Armbian for some time.
  6. Like
    pfeerick reacted to TonyMac32 in ROCK64   
    Well, I'm a cyborg, and I still run on 2.6.  . 
    I may have been grounded by the wife after I bought the Tinker Board and then had to buy another box to take up it's intended position in the living room...  :-/  Getting one of these may not be in the cards unless someone has pity on me.  I'm certainly more gunshy at this point, The nanoPi's went so well I got careless and wasted some money.  On the bright side, I've learned an awful lot about a lot of things I wouldn't have gotten myself into before hand, and I'm glad to be learning more.
    Now, speaking of, time to go work on cleaning up Tinker Board messes.  I need to "unfix" something that is reportedly messing with the MiQi and try out Myy's attempt at getting BT working (involves a Rockchip custom rfkill driver)  And figure out if my MAC address is actually stable on the thing or not with Igor's U-boot patch.  I saw more than one value, but I need to make sure I'm not just hallucinating due to distress over the general state of the board.
  7. Like
    pfeerick reacted to tkaiser in Improve 'Support over Forum' situation   
    BTW: If anyone wants to spend a little bit of time on collecting maybe 10 'SD card was the issue' threads, here's an IMO perfect one (since short, some explanation and quick confirmation):
    (this is another one where confirmation is yet missing -- 'Authentication token manipulation error' is read-only rootfs most probably related to SD card crappiness). If such a collection exists (same with power supply troubles) it gets a lot more easy and less time consuming to encourage users to focus on basics first instead of blaming software.
  8. Like
    pfeerick reacted to zador.blood.stained in Improve 'Support over Forum' situation   
    And in each SoC subforum (Allwinner A10/A20, Allwinner H2/H3, etc.) we could create a pinned locked thread named like "List of boards supported in this subforum" to improve navigation.
  9. Like
    pfeerick reacted to zador.blood.stained in Low Data Cellular Plans   
    Unattended upgrades will be the first thing to disable since even without actual upgrades package lists will eat enough traffic (use "sudo apt remove unattended-upgrades" to do that).
  10. Like
    pfeerick got a reaction from StuxNet in Moderator duties   
    Oops! I didn't spot that one either!  Sorry @chwe ... better move it before Igor decides to cut our pay!!!
  11. Like
    pfeerick reacted to Igor in Partial bugfix update   
    Well, also I could reproduce on Hummingboard when trying to connect wireless - it instantly crashed on 4.11.5 while working fine on 4.9.33 ... 
    Of course there is risk when upgrading, especially u-boot, because worse case boot breaks ... but kernel upgrades are more flexible since it "only" breaks some part of functionality at worse. Like in this example. Perhaps this upgrade procedure should be divided and provide more selective relevant upgrades. That should limit down problems. 

    Also possible to apply it to images by default and we gain stability - user must act to get latest updates. Like on deprecated boards.
  12. Like
    pfeerick reacted to tkaiser in Partial bugfix update   
    What about thinking about (discussing) update procedures? Armbian has default, next and dev variants while the distros are horribly outdated (stable, stable, stable) but for whatever reasons Armbian tries to introduce update drama every few months. Why exactly?
    I'm a big fan of users testing stuff if they have been warned they're using experimental software. But if users choose to use something called 'stable' why can't Armbian provide something stable?
    What about differentiating between next (somewhat stable LTS release) and dev (latest and greatest mainline kernel)? Applies even more to u-boot updates (this one -- BTW users and 3rd party image builders don't get it if we remain polite, they simply ignore the contents of the message)
  13. Like
    pfeerick reacted to martinayotte in Improve 'Support over Forum' situation   
    Hi folks !
    I'm overwelmed with daily job as well as looking at this thread ...
    Not even been able to do diagnonal reading ...
    "Time is the missing indredient"  !
    BTW,  I' ve received today my Rock64 (Thanks @TLLim, but don't expect upcoming work/effort until my  overwelmed situation is cleared out)
  14. Like
    pfeerick reacted to Igor in Orange PI Win+ - apt upgrade issue   
    This job is for anyone with minimal inside knowledge. Related or unrelated to Armbian.
    Again - "no support" means we will not provide any information regarding state and problems of moving experimental things. It's expensive and provide negative results. Double negative from our perspective.
    When things are good enough for bare server usage, similar kind of report is found at download page - this and that is not working, ... Currently there are too much problems and no one out of five active developers would like to have yet another burden. We don't want that experimental images are used by end users in first place. Some even use those unfinished work in production and are saying that we are losers and idiots, because upgrade break their wonderfully working system. Yes it happens. It happens way to often and there is no compensation. They don't support as in any way but expect full support from us.
    We came to conclusion that we will not share any information (for end users) regarding WIP work. Developers can find and acquire information from Github commits, from ours an upstream. Everything relevant is written there, but to write a summary ... anyone can.
  15. Like
    pfeerick reacted to TonyMac32 in What does your workbench look like?   
    Most of us probably do some electronics along with the small computers, I've been part of "what does you desktop look like?" threads (terrible, by the way), thought I'd put up (the electronics part of) my workbench:
    I wasn't about to lie and clean it up before hand...

  16. Like
    pfeerick reacted to vlad59 in What does your workbench look like?   
    This will proove I'm older than you .... but I still use my HP48sx from when I was in the University (as a side note I still works perfectly fine after more than 20 years) .....
    I'll post a photo of my workbench soon
  17. Like
    pfeerick reacted to Igor in How to make installed armbian smaller?   
    We have idea, but lack of time, to provide IOT / slim version, which means rework (put under switch) those sections + conduct few tests ... 

    Other option is do uninstall certain - non relevant to your case - packages.
  18. Like
    pfeerick reacted to joselalf in Random no booting issue on OrangePi PC2   
    Weyou, It may be obvious, but are you using a barrel type power supply? Looks like you are using an OTG (USB type) power supply, since you Are talking about Samsung and Raspberry Pi chargers. I have an orange Pi pc 2 and I use the manufacturer recommended AC adapter 3A, barrel type.
  19. Like
    pfeerick reacted to Bubba in Improve 'Support over Forum' situation   
    The "thread" is a perfect example of the Dunning–Kruger effect...
  20. Like
    pfeerick reacted to TonyMac32 in ROCK64   
    This isn't helping me not want one.  ;-)
    I'm paging through the mainline kernel support, hopefully more of these make it out of the Rockhchip patchwork and into 4.12 (like RK805 support).  As it stands I think mainline support is possible, if not extremely convenient.
  21. Like
    pfeerick reacted to tkaiser in Improve 'Support over Forum' situation   
    Folks, just don't try to behave like assholes (deleting other peoples opinions/posts, altering contents you don't understand, trying to establish BS like 'peace, love and harmony').
    Worst case option: move posts to a subforum. Never delete, never alter, never censor. If you do this the whole project becomes irrelevant.
  22. Like
    pfeerick reacted to zador.blood.stained in Improve 'Support over Forum' situation   
    Agree. Maybe it's also the time to add a "Rockchip" section.
    This section is really inactive as it is now IMO, maybe we can split it into other sections somehow.
    Mixing reviews for supported and not supported devices? And what about adding a "Tutorials" section to reduce the number of pinned posts in "Technical support" sections?
    "Community projects"? There we can create a section "Amlogic based TV boxes" and split Hardkernel boards from TV boxes.
    Deprecated boards (formerly supported by Armbian) can go there as a section too.
    Maybe put Rockchip based TV boxes there too, I don't think we will be adding official support for those anytime soon.
    Agree with tasks, but IMO we still should split build script related development from other stuff like packages, Python libraries, etc. 
  23. Like
    pfeerick reacted to mrmulti in blank password?   
    ok I'll answer my own question since i figured it out.  Start terminal emulator, type su and enter the superuser password.  then type passwd <user> and enter the user password. voila
  24. Like
    pfeerick reacted to martinayotte in Problems with Orange PC+   
    Of course you had some problems, otherwise, you would not posted that Chinese Android screenshot !
    Does he have a USB Serial to debug ?
  25. Like
    pfeerick reacted to chwe in Problems with Orange PC+   
    some more numbers on pin 1&2 that are working (setup: orangepi zero rev. 1.4, micro USB powered, samsung evo32gb, headless ssh over LAN, with NRF24l01 radio module):
    opi in idle modus: 5.16V
    running cpu-miner: 5.12V
    Just tried to create a underpower situation on my opi zero (not easy when you throw away most of the bad usb chargers& cables). 
    I got finally it with an old sony mobile phone charger and a thin noname 1m cable. Without any load on it delivers exactly 5.00V on its output (measured with a Keweisi USB powermeter). Connecting it to the opi zero voltage drops to arround ~4.8V on the USB output and ~4.5V on pin 1&2, which result in no proper startup of the opi. 
    Things that indecate that opi 0 doesn't startup properly: 
    -The LED (D7) does not shine (green one)
    -The Opi 0 gets unexpectable hot (disconnected it after 1min to avoid burnig something on my board)
    I don't wanna watch all your videos to see if D7 LED shines when you power the board but it's up to you to do that.