From: Dan Jacobson <jidanni@jidanni.org>
To: linux-kernel@vger.kernel.org
Subject: Re: kernel-parameters.txt: expand APIC
Date: Tue, 19 Dec 2006 05:58:46 +0800 [thread overview]
Message-ID: <87d56ghnmx.fsf@jidanni.org> (raw)
In-Reply-To: Pine.LNX.4.61.0612182053260.29144@yvahk01.tjqt.qr
>> kernel-parameters.txt says what ACPI and APM stand for, but not APIC.
J> Advanced PIC, most likely.
Also say what PIC means.
J> http://en.wikipedia.org/wiki/APIC will tell more.
Not when one is having booting problems and can't connect their modem.
>> Also there give some basic apm related parameters, instead of just
>> saying see apm.c, which the user is less likely to have handy than
>> kernel-parameters.txt.
J> As always, patches welcome :)
apm.c is in a Debian package that is too big for me to download before
my next trip to town. So for now I will just put
append="apm=off" as a guess in lilo, as there is no basic mention of
how to turn it off in kernel-parameters.txt, as an attempt to stop the
total power off that happens on my first boot of the day after 10 or
15 minutes.
What I'm saying is that your files should be more self-contained.
apic= [APIC,i386] Change the output verbosity whilst booting
Format: { quiet (default) | verbose | debug }
Change the amount of debugging information output
when initialising the APIC and IO-APIC components.
apm= [APM] Advanced Power Management
See header of arch/i386/kernel/apm.c.
Drat. All they had to do was add one little
Format: { ... }
line with the answers. Instead one needs to have the source code to
find the answer. Multi megabyte download just for one line of
information. And the user might be at a remote site with no net
connection too.
prev parent reply other threads:[~2006-12-18 22:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-18 13:40 kernel-parameters.txt: expand APIC jidanni
2006-12-18 19:54 ` Jan Engelhardt
2006-12-18 21:58 ` Dan Jacobson [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=87d56ghnmx.fsf@jidanni.org \
--to=jidanni@jidanni.org \
--cc=linux-kernel@vger.kernel.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