All Activity

Maybe tomorrow, try to solve this.

I found that if I use umu-run(protonge), the launcher will crash, but if i use wine staging (with dxvk), the launcher start is no problem but the game got a error.

I found "https://www.naeu.playblackdesert.com/en-US/Forum/Qna/Detail?_questionNo=1122&_answerSortType=0" have same problem, but I have no idea about find the device ID.

The game have not start couse "technique not found shader : ObjectNormal.fx, ObjectLava"

I don't have a device for that. Which one would you recommend getting? I might try it out later when I get time (not soon so if anyone else is able to post logs?)

UART logs via serial console

@Werner Which logs would be usefull? I have a full image from the broken state. Kern.log is empty (0 bytes) syslog only has log from the last shutdown and ends there dmesg is from last startup before the system broke

logs?

Just a warning for everyone, the new kernel update (6.18.xx I think?) absolutely wrecks the system (atleast it does on Ubuntu Noble). It doesn't boot at all anymore I needed to recover an old kernel from an old backup I had and overwrite the current kernel from rescue mode/petitboot. Kernel 6.12.xx seems to work fine(ish) Just a heads up because I don't know enough to pinpoint the exact cause. p.s. for me the kernel means the files in /boot not sure if I used proper terminology

https://sd-card-images.johang.se/ This is a good source of SBC images, unfortunately no image for Odroid C5 yet. The image available on the web site of Hardkernel is Ubuntu 22.4.

Firstly, thank you for the ongoing support for the RV2. I'm encountering an issue with the top M.2 slot. While I can boot from it, as soon as the prompt appears, an ext4 error is thrown, the root filesystem is mounted read-only, and the system fails to complete the login process. Interestingly, when I move the same disk to the bottom M.2 slot, everything works perfectly. To further investigate, I wiped the NVMe drive, created an empty ext4 partition, and booted from an SD card. Here are the results: Bottom Slot (Works as expected): The disk can be mounted and used without issues. Passes multiple `fio` write and read tests. Top Slot (Fails to mount): Unable to mount the disk: root@orangepirv2:~# mount /dev/nvme0n1p1 /mnt/test mount: /mnt/test: can't read superblock on /dev/nvme0n1p1. dmesg(1) may have more information after failed mount system call. I've checked the dmesg logs, and the only noticeable difference is that when the disk is in the bottom slot (and working), there are more Bluetooth-related lines. Does this indicate that the lines for that slot are used by multiple systems, or am I on the wrong track? Here are the relevant dmesg logs for both scenarios: Booting from SD, NVMe disk in top M.2 slot: Booting from SD, NVMe disk in bottom M.2 slot: Any insights or suggestions would be greatly appreciated.

@xiboliyadongtu So, you were able to play the game with Dxvk (or Zink) now? How is the performance I wonder?

@4A studio You can run the spacemit-gpu-addon.sh on forky. This should install the trixie binaries. If there is something that does not work or wants an unavailable depend, you may try recompiling, the source should be with you: apt-get build-dep somepack and apt-get source -b somepack will get you going. If that works, you can tell me and I'll integrate. @Uhtred2 No 1080p youtube for you? Maybe not every codec works. I have tried with German TV, such as Anyhow, the IMG BXE 2-32 GPU is not very fast, only 500 fish with https://webglsamples.org/aquarium/aquarium.html Hopefully, the K3 successor uses something better. @maxsub You sure use our kernels? Can you post "uname -a" output? I tried the R2S image on my RV2 which shows a zero load with "uptime". Also, why do you need to manually boot USB from uboot? That "kydevtool" together with boot switch does not work either?

Has anyone here experienced the same problem on trying to install "Armbian Imager" under Windows 11? Upon running the respective exe-file and - no matter what target directory I choose - I get a failure meassage, somewhat like this: The directory could not be established: Microsoft Edge has no Read/Write access rights to its directory: C:\Users\admin\AppData\Local\com.armbian.imager\EBWebView Should the same issue have been posted here somewhere else, I do apologize. However, before creating the help request I did try to find any entries of similar content, but in vain. So if there's already any remedial comment on this available in the Armbian community, please provide the link. Thanks a lot in advance. Meanwhile I managed to run it, however only after starting up Win11 as admin and explicitly running the programme as such. On the contrary, if I start the OS directly into my simple user account and then try to run Armbian-Imager from there, both as regular user OR as admin, it will refuse to do its job by sending the above failure message.

