Date: Thu, 01 Mar 2018 16:56:54 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 140849] [ums] [usb8] USB mouse doesn't work under FreeBSD 8.0-RELEASE Message-ID: <bug-140849-8-I2ycOhBocB@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-140849-8@https.bugs.freebsd.org/bugzilla/> References: <bug-140849-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D140849 Vin=C3=ADcius Zavam <egypcio@googlemail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |egypcio@googlemail.com --- Comment #3 from Vin=C3=ADcius Zavam <egypcio@googlemail.com> --- Hi, as crazy as it sounds, and as the status of this PR is still 'open' I will report a quick update about it... under 12.0-CURRENT right after a world/kernel upgrade (from Feb 26th, sorry for the missing re= v) I rebooted into a system without USB mouse support. moused(8) was not startin= g, and there was no /dev/umsX available. % uname -iUKa FreeBSD zim 12.0-CURRENT FreeBSD 12.0-CURRENT #4 r330240: Thu Mar 1 17:0= 2:10 CET 2018 root@zim:/usr/obj/usr/src/amd64.amd64/sys/ZIM amd64 ZIM 12000= 58 1200058 getting ums(4) back in place just solved the thing; or just kldload(8) it. % cat /sys/amd64/conf/ZIM include GENERIC-NODEBUG ident ZIM device ums # JUST ADD! the ums(4) is really not in the GENERIC kernel config for quite of a long t= ime, and that's why it sounds crazy. I was using the very same KERNCONF without = any issues til today. so, anyway, loading/using ums(4) solved it for me. ugen2.3: <Logitech USB-PS2 Optical Mouse> at usbus2, cfg=3D0 md=3DHOST sp= d=3DLOW (1.5Mbps) pwr=3DON (98mA) maybe someone can help on tracking actual changes impacting USB support like this? KR, --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-140849-8-I2ycOhBocB>