Date: Tue, 11 Nov 2008 21:09:00 +0100 From: Volker <volker@vwsoft.com> To: Peter Wemm <peter@wemm.org> Cc: FreeBSD Stable <freebsd-stable@freebsd.org>, Andriy Gapon <avg@icyb.net.ua>, freebsd-usb@freebsd.org Subject: Re: usb keyboard dying at loader prompt Message-ID: <4919E65C.1020307@vwsoft.com> In-Reply-To: <e7db6d980811111055j24ed8f4rb4539c6678553b97@mail.gmail.com> References: <4912E462.4090608@icyb.net.ua> <491586B9.2020303@vwsoft.com> <4919851B.7050800@icyb.net.ua> <e7db6d980811111055j24ed8f4rb4539c6678553b97@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/11/08 19:55, Peter Wemm wrote: > ... > * There were other consequences of using the partition ID hack - I > think I remember it turning off the apic for msdos mode. > > Your problems may be different, but mine were caused by a BIOS > whitelist of MBR partition id's. What a stupid problem. On that > motherboard I ended up taking the path of least resistance and using > the PS/2 adapter plug on the keyboard. Peter, very interesting what you've found. That reminds me on some investigations I did as I was hunting USB boot device problems. Some BIOSes do not check the partition (slice) ID but are looking for a file system magic. If a FAT filesystem is detected, the BIOS does some stupid things (like ignoring the active partition flag and booting the FAT slice no matter what you've flagged active). Just an example and off-topic to Andriy's keyboard problem. But when combining that with your findings, it may still be a thing to check for... ;) Volker
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4919E65C.1020307>