1.8.x: ACPI problems REPOST

Tero Mäntyvaara termant at gmail.com
Thu Mar 8 22:10:10 PST 2007

YONETANI Tomokazu wrote:
On Thu, Mar 01, 2007 at 02:03:56PM +0200, Tero M?ntyvaara wrote:
YONETANI Tomokazu wrote:
On Wed, Feb 28, 2007 at 05:48:27AM +0200, Tero M?ntyvaara wrote:
When I boot DF normally to ACPI mode and prompt appears, I can't write
anything to prompt.
"prompt" means the login prompt ("login:" or "#")?
I meant login prompt ("login:")
So if you enable ACPI and boot, it won't respond to keyboard no matter
whether you choose to boot into single- or multi-user mode?
Correct. I also noticed that when the login prompt is put on screen, the
num lock -indicator (on keyboard) is on and right after I try to write
something, the light goes off.

But If I boot to non-ACPI-mode, everything works
just fine, but I can't get to sigle user mode, because prompt freezes
there too...
By "everything works just fine" you mean it manages to boot into
multi-user mode in which you see "login:" prompt, but once you issue
# shutdown now
command and it goes to single-user mode, it stops responding to
your key stroke, right?  If so, it sounds like a USB keyboard issue,
but I may be wrong...
When I issue
	# shutdown now

command in non-ACPI multiuser mode, it outputs the same as in section
(3) and after hitting RETURN prompt responds to input normaly.
So ... your keyboard does not work when you boot straight into the
single user mode, whether with or without ACPI driver enabled, right?
If not, I have no idea what this part really means:
  > But If I boot to non-ACPI-mode, everything works
  > just fine, but I can't get to sigle user mode, because prompt freezes
  > there too...
I meant that OS freezes ONLY when ACPI is enabled. The issue was that I
wanted to use single user mode and when I choose it from menu, system
freezed then too and I didn't know how to get to single user mode with
ACPI disabled, but now I do. ;-).

My keyboard (Logitech Internet Pro/Y-sZ49) is not USB-version, it is
connected to PS/2-port.
How should I debug the issue further?
If the message buffer(which dmesg command shows you) survives across
reboot, I'd like to look at it after you boot with ACPI driver enabled
and booted with `boot -v' from the boot loader prompt (did I ask if
keyboard works when you go into the boot loader prompt?).
(1) So you want me to do the following:	
1. Select 6 (Escape to loader prompt) from menu,
2. type boot -v ENTER and
3. reboot (from freeze) and send the content of dmesg to you?
(2) Isn't the content of dmesg ONLY from latest boot?

Keyboard works fine when option 6 is selected. ;-)


(3) Does /var/log/messages adapt to your needs?

Tero Mäntyvaara
My hardware:
- Processor: AMD Athlon 64 3000+ (Socket 939)
- Mobo: Asus A8R-MVP (ATI CrossFireâ„¢ Xpress 1600, Marvell 88E8001)
- Memory: 512 MB (PC-3200/400 MHz)
- Storage: 2 x Samsung SpinPoint P80SD HD080HJ 80 GB  SATA2 NCQ
- Display adapter: Club 3D 6200LE PCI-E CGNX-L628R

More information about the Bugs mailing list