Enoch <[email protected]> writes: > Robert Nelson <[email protected]> > writes: > >> On Tue, Dec 22, 2015 at 7:32 PM, Robert Nelson <[email protected]> >> wrote: >>> On Tue, Dec 22, 2015 at 6:56 PM, Enoch <[email protected]> wrote: >>>> Hi Robert, >>>> >>>> Like other USB WiFi users before me I have had the chipset (RT5370 in my >>>> case) soft blocked after each boot. The problem, IMHO, rests with >>>> /lib/systemd/systemd-rfkill and not with rfkill itself. >>>> >>>> The /lib/systemd/system/[email protected] unit is expected to >>>> restore the blocking state of all devices after boot to what they were >>>> on shutdown. This is a perfect policy only that it has some bug... >>>> >>>> The network-manager package nmtui utility is a too convenient solution >>>> to those encountering trouble or otherwise this systemd bug would have >>>> been long gone. >>>> >>>> Can you provide a pointer to systemd-rfkill source code of the latest >>>> image? >>> >>> So in wheezy, we have systemd v215 >> >> "jessie" >> >> Regards, >> >> -- >> Robert Nelson >> https://rcn-ee.com/ > > The Season's Greetings! > > (1) I'm pleased to advise that your recent systemd update solved the problem > with systemd-rfkill. No longer it comes up soft blocked. > > (2) I need a DTB with ttyS4 enabled so I have to use dtb-rebuilder. My > first attempt bricked the system though I made sure (at least > I believe so) to have matching sources... will try again.
Answering my own question for the occasional Googler: RN is using a non standard DTC. Run the script 'dtb-rebuilder/dtc-overlay.sh' to create. Could have helped if the README had mentioned that :-) Regards, Enoch. > > Regards, Enoch. -- 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.
