Posts by jernej

  • Early community images for H3, H6 and A64

    Quote from lumpi

    Yes like this the actual module doesn't matter for the DTS but how can I read that out, couldn't find any howto or the like. Never mind I'll find out once you got yours to run. Hopefully I got the right module.

    I will provide only firmware for brcm and nothing else. Best way for you to check is opening the case. Don't worry, it's easy (http://linux-sunxi.org/beelink_x2#device_disassembly) and if you use plastic tools like guitar pick, it won't leave any marks. Alternatively, you can read SDIO ID in /sys/class/mmc or something like that (I don't have any device at hand to check) and then google ID to see to which company/device it belongs.

  • Early community images for H3, H6 and A64

    Quote from lumpi

    H6 boxes all have no mainline DTS

    One is coming in 5.2 I believe, Beelink GS1.

    Quote from lumpi

    is there a way to recognise which WLAN module is connected to an SDIO bus? I couldn't seem to find any way of doing this...

    Yes, each SDIO device has it's own ID, just something like USB, so autoprobing should work. That's the trick I used with old OpenELEC images. Just apply power and proper driver should be loaded automatically (if exist). Fortunately, it's same power pin for both variants. However, brcm based wifi probably still doesn't work due to missing config file and firmware. I'll fix this next week.

  • Early community images for H3, H6 and A64

    Quote from lumpi

    As I mentioned before I never felt anything is not working as expected.

    Yesterday I have discussion on #linux-sunxi about this issue (#linux-sunxi on 2019-05-10 — irc logs at whitequark.org). It seems that Android on eMMC somehow interfere. I guess I'll just just destroy boot magic number on eMMC and be done with it.

    Quote from lumpi

    At times things happen you would never ever think are possible...

    True, like Linux kernel shipped in Windows (for WSL)...

    Quote from lumpi

    But I doubt you need help choosing cards for an H3

    To be honest, I just buy cheap cards. For those few minutes during test they are good enough. If it works with low quality card, it will work with high quality too :)

    BTW, now I can add support for HDMI-CEC on Beelink X2 too. Due to missing vendor CEC driver, it has it's own software implementation of protocol through GPIO.

  • Early community images for H3, H6 and A64

    Quote from lumpi

    be aware, only older X2s have AP6181newer versions have RTL8189ETV, so I'm not having too many illusions.

    Ah, true. I have Broadcom version of the wifi. However, Realtek started contributing proper Linux drivers for version 5.2. New drivers are promised in the future, so maybe there is a hope.

    Quote from lumpi

    What boot problems do you have? I never faced any, having some sandisk uSD I guess, and it boots 100% of the time very reliably with your image. Let me know if you want to compare something (logs?) with my unit.

    SPL fails to load U-Boot from SD card most of the time. Box (re)booted only few times in more than 50 tries. I noticed few mistakes in U-Boot configuration but obviously none of these improves boot situation. I have X2_v3.1_20150831 version.

  • Early community images for H3, H6 and A64

    Polczak RPi is much more mature platform at the moment, so if you want features and less bugs, go for it. But in many ways Allwinner H6 (and some others) has better features, just software is not there yet.

    skyeagle  lumpi Given that Beelink X2 has Broadcom based WiFi module, it should be easy to support it. Recently I received this box, but first I have to make booting more reliable (it rarely boots). Once that's fixed, it should be relatively easy to add WiFi support.

  • Early community images for H3, H6 and A64

    dolphs it certainly doesn't work out-of-the-box. If pins are compatible (didn't check) you would need to modify DTB file to tell that spdif should be enabled. That would be ideally solved with DT overlays, but currently there is no support for that in AW images.

    mike2002 There is certainly a difference in output. Interestingly, AVR adds some strange video modes like 1440x480@60Hz and 2880x480@60Hz. Can you edit "extlinux/extlinux.conf" on SD card and add drm.debug=0xe at the end of APPEND line? Please provide full dmesg output and output of cat /sys/kernel/debug/clk/clk_summary with AVR connected.

    andre_276 while it's true that mainline kernel doesn't support HDMI audio on any of Allwinner SoC, images here contains support for up to 8 channels linear PCM HDMI audio. This is obviously work in progress, but eventually this work will be included in mainline kernel. You can dig out patches from LE build system if you are interested.

  • Early community images for H3, H6 and A64

    Quote from mike2002

    I think it's because the default resolution is 4096*2160

    Pick nightly image from here: Index of /

    4K@60Hz was certainly an issue at some point and I'm not sure if it is fixed in image linked in this topic but it's certainly fixed in nightly image (most of the time I test on 4K TV). Currently it will force 4K@30Hz in this case because I can't locate the issue for enabling high speed link in HDMI driver, but I'm close.

  • Early community images for H3, H6 and A64

    Quote from mike2002

    I just received my Pine H64, I try your release but my H64 do not boot. I am able to see the Libreelec logo, I have the file resizing information and suddenly I have the message "Disabling IRQ #95" and that's all, libreelec stop loading..


    Do you have an idea why this happen ?

    No clue. I often test PineH64 image (although not clean image) and I never noticed such error. Did you try another SD card?

  • Early community images for H3, H6 and A64

    Quote from AryToNeX

    Anyway, don't you think it's time to update the OP?
    Also, please tell us the known bugs as of now; you said you'd tell us about some known issues with nightly builds..

    Not exactly, links still works and linked images still have same issues.

    Currently nightlies are not so different, so they have same issues as stated here in OP, but once this topic will be abandoned, I'll make new (sticky?) topic which will track all known issues. Anyway, until image uploading is not fixed, it's not practical to switch to nightlies.

    TBH, I dislike very long topics like this when information get quickly lost and people ask same thing over and over again. Example for this topic are RTL8189ES/FS wifi drivers and eMMC installation, which is explained in OP anyway.

  • Early community images for H3, H6 and A64

    Kristian There are only few RaspberryPi boards with common design, whereas H3 boards have design differences. For example, your case works, because OPi PC and OPi PC Plus are similar enough, but you can't boot from eMMC now (if it would be supported).

    No, it's not possible to make totally universal image due to possible differences in DRAM controller initialization. There is simply not enough space to cram in all possible initializations and detection code.

    About HEVC, not much work has been done in a long time on it. I hit a wall there and moved to other aspects of LibreELEC. Still a ton of work to do...

  • Early community images for H3, H6 and A64

    Quote from Polczak

    I tried to disable passtrough and I selected 5.1 output - still no sound at all from multi channel sources. Only GUI sounds and 2.0 sources.

    I am not sure what did I wrong.

    First make sure that correct audio output is selected. You should see the name of your AVR/TV/monitor in that audio output selection menu.

    Equally important, EDID should also advertise multi channel LPCM support. You may check that with executing: edid-decode /sys/class/drm/card0-HDMI-A-1/edid If you are not sure, you can paste output of that command here and I can tell you then.