Date: Tue, 23 Feb 2010 12:47:22 -0300 From: Renato Botelho <rbgarga@gmail.com> To: Brandon Gooch <jamesbrandongooch@gmail.com> Cc: Chris Hedley <freebsd-current@chrishedley.com>, FreeBSD Current <freebsd-current@freebsd.org>, Andriy Gapon <avg@icyb.net.ua> Subject: Re: Can't use USB keyboard during boot menu Message-ID: <747dc8f31002230747u7fbe5030y2d0c869d5db94a0a@mail.gmail.com> In-Reply-To: <179b97fb1002230728l4294916cs6b4b9a18b18f044a@mail.gmail.com> References: <747dc8f31002220835g481b0baeqb1d6df32a79b7da2@mail.gmail.com> <alpine.BSF.2.00.1002222231100.98337@teapot.cbhnet> <747dc8f31002230318v384e0259mcfddbf137c0d5057@mail.gmail.com> <4B83D821.6000207@icyb.net.ua> <179b97fb1002230728l4294916cs6b4b9a18b18f044a@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Feb 23, 2010 at 12:28 PM, Brandon Gooch <jamesbrandongooch@gmail.com> wrote: > On Tue, Feb 23, 2010 at 7:29 AM, Andriy Gapon <avg@icyb.net.ua> wrote: >> on 23/02/2010 13:18 Renato Botelho said the following: >>> On Mon, Feb 22, 2010 at 7:35 PM, Chris Hedley >>> <freebsd-current@chrishedley.com> wrote: >> [snip] >>>> Do you have USB legacy support enabled in your BIOS? =A0I'm not sure i= f >>>> there's an option for the loader to use USB devices natively, but the = BIOS's >>>> legacy option where it provides AT/PS2 emulation is probably the easie= st way >>>> to get the keyboard working. >>> >>> Yes, I do, but it seems to be a regression on FreeBSD itself, I had thi= s problem >>> in the past and I checked the same things i need to check in the past a= gain and >>> everything is fine. >> >> A more precise way to state that would be "a regression in FreeBSD boot/= loader". >> I think that you are referring to the issue that was fixed by r189017. >> It might be worthwhile investigating what was done in that revision and = what >> happened in sys/boot code since then. >> >> One possibility is that your BIOS uses memory above 1MB for USB emulatio= n, but >> doesn't mark that memory as used in system memory map. =A0In that case t= hat memory >> could be overwritten by the loader. =A0If that's true then the blame is = on the BIOS. >> =A0Alternatively, our code might be parsing the system memory map incorr= ectly. >> But I am just making wild guesses here. >> > > I don't know if it is at all related, but this commit has caused > problems for me booting at least one of my machines: > > http://svn.freebsd.org/viewvc/base/head/sys/boot/i386/zfsboot/zfsboot.c?r= 1=3D199714&r2=3D200309 > > Commit message: > > Revision 200309 - (view) (annotate) - [select for diffs] > Modified Wed Dec 9 20:36:56 2009 UTC (2 months, 2 weeks ago) by jhb > File length: 24893 byte(s) > Diff to previous 199714 > - Port bios_getmem() from libi386 to {gpt,}zfsboot() and use it to > =A0safely allocate a heap region above 1MB. =A0This enables {gpt,}zfsboot= () > =A0to allocate much larger buffers than before. > - Use a larger buffer (1MB instead of 128K) for temporary ZFS buffers. = =A0This > =A0allows more reliable reading of compressed files in a raidz/raidz2 poo= l. > > Submitted by: =A0 Matt Reimer =A0mattjreimer of gmail > MFC after: =A0 =A0 =A01 week > > Renato, are you booting ZFS? Nope, UFS. I'll try to find another USB keyboard to test --=20 Renato Botelho
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?747dc8f31002230747u7fbe5030y2d0c869d5db94a0a>