The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header.
To mitigate this problem, the original message has been wrapped automatically by the mailing list software.
--- Begin Message ---Am 5. April 2024 11:11:09 MESZ schrieb w.hadife@crs-network.solutions: >Dear, > >We are building our project on orange PI R1 H3 and we want to use openwrt os >last version. >It seems that we have a problem with the WLAN driver RTL8189ES , > > >Is there a way to deploy a driver for this card using openwrt 23.05 last >version? >Can you help? >Do you have any method? >Can we use staging drivers, if yes how? > >Regards > > >- >Wissam Hadife | PDG, Fondateur >Mobile France| +33 6 29 92 71 59 >Mobile | +961 3 975 994 >Email | w.hadife@crs-network.solutions >https://crs-network.solutions > > > >_______________________________________________ >openwrt-devel mailing list >openwrt-devel@lists.openwrt.org >https://lists.openwrt.org/mailman/listinfo/openwrt-devel Hello Wissam, interesting how your threads pop up when searching on this topic: <https://forum.openwrt.org/t/openwrt-build-support-for-orange-pi-r1-h3/190172> <https://forum.armbian.com/topic/35604-openwrt-build-support-for-orange-pi-r1-h3/> I'm not sure if it's just the WiFi driver that is your problem. Have you managed to get OpenWrt to run on this unsupported device at all, so far? :) My suggestion: Search <https://firmware-selector.openwrt.org/> for hw support or the git repository (in the future). Not the possibly outdated ToH. Unless you are willing to pay money for someone to add device support: I suggest you get a different device for your project. Return the device you bought. The manufacturer appears to have switched the CPU from H2+ to H3 which means it's a new revision and needs new support (likely). They might've adjusted more than the cpu. You could email Tianling Shen and ask them kindly to add support to Linux/OpenWrt for the new revision. But they would need a sample of the new revision to work with so you might have to send them one or pay them to buy one if they are willing to do it. <https://github.com/openwrt/openwrt/pull/12662/commits/043f8a4f5ecf00e8a62b5a5d48baba48e620ea6a> As you can see this involves work. Not just settings some configs and starting a build process. Might be helpful in general since you asked: How to setup a system for building OpenWrt: <https://openwrt.org/docs/guide-developer/toolchain/install-buildsystem> How to build OpenWrt: <https://openwrt.org/docs/guide-developer/toolchain/use-buildsystem> SSH is preconfigured on OpenWrt If ethernet/network isn't broken you can SSH into your device ssh r...@openwrt.lan or ssh root@192.168.1.1 password is empty If you can't reach/ping the device on the regular build for H2+ that means network isn't working. which means someone needs to put in more work to get everything to run, which requires serial access. Again: you are better off getting an already supported device to run your project on. Everything else is a hassle. Regards Felix Baumann
--- End Message ---
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
