Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

USB mouse hotplug does not work (possibly Pi-specific)

オープン
  • 何か問題がありますか？
#175 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
35/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
静か
技術スタック
c, linux, raspberry-pi
領域
embedded-iot, operating-systems

調査の方向性

Start by collecting the missing reproduction details: board, whether the mouse works when connected before boot, port, and dmesg, /dev/input/, and usbconfig list output before and after plugging. Check whether devd reports the attach event; these observations distinguish USB event delivery, devd, and userland input handling. No code files or tests are identified, and done means locating which layer fails and recording enough evidence to route the issue appropriately.

索引モデルが issue の本文から書いたものです。

説明

area:rpi5 bug

Placeholder so this is not lost. Reported informally; symptom details not yet
captured — see "What to record" below before investigating.

Report

A USB mouse hotplugged after boot does not work. Possibly Raspberry Pi specific.

What is already ruled out

Not a missing driver. The HID input stack is compiled into the shipping config
(config/NEXTBSD, inherited by NEXTBSD-RPI5 via include NEXTBSD):

device  hms        # hidbus mouse leaf: relative mice and absolute pointers
device  hidmap     # usage->evdev mapper hms/hpen are built on
device  hmt        # multitouch
device  hpen
device  hconf

So usbhid0 -> hidbus0 -> hms should bind, and the question is why it does not happen
on a hotplug specifically.

Likely areas, roughly in order

  1. Hotplug event delivery. If the device attaches on a cold boot but not on a
    hotplug, the drivers are fine and the problem is USB port-change notification. On the
    Pi 5 family both USB controllers are behind RP1 (PCIe), so this may be RP1 interrupt
    related — cf. patch 0028, rp1: acknowledge level-triggered interrupts from post-ithread.
    That would make it genuinely Pi-specific, as suspected.
  2. devd. Not running, or running without the rules to react to the new device.
  3. The consumer. A new /dev/input/* node appearing but Gershwin/X not picking it
    up until restart. This would be userland, not kernel, and the ticket should move.

What to record when picking this up

None of this is known yet, and the answers change which of the three areas above it is:

  • Which board — Pi 500+, Pi 5 B, CM5, or a VM? Does it reproduce off-Pi at all?
  • Does the same mouse work when plugged in before boot? This is the single most
    useful bit: it splits "driver never binds" from "hotplug path broken".
  • Which port — RP1 USB (the normal ones) or something else?
  • dmesg across the plug event: does anything appear at all (ugen, usbhid, hms)?
  • ls /dev/input/ and usbconfig list before and after plugging.
  • Is devd running, and does devd -d show the attach event?
  • Does unplug/replug of a mouse that worked at boot break it, or is it only
    never-seen-before devices?

Not blocking anything

Filed to avoid losing it, not because it is urgent. No owner.

主要言語
C
スター
12
フォーク
3
平均マージ
7時間 1分
マージ済み PR（30日）
7

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

nextbsd/nextbsd-kernel のほかの issue

nextbsd/nextbsd-kernel の issue をすべて見る

似ている issue

C の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。