Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer via buildroot <buildroot@buildroot.org>
To: Shafqat Abbas <shafqat.abbas@skyelectric.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] Information Required for Buildroot Image Issue
Date: Tue, 19 Mar 2024 23:27:23 +0100	[thread overview]
Message-ID: <20240319232723.70ebf43c@gmx.net> (raw)
In-Reply-To: <CAL5xJopYY+47g9XAwr=9WDBrYBTPB4ycnh0ODy45+jNsP8WfFg@mail.gmail.com>

On Tue, 19 Mar 2024 14:18:23 +0500, Shafqat Abbas <shafqat.abbas@skyelectric.com> wrote:

> Hi,
>
> I hope you are doing well. I have been trying to compile the Linux OS for
> Raspberry Pi 4 (Compute Module / CM4) using buildroot. I have tried all the
> default configurations available for raspberry pi systems. After writing
> the image to the pi, the system boots up properly, however, it does not
> read input from the keyboard. I am facing this issue on all builds. I have
> also tried changing the board but that also resulted in the same issue.
>
> I am using the following steps to generate builds:
>
> 1. ```make raspberrypi_defconfig```
> 2. ```make```
>
> I have used this method for compiling builds for all defconfigs, including
> the following:
> 1. Build for *Raspberry Pi*
> 2. Build for *Raspberry Pi 4*
> 3. Build for *Raspberry* *Pi 4 (64 bit)*
> 4. Build for *Raspberry Pi CM4 IO*
> 5. Build for *Raspberry Pi CM4 IO (64 bit)*
>
> The keyboard does not work at all. Even the lights do not work, which shows
> that the keyboard is not connected, however the same keyboard works fine on
> other systems.
>
> So, the assumption is that the keyboard is fine, the board is fine, the RPi
> is fine, and the issue lies in the build compiled by buildroot.
>
> I kindly request the community to help me sort out this issue. Thanks a lot

See 'Bug 15910 - USB keyboard is not working by default "raspberrypicm4io_64_defconfig"'
([1]) for the same problem and different solutions...

Regards,
Peter

[1] https://bugs.busybox.net/show_bug.cgi?id=15910
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-03-19 22:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-19  9:18 [Buildroot] Information Required for Buildroot Image Issue Shafqat Abbas
2024-03-19 22:27 ` Peter Seiderer via buildroot [this message]
     [not found]   ` <CAL5xJooTe=qF8ngXTP45Uge0=ck546OnEzr2EaH4Qq5wrEj7rw@mail.gmail.com>
2024-03-20 15:46     ` Peter Seiderer via buildroot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240319232723.70ebf43c@gmx.net \
    --to=buildroot@buildroot.org \
    --cc=ps.report@gmx.net \
    --cc=shafqat.abbas@skyelectric.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox