patrick-81

Members
  • Content Count

    30
  • Joined

  • Last visited

About patrick-81

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hello all, After having done the mod suggested by Martin I have now a wifi used as hotspot which is stable. But the signal is really, really weak. So when I am more than 5m from it my PC doesn't catch the signal which is something like 25% of the full scale. Is there something I can do ?
  2. @martinayotte Your mods works fine but only to connect to a network. But the wifi is really unstable when used as hotspot. Hope it will improve a bit in the future with new firmwares. ping 172.24.1.1 PING 172.24.1.1 (172.24.1.1) 56(84) bytes of data. 64 bytes from 172.24.1.1: icmp_seq=1 ttl=64 time=1970 ms 64 bytes from 172.24.1.1: icmp_seq=2 ttl=64 time=948 ms 64 bytes from 172.24.1.1: icmp_seq=3 ttl=64 time=91.1 ms 64 bytes from 172.24.1.1: icmp_seq=4 ttl=64 time=118 ms 64 bytes from 172.24.1.1: icmp_seq=5 ttl=64 time=4.38 ms 64 bytes from 172.24.1.1: icmp_seq=6 ttl=64 time=5.03 ms 64 bytes from 172.24.1.1: icmp_seq=7 ttl=64 time=5.49 ms 64 bytes from 172.24.1.1: icmp_seq=8 ttl=64 time=5.84 ms 64 bytes from 172.24.1.1: icmp_seq=9 ttl=64 time=5.81 ms 64 bytes from 172.24.1.1: icmp_seq=10 ttl=64 time=5.75 ms 64 bytes from 172.24.1.1: icmp_seq=11 ttl=64 time=2.35 ms From 172.24.1.140 icmp_seq=12 Destination Host Unreachable From 172.24.1.140 icmp_seq=13 Destination Host Unreachable From 172.24.1.140 icmp_seq=14 Destination Host Unreachable From 172.24.1.140 icmp_seq=15 Destination Host Unreachable From 172.24.1.140 icmp_seq=16 Destination Host Unreachable From 172.24.1.140 icmp_seq=17 Destination Host Unreachable From 172.24.1.140 icmp_seq=18 Destination Host Unreachable From 172.24.1.140 icmp_seq=19 Destination Host Unreachable From 172.24.1.140 icmp_seq=20 Destination Host Unreachable From 172.24.1.140 icmp_seq=21 Destination Host Unreachable From 172.24.1.140 icmp_seq=22 Destination Host Unreachable From 172.24.1.140 icmp_seq=23 Destination Host Unreachable
  3. Thank you Martin for the help.
  4. Obviously the problem comes from the Armbian image. I tested the Radxa Ubuntu server and with it the wifi is functional. Maybe I have to do the same as you have done, compile a kernel on my side. What type of platform do you specify Rockpro64 ?
  5. So, what's the blip ? What kernel do you use Martin ?
  6. [ 1.972199] mmc0: new ultra high speed SDR104 SDIO card at address 0001 [ 7.229963] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/9 [ 8.458767] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50 [ 9.471131] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (1000000): clkctl 0x50
  7. Hello all, I have just got a all new Rockpi 4B. I have installed the armbian image and xfce desktop. I just have a problem, the wireless device is not available. hwinfo --short gives the following result. I guess that broadcom is the wifi device but looks not to be recognized by the armbian image. Am I right ?
  8. Hello, After having done the mods I have compiled all successfully. And tadaam, now all works fine. I finally have user access to the GPIO. A very great thank to all of you guys. Hope those patches will be part of the official release of ARMbian. Best regards Patrick
  9. Sorry Tony, but as I haven't got answers about my question that is why I asked it again. If I have been able to do it by myself I would have. But unfortunately I don't have the knowledge to do it. I thank you for the help you provide to all the linux users community of this board.
  10. Back with my problem of gpiomem public access. Does anybody can help ?
  11. Hello Is there a support to access to GPIO for anybody (/dev/gpiomem) like on RPI3 ? Someone suggested me to use it. https://github.com/joerg65/gpiomem_tinkerboard But I am too much awkward to create from scratch a kernel that include it. Thanks
  12. Hello all, I have initiated this project months ago : https://github.com/Patrick-81/NAFABox I had on previous version of Armbian (5.32) solved (partially) the wifi instability. Today with new version whatever I do, the wifi remain instable. Furthermore I tried to drive a focuser directly from the GPIO extension port. But I can't use it because of a leak of privileges. To make it work I need the /dev/gpiomem public access. I saw that it might be implemented in the last version of TinkerOS (2.0x). Will it be implemented in Armbian next versions ? Because of this two problems my project remains not completed. DO you think that both pf those issues can be fixed a=in a near future ?
  13. I still have a problem configuring the wifi hotspot on the armbian distribution for tinkerboard. The hotspot is clearly unstable. So none of my computers can't connect to it and my phones and tablets have a unstable connection. I thought having found a turnover using a call to iw with a frequency of 1s. This was reactivating the wifi for some times (that should simulate a continuous connection) but it looks that it doesn't work anymore. So I am stuck with that, I am unable to configure a stable hotspot. Is there something to do with the rtl8723 driver, or have I no hope to make it works ?
  14. The new API works fine now. There was issues with the previous. But my problem now is to execute programs without being root. The only solution I find is to suid all the programs that I use (found that gpio has the suid bit set). This is not a very satisfying solution. but I don't know if there is other solution. And maybe as the structure of the calling are a bit complex I don't know what part I have to suid. The bold, the red, the green, the blue or all of them ? Kstars (astro program) --> indi server (astro server) --> Focuser driver --> libwiringPi--> [GPIO --> stepper controller --> Stepper motor] I have tested: sudo chown root:gpio /usr/local/lib/libwiringPi.so.2.31 sudo chmod u+s /usr/local/lib/libwiringPi.so.2.31 compile and execute blink.c as normal user. and got the result can't open /dev/mem and /dev/gpiomem wiringpiSetup: Unable yo ope /dev/mem... I don't know what I can do else.