Onboard wifi currupt ?????

This topic contains 3 replies, has 2 voices, and was last updated by  Heiner Moderator 2 months ago.

Viewing 4 posts - 1 through 4 (of 4 total)
  • 14. Juli 2018 at 7:37 #36592

    Hi, SORRY FOT THE SPELLING MISTAKE „CORRUPT“ 🙂
    Recently I have been having lots of problems trying to connect to my M2P and then holding the connection using the Pi onboard wifi while using Accesspoint. However, I now have got one M2P system working and how I did it can be found in the Add-on section of this forum.

    Unfortunately, in resolving the problem I’m now left with what might be an expensive bill. In trying to reslove my problem I now have two raspberry pi’s which I think have onboard wifi issues.

    On both Pi’s the problem is identical, they are both sending out a wifi signal, but I cannot make them connect to anything, its as though the modulation part (the bit that puts the info in the wifi signal) of the wifi transmission is’nt working. I can’t connect to my router using wifi nor does my devices connect to the accesspoint.

    I have rebooted, re-setup my system many many times, used new scandisk SD cards and Tried wps and tried an external aerial. The only way I can connect is with an ethernet cable, and this works fine. So my questions are

    a) can installing, removing the accesspoint and wifi/lan many times, which I have on both, mess up the wifi
    b) Can someone please offer some glimmer of hope to help me get my two PI’s working in wifi mode again. And I do need them, I do have a use for them. Also, I’m worried that if I buy another, its not only the expense, I’m worried the same might happen again.

    The debug on my accesspoint is:

    #### DNSMASQ Installed ####
    Status: install ok installed

    #### HOSTAPD Installed ####
    Status: install ok installed

    #### WiFi Interface Installed ####
    2

    #### DNSMASQ Running ####

    #### HOSTAPD Running ####
    5 S 0 461 1 0 80 0 – 1543 – ? 00:00:00 hostapd

    And on my wifi/lan:

    eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    inet 192.168.1.93 netmask 255.255.255.0 broadcast 192.168.1.255
    ether b8:27:eb:28:d9:87 txqueuelen 1000 (Ethernet)
    RX packets 2569 bytes 215658 (210.6 KiB)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 2755 bytes 3115492 (2.9 MiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
    inet 127.0.0.1 netmask 255.0.0.0
    loop txqueuelen 1000 (Local Loopback)
    RX packets 643 bytes 55090 (53.7 KiB)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 643 bytes 55090 (53.7 KiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    inet 192.168.189.1 netmask 255.255.255.0 broadcast 192.168.189.255
    ether b8:27:eb:7d:8c:d2 txqueuelen 1000 (Ethernet)
    RX packets 46 bytes 5798 (5.6 KiB)
    RX errors 0 dropped 4 overruns 0 frame 0
    TX packets 376 bytes 33436 (32.6 KiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    ### WLAN ###

    THANKS

    • This topic was modified 2 months, 1 week ago by  alex.
    • This topic was modified 2 months, 1 week ago by  alex.
    • This topic was modified 2 months, 1 week ago by  alex.
    • This topic was modified 2 months, 1 week ago by  alex.
    18. Juli 2018 at 13:54 #36663

    If possible you can try changing the WiFi channel of your device, this has been an issue for some users in the past.

    You can also try out a WiFi dongle if you have one available to you, to rule out a hardware defect of your Pi.

    19. Juli 2018 at 19:13 #36683

    Hi Heiner
    Thanks for the reply.
    I should have said that I have tried several wifi dongles and still no luck. Still the same issues.

    But what I did manage to do without an external wifi dongle just by using the internal wifi of the pi, is get the Pi to connect to a travel router (https://www.amazon.co.uk/HooToo-Wireless-Performance-TripMate-Hotspot/dp/B00HZWOQZ6/ref=sr_1_1?ie=UTF8&qid=1532019850&sr=8-1&keywords=hootoo+tripmate).

    So I now have my router in the car, this is hooked into my Pi’s wifi LAN (NOT ACCESSPOINT)and all is working fine, indeed its all seems to boot up quicker than the accesspoint on it’s own.

    However, I have not actually cured the problem, just managed to find a way around it for now. But I’d like to try and get my Pi’s working in accesspoint mode so I would like to try your suggestion by changing the channel No on the pi. I would be very thankful if you might be able to point me in the right direction (web page ?) please to help me do this. Thanks again. Alex

    20. Juli 2018 at 10:16 #36686

    Hi alex,

    I meant changing your router’s WiFi channel.

    However, if you google „WiFi channel Raspberry Pi YOURMODEL“ you should find various discussion on the topic including instructions for alteration.

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.

Register here