I got a bit lazy and the make image requires sudo (direct access to loop devices).
Yeah, I probably forgot to push. Will take care of it in a few minutes.
You guys should start supporting the orx-install repo again because people can get it to install on the raspberry pi2(b). I just don’t know how to get tvheadend to work (there are no good tutorials for it and it’s not user friendly enough).
TVHeadend is no longer needed. As for orx-install, we’ll consider it, though I think we’ll get RPi2 support going before we revert to the install script.
I tried the new ORxPiv0.2.7 on my system and it does not work. I get the Outernet WiFi, but cannot connect to the Librarian. The micro SD chip looks fine with all the MS level files to include the ZImage, but does not boot the Pi.
I’ve restorted the old v0.2.4 and my system works fine. Ken
Could you explain a little more, what did you make with the new ORxPiv0.2.7? What this mean: “I get the Outernet WiFI…”?
Did you used the “update” image, or used the new system image to write it based on the wiki,s howto?
I made a new SD card on linux with dd command, put on the ORxPi-0.2.7.img file and it started without any problem. After some minutes it received the first, actually broadcasted files.
Sometimes I have problem with my (cheap) card writer/reader. It has some hw problem with the Lock/write protected switch. It sense the inserted SD card as write protected, and it mounted in read-only mode. If I try to write on such a config with the dd command the image file, it “made”, send a message, that the card is ro mounted, but it didnot write anything to the card. Ofcourse, from such an “update” it canot boot.
t.janos
Lets say I do want to use raspbian… Which packages should I install?
(If this needs a new topic, I will gladly switch.)
Compiling the different packages individually on the system should be eaiser than a kernel.
I used the Wiki procedure to write a brand new SD micro using the Win32 Disk Imager as usual. This the same procedure I used to create the older OPxPIv0.2.4 SD micro which has worked fine for a long time (with the exception of the change Branko made to the Galaxy 19 transponders). Ken
Forgot to mention - - once the Pi boots up, I use Firefox to navigage to the Outernet WiFi gateway 10.0.0.1. My browser can’t connect to what used to be the Librarian. Ken
How do you know that your RPi dont have boot? If you switch on the power on RPi, do you see something happen on its LEDs?
If I understand well, you dont use ethernet connection, but use the wifi to try to connect into it.
Have you any possibility to connect to the RPi a hdmi monitor and a keyborad, and check on it the boot/init process?
Can you SSH into your Pi? If so, please check that Librarian is running with ps ax | grep python | grep -v grep. If Librarian is not running, the next step would be to run it manually to see what the issue is:
sudo python -m librarian.app --conf /opt/orx/librarian.ini
If it is having problems coming up, it should show some error messages.
branko:
Just repointed my dish (was on a tripod and blew over). I have loaded 0.2.7 and it is working great - downloading files as I write this. As always, the issues are finding the satellite.
Once you have struggled through the process of ensuring you have the correct LNB, the correct skew on the LNB and the antenna pointed in the correct direction, some slow scanning back/forth and up/down on the antenna does the trick. I am still thinking of how to ensure that DIYers have access to some good pointing info, and the correct tools to locate the satellite.
Ok - now, the question. I see that the status pages shows 5 (oops, now 3) active devices. How can I tell if I am one of those devices? I presume I can see something in the logs that shows I am ‘calling home’ to inform you my system is connected.
Cheers,
Brian
You can look at the system log for lines that contain ‘outernet.monitor’.
OK - I see lots of outernet.monitor:connect to socket messages, so it looks like my connection messages are getting through.
Cool!
Cheers,
Brian
Connect to socket messages mean that the monitoring daemon has connected to ONDD socket to collect the data. This happens approximately once every minute. Once every 5 minutes, the daemon will attempt to transmit the collected data. These are usually ‘Transmitting’ messages.
1 Like
Yes, saw the transmission messages:
Sep 7 22:37:19 orxpi user.info outernet.monitor: Transmitting buffered data
Sep 7 22:37:19 orxpi user.info outernet.monitor: Transmission complete, claring local buffer
Spelling error in the code? Claring for clearing? (there is a correction that should be at the BOTTOM of your code bug list!)
Cheers,
Brian
PS: Keep up the good work!
I should have said the previous screen reflects the ORxPiv0.2.4
Following is a screen picture of the ORxPiv0.2.7 boot up.
I can’t get past the last line of the boot up routine. I have made an image on an 8 Gbit and 64 Gbit SD chip and they both perform the same. Ken
From your screen picture it can see the last messages of the init process and the login prompt.
It seems me, your ethernet interface dont come up, and havenot configure. This is the message, referred to this:
–> …eth0:hardware isnot capable of remote wakeaup
Starting udhcp daemon, but dont find server on the ethernet and finally gave up:
–> ifplugd: FAIL
But the wlan interface have configuration… I dont know is it correct or not. This message reffered to this:
–> interface wlan already configure
It seems, this configure process has some problems, it can see this form the next two messages:
–> dnsmasq: FAIL
–> hostapd: FAIL
I dont know too much about the details of the hostapd script, but it seems, if dont find a correct configured wlan0 interface, it dont run and configure the wifi AP mode, consequently you will not access to the system on wifi…
Another problem is the DVB-S2 device. Maybe it has correst config, but it need to access to the web setup page and fill the sat data to make the ondd config. If it will be finished, maybe the ondd will restart. In this moment this is the case:
–> ondd: FAIL
On your second picture it breaks the log messages when the udhcp try to get ip address to the eth0 interface.
It is not easy to make a remote diagnose. Without network connection you have limited possibilities to document the error messages. I propose to login on the “console”, using an usb keyboard, (login:outernet/pwd:outernet) and check the init log, it is the dmesg output. You can use the less or more command to read it page-by-page:
dmesg | less
You can try to take more attentions to the messages about the config of the wlan0 interface.
You can check its actual status on the console with the
ifconfig
or the
iwconfig command
If on this system with this wifi interface the older ORx system is working, it seems, there exists only a temporaly error.
Thank you for the suggestions. I’ll do what you suggest and report back later.
It still puzzles me that I am using the same Image file everybody else is using so successfully, and mine won’t work. More later. Ken
Still no luck here. I wonder if Branko has any suggestions? Why me not working! Right! Ken