Posts by Iridium

My car doesn't work - what is the problem?

Do you honestly think anyone can tell what your actual hardware is, or what LE release you are running from that post?

This *may* be related to an old bug where the network was down.

Also output of:

dmesg | paste

and

journalctl | paste

There are many models - each defined by the label on the bottom of the unit ... LS, LQ, LB, LP etc.

You'll need to use the internet to determine what chipset is used, see if Android can give you any details or get a magnifying glass out and examine the chips for any clues.

A ten second google search came up with This.

Looks like you have to take the box apart and bridge 2 contact points. Double double check that this is EXACTLY the same as your box, otherwise you might short out something else.

Please use the official alpha releases Here and see if you still have issues.

Appreciated. Thank you. I too am still using one of his/her builds.

Also output from.

dmesg|paste

journalctl|paste

Sounds like the card has become faulty. Please provide full logs and the output of

dmesg | paste  and

journalctl | paste 

I don't have an X86 machine running LE but this *should* work.

Create in /storage/.config/system.d

fstrim.service

[Unit]
Description=Run fstrim on all applicable drives

[Service]
User=root
Type=oneshot
ExecStart=/usr/sbin/fstrim -av

fstrim.timer

[Unit]
Description=Run fstrim on boot and weekly afterwards

[Timer]
OnBootSec=15min
OnUnitActiveSec=1w 

[Install]
WantedBy=timers.target

Check that is works:

systemctl start fstrim.service

If happy: Enable it

systemctl enable fstrim.timer

I assume you mean TRIM as in fstrim to "clean" SSD's.

You can use CRON with crontab -e or use a systemd timer and service

What type of RPi are you using and what is the PSU specifications?

Also output from.

dmesg|paste

journalctl|paste

Many thanks - Perfectly explained. Will certainly explain the results I have obtained.

I guess you could also increase the wait for network timeout.

So in answer to the original question, if you REALLY need to use you're own NTP server than edit ^^^ connman_main.conf to include just your NTP server. But, I can't see the point, as long as the time is set correctly.

Commenting out

#FallbackTimeservers = 0.pool.ntp.org,1.pool.ntp.org,2.pool.ntp.org,3.pool.ntp.org

Now shows 0.pool.ntp.org #3 instead of 3.pool.ntp.org.

I would have expected #1 then #2 and then #3, if all those fail then refer back to the FallbackTimeservers

It would seem that you "local" NTP server is not being found. However: Something seems odd.

I have:

ntp #1 as 0.uk.pool.ntp.org

ntp #2 as 1.uk.pool.ntp.org

ntp #3 as 0.pool.ntp.org

However, whilst #1 is used 3.pool.ntp.org is still being referenced

Ok, I'll have a look. I have pihole running and (LE9 Rpi) so I should be able to see if it is a TB issue.

What about?

Also output of:

dmesg | paste journalctl | paste

Try searching for Kodi Netflix addon.

For running LE the Odroid C2 and Vim2 are supported - the Vim2 does seem to run hot but you can get a heatsink and fan (For an extra cost).