BBB wifi

I am trying to get my BBB to connect to my lan using wifi. The Adafruit 814 has been discontinued so I have a D-Link, model DWA-121 dongle. I used Simon Monk’s tutorial. When I tried to configure it in SSH nano told me that I do not have access to /var/lib/connman/ directory. Help! I am unable to connect wirelessly.

Does the wifi module show up? What do these 3 commands show...

sudo ifconfig -a
lsusb
uname -r

Regards,

When I query lsusb one of the lines was:
Bus 001 Device 002: d-link … and not a Realtek RT8188CUS …

I come from a background where you have to mess around with the IRC everytime you added a peripheral. I rejoiced the day when plug and play was introduced. The tutorial directed me to write the [service_home] in; /var/lib/connman/wifi.config, but that is a write protected directory.

I am ready to abandon any BeagleBone product if I can not easily resolve this problem.

So your "first" post was 5 hours ago, and now you just want to quit on
your "second" post...

So "lets" try this again, post the output of these 4 commands..

sudo ifconfig -a
lsusb
uname -r
sudo /opt/scripts/tools/version.sh

Regards,

Like I mentioned before. I am new to Beaglebone and I have been trying to make this work for a long time (years) so please understand my frustration.

when I query sudo ifconfig -a it asks me for a debian password. I don’t know the password.

When I query lsusb one of the lines was:
Bus 001 Device 002: d-link … and not a Realtek RT8188CUS …

I come from a background where you have to mess around with the IRC everytime you added a peripheral. I rejoiced the day when plug and play was introduced. The tutorial directed me to write the [service_home] in; /var/lib/connman/wifi.config, but that is a write protected directory.

I am ready to abandon any BeagleBone product if I can not easily resolve this problem.

So your “first” post was 5 hours ago, and now you just want to quit on
your “second” post…

So “lets” try this again, post the output of these 4 commands…

sudo ifconfig -a
lsusb
uname -r
sudo /opt/scripts/tools/version.sh

Regards,

Like I mentioned before. I am new to Beaglebone and I have been trying to make this work for a long time (years) so please understand my frustration.

Why did you wait years before you posted, or did you use a different
email address?

when I query sudo ifconfig -a it asks me for a debian password. I don't know the password.

It's the same password you used to login into the system with as the
user "debian"... "temppwd"..

Regards,

eth0: flags=-28669<UP, BROADCAST, MULTICAST, DYNAMIC> mtu 1500
ether: b0:d5:cc:0f:e9:eb txqueuelen 1000 (Ethernet)
RX packet 0 byte 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collision 0
devise interrupt 45

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

usb): flags=4099<UP, BROADCAST, MULTICAST> mtu 1500
inet 192.168.7.2 netmask 255.255.255.252 broadcast 192.168.7.3
ether b0:d5:cc:0f:e9:ed txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

usb1: flags=4099<UP, BROADCAST, MULTICAST> mtu 1500
inet 192.168.6.2 netmask 255.255.255.252 broadcast 192.168.6.3
ether b0:d5:cc:0f:e9:ed txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lsusb
Bus 001 Device 005: ID 2001:331b D-Link Corp.
Bus 001 Device 003: ID 258a:0001
Bus 001 Devise 002: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

uname -r
4.14.71-ti-r80

