LeMaker Guitar

Illustration for LeMaker Guitar documentation

Summary

LeMaker Guitar documentation in the wiki is primarily archival. This page turns it into a practical hub: what to prepare, what to verify on first boot, and where to look next for login, configuration, and boot notes.

The key outcome is a stable bring-up: if you can boot reliably, keep access, and capture a baseline report, you can iterate on software changes without losing the ability to recover.

Who this is for

LeMaker Guitar owners doing first boot, developers validating images, and anyone returning to older notes who needs a predictable checklist and troubleshooting flow.

What you’ll do

  • Prepare stable power and known-good storage.
  • Boot with minimal peripherals and establish access.
  • Confirm network, storage, and service health.
  • Capture a baseline boot report and keep it.
  • Use internal links for deeper configuration and recovery topics.

Quick checklist

  • Stable PSU and cable.
  • Known-good storage (and a spare for testing).
  • Ethernet for first boot (recommended).
  • Optional: serial console adapter for recovery.
  • Minimal peripherals on first boot.

Board specifications (quick reference)

  • SoC: Actions S500 quad-core ARM Cortex-A9 (1.0 GHz)
  • RAM: 1GB DDR3
  • Storage: microSD slot, optional eMMC module
  • Network: 10/100 Ethernet
  • USB: 4x USB 2.0 host ports
  • Video: HDMI 1.4 (1080p), composite video
  • Audio: HDMI audio, 3.5mm jack
  • GPIO: 40-pin expansion header (compatible with many Raspberry Pi HATs)
  • Power: 5V 2A via Micro-USB or barrel connector
  • Form factor: Credit card size, similar to Raspberry Pi

Steps / guidance

1. Boot with minimal peripherals

For first boot, use only essential components to isolate variables:

  • Power: 5V 2A power supply via Micro-USB or barrel connector. Use a quality supply with short, thick cable to avoid undervoltage.
  • Storage: microSD card (Class 10 or UHS-I recommended) or eMMC module. Ensure card is known-good; cheap cards cause intermittent failures.
  • Network: Ethernet cable connected to router/switch for DHCP.
  • Display (optional): HDMI display for boot messages and local console.

Do not attach USB hubs, WiFi dongles, or high-current peripherals on first boot. Add them after verifying the baseline system is stable.

2. Establish access method

Before making changes, ensure reliable login access:

  • SSH over Ethernet (recommended): Check router DHCP list for board IP. SSH with default credentials (root/lemaker, pi/raspberry, or check image documentation).
  • Local console (HDMI + keyboard): Connect display and keyboard. Login prompt appears after boot completes.
  • Serial console (optional but recommended): Connect 3.3V USB-to-TTL adapter to debug header (TX, RX, GND). Use 115200 baud rate. Essential for bootloader debugging.

Test access with a simple command: uname -a.

3. Confirm system identity and connectivity

Verify the system matches expectations and network is functional:

uname -a                    # Kernel version and architecture (armv7l expected)
cat /proc/cpuinfo | head -n 20  # CPU model (Actions S500, 4 cores)
grep MemTotal /proc/meminfo # Total RAM (1GB expected)
ip a                        # Network interfaces and IP addresses
ip r                        # Routing table (should show default gateway)
ping -c 3 8.8.8.8          # Test external connectivity
cat /etc/resolv.conf       # Verify DNS nameservers

4. Confirm storage layout and health

Verify storage is detected correctly and filesystems are mounted without errors:

lsblk           # List block devices (microSD typically shows as mmcblk0)
blkid           # Filesystem UUIDs and types
df -h           # Mount points and free space
dmesg | grep mmc  # Check for SD card errors or performance warnings

If you see I/O errors, read failures, or "mmc0: error" messages, replace the storage immediately.

5. Capture a baseline boot report

Save this output to a text file on your workstation. Compare against it after updates or configuration changes:

uname -a                          # Kernel version
cat /proc/cpuinfo | head -n 20   # CPU details
ip a                              # Network configuration
ip r                              # Routes
systemctl --failed               # Failed services
journalctl -b -p err | tail -n 120  # Boot errors
dmesg | tail -n 80               # Recent kernel messages
lsblk                             # Storage layout

Name the file guitar-baseline-YYYY-MM-DD.txt and store safely.

6. Update system under supervision

Run a system update with console access available. Do not update headless without a recovery plan:

sudo apt update
sudo apt -y full-upgrade
sudo reboot

After reboot, repeat verification checks and compare to baseline. If something breaks, you can identify what changed.

Verification checks

Pick at least two after changes to storage, kernel, or networking:

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

Troubleshooting

Board does not boot or shows unstable boot

  • Symptoms: Power LED on but no display output; random resets; boot hangs at logo or kernel messages.
  • Common causes: Weak power supply, failing SD card, corrupted boot partition, wrong image for board.
  • Steps:
    1. Swap power supply and cable. LeMaker Guitar requires 5V 2A minimum. Use a quality supply with short, thick cable.
    2. Try a different microSD card. Flash from a freshly downloaded and verified image.
    3. Remove all USB peripherals except keyboard (if using local console).
    4. Connect serial console to capture bootloader and kernel messages. Look for errors or panics.
    5. Verify you downloaded the correct image for LeMaker Guitar (not Banana Pi or other board images).
    6. Check SD card for visible damage or corrosion on contacts.

