Creating a Wiki/FAQ

There’s been a bug with peripherals (on some mouses) on arm. Usbhid.mousepoll value can be changed.

Also I noticed a bug on xfce desktop on arm, there’s a line that runs across bottom of the screen I can’t seem to figure out how to get rid of. Overlaps all of the windows.

Setting up printers on arm (due to most drivers being for amd64) as IPP if compatible.

Gaming controllers : kernel updated in unstable with modules added xpad. Once its released to stable, there might not be any config required.

Would be nice to see how to correct some of these issues or ways to tweak device to get around them.

Which package of mesa do you have installed? mesa or mesa-git.

I’m not sure to be honest. It was a fresh install of xfce desktop manjaro 20.10. It is the default mesa package installed. I began to notice it after changing wallpapers. It could have been there before as well.

That would be mesa. I use xfce and do not have a line and have not seen any one else post about it. Monitor related?

I’ll open a new thread on this. Im running it on my pbpro. I have not run into this issue with other distros.

I haven’t had this issue at all on any of my devices.

What devices have you tested with, to say it’s a general issue and not just an issue with your device + mouse combo?

Sorry, I have made the correction. Its not a general issue. It is a device related problem that needed to be tweaked.

I think some tips for enabling usage of the power button on the Pi 400 would be useful. I discovered how to get it working in XFCE yesterday: Raspberry Pi 400 Power Button

@cscs, a while ago @Strit posted this. Would probably be a good addition to the Manjaro ARM Wiki.

OK I had to convert your table … and then we decided to separate it.
@Strit’s gitlab wiki is now also moved in along with some of the tips and workarounds.
But the page is getting fleshed out.

Cool. Thanks. What format does it need to be in? I only chose HTML because I was trying to make life easier for you. Also, I made a mistake with the Odtoid boards. The company is “Hard Kernel” & the models are “Odroid C4”, “Odroid N2”, etc.

Do you think the tables could benefit from any extra rows? I was thinking of adding video outputs, storage support, and maybe a few more.

Also, I’m missing a couple of devices from Pine64.

I thought so. Thanks. It wasnt too terrible to convert using a clunky tool for the bulk of it, then some sed to remove malformed lint, and just a bit of hand work - more when it was decided to have them independent.

Its mediawiki … which is ‘wiki markup’ etc …

Here are examples:

Current separate tables with wiki section headings
=Supported Devices=

==Khadas==

{|  class="wikitable" style="text-align: center;width: 100%;"-- Header --> 
!  
!  colspan="4" | Khadas
|- 
| style="width: 12%"|
<strong>Model</strong>
| Edge-V 
| Vim 1
| Vim 2 
| Vim 3 
|- 
| <strong>Release Year</strong>
| 2018 
| 2016 
| 2017 
| 2019 
|- 
| <strong>SoC Manufacturer</strong>
| Rockchip 
| Amlogic 
| Amlogic 
| Amlogic 
|- 
| <strong>Lithography</strong>
| 28nm 
| 28nm 
| 28nm 
| 12nm 
|-
| <strong>CPU</strong>
| RK3399 
| S905X 
| S912 
| A311D 
|- 
| <strong>CPU Topology</strong>
| Hexa-core:<br>2 x Cortex-A72<br>4 x Cortex-A53 
| Quad-core:<br>4 x Cortex-A53 
| Octa-core:<br>8 x Cortex-A53 
| Hexa-core:<br>4 x Cortex-A73<br>2 x Cortex-A53 
|- 
| <strong>CPU Frequency</strong>
| 2 x 1.8GHz<br>4 x 1.5GHz 
| 4 x 1.5GHz 
| 8 x 1.5GHz 
| 4 x 2.2GHz<br>2 x 1.8GHz 
|- 
| <strong>GPU</strong>
| Mali-T860 MP4 
| Mali-450 MP3 
| Mali-T820 MP3 
| Mali-G52 MP4 
|- 
| <strong>Memory</strong>
| 2&ndash;4GB<br>LPDDR4
| 2GB<br>DDR3
| 2&ndash;3GB<br>LPDDR4
| 2&ndash;4GB<br>LPDDR4
|}


==Odroid==

