Date: Mon, 12 Dec 2016 21:57:17 -0800 From: Peter Grehan <grehan@freebsd.org> To: Harry Schmalzbauer <freebsd@omnilan.de> Cc: freebsd-virtualization@freebsd.org Subject: Re: Unhandled ps2 keyboard keysym with UEFI-edk2-bootrom and bhyve(8) Message-ID: <bab035af-29e2-ea00-cb35-45d0a146cbf9@freebsd.org> In-Reply-To: <584DBEAA.1080502@omnilan.de> References: <584DBEAA.1080502@omnilan.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Harry, > Unfortunately the VNC part seems to have keyscan problems: > Unhandled ps2 keyboard keysym 0xc4 > Unhandled ps2 keyboard keysym 0xf6 > Unhandled ps2 keyboard keysym 0xff7f > Just to list a view... > > The really unfortunate problem is that some characters are completely > missing, while others are just shifted (involving even meta keys). > I haven't found any rule yet, it looks like a mixture of en-US and de-DE > layout. > Most unfortunate, I can't login because of the missing characters :-( So > close yet so far... Would you be able to list the key mappings that don't work (and also the VNC client you are using) ? > But what I'm really wondering about is how to influence boot order e.g. > > If I boot into the EFI shell (edk2-bootrom guest) and return with exit > into the uefi firmware setup (still edk2-bootrom), I can select what to > boot with the boot manager (also MBR booting via CSM works great, thanks > thanks thanks!), and I can also save the settings, but they are lost if > bhyve(8) terminates. > There's /dev/vmm.io/host-bootrom, which I don't understand yet, but > probably that's a way to feed the firmware? There's a fix for this in progress - the contents of the UEFI NV vars will be saved/restored from a host file. later, Peter.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bab035af-29e2-ea00-cb35-45d0a146cbf9>