Problems in ArchArm

[newaddressunknown]

The IoT_pHAT seems to be not recognized as a wifi-device in ArchARM. What would be the next place to look into for debbuging?

• device accessible
  $ cat /proc/device-tree/hat/product
IoT pHAT w/eep_v0.3
$ ls /proc/device-tree/soc/iothat/
name pinctrl-0 pinctrl-names status
$ cat /proc/device-tree/soc/iothat/status
okay

• not recognized as wifi device
  $ ifconfig -a
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1 (Local Loopback) RX packets 344 bytes 29704 (29.0 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 344 bytes 29704 (29.0 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

[procount]

Looks like the same issue as NOOBS had. See its resolution in v2.1 raspberrypi/noobs@9e9184c

[newaddressunknown]

looking at
https://github.com/archlinuxarm/PKGBUILDs/blob/master/core/linux-raspberrypi/config.v6
it seems, that these options are already enabled by default. My current kernel is
Linux alarmpi 4.4.33-1-ARCH #1 Sat Nov 19 14:05:02 MST 2016 armv6l GNU/Linux

Is there a way to check at runtime wether the options are enabled?
Checking the enabled options:
cat /proc/config.gz | gunzip > running.config
produced the attached file.
running.config.txt

The options
CONFIG_POWER_SUPPLY=y
CONFIG_POWER_RESET=y
CONFIG_POWER_RESET_GPIO=y
are set

after adding the modules
i2c-bcm2708
i2c-dev
to load at startup, I get the following i2cdetect-output

$ sudo i2cdetect -y 0
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: 50 -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

[halocaridina]

I can confirm that the IoT_pHAT is not recognized as a wifi-device in ArchARM. In contrast, booting the same Pi Zero and IoT_pHAT off a clean install of Raspbian/Jessie Lite 2016-11-25 and was connected to the Internet in 2 min. Some quick comparisons between ArchARM running on the Pi Zero vs a RaspPI 3B regarding kernel compilation options, kernel modules/drivers and firmware found no obvious differences. Still need to do some comparisons of these between ArchARM on the RaspPI 3B vs. Jessie Lite 2016-11-25 on the Pi Zero to see what might be needed to get the IoT_pHAT up and running in ArchARM.

Do the Redbear developers of the IoT_pHAT have any suggestions for people on ArchARM to try?