surenz

@surenz Seems like discord went down. So posting here instead
 
As the overlay you are using seems ok, could you try creating your own custom image using https://github.com/armbian/build. I think there is a kernel patch that might be causing the conflict. Try editing patch/kernel/archive/sunxi-6.1/series.conf file to add a - (hyphen) at the start of the line that contains patches.megous/phy-allwinner-sun4i-usb-Add-support-for-usb_role_switch.patch. Then compile using ./compile.sh BOARD=orangepione BRANCH=current. For detailed instruction on setting up build environment and creating an image, see https://docs.armbian.com/Developer-Guide_Build-Preparation/

Hello all, 
 
I've been having a *fun* old time getting this 3.5" LCD (http://www.lcdwiki.com/MHS-3.5inch_RPi_Display) I have laying around working with my "new" BananaPi M2 Zero (http://wiki.banana-pi.org/Banana_Pi_BPI-M2_ZERO).
I know fbtft_device has been dropped as of kernel 5.4 and have been researching into how others have done it. I now know it requires custom overlays, (dts files, etc) and using 
sudo armbian-add-overlay xxx.dts as well as having a conf defined under /usr/share/X11/xorg.conf.d/ (attached).
I'm *real, real* close (got the LCD flickering!), but I think I need some guidance with the dts file (attached).
 
I've seen others trying to get similar screens working post 5.4 using OrangePis etc and have shaped my progress off that, but thought I'd reach out for help.
 
$ dmesg | grep spi [ 3.548563] [drm] Initialized ili9486 1.0.0 20200118 for spi0.0 on minor 2 [ 5.436435] ili9486 spi0.0: [drm] fb0: ili9486drmfb frame buffer device [ 14.303783] ads7846 spi0.1: supply vcc not found, using dummy regulator [ 14.311471] ads7846 spi0.1: touchscreen, irq 67 [ 14.312205] input: ADS7846 Touchscreen as /devices/platform/soc/1c68000.spi/spi_master/spi0/spi0.1/input/input1 $ dmesg | grep touch [ 14.311471] ads7846 spi0.1: touchscreen, irq 67 $ dmesg | grep tft [ 2.578895] tft35a-ts@1 enforce active low on chipselect handle [ 14.112100] fbtft: module is from the staging directory, the quality is unknown, you have been warned.  
waveshare35a.dts 50-fbtft.conf

Hi, have the same problem with compiling the can4linux driver.
Why does someone suggest to remove the last line of the linker script module.lds ?
  sudo sh -c "sed '$ d' 
 
it should include something for sure, may be the .plt section.
#include does not work, so I added the content of  ./linux-headers-5.10.4-sunxi/arch/arm/include/asm/module.lds.h
 

now I can load the module, but is may be not correct

Hi,
 
I've been struggling also with all the info in this thread but finally succeeded to make decompile/edit/compile the dtb file (assume this file as BIOS for ARM  )
I'm putting all commands here as reference for me as well :
 
cd /boot/dtb sudo cp sun8i-h3-orangepi-one.dtb sun8i-h3-orangepi-one.dtb.old sudo dtc -I dtb -O dts -o sun8i-h3-orangepi-one.dts sun8i-h3-orangepi-one.dtb sudo sed -i -e 's/dr_mode = "otg";/dr_mode = "host";/g' sun8i-h3-orangepi-one.dts sudo dtc -I dts -O dtb -o sun8i-h3-orangepi-one.dtb sun8i-h3-orangepi-one.dts Explanation of different lines:
 
1. go to dtb directory
2. make backup of the compiled file in case something goes wrong
3. decompile the file to be able to alter it with text editor
4. change the string from "otg" to "host"
5. compile the altered file back to binary format dtb
 
 
The only bad thing with all this above is that if you upgrade your kernel the info will be lost so you have to do it again.
I don't get why this parameter is set by default to "otg"?

log2ram writes files from ramdisk to sdcard every hour (if they are updated) by cron task. Also at startup log2ram loads all content from /var/log.hdd to ramdisk.
 
1. For improving situation with full ramdisk you can organize log rotation rules in /etc/logrotate.d to optimize logs by size. Log rotation is time dependent - daily, weekly. But, using log2ram, the best choice is to make it size-dependent.
 
edit /etc/logrotate.d/rsyslog:
 
/var/log/syslog
{
    # rotate only once
    rotate 1
    # rotate only if syslog > 10 Mb
    size 10M
    missingok
    notifempty
    delaycompress
    compress
    postrotate
        invoke-rc.d rsyslog rotate > /dev/null
    endscript
}
 
/var/log/kern.log
{
    # do not rotate, just purge file
    rotate 0
    # if size more than 1 Mb
    size 1M
    missingok
    notifempty
    compress
    delaycompress
    sharedscripts
    postrotate
        invoke-rc.d rsyslog rotate > /dev/null
    endscript
}
 
