<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:content="http://purl.org/rss/1.0/modules/content/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>UP Core Plus Linux — upcommunity</title>
        <link>https://forum.up-community.org/</link>
        <pubDate>Thu, 08 Oct 2026 01:27:56 +0000</pubDate>
        <language>en</language>
            <description>UP Core Plus Linux — upcommunity</description>
    <atom:link href="https://forum.up-community.org/categories/up-core-plus-linux/feed.rss" rel="self" type="application/rss+xml"/>
    <item>
        <title>bluetooth choppy sound ubuntu 20.04 and 18.04</title>
        <link>https://forum.up-community.org/discussion/4614/bluetooth-choppy-sound-ubuntu-20-04-and-18-04</link>
        <pubDate>Thu, 25 Mar 2021 21:00:05 +0000</pubDate>
        <category>UP Core Plus Linux</category>
        <dc:creator>Earsistemas</dc:creator>
        <guid isPermaLink="false">4614@/discussions</guid>
        <description><![CDATA[<p>Ubuntu 20.04 , Up Core Plus, I have followed all instrucctions from wiki pages (Up kernell and Wifi/BT firmware), but the sound is chopped all the time in the bluetooth devices. Using HDMI, sound output is ok. <br />
I have tried PulseAudio latency offset, many pairings with differents bluetooth devices and all possible configurations, but always the same: it connects but the sound is choppy. The A2DP configuration is possible, but the HSP/HFP is not available. Please, any help will be wellcome. Thanks</p>
]]>
        </description>
    </item>
    <item>
        <title>UP Core Plus I2S Audio support - Linux</title>
        <link>https://forum.up-community.org/discussion/4484/up-core-plus-i2s-audio-support-linux</link>
        <pubDate>Tue, 10 Nov 2020 12:08:54 +0000</pubDate>
        <category>UP Core Plus Linux</category>
        <dc:creator>Jaimin_Thakkar</dc:creator>
        <guid isPermaLink="false">4484@/discussions</guid>
        <description><![CDATA[<p>Hi Team,</p>

<p>We are planning to use I2S (AVS_I2S2_*) from a 100pin docking connector for interfacing with audio codecs in our product. <br />
Can we get any support/reference implementation of the codec integration with Linux?<br />
What are the changes (BIOS,  IO mixing, machine driver, etc) needed for the integration?</p>

<p>Thanks,<br />
Jaimin</p>
]]>
        </description>
    </item>
    <item>
        <title>Could not see any visible networks on UP core plus after installing Ubuntu 18.04</title>
        <link>https://forum.up-community.org/discussion/4472/could-not-see-any-visible-networks-on-up-core-plus-after-installing-ubuntu-18-04</link>
        <pubDate>Tue, 27 Oct 2020 12:35:59 +0000</pubDate>
        <category>UP Core Plus Linux</category>
        <dc:creator>Shm</dc:creator>
        <guid isPermaLink="false">4472@/discussions</guid>
        <description><![CDATA[<p>Hello,</p>

<p>I have  a UP core plus board. I followed** <a rel="nofollow" href="https://forum.up-community.org/home/leaving?allowTrusted=1&amp;target=https%3A%2F%2Fwiki.up-community.org%2FUbuntu_18.04%2A%2A">https://wiki.up-community.org/Ubuntu_18.04**</a> to install Ubuntu 18.04 on the board.  I also installed Ubuntu kernel 5.0.0 locally from debian packages.Then installed the Ampak firmware for WiFi and Bluetooth locally from debian package. So basically I set up my board as said in the wiki link.<br />
Now  I can see <strong>wlan0</strong> interface when I execute <strong>iwconfig</strong>.  But when I do <strong>iwlist wlan0 scan</strong> , there are no scan results. <br />
There are no visible networks in the WiFi settings menu.<br />
As per the link , the WiFi should be up and running if we follow all the steps mentioned in the link.But in my case I could not see any networks around me. <br />
Please help!!!!</p>
]]>
        </description>
    </item>
    <item>
        <title>Up Core Plus, BIOS still problem</title>
        <link>https://forum.up-community.org/discussion/4273/up-core-plus-bios-still-problem</link>
        <pubDate>Sat, 02 May 2020 01:44:24 +0000</pubDate>
        <category>UP Core Plus Linux</category>
        <dc:creator>noom</dc:creator>
        <guid isPermaLink="false">4273@/discussions</guid>
        <description><![CDATA[<p>Invalid entry length (0). DMI table is broken! Stop. This error happen on UP Core Plus model Atom® x5-E3930, 2GB RAM, very hard to get help or support from this company.</p>
]]>
        </description>
    </item>
    <item>
        <title>Linux i2c mapping</title>
        <link>https://forum.up-community.org/discussion/4123/linux-i2c-mapping</link>
        <pubDate>Mon, 20 Jan 2020 17:44:04 +0000</pubDate>
        <category>UP Core Plus Linux</category>
        <dc:creator>rreignier</dc:creator>
        <guid isPermaLink="false">4123@/discussions</guid>
        <description><![CDATA[<p>Does some know the mapping of the i2c buses on Linux.</p>

<p><code spellcheck="false" tabindex="0">/sys/bus/i2c/devices/</code> shows 10 i2c buses:</p>

<pre spellcheck="false" tabindex="0">$ ls -l /sys/bus/i2c/devices/
total 0
lrwxrwxrwx 1 root root 0 Jan 20 17:33 i2c-0 -&gt; ../../../devices/pci0000:00/0000:00:16.0/i2c_designware.0/i2c-0
lrwxrwxrwx 1 root root 0 Jan 20 17:33 i2c-1 -&gt; ../../../devices/pci0000:00/0000:00:16.1/i2c_designware.1/i2c-1
lrwxrwxrwx 1 root root 0 Jan 20 17:33 i2c-2 -&gt; ../../../devices/pci0000:00/0000:00:17.0/i2c_designware.2/i2c-2
lrwxrwxrwx 1 root root 0 Jan 20 17:33 i2c-3 -&gt; ../../../devices/pci0000:00/0000:00:02.0/i2c-3
lrwxrwxrwx 1 root root 0 Jan 20 17:33 i2c-4 -&gt; ../../../devices/pci0000:00/0000:00:02.0/i2c-4
lrwxrwxrwx 1 root root 0 Jan 20 17:33 i2c-5 -&gt; ../../../devices/pci0000:00/0000:00:02.0/i2c-5
lrwxrwxrwx 1 root root 0 Jan 20 17:33 i2c-6 -&gt; ../../../devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-1/i2c-6
lrwxrwxrwx 1 root root 0 Jan 20 17:33 i2c-7 -&gt; ../../../devices/pci0000:00/0000:00:02.0/drm/card0/card0-DP-2/i2c-7
lrwxrwxrwx 1 root root 0 Jan 20 17:33 i2c-8 -&gt; ../../../devices/pci0000:00/0000:00:17.2/i2c_designware.3/i2c-8
lrwxrwxrwx 1 root root 0 Jan 20 17:33 i2c-9 -&gt; ../../../devices/pci0000:00/0000:00:17.3/i2c_designware.4/i2c-9
</pre>

<p>The 100-pin connector has I2C0, I2C1 and I2C6. But what are their mapping to Linux buses?</p>

<p>Thanks you.</p>
]]>
        </description>
    </item>
    <item>
        <title>OV5647 (Raspberry Pi camera integration) supported???</title>
        <link>https://forum.up-community.org/discussion/4168/ov5647-raspberry-pi-camera-integration-supported</link>
        <pubDate>Sun, 16 Feb 2020 01:34:36 +0000</pubDate>
        <category>UP Core Plus Linux</category>
        <dc:creator>Zoromoth</dc:creator>
        <guid isPermaLink="false">4168@/discussions</guid>
        <description><![CDATA[<p>I have a raspberry pi with the OV5647 sensor module. The standard linux drivers contain a built ov5647.c Is this supported by up core plus? I had this question since the board has 2 Mipi csi camera lanes. Is the standard prebuit driver in linux:</p><p>a. Smart enough to figure out which lane to use?</p><p>b. Is tje driver even compatible with up core plus.</p><p>Any help will be greatly appreciated...</p><p>Thanks and Regards,</p><p>Zoromoth</p>]]>
        </description>
    </item>
    <item>
        <title>failed to install Ubuntu 16.04 for Up Core Plus</title>
        <link>https://forum.up-community.org/discussion/3884/failed-to-install-ubuntu-16-04-for-up-core-plus</link>
        <pubDate>Thu, 29 Aug 2019 08:02:53 +0000</pubDate>
        <category>UP Core Plus Linux</category>
        <dc:creator>hgemini</dc:creator>
        <guid isPermaLink="false">3884@/discussions</guid>
        <description><![CDATA[<p>Hello,<br />
I tried to install Ubuntu 16.04 for Up Core Plus (Atom® x5-E3930), but failed even to load install.  Though I watched install menu, when loading installer, the following message shows up and returns back to boot.</p>

<p><img src="https://us.v-cdn.net/6030431/uploads/editor/me/3fh9pju73kgg.jpg" alt="" title="" srcset="https://us.v-cdn.net/cdn-cgi/image/quality=80, format=auto, fit=scale-down, height=300, width=300/6030431/uploads/editor/me/3fh9pju73kgg.jpg 300w, https://us.v-cdn.net/cdn-cgi/image/quality=80, format=auto, fit=scale-down, height=600, width=600/6030431/uploads/editor/me/3fh9pju73kgg.jpg 600w, https://us.v-cdn.net/cdn-cgi/image/quality=80, format=auto, fit=scale-down, height=800, width=800/6030431/uploads/editor/me/3fh9pju73kgg.jpg 800w, https://us.v-cdn.net/cdn-cgi/image/quality=80, format=auto, fit=scale-down, height=1200, width=1200/6030431/uploads/editor/me/3fh9pju73kgg.jpg 1200w, https://us.v-cdn.net/cdn-cgi/image/quality=80, format=auto, fit=scale-down, height=1600, width=1600/6030431/uploads/editor/me/3fh9pju73kgg.jpg 1600w, https://us.v-cdn.net/cdn-cgi/image/quality=80, format=auto, fit=scale-down, height=2000, width=2000/6030431/uploads/editor/me/3fh9pju73kgg.jpg 2000w, https://us.v-cdn.net/6030431/uploads/editor/me/3fh9pju73kgg.jpg" sizes="100vw" /></p>

<p>Regarding "TPM error",  by disabling secure boot in BIOS it doesn't show up anymore.</p>

<p>I tried to search the error "Couldn't get size:  ...",  and it seems to be related with secure boot,<br />
but I cannot find any solution.</p>

<p>Giving me any advices are really helpful.</p>

<p>Best regrads,</p>

<p>Hide</p>
]]>
        </description>
    </item>
   </channel>
</rss>
