Thank you for bearing with us, and sorry for the long wait. We have finally finished the new Raspberry Pi image. Currently, this image only supports Raspberry Pi v1. Support for v2 is in the pipeline.
The files and instructions posted here come with no warranty. You use them at your own risk. Outernet will only provide support as time allows, via this forum or GitHub issue tracker.
Support for new Outernet stream
As mentioned in one of my previous posts, Outernet data stream has been changed in a backwards-incompatible way, making all previous Raspberry Pi builds obsolete. The new image supports the new stream format.
Reduced image size and simplified updates
The new image contains a single 40MB FAT32 partition containing the kernel image. This has several important consequences:
- Faster download
- No more minimum card size requirement
- Updating the entire system is as simple as dropping the new kernel image into the first partition (usually visible to your computer) without having to write the whole image again
- More space for storage
Despite the size, the ORx system will automatically expand to take up the entire card on first boot, so no space is wasted. You can use as large a card as you wish to increase the storage capacity.
Downside is that the kernel and root filesystem needed to be slimmed down to bare essentials. There is no package system, no build tools, etc. In other words, the system is no longer as easily customizable as before.
On first boot, you will see the new setup wizard, which will guide you through basic system setup, including administrator account creation and tuner settings.
No more TVHeadend
The new image includes a version of Librarian that provides the tuner configuration interface with convenient presets for our existing transponders and C-band support (China).
Enhanced hardware support
The new image includes drivers and firmware for several satellite tuners and wifi devices.
Image incldues the drivers for the following DVB tuners:
- Pinnacle PCTV USB 2.0 DVB-S/S2
- Geniatech HDStar
- Pinnacle 400e USB 2.0 DVB-S
- Opera USB 2.0 DVB-S
- DVBWorld USB 2.0 DVB-S
- TeVii USB 2.0 DVB-S/S2
- Prof USB 2.0 DVB-S/S2
- Azurewave AZ6027 USB 2.0 DVB-S/S2
- Technisat USB 2.0 DVB-S/S2
- DVBSky USB 2.0 DVB-S
Please note that we do not have the ability to obtain and/or test all those devices. The devices we have tested are:
- Pinnacle PCTV 461e*
- Geniatech HDStar SU3000 v3.0
We would appreciate information about any working or non-working hardware you run into.
[*] PCTV 461e may have issues on model B (not model B+)
Drivers for the following USB wifi chipsets are included:
- Realtek 8187
- Realtek 8187B
- Realtek 8192C
- Realtek 8712U
- Realtek 8712SU
- Realtek 8188EU
- Atheros AR5008
- Atheros AR5523
- Atheros AR6003
- Atheros AR6004
- Atheros AR9001
- Atheros AR9002
- Atheros HTC (AR9271)
- Atheros AR1000 family (IEEE 802.11ac)
- Qualcomm Atheros WCN3660 and WCN3680
- Ralink rt2500
- Ralink rt2501
- Ralink rt27xx
- Ralink rt28xx
- Ralink rt29xx
- Ralink rt33xx
- Ralink rt3573
- Ralink rt53xx
- Ralink rt28xx with unknown chipset
- Ralink rt8192e
As with DVB equipment, we could not test all supported chipsets. Here is a list of devices we have tested, and the results of testing:
- Tenda W311MI (Ralink 5370 chipset), works with AP mode
- TP-Link TL-WN722M (Atheros AR9271 rev2 chipset), works with AP mode
- Edimax EW-7188Un (Realtek 8192CU chipset), works, but AP operation unreliable
- No name Realtek 8188E chipset, does not work as AP
Again, information about working and non-working hardware is appreciated.
Creating the SD card
For now, please follow the instructions found here (skip Obtaining the image file section). We will update the instructions in the coming weeks.
The username and password for SSH access are both
outernet. Currently, the password cannot be changed (it will be reset on boot).
- Currently, IS10 cannot be used with this image.
- PCTV 461e may have issues receiving on model B (currently looking into the issue)
- Booting with PCTV connected results in kernel error on model B (not model B+, workaround: connect PCTV after boot)
- Wired network configuration fails on boot on model B (workaround: manual network configuration)
What about Raspbian and Arch Linux ARM?
This image marks the end of support for Raspbian and Arch Linux ARM distributions for Raspberry Pi. Having said that, if anyone wants to continue using these distributions (or any other distribution on Raspberry Pi), we are available on this forum to answer questions and provide assistance.
Where are the sources?
The sources are currently being cleaned up and documented. Once that is complete, they will be published online.