Re: securelevel and embedded targets

[Lloyd Parkes <lloyd%must-have-coffee.gen.nz@localhost>]

You might find it useful to set securelevel=NO in rc.conf while you are 
on your journey. It will disable the kernel security and allow you to 
modify the GPIO configuration after the system has booted.

It's not the advised way of doing things normally, but if the only thing 
you are doing on that device is experimenting with GPIO, then it will 
make your life easier.

Obviously, once you have GPIO working you can remove the securelevel=NO 
setting.

Cheers,
Lloyd

On 19/09/22 06:45, Vincent DEFERT wrote:
> Thanks for the hint, /var/run/rc.log contains:
> gpioctl: GPIOSET: Operation not supported by device
>
> I think I'm at the beginning of a long adventure... :D
>
> On 18/09/2022 20:31, Lloyd Parkes wrote:
> > Check /var/run/rc.log just in case something useful is logged there?
> >
> > Surely the service command is "service gpio start"? I've never used it 
> > myself. Maybe you typed "service gpio onestart" by habit and there is 
> > a typo in your rc.conf? I'm sure I've done that before.
> >
> > Cheers
> >
> > On 19/09/22 06:13, Vincent DEFERT wrote:
> > > I have added my configuration to /etc/gpio.conf, appended "gpio=YES" 
> > > to /etc/rc.conf and rebooted, but /etc/rc.d/gpio isn't executed.
> > > When I run "service start gpio", it get executed, but of course with 
> > > error messages.
> > > What am I missing?