Opened 7 years ago

Closed 7 years ago

#563 closed defect (No Change Needed)

Keyboard dead with ACPI 3.21.02

Reported by: bobmcl Owned by: dazarewicz
Priority: minor Milestone: Release 4.00
Component: ACPI PSD Version: 3.21.02
Keywords: keyboard Cc:

Description

I have two new eCS systems on the same PC, one (D:) with ACPI 3.18 (ECS 2.1 install) and the other (C:) I have installed ACPI 3.21.02. On C: nothing on the keyboard works. The keyboard does work on D:, BIOS and AIRBOOT menu. If I rem out the ACPI.PSD the keyboard works. I have swapped the original IBMKBD.SYS back in with no change. I have had the /VW switch on, no change. Currently rem'd out usb, apm.add, acpidaemon and powerman. C: boots with 2 processors enabled. MOBO Gigabyte GA-945GCMX-S2. I've got other systems but I'd love to finish this upgrade and switch over.

Attachments (2)

ALLBLACK-20121121-acpi-3.21.02.zip (40.0 KB) - added by bobmcl 7 years ago.
acpi debug log
cpartnCONFIG.SYS (7.1 KB) - added by bobmcl 7 years ago.

Download all attachments as: .zip

Change History (9)

Changed 7 years ago by bobmcl

acpi debug log

comment:1 follow-up: Changed 7 years ago by dazarewicz

  • Milestone changed from Release Version 4.0.0 to Feedback pending

I assume you are using a PS/2 keyboard.

Does a USB keyboard work?

Please provide your CONFIG.SYS.

comment:2 in reply to: ↑ 1 ; follow-up: Changed 7 years ago by bobmcl

Replying to dazarewicz:

I assume you are using a PS/2 keyboard.

Does a USB keyboard work?

Please provide your CONFIG.SYS.

Yes, I am using a PS/2 keyboard. When the system is installed it will run through a PS/2 KVM. Right now the kbd/mouse are directly plugged in. The USB kbd does not work either. It does work on the BIOS and AIRBOOT menu. config.sys attached (with usb remmed out, prior to the above test).

Changed 7 years ago by bobmcl

comment:3 in reply to: ↑ 2 Changed 7 years ago by bobmcl

Replying to bobmcl:

Replying to dazarewicz:

I assume you are using a PS/2 keyboard.

Does a USB keyboard work?

Please provide your CONFIG.SYS.

Yes, I am using a PS/2 keyboard. When the system is installed it will run through a PS/2 KVM. Right now the kbd/mouse are directly plugged in. The USB kbd does not work either. It does work on the BIOS and AIRBOOT menu. config.sys attached (with usb remmed out, prior to the above test).

My apologies. The USB keyboard does work, I had remmed out the usbkbd driver. This means I can continue testing but still need the PS/2 keyboard for the final install.

comment:4 follow-up: Changed 7 years ago by dazarewicz

I thought that might be the case.

Does a PS/2 mouse work? Or are you only using a USB mouse?

Keep in mind that the PSD has no knowledge of any keyboard and it does not even care if a keyboard even exists. So regardless of what you might think, it does not do anything to any keyboard (or mouse, etc.) Assuming that you do not have a driver setup issue, your BIOS is probably turning PS/2 support off when Acpi is enabled. I suggest you check your BIOS settings for something related to PS/2 support.

comment:5 in reply to: ↑ 4 ; follow-up: Changed 7 years ago by bobmcl

Replying to dazarewicz:

I thought that might be the case.

Does a PS/2 mouse work? Or are you only using a USB mouse?

Keep in mind that the PSD has no knowledge of any keyboard and it does not even care if a keyboard even exists. So regardless of what you might think, it does not do anything to any keyboard (or mouse, etc.) Assuming that you do not have a driver setup issue, your BIOS is probably turning PS/2 support off when Acpi is enabled. I suggest you check your BIOS settings for something related to PS/2 support.

Both the PS/2 and USB mouse work. Yes, I am surprised also at the coincidence of acpi and keyboard problems. There is nothing in the BIOS about PS/2 keyboard, just an option to disable the usb keyboard. It is an Award BIOS. Theseus shows the IBMKBD$ driver resident. I notice a few things in the Hardware Manager

  • PIC 0 has no interrupt assigned, PIC 1 has interrupt 2.
  • With ACPI 318 and 321 the same interrupts are assigned to the following ... KDB 1,PIC1 2, Floppy 6, RTC 8, aux mouse 12, ide0 14, ide1 15, acpi 9 44 45 46 47.
  • With ACPI 318 these interrupts are assigned ... usb1.1(1) 9, usb1.1(2) 11, usb1.1(3) 11, usb1.1(4) 5, usb2 9. These are the same as the hardware assigments displayed at bootup.
  • With ACPI 321 these interrupts are assigned ... usb1.1(1) 23, usb1.1(2) 19, usb1.1(3) 18, usb1.1(4) 16, usb2 23.

I will recheck everything (maybe reinstall).

comment:6 in reply to: ↑ 5 Changed 7 years ago by bobmcl

Replying to bobmcl:

Replying to dazarewicz:

I thought that might be the case.

Does a PS/2 mouse work? Or are you only using a USB mouse?

Keep in mind that the PSD has no knowledge of any keyboard and it does not even care if a keyboard even exists. So regardless of what you might think, it does not do anything to any keyboard (or mouse, etc.) Assuming that you do not have a driver setup issue, your BIOS is probably turning PS/2 support off when Acpi is enabled. I suggest you check your BIOS settings for something related to PS/2 support.

Both the PS/2 and USB mouse work. Yes, I am surprised also at the coincidence of acpi and keyboard problems. There is nothing in the BIOS about PS/2 keyboard, just an option to disable the usb keyboard. It is an Award BIOS. Theseus shows the IBMKBD$ driver resident. I notice a few things in the Hardware Manager

  • PIC 0 has no interrupt assigned, PIC 1 has interrupt 2.
  • With ACPI 318 and 321 the same interrupts are assigned to the following ... KDB 1,PIC1 2, Floppy 6, RTC 8, aux mouse 12, ide0 14, ide1 15, acpi 9 44 45 46 47.
  • With ACPI 318 these interrupts are assigned ... usb1.1(1) 9, usb1.1(2) 11, usb1.1(3) 11, usb1.1(4) 5, usb2 9. These are the same as the hardware assigments displayed at bootup.
  • With ACPI 321 these interrupts are assigned ... usb1.1(1) 23, usb1.1(2) 19, usb1.1(3) 18, usb1.1(4) 16, usb2 23.

I will recheck everything (maybe reinstall).

I reinstalled eCS 2.1 then updated to ACPI 3.21.02. The PS/2 keyboard now works. I have no idea what the problem was, I assume that there was some glitch in my system when I initially installed the ACPI update. I would like to say that David's support for this problem was much appreciated and very helpful in clearing it up. This can be closed, do I do that and if so, how?

comment:7 Changed 7 years ago by dazarewicz

  • Milestone changed from Feedback pending to Release Version 4.0.0
  • Resolution set to No Change Needed
  • Status changed from new to closed

I'm glad you got it working. I'll close the ticket.

Note: See TracTickets for help on using tickets.