Posts by chewitt

  • What is the right way to apply a patch to a dts while building

    Code
    PROJECT=Allwinner DEVICE=H3 ARCH=arm scripts/clean linux
PROJECT=Allwinner DEVICE=H3 ARCH=arm scripts/unpack linux

    I would expect that both folders are functionally the same; PROJECT patches should be applied first, then DEVICE patches. You can check the unpack (and patch) process outside of a build with ^ those commands. It's easier to spot what's included/not-included. Patch files need to be something.patch and are applied in alpha-sort ordering.

  • Raspberry Firmware Update LE11

    LE settings > Update > If there are firmware updates of any kind they will be offered there. There have been no firmware updates for RPi3 for a while so if you've been running another recent LE release or RPiOS then the board is probably up-to-date already. Firmware updates are not always tied to an LE major release.

  • Wrong mirror is selected when downloading updates

    Your download request hits our mirror redirector (running mirrorbits) which we would expect to route you to a mirror geographically close or at least in the same continent. The geo data isn't always accurate though, and with ISPs trading IPv4 address space ASNs that used to belong to someone else can give occasional random results. Or maybe the wrong number of jelly beans were in the jar today.. we honestly have no idea (and no real influence) on how it works.

  • Which Version should i use?

    I think calling Generic "broken" because you can't use the Chrome browser add-on is a little over-dramatic. For the majority of users it works great. For a minority that need specific features currently tied to Xorg the GBM image is a regressive step; but they are the minority.

  • Unable to boot LE11 on a PI 3A+

    We stopped formally supporting ARM devices with < 1GB RAM with LE10 as our feeling was the codebase using the newer video pipeline has outgrown 512MB devices and 1GB was the minimum needed for a good user experience. There's been no attempt to actively prevent installs on 512MB devices and stats show some LE10 users have been using it, but it sounds like things finally tipped over the edge.

    The issue is likely to be RAM footprint. You can save memory in a custom image rebuilding the kernel with fewer things enabled (and more use of =m than =y) and disabling services that might not be required; WiFi, BT, Samba, etc. and perhaps experimenting with ZRAM (there's a Pull Requst for that on GitHub). All of them are marginal gains but collectively they might accumulate enough to be meaningful.

    The easier option is repurposing a Model B board with 1GB RAM.

  • invalid wifi key

    External Content www.youtube.com
    Content embedded from external sources will not be displayed without your consent.
    Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.

  • Compatibility finished on old hardware ?

    Code
    2023-03-09 14:15:11.682 T:1194  warning <general>: Failed to get an OpenGL context supporting core profile 3.2, using legacy mode with reduced feature set
2023-03-09 14:15:11.765 T:1194     info <general>: Using visual 0x20
2023-03-09 14:15:11.796 T:1194     info <general>: VDPAU::CreateContext - creating decoder context
2023-03-09 14:15:11.799 T:1194     info <general>: vdp_device = 0x000000 vdp_st = 0x000001
2023-03-09 14:15:11.799 T:1194    error <general>: (VDPAU) unable to init VDPAU - vdp_st = 0x1.  Falling back.
2023-03-09 14:15:11.800 T:1194     info <general>: CRenderSystemGL::InitRenderSystem - Version: 2.1 Mesa 22.3.5, Major: 2, Minor: 1
2023-03-09 14:15:11.800 T:1194     info <general>: GL_VENDOR = Mesa Project
2023-03-09 14:15:11.800 T:1194     info <general>: GL_RENDERER = i915 (chipset: Pineview M)
2023-03-09 14:15:11.800 T:1194     info <general>: GL_VERSION = 2.1 Mesa 22.3.5
2023-03-09 14:15:11.800 T:1194     info <general>: GL_SHADING_LANGUAGE_VERSION = 1.20

    The GPU fails to create the OpenGL surface needed for Kodi ^

    CvH I'm wondering if this device requires the older i965 driver?

  • Wetek play 2 build

    I added that ^ to the release announcement for LE 11.x final (and all beta releases). In the same text I also tell people to read the instructions in the wiki as boot processes have changed from older releases (things like needing to set dtb names). I also state that these images might not meet everyone's requirements, and it seems you are one of those users, so please continue to use LE 9.x .. or Android .. or anything else.