Volunteers wanted for testing the 0.2.6 ORxPi image


#1

With some delay, here is the new ORxPi image. Since I moved meanwhile, and I don’t have the dish on me right now, I would like to ask for some help from the volunteers. If you have an Outernet’s Raspberry Pi setup (or just a Raspberry Pi and a spare USB DVB-S/S2 tuner), please give this a spin:

http://archive.outernet.is/images/ORxPi/0.2.6/

To create SD card: https://wiki.outernet.is/wiki/ORxPi#Creating_the_bootable_SD_card
To update existing ORxPi (not Raspbian): https://wiki.outernet.is/wiki/Updating_ORxPi

The new image contains the new restyled interface that you can find in the online demo, and the monitoring script that submits signal monitoring data to the status page.


#2

Hmmm…maybe the problem is in my devices.
I put here part of the messages log.
It dont start, if I plug in the usb the PCTV receiver.
It come up witout it, I call in the browser the web interface, fill the setup pages. At the sat config I plug the PCTV receiver, it seems, it is OK, save the config for ondd.
In the next part of the log it seems, it recongizes the PCTV receiver, but dont find the ondd config, see in this line:
–> Aug 19 13:36:45 orxpi user.err ondd: [main] Unable to load config: /opt/orx/ondd.conf (null)

Later disconnect the tuner, and drop the ethernet too and hang up.


