DmitryS

I'm not here to blame somebody or something if you thought that I am. I want to find somebody who maybe knows this problem and how to solve it. I have a problem with official orange pi, official armbian image and some display which doesn't want to work with them but works with another mini PC with another OS. But there is the display which works with both so it is not an issue with each piece separately. It is something between them. And if somebody has an answer - I would be glad to have it too.

Hi! I'm using armbian Jammy on my orange pi 5 with installed xfce desktop. I'm trying to connect it to a small HDMI screen and it doesn't work. It shows "no signal". I tried to use another screen (different model, resolution, manufacturer etc.) and it works. Then I tried to use non working screen with jetson nano and it works without any actions. So, the problem is with orange pi with armbian and this specific screen. Here is the result of "xrandr -display :0" launched trough ssh: Screen 0: minimum 320 x 200, current 1024 x 600, maximum 16384 x 16384 HDMI-1 connected primary 1024x600+0+0 (normal left inverted right x axis y axis) 476mm x 268mm 1024x600 59.82*+ 1920x1080 60.00 50.00 59.94 1920x1080i 60.00 50.00 59.94 1280x1024 75.02 1280x720 60.00 50.00 59.94 1024x768 75.03 70.07 60.00 832x624 74.55 800x600 72.19 75.00 60.32 56.25 720x576 50.00 720x480 60.00 59.94 640x480 75.00 72.81 60.00 59.94 720x400 70.08 DP-1 disconnected (normal left inverted right x axis y axis) So, orange sees the screen but doesn't show anything on it. There was an instruction with the screen for raspbian. It says that I need to change config.txt with this content: max_usb_current=1 hdmi_force_hotplug=1 config_hdmi_boost=10 hdmi_group=2 hdmi_mode=87 hdmi_cvt 1024 600 60 6 0 0 0 But what are analogue steps for the orange?

@jock that's sad. Thanks for the answer.

Hi. It's me again. I want to know: is there any way to install opencl on rk3328 with your image? I tried to install libs from here and after that I see these files in my system: /opt/libmali-gbm/libOpenCL.so /usr/lib/arm-linux-gnueabihf/libOpenCL.so /usr/lib/aarch64-linux-gnu/libOpenCL.so But clpeak fails to build with error: No rule to make target «/usr/lib/aarch64-linux-gnu/libOpenCL.so». UPD: I reinstalled packages from the link and did a little clearing in the system and now clpeak launches and says: clGetPlatformIDs (-1001) no platforms found

Thanks for the explanation. I finally unbricked it. What I figured out is that I should put a sd-card. I put it into the board, shortened contacts which MattWestB helped me to find and it booted into multitool where I choose to burn another image and now it boots into it from emmc! Thank you guys!

Hi! Sorry for the long reply and thanks! I shortened TP2300 and TP2301 before plugging cable and, as said in the instruction, blue led started blinking but I don't see any new device in lsusb on the host computer.

Hi. I bricked my plate and want to unbrick it. But can't find clock pin. Here is the emmc chip and it's back. Can somebody tell what should I short here to erase emmc? Thanks in advance. P.S. What should I do after going into maskrom mode? Should I attach box to a computer with usb? Should I plug usb after enabling maskrom or before?

Hi! Thanks for images at first. I'm trying to launch docker on your image but get problems with cgroup. dockerd --debug output: cgroupfs-mount: I see this row in dmesg which looks suspectable for me: Unknown kernel command line parameters "ubootpart=534ffe7a-01 cgroup_enable=memory cgroup_memory=1", will be passed to user space. Full dmesg: I tried 22.05 version of the image first and then uninstalled docker and updated to 22.08 through installing packages from "upgrade" folder. After installation I still have this issue. Can somebody help, please?

@SteeMan thanks. I can't write more than 1 post in a day, so I'm writing it now. What about this problem? I got it on X88. Any solutions except installing old version?

Hi. I'm trying to use Armbian 20.10 from Balbes and I'm thankfull to you for supporting it. But I have a problem. I have: 1. X88 pro X3 with u-boot-s905x2-s922 as u-boot.ext and meson-g12a-x96-max-rmii.dtb choosen. 2. A95X F3 Air with u-boot-s905x2-s922 as u-boot.ext and meson-sm1-sei610.dtb Both of them work. I can connect to them with ssh. But I found that sometimes after reboot command both of them do not start again until I plug/unplug them. I made this little script: date >> ~/Files/reboots.txt /sbin/reboot I put it into a crontab. It executes it each 2 minutes. Both of devices rebooted well for 10-15 times when I tried it first. But after that it takes 3-4 reboots to hang. During that hanging device is unaccessible through ssh and HDMI output shows nothing. I tried to look into journalctl logs but found that a journal for hanged boot doesn't exist. There are journals for previous boot and for the next after unplugging and nothing in between. So, I thought that the problem is with u-boot. I connected to X88 with UART adapter. This is how the end of normal session looks: *kernel started* ... arm-64 login: *here it asks for a login and password but I just wait* reboot: Restarting system *some messages about restarting here* ... *beggining of a new start here* And this is how the ending of weird session looks: *kernel started* ... arm-64 login: *here it asks for a login and password but I just wait* Yes, it doesn't show a log for a new start neither a log for ending of previous session. It looks for me like system is hanging not on start but on shutting down. Nobody had such an issue? How it can be fixed? Thanks in advance.