Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 23 Feb 2010 09:28:49 -0600
From:      Brandon Gooch <jamesbrandongooch@gmail.com>
To:        Andriy Gapon <avg@icyb.net.ua>
Cc:        Renato Botelho <rbgarga@gmail.com>, Chris Hedley <freebsd-current@chrishedley.com>, FreeBSD Current <freebsd-current@freebsd.org>
Subject:   Re: Can't use USB keyboard during boot menu
Message-ID:  <179b97fb1002230728l4294916cs6b4b9a18b18f044a@mail.gmail.com>
In-Reply-To: <4B83D821.6000207@icyb.net.ua>
References:  <747dc8f31002220835g481b0baeqb1d6df32a79b7da2@mail.gmail.com> <alpine.BSF.2.00.1002222231100.98337@teapot.cbhnet> <747dc8f31002230318v384e0259mcfddbf137c0d5057@mail.gmail.com> <4B83D821.6000207@icyb.net.ua>

next in thread | previous in thread | raw e-mail | index | archive | help
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 if
>>> there's an option for the loader to use USB devices natively, but the B=
IOS's
>>> legacy option where it provides AT/PS2 emulation is probably the easies=
t way
>>> to get the keyboard working.
>>
>> Yes, I do, but it seems to be a regression on FreeBSD itself, I had this=
 problem
>> in the past and I checked the same things i need to check in the past ag=
ain and
>> everything is fine.
>
> A more precise way to state that would be "a regression in FreeBSD boot/l=
oader".
> 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 w=
hat
> happened in sys/boot code since then.
>
> One possibility is that your BIOS uses memory above 1MB for USB emulation=
, but
> doesn't mark that memory as used in system memory map. =A0In that case th=
at memory
> could be overwritten by the loader. =A0If that's true then the blame is o=
n the BIOS.
> =A0Alternatively, our code might be parsing the system memory map incorre=
ctly.
> 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?r1=
=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
  safely allocate a heap region above 1MB.  This enables {gpt,}zfsboot()
  to allocate much larger buffers than before.
- Use a larger buffer (1MB instead of 128K) for temporary ZFS buffers.  Thi=
s
  allows more reliable reading of compressed files in a raidz/raidz2 pool.

Submitted by:	Matt Reimer  mattjreimer of gmail
MFC after:	1 week

Renato, are you booting ZFS?

-Brandon



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?179b97fb1002230728l4294916cs6b4b9a18b18f044a>