ZipperSpark
ZipperSpark
> You can also add test files here. There is a button below the text field to do so: > >  I fired up several cards and did these...
I am also happy to ship you a R5C to play around with. In the meantime, would you say that it's safe to update to 9.13.2 for devices in the...
> Do the boards with the missing LAN port interface have this consequently every reboot, and those without the issue never have it? Yes, it's either the board has it...
Seems the issue is there with both kernels, so maybe removing it doesn't solve anything. How do I update the kernel manually? "sorry if this is noob question, just want...
> Or do you use a different time sync daemon? I know what happened, this was an image that I made on May 10 and rebooted the system with ethernet...
In case I got the dtc conversion correct, this is the result (still no love) ``` dmesg | grep busn_res [ 2.201838] pci_bus 0000:11: busn_res: [bus 11-1f] end is updated...
[device-known-NOT-TO-WORK-after-applying-delay-patch.txt](https://github.com/user-attachments/files/20510266/device-known-NOT-TO-WORK-after-applying-delay-patch.txt) ok strange, after first apply, reboot, device actually connected and worked with eth0 ```lspci 0000:00:00.0 PCI bridge: Rockchip Electronics Co., Ltd RK3568 Remote Signal Processor (rev 01) 0000:01:00.0 Network...
Still same issue. log attached. [device-known-NOT-TO-WORK-after-applying-mac-patch.txt](https://github.com/user-attachments/files/20513738/device-known-NOT-TO-WORK-after-applying-mac-patch.txt) I did notice this in the dmesg log, not sure what it means ``` [ 5.461852] rockchip-dw-pcie 3c0400000.pcie: Phy link never came up [...
I used the commands as below, I think it's "image" not "images" ``` cd /tmp wget https://dietpi.com/downloads/binaries/testing/linux-{dtb,image}-current-rockchip64.deb dpkg -i linux-{dtb,image}-current-rockchip64.deb G_CONFIG_INJECT 'user_overlays=' 'user_overlays=' /boot/dietpiEnv.txt # in case ;) reboot ```...
> Had another look into this, assured that changes were applied to the correct device nodes. Still do not see the error. [@InnovoDeveloper](https://github.com/InnovoDeveloper) on a functional system, can you apply...