Problem with Wifi with Raspberry PI 3, HiFiBerry Amp+ and 7" Official Display

Max2Play Home 2016 (en) Forums Max2Play on Raspberry PI Problem with Wifi with Raspberry PI 3, HiFiBerry Amp+ and 7" Official Display

Tagged: 

This topic contains 3 replies, has 2 voices, and was last updated by  Christoph premium 4 months, 1 week ago.

Viewing 4 posts - 1 through 4 (of 4 total)
  • 23. July 2016 at 21:37 #21782

    Hi folks,

    I saw a few other posts that also describe this issue.
    Issue: After updating or install 7″ plugin, wifi will not connect to a wireless network.

    Here are the steps to reproduce the bug:
    * Download either the HiFiBerry image or the 7″ Display image
    * Install works (2.32) – Updating to the latest (2.33 or 2.34) or beta Max2Play causes WiFi to stop working (NO CARRIER)
    * Install (from HiFiBerry image) using either image, using WPS works on reboot. – Install the 7″ display plugin after reboot causes WiFi functionality to stop working

    The problem appears to be some dependancies that occur from apt-get update, probably tied to the 7″ driver or config files. Running the appropriate wpa_supplicant commands, editing /etc/network/interfaces do not help.

    I would be happy to get logs and send them, this is rather frustrating

    26. July 2016 at 13:11 #21856

    Hello Derek,

    Did you expand your filesystem?

    Could you give me the debug info of the WLAN?

    Best Regards

    26. July 2016 at 23:46 #21871

    The first few times I tired, I did expand the filesystem. The current install, the file system is the default size.

    
    eth0      Link encap:Ethernet  HWaddr b8:27:eb:38:ef:cd  
              inet addr:192.168.1.66  Bcast:192.168.1.255  Mask:255.255.255.0
              inet6 addr: fe80::c7ed:4b71:a2d5:ce80/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:17970 errors:0 dropped:0 overruns:0 frame:0
              TX packets:8599 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000 
              RX bytes:24513125 (23.3 MiB)  TX bytes:1077963 (1.0 MiB)
    
    lo        Link encap:Local Loopback  
              inet addr:127.0.0.1  Mask:255.0.0.0
              inet6 addr: ::1/128 Scope:Host
              UP LOOPBACK RUNNING  MTU:65536  Metric:1
              RX packets:105 errors:0 dropped:0 overruns:0 frame:0
              TX packets:105 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1 
              RX bytes:8996 (8.7 KiB)  TX bytes:8996 (8.7 KiB)
    
    wlan0     Link encap:Ethernet  HWaddr b8:27:eb:6d:ba:98  
              inet6 addr: fe80::5678:85a5:2f7d:6731/64 Scope:Link
              UP BROADCAST MULTICAST  MTU:1500  Metric:1
              RX packets:236 errors:0 dropped:0 overruns:0 frame:0
              TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000 
              RX bytes:37201 (36.3 KiB)  TX bytes:0 (0.0 B)
    

    I’m connected via eth0 right now, so it won’t say NO CARRIER.

    Are there some commands you would like me to run?

    2. August 2016 at 13:23 #21959

    Hello Derek,

    Sorry for the late reply. Your problem could be the power supply. If you use same time a Raspberry Pi, 7″ Touch Display and a HiFiBerry, you need an additional power source for the display.

    You should see a symbol at the right upper corner, if not, please first test it without a hifiberry sound card.

    I have tested your setup and it works fine.

    • This reply was modified 4 months, 1 week ago by  Christoph.
Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.

Register here