Date: Tue, 07 Mar 2006 14:10:50 -0800 From: Maksim Yevmenkin <maksim.yevmenkin@savvis.net> To: Tai-hwa Liang <avatar@mmlab.cse.yzu.edu.tw> Cc: freebsd-current@freebsd.org Subject: Re: HEADSUP: kbdmux(4) is in both HEAD and RELENG_6 Message-ID: <440E04EA.4040805@savvis.net> In-Reply-To: <0603080540553.70476@www.mmlab.cse.yzu.edu.tw> References: <4408E4E9.1010705@savvis.net> <0603080540553.70476@www.mmlab.cse.yzu.edu.tw>
next in thread | previous in thread | raw e-mail | index | archive | help
Tai-hwa Liang wrote: > On Fri, 3 Mar 2006, Maksim Yevmenkin wrote: > >> kbdmux(4) is now fully integrated into HEAD and RELENG_6. please give >> it a try and let us know if you have any problems. > > Hi, > > Thank you for your effort on this. Just tried to upgrade my -CURRENT > to HEAD and the GENERIC kernel seems not happy with the keyboard. > > It turns out that I had ukbd_load in /boot/loader.conf and this froze > latest GENERIC kernel booting: > > . > . > xl0: [MPSAFE] > psmcpnp0: <PS/2 mouse port> irq 12 on acpi0 > atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0 > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > stuck here did you try to NOT load kbdmux(4)? does it still hang? also GENERIC already has 'device ukbd' so you do not have to load it. > If I stop loading ukbd.ko in loader.conf, GENERIC will boot(see the > attached verbosing boot dmesg). It also looks to me that whether the > external USB keyboard is attached or not doesn't matter in this case. ok. does kbdmux(4) work?, i.e. can you type on both (atkbd(4) and ukbd(4)) keyboards? > I can reproduce this on a 5-hours-old RELENG_6(on a Tyan TigerMPX > desktop) and an one-day-old HEAD(on a Thinkpad T40), with GENERIC kernel > from: well, i'm not sure what is the problem here. just by looking at the dmesg you posted i can see all three atkbd(4), ukbd(4) and kbdmux(4). so it seems like everything should be working. is it not? thanks, max
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?440E04EA.4040805>