{|  class="wikitable" style="text-align: center;width: 100%;"-- Header --> 
! &nbsp;
!  colspan="4" | Odroid
|- 
| style="width: 12%"|
<strong>Model</strong>
| C2
| C4 
| N2 
| N2+ 
|- 
| <strong>Release Year</strong>
| 2016 
| 2020 
| 2019 
| 2020 
|- 
| <strong>SoC Manufacturer</strong>
| Amlogic 
| Amlogic 
| Amlogic 
| Amlogic 
|- 
| <strong>Lithography</strong>
| 28nm 
| 12nm 
| 12nm 
| 12nm 
|- 
| <strong>CPU</strong>
| S905 
| S905X3 
| S922X 
| S922X 
|- 
| <strong>CPU Topology</strong>
| Quad-core:<br>4 x Cortex-A53 
| Quad-core:<br>4 x Cortex-A55 
| Hexa-core:<br>4 x Cortex-A73<br>2 x Cortex-A53 
| Hexa-core:<br>4 x Cortex-A73<br>2 x Cortex-A53 
|- 
| <strong>CPU Frequency</strong>
| 4 x 1.5GHz 
| 4 x 2.0GHz 
| 4 x 2.0GHz<br>2 x 1.8GHz 
| 4 x 2.4GHz<br>2 x 1.9GHz 
|- 
| <strong>GPU</strong>
| Mali-450 MP3 
| Mali-G31 MP2 
| Mali-G52 MP4 
| Mali-G52 MP4 
|- 
| <strong>Memory</strong>
| 2GB<br>DDR3
| 4GB<br>DDR4 
| 2&ndash;4GB<br>DDR4
| 2&ndash;4GB<br>DDR4
|}


==Pine64==

{|  class="wikitable" style="text-align: center;width: 100%;"-- Header --> 
! &nbsp;
!  colspan="5" | Pine64
|- 
| style="width: 12%"|
<strong>Model</strong>
| Rock64 
| RockPro64 
| Pinebook 
| Pinebook Pro 
| PinePhone 
|- 
| <strong>Release Year</strong>
| 2017 
| 2017 
| 2017 
| 2019 
| 2019 
|- 
| <strong>SoC Manufacturer</strong>
| Rockchip 
| Rockchip 
| Allwinner 
| Rockchip 
| Allwinner 
|- 
| <strong>Lithography</strong>
| 28nm 
| 28nm 
| 40nm 
| 28nm 
| 40nm 
|- 
| <strong>CPU</strong>
| RK3328 
| RK3399 
| A64 
| RK3399 
| A64 
|- 
| <strong>CPU Topology</strong>
| Quad-core:<br>4 x Cortex-A53 
| Hexa-core:<br>2 x Cortex-A72<br>4 x Cortex-A53 
| Quad-core:<br>4 x Cortex-A53 
| Hexa-core:<br>2 x Cortex-A72<br>4 x Cortex-A53 
| Quad-core:<br>4 x Cortex-A53 
|- 
| <strong>CPU Frequency</strong>
| 4 x 1.5GHz 
| 2 x 2.0GHz<br>4 x 1.5GHz 
| 4 x 1.152GHz 
| 2 x 2.0GHz<br>4 x 1.5GHz 
| 4 x 1.2GHz 
|- 
| <strong>GPU</strong>
| Mali-450 MP2 
| Mali-T860 MP4 
| Mali-400 MP2 
| Mali-T860 MP4 
| Mali-400 MP2 
|- 
| <strong>Memory</strong>
| 1&ndash;4GB<br>LPDDR3
| 2&ndash;4GB<br>LPDDR4
| 2GB<br>LPDDR3
| 4GB<br>LPDDR4
| 2&ndash;3GB<br>LPDDR3
|}


==Raspberry==

