PINE64
WiFi module causes boot loop - Printable Version

+- PINE64 (https://forum.pine64.org)
+-- Forum: General (https://forum.pine64.org/forumdisplay.php?fid=1)
+--- Forum: Getting Started (https://forum.pine64.org/forumdisplay.php?fid=21)
+--- Thread: WiFi module causes boot loop (/showthread.php?tid=641)

Pages: 1 2


RE: WiFi module causes boot loop - bpcoyo - 04-22-2016

(04-17-2016, 08:45 AM)tllim Wrote:
(04-15-2016, 04:24 PM)BnEc Wrote: Sadly I have had no luck, I'm unable to boot into Arch on the Pine when I have the WiFi module plugged in, looks like it is DOA.  I have tried several OSs and power cables, just tried it with the Pi 3 offical power supply. Pine will boot though will just loop while WiFi is in.

Does anyone know the process of getting a new one? Do Pine have an RMA process?

Please PM me and I will ship out a new Wifi/BT module to you.

I have this exact same problem and I've spent about 5 hours today trying to get it figured out.  But no luck and I have to resort to message board posting...

Pine64 2Gb.  Can't boot into Arch or Remix (20160227 or 20160415) with wifi module plugged in.  Multiple power cables don't do it, neither does offic. Pi3 power supply.  

Ethernet boots just fine, but wifi = endless bootloop.


RE: WiFi module causes boot loop - bpcoyo - 04-22-2016

Update:  Just tried it again with the latest Android image (20160303) and still no luck.


RE: WiFi module causes boot loop - tllim - 04-22-2016

(04-22-2016, 01:30 PM)bpcoyo Wrote:
(04-17-2016, 08:45 AM)tllim Wrote:
(04-15-2016, 04:24 PM)BnEc Wrote: Sadly I have had no luck, I'm unable to boot into Arch on the Pine when I have the WiFi module plugged in, looks like it is DOA.  I have tried several OSs and power cables, just tried it with the Pi 3 offical power supply. Pine will boot though will just loop while WiFi is in.

Does anyone know the process of getting a new one? Do Pine have an RMA process?

Please PM me and I will ship out a new Wifi/BT module to you.

I have this exact same problem and I've spent about 5 hours today trying to get it figured out.  But no luck and I have to resort to message board posting...

Pine64 2Gb.  Can't boot into Arch or Remix (20160227 or 20160415) with wifi module plugged in.  Multiple power cables don't do it, neither does offic. Pi3 power supply.  

Ethernet boots just fine, but wifi = endless bootloop.

From description, seems like you have a marginal working power supply or USB cable with Pine A64 board. When Pine A64 board boot up and certain point needs to draw more current, teh power supply stall and reboot. Since youi have try out several power supply, please check the USB cable.


RE: WiFi module causes boot loop - bpcoyo - 04-23-2016

(04-22-2016, 04:36 PM)tllim Wrote:
(04-22-2016, 01:30 PM)bpcoyo Wrote:
(04-17-2016, 08:45 AM)tllim Wrote:
(04-15-2016, 04:24 PM)BnEc Wrote: Sadly I have had no luck, I'm unable to boot into Arch on the Pine when I have the WiFi module plugged in, looks like it is DOA.  I have tried several OSs and power cables, just tried it with the Pi 3 offical power supply. Pine will boot though will just loop while WiFi is in.

Does anyone know the process of getting a new one? Do Pine have an RMA process?

Please PM me and I will ship out a new Wifi/BT module to you.

I have this exact same problem and I've spent about 5 hours today trying to get it figured out.  But no luck and I have to resort to message board posting...

Pine64 2Gb.  Can't boot into Arch or Remix (20160227 or 20160415) with wifi module plugged in.  Multiple power cables don't do it, neither does offic. Pi3 power supply.  

Ethernet boots just fine, but wifi = endless bootloop.

From description, seems like you have a marginal working power supply or USB cable with Pine A64 board. When Pine A64 board boot up and certain point needs to draw more current, teh power supply stall and reboot. Since youi have try out several power supply, please check the USB cable.

I've now tried two different power supplies (had the Rasp Pi3 one and an older 5v 2.5a) and 2 different cables (as well as both combinations).  All combinations power up Pi and have no power supply issues with other devices.  As I said, the device powers up with ethernet just fine (including while also powering a usb hub), but boot loops with wifi.


RE: WiFi module causes boot loop - BnEc - 04-25-2016

Thank you tllim new wifi module arrived today, will test out and will report back if it works.


RE: WiFi module causes boot loop - tllim - 04-26-2016

(04-25-2016, 03:00 PM)BnEc Wrote: Thank you tllim new wifi module arrived today, will test out and will report back if it works.

welcome, quicker than I thought.


RE: WiFi module causes boot loop - cyphergenetics - 09-24-2016

Sorry for bumping this but i have the same issue with or without wifi module. Tried multiple power source. Apparently only happens on Android image. Been running Ubuntu Xenial with apache server and left it on for a week with the Http server without problems but without the ability to use my LCD Touchscreen. Seems like Android the only Operating System that i can use my LCD Touchscreen on Pine64+


RE: WiFi module causes boot loop - pfeerick - 09-24-2016

(09-24-2016, 07:36 PM)cyphergenetics Wrote: Sorry for bumping this but i have the same issue with or without wifi module. Tried multiple power source. Apparently only happens on Android image. Been running Ubuntu Xenial with apache server and left it on for a week with the Http server without problems but without the ability to use my LCD Touchscreen. Seems like Android the only Operating System that i can use my LCD Touchscreen on Pine64+


Yeah, unless you want to go fiddling around in DTS, etc, Android is the only practical way to use the LCD atm. 

As the OP never got back, I would assume the replacement module worked. If you can run android with the LCD connected, we can probably rule out the power supply being a factor. I would think the pine64+LCD would draw more power than the pine64+wifi. As long as you're not plugging the module in wrong way around (14 connections one side, 16 on the other), I would suspect it is a faulty module, and it would be best to PM tllim and organise a replacement.