atone

You didn’t get any update for transmission? I guess you have to contact their support.

I don't know if editing armbian_firstlogin is the right thing to do. Wouldn't it prevent the source code from being updated (git pull) or make it more difficult? Did you already looked at the following links? https://docs.armbian.com/Developer-Guide_User-Configurations/ https://docs.armbian.com/Developer-Guide_Extensions/ https://docs.armbian.com/Developer-Guide_Extensions-Hooks/ Don't have experience with such things yet, but hope it helps.

Did you tried this? https://docs.armbian.com/User-Guide_Fine-Tuning/#system-language

Search on Google reveal there was an issue with transmission opened in may and closed in october. Another, newer issue is still open, but related to docker. It doesn't seem to be your case. So maybe try to update?

Sorry, don't know how to help further. Hope someone more knowledgeable will.

Did you rebooted after adding your user to the group xrdp? Restarting the service xrdp was not enough for me.

I see. Good luck!

Sorry, didn't notice that armbian-config offered to enable RDP and didn't know that it would install xorgxrdp too. Did you tried to log in with root? 'cause it works for me. So seems to be related to permissions. Added my user to the xrdp group with: usermod -aG xrdp [username] and now I can log in with my user (need to reboot to take effect). But following annoying message (that can be cancelled) appeared: After searching on Google, I followed these indications and now that's solved too. Hope it helps.

sudo apt install xorgxrdp

Why not make an image when you're done?

@iamdrq

