Date: Tue, 13 Mar 2018 01:05:06 +0000 From: Shamim Shahriar <shamim.shahriar@gmail.com> To: Ralph Smith <ralph@ralphsmith.org> Cc: freebsd-arm@freebsd.org Subject: Re: PPS or /dev/ppsN on Raspberry Pi 3 Message-ID: <2ef1f6f3-3e8f-529f-33dd-3a75f86891f3@gmail.com> In-Reply-To: <5F567062-88EF-4707-B8A7-2B5841C23E38@ralphsmith.org> References: <819975e8-56a8-677b-e5f5-003ff2091553@gmail.com> <20180312011202.GA60784@bluezbox.com> <9d27f6ff-d317-aa24-4f22-b06624fd6d1d@gmail.com> <5F567062-88EF-4707-B8A7-2B5841C23E38@ralphsmith.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 12/03/2018 14:48, Ralph Smith wrote: > Look for /dev/gpiopps* > > You may also need to load gpiopps.ko > > Ralph > thanks to all who responded and helped with the issue. The problem was, even though i had gpiopps_load="YES" in my /boot/loader.conf, and the module was loaded during boot -- it was NOT creating anything in the /dev/ folder. Same was true for a uftdi_load="YES". Even worse, if I built the ftdi module into the kernel, the system would not boot for some reason. So I did what felt quite logical (after reading all the supporting emails you have sent me, thank you so much). I unloaded and re-loaded the kernel modules, and lo! all the devices popped up like magic :D And now I wrote a small script to wait a few seconds after boot, and then unload whatever has been loaded, and then load only the ones I need. Working like a charm! Thanks to everyone, once again, for helping me to make it work. Best regards
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2ef1f6f3-3e8f-529f-33dd-3a75f86891f3>