• Content count

  • Joined

  • Last visited

About jeanrhum

  • Rank
    Advanced Member

Recent Profile Visitors

618 profile views
  1. A quick review of recent testing images made with samsung sdcards (evo 16 or 32GB). I only check a few things: - Armbian_5.44.180510_Pine64_Ubuntu_xenial_default_3.10.107_desktop: - work as expected (no libreoffice application pre-installed) - start in 720p and successfully reboot to 1080p after modifying armbian_uEnv.txt - Armbian_5.44.180510_Pine64_Debian_jessie_default_3.10.107: - boot fail: eth led are off, no hdmi signal - Armbian_5.44.180510_Pine64_Ubuntu_xenial_default_3.10.107: - work as expected - successfull switch to next kernel (4.14.40) - successfull switching to dev kernel (4.17.0-rc3) - Armbian_5.44.180510_Bananapipro_Ubuntu_xenial_next_4.14.40: - work as expected - successfull switch to dev kernel (4.17.0-rc3), but no wifi - Armbian_5.44.180510_Orangepione_Ubuntu_xenial_next_4.14.40: - work as expected - fail to switch to dev kernel (ethernet led are on but not blinking and no hdmi signal) Only pine64 debian stretch image fails to boot. I have no more time in the coming days to investigate further.
  2. jeanrhum

    Armbian for Amlogic S912

    I'm not sure any of the proposed image has vpu software, which make plex less interesting (no transcoding). I currently use a 5.37 based image with kernel 3.14 and this functionality is not installed by default.
  3. I test to upgrade a pine64 from 5.38 (xenial server 3.10.107) to nightly builds i got this output after the upgrade: I'm still on 3.10.107 kernel even after trying to swtiching to dev or next kernel (switch is very fast). Do you want me to test something particular? I don't know where to search since no error is reported.
  4. Thanks, I forgot this point and will add this to my check list ;). If I have time, I will try again to upgrade my pine64 but this time starting from latest 5.37 instead of the old image I was using.
  5. I agree with you and was a member of the project management platform that was used one year ago. Maybe this platform was too heavy and a bit rigid. IMO the forum is more dynamic and open to any people, but currently there is no clear rule/guide on how to conduct some tests. What I've done each time I test a build is (order is approximative): 1. burn an image to a sd card with etcher 2. check if it boots as expected (command line or desktop) 3. configure linux using armbian-config (timezone, keyboard, etc.) 4. check hardware support (ethernet, wireless, sound, gpu, vpu), 5. check some highlighted functionalities I'm able to test (eg: kernel switching, desktop install) 6. update and upgrade packages 7. report back to forum and post the result of send diagnostic item in armbian-config (I suppose it calls armbianmonitor -u). Is there something wrong/missing in this list to help you in a better way?
  6. I think it would be interesting to list the preferred boards that should be used for testing (maybe in a specific thread). I look at armbian website, documentation and forum, but this kind of information is not defined in a clear and unique place. In the first post of this thread, we can identify a few of them but that's all. If we want to help in testing and for instance buy a new board for that purpose, it could guide us. It can also give everbody a clue about best supported boards and their probably long term support by armbian. For instance: - Officially supported boards for testing: orange pi plus 2E (H3), pine64+ (A64), tinker board (rk3288), odroid c2 (s905), odroid xu4 (Exynos5422)... - WIP boards for testing: espresso bin (Armada 3700), rock64 (rk3328), NanoPi Neo Core2 (h5)... In the previous list, I only chose 1 board for a given soc, but it is just an example and it is probably difficult to define this list with most people agreeing. For instance, nighlty builds are not generated for all boards, so it can be a criterion to select these boards. The WIP boards list can also be fed by the board bring up section when a board is validated for official support and software is mature enough. With this list, if a thread like this one is created before each new release, it think it will focus testing on these preferred boards.
  7. Hi, I succesfully boot last image for pine64: Linux pine64 4.14.29-sunxi64 #57 SMP Fri Mar 23 12:09:14 CET 2018 aarch64 GNU/Linux I use debian stretch server image and after freezing kernel upgrade, I install desktop from armbian-config: Desktop does not feel so smooth than on my opi+2e. Before that, I upgraded without freezing kernel upgrades and than I was not able to boot again. I will try again and will look at uart, but I had no u-boot screen. After defreeze, these 4 packages can be upgraded: linux-dtb-next-sunxi64 linux-image-next-sunxi64 linux-stretch-root-next-pine64 linux-u-boot-pine64-next Edit: Here is the UART info: U-Boot SPL 2017.11-armbian (Mar 24 2018 - 11:04:27) DRAM: 0 MiB ### ERROR ### Please RESET the board ###
  8. I successfully upgrade my opi one (debian 9 5.38 next) to nightly using armbian-config. I have 2 pine64 boards, but I suspect one to have hardware issues. With this one, I did not achieve the upgrade when starting from latest 5.38 (debian or xenial server 3.4 kernel), the screen stay blue after some downloads and I can't do anything even after more than 10 minutes. With the other one (running a 5.31 ubuntu desktop I think) I update&upgrade to 5.38, after that when I want to switch to nightly, it downloads package and propose to reboot, but after reboot I'm still on kernel 3.14. Armbian-config title says 5.42 but kernel stay at 3.14 even if I try to swith to dev or next.
  9. hi, Writing from: Linux orangepiplus2e 4.14.27-sunxi #105 SMP Thu Mar 15 22:24:12 CET 2018 armv7l armv7l armv7l GNU/Linux I'm testing xubuntu server nightly image. I successfully installed desktop and I'm writing this post inside chromium. Navigation on several simple websites is smooth and I was able to play a video from youtube. I configure wifi using armbian-config (default dhcp), then I defined a fixed IP. I was able to play a video with mpv, but it only plays smoothly inside a small window (default size). Sound is working but I had to launch alsamixer to increase the volume (~40% by default) because I was not able to change this in pulse audio gui. Cpu-freq adjust cpu frequency between 480MHz and 1.3GHz as expected More details: Major features seems to work, great job! I will try to take time to test another image on my opi one upgrade to nightly and/or on a pine64.
  10. Concerning the testing phase of Armbian, I was participating in previous "effort" using I can continue to make some end-user tests (installation, upgrade, functionality test) if a process or something else is defined. I owned a few "armbian" boards based on A20, H3 and A64 and maybe planned to buy a more recent one based on rk3399 if it is cheap enough. Currently, I have not enough knowledge and time to come to the dev side.
  11. jeanrhum

    Armbian for Amlogic S912

    I don't remember exactly which initial version I got (maybe 313 or something like that since I bought it about one year ago) and I manually upgrade via usb to one of the latest official rom (I think 704). Currently I use latest armbian server image from Balbes on sdcard and it just work as expected. I use the backup and upgrade procedure as described on the 1rst post of s905 topic. I upgraded android because , by accident, I erased the emmc with a previous version of Balbes' armbian a few month ago.
  12. jeanrhum

    Armbian for Amlogic S912

    I had exact same problem with mine (Alfawise H96 pro+). I didn't find any solution... In fact I suppose that it comes from u-boot, but I had also some powering issues. with default android, reboot didn't work (I use now superceleron ATV and it works). Powering through classical power barrel didn't work anymore and I power it through usb . I have the model with 2 hidden usb ports. I also have a GT1 Ultimate and armbian work well with kernel 3.4 with no specified dtb (no wifi but no use for me). Since it has better heat dissipation than h96, I gave up to put armbian on it.
  13. I haven't tested it. You have 2 possibilities: - look at retrorangepi to customize balbes image since they based their work on armbian and support most xunluong h3 boards. - use some similar emulators running on android. I just quickly test some emulators on android, and the main problem is with controllers. Since your are on a classical android, the user interface is based on tactile interactions (ie smartphone). Some of them allow to use a bluetooth or wired gamepad, which is very well supported by android, but mine low-cost one is not well recognized by the emulator itself. I just made some quick tests with some MAME emulators and it is not in my priorities to invest more times in this direction.
  14. Hi, I have similar needs and here is my current configuration at home with the following hardware: - OPi+2E as server (nas+plex+home-assistant+small other various things) - an Amlogic TV box for multimedia (hdmi to TV and spdif to an home cinema for tv audio and airplay server) Previously I used a RPI2 (with raspbmc or openelec) instead of my TV box, but I had to plug a dac to have a decent audio rendering. Depending on the tv box you choose, you can have spdif and optical audio outputs for less money than a RPI+dac and android offers much more possiblities for multimedia and other activities, but it is less customizable than a real linux. You can also use Balbes150 armbian images on such hardware (look at TV box section of this forum). There are also android community firmwares which will most often deliver a better experience than the default one (look at freaktab forum). I think that for less than 80 euros you can have a good config with a sbc as server with a H3/H5 or A64 soc and GBE (or tv box with armbian on it) and a tv box for multimedia on your tv. Moreover, this config may not consume much more power than a big sbc around 200 euros (like those with A72 cores).
  15. jeanrhum

    Armbian for Amlogic S912

    Maybe it is only for Allwinner SoCs, but you can try (Pine64 doc): If you use a DVI display don’t forget to define disp_dvi_compat=1 in /boot/armbianEnv.txt (supported starting with 5.21).