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: Fri, 25 Nov 2005 22:51:57 -0500 [thread overview]
Message-ID: <200511252251.58027.dtor_core@ameritech.net> (raw)
In-Reply-To: <20051124085018.GB7799@stiffy.osknowledge.org>
On Thursday 24 November 2005 03:50, Marc Koschewski wrote:
> * Dmitry Torokhov <dtor_core@ameritech.net> [2005-11-23 20:57:43 -0500]:
>
> > 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.
>
> Oh! I didn't know. Is there any good reason to do so? I mean, any device
> change (ie. serial port re-configuration) is just valid from next reboot, thus
> not affecting the running kernel. Am I missing something?
>
ACPI takes control over entire box, from that point on you can't enter
pretty much any BIOS code. FWIW one ACPI is active it does not work in
Windows either.
--
Dmitry
prev parent reply other threads:[~2005-11-26 3:52 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
2005-11-24 8:50 ` Marc Koschewski
2005-11-26 3:51 ` Dmitry Torokhov [this message]
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=200511252251.58027.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.