On 20/07/07, Vladimir Grebenschikov <[EMAIL PROTECTED]> wrote:
Tries your patch under 7-CURRENT,
Both USB keyboard and USB mouse (MS) was not attached after boot, but
detected successful. Most probably due to not fixed default entry in
devd.conf:
attach 100 {
device-name "ums[0-9]+";
action "/etc/rc.d/moused start $device-name";
};
...
# When a USB keyboard arrives, attach it as the console keyboard.
attach 100 {
device-name "ukbd0";
action "/etc/rc.d/syscons setkeyboard /dev/ukbd0";
};
detach 100 {
device-name "ukbd0";
action "/etc/rc.d/syscons setkeyboard /dev/kbd0";
};
...
part of dmesg:
uhub5: 7 ports with 7 removable, self powered
uhidev0: <BTC USB KMp, class 0/0, rev 1.00/1.00, addr 3> on uhub5
uhid0 on uhidev0
uhid0: input=8, output=1, feature=0
uhidev1: <BTC USB KMp, class 0/0, rev 1.00/1.00, addr 3> on uhub5
uhid1 on uhidev1
uhid1: input=3, output=0, feature=0
uhidev2: <Microsoft Microsoft 5-Button Mouse with IntelliEye(TM), class 0/0, rev
1.10/3.00, addr 4> on uhub5
uhid2 on uhidev2
Hi Vladimir,
Thanks for helping test the patch.
devd.conf should be is alright how it is, as keyboards are still ukbd
devices and mice are still ums devices. The difference with the patch
is they now attach to the uhidev driver level.
So what we should be seeing something like this for your mouse -
uhidev2: <Microsoft Microsoft 5-Button Mouse with IntelliEye(TM),
class 0/0, rev 1.10/3.00, addr 4> on uhub5
ums0 on uhidev0
ums0: 5 buttons and Z dir and a TILT dir.
Before I look into trying to work out how to debug this further could you
just confirm to me that ukbd and ums are both either in your kernel or
kldload'ed.
The following command should show you:
# kldstat -v | egrep '(ukbd|ums)'
Thanks,
Mark
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-usb
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