Sudo /opt/scripts/tools/version.sh
git: /oopt/scripts/:[1aa73453b2c980b75e31e83dab7dd8b6696f10c7]
eeprom:[A335BNLT00C02016BBBK2827]
MODEL:[TI_AM336x_Beaglebone_Black]
dogtag:[BeagleBoard.org Debian Image 2018-10-07]
bootloader:[microSD-(push-button):[/dev/mmcblk0]:[U-Boot 2018.09.00002-g0b54a51eee]:[location:dd MBR]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2015.10-00001-g143c9ee]:[location:dd MBR]
kernel:[4.14.71-ti-r80]
nodejs:[v6.14.4]
uboot_overlay_options:[enable_uboot_overlay=1]
uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-14-YI-00A0.dtbo]
uboot_overlay_options:[enable_uboo_cape_universal=1]
pkg check: to individually upgrade run:[sudo apt install --only-upgrade ]
pkg:[bb-cape-overlays]:[4.4.20180928.0-0rcnee0-stretch+20180928]
pkg:[bb-wl18xx=firmware]:[1020180517-0rcnee0-stretch+20180517]
pkg:[kmod]:[23-2rcnee1-stretch_20171005]
pkg:[librobotcontrol]:[1.0.3-git20181005.0-0rcnee1-stretch+20180328]
pkg:[firmware-ti-connectivity]:[20170823-1rcnee1-stretch_20180328]
groups:[debian : debian adm kmem dialoutbcdrom floppy audio spi tisdk weston-launch xenomai]
cmdline:[console=tty00,115200n8 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 quiet]
dmesg | grep pinctrl-single
[ 1.052428] pinctrl-single 44e10880.pinmux:142 pins at pa f9e10800 size 568
dmegs | grep gpio-of-helper
[ 1.053609] gpio-of-helper ocp:cape-universal: ready
END

Like I mentioned before. I am new to Beaglebone and I have been trying to make this work for a long time (years) so please understand my frustration.

Why did you wait years before you posted, or did you use a different
email address?

when I query sudo ifconfig -a it asks me for a debian password. I don’t know the password.

It’s the same password you used to login into the system with as the
user “debian”… “temppwd”…

Regards,

Thanks David!

lsusb
Bus 001 Device 005: ID 2001:331b D-Link Corp.

This looks like fun one, i've got a unit on order from Amazon, should
be arrive in the next week or two...

I've found a possible work-around here:

Please give this a try..

sudo modprobe 8188eu
sudo sh -c "echo '2001 331b' > /sys/bus/usb/drivers/r8188eu/new_id"

uname -r
4.14.71-ti-r80

Sudo /opt/scripts/tools/version.sh
git: /oopt/scripts/:[1aa73453b2c980b75e31e83dab7dd8b6696f10c7]
eeprom:[A335BNLT00C02016BBBK2827]
MODEL:[TI_AM336x_Beaglebone_Black]
dogtag:[BeagleBoard.org Debian Image 2018-10-07]
bootloader:[microSD-(push-button):[/dev/mmcblk0]:[U-Boot 2018.09.00002-g0b54a51eee]:[location:dd MBR]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2015.10-00001-g143c9ee]:[location:dd MBR]

BTW, your version of u-boot in teh eMMC will cause some other
problems.. It's best to run:

sudo dd if=/dev/zero of=/dev/mmcblk1 bs=1M count=100

This will "clear" out the first 100Mb of the eMMC partition, thus
removing the old version of u-boot..

BTW, one side issues we've had with rtl8188eu devices is noise from
the HDMI port, are you currently using the HDMI for anything.. If not
you should add:

disable_uboot_overlay_video=1

to /boot/uEnv.txt and that will disable the hdmi output and one source
of noise that causes some wifi antenna issues.

Regards,

Tried to do the fix in github.com
No Joy
Error writing Permission denied

now what?

respectfully,
David

Thanks David!

lsusb
Bus 001 Device 005: ID 2001:331b D-Link Corp.

This looks like fun one, i’ve got a unit on order from Amazon, should
be arrive in the next week or two…

I’ve found a possible work-around here:

https://github.com/ev3dev/ev3dev/wiki/USB-Wi-Fi-Dongles

Please give this a try…

sudo modprobe 8188eu
sudo sh -c “echo ‘2001 331b’ > /sys/bus/usb/drivers/r8188eu/new_id”

uname -r
4.14.71-ti-r80

