TracyLBaker wrote:Before I continue... Is this one Pi, or two?
To clarify, we're only talking about one Pi, two SD cards. (Not to confuse things, but I do have a second Pi-to-jamma setup, but I've not had it in the mix at all. It's identical to the first. I'm trying to help my friend setup his first, then got excited and bought my own.)
TracyLBaker wrote:1) Why is there a wlan1 (in both)? Do you have two wireless adapters? If so, the working in the "working" machine isn't even configured. This is seen in your /etc/network/interfaces file.
TracyLBaker wrote:3) On the working config, you're showing two IPv4 addresses 192.168.7.34/24 and 192.168.7.33/24 on the wlan0 interface. While it is obviously working, this something that is most likely misconfigured.
TracyLBaker wrote:4) Why do you have AppleTalk filing protocol (on port 548) on the working config? I only ask because I can't remember the last time I saw anything AppleTalk -- but if its needed, it is needed.
TracyLBaker wrote:2) On both configurations, DHCP isn't working with the eth0 interface. That's why it shows an APIPA address (169.254.x.x), which is an address that a computer assigns to itself when it cannot reach a DHCP server, see: http://www.webopedia.com/TERM/A/APIPA.html -- APIPA is actually a Microsoft thing, not a Linux thing. Upon doing a little research, I found that Avahi (a zero configuration tool for Linux) will do the same thing.
They both show the same APIPA addresses. This is interesting because APIPA addresses are randomly derived from the 169.254.0.0/16 network -- meaning they can range from 169.254.0.1 to 169.254.255.254 -- a total of 65,534 different addresses -- to have two that are the same is very unlikely (but possible). Additionally, before a machine uses an APIPA address, it pings the network to make certain it isn't already in use.
In either case, the address is not in your network. So now you apparently have something else jacking with the network settings ... and maybe the thing that's preventing your being able to fix this.
A lot of good detective work here, but I'm afraid I'm not sure how to provide answers. Again we're just talking about one Pi 3, with its built-in wifi. I'm plugging an ethernet into the Pi, then that cable is going into a USB-C adapter and into my MBP. AppleTalk must be showing on the working wifi build because initially I thought I needed to setup VNC, tried and failed, but along the way, once the wifi was working, the Pi would show itself as a shared computer in Finder. It may have been a "getting your Pi to work with OS X" tutorial, wish I could remember, but as far as I can tell I've already reread all of the tutorials I worked through with the first build. I'd love to have the new build showing up in Finder again, as that was a great pairing along with SSH to modify certain files.
All I recall with that first build is working through a few tutorials and to my surprise I got the wifi working somehow. Perhaps when I was trying to prep for VNC I installed a package that modified a few things.
TracyLBaker wrote:Before I continue... I had a thought. Since you have two of these, have you tried swapping the SD cards to see if the problem follows the card? If it does, it is something hosed with the installation. If it does not, then you most likely have a hardware problem.
If it follows the card, you can use dd to copy the working image onto the SD card with the non-working image. You'd need a USB micro SD card reader to do this.
I'm wondering, where did you get the pi-to-jamma image? I've done a little looking and I don't see it about.
Per your request, I put the non working wifi image into my second Pi (that's been sitting aside, unused through all of this), and have the exact same results -- no wifi.
I'm concerned about copying the working wifi image because I believe this build or the SD card to be bad in other ways. I spent several nights trying to make an image from that card and it fails partway through. I tried one MBP, one Windows machine with an internal SD reader, command line, a gui, all with the same results. Someone suggested due to my original SD reader having its own issues and randomly unmounting the SD card, it may have corrupted something.
So while that build has the lovely working wifi, it likely has other faults. I've only kept it around for testing, but glad I did.