Aug 19 13:36:43 orxpi user.info kernel: [ 248.357805] usb 1-1.2: new high-speed USB device number 5 using dwc_otg
Aug 19 13:36:43 orxpi user.info kernel: [ 248.458995] usb 1-1.2: New USB device found, idVendor=2013, idProduct=0258
Aug 19 13:36:43 orxpi user.info kernel: [ 248.463379] usb 1-1.2: New USB device strings: Mfr=3, Product=1, SerialNumber=2
Aug 19 13:36:43 orxpi user.info kernel: [ 248.467698] usb 1-1.2: Product: PCTV 461
Aug 19 13:36:43 orxpi user.info kernel: [ 248.471940] usb 1-1.2: Manufacturer: PCTV
Aug 19 13:36:43 orxpi user.info kernel: [ 248.476114] usb 1-1.2: SerialNumber: 0011317095
Aug 19 13:36:43 orxpi user.info kernel: [ 248.497335] media: Linux media interface: v0.10
Aug 19 13:36:43 orxpi user.info kernel: [ 248.515256] Linux video capture interface: v2.00
Aug 19 13:36:43 orxpi user.info kernel: [ 248.543080] em28xx: New device PCTV PCTV 461 @ 480 Mbps (2013:0258, interface 0, class 0)
Aug 19 13:36:43 orxpi user.info kernel: [ 248.547398] em28xx: DVB interface 0 found: isoc
Aug 19 13:36:43 orxpi user.info kernel: [ 248.552640] em28xx: chip ID is em28178
Aug 19 13:36:43 orxpi user.info kernel: [ 248.939461] em28178 #0: EEPROM ID = 26 00 01 00, EEPROM hash = 0x663c7aa0
Aug 19 13:36:43 orxpi user.info kernel: [ 248.943801] em28178 #0: EEPROM info:
Aug 19 13:36:43 orxpi user.info kernel: [ 248.948054] em28178 #0: microcode start address = 0x0004, boot configuration = 0x01
Aug 19 13:36:44 orxpi user.info kernel: [ 248.961067] em28178 #0: AC97 audio (5 sample rates)
Aug 19 13:36:44 orxpi user.info kernel: [ 248.965488] em28178 #0: 500mA max power
Aug 19 13:36:44 orxpi user.info kernel: [ 248.969877] em28178 #0: Table at offset 0x27, strings=0x148c, 0x1874, 0x0a6a
Aug 19 13:36:44 orxpi user.info kernel: [ 248.975463] em28178 #0: Identified as PCTV DVB-S2 Stick (461e) (card=92)
Aug 19 13:36:44 orxpi user.info kernel: [ 248.980038] em28178 #0: dvb set to isoc mode.
Aug 19 13:36:44 orxpi user.info kernel: [ 248.984748] usbcore: registered new interface driver em28xx
Aug 19 13:36:44 orxpi user.info kernel: [ 249.016303] em28178 #0: Binding DVB extension
Aug 19 13:36:44 orxpi user.info kernel: [ 249.048231] i2c i2c-3: Added multiplexed i2c bus 4
Aug 19 13:36:44 orxpi user.info outernet.monitor: Could not connect to socket. Pausing for next attempt
Aug 19 13:36:44 orxpi user.info kernel: [ 249.108605] m88ts2022 4-0060: Montage M88TS2022 successfully identified
Aug 19 13:36:44 orxpi user.info kernel: [ 249.133416] i2c i2c-3: a8293: Allegro A8293 SEC attached
Aug 19 13:36:44 orxpi user.info kernel: [ 249.138309] DVB: registering new adapter (em28178 #0)
Aug 19 13:36:44 orxpi user.info kernel: [ 249.142993] usb 1-1.2: DVB: registering adapter 0 frontend 0 (Montage M88DS3103)…
Aug 19 13:36:44 orxpi user.info kernel: [ 249.158054] em28178 #0: DVB extension successfully initialized
Aug 19 13:36:44 orxpi user.info kernel: [ 249.162914] em28xx: Registered (Em28xx dvb Extension) extension
Aug 19 13:36:44 orxpi user.info kernel: [ 249.250107] em28178 #0: Registering input extension
Aug 19 13:36:44 orxpi user.notice hotplug.dvb: DVB frontend /dev/dvb/adapter0/frontend0 added, restarting ONDD
Aug 19 13:36:44 orxpi user.info kernel: [ 249.317710] Registered IR keymap rc-pinnacle-pctv-hd
Aug 19 13:36:44 orxpi user.info kernel: [ 249.323285] input: em28xx IR (em28178 #0) as /devices/platform/bcm2708_usb/usb1/1-1/1-1.2/rc/rc0/input1
Aug 19 13:36:44 orxpi user.info kernel: [ 249.335658] rc0: em28xx IR (em28178 #0) as /devices/platform/bcm2708_usb/usb1/1-1/1-1.2/rc/rc0
Aug 19 13:36:44 orxpi user.info kernel: [ 249.351543] em28178 #0: Input extension successfully initalized
Aug 19 13:36:44 orxpi user.info kernel: [ 249.356544] em28xx: Registered (Em28xx Input Extension) extension
Aug 19 13:36:45 orxpi user.err ondd: [main] Unable to load config: /opt/orx/ondd.conf (null)
Aug 19 13:36:45 orxpi user.info ondd[293]: [main] v2.0.0
Aug 19 13:36:45 orxpi user.info kernel: [ 250.419614] i2c i2c-3: m88ds3103: found a ‘Montage M88DS3103’ in cold state
Aug 19 13:36:45 orxpi user.info kernel: [ 250.425001] i2c i2c-3: m88ds3103: downloading firmware from file 'dvb-demod-m88ds3103.fw’
Aug 19 13:36:45 orxpi user.info kernel: [ 250.720066] i2c i2c-3: m88ds3103: found a ‘Montage M88DS3103’ in warm state
Aug 19 13:36:45 orxpi user.info kernel: [ 250.725279] i2c i2c-3: m88ds3103: firmware version 3.B
Aug 19 13:36:45 orxpi user.info ondd[293]: [main] tuning to 0 Mhz 0 KSym
Aug 19 13:36:45 orxpi user.warn ondd[293]: [main] ioctl( FE_SET_PROPERTY ) failed: (22) Invalid argument
Aug 19 13:36:45 orxpi user.warn kernel: [ 250.794960] usb 1-1.2: DVB: adapter 0 frontend 0 frequency 0 out of range (950000…2150000)
Aug 19 13:36:49 orxpi user.info outernet.monitor: Connected to socket
Aug 19 13:36:49 orxpi user.info outernet.monitor: Connected to socket
Aug 19 13:36:49 orxpi user.info outernet.monitor: Finished collecting data in 155.243997812 seconds
Aug 19 13:37:01 orxpi user.info ondd[293]: [main] tuning to 1721 Mhz 27500 KSym
Aug 19 13:37:02 orxpi user.info ondd[293]: [main] tuning to 1721 Mhz 27500 KSym
Aug 19 13:37:02 orxpi user.info ondd[293]: [main] tuning to 1721 Mhz 27500 KSym
Aug 19 13:37:03 orxpi user.info ondd[293]: [main] tuning to 1721 Mhz 27500 KSym
Aug 19 13:37:07 orxpi user.warn ondd[293]: [main] timed out waiting for PMT
Aug 19 13:37:34 orxpi user.warn kernel: [ 299.845287] ERROR::dwc_otg_hcd_urb_enqueue:505: Not connected
Aug 19 13:37:34 orxpi user.warn kernel: [ 299.845287]
Aug 19 13:37:34 orxpi user.warn kernel: [ 299.937708] NYET/NAK/ACK/other in non-error case, 0x00000002
Aug 19 13:37:34 orxpi user.warn kernel: [ 299.942925] NYET/NAK/ACK/other in non-error case, 0x00000002
Aug 19 13:37:34 orxpi user.warn kernel: [ 299.947982] NYET/NAK/ACK/other in non-error case, 0x00000002
Aug 19 13:37:35 orxpi user.warn kernel: [ 300.047880] NYET/NAK/ACK/other in non-error case, 0x00000002
Aug 19 13:37:35 orxpi user.warn kernel: [ 300.052895] NYET/NAK/ACK/other in non-error case, 0x00000002
Aug 19 13:37:35 orxpi user.warn kernel: [ 300.057761] NYET/NAK/ACK/other in non-error case, 0x00000002
Aug 19 13:37:35 orxpi user.info kernel: [ 300.063623] usb 1-1: USB disconnect, device number 2
Aug 19 13:37:35 orxpi user.info kernel: [ 300.068573] usb 1-1.1: USB disconnect, device number 3
Aug 19 13:37:35 orxpi user.info kernel: [ 300.073564] smsc95xx 1-1.1:1.0 eth0: unregister ‘smsc95xx’ usb-bcm2708_usb-1.1, smsc95xx USB 2.0 Ethernet
Aug 19 13:37:35 orxpi user.info kernel: [ 300.078605] smsc95xx 1-1.1:1.0 eth0: hardware isn’t capable of remote wakeup
Aug 19 13:37:35 orxpi user.info kernel: [ 300.088984] usb 1-1.2: USB disconnect, device number 5
Aug 19 13:37:35 orxpi user.info kernel: [ 300.094242] em28178 #0: Disconnecting em28178 #0
Aug 19 13:37:35 orxpi user.err ondd[293]: [tuner] ioctl( FE_READ_SIGNAL_STRENGTH ) failed: (19) No such device
Aug 19 13:37:35 orxpi user.err ondd[293]: [tuner] ioctl( FE_READ_SNR ) failed: (19) No such device
Aug 19 13:37:35 orxpi daemon.err ifplugd(eth0): getting interface flags failed: No such device
Aug 19 13:37:35 orxpi daemon.err ifplugd(eth0): ETHTOOL_GLINK failed: No such device
Aug 19 13:37:35 orxpi daemon.err ifplugd(eth0): can’t detect link status
Aug 19 13:37:35 orxpi daemon.err ifplugd(eth0): exiting
Aug 19 13:37:36 orxpi user.err ondd[293]: [tuner] ioctl( FE_READ_SIGNAL_STRENGTH ) failed: (19) No such device
Aug 19 13:37:36 orxpi user.err ondd[293]: [tuner] ioctl( FE_READ_SNR ) failed: (19) No such device
Aug 19 13:37:36 orxpi daemon.info ntpd[197]: Deleting interface #2 eth0, 192.168.1.110#123, interface stats: received=19, sent=19, dropped=0, active_time=226 secs
Aug 19 13:37:36 orxpi daemon.info ntpd[197]: 193.225.121.161 local addr 192.168.1.110 ->
Aug 19 13:37:36 orxpi daemon.info ntpd[197]: 193.225.190.5 local addr 192.168.1.110 ->
Aug 19 13:37:37 orxpi user.err ondd[293]: [tuner] ioctl( FE_READ_SIGNAL_STRENGTH ) failed: (19) No such device
Aug 19 13:37:37 orxpi user.err ondd[293]: [tuner] ioctl( FE_READ_SNR ) failed: (19) No such device
Aug 19 13:37:38 orxpi user.err ondd[293]: [tuner] ioctl( FE_READ_SIGNAL_STRENGTH ) failed: (11) Resource temporarily unavailable
Aug 19 13:37:38 orxpi user.err ondd[293]: [tuner] ioctl( FE_READ_SNR ) failed: (11) Resource temporarily unavailable
Aug 19 13:37:39 orxpi user.err ondd[293]: [tuner] ioctl( FE_READ_SIGNAL_STRENGTH ) failed: (11) Resource temporarily unavailable
Aug 19 13:37:39 orxpi user.err ondd[293]: [tuner] ioctl( FE_READ_SNR ) failed: (11) Resource temporarily unavailable


#3

This happens after you successfully tune in the first time, and then reboot?


#4

I put with dd the new, updated image to the sd card, and reboote. If it was the original hw setup, means puggged in the RPi-s usb the PCTV receiver, it restart automativally in loop. I wasnot able to record the dmesg appeared on the RPi console. If I unplugged the PCTV, it started up normally, get IP on eth0, and I was able to call into the browser the setup web pages. When I finished the setup, some minutes later it hang up, as you can see in the log.


#5

That sounds like something that had happened to me when I forgot to plug in PCTV’s power adaptor. Also, what kind of power does the Pi’s own PSU provide?


#6

I have good experiences with the used power unit. It consist of a small accumulator, 12 V and 5AH, with a stab unit, produced the 5 V on a USB connector.
The PCTV unit has its own, factory made, 12 V power unit.

After the last boot, the init started to reformat the SD card, beause the hang up, maybe remained some bad block on it. Repeated the setup on the web interface, it is clear, it saved the sat config.
But it can say, the weather conditions not good for test: havy clouds and rainig here. I will try the real receive next time, in better conditoins.


#7

Yeah it doesn’t sound like it’s the PSU. Has PCTV worked for you with the previous version of the firmware (0.2.4)?


#8

yes, worked fine. I have the old SD card too with the working setup.


#9

It seems, the monitor is working continuously. It can see this sequneces in the log:

Aug 19 15:35:20 orxpi user.info outernet.monitor: Collecting data
Aug 19 15:35:20 orxpi user.info outernet.monitor: Connected to socket
Aug 19 15:35:20 orxpi user.info outernet.monitor: Connected to socket
Aug 19 15:35:20 orxpi user.info outernet.monitor: Finished collecting data in 0.035551071167 seconds
Aug 19 15:35:22 orxpi user.warn ondd[283]: [main] timed out waiting for PMT
Aug 19 15:35:26 orxpi user.warn ondd[283]: [main] timed out waiting for PMT

But, because the LNB not locked, and there is no signal, it dont appeared anything on the status.outernet page.


#10

Yeah, monitoring will not do anything unless there is a lock. Reports that do not have a lock are treated as coming from unconfigured devices. It will work in the background and collect and buffer data until the first opportunity to send it out.


#11

Going to image my SD tonight and get my rig on the air tomorrow. Looking forward to seeing the new UI.


#12

You can also update an existing Pi card by dropping the zImage file from the update zip file onto its first partition (the one that already has a zImage file).


#13

Im going to create another image on a 16GB card, in preparation for my library expanding!

(keeping my working 0.2.4 card on standby, as i have a few demostrations lined up shortly.)

John


#14

That makes sense.


#15

That said, after running those commands to delete my library, i can no longer access 0.2.4…

Gonna check I started librarian…


#16

Would also be worthwhile to check the logs:

cat /var/log/librarian.log

#17

In the mean time I went out in the rain and deployed my dish. Luckily I marked the pavement where the tripod feet sit, so didnt get to wet in this british summer.

Swapped SD’s over to 0.2.6, and booted. follwed the quick start, and I have 77% signal, 0.48SNR, and lock. so all good there.

Nothing in the library (as expected) but watching for the bell to change colour!

Good job Outernet team!

Cheers

John


#18

Bell doesn’t change color on its own. Also, it’s not the bell that signals downloads. You’ll see another icon named “Updates” pop up. You’d need to be logged in to see it, though, which can be done by going to settings (cog icon).


#19

Ok, going to go check! Cheers!


Updates are coming in fast.
I see how it works; the bell notifies “users” that the “admin” has passed updates into the Library. Nice.

So how does your broadcast work? I see a file that I received weeks ago has been received again. How long will it take to get completely up to date, and does the library disregard any duplicate content?

Slick interface BTW.

Cheers


#20

The datacast (lawyers say we can’t call it ‘broadcast’) goes in a loop. Each file has an identifier that changes only when file contents change. The software in the receiver (ondd) tracks these identifiers and downloads files it sees for the first time. For each file that is downloaded, a symlink is created in /mnt/data/downloads/.cache. Currently, the only way to force a redownload is to remove that symlink. Note that whether the symlink actually points to an existing file is irrelevant.

EDIT: Forgot to mention about how long it takes to get all files. That depends. If you miss a file because of bead weather or something, you need to wait for it to come around, etc. Also, new files are added every day (twitter feeds, for example), so in theory, you can never be completely up to date. :))