| Summary: | Boot loader doesn't recognize IBM Spacesaver keyboard | ||
|---|---|---|---|
| Product: | Base System | Reporter: | bob <bob> |
| Component: | misc | Assignee: | Sheldon Hearn <sheldonh> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | Unspecified | ||
| Hardware: | Any | ||
| OS: | Any | ||
|
Description
bob
1999-07-21 17:10:00 UTC
>>Number: 12738 >>Category: misc >>Synopsis: Boot loader doesn't recognize IBM Spacesaver keyboard [...] >>Environment: >This happens on 3.2-RELEASE and several versions of 4.0-current snaps >that I tried. >>Description: >When booting the kern floppy the boot loader displays "Keyboard: no" >then refuses to boot (hangs after printing the BTX loader version msg). >This is with one of the small IBM (Lexmark) keyboards (the ones without >the numeric keypad and lights). Changing to a full-sized keyboard >allows the boot to proceed. >>How-To-Repeat: >Install one of the Spacesaver keyboards and attempt to boot the kern >floppy. >>Fix: >Workaround is to replace the Spacesaver keyboard with a full-sized one. As soon as you see "Keyboard: no", hit the space key. You will see the boot block (note that this is not the boot loader) prompt. Type -Dh and return. Yes, you can type from the spacesaver keyboard at this point. Then things should go normally. This is a known problem and recently added to TROUBLE.TXT. Kazu In my previous mail, I wrote: >>>Number: 12738 >>>Category: misc >>>Synopsis: Boot loader doesn't recognize IBM Spacesaver keyboard >[...] >As soon as you see "Keyboard: no", hit the space key. You will see >the boot block (note that this is not the boot loader) prompt. > >Type -Dh and return. Yes, you can type from the spacesaver keyboard >at this point. Then things should go normally. > >This is a known problem and recently added to TROUBLE.TXT. > >Kazu Just for the record, would you provide us the part number of your Spacesaver keyboard and details of your motherboard and BIOS, please? Also, after you install FreeBSD on the machine, give -v option to the boot command. (You hit space when you see "automatic boot in X seconds..." in the BTX loader, then type "boot -v".) When the system is up and running, review the file /var/run/dmesg.boot and locate the line: atkbd: keyboard ID 0xXXXX (XX) I would like to know the ID number. I also own an IBM Spacesaver keyboard (part # 1393278), and it's recognized by the boot block all right. My motherboard is MicroStar MS-6103 with the AWARD BIOS. Kazu On Thu, Jul 22, 1999 at 03:29:26AM +0900, Kazutaka YOKOTA wrote: > > In my previous mail, I wrote: > > >>>Number: 12738 > >>>Category: misc > >>>Synopsis: Boot loader doesn't recognize IBM Spacesaver keyboard > >[...] > > >As soon as you see "Keyboard: no", hit the space key. You will see > >the boot block (note that this is not the boot loader) prompt. > > > >Type -Dh and return. Yes, you can type from the spacesaver keyboard > >at this point. Then things should go normally. > > > >This is a known problem and recently added to TROUBLE.TXT. > > > >Kazu > > Just for the record, would you provide us the part number of your > Spacesaver keyboard and details of your motherboard and BIOS, please? > > Also, after you install FreeBSD on the machine, give -v option to the > boot command. (You hit space when you see "automatic boot in X > seconds..." in the BTX loader, then type "boot -v".) > > When the system is up and running, review the file > /var/run/dmesg.boot and locate the line: > > atkbd: keyboard ID 0xXXXX (XX) > > I would like to know the ID number. It is: atkbd: keyboard ID 0x54ab (0) > > I also own an IBM Spacesaver keyboard (part # 1393278), and it's > recognized by the boot block all right. My motherboard is MicroStar > MS-6103 with the AWARD BIOS. My keyboard is part #1397681. The motherboard is an ASUS P/I-XP6NP5, Award BIOS (Ver. 0105). Hope this helps, Bob -- Bob Willcox Don't tell me that worry doesn't do any good. bob@pmr.com I know better. The things I worry about don't Austin, TX happen. -- Watchman Examiner State Changed From-To: open->feedback Since this is a known problem documented in the trouble-shooting notes at http://www.freebsd.org/releases/3.2R/errata.html I'd like to close your PR. Are you happy with that? Responsible Changed From-To: freebsd-bugs->sheldonh I'll take this one. State Changed From-To: feedback->closed Originator is happy with the answer in the release errata. |