Jump to content

Eng-Shien Wu

Members
  • Posts

    21
  • Joined

  • Last visited

Posts posted by Eng-Shien Wu

  1. I tried getting the wifi working a while back, but not a serious effort as I typically use a better performing USB Wi-Fi dongle. The main hurdle on the internal Wi-Fi was that the drivers exist in the sun7i but not the sun8i kernel. I was more interested in the eMMC, but didn't even know where to start. 

  2. echo "Beelink X2" >/root/.machine.id
    

    would prevent wrong auto detection when 'firstrun' script is running.

     

    @tkaiser: thanks for the tip--now motd is correct. :)  I have updated the Armbian 5.10 Beelink X2 image and re-uploaded: download here.

     

    @Tido: thanks for the links. From the picture, I was able to identify the WiFi module as AP6181 with a Broadcom chipset. According to this forum topic, the chipset is also used by BPi-M2 and the proper module is brcmfmac. However, loading the module doesn't seem to do anything.

     

    Another issue is that the internal eMMC doesn't not appear as /dev/mmcblk0 (SD card) or any device. Maybe this is because of the Android-derived config.bin.

     

    At this point, I am at the end of my skill/knowledge level to push this image further. Maybe others with better skills can figure out what I can't. As is, it is quite usable and snappy.

  3. I have a working version of Armbian 5.10:

     download here  [link updated 2016-05-07]

     

    Working

    • Ethernet
    • USB ports (2)
    • HDMI w/ sound

    Not working:

    • WiFi is missing
    • No sound via S/PDIF

    Basically, I overwrite /boot/bin/beelinkx2.bin with the one from the blog post. I also manually link it to /boot/script.bin as /etc/init.d/firstrun is failing to detect that it is a Beelink X2 (/run/machine.id returns that it is a 'Orange Pi PC').

     

    I think from this, somebody with a Beelink X2 should be able to figure out how to make Armbian work out of the box. I will look at this again next week if somebody hasn't already beat me to the punch.

     

    This script should reproduce the image:

     

     

    OS=Armbian_5.10_Orangepih3_Debian_jessie_3.4.112_desktop
    RAW="${OS}.raw"
    MNT=root
    
    sudo apt-get install p7zip
    
    wget http://nanospic.com/dld/beelink/uboot_beelink_x2.zip
    unzip uboot_beelink_x2.zip
    cd uboot_beelink_x2
    
    wget "http://mirror.igorpecovnik.com/${OS}.7z"
    /usr/bin/7zr e "${OS}.7z" "$RAW"
    
    mkdir -p "$MNT"
    sudo mount -t ext4 -o loop,offset=$((4096*512)) "$RAW" "$MNT"
    sudo cp sys_config.bin "$MNT/boot/bin/beelinkx2.bin"
    (cd "$MNT/boot"; sudo ln -sf bin/beelinkx2.bin script.bin)
    sudo umount "$MNT"

  4. Orange Pi Plus2 (3.4.110-sun8i)

     

    Internal 16GB eMMC (ext4 default)

     

     

                                                                  random    random
                  kB  reclen    write  rewrite    read    reread    read     write
              102400       4     8492    10095     8338     8664     8445    10208
              102400      16    23447    25116    26746    26757    26200    24697
              102400     512    43090    43578    63193    63137    62919    43216
              102400    1024    43879    44221    68323    68414    68306    43544
              102400   16384    47075    47792    77034    77155    77226    47549
     
              102400       4     9438    10336     8274     8624     8602    10222
              102400      16    23473    25063    26765    26775    26248    24851
              102400     512    43084    43813    63765    63687    63607    43213
              102400    1024    43892    44595    68199    68395    68288    43945
              102400   16384    47481    47817    77016    77196    77068    47634

     

     

     

    Samsung EVO+ 32GB

     

     

                                                                  random    random
                  kB  reclen    write  rewrite    read    reread    read     write
              102400       4     1915     3314     7246     7373     7036     3392
              102400      16     8721     9930    14333    14211    14337    11827
              102400     512    20023    20107    21360    21338    21336    19805
              102400    1024    20209    20244    21991    21994    21978    20300
              102400   16384    20882    20838    22791    22796    22842    20952
     
              102400       4     3231     3324     7378     7364     7391     3402
              102400      16    11296    11957    14358    14351    14376    11858
              102400     512    14713    16865    21356    21337    21337    19770
              102400    1024    16534    18337    21970    21970    21974    19856
              102400   16384    17611    18955    22816    22801    22793    19766

     

     

     
    The 16GB eMMC on the OPI Plus2 appears to be a step up from the 8GB eMMC on the OPI Plus and the 32GB EVO+.
  5. My ES9024 DAC arrived earlier and I have been happily listening to music with it for the past several days. I can confirm that the instructions are correct and that the DAC works very well. The biggest challenge was soldering on female pin headers onto the wires (need small tip) and editing /boot/script.bin because I am a H3 noob (bin2fex/fex2bin).

     

    An easier option, albeit of lower sound quality (16-bit 48k), is a cm108 USB Sound DAC:

     

       http://www.banggood.com/USB-Virtual-7_1-Channel-Audio-Sound-Card-Adapter-p-938086.html

     

    It is plug-and-play on Armbian 5.05 and shows up as the third audio device (assuming you didn't edit script.bin for i2s):

     

       sudo aplay -l

       sudo speaker-test -twav -c2 -Dhw:2

  6. @zamar19: the audio via AV port works just fine on OPI PC in Armbian 5.05, but you need to unmute it:

     

        amixer set -c 0 'Audio lineout' unmute

     

    Then test it by

     

        speaker-test -twav -c2 -Dhw:0
     
    @Igor: Maybe first_run should unmute the Audio lineout by default?
     
    [That said, for my application (shairport-sync), the native audio of the OPI PC, like that of the NTC Chip and Raspberry PI 2b+, is unusable (either bad quality and/or loud pops when switching songs).]
  7. it not about cost .  for it is hard to procurement.  it is just about  supply chain management.

     

    If I understand correctly, the implications of a fixed voltage regulator is that the BPi M2+ will need a fan to achieve the same CPU performance under load as the OPI PC AND it won't support a low power 'idle'.  I would consider that a FATAL FLAW for most ARM board use-cases.

  8. Thx for confirmation. I wouldn't count on the currently available driver at all. If Hans' modifications also work with 3.4.x then it might be worth a look whether the driver can be backported (volunteers needed), otherwise I would simply ignore the onboard Wifi of all currently available Orange Pi.

     

    Xunlong realised in the meantime that it's better to replace the WiFi with the next models: http://www.orangepi.org/orangepibbsen/forum.php?mod=redirect&goto=findpost&ptid=1300&pid=11081

     

    BTW: Regarding mainline kernel things are really progressing nicely, see eg. https://groups.google.com/d/msg/linux-sunxi/EIeU32D5kpM/gPvPUwgwAwAJ

     

    I'm not sure the effort for a backport is warranted.. the performance of the onboard WiFi is anemic compared to a cheap USB 300N wifi dongle. I would rather see all effort made towards mainline kernel. It does look like they are really progressing well on it. 

     

    An upgraded Orange Pi PC with onboard Flash would be nice--even if you want to boot from MicroSD, the onboard flash should make for (hopefully) faster scratch storage. If they even manage to put a decent OS pre-installed on there, it should greatly help adoption or Orange Pi.

     

    However, I really, really wish they would drop the onboard WiFi.. if I need WiFi, I would rather get a better WiFi dongle (300N or AC600) than what I know they will include. 

  9. Sorry, my bad, I misread the linux-sunxi page.. according to lshw, it is rt8189es (or at least the driver)

    root@orangepiplus2:~#  lshw -C network
      *-network:0
           description: Wireless interface
           physical id: 8
           logical name: wlan1
           serial: da:47:10:fe:e2:ae
           capabilities: ethernet physical wireless
           configuration: broadcast=yes driver=rtl8189es driverversion=3.4.110-sun8i firmware=N/A link=no multicast=yes wireless=unassociated
      *-network:1
           description: Wireless interface
           physical id: 9
           logical name: wlan0
           serial: d8:47:10:fe:e2:ae
           capabilities: ethernet physical wireless
           configuration: broadcast=yes driver=rtl8189es driverversion=3.4.110-sun8i firmware=N/A ip=192.168.1.28 link=yes multicast=yes wireless=IEEE 802.11bgn
      *-network:2 DISABLED
           description: Ethernet interface
           physical id: a
           logical name: eth0
           serial: e6:15:2b:93:4a:64
           capabilities: ethernet physical
           configuration: broadcast=yes ip=192.168.1.42 multicast=yes
    

    It does have a weird quirk in that two wireless interfaces show up (wlan0 and wlan1) with different HWaddr, but seem to refer to same device. Also, ssh through the internal wireless seems to pause for a second every so often so maybe not everything is working perfectly.

  10. Just got my Orange Pi Plus 2 and was under the impression from this thread that I shouldn't expect the internal WiFi to work with Armbian. While building/installing drivers for my 300Mbps WiFi dongle, I was shocked to see WiFi working *without* my dongle plugged in. At first, I thought the drivers activated the internal WiFi (8192eu vs 8192etv), but starting with a fresh image of Armbian (Jessie server), I realized that the internal WiFi worked all along.

     

    This should let you set the SSID and Password

    sudo apt-get install -y network-manager
    sudo /usr/bin/nmtui-connect
    

    It looks like I can push ~40Mbps through the internal WiFi, while my "300Mbps" WiFi dongle manages ~75Mbps. The internal giga ethernet gets ~775Mbps.

  11. [Thanks Igor et al. for all the hard work]

     

    For those who prefer LXDE, here are the steps to transform the Jessie server to LXDE desktop:

    ## Update distro
    sudo apt-get update
    sudo apt-get dist-upgrade -y
    
    ## Install LXDE Desktop
    sudo apt-get install -y xorg lxde lightdm policykit-1
    sudo sed -i.bak -e 's/^NotShowIn=GNOME;KDE;$/NotShowIn=LXDE;GNOME;KDE;/' /etc/xdg/autostart/lxpolkit.desktop
    
    ## Add Armbian wallpaper
    umask 022
    sudo mkdir -p /usr/local/wallpapers
    (cd /usr/local/wallpapers; sudo wget https://raw.githubusercontent.com/igorpecovnik/lib/master/bin/armbian01.jpg)
    sudo sed -i.bak -e 's/^wallpaper=.*$/wallpaper=\/usr\/local\/wallpapers\/armbian01.jpg/' /etc/xdg/pcmanfm/LXDE/pcmanfm.conf
    sudo sed -i.bak -e 's/^background=.*$/background=\/usr\/local\/wallpapers\/armbian01.jpg/' /etc/lightdm/lightdm-gtk-greeter.conf
    

    In addition, I usually add

    ## Lock down SSH (no root login && ssh key-only login)
    sudo sed -i.bak -e 's/PermitRootLogin yes/PermitRootLogin no/' -e 's/#PasswordAuthentication yes/PasswordAuthentication no/' /etc/ssh/sshd_config
    sudo systemctl restart sshd
    
    ## Install Git
    sudo apt-get install -y git
    
    ## Install Armbian monitor
    sudo armbianmonitor -r
    

    BTW, I am fully expecting people to point out that directly sed'ing pkg files is wrong and I really should be doing it another way. :-)

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines