<![CDATA[PINE64 - Linux on Pine A64(+)]]>

<![CDATA[PINE64 - Linux on Pine A64(+)]]> https://forum.pine64.org/ Thu, 07 May 2026 01:12:21 +0000 MyBB <![CDATA[Volumio 3 Pine A64+ unofficial]]> https://forum.pine64.org/showthread.php?tid=20262 Sat, 02 May 2026 16:49:24 +0000 shinzuka]]> https://forum.pine64.org/showthread.php?tid=20262 Volumio 3.999

Tested OK

- USB DAC
- Headphone jack

What remains to be tested:

- i2s DAC]]> Volumio 3.999

Tested OK

- USB DAC
- Headphone jack

What remains to be tested:

- i2s DAC]]> <![CDATA[Need Asound.state file with mic enabled]]> https://forum.pine64.org/showthread.php?tid=18602 Sat, 12 Aug 2023 11:54:19 +0000 muromec]]> https://forum.pine64.org/showthread.php?tid=18602
I have archlinux running on pine64+, everything is fine except mic input. Output to 3.5mm jack works nice, but I can't get recording anything. Can you please share asound.state file with mic enabled.
So far I went through sound codec code and tried to enabled the path from Mic2 -> DAC Mixer -> AIF1 -> Capture, but only thing I'm having is white noise.

Here is some debug info from capture:

Code:
$ cat './1c22e00.codec/dapm/AIF1 Capture'

AIF1 Capture: On  in 4 out 1

 stream AIF1 Capture active

 out  "static" "Capture"

 in  "static" "AIF1 AD0L"

$ cat /sys/kernel/debug/asoc/sun50i-a64-audio/1c22e00.codec/dapm/AIF1 AD0L

AIF1 AD0L: Off  in 4 out 0 - R68(0x44) mask 0x8000

 stream AIF1 Capture inactive

 out  "static" "AIF1 Capture"

 in  "static" "AIF1 AD0L Stereo Mux"

 in  "static" "RST AIF1"

$ cat './1c22e00.codec/dapm/AIF1 AD0L'

AIF1 AD0L: On  in 4 out 1 - R68(0x44) mask 0x8000

 stream AIF1 Capture inactive

 out  "static" "AIF1 Capture"

 in  "static" "AIF1 AD0L Stereo Mux"

 in  "static" "RST AIF1"

$ cat './1c22e00.codec/dapm/AIF1 AD0L Stereo Mux'

AIF1 AD0L Stereo Mux: On  in 4 out 1

 out  "static" "AIF1 AD0L"

 in  "Sum Mono" "AIF1 AD0R Mixer"

 in  "Sum Mono" "AIF1 AD0L Mixer"

$ cat './1f015c0.codec-analog/dapm/Mic2 Amplifier'

Mic2 Amplifier: On  in 1 out 2 - R8(0x8) mask 0x8

 out  "Mic2 Capture Switch" "Right ADC Mixer"

 out  "Mic2 Capture Switch" "Left ADC Mixer"

 in  "static" "MIC2"

]]>
I have archlinux running on pine64+, everything is fine except mic input. Output to 3.5mm jack works nice, but I can't get recording anything. Can you please share asound.state file with mic enabled.
So far I went through sound codec code and tried to enabled the path from Mic2 -> DAC Mixer -> AIF1 -> Capture, but only thing I'm having is white noise.

Here is some debug info from capture:

Code:
$ cat './1c22e00.codec/dapm/AIF1 Capture'

AIF1 Capture: On  in 4 out 1

 stream AIF1 Capture active

 out  "static" "Capture"

 in  "static" "AIF1 AD0L"

$ cat /sys/kernel/debug/asoc/sun50i-a64-audio/1c22e00.codec/dapm/AIF1 AD0L

AIF1 AD0L: Off  in 4 out 0 - R68(0x44) mask 0x8000

 stream AIF1 Capture inactive

 out  "static" "AIF1 Capture"

 in  "static" "AIF1 AD0L Stereo Mux"

 in  "static" "RST AIF1"

$ cat './1c22e00.codec/dapm/AIF1 AD0L'

AIF1 AD0L: On  in 4 out 1 - R68(0x44) mask 0x8000

 stream AIF1 Capture inactive

 out  "static" "AIF1 Capture"

 in  "static" "AIF1 AD0L Stereo Mux"

 in  "static" "RST AIF1"

$ cat './1c22e00.codec/dapm/AIF1 AD0L Stereo Mux'

AIF1 AD0L Stereo Mux: On  in 4 out 1

 out  "static" "AIF1 AD0L"

 in  "Sum Mono" "AIF1 AD0R Mixer"

 in  "Sum Mono" "AIF1 AD0L Mixer"

$ cat './1f015c0.codec-analog/dapm/Mic2 Amplifier'

Mic2 Amplifier: On  in 1 out 2 - R8(0x8) mask 0x8

 out  "Mic2 Capture Switch" "Right ADC Mixer"

 out  "Mic2 Capture Switch" "Left ADC Mixer"

 in  "static" "MIC2"

]]> <![CDATA[Devuan 3.1 on A64+?]]> https://forum.pine64.org/showthread.php?tid=14399 Sat, 10 Jul 2021 15:30:17 +0000 Obliterous]]> https://forum.pine64.org/showthread.php?tid=14399
I've tried following a few guides and nothing has worked so far...]]>
I've tried following a few guides and nothing has worked so far...]]> <![CDATA[Open Media Vault - Help needed]]> https://forum.pine64.org/showthread.php?tid=13527 Tue, 30 Mar 2021 12:42:25 +0000 janeku]]> https://forum.pine64.org/showthread.php?tid=13527 I know there is some info about open media vault and using Pine64+ as a NAS device on this forum, but looks like OMV is no longer supported.
Would somebody help me and explain me how and where to download image for OMV to run on my Pine64+ board ?
Or just tu put a link to iso image (OMV github is active but I can't find any Pine64 iso's) where I can download it.
Also new experiences concerning Pie64+ and it use as a NAS storage device would be appreciated.
Regards,]]> I know there is some info about open media vault and using Pine64+ as a NAS device on this forum, but looks like OMV is no longer supported.
Would somebody help me and explain me how and where to download image for OMV to run on my Pine64+ board ?
Or just tu put a link to iso image (OMV github is active but I can't find any Pine64 iso's) where I can download it.
Also new experiences concerning Pie64+ and it use as a NAS storage device would be appreciated.
Regards,]]> <![CDATA[Zwave module not loaded]]> https://forum.pine64.org/showthread.php?tid=13022 Sun, 07 Feb 2021 08:55:16 +0000 caragk]]> https://forum.pine64.org/showthread.php?tid=13022