2. If your system spams a lot of messages, you can make log rotation more aggressive:
 
move /etc/cron.daily/logrotate to /etc/cron.hourly/logrotate
 
3. If you don't need detailed archived logging. You can protect your sdcard from hourly writes by telling log2ram to not write syslog and kern.log to disk. As a bonus at boot your ramdisk will not be filling with previous session's logs.
 
a) activate rsync mode in /etc/default/log2ram (or in /etc/log2ram.conf):
USE_RSYNC=true
 
b) find your log2ram (delete duplicates, if there is) and edit
whereis log2ram
 
replace two lines
rsync -aXWv --delete --links $RAM_LOG/ $HDD_LOG/ 2>&1 | $LOG_OUTPUT
and
rsync -aXWv --delete --links $HDD_LOG/ $RAM_LOG/ 2>&1 | $LOG_OUTPUT
 
with
rsync -aXWv --delete --delete-excluded --exclude-from '/etc/log2ram-exclude' --links $RAM_LOG $HDD_LOG 2>&1 | $LOG_OUTPUT
and
rsync -aXWv --delete --delete-excluded --exclude-from '/etc/log2ram-exclude' --links $HDD_LOG $RAM_LOG 2>&1 | $LOG_OUTPUT

c) create new file /etc/log2ram-exclude and add lines:
/log2ram.log
/syslog*
/kern.log*
 

Hi,
 
I've been struggling also with all the info in this thread but finally succeeded to make decompile/edit/compile the dtb file (assume this file as BIOS for ARM  )
I'm putting all commands here as reference for me as well :
 
cd /boot/dtb sudo cp sun8i-h3-orangepi-one.dtb sun8i-h3-orangepi-one.dtb.old sudo dtc -I dtb -O dts -o sun8i-h3-orangepi-one.dts sun8i-h3-orangepi-one.dtb sudo sed -i -e 's/dr_mode = "otg";/dr_mode = "host";/g' sun8i-h3-orangepi-one.dts sudo dtc -I dts -O dtb -o sun8i-h3-orangepi-one.dtb sun8i-h3-orangepi-one.dts Explanation of different lines:
 
1. go to dtb directory
2. make backup of the compiled file in case something goes wrong
3. decompile the file to be able to alter it with text editor
4. change the string from "otg" to "host"
5. compile the altered file back to binary format dtb
 
 
The only bad thing with all this above is that if you upgrade your kernel the info will be lost so you have to do it again.
I don't get why this parameter is set by default to "otg"?

Hi,
 
I've been struggling also with all the info in this thread but finally succeeded to make decompile/edit/compile the dtb file (assume this file as BIOS for ARM  )
I'm putting all commands here as reference for me as well :
 
cd /boot/dtb sudo cp sun8i-h3-orangepi-one.dtb sun8i-h3-orangepi-one.dtb.old sudo dtc -I dtb -O dts -o sun8i-h3-orangepi-one.dts sun8i-h3-orangepi-one.dtb sudo sed -i -e 's/dr_mode = "otg";/dr_mode = "host";/g' sun8i-h3-orangepi-one.dts sudo dtc -I dts -O dtb -o sun8i-h3-orangepi-one.dtb sun8i-h3-orangepi-one.dts Explanation of different lines:
 
1. go to dtb directory
2. make backup of the compiled file in case something goes wrong
3. decompile the file to be able to alter it with text editor
4. change the string from "otg" to "host"
5. compile the altered file back to binary format dtb
 
 
The only bad thing with all this above is that if you upgrade your kernel the info will be lost so you have to do it again.
I don't get why this parameter is set by default to "otg"?

Hi,
 
I've been struggling also with all the info in this thread but finally succeeded to make decompile/edit/compile the dtb file (assume this file as BIOS for ARM  )
I'm putting all commands here as reference for me as well :
 
cd /boot/dtb sudo cp sun8i-h3-orangepi-one.dtb sun8i-h3-orangepi-one.dtb.old sudo dtc -I dtb -O dts -o sun8i-h3-orangepi-one.dts sun8i-h3-orangepi-one.dtb sudo sed -i -e 's/dr_mode = "otg";/dr_mode = "host";/g' sun8i-h3-orangepi-one.dts sudo dtc -I dts -O dtb -o sun8i-h3-orangepi-one.dtb sun8i-h3-orangepi-one.dts Explanation of different lines:
 
1. go to dtb directory
2. make backup of the compiled file in case something goes wrong
3. decompile the file to be able to alter it with text editor
4. change the string from "otg" to "host"
5. compile the altered file back to binary format dtb
 
 
The only bad thing with all this above is that if you upgrade your kernel the info will be lost so you have to do it again.
I don't get why this parameter is set by default to "otg"?