mirror of
https://github.com/netbootxyz/netboot.xyz.git
synced 2026-04-25 15:15:56 +03:00
[GH-ISSUE #1608] Debian image flavours have problems with keyboard and mouse operation #536
Labels
No labels
Hacktoberfest
Hacktoberfest
bootloader
bsd
bug
confirmed
documentation
duplicate
enhancement
enhancement
enhancement
eol
experimental-merged
freebsd
help wanted
invalid
investigate
ipxe
linux
live-os
memdisk
menu
no-issue-activity
no-issue-activity
pull-request
released
todo
upstream
windows
windows
work-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/netboot.xyz#536
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @juampe on GitHub (Apr 13, 2025).
Original GitHub issue: https://github.com/netbootxyz/netboot.xyz/issues/1608
The bug at this time is reproducible with PXE boot in Hyper-V, VirtualBox, HP Probook and MSI B550 Ryzen7 5800X
server docker image linuxserver/netbootxyz
webapp version 0.7.5
Menu version 2.0.86
Al flavours of live Debian 12 boot but frozen
The machine boots and download objects to boot , but when start display, the mosue and keyboard does not work
Unexpectedly SysReq keys works and can reboot the machine
Seems an issue related with Debian 12 squashfs
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Got a Debian 12 Live environment
Screenshots


For example "Debian Mate" boots but the keyboard and mouse does not work (PS/2 or USB)
Same with Gnome flavour
Same with polluted assets (Debian 11 KDE with 12 squashfs)
Additional context
Live Debian 11 Xfce works
Live Debian 11 cinnamon works
Live Debian 11 Kde does not work, maybe menu misconfigurarion
Weird menu assets for debian 11 (with version 12 squashfs)
@UntouchedWagons commented on GitHub (Apr 29, 2025):
Yes I have experienced this too. Interestingly Proxmox (which is based off of Debian) does not have this issue.