I recently had to reinstall my Pine64's DietPie (raspbian mod). I use this SBC as home automation (formerly Jeedom, trying now Hass.io) with the Pine64 Zwave GPIO module.

Before this module was well recognised with Jeedom. But after reinstall (and DietPie upgrade) it isn't anymore. I first thought about a problem in HassIO's Zwave integration but it isn't. I mean /dev/ttyS2 don't link to the module :

Code:
# dmesg | grep -i tty

[    0.000000] Kernel command line: root=UUID=45e3e951-caf9-4aa6-909d-ceb24242c91e rootwait rootfstype=ext4 console=ttyS0,115200 console=tty1 consoleblank=0 loglevel=4 ubootpart=1dd8dfdc-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u  

[    0.000460] printk: console [tty1] enabled

[    2.036068] printk: console [ttyS0] disabled

[    2.036157] 1c28000.serial: ttyS0 at MMIO 0x1c28000 (irq = 38, base_baud = 1500000) is a 16550A

[    2.049344] printk: console [ttyS0] enabled

[    2.050667] 1c28400.serial: ttyS1 at MMIO 0x1c28400 (irq = 39, base_baud = 1500000) is a 16550A

[    2.050812] serial serial0: tty port ttyS1 registered

[    6.022066] systemd[1]: Created slice system-getty.slice.

[    7.861583] usb 2-1: FTDI USB Serial Device converter now attached to ttyUSB0

[    7.866494] usb 4-1: FTDI USB Serial Device converter now attached to ttyUSB1

So it'd be a kernel module missing, isn't it ?

Here is my lsmod and my kernel version :

Code:
# uname -srv

Linux 5.10.12-sunxi64 #21.02.1 SMP Wed Feb 3 20:42:58 CET 2021

# lsmod

Module                  Size  Used by

xt_conntrack           16384  1

xt_MASQUERADE          20480  1

nf_conntrack_netlink    49152  0

xfrm_user              40960  1

xfrm_algo              16384  1 xfrm_user

nft_counter            16384  15

xt_addrtype            16384  2

nft_compat             20480  4

nft_chain_nat          16384  4

nf_nat                 40960  2 nft_chain_nat,xt_MASQUERADE

nf_conntrack          135168  4 xt_conntrack,nf_nat,nf_conntrack_netlink,xt_MASQUERADE

nf_defrag_ipv6         24576  1 nf_conntrack

nf_defrag_ipv4         16384  1 nf_conntrack

nf_tables             176128  45 nft_compat,nft_counter,nft_chain_nat

nfnetlink              16384  4 nft_compat,nf_conntrack_netlink,nf_tables

br_netfilter           28672  0

bridge                233472  1 br_netfilter

aufs                  229376  0

overlay               114688  0

sunxi_cedrus           36864  0

ftdi_sio               61440  2

snd_soc_hdmi_codec     20480  1

usbserial              45056  5 ftdi_sio

videobuf2_dma_contig    24576  1 sunxi_cedrus

axp20x_battery         16384  0

axp20x_ac_power        16384  0

v4l2_mem2mem           36864  1 sunxi_cedrus

sun4i_gpadc_iio        24576  0

axp20x_adc             20480  0

lima                   57344  0

videobuf2_memops       20480  1 videobuf2_dma_contig

videobuf2_v4l2         24576  2 sunxi_cedrus,v4l2_mem2mem

industrialio           65536  4 axp20x_battery,sun4i_gpadc_iio,axp20x_ac_power,axp20x_adc

gpu_sched              32768  1 lima

videobuf2_common       49152  3 sunxi_cedrus,videobuf2_v4l2,v4l2_mem2mem

sun4i_i2s              24576  4

dw_hdmi_cec            16384  0

dw_hdmi_i2s_audio      16384  0

videodev              241664  4 sunxi_cedrus,videobuf2_v4l2,videobuf2_common,v4l2_mem2mem

snd_soc_simple_card    24576  0

mc                     49152  5 sunxi_cedrus,videodev,videobuf2_v4l2,videobuf2_common,v4l2_mem2mem

sun8i_ce               28672  0

snd_soc_simple_card_utils    24576  1 snd_soc_simple_card

display_connector      20480  0

crypto_engine          20480  1 sun8i_ce

cpufreq_dt             20480  0

realtek                24576  1

pinctrl_axp209         16384  0

dwmac_sun8i            28672  0

mdio_mux               16384  1 dwmac_sun8i

i2c_mv64xxx            24576  0

Is that Marvell i2c_mv64xxx the linux kernel module for the Pine64 Zwave module ? I can't find which exact hardware it is...

I found some threads (like this one but also for others dist or SBC) about I2C, SPI, UART and hdi_uart (Bluetooth) so I've tested to add any of those kernel modules without any success...

My kernel I2C config :

Code:
# cat /proc/config.gz | gunzip | grep -i i2c

CONFIG_NFC_FDP_I2C=m

CONFIG_NFC_PN544_I2C=m

CONFIG_NFC_PN533_I2C=m

CONFIG_NFC_MICROREAD_I2C=m

CONFIG_NFC_MRVL_I2C=m

CONFIG_NFC_ST21NFCA_I2C=m

CONFIG_NFC_ST_NCI_I2C=m

CONFIG_NFC_NXP_NCI_I2C=m

CONFIG_NFC_S3FWRN5_I2C=m

CONFIG_REGMAP_I2C=y

# CONFIG_SENSORS_LIS3_I2C is not set

CONFIG_NET_DSA_MICROCHIP_KSZ9477_I2C=m

# CONFIG_NET_DSA_SMSC_LAN9303_I2C is not set

# CONFIG_MOUSE_ELAN_I2C is not set

# CONFIG_MOUSE_SYNAPTICS_I2C is not set

CONFIG_TOUCHSCREEN_AD7879_I2C=m

CONFIG_TOUCHSCREEN_AR1021_I2C=m

# CONFIG_TOUCHSCREEN_WACOM_I2C is not set

# CONFIG_TOUCHSCREEN_WDT87XX_I2C is not set

# CONFIG_TOUCHSCREEN_SIS_I2C is not set

CONFIG_RMI4_I2C=m

CONFIG_SERIAL_SC16IS7XX_I2C=y

CONFIG_TCG_TIS_I2C_ATMEL=m

CONFIG_TCG_TIS_I2C_INFINEON=m

CONFIG_TCG_TIS_I2C_NUVOTON=m

CONFIG_TCG_TIS_ST33ZP24_I2C=m

# I2C support

CONFIG_I2C=y

CONFIG_I2C_BOARDINFO=y

CONFIG_I2C_COMPAT=y

CONFIG_I2C_CHARDEV=y

CONFIG_I2C_MUX=y

# Multiplexer I2C Chip support

CONFIG_I2C_ARB_GPIO_CHALLENGE=m

CONFIG_I2C_MUX_GPIO=m

CONFIG_I2C_MUX_GPMUX=m

CONFIG_I2C_MUX_LTC4306=m

CONFIG_I2C_MUX_PCA9541=m

CONFIG_I2C_MUX_PCA954x=m

CONFIG_I2C_MUX_PINCTRL=m

CONFIG_I2C_MUX_REG=m

CONFIG_I2C_DEMUX_PINCTRL=m

CONFIG_I2C_MUX_MLXCPLD=m

# end of Multiplexer I2C Chip support

CONFIG_I2C_HELPER_AUTO=y

CONFIG_I2C_SMBUS=m

CONFIG_I2C_ALGOBIT=y

CONFIG_I2C_ALGOPCA=m

# I2C Hardware Bus support

# I2C system bus drivers (mostly embedded / system-on-chip)

CONFIG_I2C_CADENCE=m

CONFIG_I2C_CBUS_GPIO=m

CONFIG_I2C_DESIGNWARE_CORE=y

# CONFIG_I2C_DESIGNWARE_SLAVE is not set

CONFIG_I2C_DESIGNWARE_PLATFORM=y

CONFIG_I2C_EMEV2=m

CONFIG_I2C_GPIO=m

# CONFIG_I2C_GPIO_FAULT_INJECTOR is not set

CONFIG_I2C_MV64XXX=m

CONFIG_I2C_NOMADIK=m

CONFIG_I2C_OCORES=m

CONFIG_I2C_PCA_PLATFORM=m

CONFIG_I2C_RK3X=m

CONFIG_I2C_SIMTEC=m

CONFIG_I2C_XILINX=m

# External I2C/SMBus adapter drivers

CONFIG_I2C_DIOLAN_U2C=m

CONFIG_I2C_ROBOTFUZZ_OSIF=m

CONFIG_I2C_TAOS_EVM=m

CONFIG_I2C_TINY_USB=m

# Other I2C/SMBus bus drivers

# end of I2C Hardware Bus support

CONFIG_I2C_STUB=m

CONFIG_I2C_SLAVE=y

CONFIG_I2C_SLAVE_EEPROM=m

# CONFIG_I2C_SLAVE_TESTUNIT is not set

# CONFIG_I2C_DEBUG_CORE is not set

# CONFIG_I2C_DEBUG_ALGO is not set

# CONFIG_I2C_DEBUG_BUS is not set

# end of I2C support

# I2C GPIO expanders

# end of I2C GPIO expanders

CONFIG_BATTERY_BQ27XXX_I2C=m

CONFIG_SENSORS_LTC2947_I2C=m

CONFIG_SENSORS_OCC_P8_I2C=m

CONFIG_MFD_AXP20X_I2C=y

CONFIG_MFD_MADERA_I2C=m

# CONFIG_MFD_DA9052_I2C is not set

# CONFIG_MFD_MC13XXX_I2C is not set

# CONFIG_HTC_I2CPLD is not set

# CONFIG_MFD_TPS65912_I2C is not set

# CONFIG_MFD_ARIZONA_I2C is not set

# CONFIG_MFD_WM831X_I2C is not set

# CONFIG_MFD_WM8350_I2C is not set

CONFIG_VIDEO_V4L2_I2C=y

# IR I2C driver auto-selected by 'Autoselect ancillary drivers'

CONFIG_VIDEO_IR_I2C=m

# audio, video and radio I2C drivers auto-selected by 'Autoselect ancillary drivers'

# SPI I2C drivers auto-selected by 'Autoselect ancillary drivers'

# I2C encoder or helper chips

CONFIG_DRM_I2C_CH7006=m

CONFIG_DRM_I2C_SIL164=m

# CONFIG_DRM_I2C_NXP_TDA998X is not set

CONFIG_DRM_I2C_NXP_TDA9950=m

# end of I2C encoder or helper chips

# CONFIG_DRM_I2C_ADV7511 is not set

CONFIG_SND_SOC_I2C_AND_SPI=y

# CONFIG_SND_SOC_ADAU1761_I2C is not set

CONFIG_SND_SOC_ADAU7118_I2C=m

# CONFIG_SND_SOC_CS42L51_I2C is not set

# CONFIG_SND_SOC_CS4271_I2C is not set

# CONFIG_SND_SOC_CS42XX8_I2C is not set

# CONFIG_SND_SOC_ES8328_I2C is not set

# CONFIG_SND_SOC_MAX98373_I2C is not set

CONFIG_SND_SOC_PCM1789_I2C=m

# CONFIG_SND_SOC_PCM179X_I2C is not set

CONFIG_SND_SOC_PCM186X_I2C=m

CONFIG_SND_SOC_PCM3060_I2C=m

# CONFIG_SND_SOC_PCM3168A_I2C is not set

# CONFIG_SND_SOC_PCM512x_I2C is not set

