Date: Thu, 27 Jul 2006 11:59:46 -0700 From: Maksim Yevmenkin <maksim.yevmenkin@savvis.net> To: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= <des@des.no> Cc: freebsd-hackers@freebsd.org, Intron <mag@intron.ac> Subject: Re: How to Use ddb(4)? Message-ID: <44C90D22.5010607@savvis.net> In-Reply-To: <868xme28nt.fsf@xps.des.no> References: <1153997829.12770@origin.intron.ac> <864px31eyz.fsf@xps.des.no> <courier.44C8C9B1.00003D28@intron.ac> <86psfryvvo.fsf@xps.des.no> <44C8CFA2.3000400@savvis.net> <868xme28nt.fsf@xps.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
Dag-Erling Smørgrav wrote: > maksim yevmenkin <maksim.yevmenkin@savvis.net> writes: >> Dag-Erling Smørgrav <des@des.no> writes: >>> No, kbdmux needs to be fixed so it works in DDB. >> actually, atkbd(4) needs to be fixed to support "polled" mode :) > > It used to work fine before kbdmux(4) came along... because it makes certain assumptions about console (i.e. syscons(4)) driver. anyway, the link i posted in previous email contains a patch that should fix problems with kbdmux(4) and atkbd(4) not working in ddb(4), mid-boot (rootfs prompt, geli prompt, etc). so far i only got one (successful) report. would people please give it a try to see if work, so i can commit it. thanks, max
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44C90D22.5010607>