{|  class="wikitable" style="text-align: center;width: 100%;"-- Header --> 
! &nbsp;
!  colspan="4" | Raspberry
|- 
| style="width: 12%"|
<strong>Model</strong>
| Pi 3B 
| Pi 3B+ 
| Pi 4B 
| Pi 400 
|- 
| <strong>Release Year</strong>
| 2016 
| 2018 
| 2019 
| 2020 
|- 
| <strong>SoC Manufacturer</strong>
| Broadcom 
| Broadcom 
| Broadcom 
| Broadcom 
|- 
| <strong>Lithography</strong>
| 28nm 
| 28nm 
| 28nm 
| 28nm 
|- 
| <strong>CPU</strong>
| BCM2837 
| BCM2837B0 
| BCM2711 
| BCM2711 
|- 
| <strong>CPU Topology</strong>
| Quad-core:<br>4 x Cortex-A53 
| Quad-core:<br>4 x Cortex-A53 
| Quad-core:<br>4 x Cortex-A72 
| Quad-core:<br>4 x Cortex-A72 
|- 
| <strong>CPU Frequency</strong>
| 4 x 1.2GHz 
| 4 x 1.4GHz 
| 4 x 1.5GHz 
| 4 x 1.5GHz 
|- 
| <strong>GPU</strong>
| VideoCore IV 
| VideoCore IV 
| VideoCore VI 
| VideoCore VI 
|- 
| <strong>Memory</strong>
| 1GB<br>LPDDR2
| 1GB<br>LPDDR2
| 1&ndash;8GB<br>LPDDR4
| 4GB<br>LPDDR4
|}
All on one table
{|  class="wikitable" style="text-align: center;width: 100%;"-- Header --> 
! &nbsp;
!  colspan="4" | Khadas
!  colspan="4" | Odroid
!  colspan="5" | Pine64
!  colspan="4" | Raspberry
!  colspan="1" | Radxa
|- 
| <strong>Model</strong>
| Edge-V 
| Vim 1
| Vim 2 
| Vim 3 
| C2
| C4 
| N2 
| N2+ 
| Rock64 
| RockPro64 
| Pinebook 
| Pinebook Pro 
| PinePhone 
| Pi 3B 
| Pi 3B+ 
| Pi 4B 
| Pi 400 
| Rock Pi 4 
|- 
| <strong>Release Year</strong>
| 2018 
| 2016 
| 2017 
| 2019 
| 2016 
| 2020 
| 2019 
| 2020 
| 2017 
| 2017 
| 2017 
| 2019 
| 2019 
| 2016 
| 2018 
| 2019 
| 2020 
| 2019 
|- 
| <strong>SoC Manufacturer</strong>
| Rockchip 
| Amlogic 
| Amlogic 
| Amlogic 
| Amlogic 
| Amlogic 
| Amlogic 
| Amlogic 
| Rockchip 
| Rockchip 
| Allwinner 
| Rockchip 
| Allwinner 
| Broadcom 
| Broadcom 
| Broadcom 
| Broadcom 
| Rockchip 
|- 
| <strong>Lithography</strong>
| 28nm 
| 28nm 
| 28nm 
| 12nm 
| 28nm 
| 12nm 
| 12nm 
| 12nm 
| 28nm 
| 28nm 
| 40nm 
| 28nm 
| 40nm 
| 28nm 
| 28nm 
| 28nm 
| 28nm 
| 28nm 
|- 
| <strong>CPU</strong>
| RK3399 
| S905X 
| S912 
| A311D 
| S905 
| S905X3 
| S922X 
| S922X 
| RK3328 
| RK3399 
| A64 
| RK3399 
| A64 
| BCM2837 
| BCM2837B0 
| BCM2711 
| BCM2711 
| RK3399 
|- 
| <strong>CPU Topology</strong>
| Hexa-core:<br>2 x Cortex-A72<br>4 x Cortex-A53 
| Quad-core:<br>4 x Cortex-A53 
| Octa-core:<br>8 x Cortex-A53 
| Hexa-core:<br>4 x Cortex-A73<br>2 x Cortex-A53 
| Quad-core:<br>4 x Cortex-A53 
| Quad-core:<br>4 x Cortex-A55 
| Hexa-core:<br>4 x Cortex-A73<br>2 x Cortex-A53 
| Hexa-core:<br>4 x Cortex-A73<br>2 x Cortex-A53 
| Quad-core:<br>4 x Cortex-A53 
| Hexa-core:<br>2 x Cortex-A72<br>4 x Cortex-A53 
| Quad-core:<br>4 x Cortex-A53 
| Hexa-core:<br>2 x Cortex-A72<br>4 x Cortex-A53 
| Quad-core:<br>4 x Cortex-A53 
| Quad-core:<br>4 x Cortex-A53 
| Quad-core:<br>4 x Cortex-A53 
| Quad-core:<br>4 x Cortex-A72 
| Quad-core:<br>4 x Cortex-A72 
| Hexa-core:<br>2 x Cortex-A72<br>4 x Cortex-A53 
|- 
| <strong>CPU Frequency</strong>
| 2 x 1.8GHz<br>4 x 1.5GHz 
| 4 x 1.5GHz 
| 8 x 1.5GHz 
| 4 x 2.2GHz<br>2 x 1.8GHz 
| 4 x 1.5GHz 
| 4 x 2.0GHz 
| 4 x 2.0GHz<br>2 x 1.8GHz 
| 4 x 2.4GHz<br>2 x 1.9GHz 
| 4 x 1.5GHz 
| 2 x 2.0GHz<br>4 x 1.5GHz 
| 4 x 1.152GHz 
| 2 x 2.0GHz<br>4 x 1.5GHz 
| 4 x 1.2GHz 
| 4 x 1.2GHz 
| 4 x 1.4GHz 
| 4 x 1.5GHz 
| 4 x 1.5GHz 
| 2 x 2.0GHz<br>4 x 1.5GHz 
|- 
| <strong>GPU</strong>
| Mali-T860 MP4 
| Mali-450 MP3 
| Mali-T820 MP3 
| Mali-G52 MP4 
| Mali-450 MP3 
| Mali-G31 MP2 
| Mali-G52 MP4 
| Mali-G52 MP4 
| Mali-450 MP2 
| Mali-T860 MP4 
| Mali-400 MP2 
| Mali-T860 MP4 
| Mali-400 MP2 
| VideoCore IV 
| VideoCore IV 
| VideoCore VI 
| VideoCore VI 
| Mali-T860 MP4 
|- 
| <strong>Memory</strong>
| 2&ndash;4GB<br>LPDDR4
| 2GB<br>DDR3
| 2&ndash;3GB<br>LPDDR4
| 2&ndash;4GB<br>LPDDR4
| 2GB<br>DDR3
| 4GB<br>DDR4 
| 2&ndash;4GB<br>DDR4
| 2&ndash;4GB<br>DDR4
| 1&ndash;4GB<br>LPDDR3
| 2&ndash;4GB<br>LPDDR4
| 2GB<br>LPDDR3
| 4GB<br>LPDDR4
| 2&ndash;3GB<br>LPDDR3
| 1GB<br>LPDDR2
| 1GB<br>LPDDR2
| 1&ndash;8GB<br>LPDDR4
| 4GB<br>LPDDR4
| 1&ndash;4GB<br>LPDDR4
|}