# CONFIG_SND_SOC_SSM2602_I2C is not set

# CONFIG_SND_SOC_TLV320AIC23_I2C is not set

CONFIG_SND_SOC_TLV320AIC32X4_I2C=m

# CONFIG_SND_SOC_WM8804_I2C is not set

# I2C HID support

CONFIG_I2C_HID=m

# end of I2C HID support

# I2C RTC drivers

CONFIG_RTC_I2C_AND_SPI=y

# SPI and I2C RTC drivers

# CONFIG_MOST_I2C is not set

CONFIG_ADXL345_I2C=m

CONFIG_ADXL372_I2C=m

CONFIG_BMA400_I2C=m

CONFIG_BMC150_ACCEL_I2C=m

CONFIG_IIO_ST_ACCEL_I2C_3AXIS=m

CONFIG_KXSD9_I2C=m

CONFIG_MMA7455_I2C=m

CONFIG_BME680_I2C=m

CONFIG_IIO_MS_SENSORS_I2C=m

CONFIG_IIO_ST_SENSORS_I2C=m

CONFIG_AD5696_I2C=m

CONFIG_BMG160_I2C=m

CONFIG_FXAS21002C_I2C=m

CONFIG_MPU3050_I2C=m

CONFIG_IIO_ST_GYRO_I2C_3AXIS=m

CONFIG_HTS221_I2C=m

# CONFIG_BMI160_I2C is not set

CONFIG_FXOS8700_I2C=m

# CONFIG_INV_ICM42600_I2C is not set

# CONFIG_INV_MPU6050_I2C is not set

CONFIG_ST_UVIS25_I2C=m

CONFIG_BMC150_MAGN_I2C=m

CONFIG_IIO_ST_MAGN_I2C_3AXIS=m

CONFIG_SENSORS_HMC5843_I2C=m

CONFIG_SENSORS_RM3100_I2C=m

CONFIG_BMP280_I2C=m

# CONFIG_MPL115_I2C is not set

CONFIG_VL53L0X_I2C=m

I2C devices founded :

Code:
# ls /sys/bus/i2c/devices/

i2c-0  i2c-1

Any idea there ? Which are the *right* kernel modules ?
As a n00b, I forgot to dd an image of the SDcard before erasing it (precisely I said f***k the moment I press Return)...]]>

I recently had to reinstall my Pine64's DietPie (raspbian mod). I use this SBC as home automation (formerly Jeedom, trying now Hass.io) with the Pine64 Zwave GPIO module.

Before this module was well recognised with Jeedom. But after reinstall (and DietPie upgrade) it isn't anymore. I first thought about a problem in HassIO's Zwave integration but it isn't. I mean /dev/ttyS2 don't link to the module :

Code:
# dmesg | grep -i tty

[    0.000000] Kernel command line: root=UUID=45e3e951-caf9-4aa6-909d-ceb24242c91e rootwait rootfstype=ext4 console=ttyS0,115200 console=tty1 consoleblank=0 loglevel=4 ubootpart=1dd8dfdc-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u  

[    0.000460] printk: console [tty1] enabled

[    2.036068] printk: console [ttyS0] disabled

[    2.036157] 1c28000.serial: ttyS0 at MMIO 0x1c28000 (irq = 38, base_baud = 1500000) is a 16550A

[    2.049344] printk: console [ttyS0] enabled

[    2.050667] 1c28400.serial: ttyS1 at MMIO 0x1c28400 (irq = 39, base_baud = 1500000) is a 16550A

[    2.050812] serial serial0: tty port ttyS1 registered

[    6.022066] systemd[1]: Created slice system-getty.slice.

[    7.861583] usb 2-1: FTDI USB Serial Device converter now attached to ttyUSB0

[    7.866494] usb 4-1: FTDI USB Serial Device converter now attached to ttyUSB1

So it'd be a kernel module missing, isn't it ?

Here is my lsmod and my kernel version :

Code:
# uname -srv

Linux 5.10.12-sunxi64 #21.02.1 SMP Wed Feb 3 20:42:58 CET 2021

# lsmod

Module                  Size  Used by

xt_conntrack           16384  1

xt_MASQUERADE          20480  1

nf_conntrack_netlink    49152  0

xfrm_user              40960  1

xfrm_algo              16384  1 xfrm_user

nft_counter            16384  15

xt_addrtype            16384  2

nft_compat             20480  4

nft_chain_nat          16384  4

nf_nat                 40960  2 nft_chain_nat,xt_MASQUERADE

nf_conntrack          135168  4 xt_conntrack,nf_nat,nf_conntrack_netlink,xt_MASQUERADE

nf_defrag_ipv6         24576  1 nf_conntrack

nf_defrag_ipv4         16384  1 nf_conntrack

nf_tables             176128  45 nft_compat,nft_counter,nft_chain_nat

nfnetlink              16384  4 nft_compat,nf_conntrack_netlink,nf_tables

br_netfilter           28672  0

bridge                233472  1 br_netfilter

aufs                  229376  0

overlay               114688  0

sunxi_cedrus           36864  0

ftdi_sio               61440  2

snd_soc_hdmi_codec     20480  1

usbserial              45056  5 ftdi_sio

videobuf2_dma_contig    24576  1 sunxi_cedrus

axp20x_battery         16384  0

axp20x_ac_power        16384  0

v4l2_mem2mem           36864  1 sunxi_cedrus

sun4i_gpadc_iio        24576  0

axp20x_adc             20480  0

lima                   57344  0

videobuf2_memops       20480  1 videobuf2_dma_contig

videobuf2_v4l2         24576  2 sunxi_cedrus,v4l2_mem2mem

industrialio           65536  4 axp20x_battery,sun4i_gpadc_iio,axp20x_ac_power,axp20x_adc

gpu_sched              32768  1 lima

videobuf2_common       49152  3 sunxi_cedrus,videobuf2_v4l2,v4l2_mem2mem

sun4i_i2s              24576  4

dw_hdmi_cec            16384  0

dw_hdmi_i2s_audio      16384  0

videodev              241664  4 sunxi_cedrus,videobuf2_v4l2,videobuf2_common,v4l2_mem2mem

snd_soc_simple_card    24576  0

mc                     49152  5 sunxi_cedrus,videodev,videobuf2_v4l2,videobuf2_common,v4l2_mem2mem

sun8i_ce               28672  0

snd_soc_simple_card_utils    24576  1 snd_soc_simple_card

display_connector      20480  0

crypto_engine          20480  1 sun8i_ce

cpufreq_dt             20480  0

realtek                24576  1

pinctrl_axp209         16384  0

dwmac_sun8i            28672  0

mdio_mux               16384  1 dwmac_sun8i

i2c_mv64xxx            24576  0

Code:
# cat /proc/config.gz | gunzip | grep -i i2c

CONFIG_NFC_FDP_I2C=m

CONFIG_NFC_PN544_I2C=m

CONFIG_NFC_PN533_I2C=m

CONFIG_NFC_MICROREAD_I2C=m

CONFIG_NFC_MRVL_I2C=m

CONFIG_NFC_ST21NFCA_I2C=m

CONFIG_NFC_ST_NCI_I2C=m

CONFIG_NFC_NXP_NCI_I2C=m

CONFIG_NFC_S3FWRN5_I2C=m

CONFIG_REGMAP_I2C=y

# CONFIG_SENSORS_LIS3_I2C is not set

CONFIG_NET_DSA_MICROCHIP_KSZ9477_I2C=m

# CONFIG_NET_DSA_SMSC_LAN9303_I2C is not set

# CONFIG_MOUSE_ELAN_I2C is not set

# CONFIG_MOUSE_SYNAPTICS_I2C is not set

CONFIG_TOUCHSCREEN_AD7879_I2C=m

CONFIG_TOUCHSCREEN_AR1021_I2C=m

# CONFIG_TOUCHSCREEN_WACOM_I2C is not set

# CONFIG_TOUCHSCREEN_WDT87XX_I2C is not set

# CONFIG_TOUCHSCREEN_SIS_I2C is not set

CONFIG_RMI4_I2C=m

CONFIG_SERIAL_SC16IS7XX_I2C=y

CONFIG_TCG_TIS_I2C_ATMEL=m

CONFIG_TCG_TIS_I2C_INFINEON=m

CONFIG_TCG_TIS_I2C_NUVOTON=m

CONFIG_TCG_TIS_ST33ZP24_I2C=m

# I2C support

CONFIG_I2C=y

CONFIG_I2C_BOARDINFO=y

CONFIG_I2C_COMPAT=y

CONFIG_I2C_CHARDEV=y

CONFIG_I2C_MUX=y

# Multiplexer I2C Chip support

CONFIG_I2C_ARB_GPIO_CHALLENGE=m

CONFIG_I2C_MUX_GPIO=m

CONFIG_I2C_MUX_GPMUX=m

CONFIG_I2C_MUX_LTC4306=m

CONFIG_I2C_MUX_PCA9541=m

CONFIG_I2C_MUX_PCA954x=m

CONFIG_I2C_MUX_PINCTRL=m

CONFIG_I2C_MUX_REG=m

CONFIG_I2C_DEMUX_PINCTRL=m

CONFIG_I2C_MUX_MLXCPLD=m

# end of Multiplexer I2C Chip support

CONFIG_I2C_HELPER_AUTO=y

CONFIG_I2C_SMBUS=m

CONFIG_I2C_ALGOBIT=y

CONFIG_I2C_ALGOPCA=m

# I2C Hardware Bus support

# I2C system bus drivers (mostly embedded / system-on-chip)

CONFIG_I2C_CADENCE=m

CONFIG_I2C_CBUS_GPIO=m

CONFIG_I2C_DESIGNWARE_CORE=y

# CONFIG_I2C_DESIGNWARE_SLAVE is not set

CONFIG_I2C_DESIGNWARE_PLATFORM=y

CONFIG_I2C_EMEV2=m

CONFIG_I2C_GPIO=m

# CONFIG_I2C_GPIO_FAULT_INJECTOR is not set

CONFIG_I2C_MV64XXX=m

CONFIG_I2C_NOMADIK=m

CONFIG_I2C_OCORES=m

CONFIG_I2C_PCA_PLATFORM=m

CONFIG_I2C_RK3X=m

CONFIG_I2C_SIMTEC=m

CONFIG_I2C_XILINX=m

# External I2C/SMBus adapter drivers

CONFIG_I2C_DIOLAN_U2C=m

CONFIG_I2C_ROBOTFUZZ_OSIF=m

CONFIG_I2C_TAOS_EVM=m

CONFIG_I2C_TINY_USB=m

# Other I2C/SMBus bus drivers

# end of I2C Hardware Bus support

CONFIG_I2C_STUB=m

CONFIG_I2C_SLAVE=y

CONFIG_I2C_SLAVE_EEPROM=m

# CONFIG_I2C_SLAVE_TESTUNIT is not set

# CONFIG_I2C_DEBUG_CORE is not set

# CONFIG_I2C_DEBUG_ALGO is not set

# CONFIG_I2C_DEBUG_BUS is not set

# end of I2C support

# I2C GPIO expanders

# end of I2C GPIO expanders

CONFIG_BATTERY_BQ27XXX_I2C=m

CONFIG_SENSORS_LTC2947_I2C=m

CONFIG_SENSORS_OCC_P8_I2C=m

CONFIG_MFD_AXP20X_I2C=y

CONFIG_MFD_MADERA_I2C=m

# CONFIG_MFD_DA9052_I2C is not set

# CONFIG_MFD_MC13XXX_I2C is not set

# CONFIG_HTC_I2CPLD is not set

# CONFIG_MFD_TPS65912_I2C is not set

# CONFIG_MFD_ARIZONA_I2C is not set

# CONFIG_MFD_WM831X_I2C is not set

# CONFIG_MFD_WM8350_I2C is not set

CONFIG_VIDEO_V4L2_I2C=y

# IR I2C driver auto-selected by 'Autoselect ancillary drivers'

CONFIG_VIDEO_IR_I2C=m

# audio, video and radio I2C drivers auto-selected by 'Autoselect ancillary drivers'

