0

It seems that right after local-fs.target doesn't work. Any idea what prevents it from working early in the boot process?

Improve this question
4
  • Does it spit out any errors (e.g. in journalctl) that might point towards what's missing?
    – Aurora0001
    Commented Jan 19, 2018 at 20:22
  • Unfortunately it doesn't say much, except that my disableusb script (I placed the camera stuff there as a test) failed to start. Then it just hangs, it will never get to the serial console login, so I have to power off, put the card in my pc and comment out the camera line there. Lucky for me, I can access (r/w) file systems from my Windows machine, or else it would really suck :)
    – Radu
    Commented Jan 19, 2018 at 21:05
  • unclear what are you asking
    – Chetan Bhargava
    Commented Jan 24, 2018 at 17:00
  • You need to provide more details: the exact command that fails, the error messages (have you tried raspistill blabla 2>&1 >error.log?), relevant details about your boot process.
    – Dmitry Grigoryev
    Commented Jan 29, 2018 at 14:58

1 Answer 1

Reset to default
0

I found the problem, by manually starting the script after the log in. The camera cable moved a bit and I was getting an error, and for some reason things didn't continue after that. Now it works ok.

Improve this answer
1
  • Please accept your own answer with a click on the tick on its left side. Only this will finish the question and it will not pop up again year for year.
    – Ingo
    Commented Mar 2, 2020 at 13:06

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.