Sry, it is too late so i go sleep. But i found the method to fix this. I use box64 and wine staging succeed run the luancher by edit the file. “To fix the white or black launcher: Go in Documents\BlackDeser\GameOptionLauncher.txt and change these value to 0 launcherGpu = 0 launcherOffScreen = 0 This should fix the launcher once for all” https://www.codeweavers.com/compatibility/crossover/forum/black-desert-online?srsltid=AfmBOoomxtE1rM4fxkwr05vZXqg7N30pyVeyxG9wztivOZNf4rmiFs9W;msg=319137 By the way, this game must boot by luancher.

With the help of AI, dts writing (kernel 5.10) has been achieved. It's basically error-free. Only applicable to shutuo v8 version Results: Wired network is normal Wireless network is normal USB interface is normal rk3288-shutuo-v8.dtb rk3288-shutuo-v8.dts

I see there's an overlay for the R4S called rk3399-dwc3-0-host, but it already seems to be in host mode by default. I can't figure out how to set it to peripheral mode so I can have some usb-gadget love. Anyone figured out a fix?

Good morning I have big problem I have tv box Transpeed-H616_ I update with orange pi But i can't back to old firmware

Hello! I had motherboard BA839_141 V2.0 21021 with this type hardware on the photos. Allwinner H313, 8x D9PSC, Toshiba THGBM5G7A2JBAIR And i want use it only with non graphical linux, can someone help me, because i don't see anywhere images for this one, and the other ones only give me black screen. Device won't start with microSD card.

Managed to edit the MMC by booting from USB, mounting the MMC. The R2S is now up and running, with the mainline armbian. However, the CPU still spins in the kernel and generates a lot of heat. Idle load average is 2.02.

Youtube did not work with the Trixie image for me before or after the script. The Noble image did a decent job at 720p., would not work at 1080. I have the RV2 with 8GB of memory. Very nice progress!

@sven-ola thanks for your job, much appreciated. However, are there any chances for the GPU driver to be ported to forky-based Armbian to get both GPU acceleration support and fresher software (except for older patched mesa, of course)? For example, there is lxqt-wayland-session but starting from 2.1.0 version of lxqt while Ubuntu-based Armbian and Bianbu provide 1.4.0 version only. I happened to test it with kwin_wayland as the compositor with one of your previous images and it kind of works but it can suddenly freeze the whole system. I also tested your last image with Gnome but I started it from tty (the command is "XDG_SESSION_TYPE=wayland gnome-shell") and I got a bit higher score of 440-ish in glmark2-es2-wayland.

The problem was in the dtb which comes with the Armbian image, added the fix, now it is working as expected. Attaching the fixed dtb file, just replace it with this one and enjoy! Rename the attached file to k3-am67a-beagley-ai.dtb and copy it to your /boot/dtb/ti/ path and reboot. k3-am67a-beagley-ai.dtb_armbian_fixed

I ran into some trouble. I managed to boot the USB and then used armbian-config to flash the image to internal eMMC. However the script copied the USB UUID instead of the MMC UUID so now the MMC won't boot. I need to edit the MMC and change the UUID.

Thanks for the script @sven-ola. I got the R2S booted from USB. I had to tweak a few minor things. Where did you get the Ubuntu boot.cmd? usb start setenv devtype usb setenv devnum 0:1 setenv prefix boot/ setenv fdtfile dtb-6.6.99-legacy-spacemit/spacemit/x1_orangepi-r2s.dtb #setenv fdtfile spacemit/k1-orangepi-rv2.dtb setenv bootargs "console=ttyS0,115200 root=/dev/sda1" ls ${devtype} ${devnum} ${prefix} load ${devtype} ${devnum} ${ramdisk_addr_r} ${prefix}uInitrd load ${devtype} ${devnum} ${kernel_addr_r} ${prefix}Image load ${devtype} ${devnum} ${fdt_addr_r} ${prefix}/${fdtfile} booti ${kernel_addr_r} ${ramdisk_addr_r} ${fdt_addr_r}