atone

Multiple causes are possible, don't know how to help further. Hope someone more knowledgeable will help.

WordPad is even worse. Use only Notepad++ or follow @SteeMan's advise (don't allow the sd card to touch a windows machine).

Not Notepad, but Notepad++! It's not the same.

+1 How is this an argument for TeamViewer? TeamViewer needs to communicate over a port too. Sorry, didn't read carefully. ssh can be configured to use port 80 too.

Notepad++ is really good at preserving the correct encoding + LF under Windows

Yes.

Please post it here. Edit: I mean the dts file, hope it was clear.

[353899.757436] sprdwl:sprdwl_tx_ba_mgmt, 1636, tx_addba failed, reason=1, lut_index=6, tid=0, map=0 Doesn't look good. Don't know if it is the cause or a consequence of high zram usage. Can you post a screenshot of htop?

On the same board? Which image are you trying? Where did you get it from?

To query i2c-7: i2cdetect -y 7

Here other, not necessarily better ideas: Frozen Legacy R.I.P. (Rest In Place) Still Alive Afterlife Heaven I'll stop here 😂

Hi! This is probably what you're looking for: https://docs.armbian.com/User-Guide_Getting-Started/#how-to-prepare-a-sd-card There's also this excellent video tutorial and plenty other infos.

As far as I understand the doc, power consumption can be adjusted with CPU governors. For the Orange Pi PC the default governor is OnDemand. Other CPU governors achieve different purposes.

As others would say, providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

Hi! Did you tries this https://docs.armbian.com/User-Guide_Fine-Tuning/#screen-resolution-within-xorg?

It seems that the baud rate parameter is being actively refused, as it's probably not allowed in a predefined list. That could be the standard serial node... ... or the driver.

According to this posts here, here and here the baud rate depends on the clockrate and setting an unsual baud rate such as 1000 would imply overcloking (or underclocking) the CPU. But that's a lot of assumptions from me, so I hope that someone with more knowledge and experience will answer. Edit: simplification.

This measure serves to fight spam and will be relieved as soon are your membership request has been approved. ff370000.serial: ttyS4 at MMIO 0xff370000 (irq = 46, base_baud = 1500000) is a 16550A Did you tried with a baud rate of 1500000?

https://docs.armbian.com/Quick_facts/#armbian-is-the-opposite-of-raspbian

Hi everyone, Here an idea: It may be useful to know which board and wich compilation environment has already been tested with armbian-next, i.e.: Board User space Kernel Interface Environment Compilation Boot Hardware peripherals Hardware features Apps uefi-x86 Bullseye Current Desktop XFCE ✅ ✅ uefi-x86 Bullseye Edge Desktop XFCE ✅ ✅ bananapim5 Bullseye Edge Desktop XFCE ✅ ❎ And for the compilation environment: Host Container Guest Compilation Windows 10 VirtualBox Ubuntu Jammy 22.04.1 Desktop amd64 ✅ Ubuntu Jammy 22.04.1 Desktop amd64 -- -- ✅ The goal would be not to test every possible combination, but just to not waste time (test something that has already been tested) and as a bonus have an overview. "We" neither should fix images in next that aren't working in master too, but next should be at least on par with master. The forum is probably not the right place to host such a document. Maybe Jira? What do you think about this idea? Feel free to reject it or propose modifications.

My bad, the tree is upside down. Don't know how it works, but "network.target" is not listed. Edit: neither is system.slice

Plenty of other useful advices here.

Which kind of SD card do you have? Startup operations are often tied to read/write operations to the file system, so you may have a chance there.

Reducing the log size would maybe help?