LeMedia

Summary

LeMedia in the LeMaker archive refers to older media-centre images and the notes that go with them. If you are trying to install, recover, or check one of those images now, the useful part is the process, not nostalgia.

Start with the download itself. Verify it, flash it carefully, boot on stable power and known-good storage, then run a few checks so you can tell whether the fault sits with power, storage, networking, or the image.

Who this is for

This page is for people installing or recovering LeMedia images, and for anyone returning to older downloads who needs a repeatable way to confirm that a board actually boots cleanly.

What you'll do

• Check the image file before flashing anything.
• Write it to known-good storage and confirm the partitions appear as expected.
• Boot with Ethernet and the fewest peripherals possible.
• Capture logs early and keep a baseline boot report.
• Use a troubleshooting checklist that starts with power, storage, and networking.

What LeMedia is (neutral)

In the LeMaker archive, LeMedia refers to a set of images, builds, and related notes for media-oriented setups. The contents change from release to release, so treat each file as a specific artefact: verify it, flash it safely, and note exactly which image you used.

Quick checklist

• A stable PSU and cable. Random resets usually start there.
• A known-good SD card or other storage device, plus a reliable writer.
• An Ethernet cable for the first boot, which is the safer default.
• An optional serial console adapter for recovery and early boot logs.
• The image file from the downloads hub or mirror.
• A checksum, or a published hash, to confirm the download.
• Spare storage for quick A/B testing.

LeMedia Status for Banana Pi/Pro

sudo apt update
sudo apt install kodi kodi-peripheral-joystick
# Configure Kodi to start at boot if desired

Steps / guidance

1. Find the image via internal links. Use the downloads hub, and if you need a direct directory view use the internal mirror.
   • Downloads hub
   • Mirror (downloads directory)
2. Verify integrity before flashing.

   sha256sum lemedia-image.img.xz
   sha256sum lemedia-image.img

3. Flash to storage and confirm it was written to the correct device.

   lsblk
   # Confirm the SD card size and device name before writing
   lsblk

4. Boot with minimal peripherals. Power, storage, Ethernet. If something fails, do not change multiple things at once.
5. Establish access and capture logs early.

   uname -a
   ip a
   lsblk
   journalctl -b -p err | tail -n 120
   dmesg --color=never | tail -n 120

6. Once stable, update and reboot once under supervision. Keep a console open. After reboot, repeat the verification checks.

Verification checks

Use these to confirm the system is healthy. Pick at least two.

lsblk
ip a
dmesg | tail -n 50
journalctl -b -p err | tail -n 120

Troubleshooting

• No boot / stuck early: treat PSU/cable and storage as suspects; try a different SD card; re-flash from a verified download; capture serial logs if available.
• Boot loop or random resets: swap the PSU/cable; remove USB peripherals; test with minimal draw.
• Storage not detected: check lsblk; reseat or re-flash; try known-good storage.
• No network: prefer Ethernet; check ip a and ip r; confirm DNS with cat /etc/resolv.conf.
• Services failing: use systemctl --failed and journalctl -b -p err to pinpoint the failure class.

Common mistakes

• Skipping checksum verification and then debugging a corrupted flash.
• Changing power, storage, and image at the same time, which makes the result non-repeatable.
• Trying to troubleshoot networking before confirming the board is stable, with no resets and no storage errors.
• Assuming a working SD card is reliable under SBC write loads.
• Not capturing logs on the first failure and losing the evidence after reboot.

Related guides

• Downloads hub
• Boot and storage notes

Author: LeMaker Documentation Team
Last updated: 2026-01-20