Gunjan Gupta
-
Posts
437 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Everything posted by Gunjan Gupta
-
it shows your otg port is in auto mode, did you had your otg cable connected when taking the logs? -
Main debugging information that would be needed in this case will be in kernel logs i.e. dmesg output.
-
Yeah I see what you mean. But then orangepi zero is a 32-bit device, so the developer might have thought that it would be obvious that a dtsi in arm64 directory will not be applicable to the same.
-
Its setup using a systemd service as I remember armbian-zram-config.service. Disabling that service should be enough.
-
I would say keep it in the format as done in mainline or next kernel that way we can easily handle kernel updates.
-
There are still glitches? Can you tell me the steps to reproduce the same? I will try it on my zero3
-
OrangePi 3 LTS with Armbian 23.11.1: intermittent bluetooth
Gunjan Gupta replied to tizianomattei's topic in Allwinner sunxi
Hmm... Interesting. ok, will take a look on Tuesday. Busy until then with other stuff. But thanks for reporting and doing all of the testing. -
It should work after a reboot. But as you manually removed using modprobe command, the module will return on reboot.
-
Feel free to do that. I only worked on zero2w for a client. I don't have the device and hence can't be the maintainer for that one. Also I have no interest to add that to armbian either. But if you will raise a PR, I will review the same. BTW, there seems to be a sudden influx of H618 based devices, I noticed Bananapi M4 berry and there is also Sipeed Longan Pi3H. More devices must be coming soon as well.
-
Raised another PR for HDMI support. Its merged now. Pending things as I understand are now audio, dma, iommu and cpufreq for H618
-
OrangePi 3 LTS with Armbian 23.11.1: intermittent bluetooth
Gunjan Gupta replied to tizianomattei's topic in Allwinner sunxi
ok...so it seems you got lucky 5 times in a row when you did the testing before. Np, I will test later on my Orange Pi 3 LTS. Try editing /lib/systemd/system/aw859a-wifi.service and add "After=aw859a-bluetooth.service" as a newline after Description line. Reboot couple of times and see if bluetooth is working. You can check status of aw859a-bluetooth.service. If its reported running, your bluetooth will work. If you face issues with After, try changing it to Before. -
Thanks, that does theoretically tells me that the issue is being caused by some changes I missed when integrating drm-sun4i-Mark-one-of-the-UI-planes-as-a-cursor-one.patch. I will revisit the hdmi code again while keeping that patch in mind. But we should be close to getting a working hdmi now.
-
Thats caused by the wifi driver. Its a known issue on every board that uses uwe5622 wifi module
-
remove g_serial from /etc/modules. Then if you have a otg adapter then it should work fine
-
OrangePi 3 LTS with Armbian 23.11.1: intermittent bluetooth
Gunjan Gupta replied to tizianomattei's topic in Allwinner sunxi
Thanks for testing, raised https://github.com/armbian/build/pull/6113 to replace the binary for everyone. -
OrangePi 3 LTS with Armbian 23.11.1: intermittent bluetooth
Gunjan Gupta replied to tizianomattei's topic in Allwinner sunxi
Yeah, seems like hciattach binary crashes some times as reported by @Stephen Graf as well. Try replacing /usr/bin/hciattach_opi with https://github.com/orangepi-xunlong/orangepi-build/raw/next/external/packages/blobs/bt/hciattach/hciattach_opi_arm64. Make sure to keep the filename the same i.e hciattach_opi. Let me know if it works after reboot -
I do expect that you will get the same half screen issue, but still can you once check it on zero2?
-
@pixdrift Did you tested hdmi on cli image or on desktop image?
-
@Stephen Graf From the logs, drivers seems to have been loaded correctly. Still could you please reproduce the issue and with the non-working bluetooth state share me the output of: ls /dev/tty* journalctl -u aw859a-bluetooth.service
-
You can follow this guide to build an image - https://docs.armbian.com/Developer-Guide_Build-Preparation/
-
Yes, those messages appear on boot, but are not critical. -517 is just defered probing. Things settles down later. As those messages are harmless, I am not focusing on those right now. But will come back to them later after all major issues are resolved.
-
Need testers for - https://github.com/armbian/build/pull/6106 HDMI support for H616/H618 and WIP support for Orange Pi Zero3 known issues - cpufreq seems to be broken. Will be working to fix the same - Plymouth and tty on HDMI works fine, though xfce on bookworm seems to be having some weird issues where its only rendering the top half of the display. Will check on sid to see how newer version of mesa behaves.
-
Looks like you misread the board name posted by mattdebauge. We currently have no support Orange Pi Zero 2w right now.
-
Just to rule out one possibility, Have you tried using a different power supply? What power supply you are using right now? Orange Pi recommends 5V 3A supply
-
Disable aw859a-wifi and aw859a-bluetooth services. For a more paranoid way, you can also add a dtoverlay to disable mmc1 something like /dts-v1/; /plugin/; &mmc1 { status = "disabled"; }; Save above to a file with .dts as extension and run "sudo armbian-add-overlay <filename>"