Jump to content

jeanrhum

Members
  • Posts

    287
  • Joined

  • Last visited

Posts posted by jeanrhum

  1. 11 hours ago, Miguel Galan Valdivia said:

     

    Hello, I have been testing with several dtb's, I will try without them as you indicate that it assumes by default. Anyway both ubuntu and debian in kernel 3.14.29 linux-headers do not appear and I can not install wifi drivers, if you upgrade to some higher version is blocked, I only run now with ethernet. I will keep trying but I can not get the linux-headers in any way (i'm so too bad with linux). Thank you

    I didn't test if wif was working (I think it wasn't), because I only used ethernet.

  2. 10 hours ago, Miguel Galan Valdivia said:

    Hello, I have beelink GT1 but not ultimate CPU Amlogic S912, GPU Mali-T820MP3 with 2GB and 32GB of RAM I have been trying unsuccessfully with Armbian_5.41.1_S9xxx_Debian_stretch_3.14.29_icewm_20180406 for having the same kernel so I try now with Armbian_5.37_S9xxx_Debian_stretch_3.14.29_icewm_20171226 but I do not recognize WIFI (Ateros chip CQA9377), which dtb can work? I'm still trying with vegas_s96.dtb Thanks in advance.

     

    With 3.14 kernel, I use the dtb of android img that is stored on emmc. So this is the Beelink dtb. In fact it is automatically used when you don't put a dtb file at the root of the sd card. I'll try to install it again, since a recent upgrade broke my system (no ethernet anymore). New images (4.xx) of Balbes does not really work on my box (no ethernet and no usb even if it boots).

  3. 22 hours ago, r4w said:

     

    Everything works with a 3.14.x kernel and module wlan, but I can't get it working with the latest kernel :(

    I tested recently and had the same issues with an s912 tv box (gt1 ultimate) previously running a 3.14 img. I was able to boot with most dtbs cthat are compatible with the soc, but I never hab been able to use usb nor network devices.

  4. Until the campaign ends and they send the boards, I should receive one (1GB). I'll be able to test if there is any armbian build for it.

    I'm impressed (if verified when testing the board) by the current support status of this board. It often requires several months (years) when we look at existing boards (even if open source communities are doing a really great job).

  5. 2 hours ago, zogu said:

    @jeanrhum What is the difference between 5.37 and newer version, for example 5.41 with mali6?

    Since I upgrade frequently, I think there is not too much difference. Armbian tools and firmware are updated as other packages. Of course there should be some specific modifications of Balbes after each update he made.

    If 5.41 has mali, it is useless for me since I use my box as a server.

  6. I tested yesterday evening your last image with my V88 mini III. I burnt your u-boot related files using rockchip opensource documentation, otherwise it booted to emmc starting android instead of sd card.

    After that, I still was not able to boot even after testing all available dtbs (except android ones). I'll try too connect uart as soon as possible to give more insight of the problem.

  7. I found that bt chip should be supported by mainline kernel, but relevant info have to be defined in device tree: https://github.com/torvalds/linux/blob/master/Documentation/devicetree/bindings/net/broadcom-bluetooth.txt

    I suppose that your chip is also concerned, but I'm a totally newbie concerning device tree. I tried to decompile your current dtb, but then I'm not able to make the relevant modifications to then compile and get a working dtb. The dtc command asks for uart2_pins in the best case and I don't know how to configure them.

    Is there somebody else who make such broadcom bluetooth chip working with mainline?

    As I understand, only allwinner chips support overlays, because armbian-add-overlay returns an error claiming that.

  8. Thanks a lot, wifi works well now with fw_bcm4339a0_ag.bin from github!

    In fact those files where in /lib/firmware/brcm/ (as asked by martinayotte) and not in /lib/firmware/ap6335/brcm/. I use the ones you told me to download, but I suppose that those in /lib/firmware/brcm/ should also work. You did something special to use this path?

  9. 3 hours ago, balbes150 said:

    The image of RK3328-tv is arm64\aarch64 (64 bits). If I'm not confused, rk3288 is arm\armhf (32 bits). On arm64 the system can run the assembled arm, but on the contrary it is impossible.

    You are absolutely right, I didn't consider this obvious fact...

    But it suppose it may be possible for rk3399 or rk3368. The main problem is probably about u-boot compatibility (especially for rk3368).

  10. Even if you don't want to support it, here is the situation with wifi:

    - on ugoos ut3s it seems to be ap6335, is it similar for you?

    - when i write the folowing commands:

    sudo rmmod brcmfmac
    sudo modprobe brcmfmac

    I have no error on the command line, but on dmesg I can read:

    [  190.311691] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4339-sdio for chip BCM4339/2
    [  190.311982] brcmfmac mmc1:0001:1: Direct firmware load for ap6330/brcm/brcmfmac4339-sdio.bin failed with error -2
    [  191.313814] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50

     

    brcmfmac appears with lsmod, but there is no wireless interface with iwconfig. In dmesg, i app6330 is written instead of ap6335, maybe it is the problem.

    Have you any clue to solve that?

  11. I had no time to look at this yesterday, but lspci does not work on most arm board, since, there is no real pci bus like on standard motherboards. I will open the box and look at the chip, or if it's too difficult to read, I suppose I can find this info on the web.

     

    Some other elements are not working: reboot, power button and power led.

    I didn't test audio, bluetooth seems to work and I successfully installed JMCC's media script.

     

    Another annoying fact is that desktop is a bit long to launch (a few minutes) after boot seems to be finished (I can log in console and use the system).

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines