I hate to make an unhelpful "me too" post, but... me too. Same adapter.

I did notice that in the boot logs from journalctl, everything seems like 
it's working fine up until connmand starts. I'm not too familiar with 
connmanctl or how connmand works, so I'm kind of bumbling around with that 
at the moment.

On Monday, December 14, 2015 at 8:06:17 PM UTC-5, [email protected] wrote:
>
> I have recently acquired a Beagleboard Black for a project and am having 
> some problems with WiFi rfkill soft blocking.
>
> Following the the recommendations on the getting started page, I updated 
> the system to the latest Jessie release, Debian 8.2 2015-11-12. I also 
> followed the recommendation to update to the latest kernel: 4.1.13-ti-r36 
> as of this writing.
>
> I next attached a WiFi adaptor: Realtek Semiconductor RTL8188CUS 802.11n, 
> and followed the recommendation to edit the /etc/network/interfaces file to 
> uncomment the WLAN example and set the SSID and passphrase (using the 
> output of wpa_passphrase).
>
> I saw that rfkill has the interface soft blocked; manually unblocking the 
> interface, I can connect to my WiFi network, however, this does not survive 
> a reboot, even though the systemd-rfkill service is running, which should 
> preserve rfkill state across reboots. Further checking the service, I 
> discovered that by default the rfkill service saves the state, but does not 
> restore unless a kernel parameter, system.restore_state is set, which I 
> have done in the uEnv.txt file via:
>
> cmdline=coherent_pool=1M quiet cape_universal=enable 
> systemd.restore_state=1
>
> Despite this, the WiFi is still blocked upon boot. Any ideas for what 
> configuration changes are needed to get WiFi enabled (hopefully without a 
> kludge tower of scripts, this ought to be a single parameter change 
> somewhere)?
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to