- ryang2678 (Decatf)
A random MAC address is generated by the kernel at each boot. This is because the smsc9500 Ethernet device does not have a valid mac address stored in EEPROM. To set a consistent MAC address, create the file
/etc/udev/rules.d/99-mac-address.rules with the following udev rule.
ACTION=="add", SUBSYSTEM=="net", KERNEL=="eth0", RUN+="/sbin/ip link set dev %k address f6:23:f0:42:98:cf"
- The Ouya uses a BCM4330 radio chip for wifi and bluetooth. The downstream and mainline kernel use the same wifi firmware. The firmware shipped with the device is the only known firmware to work with the Ouya. The BCM4330 firmware in
linux-firmwaredoes not work.
- Two later releases (the completely white special edition and completely black 2nd generation) allegedly use a BCM4334 chipset. This needs to be implemented and tested at a future date.
- Currently we avoid flashing directly to the device as a corrupted kernel would irreversibly brick the Ouya due to the locked bootloader. We use a tool called Ouya BootMenu (source) that allows us to run the postmarketOS kernel through a kexec method. This implements an extra failsafe to prevent bricking and in theory allows dualbooting and kernel development.
The eMMC storage on mainline cannot run at 1.8V DDR mode even though it does on the downstream kernel. Attempting to run at this mode leads to data corruption. The device tree is configured to run the eMMC storage at 3.3V High Speed mode.
Despite this, the eMMC storage benchmarks the same on mainline as on the downstream kernel.
$ hdparm -t /dev/mmcblk1 /dev/mmcblk1: Timing buffered disk reads: 127 MB in 3.02 seconds = 43021 kB/s
On the mainline kernel, display resolutions above 1280x720 are glitchy. The GPU is dependent on memory bandwidth but EMC scaling is not implemented in mainline. The Ouya bootloader sets the memory to 400 Mhz. Higher display resolutions work a bit better when the memory is set to 800Mhz but it is still glitchy.
- Splash screen doesn't appear
- Hildon doesn't work?
- USB booting needs to be tested
How to enter flash mode
1. Connect Ouya to PC
adb reboot recovery to enter recovery (or
adb reboot bootloader to enter bootloader for fastboot commands)
2. Turn on Ouya, then press the power button many times until it scrolls to Bootloader, and then wait until the boot menu disappears.
3. Run the following using pmbootstrap:
$ pmbootstrap init $ pmbootstrap install --no-fde $ pmbootstrap export $ pmbootstrap flasher flash_rootfs
4. Reboot Ouya, then press the power button many times until it scrolls to Recovery, and then wait until CWM appears.
6. Using CWM menu options, mount /data partition.
7. Copy postmarketOS boot.img to /sdcard as altboot.img:
$ adb push /tmp/postmarketOS-export/boot.img-ouya-ouya /sdcard/altboot.img
8. Reboot Ouya, then press the power button many times until it scrolls to Alternate Boot, and then wait until postmarketOS appears.
Using data partition as rootfs
It is much more usable to flash rootfs to the data partition which is around 5.7GB in size.
Flashing to the data partition
Specify the partition to flash rootfs to with the
$ pmbootstrap flasher flash_rootfs --partition userdata
$ adb push /tmp/postmarketOS-export/boot.img-ouya-ouya /system/boot.img
Updating the kernel
apk package manager updates the kernel package (e.g.
linux-ouya-ouya-mainline) then the
boot.img will be regenerated with the new kernel. Run the following commands on device to install the updated
$ mkdir /system $ mount /dev/mmcblk1p3 /system $ cp /boot/boot.img-ouya-ouya /system/boot.img