# SPI I2C drivers auto-selected by 'Autoselect ancillary drivers'

# I2C encoder or helper chips

CONFIG_DRM_I2C_CH7006=m

CONFIG_DRM_I2C_SIL164=m

# CONFIG_DRM_I2C_NXP_TDA998X is not set

CONFIG_DRM_I2C_NXP_TDA9950=m

# end of I2C encoder or helper chips

# CONFIG_DRM_I2C_ADV7511 is not set

CONFIG_SND_SOC_I2C_AND_SPI=y

# CONFIG_SND_SOC_ADAU1761_I2C is not set

CONFIG_SND_SOC_ADAU7118_I2C=m

# CONFIG_SND_SOC_CS42L51_I2C is not set

# CONFIG_SND_SOC_CS4271_I2C is not set

# CONFIG_SND_SOC_CS42XX8_I2C is not set

# CONFIG_SND_SOC_ES8328_I2C is not set

# CONFIG_SND_SOC_MAX98373_I2C is not set

CONFIG_SND_SOC_PCM1789_I2C=m

# CONFIG_SND_SOC_PCM179X_I2C is not set

CONFIG_SND_SOC_PCM186X_I2C=m

CONFIG_SND_SOC_PCM3060_I2C=m

# CONFIG_SND_SOC_PCM3168A_I2C is not set

# CONFIG_SND_SOC_PCM512x_I2C is not set

# CONFIG_SND_SOC_SSM2602_I2C is not set

# CONFIG_SND_SOC_TLV320AIC23_I2C is not set

CONFIG_SND_SOC_TLV320AIC32X4_I2C=m

# CONFIG_SND_SOC_WM8804_I2C is not set

# I2C HID support

CONFIG_I2C_HID=m

# end of I2C HID support

# I2C RTC drivers

CONFIG_RTC_I2C_AND_SPI=y

# SPI and I2C RTC drivers

# CONFIG_MOST_I2C is not set

CONFIG_ADXL345_I2C=m

CONFIG_ADXL372_I2C=m

CONFIG_BMA400_I2C=m

CONFIG_BMC150_ACCEL_I2C=m

CONFIG_IIO_ST_ACCEL_I2C_3AXIS=m

CONFIG_KXSD9_I2C=m

CONFIG_MMA7455_I2C=m

CONFIG_BME680_I2C=m

CONFIG_IIO_MS_SENSORS_I2C=m

CONFIG_IIO_ST_SENSORS_I2C=m

CONFIG_AD5696_I2C=m

CONFIG_BMG160_I2C=m

CONFIG_FXAS21002C_I2C=m

CONFIG_MPU3050_I2C=m

CONFIG_IIO_ST_GYRO_I2C_3AXIS=m

CONFIG_HTS221_I2C=m

# CONFIG_BMI160_I2C is not set

CONFIG_FXOS8700_I2C=m

# CONFIG_INV_ICM42600_I2C is not set

# CONFIG_INV_MPU6050_I2C is not set

CONFIG_ST_UVIS25_I2C=m

CONFIG_BMC150_MAGN_I2C=m

CONFIG_IIO_ST_MAGN_I2C_3AXIS=m

CONFIG_SENSORS_HMC5843_I2C=m

CONFIG_SENSORS_RM3100_I2C=m

CONFIG_BMP280_I2C=m

# CONFIG_MPL115_I2C is not set

CONFIG_VL53L0X_I2C=m

I2C devices founded :

Code:
# ls /sys/bus/i2c/devices/

i2c-0  i2c-1

Any idea there ? Which are the *right* kernel modules ?
As a n00b, I forgot to dd an image of the SDcard before erasing it (precisely I said f***k the moment I press Return)...]]> <![CDATA[DietPi OS for PINE A64]]> https://forum.pine64.org/showthread.php?tid=12513 Tue, 15 Dec 2020 12:11:58 +0000 MichaIng]]> https://forum.pine64.org/showthread.php?tid=12513

DietPi is an extremely lightweight Debian-based OS. It is highly optimised for minimal CPU and RAM resource usage, ensuring your PINE A64 always runs at its maximum potential.

Use dietpi-software to quick and easy install Ready to Run & Optimised applications for your system. DietPi will do all the necessary configurations, including starting the services.

DietPi images are available for PINE A64, PINE H64, Pinebook, ROCK64 and ROCKPro64.

Our PINE64 images are based on the great kernel and firmware, developed by Armbian. However, if you face any issues, please contact us via forum or GitHub issue first.

Website: https://dietpi.com/
Download images: https://dietpi.com/#download
Documentation: https://dietpi.com/docs/
Forums: https://dietpi.com/phpbb/
GitHub repository: https://github.com/MichaIng/DietPi

DietPi is a free and open-source project. We are be happy if you consider to contribute or donate: https://dietpi.com/contribute.html
Consider to share your donation between DietPi and Armbian.]]>

DietPi is an extremely lightweight Debian-based OS. It is highly optimised for minimal CPU and RAM resource usage, ensuring your PINE A64 always runs at its maximum potential.

Use dietpi-software to quick and easy install Ready to Run & Optimised applications for your system. DietPi will do all the necessary configurations, including starting the services.

DietPi images are available for PINE A64, PINE H64, Pinebook, ROCK64 and ROCKPro64.

Our PINE64 images are based on the great kernel and firmware, developed by Armbian. However, if you face any issues, please contact us via forum or GitHub issue first.

Website: https://dietpi.com/
Download images: https://dietpi.com/#download
Documentation: https://dietpi.com/docs/
Forums: https://dietpi.com/phpbb/
GitHub repository: https://github.com/MichaIng/DietPi

DietPi is a free and open-source project. We are be happy if you consider to contribute or donate: https://dietpi.com/contribute.html
Consider to share your donation between DietPi and Armbian.]]> <![CDATA[Fedora 32/CentOS 8 Pine A64+ Images]]> https://forum.pine64.org/showthread.php?tid=11157 Thu, 27 Aug 2020 02:50:55 +0000 wideawake]]> https://forum.pine64.org/showthread.php?tid=11157
I got my hands on some 2GB A64+ boards and noticed there were no Fedora 32 or CentOS 8 images so I decided to throw some together.

