Jump to content

slinde

Members
  • Posts

    59
  • Joined

  • Last visited

Posts posted by slinde

  1. That means a new hardware revision is out since the older Beelink X2 are equipped with AP6181: http://linux-sunxi.org/images/1/19/X2_PCB_top.jpg(the device I have also has AP6181 but different DRAM modules compared to the wiki picture)

     

    Did you check which hardware revision you have?

    Indeed there are two different hardware versions. I have a total of three units of Beelink X2. The first two with serial numbers: X2H3CKFH1D054 and X2H3CKFH80684 have wifi chip that uses the brcmdhd driver. My newest third unit with serialnumber: A2H3CKHH71819 has wifi chip using the 8189es driver.

     

    There is no externally visible indication of HW version other than the serial number. I have not opened my units to have a look inside.

  2.  

    The Wi-Fi is up and running but I can't connect to my WPA2 !!!

    Only WEP!!! Any idea about this issue?

     

    I have no problems connecting to wpa2 using the following routine:

     

    First prepare a file with name wpa_supplicant.conf and the content like this (replace your own SSID and PSK):

     

    network={
      ssid="XXXXXXX"
      psk="yyyyyyyy"
      scan_ssid=1
    }
     
     
    Then issue the following commands:
     
    ifconfig wlan0 up
     
    wpa_supplicant -c wpa_supplicant.conf -i wlan0 &
     
    dhclient wlan0
     
  3. Only when ordering from the Chinese warehouse and not any more ($11.40 currently). Price is rising (I asked Jean-Luc from cnxsoft whether Gearbest is trustworthy, he posted the promo and now we can watch the price increase every few minutes ;) )

    Yes, the price is when ordering from the chinese warehouse and it will not be sent until the end of July.

    I managed to order 2 pcs without problems. Price is still showing $8.57 when I refresh the page http://www.gearbest.com/boards-shields/pp_314651.html

     

    If you can wait it is a bargain!

  4. I have bought from Gearbest 50+ times. I find them trustworthy and they deliver what they promise. If there is any trouble they have a customer service that works quite well for being a chinese webshop. Sometimes there are misunderstandings but they usually sort it out in the end.

     

    I will put in a order for an Orange Pi PC, today the price following your link is $8.57! :)

  5. Hi slinde, inside the firmware file there is no bcmdhd.bin file.

    When I do a:

    sudo modprobe bcmdhd firmware_path=/lib/firmware/ap6210/bcmdhd.bin nvram_path=/lib/firmware/ap6210/nvram.txt

    I have a message like this:

    modprobe: ERROR: could not insert 'bcmdhd': No such device

    And the dmesg shows me:

    [ 1004.060351] failed to power up DHD generic adapter, 0 retry left

    Any help?

     

    Hi manuti, I tested this once more today and it works for me as earlier described and with the file I uploaded to my web server. See the full logfile for details:

    root@beelinkx2:~# lsmod
    Module                  Size  Used by
    sunxi_spdma             3703  1
    sunxi_spdif             7037  1
    sunxi_sndspdif          3885  0
    sndspdif                2743  1
    bcmdhd                648477  0
    
    root@beelinkx2:~# wget http://www.itgubben.eu/files/ap6210.tar.xz
    --2016-07-09 15:55:33--  http://www.itgubben.eu/files/ap6210.tar.xz
    Resolving www.itgubben.eu (www.itgubben.eu)... 2001:470:27:75b::2, 83.209.13.109
    Connecting to www.itgubben.eu (www.itgubben.eu)|2001:470:27:75b::2|:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 225284 (220K) [application/x-xz]
    Saving to: ‘ap6210.tar.xz’
    
    ap6210.tar.xz       100%[=====================>] 220.00K  1.19MB/s   in 0.2s
    
    2016-07-09 15:55:33 (1.19 MB/s) - ‘ap6210.tar.xz’ saved [225284/225284]
    
    root@beelinkx2:~# cd /lib/firmware/
    root@beelinkx2:/lib/firmware# tar xvf ~/ap6210.tar.xz
    ap6210/
    ap6210/fw_bcm40181a2_p2p.bin
    ap6210/nvram.txt
    ap6210/fw_bcm40181a2_apsta.bin
    ap6210/fw_bcm40181a2.bin
    
    root@beelinkx2:/lib/firmware# cd
    
    root@beelinkx2:~# lsmod
    Module                  Size  Used by
    sunxi_spdma             3703  1
    sunxi_spdif             7037  1
    sunxi_sndspdif          3885  0
    sndspdif                2743  1
    bcmdhd                648477  0
    
    root@beelinkx2:~# rmmod bcmdhd
    
    root@beelinkx2:~# modprobe bcmdhd firmware_path=/lib/firmware/ap6210/bcmdhd.bin nvram_path=/lib/firmware/ap6210/nvram.txt
    
    root@beelinkx2:~# lsmod
    Module                  Size  Used by
    bcmdhd                648477  0
    sunxi_spdma             3703  1
    sunxi_spdif             7037  1
    sunxi_sndspdif          3885  0
    sndspdif                2743  1
    
    root@beelinkx2:~# ifconfig wlan0 up
    
    root@beelinkx2:~# iwlist wlan0 scan
    wlan0     Scan completed :
              Cell 01 - Address: 14:CC:20:CB:A4:72
                        ESSID:"XXXXXXX"
                        Mode:Managed
                        Frequency:2.437 GHz (Channel 6)
                        Quality:5/5  Signal level:-40 dBm  Noise level:-82 dBm...
    

    This test was done with a Beelink X2 and the file Armbian_5.14_Beelinkx2_Debian_jessie_3.4.112.7z downloaded today.

    I agree there is no file called "bcmdhd.bin" in the ap6210.tar.xz file but somehow it seems to work anyhow. If I look in the /var/syslog file I see that the driver finds the correct paths:

    Jul  9 15:59:45 localhost kernel: [  498.139371] dhd_bus_devreset: == WLAN ON ==
    Jul  9 15:59:45 localhost kernel: [  498.139671] F1 signature read @0x18000000=0x1591a962
    Jul  9 15:59:45 localhost kernel: [  498.140467] dhd_conf_set_hw_oob_intr: Enable HW OOB for 43362
    Jul  9 15:59:45 localhost kernel: [  498.146815] F1 signature OK, socitype:0x1 chip:0xa962 rev:0x1 pkg:0x9
    Jul  9 15:59:45 localhost kernel: [  498.149117] DHD: dongle ram size is set to 245760(orig 245760) at 0x0
    Jul  9 15:59:45 localhost kernel: [  498.152761] dhd_conf_read_config: Ignore config file /lib/firmware/ap6212/config.txt
    Jul  9 15:59:45 localhost kernel: [  498.152836] dhd_conf_set_fw_name_by_chip: firmware_path=/lib/firmware/ap6210/fw_bcm40181a2.bin
    Jul  9 15:59:45 localhost kernel: [  498.152888] Final fw_path=/lib/firmware/ap6210/fw_bcm40181a2.bin
    Jul  9 15:59:45 localhost kernel: [  498.152925] Final nv_path=/lib/firmware/ap6210/nvram.txt
    Jul  9 15:59:45 localhost kernel: [  498.152959] Final conf_path=/lib/firmware/ap6212/config.txt
    Jul  9 15:59:45 localhost kernel: [  498.197314] NVRAM version: AP6210_NVRAM_V1.3_08182013
    
    
  6. I am not sure how you have done but the correct procedure is to unpack the .7z file and after that use an img-burning software like win32diskimager or dd in Linux to transfer the image to the SD-card. It is not enough to simply copy the image file to the SD-card.

  7.  @slinde and/or @markbirss: Please remember that fex file should be exchanged (and reboot in between) and one minor tweak should also be applied, see my last comment: https://github.com/igorpecovnik/lib/commit/60e935b34e3ed8b2ed14cf812fc30b08506b1651#commitcomment-17864605

     

    When I did my last test and got wifi working I had already exchanged the fex/bin file to your latest version and rebooted. The "minor tweak" already seems to be include in the version of fex file I have.

  8. Firmware is missing. Extract https://transfer.sh/h6nda/ap6210.tar.xzto /lib/firmware so you will have /lib/firmware/ap6210 folder. Then unload bcmdhd driver if it is already loaded and load it with following command:

    modprobe bcmdhd firmware_path=/lib/firmware/ap6210/bcmdhd.bin nvram_path=/lib/firmware/ap6210/nvram.txt
    

    NOTE: Download link will be valid only for 14 days, but until then it will be fixed, I guess.

    Confirmed working!

    root@beelinkx2:~# modprobe bcmdhd firmware_path=/lib/firmware/ap6210/bcmdhd.bin nvram_path=/lib/firmware/ap6210/nvram.txt
    root@beelinkx2:~# lsmod
    Module                  Size  Used by
    bcmdhd                648477  0
    sunxi_spdma             3703  1
    sunxi_spdif             7037  1
    sunxi_sndspdif          3885  0
    sndspdif                2743  1
    root@beelinkx2:~# ifconfig wlan0 up
    root@beelinkx2:~# iwlist wlan0 scan
    wlan0     Scan completed :
                   bla, bla....
    

    A VERY big thank you for your help! :)

  9. I did some more testing on the wlan issue. There seems to be some sort of missmatch regarding the driver. Error message: dhdsdio_download_code_file: Open firmware file failed /lib/firmware/ap6212/fw_bcm40181a2.bin

     

    I tried to make a symbolic link named fw_bcm40181a2.bin pointing to the existing driver fw_bcm43438a0.bin in the /lib/firmware/ap6212 directory but no success.

     

    Dmesg:

    [ 2147.698347] dhd_bus_devreset: == WLAN ON ==
    [ 2147.698788] F1 signature read @0x18000000=0x1591a962
    [ 2147.699479] dhd_conf_set_hw_oob_intr: Enable HW OOB for 43362
    [ 2147.705885] F1 signature OK, socitype:0x1 chip:0xa962 rev:0x1 pkg:0x9
    [ 2147.708253] DHD: dongle ram size is set to 245760(orig 245760) at 0x0
    [ 2147.710776] dhd_conf_read_config: Ignore config file /lib/firmware/ap6212/config.txt
    [ 2147.710851] dhd_conf_set_fw_name_by_chip: firmware_path=/lib/firmware/ap6212/fw_bcm40181a2.bin
    [ 2147.710901] Final fw_path=/lib/firmware/ap6212/fw_bcm40181a2.bin
    [ 2147.710939] Final nv_path=/lib/firmware/ap6212/nvram.txt
    [ 2147.710973] Final conf_path=/lib/firmware/ap6212/config.txt
    [ 2147.712535] dhdsdio_download_code_file: Open firmware file failed /lib/firmware/ap6212/fw_bcm40181a2.bin
    [ 2147.712594] _dhdsdio_download_firmware: dongle image file download failed
    [ 2147.712710] dhd_net_bus_devreset: dhd_bus_devreset: -35
    [ 2147.712754] dhd_prot_ioctl : bus is down. we have nothing to do
    [ 2147.712797] dhd_net_bus_devreset: dhd_bus_devreset: -35
    [ 2147.712938] wifi_platform_set_power = 0
    [ 2147.712973] ======== PULL WL_REG_ON LOW! ========
    [ 2147.713008] [wifi_pm]: set wl_reg_on 0 !
    [ 2147.713043] wl_android_wifi_on: Failed
    [ 2147.713077] dhd_open : wl_android_wifi_on failed (-35)
    [ 2147.713118] dhd_stop: Enter ee5d9000
    [ 2147.713148] wl_android_wifi_off in 1
    [ 2147.713179] wl_android_wifi_off in 2: g_wifi_on=0
    [ 2147.713210] wl_android_wifi_off out
    [ 2147.713239] dhd_stop: Exit
    [ 2147.713279] dhd_open: Exit ret=-1
    
    
  10. http://www.armbian.com/beelinkx2/

     

    But it's untested.

    I did a quick test of Armbian_5.14_Beelinkx2_Debian_jessie_3.4.112.7z.

     

    It boots up just like it should, does the first reboot and resizes the SD-card just like it should. At first login everything looks as expected. So the basic image seems flawless. :)

     

    Regarding wifi I can't get it to work. It loads the bcmdhd driver but I can't get the interface up:

    root@beelinkx2:~# ifconfig wlan0 up
    SIOCSIFFLAGS: Operation not permitted
    root@beelinkx2:~# iwlist wlan0 scan
    wlan0     Interface doesn't support scanning.
    
    

    If I do the same two commands with a TP-Link WN-725N USB wifi dongle it works and I get a list of the available networks.

     

    However, I am very happy that Beelink X2 will be supported by Armbian and for my personal use wifi is not important. Hopefully the wifi issue and emmc access can be solved later on.

  11. It looks like we should add the Beelink X2 to list of officially supported boards with first officially H3 build (to be released soon). In case you've a spare SD card (4 GB are enough), please use our lima-memtester Armbian test image (originally created for BPi M2+ but after a small modification -- see below -- this can be used to test the X2 too) as outlined here in post #4: http://forum.armbian.com/index.php/topic/1322-testers-wanted-testing-dram-reliability-on-bpi-m2-and-nanopi-m1/

     

    The only modification: Please create /boot/bin/beelinkx2.fex with the contents from here http://sprunge.us/UcBT  (everything and including between "[product]" and "corekeeper_enabled = 1") with one minor modification: dram_clk = 648. Then do

    fex2bin /boot/bin/beelinkx2.fex /boot/bin/beelinkx2.bin
    ln -sf /boot/bin/beelinkx2.bin /script.bin
    armbianmonitor -r && reboot
    

    And after the reboot you should let "lima-memtester 100M" run for at least 1 hour and check whether a spinning cube is shown on the monitor (with gray background, a glowing red background would be a bad sign). Then please report back in the other thread and post also a screenshot how temperatures/throttling looked like (the thermal pad on H3 and the large metal plate seem okish to improve heat dissipation).

     

    BTW: I tried to enable eMMC but get then kernel panics and stuff like that, so won't waste any time with this for now. Also regarding Wi-Fi at least I won't look into it because my need for 2.4Ghz Wi-Fi is zero. So anyone else has to take care that a 'modprobe ap6211' will succeed and Wi-Fi gets useable.

     

    I would be happy if the Beelink X2 was officially supported by Armbian! :)  I have two units of the Beelink X2 and will be glad to help out to the best of my abilities. I am a seasoned Unix/Network administrator but not experienced in software development.

     

    I managed to start up the "lima-memtester 100M". It is now running and I will post my results in the other thread in about an hour or so.

    A big Thank You to tkaiser and Igor for all your good work with Armbian!

  12. Thx for the feedback! But we have currently already a board config for X2 so next logical step is to adjust board config in the following way:

    BOOTCONFIG=orangepi_pc_defconfig
    MODULES="#gpio_sunxi sndspdif sunxi_sndspdif sunxi_spdif sunxi_spdma ap6211"
    MODULES_NEXT=""
    CPUMIN=240000
    CPUMAX=1200000
    

    Switching to orangepi_pc_defconfig will enable eMMC, thermal settings have to be adopted to 'overheats as hell' (but I'll make some tests again with applied heat pad and metal plate since we should assume that every X2 owner uses his device inside the enclosure) and then anyone has to add/fix the Wi-Fi driver to sun8i sources if not already there.

    Thanks for info about the board config! Since I am relative new to Armbian I don't understand how to use it? Is this something I can use if I compile Armbian myself? I have not set up an environment to compile Armbian so far.

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines