Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 27 Jun 2022 16:18:58 +0000
From:      Ivan Quitschal <tezeka@hotmail.com>
To:        Hans Petter Selasky <hps@selasky.org>, "freebsd-current@freebsd.org" <freebsd-current@freebsd.org>, "wulf@freebsd.org" <wulf@freebsd.org>, "grembo@freebsd.org" <grembo@freebsd.org>, "imp@bsdimp.com" <imp@bsdimp.com>
Subject:   RES: iichid/hms keyboard/mouse wrongly reattached to uhid/ums
Message-ID:  <CP6P284MB190046AC1EBBB9F6B4123246CBB99@CP6P284MB1900.BRAP284.PROD.OUTLOOK.COM>
In-Reply-To: <420b1f58-09c4-6876-b1ad-91751c60e83c@selasky.org>
References:  <CP6P284MB1900818F505F78F68EC4C6BECBB99@CP6P284MB1900.BRAP284.PROD.OUTLOOK.COM> <420b1f58-09c4-6876-b1ad-91751c60e83c@selasky.org>

next in thread | previous in thread | raw e-mail | index | archive | help

> Hi,
>
>Can you dump "kldstat" at the different times?

>I guess it may be just be that the wrong module is loaded first, so it gra=
bs the device, because there are no other drivers loaded, even though ums i=
s a generic driver.

>Try loading all relevant drivers in /boot/loader.conf . Then the attach or=
der shouldn't matter.

>--HPS


Hi Michael=20

Yes , hw.usb.usbhid.enable=3D"1" is in loader.conf , not sysctl=20

Hi Warner

When ums.ko is up, the second attach is always taken by "ums" first no matt=
er what. First time you boot tho, it takes the correct one (hms)

Hi Hans

Looks like this below is the only order I could make it work even tho  uhid=
 and usbhid get loaded regardless what I put on loader.conf

usbhid_load=3D"NO" <-- still loaded anyway
uhid_load=3D"NO" <-- still loaded anyway
ums_load=3D"NO" <- this one is not loaded
ic_load=3D"YES"
iichid_load=3D"YES"
hidbus_load=3D"YES"
hsctrl_load=3D"YES"
hidmap_load=3D"YES"
hcons_load=3D"YES"
hkbd_load=3D"YES"
hms_load=3D"YES"
hmt_load=3D"YES"
hconf_load=3D"YES"

hw.usb.usbhid.enable=3D"1"

with the order below , after 5 reboots and lots of kvm switches , it always=
 ended up on the right iichid device. Seems to be working now

but like I said, its random, let see after some more reboots if this rule i=
s still valid

thanks

Ivan



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CP6P284MB190046AC1EBBB9F6B4123246CBB99>