SD Card boot failure with ESCPOS printer connected via USB

Open
#1,408 13 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
linux, raspberry-pi
Domain
embedded-iot, operating-systems

Research direction

Reproduce the boot failure on a Pi4B with the ESCPOS printer connected before startup, using the reported 2020-02-13 Raspberry Pi reference image, firmware version 6379679d, and kernel 4.19.118-v7l+. Compare it with booting first and connecting the printer afterward; investigate the boot path using the available system details, noting that the report includes no logs. Done means the Pi boots normally with the printer already connected.

Written by the indexing model from the issue text.

Description

Is this the right place for my bug report?
I believe so.

Describe the bug
Pi4B won't boot with ESCPOS printer connected via USB. Printer works fine if connected straight after the boot.

To reproduce
Plug the ESCPOS printer to one of the USBs and start Pi4B.

Expected behaviour
Should boot normally.

Actual behaviour
Hung with black screen. Red light on. No green light activity.

System

  • Which model of Raspberry Pi? e.g.
    Pi4B

  • Which OS and version (cat /etc/rpi-issue)?
    Raspberry Pi reference 2020-02-13
    Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, 5f884374b6ac6e155330c58caa1fb7249b8badf1, stage4

  • Which firmware version (vcgencmd version)?
    Jun 1 2020 13:23:40
    Copyright (c) 2012 Broadcom
    version 6379679d1ec6a8c746d7e77e015f5b56b939976f (clean) (release) (start)

  • Which kernel version (uname -a)?
    Linux terminalrpi 4.19.118-v7l+ #1311 SMP Mon Apr 27 14:26:42 BST 2020 armv7l GNU/Linux

Logs
None.

Additional context
If printer is connected straight after the boot then all is good.

Dominant language
No language data
Stars
5.6k
Forks
1.7k
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from raspberrypi/firmware

All issues in raspberrypi/firmware

Similar issues

More Embedded & IoT issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.