Sudo /opt/scripts/tools/version.sh
git: /oopt/scripts/:[1aa73453b2c980b75e31e83dab7dd8b6696f10c7]
eeprom:[A335BNLT00C02016BBBK2827]
MODEL:[TI_AM336x_Beaglebone_Black]
dogtag:[BeagleBoard.org Debian Image 2018-10-07]
bootloader:[microSD-(push-button):[/dev/mmcblk0]:[U-Boot 2018.09.00002-g0b54a51eee]:[location:dd MBR]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2015.10-00001-g143c9ee]:[location:dd MBR]

BTW, your version of u-boot in teh eMMC will cause some other
problems… It’s best to run:

sudo dd if=/dev/zero of=/dev/mmcblk1 bs=1M count=100

This will “clear” out the first 100Mb of the eMMC partition, thus
removing the old version of u-boot…

BTW, one side issues we’ve had with rtl8188eu devices is noise from
the HDMI port, are you currently using the HDMI for anything… If not
you should add:

disable_uboot_overlay_video=1

to /boot/uEnv.txt and that will disable the hdmi output and one source
of noise that causes some wifi antenna issues.

Regards,

Okay, thanks for testing that.

Amazon currently shows: Arriving Jan 22 - Jan 25

So maybe i'll have an answer next week.

If you don't want to wait that long, find a USB WiFi module using a
non Realtek chipset..

Regards,

On Wed, 16 Jan 2019 19:15:08 +0000 (UTC), david rediger
<david.rediger@att.net> declaimed the following:

Tried to do the fix in github.comNo JoyError writing Permission denied
now what?

  Did you do that from a root user privilege level? Did you try changing
file protection first?

{I'm too lazy to hook up a BBB just for the example, so this is an RPi-3
running Pi-Star release -- still a Debian OS [though Pi-Star is still on
Jessie]}

pi-star@pi-star-3b(rw):~$ ls -l /etc/udev
total 12
drwxr-xr-x 2 root root 4096 Apr 2 2016 hwdb.d
drwxr-xr-x 2 root root 4096 Aug 14 2017 rules.d
-rw-r--r-- 1 root root 148 Apr 2 2016 udev.conf
pi-star@pi-star-3b(rw):~$ ls -l /etc/udev/rules.d/
total 4
-rw-r--r-- 1 root root 983 Mar 21 2016 99-com.rules
pi-star@pi-star-3b(rw):~$ vim /etc/udev/rules.d/99-com.rules

  *** get warning about editing a read-only file

pi-star@pi-star-3b(rw):~$ ls -l /etc/udev/rules.d/
total 4
-rw-r--r-- 1 root root 983 Mar 21 2016 99-com.rules
pi-star@pi-star-3b(rw):~$ chmod ugo+w /etc/udev/rules.d/99-com.rules
chmod: changing permissions of ‘/etc/udev/rules.d/99-com.rules’: Operation
not permitted

  *** note that user level can not change file protection

pi-star@pi-star-3b(rw):~$ sudo chmod ugo+w /etc/udev/rules.d/99-com.rules
pi-star@pi-star-3b(rw):~$ ls -l /etc/udev/rules.d/
total 4
-rw-rw-rw- 1 root root 983 Mar 21 2016 99-com.rules

  *** file is now read/write for everyone

pi-star@pi-star-3b(rw):~$ vim /etc/udev/rules.d/99-com.rules

  *** no warning when editing

pi-star@pi-star-3b(rw):~$ ls -l /etc/udev/rules.d/
total 4
-rw-rw-rw- 1 root root 985 Jan 16 16:46 99-com.rules

  *** time stamp updated to show result of editing

pi-star@pi-star-3b(rw):~$
pi-star@pi-star-3b(rw):~$ sudo chmod go-w /etc/udev/rules.d/99-com.rules

  *** restore original protection

pi-star@pi-star-3b(rw):~$ ls -l /etc/udev/rules.d/
total 4
-rw-r--r-- 1 root root 983 Jan 16 16:49 99-com.rules
pi-star@pi-star-3b(rw):~$ vim /etc/udev/rules.d/99-com.rules

  *** again shows warning of read-only file

pi-star@pi-star-3b(rw):~$ sudo vim /etc/udev/rules.d/99-com.rules
pi-star@pi-star-3b(rw):~$

  *** no warning, since running as root, and root always had read/write

  I would strongly suggest you obtain a book on administering a Linux
system -- many of your comments (password requested for sudo command, file
protection matters, etc.) have come across as a lack of knowledge about the
OS, and not of the board itself.

Yes I did it from the root. Don’t know how to change file protection.

On Wed, 16 Jan 2019 19:15:08 +0000 (UTC), david rediger

<david.rediger@att.net> declaimed the following:

Tried to do the fix in github.comNo JoyError writing Permission denied

now what?

Did you do that from a root user privilege level? Did you try changing

file protection first?

{I’m too lazy to hook up a BBB just for the example, so this is an RPi-3

running Pi-Star release – still a Debian OS [though Pi-Star is still on

Jessie]}

pi-star@pi-star-3b(rw):~$ ls -l /etc/udev

total 12

drwxr-xr-x 2 root root 4096 Apr 2 2016 hwdb.d

drwxr-xr-x 2 root root 4096 Aug 14 2017 rules.d

-rw-r–r-- 1 root root 148 Apr 2 2016 udev.conf

pi-star@pi-star-3b(rw):~$ ls -l /etc/udev/rules.d/

total 4

-rw-r–r-- 1 root root 983 Mar 21 2016 99-com.rules

pi-star@pi-star-3b(rw):~$ vim /etc/udev/rules.d/99-com.rules

*** get warning about editing a read-only file

pi-star@pi-star-3b(rw):~$ ls -l /etc/udev/rules.d/

total 4

-rw-r–r-- 1 root root 983 Mar 21 2016 99-com.rules

pi-star@pi-star-3b(rw):~$ chmod ugo+w /etc/udev/rules.d/99-com.rules

chmod: changing permissions of ‘/etc/udev/rules.d/99-com.rules’: Operation

not permitted

*** note that user level can not change file protection

pi-star@pi-star-3b(rw):~$ sudo chmod ugo+w /etc/udev/rules.d/99-com.rules

pi-star@pi-star-3b(rw):~$ ls -l /etc/udev/rules.d/

total 4

-rw-rw-rw- 1 root root 983 Mar 21 2016 99-com.rules

*** file is now read/write for everyone

pi-star@pi-star-3b(rw):~$ vim /etc/udev/rules.d/99-com.rules

*** no warning when editing

pi-star@pi-star-3b(rw):~$ ls -l /etc/udev/rules.d/

total 4

-rw-rw-rw- 1 root root 985 Jan 16 16:46 99-com.rules

*** time stamp updated to show result of editing

pi-star@pi-star-3b(rw):~$

pi-star@pi-star-3b(rw):~$ sudo chmod go-w /etc/udev/rules.d/99-com.rules

*** restore original protection

pi-star@pi-star-3b(rw):~$ ls -l /etc/udev/rules.d/

total 4

-rw-r–r-- 1 root root 983 Jan 16 16:49 99-com.rules

pi-star@pi-star-3b(rw):~$ vim /etc/udev/rules.d/99-com.rules

*** again shows warning of read-only file

pi-star@pi-star-3b(rw):~$ sudo vim /etc/udev/rules.d/99-com.rules

pi-star@pi-star-3b(rw):~$

*** no warning, since running as root, and root always had read/write

I would strongly suggest you obtain a book on administering a Linux

system – many of your comments (password requested for sudo command, file

protection matters, etc.) have come across as a lack of knowledge about the

OS, and not of the board itself.

On Wed, 16 Jan 2019 22:49:30 +0000 (UTC), david rediger
<david.rediger@att.net> declaimed the following:

Yes I did it from the root. Don't know how to change file protection.

  I provided examples of doing just that...

  Show us what "ls -l" displays for the file -- since that will show what
protection is in place, and who owns the file...

~$ sudo chmod ugo+w /etc/udev/rules.d/99-com.rules

No such file or directory

