Connect to wifi

Hey @alpo that does sound odd, can you also provide the output of ifconfig -a and the content of your config.txt for reference?

This is the output of ifconfig -a:

pi@raspberrypi:~ $ ifconfig -a
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.5.212 netmask 255.255.255.0 broadcast 192.168.5.255
inet6 fe80::1b1b:5e2f:a030:d14f prefixlen 64 scopeid 0x20
ether b8:27:eb:d6:ef:21 txqueuelen 1000 (Ethernet)
RX packets 34773 bytes 3830093 (3.6 MiB)
RX errors 0 dropped 2067 overruns 0 frame 0
TX packets 14343 bytes 11553376 (11.0 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1000 (Local Loopback)
RX packets 25 bytes 1484 (1.4 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 25 bytes 1484 (1.4 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

As you can see I’m connected with wired ethernet but I can’t see WiFi.

And is is my config.txt:

For more options and information see

http://rpf.io/configtxt

Some settings may impact device functionality. See link above for details

uncomment if you get no picture on HDMI for a default “safe” mode

#hdmi_safe=1

uncomment this if your display has a black border of unused pixels visible

and your display can output without overscan

disable_overscan=1

uncomment the following to adjust overscan. Use positive numbers if console

goes off screen, and negative if there is too much border

#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

uncomment to force a console size. By default it will be display’s size minus

overscan.

#framebuffer_width=800
#framebuffer_height=600

uncomment if hdmi display is not detected and composite is being output

hdmi_force_hotplug=1

Force a specific HDMI mode (800x600 60Hz)

hdmi_group=2
hdmi_mode=9
hdmi_ignore_edid=0xa5000080

uncomment to force a HDMI mode rather than DVI. This can make audio work in

DMT (computer monitor) modes

#hdmi_drive=2

uncomment to increase signal to HDMI, if you have interference, blanking, or

no display

#config_hdmi_boost=4

uncomment for composite PAL

#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800

Uncomment some or all of these to enable the optional hardware interfaces

dtparam=i2c_arm=on
#dtparam=i2s=on
dtparam=spi=on

Uncomment this to enable the lirc-rpi module

#dtoverlay=lirc-rpi

Additional overlays and parameters are documented /boot/overlays/README

Enable audio (loads snd_bcm2835)

dtparam=audio=on
dtoverlay=balena-fin-updated
dtoverlay=i2c-rtc,ds1307

Thank you in advance.

Hey @AlPo and @markusk , I’m currently investigating this issue. It appears as though the wlan driver we supply with our raspbian image is being removed upon apt-get upgrade.

I’m currently working towards a solution for this and will report back as I get more information.

Thanks!

Thank you @bucknalla.
Only as a patch while you’re looking for a permanent solution, is there a way to manually load the drivers in question?

@bucknalla, do you have some news?

Hi @AlPo,

It looks like it has to do with our CI doing automated releases of the fin Raspbian image - I’m checking with the OS team to see if we can package the driver as standalone for the time being so we can get you up and running. I’ll keep checking in here as this develops!

Thanks for your patience!

I just also want to say that we are in the same boat. We needed to reinstall several of our balenaFins due to the wlan driver disappearing after an update. So yea, a workaround (packaged standalone driver) would be much appreciated at this point!