These images are using the armbian 5.7.15 kernel and firmware. I have bundled them into rpms and installed them into the base images.

CentOS 8
CentOS8-Minimal-202008.0.pine64-plus.img.xz
CentOS8-Server-202008.0.pine64-plus.img.xz
Username: root
Password: centos

Fedora 32
Fedora32-Minimal-202008.0.pine64-plus.img.xz
Fedora32-Server-202008.0.pine64-plus.img.xz
Username: root
Password: fedora

Debating doing some with a desktop environment installed if any interest is shown. If you run into any issues, please post there here.

Cheers,
Mike]]>
I got my hands on some 2GB A64+ boards and noticed there were no Fedora 32 or CentOS 8 images so I decided to throw some together.

These images are using the armbian 5.7.15 kernel and firmware. I have bundled them into rpms and installed them into the base images.

CentOS 8
CentOS8-Minimal-202008.0.pine64-plus.img.xz
CentOS8-Server-202008.0.pine64-plus.img.xz
Username: root
Password: centos

Fedora 32
Fedora32-Minimal-202008.0.pine64-plus.img.xz
Fedora32-Server-202008.0.pine64-plus.img.xz
Username: root
Password: fedora

Debating doing some with a desktop environment installed if any interest is shown. If you run into any issues, please post there here.

Cheers,
Mike]]> <![CDATA[Pine A64+ mainline mipi-dsi]]> https://forum.pine64.org/showthread.php?tid=9751 Mon, 27 Apr 2020 11:56:48 +0000 Learnincurve]]> https://forum.pine64.org/showthread.php?tid=9751
Kernel 5.6 is out and mipi-dsi is finally in there, so the pine lcd screen (feiyang) should now finally work with the mainline kernel.

Can anyone say how to set this up? Armbian is available with this kernel through build scripts and nightly builds, but I can't work out how to set up uboot, to initialize the mipi-dsi pipeline.

Any help greatly appreciated!

BR.

--Learnincurve--]]>
Kernel 5.6 is out and mipi-dsi is finally in there, so the pine lcd screen (feiyang) should now finally work with the mainline kernel.

Can anyone say how to set this up? Armbian is available with this kernel through build scripts and nightly builds, but I can't work out how to set up uboot, to initialize the mipi-dsi pipeline.

Any help greatly appreciated!

BR.

--Learnincurve--]]> <![CDATA[Manjaro IMG for A64+]]> https://forum.pine64.org/showthread.php?tid=9568 Thu, 02 Apr 2020 16:20:48 +0000 tophneal]]> https://forum.pine64.org/showthread.php?tid=9568 <![CDATA[Manjaro arm on pine64+]]> https://forum.pine64.org/showthread.php?tid=7909 Tue, 27 Aug 2019 14:27:46 +0000 roel]]> https://forum.pine64.org/showthread.php?tid=7909
I made a build of Manjaro arm for the pine64+. Everything works fine, only sound through hdmi with most recent kernels doesn't work. With kernel 4.2 hdmi sound works. Analogue sound works.
As it was just a few changes in the manjaro-arm-tools they added them in git -> https://gitlab.manjaro.org/manjaro-arm/a...-arm-tools
So probably with the next manjaro arm release there will be a image for the pine64+.
As I don't have the wifi and DAC board I couldn't test if they work, so don't expect them to work.]]>
I made a build of Manjaro arm for the pine64+. Everything works fine, only sound through hdmi with most recent kernels doesn't work. With kernel 4.2 hdmi sound works. Analogue sound works.
As it was just a few changes in the manjaro-arm-tools they added them in git -> https://gitlab.manjaro.org/manjaro-arm/a...-arm-tools
So probably with the next manjaro arm release there will be a image for the pine64+.
As I don't have the wifi and DAC board I couldn't test if they work, so don't expect them to work.]]> <![CDATA[Fedora 30 on Pinebook]]> https://forum.pine64.org/showthread.php?tid=7844 Wed, 14 Aug 2019 17:41:58 +0000 sdgathman]]> https://forum.pine64.org/showthread.php?tid=7844
Fedora 30 installed on my Pinebook with only a few issues. The main one being that brightness defaulted to 0 on the original aarch64 image. :-P

I booted the SD on an rPi3 to do initial configuration, and updates. Then used the dracut option to create a multi-platform initrd for the new kernel, and moved the SD card back to the Pinebook. The newer kernel defaults to brightness 2 - so I took it into a dark bathroom to navigate /sys and set a higher brightness, and change the text console fonts to the biggest available. :-) Fedora uses upstream kernels, so it reflects the state of A64 support in the mainline kernel.

I've been using it a few weeks now. Here are the biggest issues:

1) the biggest issue is lack of support for cpufreq on A64. It feels like 500Mhz, but without any supported readout, that is subjective. Bogomips is 48.0. I don't know what the cpufreq actually defaults to, but let's just say I do aarch64 builds on a 1G rPI3... What is needed to get that upstream?

2) the second most annoying problem is lack of support for internal wifi. This is worked around by adding one of those tiny EdiMax wifi dongles (the big long ones can pose a danger of geting caught on something and damaging the USB port).

3) the third problem is inability to read mic input. The mics are active - because if you turn up the gain, they feed back. And if you connect some speakers to the audio out, the pinebook becomes a megaphone. However, ALSA doesn't know how to make the mic data available to apps like Sound Recorder, Linphone, etc.

4) the internal bluetooth is also not supported. It would be nice to connect decent speakers (the internal speakers are understandably tinny tiny ones) or headset without resorting to an audio cable or yet another dongle.

5) the Mali GPU is not supported. I just use LXDE, which doesn't require 3D, and video playback is fine (xorg reports video accel active). So this is the least important unsupported feature for this user.

I should mention that the sound quality via decent headphones attached by audio cable is quite impressive. Engineering clean audio in a digital environment takes a lot of attention to detail - so kudos to the engineers.]]>
Fedora 30 installed on my Pinebook with only a few issues. The main one being that brightness defaulted to 0 on the original aarch64 image. :-P