Oops … let me look into that.
(EDIT - should be fixed now)

I am not sure what would be of must interest/use.

Think something like this could be usefull.
But has to be updated by devs when a branch gets kernel updates.

arm-kernel-table
{|{{prettytable}} class="sortable" border="1" style="width:100%"
 !style="width:15%;background-color:#E5E5E5"|'''kernel'''
 !style="width:15%;text-align:center;background-color:#E5E5E5"|'''arm-branch'''
 !style="width:70%;text-align:center;background-color:#E5E5E5"|'''known issues'''
 |-
 |linux-rpi4 5.4.77-1
 |<div align="center">stable</div>
 |<div align="center">not documented</div>
 |-
 |linux-rpi4 5.4.80-1
 |<div align="center">testing+unstable</div>
 |<div align="center">not documented</div>
  |-
 |linux-pinebookpro 5.7.19-1
 |<div align="center">stable+testing+unstable</div>
 |DP-Alt-Mode
 |-
 |linux-rpi4-mainline 5.9.6-1
 |<div align="center">stable</div>
 |<div align="center">not documented</div>
 |-
 |linux-pinephone 5.9.9-1
 |<div align="center">stable</div>
 |<div align="center">not documented</div>
 |-
 |linux 5.9.9-2
 |<div align="center">stable</div>
 |<div align="center">not documented</div>
 |-
 |linux-rpi4-mainline 5.9.11-1
 |<div align="center">testing+unstable</div>
 |<div align="center">not documented</div>
 |-
 |linux-vim 5.9.8-1
 |<div align="center">stable</div>
 |<div align="center">not documented</div>
 |-
 |linux-vim 5.9.8-2
 |<div align="center">testing+unstable</div>
 |<div align="center">not documented</div>
 |-
 |linux 5.9.11-2
 |<div align="center">testing</div>
 |<div align="center">not documented</div>
 |-
 |linux-pinephone 5.9.11-4
 |<div align="center">testing</div>
 |<div align="center">not documented</div>
 |-
 |linux-pinephone 5.9.12-1
 |<div align="center">unstable</div>
 |<div align="center">not documented</div>
 |-
 |linux 5.9.12-3
 |<div align="center">unstable</div>
 |<div align="center">not documented</div>
 |-
 |linux-rc 5.10.rc4-1
 |<div align="center">stable</div>
 |<div align="center">not documented</div>
 |-
 |linux-rpi4-rc 5.10.rc5-1
 |<div align="center">stable+testing</div>
 |<div align="center">not documented</div>
 |-
 |linux-rpi4-rc 5.10.rc6-1
 |<div align="center">unstable</div>
 |<div align="center">not documented</div>
 |-
 |linux-rc 5.10.rc6-1
 |<div align="center">testing+unstable</div>
 |pbp=battary-status,wifi
 |}

Using kernel versions is not viable, since they change very often. But maybe a list of what kernel packages are available and what they are tuned for, could be useful.

Hi pttrr,

I agree with you, good idea, don’t forget to add a wiki post to edit the user feedback and add some specific trick with the wiki…

I don’t think that is what is requested here.
I think the OP as talking about the wiki.manjaro.org page, which was lacking a Manjaro ARM section, until recently, thanks to @cscs.

Hi,

Thanks for your answer,

on my side, I think that the idea is to create a specific Manjaro ARM wiki section…
not bad, OK already present on the top page with some wiki…

It’s already present at Manjaro-ARM - Manjaro

Thanks, I discover it today :-)

Is it possible to add a section for setting up TV/monitors with different aspect ratios or custom resolutions that do not appear in the display manager?
Also ways to configure audio. Run through HDMI or setting it up to output from analogue.