phelum

I've just be trying again and have managed to get X running on my Nano. But not very well I fear. My first problem is that the Nano can't read the screen EDID. I get lots of "transfer timed out" errors for i2c-1 in the log. I believe this is the ddc connection to the HDMI port. Has anybody here seen this issue and found a solution ? The killer I hit before was that Xorg would hang when first checking the ports (e.g. /sys/class/drm/card0-HDMI-A-1). What I have found is that removing /dev/dri/* before starting X avoids this hang and I do get my desktop and all works. But it seems awfully risky to delete files such as /dev/dri/* and I'm hoping there's a better way. The hang could be an Xorg bug because the same hang happens on a Raspberry Pi 5 when running a 64-bit system but not when running a 32-bit system. As the Nano can't read the EDID it will default to 1024x768 mode. If I force an EDID using drm.edid_firmware=xxx in the kernel command line I can get 1920x1080 on a small HD screen but not on other 1920x1080 screens I've tried. What could confuse the issue here is that I'm running a custom 6.6.87 kernel and use sysvinit rather than systemd. So perhaps my problems are partially self-inflicted. But I have managed to get my 4GB Nano running X with one monitor. The video driver is only the fbdev driver so how well it works with videos etc. remains to be seen. Cheers, Steven

Thanks for the tip. I've posted there and hopefully will get a reply. I'm now testing on a Cubietruck with two adaptors (AP6210 and dongle) and everything is still pointing to a driver issue with the mainline kernel. Cheers, Steven

I've found the patches written by Chen-Yu Tsai and Maxime Rippard for Bluetooth using the AP6210 on a Cubietruck and as far as I can tell they're still fully included in the mainline 6.6 kernel. I'm wondering if either of these people can help me. Does anybody know any groups or mailing lists where I can contact Maxime or Chen-Yu ? Thanks, Steven

Hi, I'm trying to get Bluetooth working on a Cubietruck running 6.6 kernels including the latest Armbian release. What I'm finding is that a Cubietruck can discover other Cubietrucks but nothing else. Other devices (e.g. Raspberry Pi, Nvidia, Rockpi, and various phones) can discover each other but not the Cubietrucks. I have three Cubietrucks here and testing with the old 4.99 Bluetooth software or the current 5.55 release shows no difference. But if I run a Cubietruck with the ancient 3.4 kernel it can detect other devices but not the Cubietrucks running the 6.6 kernels. I'm using the same Wi-Fi firmware and BT .hcd file in all cases. So it's like the Cubietrucks with 6.6 kernels run Bluetooth in their own separate little world. Has anybody managed to get AP6210 Bluetooth working properly with a mainline kernel ? If so do you have any clues about how I can rectify this problem ? Thanks, Steven