1.8.x: ACPI problems
qhwt+dfly at les.ath.cx
Fri Mar 2 19:44:01 PST 2007
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?
> >> 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...
> 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?).
More information about the Bugs