I booted the SD on an rPi3 to do initial configuration, and updates. Then used the dracut option to create a multi-platform initrd for the new kernel, and moved the SD card back to the Pinebook. The newer kernel defaults to brightness 2 - so I took it into a dark bathroom to navigate /sys and set a higher brightness, and change the text console fonts to the biggest available. :-) Fedora uses upstream kernels, so it reflects the state of A64 support in the mainline kernel.

I've been using it a few weeks now. Here are the biggest issues:

1) the biggest issue is lack of support for cpufreq on A64. It feels like 500Mhz, but without any supported readout, that is subjective. Bogomips is 48.0. I don't know what the cpufreq actually defaults to, but let's just say I do aarch64 builds on a 1G rPI3... What is needed to get that upstream?

2) the second most annoying problem is lack of support for internal wifi. This is worked around by adding one of those tiny EdiMax wifi dongles (the big long ones can pose a danger of geting caught on something and damaging the USB port).

3) the third problem is inability to read mic input. The mics are active - because if you turn up the gain, they feed back. And if you connect some speakers to the audio out, the pinebook becomes a megaphone. However, ALSA doesn't know how to make the mic data available to apps like Sound Recorder, Linphone, etc.

4) the internal bluetooth is also not supported. It would be nice to connect decent speakers (the internal speakers are understandably tinny tiny ones) or headset without resorting to an audio cable or yet another dongle.

5) the Mali GPU is not supported. I just use LXDE, which doesn't require 3D, and video playback is fine (xorg reports video accel active). So this is the least important unsupported feature for this user.

I should mention that the sound quality via decent headphones attached by audio cable is quite impressive. Engineering clean audio in a digital environment takes a lot of attention to detail - so kudos to the engineers.]]> <![CDATA[Lakka-nightlies for Pine A64 (and H64)]]> https://forum.pine64.org/showthread.php?tid=7832 Sun, 11 Aug 2019 09:02:16 +0000 roel]]> https://forum.pine64.org/showthread.php?tid=7832
I just recently discovered that Lakka is available in the nightlies for the pine allwinner boards. I tested it on my A64+ and what I tested (NES, SNES, GBA, PSX, DOOM, Quake) worked. N64 and NDS didn't work. (I didn't have other roms to try).

What also didn't work was HDMI sound, I couldn't test analog out as I broke my headphones.

Here is the link: http://nightly.builds.lakka.tv/Lakka-LE9.2/latest/

Probably most thanks to Jernej as he made this boards available in the libreelec 9.2 build system.

I don't have a pine H64 to test the lakka builds. And I'm sill wondering wich board would be better, the rock64 or the pineH64 to run emulation on.]]>
I just recently discovered that Lakka is available in the nightlies for the pine allwinner boards. I tested it on my A64+ and what I tested (NES, SNES, GBA, PSX, DOOM, Quake) worked. N64 and NDS didn't work. (I didn't have other roms to try).

What also didn't work was HDMI sound, I couldn't test analog out as I broke my headphones.

Here is the link: http://nightly.builds.lakka.tv/Lakka-LE9.2/latest/

Probably most thanks to Jernej as he made this boards available in the libreelec 9.2 build system.

I don't have a pine H64 to test the lakka builds. And I'm sill wondering wich board would be better, the rock64 or the pineH64 to run emulation on.]]> <![CDATA[PineA64+: Audio in 5.0 Kernel]]> https://forum.pine64.org/showthread.php?tid=7664 Fri, 05 Jul 2019 14:49:44 +0000 puzzles]]> https://forum.pine64.org/showthread.php?tid=7664
Additional information:
Kernel was built from source by tweaking the 5.0-trunk config as such:

Code:
+CONFIG_SND_SUN4I_CODEC=m

+CONFIG_SND_SUN8I_CODEC=m

+CONFIG_SND_SUN8I_CODEC_ANALOG=m

+CONFIG_SND_SUN50I_CODEC_ANALOG=m

+CONFIG_SND_SUN4I_I2S=m

+CONFIG_SND_SUN4I_SPDIF=m

+CONFIG_SND_SUN8I_ADDA_PR_REGMAP=m

+CONFIG_SUN50I_ERRATUM_UNKNOWN1=y

DTB file should enable the audio interface
sun*i* modules are loaded]]>
Additional information:
Kernel was built from source by tweaking the 5.0-trunk config as such:

Code:
+CONFIG_SND_SUN4I_CODEC=m

+CONFIG_SND_SUN8I_CODEC=m

+CONFIG_SND_SUN8I_CODEC_ANALOG=m

+CONFIG_SND_SUN50I_CODEC_ANALOG=m

+CONFIG_SND_SUN4I_I2S=m

+CONFIG_SND_SUN4I_SPDIF=m

+CONFIG_SND_SUN8I_ADDA_PR_REGMAP=m

+CONFIG_SUN50I_ERRATUM_UNKNOWN1=y

DTB file should enable the audio interface
sun*i* modules are loaded]]> <![CDATA[LibreELEC(KODI) for Pine A64 (+)]]> https://forum.pine64.org/showthread.php?tid=7478 Fri, 10 May 2019 09:16:11 +0000 pineadmin]]> https://forum.pine64.org/showthread.php?tid=7478 LibreELEC(KODI) - 20190324 to Wiki and PINE64 Installer.]]> LibreELEC(KODI) - 20190324 to Wiki and PINE64 Installer.]]> <![CDATA[Arch, Debian or other for Pinebook?]]> https://forum.pine64.org/showthread.php?tid=7422 Thu, 25 Apr 2019 22:31:58 +0000 cootcraig]]> https://forum.pine64.org/showthread.php?tid=7422 20190112 ArchLinux from Anarsoul. I decided to ask what distro's might be best on a Pinebook. On my desktop I use Arch (my current favorite) and Debian. For the Pinebook, I'm just looking for ease of use, good performance and best distro support. What is recommended?]]> 20190112 ArchLinux from Anarsoul. I decided to ask what distro's might be best on a Pinebook. On my desktop I use Arch (my current favorite) and Debian. For the Pinebook, I'm just looking for ease of use, good performance and best distro support. What is recommended?]]>