# inxi ## Identification [[X.Org Server|X.Org]], `fbdev`, [[evdev|evdev]], and XInput form a Linux graphical/input stack. A Xen guest may expose a virtual pointer in addition to a passed-through or host-integrated mouse, causing duplicate or conflicting devices. [[inxi|inxi]] inventories hardware and system configuration. ## Notebook evidence - [[Scanned_20260730-1719#PDF page 70 — X.Org input-driver troubleshooting in a Xen guest|PDF page 70: X.Org input-driver troubleshooting in a Xen guest]] — This is a concrete troubleshooting page: a SysVinit guest reaches runlevel 5, loads a basic framebuffer driver, and then needs an X.Org rule to ignore an unwanted Xen virtual pointer while retaining the physical Mionix mouse. ## Relationships and overlays The source places this note in a shared evidence cluster with [[evdev|evdev]] · [[X.Org Server|X.Org Server]]. Within the larger collection, this evidence extends [[Vendor-Agnostic Recovery|vendor-agnostic recovery]] and [[Continuity Architecture|continuity architecture]] by showing how software, hardware, identity, and pre-OS control depend on recoverable interfaces. ## Evidentiary status and open leads Preserve `xinput list`, `/var/log/Xorg.0.log`, device match properties, and the final tested rule. ## Source - [[Scanned_20260730-1719|Scanned_20260730-1719]]