Raspberry pi3 A+ no interfaces

Hi, I am already desperate. I "dd" image on SD card, put it in RPi3A+ having console with USB serial converter. System boots I can even change password after first boot. But ifconfig shows only loop device. No wlan no eth (I tried two different usb-lan as there is no eth on board. But I can see in network file lan shoul be static 192.168.1.1 but of course it does not ping as it does not exist. What is going on?? Why no wifi no lan? Wifi is configured in wireless file to be 5G AP. ?????? Heeelp!

post the console boot log, might need to use several posts and split it up.

you'll never get a 5G AP from the built in radio.

Forget it, OpwnWrt for this is total sh*t. I wanted to try to make sysupgrade but I can not even mount usb stick:
root@OpenWrt:/tmp/xxx# mount |grep sda
root@OpenWrt:/tmp/xxx# ls /dev |grep sda
sda
sda1
root@OpenWrt:/tmp/xxx# mount -t vfat /dev/sda1 /tmp/xxx
root@OpenWrt:/tmp/xxx# ls
root@OpenWrt:/tmp/xxx#

it shows no files
I am surprised how anybody could publish files for this device without even to try them?!

don't let the door hit you in the back on your way out ...

does your openwrt image include the fs support packages (it doesn't, by default) ?

it sure sucks when stuff you get for free doesn't work ....

exactly, better not to do anything or publish it on tiktok with those famous perpetum mobile

@sky59 - just to be clear...

  1. Network hardware:
    As you have stated, since your Pi3 A+ doesn't have any wifi or ethernet hardware, you are obviously reliant on a USB-ethernet or USB-wifi adapter. These devices require drivers which are not included in the default firmware image for OpenWrt. You need to determine which chipset is used in the adapter you are using, and create a custom image (using the firmware selector) that includes the appropriate driver packages. Without that, the adapter(s) will not work.

  2. Filesystem support/mounting
    Like the situation with the network adapters, the default firmware image doesn't include additional filesystem drivers. You need to add those to the image as well, if you want to be able to mount vfat or other filesystems.

It does have wifi hardware, this is the reason I purchased it.
Once it mounted usb stick, just once. Why then no error message that it can not be mounted? Even mount shows it IS mounted but no files.

ok... so how did you determine that the wifi was not working? Wifi is disabled by default on OpenWrt. You need to enable it.

Let's see the output of the following (you can use the serial console to get this information):

Please connect to your OpenWrt device using ssh and copy the output of the following commands and post it here using the "Preformatted text </> " button:
grafik
Remember to redact passwords, MAC addresses and any public IP addresses you may have:

ubus call system board
cat /etc/config/network
cat /etc/config/wireless
cat /etc/config/dhcp
cat /etc/config/firewall

I can not ssh, no interface is working. I had a look at selector you mentioned and there IS support for vfat in the image. But does not work. Anyway, as there is wifi hardware it is for me total nonsense not to have it active by default. It is the only way to connect to it. I will try raspbian, if it works I forget owrt

Wifi, no wlan in ifconfig, no really any AP from it checked with mobile

Sorry, that was boiler plate. You can use the serial console.

You will not see the wlan hardware in the ifconfig output. You may see br-lan, though, which is a bridge to which the wifi can attach.

And yes, you will not see an AP running because wifi is disabled by default.

Please use the serial console to grab the files requested.

I have no time to waste. I used to use chaos calmer 15.05 and was very happy with it. Downloaded image, flashed it and everything was working!
Now? There is the ONLY way to connect to 3A+ over wifi and it is disabled??? No support for vfat? Threre is also no support for ndis modem, no usb-modeswitch! There is nothing, it is useless. I think the original goal for owrt was take-it-flashit-use-it, this is not true anymore. No luci over serial console, nothing, useless. I know how to configure debian, but this is different, I am not going to study another files regarding network. Totally disapointed

1 Like

If you're not happy, use something else. I'm trying to help you, but I can only do so if you share the files so that we know what is going on (otherwise it's a mystery).

By not gathering the files I requested (via the serial console that you said is working), you're actually wasting your own time.

1 Like

On your RasPi 3A+?
Then it was a fork, something loosely based on the original and heavily modified. Because the original OpenWrt supports this board since 18.06.0

1 Like

OK, I slept a bit (though I was too excited yesterday) calmed down and decided to give it another chance. Because I liked ChaosCalmer too much. (not for pi3 A+ !)
I did not know abovementioned "firmware selector" can generate what I need. Unfortunately it is not described deeply anywhere, at least I did not find it.
So I added two packages kmod-usb-net-dm9601-ether & kmod-usb-net-qmi-wwan
Also this was not straight-forward as I had to search Packages to get proper name of the package (:slight_smile: to add it in the window for generating "my" image. I was also a bit confused as I was not sure it is really for me what I downloaded base on added two my packages.
Long story short: connected DM9601 usb-lan, immediatelly visible in ifconfig as eth0 static 192.168.1.1 so I could connect PC and in browser open LUCI interface. I could configure wlan as master so I can now connect to it also on 192.168.1.1
I replaced DM9601 with usb modem with sim card but as I expected it is not found, not working. I already noticed usb-modeswitch does not exist.
I do have now kmod-usb-net-qmi-wwan in the image but I do not know how to deal with this modem. In chaoscalmer it used usb-modeswitch and other staff, something to do with Sierra. I am stuck again (:
What to do next? How to make usb modem work? Thanx!

DONE.
I found out usb-modeswitch is in base, unfortunately link does not point on base folder so I could not find it like others.
I installed everything for every type of modem.
MBIM has problem with wrong PIN - but it is not required!?
QIM works like charm, very very fast 30/30Mbit/s. I use 64b system. Radio seems to be excellent with super sensitivity though not external antenna. Inside building trough 2 walls estimated distance 30 meters.
The most useful info for me from you guys was "discovering" that page which generates images.
I can not resist to write that any "normal" user would not probably solve all these problems I was faced - this is not to say I am something super excellent!

While admittedly the documentation for OpenWrt is lacking in some areas, I want to point out that you arrived here with wrong expectations. OpenWrt is a minimalistic embedded distribution, mainly intended for routers, which does not and should not include every driver for every device. Rather, the images intentionally include the minimum selection of drivers to enable all built-in components of given device. Evidently, this worked as designed in your case. Wifi is not and should not be enabled out of the box for security and regulatory reasons.

I disagree with you on one point: for pi3A+ wifi SHOULD be active as it is the only way to do something with it. Otherwise it is like giving birth - I proved it.
If it is, SSID openwrt, no crypting then it would be child's game to deal with it.
In my case:

  • I needed usb-ftdi serial converter for console
  • I needed DM9601 usb-lan converter
  • I needed to search for packages and generate image with them
    if wifi is active, no need to generate image, just connect and do opkg install what you need
    these two approaches can not be even compared with complexity of each

If you knew that you needed to generate a custom image which would include the driver for your usb ethernet adapter, you wouldn't need to use USB-to-serial, right? So IMO this is what needs to be improved, in the documentation. If so, you could contribute to the project by modifying the wiki page for raspberry pi devices, or asking someone with wiki editing permissions to do the same.

I don't think that the idea of enabling wifi out-of-the-box is going to be implemented. Maybe it is possible to configure the custom image in a way which enables wifi - @efahl ?

Sure, just add an init script that enables WiFi on first boot

uci set wireless.radio0.disabled=0  # or whatever

in the Script to run on first boot (uci-defaults) on

1 Like

Yes, right. After battle everybody is general :slight_smile: I had in my hands dead pcb and console was the only thing that worked. There I realized I have no interfaces at all using ifconfig. So I do not know if I needed it or not. This was the very first information