From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Marc Koschewski <marc@osknowledge.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Entering BIOS on DELL mobiles - does the kernel prohibit?
Date: Wed, 23 Nov 2005 20:57:43 -0500 [thread overview]
Message-ID: <200511232057.44022.dtor_core@ameritech.net> (raw)
In-Reply-To: <20051123155319.GA6970@stiffy.osknowledge.org>
On Wednesday 23 November 2005 10:53, Marc Koschewski wrote:
> Hi all,
>
> first of all, if someone could point me to some information on that
> topic, I would be glad. I didn't find anything on Google.
>
> The 'problem' is: I remember being able to enter the DELL Inspiron BIOS
> from a running X session (or console) some (long) time ago. I just noticed,
> it no longer works. Does the kernel somehow prohibit to enter the BIOS
> or does the laptop itself stop from doing so (maybe due to a BIOS update).
>
It is only pssible with APM. ACPI "kills" it.
--
Dmitry
next prev parent reply other threads:[~2005-11-24 1:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-23 15:53 Entering BIOS on DELL mobiles - does the kernel prohibit? Marc Koschewski
2005-11-24 1:57 ` Dmitry Torokhov [this message]
2005-11-24 8:50 ` Marc Koschewski
2005-11-26 3:51 ` Dmitry Torokhov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200511232057.44022.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marc@osknowledge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox