Hotfix firmware 2.3.000 for Lighthouse and ORx

This release addresses issue with updating pre-2.0.000 boxes to the new release and having to reboot twice after update.

It also adds two new tools:

facres command resets the device to factory settings, and removes any downloads and databases. It has no additional options so simply:

sudo facres

Another command that has been added is service, which is used to start/stop/restart system services. Behind the scenes it finds the correct init script so it’s equivalent of calling init scripts. Example:

sudo /etc/init.d/S91librarian restart


service librarian restart


As usual, Lighthouse users will receive the update as part of the datacast, so there’s no need to do anything unless you’re in a hurry.

1 Like

I baked a fresh SD card with ORx hotfix 2.3.000 firmware. Started the Pi with both HDStar tuner and WiFi adapter attached. Librarian gets started, configured the librarian interface settings and got the signal lock.

Currently, the UI is showing 4 carousels but all of them are showing the downloaded percentage as 100%. But only the file names of carousel 1 and 2 are changing. I can’t see any downloaded files, pages or tweets in the librarian UI.

Also here is the part of the FSAL


[1970-01-01 00:01:31 (+0000)] DEBUG Migration version for fsal.migrations.fs is 0.0
[1970-01-01 00:01:31 (+0000)] DEBUG Finished migrating to 01_00_add_filesystem_tables
[1970-01-01 00:01:31 (+0000)] DEBUG Finished migrating to 02_00_add_path_index
[1970-01-01 00:01:31 (+0000)] DEBUG Finished migrating to 03_00_add_events_table
[1970-01-01 00:01:31 (+0000)] INFO FSAL server started.
[1970-01-01 00:01:31 (+0000)] DEBUG Fetched 0 events from ONDD
[1970-01-01 00:01:32 (+0000)] DEBUG DB refreshed in 23.965 ms
[1970-01-01 00:01:41 (+0000)] DEBUG Fetched 0 events from ONDD
[1970-01-01 00:01:51 (+0000)] DEBUG Fetched 0 events from ONDD
[1970-01-01 00:02:01 (+0000)] DEBUG Fetched 0 events from ONDD
[1970-01-01 00:02:11 (+0000)] DEBUG Fetched 0 events from ONDD
[1970-01-01 00:02:21 (+0000)] DEBUG Fetched 0 events from ONDD
[1970-01-01 00:02:31 (+0000)] DEBUG Fetched 0 events from ONDD

This is the service status.

This is the same thing I am seeing - tried a fresh SD card on a Pi2 a couple of times.

I restarted the Pi several times, but it doesn’t get the signal lock.

Also here are the results for new commands.

ORxPi2 v2.3.000 | [email protected]:~> service fsal restart
Stopping fsal: OK
Starting fsal: OK
ORxPi2 v2.3.000 | [email protected]:~> service ondd restart
Stopping ondd: rm: can't remove '/var/run/': No such file or directory
Starting ondd: OK
ORxPi2 v2.3.000 | [email protected]:~> service librarian restart
Stopping librarian: OK
Starting librarian: OK
ORxPi2 v2.3.000 | [email protected]:~> service librarian restart
Stopping librarian: OK
Starting librarian: OK
ORxPi2 v2.3.000 | [email protected]:~>

Just saw this thread :smiley:

Here on Galaxy 19 for the last week all I have been getting are new Tweets (the last ones received yesterday had many football pictures), and MP3 downloads of The Adventures of Sherlock Holmes, Mark Twain, and the last few Count of Monte Christo chapters. Ken

This means that ONDD was down, otherwise it would have said “Stopping ondd: OK”.

That is correct, those are the files you would have received in the past week. There should be a weekly bin going up today as well.

I’ve been running both my Lighthouse and ORxPi on 2 separate linear feeds from my quad LNB on Galaxy 19, and am receiving similar downloads. Getting the ORxPi running, however, has always been more challenging than using the Lighthouse.

Aren’t both devices fundamentally the same except for the integration of components into the single Lighthouse box? Are we running different Linux versions? How would you explain the differences? Ken

They use a completely different kernel due to Lighthouse being an integrated device with a known and limited set of hardware support targets, but the client software (ONDD, Librarain) is identical.

Hardware-wise, the main difference is that the tuner is connected via a USB hub which has been problematic from the start. It would really require digging into the logs and, more importantly, keeping an eye on it during real-life operation, which is a bit beyond what we can do for each and every set-up in the wild (which is exactly why ORx is called a DIY receiver).

That said - - let me unload a “broad-side shot”.

All of us who have been so diligently working with Outernet (having built our own DIY ORxPIs) to prove the concept and figure out the technical problems with your fine engineering staff, might want to request a redirection on corporate’s part. Syed, perhaps it is time to retire the ORxPi who’s job is done. Concentrate on the Lighthouse and the new DIY L-band box that I would like to build.

Oh - - I hear the cry from all of my fellow DIYers :cry: but . . .

Find out how many of us there are, and replace our ORxPis with one of your Lighthouses, and let’s move on. I bought mine at your store at full price, but perhaps you can incentivize others to migrate! :grinning: Ken

There are cases like this one where having an independent solution would be desirable. Outernet is a US company, so some countries cannot be served due to political constraints.

I see your point. Let’s see what others think. Ken