Jump to content

pfeerick

Members
  • Posts

    148
  • Joined

  • Last visited

Reputation Activity

  1. Like
    pfeerick reacted to zador.blood.stained in Quick Pinebook Preview / Review   
    Without the ARISC firmware sources it's hard to predict what AXP flags are enabled or disabled on suspend or shutdown.
  2. Like
    pfeerick reacted to Xalius in Quick Pinebook Preview / Review   
    The protection circuit specs are in the battery datasheets which are already on the Pine wiki. The UVLO voltages for are around 2.7-2.8V and should be well below those set in the AXP. I still have a suspicion that whatever happens, it has something to do with running out of battery in suspend. Under normal load the battery cuts out well above 3.0V , I saw values around 3.2-3.4V in my tests....
  3. Like
    pfeerick reacted to tkaiser in Quick Pinebook Preview / Review   
    Thank you, should now be active as part of installation and user creation: https://github.com/armbian/build/commit/92dbd66b33f5eb8d4fb837e420a5a9a62050fad3
     
    BTW: On current Pinebook image mpv isn't working and can we please provide only nightlies for Pinebook now? IMO it's useless to provide a normal build at this stage now that every day fixes and enhancements are commited.
  4. Like
    pfeerick reacted to hojnikb in Quick Pinebook Preview / Review   
    How about just lifting minimum voltage in AXP to above that of protection circuit ? This way, axp will cut off battery before internal protection can kick in. Or if you're brave enough, just remove protection from the battery all together and let axp do it's thing
  5. Like
    pfeerick reacted to Igor in Quick Pinebook Preview / Review   
    Once per second.
     
    Edit #1: revitalised with this RC toy charger to 3.6V. Now charging ...
    Edit #2: Armbian running on Pinebook
     


  6. Like
    pfeerick reacted to martinayotte in How to remove Bluetooth module (for good) from CT/Armbian   
    systemctl disable bluetooth ... or whatever the service is named ...
    And then reboot, or do "systemctl stop bluetooth".
  7. Like
    pfeerick reacted to MickMake in Orange Pi Zero You Tube review with Armbian, Dec 17. Cooling, GPIO, MIPI   
    Hi guys,
    It's always tricky doing reviews as things change very quickly. So my initial review concentrates on how quickly an "average Joe" can get their board doing what they want it to do and whether it will actually do it. Then I'll follow up with updates getting into deeper testing.
     
    I don't like companies shoving products to market and expecting the community to pick up the slack. They need to put at least *some* effort into their product aside from hardware design. I bet none of the community has been paid for their efforts, yet the company is reaping the rewards? A lot of effort has been put into Armbian, yet companies like Orange Pi seem to gracefully ignore these efforts. At least some gratitude, (if not financial), would be nice.
     
    The Pine64 was a case in point: I eventually did three reviews on that hoping that things would change, but alas still one primary guy, (longsleep), doing all the hard yards.
     
    Apart from that I like the OPiZ and have a couple of projects in mind for it that the RPiZ won't be able to keep up with.
  8. Like
    pfeerick reacted to MickMake in Orange Pi Zero You Tube review with Armbian, Dec 17. Cooling, GPIO, MIPI   
    Yes, I tend to approach this with a lot of boards, because the average Joe is always on the hunt for something they can use quickly. Most of the time I tend to direct them towards an RPi as a lot of boards don't fit into the "easy" category. As you said the OPiZ is a good example.
     
    From what Igor has said, it seems that they actually have a decent relationship with the hacker community. This is great news. I don't mind a company pushing out boards when the expectation is WYSIWYG...
     
    ... on the other hand companies like the Pine64... Yeah, well. Marketing at its worst, (or best, whichever way you look at it). I have been lead to believe that the original creator of the Pine64 was a decent guy, but he hired a gun slinging marketer who came in blazing. The end result is the mess that we see today.
  9. Like
    pfeerick reacted to zador.blood.stained in Orange Pi Zero You Tube review with Armbian, Dec 17. Cooling, GPIO, MIPI   
    With this board it's tricky - why would an "average Joe" buy a board with no display output (CVBS requires soldering or making a special cable - so not an option for an "average Joe") in the first place? It can't be a good media player or a desktop replacement, so you'll need to find a good use case to choose it over Orange Pi Lite/One for example.
     
    OK. That's good, because while hardware situation usually doesn't change over time, software will improve and end users need to be aware about that.
     
    As a relatively small Chinese company Xunlong does its best - produces cheap hardware in large quantities and different variations.
     
    Well, just look at Pine64 kickstarter page. I'm sure that if they didn't advertise a development board with smartphone/tablet grade hardware as a "super computer" people would have less problems with current software support.
  10. Like
    pfeerick reacted to tkaiser in Orange Pi Zero ARMBian Debian - Disabling the Ethernet LEDS?   
    If it shouldn't be that permanent I would recommend doing a search for 'Bostik Blu-Tack' on Amazon instead  
     
    One unit is sufficient to deal with 1000 annoying LED.
  11. Like
    pfeerick reacted to nightseas in RK3328 Kernel   
    And it has 4GB dual-channel LPDDR3 by default, a small cortex-M4 MCU for board management or real time processing.
    The real purpose of this board is not for SBC but micro blade server cluster.
    that's why all connectors are placed to one side, as front panel in the future.
    I was also planning a real open cluster project to DIY blade system with managed switch blade ( the SOM on clearfog could be a good start ), backplane power delivery and cooling control.
    Just need more TIME. Ouch...
  12. Like
    pfeerick reacted to TonyMac32 in RK3328 Kernel   
    Well, I decided to quit being lazy and starting hacking away, I have a better understanding of the structure now and have begun updating the device tree, testing it out now.  I found the issue I was having before, my brain was stuck in C territory and I was assuming declarations flowed from the top down, and didn't stop to think that the various subsections (like, oh , pinctrl) would be referenced elsewhere within the same file.  I transplanted the LED information from a Feb patch on Kernel.org, it had aliases for the pin numbers that were breaking everything.   I'm testing and tweaking, forgot to add the appropriate modules to the board config after I got the dtb :-/
     
    [Edit] is there any reason the board is equipped with  the 8723bs but every DTS has ap6212  listed?
     
     
  13. Like
    pfeerick reacted to TonyMac32 in RK3328 Kernel   
    OK, so I have the LED's, 4k, and an assortment of other things working properly, I have, in theory, everything in the DTS to make it work.  Of course at this point I truly am lost, the wlan type in the DTS's that other working distros use says AP6212, but the board has 8723bs.  I also am not enough of a Linux guru to patch driver things.
     
    Some notes:   I am trying to track down the most recent rk3288.dtsi, I had to add A LOT to it to cover the additions for hevc and gpu handling.  (have not tested any of that yet).  I plan on starting from the latest "official" one to make sure there's as little hackery as possible.  Unless patching in the one from rockchip-linux is acceptable, then I'll save myself the time.
     
    Also, preliminarily working on getting the DTS to compile with the dev kernel.  will keep you posted.
  14. Like
    pfeerick reacted to Tido in RK3328 Kernel   
    The first time I looked closely to the first picture.
     
    This is a really brilliant move from ASUS, an exact copy of the connectors placing and size, combined with a real CPU, twice as much RAM.
    If the camera and display connector even have the same ports - hallelujah   
    Really neat, the colored GPI/O pins 
     
    Brilliant - as long as Rockchip and ASUS send their code upstream.
  15. Like
    pfeerick reacted to zador.blood.stained in Orange Pi Zero not resizing on first boot   
    ~ 3 months ago according to the git history. Documentation needs to be updated, it's hard to keep track of all changes.
     
    It should be in red color unless terminal type settings are wrong again for some reason and colors in MOTD are not displayed correctly.
  16. Like
    pfeerick reacted to hmartin in Orange Pi Zero went to the market   
    Show me where on that page is says "AP"
     
    A wireless server can be any computer connected via WiFi which exchanges data. e.g. it's connected as a client and runs an HTTP server where you can download files.
     
    Boom! Wireless. Server.
     
     
     
    So you won't donate to us, volunteers who spend our own time and money to buy the hardware and improve it, because we didn't make a perfect product that can do everything you dream of?
     
     
    If people like you didn't complain so much, we might actually have the time and motivation to do "innovation"
     
    This is the n'th time you've suggested that we take even more time away from "innovation" to create an FAQ for lazy people like you who can't be bothered to read the forum or mailing list.
     
    I will again suggest that you can spend your own time making the monthly FAQ, instead of posting complaints on the forum about how we don't follow your every suggestion.
     
     
     
    Excuse me? Our answers are 'abusing' you?
     
    Please. Get a grip. We're the ones actually improving the features you all are using, and what do we get? You publicly congratulating yourself for not donating money to the cause and complaining that it doesn't work.
     
    Why do we work on this at all? Maybe because we bought the hardware, realized that it has limitations, and are working to improve it for our own use. We could certainly improve it and keep the improvements to ourselves. We're not selling a product, we're not required to push our patches upstream.
     
    Unlike you, I don't go to internet forums of open source projects and whine that my expectations weren't immediately satisfied. I'm actually trying to improve things to the point where your completely unrealistic expectations ARE realized.
     
     
     
    If you want to see "innovation" go use the Debian image from Xunlong: http://www.orangepi.org/downloadresources/ Do your own research before buying. You're presumably an adult, it's not our job to educate you before you spend money. We're able to spot marketing bullshit before buying, and adjust our expectations accordingly. I'd suggest you file this under a "learning experience" that not everything the salesmen tell you is true. At $10, it's a pretty cheap life lesson. We'd have a much better attitude if people like you didn't show up to lecture us on how we should be "innovating" more. The best thing you personally can do for innovation right now, is put away your Orange Pi Zero, stop posting stupid missives like the one above, and come back in 6 months.
  17. Like
    pfeerick reacted to zador.blood.stained in Orange Pi Zero went to the market   
    OK, no need to argue about this. Even large companies do make mistakes, false claims in advertising their products and sometimes ignore feedback. Again, Xunlong, by the looks of it, doesn't have a software department - this helps keeps the prices as low as they are, but this means that testing coverage and software situation won't be as good as with more expensive boards from other vendors.
  18. Like
    pfeerick reacted to tkaiser in Orange Pi Zero wireless module status (XRADIO / ST CW1200)   
    Ok, for all the "Buy cheap, Buy twice" fellows doing the necessary research only after they bought hardware here's a great (and the official) place to discuss the funny mismatch between expectations and reality: http://www.orangepi.org/orangepibbsen/forum.php?mod=forumdisplay&fid=67
  19. Like
    pfeerick reacted to tkaiser in Orange Pi Zero wireless module status (XRADIO / ST CW1200)   
    So please go visit https://lede-project.org/supported_devices and choose a supported device. If you really want to use crappy Wi-Fi (single antenna, 2.4 GHz band only) there are a lot of cheap AP to choose from. Please also note that you're using legacy kernel and literally no one ever will be that dumb to even touch this driver version.
     
    Why the hell do people buy an SBC if they want an AP instead? Is it really saving the few bucks? Why are people that weird and believe in advertising and then add also (wrong) assumptions to that ("if there's Wi-Fi I expect it to be performant and stable, it has to be useable as access point and of course with monitor mode too")?
     
    BTW: the thread you entered with support questions is a developer thread talking about tweaks for the mainline variant of the driver or similarities with a different and already present driver there. In the meantime I think it was a mistake starting to support those cheap H3 devices and it got even worse with H2+
     
    What to do with the pollution of this thread (whining and support questions)?
  20. Like
    pfeerick reacted to hmartin in Orange Pi Zero wireless module status (XRADIO / ST CW1200)   
    Yes, I was able to find wsm_22.bin as well, it's in linux-firmware. However if you look at fwio.h, there are way more firmware files for this driver:
    #define BOOTLOADER_CW1X60 "boot_cw1x60.bin" #define FIRMWARE_CW1X60 "wsm_cw1x60.bin" #define FIRMWARE_CUT22 "wsm_22.bin" #define FIRMWARE_CUT20 "wsm_20.bin" #define FIRMWARE_CUT11 "wsm_11.bin" #define FIRMWARE_CUT10 "wsm_10.bin" #define SDD_FILE_CW1X60 "sdd_cw1x60.bin" #define SDD_FILE_22 "sdd_22.bin" #define SDD_FILE_20 "sdd_20.bin" #define SDD_FILE_11 "sdd_11.bin" #define SDD_FILE_10 "sdd_10.bin" I guess these files were never released.
     
    The wsm_##.bin and sdd_##.bin files seem to be for specific versions of the hardware. After changing the SDIO ID of the chip, the cw1200 driver is detecting the silicon as CW1X60_HW_REV and attempting to load boot_cw1x60.bin, sdd_cw1x60.bin, and wsm_cw1x60.bin.
     
    If you do a hexdump on the boot_xr819.bin from Allwinner, it appears to be a loader for the rest of the firmware (wsm_*.bin files):
    000008c0 72 65 64 0a 00 00 00 00 57 53 43 5f 4c 4f 41 44 |red.....WSC_LOAD| 000008d0 45 52 5f 46 57 5f 41 30 31 5f 30 30 5f 30 30 30 |ER_FW_A01_00_000| 000008e0 31 3a 41 75 67 20 31 39 20 32 30 31 35 2c 20 31 |1:Aug 19 2015, 1| 000008f0 38 3a 35 37 3a 35 31 3a 41 53 49 43 0a 00 00 00 |8:57:51:ASIC....| 00000900 28 20 70 7f |( p.|  
    We do have a working bootloader, it's boot_xr819.bin from the Allwinner SDK.
     
     
     
    Thanks, I'll just call up ST-Ericsson and ask them for their firmware reference manual 
  21. Like
    pfeerick reacted to Igor in More proper testing - better Armbian experience   
    Like this?
     
    /etc/update-motd.d/35-motd 
    #!/bin/bash quotes="/etc/update-motd.d/armbian-quotes.txt" random_line=$(shuf -i 1-$(wc -l < $quotes) -n 1) quote=$(sed -n -e "$random_line"p $quotes) echo -e "\e[93mTip of the day:\e[39m $quote\n"
  22. Like
    pfeerick reacted to zador.blood.stained in More proper testing - better Armbian experience   
    @tkaiser, @Igor
     
    Any objections against adding an issue template like this to our build script repository?
    IMO it would be nice to keep the issues clean and split build script support from everything else.
    So far I came up with this:
     
     
  23. Like
    pfeerick reacted to tkaiser in More proper testing - better Armbian experience   
    Well, providing less images is perfectly ok as long as users can cope with and know what to expect. We already have firstrun and especially check_first_login.sh where we query the user before starting with Armbian. This could also be the place to ask for such stuff (and do all the necessary changes in one single step afterwards). But then we could also revert back to 'one image per $LINUXFAMILY' which has also some drawbacks if someone rolls out a fleet of devices.
     
    In other words: I would prefer to discuss things first, then communicate, then change. Not the other way around.
  24. Like
    pfeerick reacted to Code4Sale LLC in More proper testing - better Armbian experience   
    The ODROID C2 image as listed below seems to work great! I am very pleased.
     
    Sound, video, network are all very good. USB devices (flash drives etc) performed exceptionally well and and as expected.
     
    I even tested the PayPal button. It worked fine (tested with 22 Euros). I encourage others to continue testing this very important feature using the same and or other amounts, as my ability to test this important feature testing is not nearly sufficient.
     
    This image boots fast. Very very fast. I used a sandisk ultra SD card. I plan to try both the samsung and that other brand (ODROID red using with the XU4) of EEMC cards later tonight. Honestly, it run so fast now, I don't know what to think. I often have corruption troubles with EEMC on the C2 using the manufactures images. It would not surprise me to find that armbian would run perfectly stable on EEMC.
      At Igor's request, I did perform "nasty things" to the board, however, I'm a little embarrassed to publicly admit any testing I did in this area. Let's just put it into the "extreme" category, and call it good (OK, it was great... really really great).
     
    I looked over the list of what you need, and saw nothing in particular that needs testing for this image, so IMHO, I would call this image good (great) and ship it! It beats the hell out of the manufacturers image (that rendered itself unbootable on two different devices).
     
    If you need me to perform any particular test, please let me know... If it is in the nasty category, it will have to wait, as I am a bit spent at the moment from this exceptional boot.
     
    Much thanks go out to Igor and the team! My boards would not boot without you and your fine work!
      Tested Image: http://image.armbian.com/betaimages/Armbian_5.23.161025_Odroidc2_Ubuntu_xenial_3.14.79_desktop.7z
     
    Joe
  25. Like
    pfeerick reacted to Tido in More proper testing - better Armbian experience   
    Well, how often do you download an image, I guess this extra step won't hurt you.
     
    on download/donate pages:
    but then, instead of encourage to spend some money - you would distract the person with technical, important information.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines