[doveman2]

autostart.sh always runs - if your isn't doing what you expect it's almost certainly not because it isn't running, but an error in the script.

Add some "echo" statements to autostart.sh and you should see them appear in journalctl.

Check the status of the autostart service with "systemctl status kodi-autostart".

So with autostart.sh as

#! /bin/sh
(sleep 10;
rmmod dvb_usb_af9035
modprobe dvb_usb_af9035) &

"systemctl status kodi-autostart" gives:

â kodi-autostart.service - Kodi user autostart script
Loaded: loaded (/usr/lib/systemd/system/kodi-autostart.service; disabled; vendor preset: enabled)
Active: active (exited) since Thu 1970-01-01 01:00:04 BST; 45 years 11 months ago
Process: 371 ExecStart=/bin/sh -c . /etc/profile; exec /bin/sh /storage/.config/autostart.sh (code=exited, status=0/SUCCESS)
Main PID: 371 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/kodi-autostart.service

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

If I add a couple of echo commands like so:

#! /bin/sh
(sleep 10;
echo rmmod
rmmod dvb_usb_af9035
echo modprobe
modprobe dvb_usb_af9035) &

it gives

â kodi-autostart.service - Kodi user autostart script
Loaded: loaded (/usr/lib/systemd/system/kodi-autostart.service; disabled; vendor preset: enabled)
Active: active (exited) since Thu 1970-01-01 01:00:04 BST; 45 years 11 months ago
Process: 371 ExecStart=/bin/sh -c . /etc/profile; exec /bin/sh /storage/.config/autostart.sh (code=exited, status=0/SUCCESS)
Main PID: 371 (code=exited, status=0/SUCCESS)
CGroup: /system.slice/kodi-autostart.service

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

If I "sh .config/autostart.sh" I get:

: not found# .config/autostart.sh: line 6:
rmmod
is not currently loaded_usb_af9035
modprobe

and the cmdline prompt only re-appears when I press enter.