Network access failure

  • Symptoms: No IP address; eth0 shows no carrier; DHCP lease not appearing in router.
  • Common causes: Ethernet cable fault, interface not brought up, driver issue, DHCP server not responding.
  • Steps:
    1. Check link LEDs on Ethernet port. Try different cable and router/switch port.
    2. Run ip a. If eth0 shows "state DOWN" or "NO-CARRIER", check cable connection.
    3. Bring interface up manually: sudo ip link set eth0 up.
    4. Request DHCP lease: sudo dhclient eth0.
    5. Check for default route: ip r should show "default via...".
    6. Verify DNS: cat /etc/resolv.conf should list nameservers. Test with ping -c 3 8.8.8.8.
    7. Review network logs: journalctl -u NetworkManager or dmesg | grep eth.

Filesystem errors or corruption

  • Symptoms: Read-only filesystem; I/O errors in dmesg; boot fails with fsck errors; random file corruption.
  • Common causes: Failing SD card, power interruptions during writes, undervoltage, cheap/counterfeit media.
  • Steps:
    1. Replace SD card immediately. Use a known-good, name-brand card (SanDisk, Samsung, Kingston).
    2. Re-flash image and verify checksum before flashing.
    3. Ensure power supply is stable (5V 2A). Measure voltage at board if possible; should not drop below 4.75V.
    4. Mount card on another Linux system and run filesystem check: sudo fsck.ext4 -f /dev/sdX2 (adjust partition).
    5. Check dmesg for SD card errors: dmesg | grep -E "mmc|blk|I/O".

Services fail to start

  • Symptoms: Boot completes but expected functionality missing; systemctl shows failed units.
  • Common causes: Misconfiguration, missing dependencies, network not ready before service starts.
  • Steps:
    1. List failed services: systemctl --failed.
    2. Check specific service status: systemctl status SERVICE_NAME.
    3. Review service logs: journalctl -u SERVICE_NAME -n 100.
    4. If service requires network, verify network is up: ip a, ip r.
    5. Restart service after fixing config: sudo systemctl restart SERVICE_NAME.
    6. Enable service to start on boot: sudo systemctl enable SERVICE_NAME.

USB devices not detected or unstable

  • Symptoms: USB devices disconnect randomly; lsusb does not show device; dmesg shows enumeration errors.
  • Common causes: Power supply insufficient for USB device current draw, USB port or cable fault, driver issue.
  • Steps:
    1. Check dmesg after plugging device: dmesg | tail -n 50. Look for "new USB device" or error messages.
    2. Try different USB port. Guitar has 4 USB 2.0 ports; test each one.
    3. If device draws >500mA, use a powered USB hub.
    4. Verify power supply is adequate. USB device current adds to board consumption.
    5. Test device on another Linux system to confirm it works (not faulty hardware).

Common mistakes

  • Adding many peripherals on first boot and losing reproducibility.
  • Debugging software without swapping PSU/cable and storage when symptoms are inconsistent.
  • Changing multiple variables at once (image + network + kernel).
  • Running headless updates without a recovery path.

FAQ

What operating systems are supported on LeMaker Guitar?

LeMaker Guitar supports Linux distributions (Debian, Ubuntu, Arch) and Android. Images are typically board-specific due to the Actions S500 SoC. Check the LeMaker downloads page for available images. Not all Raspberry Pi images are compatible.

Can I use Raspberry Pi HATs with LeMaker Guitar?

Many HATs work due to the 40-pin GPIO header compatibility, but not all. The pinout is similar but not identical. Verify GPIO pin assignments and voltage levels (3.3V) before connecting. Some HATs require device tree modifications.

Does LeMaker Guitar have WiFi or Bluetooth?

No onboard WiFi or Bluetooth. Use USB WiFi dongles (check driver compatibility) or USB Bluetooth adapters. The board has 4 USB 2.0 ports for peripherals.

What power supply do I need?

5V 2A minimum via Micro-USB or barrel connector (5.5mm x 2.1mm center positive). Higher current supplies (2.5A, 3A) provide margin for USB peripherals. Weak supplies cause random resets and instability.

Can I boot from USB or SATA?

No. LeMaker Guitar boots from microSD card or optional eMMC module only. USB boot is not supported by the bootloader. Some users have achieved rootfs on USB with boot partition on SD card.

How do I enable serial console?

Connect a 3.3V USB-to-TTL adapter to the debug header (typically near the GPIO header). Connect TX (adapter) to RX (board), RX (adapter) to TX (board), and GND to GND. Do NOT connect VCC. Use 115200 baud, 8N1. Consult board pinout for exact pins.

Why does my board reset randomly?

Almost always caused by undervoltage (weak power supply or thin/long cable) or a failing SD card. Swap power supply first, then try a new SD card. Measure voltage at the board if possible (should stay above 4.75V).

Can I overclock the LeMaker Guitar?

Overclocking is possible but not officially supported. The Actions S500 runs at 1.0 GHz stock. Overclocking requires bootloader or device tree changes and adequate cooling. Stability is not guaranteed; use at your own risk.

Where can I find GPIO pinout?

Check the LeMaker Guitar hardware manual or schematic. The 40-pin header follows a layout similar to Raspberry Pi but with SoC-specific differences. GPIO numbering may differ from physical pin numbers. Use gpioinfo to list available GPIO lines.

Where can I get help if I am stuck?

Check the docs and search for LeMaker Guitar topics. For kernel or driver issues specific to Actions S500, search Linux kernel mailing lists or Actions Semiconductor documentation.

Concrete example (first boot checks)

uname -a
ip a
systemctl --failed
journalctl -b -p err | tail -n 80

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