I also noticed that the pins for the i2c busses are not set in the DT. At the end of the meson-sm1-bananapi-m5.dts following symbols are defined but never used: i2c0_sda_c_pins = "/soc/bus@ff600000/bus@34400/pinctrl@40/i2c0-sda-c"; i2c0_sck_c_pins = "/soc/bus@ff600000/bus@34400/pinctrl@40/i2c0-sck-c"; i2c0_sda_z0_pins = "/soc/bus@ff600000/bus@34400/pinctrl@40/i2c0-sda-z0"; i2c0_sck_z1_pins = "/soc/bus@ff600000/bus@34400/pinctrl@40/i2c0-sck-z1"; i2c0_sda_z7_pins = "/soc/bus@ff600000/bus@34400/pinctrl@40/i2c0-sda-z7"; i2c0_sck_z8_pins = "/soc/bus@ff600000/bus@34400/pinctrl@40/i2c0-sck-z8"; ... And this is the definition of a i2c bus: i2c@1c000 { compatible = "amlogic,meson-axg-i2c"; status = "disabled"; reg = <0x00 0x1c000 0x00 0x20>; interrupts = <0x00 0x27 0x01>; #address-cells = <0x01>; #size-cells = <0x00>; clocks = <0x02 0x18>; phandle = <0x121>; }; If I compare to these patches here or here and to the documentation, seems to me that the link between busses and pins (pinctrl-0, pinctrl-names / scl-gpios, sda-gpios) is missing. I really would appreciate a feedback, because I've really no idea if I'm looking in the right direction and if what I'm saying makes sense.

How? Can you upload your /boot/armbianEnv.txt here?

Could it be that kernel configuration must be adjusted? Here's the output of "cat /boot/config-6.1.4-meson64 | 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_XRS700X_I2C=m CONFIG_NET_DSA_SMSC_LAN9303_I2C=m CONFIG_MCTP_TRANSPORT_I2C=m CONFIG_MDIO_I2C=m # 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=m CONFIG_RMI4_I2C=m CONFIG_SERIAL_SC16IS7XX_I2C=y CONFIG_TCG_TIS_I2C=m CONFIG_TCG_TIS_I2C_CR50=m 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_ACPI_I2C_OPREGION=y CONFIG_I2C_BOARDINFO=y CONFIG_I2C_COMPAT=y CONFIG_I2C_CHARDEV=y CONFIG_I2C_MUX=m # 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 CONFIG_I2C_CCGX_UCSI=m CONFIG_I2C_ALI1535=m CONFIG_I2C_ALI1563=m CONFIG_I2C_ALI15X3=m CONFIG_I2C_AMD756=m CONFIG_I2C_AMD8111=m CONFIG_I2C_AMD_MP2=m CONFIG_I2C_I801=m CONFIG_I2C_ISCH=m CONFIG_I2C_PIIX4=m CONFIG_I2C_NFORCE2=m CONFIG_I2C_NVIDIA_GPU=m CONFIG_I2C_SIS5595=m CONFIG_I2C_SIS630=m CONFIG_I2C_SIS96X=m CONFIG_I2C_VIA=m CONFIG_I2C_VIAPRO=m CONFIG_I2C_SCMI=m # I2C system bus drivers (mostly embedded / system-on-chip) CONFIG_I2C_CADENCE=m CONFIG_I2C_CBUS_GPIO=m CONFIG_I2C_DESIGNWARE_CORE=m # CONFIG_I2C_DESIGNWARE_SLAVE is not set CONFIG_I2C_DESIGNWARE_PLATFORM=m CONFIG_I2C_DESIGNWARE_PCI=m # CONFIG_I2C_EMEV2 is not set CONFIG_I2C_GPIO=m # CONFIG_I2C_GPIO_FAULT_INJECTOR is not set CONFIG_I2C_HISI=m CONFIG_I2C_KEMPLD=m CONFIG_I2C_MESON=y # CONFIG_I2C_NOMADIK is not set CONFIG_I2C_OCORES=m CONFIG_I2C_PCA_PLATFORM=m CONFIG_I2C_RK3X=y CONFIG_I2C_SIMTEC=m CONFIG_I2C_THUNDERX=m CONFIG_I2C_XILINX=m # External I2C/SMBus adapter drivers CONFIG_I2C_DIOLAN_U2C=m CONFIG_I2C_DLN2=m CONFIG_I2C_CP2615=m CONFIG_I2C_PCI1XXXX=m CONFIG_I2C_ROBOTFUZZ_OSIF=m CONFIG_I2C_TAOS_EVM=m CONFIG_I2C_TINY_USB=m CONFIG_I2C_VIPERBOARD=m # Other I2C/SMBus bus drivers CONFIG_I2C_CROS_EC_TUNNEL=y CONFIG_I2C_VIRTIO=m # end of I2C Hardware Bus support CONFIG_I2C_STUB=m CONFIG_I2C_SLAVE=y CONFIG_I2C_SLAVE_EEPROM=m CONFIG_I2C_SLAVE_TESTUNIT=m # 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 CONFIG_PINCTRL_MCP23S08_I2C=m # I2C GPIO expanders # end of I2C GPIO expanders CONFIG_BATTERY_BQ27XXX_I2C=m CONFIG_SENSORS_LTC2947_I2C=m CONFIG_SENSORS_NCT6775_I2C=m CONFIG_SENSORS_OCC_P8_I2C=m CONFIG_MFD_AXP20X_I2C=m CONFIG_MFD_MADERA_I2C=m CONFIG_MFD_DA9052_I2C=y CONFIG_MFD_MC13XXX_I2C=m CONFIG_HTC_I2CPLD=y CONFIG_MFD_SIMPLE_MFD_I2C=m CONFIG_MFD_TPS65912_I2C=y CONFIG_MFD_ARIZONA_I2C=m CONFIG_MFD_WM831X_I2C=y CONFIG_MFD_WM8350_I2C=y CONFIG_MFD_ATC260X_I2C=m CONFIG_MFD_RSMU_I2C=m CONFIG_VIDEO_V4L2_I2C=y CONFIG_I2C_SI470X=m CONFIG_I2C_SI4713=m # IR I2C driver auto-selected by 'Autoselect ancillary drivers' CONFIG_VIDEO_IR_I2C=m CONFIG_VIDEO_I2C=m # 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_DRM_SSD130X_I2C=m CONFIG_SND_HDA_SCODEC_CS35L41_I2C=m CONFIG_SND_SOC_I2C_AND_SPI=m CONFIG_SND_SOC_ADAU1372_I2C=m CONFIG_SND_SOC_ADAU1761_I2C=m CONFIG_SND_SOC_ADAU7118_I2C=m CONFIG_SND_SOC_CS35L41_I2C=m CONFIG_SND_SOC_CS35L45_I2C=m CONFIG_SND_SOC_CS42L51_I2C=m CONFIG_SND_SOC_CS4271_I2C=m CONFIG_SND_SOC_CS42XX8_I2C=m CONFIG_SND_SOC_ES8328_I2C=m CONFIG_SND_SOC_MAX98373_I2C=m CONFIG_SND_SOC_PCM1789_I2C=m CONFIG_SND_SOC_PCM179X_I2C=m CONFIG_SND_SOC_PCM186X_I2C=m CONFIG_SND_SOC_PCM3060_I2C=m CONFIG_SND_SOC_PCM3168A_I2C=m CONFIG_SND_SOC_PCM512x_I2C=m CONFIG_SND_SOC_SIGMADSP_I2C=m CONFIG_SND_SOC_SRC4XXX_I2C=m CONFIG_SND_SOC_SSM2602_I2C=m CONFIG_SND_SOC_TLV320AIC23_I2C=m CONFIG_SND_SOC_TLV320AIC32X4_I2C=m CONFIG_SND_SOC_TLV320AIC3X_I2C=m CONFIG_SND_SOC_WM8731_I2C=m CONFIG_SND_SOC_WM8804_I2C=m # I2C HID support CONFIG_I2C_HID_ACPI=m CONFIG_I2C_HID_OF=m CONFIG_I2C_HID_OF_ELAN=m CONFIG_I2C_HID_OF_GOODIX=m # end of I2C HID support CONFIG_I2C_HID_CORE=m # I2C RTC drivers CONFIG_RTC_I2C_AND_SPI=y # SPI and I2C RTC drivers # CONFIG_MOST_I2C is not set # CONFIG_CROS_EC_I2C is not set CONFIG_ADXL313_I2C=m CONFIG_ADXL345_I2C=m CONFIG_ADXL355_I2C=m CONFIG_ADXL367_I2C=m CONFIG_ADXL372_I2C=m CONFIG_BMA400_I2C=m CONFIG_BMC150_ACCEL_I2C=m CONFIG_FXLS8962AF_I2C=m CONFIG_IIO_ST_ACCEL_I2C_3AXIS=m CONFIG_KXSD9_I2C=m CONFIG_MMA7455_I2C=m CONFIG_BME680_I2C=m CONFIG_SCD30_I2C=m CONFIG_SPS30_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_BOSCH_BNO055_I2C=m CONFIG_FXOS8700_I2C=m CONFIG_INV_ICM42600_I2C=m # CONFIG_INV_MPU6050_I2C is not set CONFIG_IIO_ST_LSM9DS0_I2C=m 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 CONFIG_CRYPTO_DEV_ATMEL_I2C=m Particularly following lines are concerning: CONFIG_I2C_MUX=m CONFIG_I2C_MUX_GPIO=m CONFIG_I2C_GPIO=m Would it explain the behavior in my precedent post? And don't know if there are other important missing configurations. Do I have to build the complete image to test? Or can I build the kernel locally? I would really, really appreciate some hints as I have no experience with Linux, Kernel building, etc. Mux are used for I2C in DT. From meson-sm1-bananapim5.dts: i2c0-sda-c { phandle = <0x63>; mux { groups = "i2c0_sda_c"; function = "i2c0"; bias-disable; drive-strength-microamp = <0xbb8>; }; }; i2c0-sck-c { phandle = <0x64>; mux { groups = "i2c0_sck_c"; function = "i2c0"; bias-disable; drive-strength-microamp = <0xbb8>; }; }; Here's the complete meson-sm1-bananapi-m5.dts Thank you for your help, really appreciate.

@SoSie can you please tell the native resolution of each monitors? thx

@SoSie can you please tell which exact image has this issue? thx

@Igor I tried with latest image, the behavior is still exactly the same as above. Was my proceeding correct? i2c slave still doesn't answer. On other board (BPi M2 Zero) it answers as expected. On BPi M5 it's connected to the pins 3 (CON1-P03/GPIOX_17/I2C_M2_SDA) and 5 (CON1-P05/GPIOX_18/I2C_M2_SCL). Although I analized the meson-sm1-bananapi-m5.dts, I don't understand if it supposed to be i2c0, i2c1, i2c2 or i2c3. But all 4 doesn't answer, so there's maybe an error in the dts. Edit: The electrician doublechecked the wirings, he says that it should be fine.

@iamdrq please look at this topic, seems very similar to this. Is the overlay correct? /dts-v1/; /plugin/; / { compatible = "rockchip,rk3399"; fragment@0 { target=<&backlight>; __overlay__ { status = "okay"; }; }; fragment@1 { target=<&edp>; __overlay__ { status = "okay"; }; }; fragment@2 { target=<&vopb>; __overlay__ { status = "okay"; }; }; fragment@3 { target=<&vopb_mmu>; __overlay__ { status = "okay"; }; }; }; I don't have hardware to test, but maybe @Erica will.

@SoSie, as @Igor has said, new images are available on https://www.armbian.com/bananapi-m5/ since 2023-01-09. They work flawlessly.

Image built with Armbian NEXT® boots on BPi M5! Most important things seem to work correctly (or at least on par with master). Well done! Just to give another perspective: I'm a .NET developer and Windows user. I first heard of Armbian on 2022-10-21 (and downloaded and flashed an official image), and built my first custom image from master 12 days ago. So NEXT cannot be so bad

Maybe TeamViewer is missing some desktop related package? Try to enable desktop in armbian-config, check if TeamViewer works, then disable desktop again (in armbian-config).

Maybe here's a solution: https://stackoverflow.com/questions/63590521/cant-open-pid-file-var-run-teamviewerd-pid-yet-after-start-no-such-file-or

Seems to be a task for a DNS. But sorry, don't know how to work around your problem with TeamViewer.

Thanks @Igor and the whole Armbian team! 💪

Right click on desktop -> Settings -> Display Settings. If it doesn't help to solve your issue or if you prefer typing instead of clicking: https://docs.armbian.com/User-Guide_Fine-Tuning/#screen-resolution-within-xorg