Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#175 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
c, linux, raspberry-pi
Área
embedded-iot, operating-systems

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
C
Estrellas
12
Forks
3
Merge medio
7 h 1 min
PR fusionados (30 d)
7

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de nextbsd/nextbsd-kernel

Todos los issues de nextbsd/nextbsd-kernel

Issues similares

Más issues de C

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.