mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: mike heffner <mdheffner@yahoo.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Frank.Otto@tc.pci.uni-heidelberg.de, linux-kernel@vger.kernel.org
Subject: Re: PROBLEM:  conflict between apm and system clock on Inspiron 8100
Date: Thu, 29 Aug 2002 17:33:38 -0700 (PDT)	[thread overview]
Message-ID: <20020830003338.86493.qmail@web40208.mail.yahoo.com> (raw)
In-Reply-To: <20020830094825.75fd8519.sfr@canb.auug.org.au>

Hi Shephen,

I tried this early on, but I just tried it again to
make sure.  There is no noticeable effect from setting
apm=allow_ints at the boot prompt.  So either my
command is not getting set, or the BIOS itself is
restricting the interrupts?  Is there a way to check
that I did indeed allow interrupts?
  I don't know much about BIOS hacking, any
suggestions about how to get the code for the BIOS
(other than disassembling it)?  I bet Dell isn't going
to give it to me.  I am struggling to get them to even
understand the problem.

Thanks,
Mike


--- Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> 
> OK, for the Dells, we autodetect the 4000 series and
> allow
> interrupts during BIOS calls, but not the 8000's
> (unless
> your RedHat patched kernel does this).  So could you
> try
> booting with "apm=allow_ints" on the command line
> (or load
> the apm modules with "allow_ints=1"). and try again.
>  If
> this changes things, then we need to add the 8100 to
> the
> list of things we automatically allow interrupts
> for.
> 
> The default from the very beginning has been to
> disable interrupts
> and on most machines this works fine.  The option of
> leaving
> interrupts enabled was introduced when we discovered
> that the
> Thinkpads won't resume if you disable them ...
> 


__________________________________________________
Do You Yahoo!?
Yahoo! Finance - Get real-time stock quotes
http://finance.yahoo.com

  reply	other threads:[~2002-08-30  0:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-26  8:14 mike heffner
2002-08-26  9:55 ` Alan Cox
2002-08-26 17:00   ` mike heffner
2002-08-26 17:08     ` Alan Cox
2002-08-28 15:04       ` Frank.Otto
2002-08-28 17:00         ` mike heffner
2002-08-29 12:42           ` Frank Otto
2002-08-29  2:11         ` Stephen Rothwell
2002-08-29 12:25           ` Frank Otto
2002-08-29 17:19           ` mike heffner
2002-08-29 23:48             ` Stephen Rothwell
2002-08-30  0:33               ` mike heffner [this message]
2002-08-30 11:39           ` Frank Otto

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=20020830003338.86493.qmail@web40208.mail.yahoo.com \
    --to=mdheffner@yahoo.com \
    --cc=Frank.Otto@tc.pci.uni-heidelberg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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

all inboxes | Powered by JetHome®