On Wed, 16 Jan 2019 22:49:30 +0000 (UTC), david rediger

<david.rediger@att.net> declaimed the following:

Yes I did it from the root. Don’t know how to change file protection.

I provided examples of doing just that…

Show us what “ls -l” displays for the file – since that will show what

protection is in place, and who owns the file…

On Sat, 19 Jan 2019 16:43:10 +0000 (UTC), david rediger
<david.rediger@att.net> declaimed the following:

~$ sudo chmod ugo+w /etc/udev/rules.d/99-com.rules
No such file or directory

  Use the file YOU have available... My example was for the file on my
RPi (I don't have a WiFi capable BeagleBone).

Dennis,
As I said before I am a newbie and will ask a lot of rookie questions. I have enrolled in a Linux Course on EdX. I have experience in DOS even though Linux works on a different convention I can relate a lot of the protocols to DOS.

I did a ‘ls’ to ‘/etc/udev/rules.d/’

here are the results:

50-hidraw.rules 80-gpio-noroot.rules 83-eqep-noroot.rules beagle-tester.rules
50-spi.rules 81-pwm-noroot.rules 84-gpio-noroot.rules tisdk.rules
60-omap-tty.rules 82-gpio-config-pin.rules 85-gpio-noroot.rules uio.rules

My BBB is not WiFi capable either. Hence the Dongle.
The dongle came with a disk. Is the driver I need on that disk and if so:
How do I get it to my BBB?
How do I active the dongle with it?

If the directories need admin permission how do I unlock it to change the directories I need?

v/r David

On Sat, 19 Jan 2019 16:43:10 +0000 (UTC), david rediger

<david.rediger@att.net> declaimed the following:

~$ sudo chmod ugo+w /etc/udev/rules.d/99-com.rules

No such file or directory

Use the file YOU have available… My example was for the file on my

RPi (I don’t have a WiFi capable BeagleBone).

Found this workaround in GIT Hub:

2001:331b D-Link Corp. DWA-121 rev B1

  • Very small and cheap device.

  • Supported by the rtl8188eu driver, but isn’t detected yet by the driver supplied with the ev3dev-stretch beta.

    Workaround:
    Create a new udev rule
    nano /etc/udev/rules.d/99-dwa121.rules
    And add the following line:
    ACTION=="add", ATTRS{idVendor}=="2001", ATTRS{idProduct}=="331b", RUN+="/sbin/modprobe 8188eu" RUN+="/bin/sh -c 'echo 2001 331b > /sys/bus/usb/drivers/r8188eu/new_id'"

But when I try to create it I get a message if I do not have permission.

How do I get permission? is there some sort of password I have to use?

On Sat, 19 Jan 2019 16:43:10 +0000 (UTC), david rediger

<david.rediger@att.net> declaimed the following:

~$ sudo chmod ugo+w /etc/udev/rules.d/99-com.rules

No such file or directory

Use the file YOU have available… My example was for the file on my

RPi (I don’t have a WiFi capable BeagleBone).

On Mon, 21 Jan 2019 20:49:20 +0000 (UTC), david rediger
<david.rediger@att.net> declaimed the following:

Dennis,As I said before I am a newbie and will ask a lot of rookie questions. I have enrolled in a Linux Course on EdX. I have experience in DOS even though Linux works on a different convention I can relate a lot of the protocols to DOS.
I did a 'ls' to '/etc/udev/rules.d/'

  Which is NOT "ls -l " to show owner/protection

My BBB is not WiFi capable either. Hence the Dongle.The dongle came with a disk. Is the driver I need on that disk and if so: How do I get it to my BBB?How do I active the dongle with it?

  The disk probably contains Windows drivers -- very few devices are
provided with Linux drivers (and even if it did, it would be for an Intel
architecture, not ARM -- unless it is provided in source code form so it
can be compiled on the target system). Either the device is already
recognized by the OS and has a built-in driver it can load, or one ends up
downloading the package from the distribution's package manager (and that
will require a network connection -- most likely via a CAT-5 cable to some
router connected to the internet).

If the directories need admin permission how do I unlock it to change the directories I need?

  By using the various commands I showed /with the file name you need to
affect/

I found a Beagebone for Dummies post and figured out why I could not write to protected files. I had to log in as a Superuser. Once I did that did that I wrote the workaround in. Unfortunately the drivers file lacked the r8188eu driver necessary to link the dongle.

I have a trouble report to GitHub for a patch request.

Thank you for your help.
v/r David

On Mon, 21 Jan 2019 20:49:20 +0000 (UTC), david rediger

<david.rediger@att.net> declaimed the following:

Dennis,As I said before I am a newbie and will ask a lot of rookie questions. I have enrolled in a Linux Course on EdX. I have experience in DOS even though Linux works on a different convention I can relate a lot of the protocols to DOS.

I did a ‘ls’ to ‘/etc/udev/rules.d/’

Which is NOT "ls -l " to show owner/protection

My BBB is not WiFi capable either. Hence the Dongle.The dongle came with a disk. Is the driver I need on that disk and if so: How do I get it to my BBB?How do I active the dongle with it?

The disk probably contains Windows drivers – very few devices are

provided with Linux drivers (and even if it did, it would be for an Intel

architecture, not ARM – unless it is provided in source code form so it

can be compiled on the target system). Either the device is already

recognized by the OS and has a built-in driver it can load, or one ends up

downloading the package from the distribution’s package manager (and that

will require a network connection – most likely via a CAT-5 cable to some

router connected to the internet).

If the directories need admin permission how do I unlock it to change the directories I need?

By using the various commands I showed /with the file name you need to

affect/

I found a Beagebone for Dummies post and figured out why I could not write to protected files. I had to log in as a Superuser. Once I did that did that I wrote the workaround in. Unfortunately the drivers file lacked the r8188eu driver necessary to link the dongle.

I have a trouble report to GitHub for a patch request.

Thank you for your help.
v/r David

Okay, finally an update on this issue. My Dongle from Amazon arrive
over the weekend, same vid/pid as you..

debian@beaglebone:~$ lsusb
Bus 001 Device 002: ID 2001:331b D-Link Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Found the mainline fix, just a vid/pid update

[ 29.374580] r8188eu: module is from the staging directory, the
quality is unknown, you have been warned.
[ 29.817901] Chip Version Info:
CHIP_8188E_Normal_Chip_TSMC_D_CUT_1T1R_RomVer(0)
[ 29.972280] usbcore: registered new interface driver r8188eu
[ 30.767851] MAC Address = 00:ad:24:90:c7:a9
[ 30.784084] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready

wlan0: flags=-28669<UP,BROADCAST,MULTICAST,DYNAMIC> mtu 1500
        ether 00:ad:24:90:c7:a9 txqueuelen 1000 (Ethernet)
        RX packets 0 bytes 0 (0.0 B)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 0 bytes 0 (0.0 B)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

debian@beaglebone:~$ sudo connmanctl

scan wifi
services

*AO Wired ethernet_3403de9a8e37_cable
                         wifi_00ad2490c7a9_hidden_managed_psk
                         wifi_00ad2490c7a9_hidden_managed_none
    Content_Dev wifi_00ad2490c7a9_436f6e74656e745f446576_managed_psk
    DKE_Employee
wifi_00ad2490c7a9_444b455f456d706c6f796565_managed_ieee8021x
    DKE_Guest wifi_00ad2490c7a9_444b455f4775657374_managed_psk
    TE-M321-SDK-01054
wifi_00ad2490c7a9_54452d4d3332312d53444b2d3031303534_managed_psk
    dd-wrt wifi_00ad2490c7a9_64642d777274_managed_psk
Scan completed for wifi

Patch is now merged:

and pushed out to the build farm..

in roughly 6 hours from now, just run:

sudo /opt/scripts/tools/update_kernel.sh

and it should try to install "4.14.94-ti-r92" which has the fix for this module.

Regards,