On Friday 10 December 2004 07:30 pm, RickSisler wrote:
> Kaj Haulrich ([EMAIL PROTECTED]) wrote:
> > On Friday 10 December 2004 21:47, Tom Brinkman wrote:
> > > On Friday 10 December 2004 08:53 am, Keith Powell wrote:
> > > > > In /etc/lilo.conf try editing the append-line,
> > > > > especially the apic thing. Remove it completely or set
> > > > > it to apic=ht or noapic.
> > > > >
> > > > > HTH
> > > > > Kaj Haulrich.
> > > >
> > > > Thanks, Kaj.
> > > >
> > > > apic=off �has solved it.
> > > >
> > > > The append line was already �apic=ht, �so I first changed
> > > > it to noapic and then �apic=noapic. Neither had any
> > > > effect.
> > >
> > > For proper and valid kernel parameters give
> > > kernel-parameters.txt a thorough read. You'll need to
> > > have kernel-source installed, as it contains the file. eg,
> > > /usr/src/linux-2.6.8.1-20mdk/Documentation/kernel-parameter
> > >s.txt Or you might Google for the file for your kernel.
> > >
> > > Many of the parameters I see in various ML posts are
> > > not valid (possibly undocumented) and are ignored by the
> > > kernel, ie, 'no effect'.
> > >
> > > APIC, advance programable interrupt control. If your
> > > system works better with 'noapic', then what this really
> > > means is you have non-compliant and/or deficient hardware
> > > bordering on the 'designed for windoze' variety.
> > >
> > > Disabling ACPI and/or APIC is best avoided when not
> > > absolutely necessary, to deal with sloppy, sub-standard
> > > hardware. Tho in fairness, other popular distros do
> > > disable them by default. If your system can't use these
> > > advanced features, don't kid youself with believing that
> > > optimization for i586, i686, or K7, compiling with PREEMPT
> > > and such, will provide any benefit.
> >
> > Tom, does that mean, that an empty append line defaults to
> > booting with both enabled ?
> >
> > Kaj Haulrich.
>
> Kaj,
> as Tom said,"you'll need the kernel sources installed"
> and the place to look for default kernel info is in:
>
> $ cd /usr/src/linux/arch/i386/
>
> *linux* should be a symlink but YMMV..
> which contains the default configs for many different kernels.
> So for example, mine is:
>
> #> uname -sr
> Linux 2.6.8.1-12mdk
>
> since we're in the proper dir..
> we grep the file for "apic" :
> #> cat defconfig |grep -i acpi
> # Power management options (ACPI, APM)
> # ACPI (Advanced Configuration and Power Interface) Support
> CONFIG_ACPI=y
> CONFIG_ACPI_BOOT=y
> CONFIG_ACPI_INTERPRETER=y
> CONFIG_ACPI_SLEEP=y
> CONFIG_ACPI_SLEEP_PROC_FS=y
> CONFIG_ACPI_AC=m
> CONFIG_ACPI_BATTERY=m
> CONFIG_ACPI_BUTTON=m
> CONFIG_ACPI_FAN=m
> CONFIG_ACPI_PROCESSOR=m
> CONFIG_ACPI_THERMAL=m
> CONFIG_ACPI_ASUS=m
> CONFIG_ACPI_TOSHIBA=m
> # CONFIG_ACPI_DEBUG is not set
> CONFIG_ACPI_BUS=y
> CONFIG_ACPI_EC=y
> CONFIG_ACPI_POWER=y
> CONFIG_ACPI_PCI=y
> CONFIG_ACPI_SYSTEM=y
> CONFIG_ACPI_INITRD=y
> CONFIG_ACPI_TC1100=m
> CONFIG_X86_ACPI_CPUFREQ=m
> # CONFIG_X86_ACPI_CPUFREQ_PROC_INTF is not set
> CONFIG_X86_POWERNOW_K7_ACPI=y
> CONFIG_X86_POWERNOW_K8_ACPI=y
> CONFIG_X86_SPEEDSTEP_CENTRINO_ACPI=y
> CONFIG_HOTPLUG_PCI_ACPI=m
> CONFIG_SERIAL_8250_ACPI=y
> CONFIG_SERIAL_WACOM_ACPI=m
>
> Then also grep for "apic":
> #> cat defconfig |grep -i apic
> CONFIG_X86_GOOD_APIC=y
> CONFIG_X86_UP_APIC=y
> CONFIG_X86_UP_IOAPIC=y
> CONFIG_X86_LOCAL_APIC=y
> CONFIG_X86_IO_APIC=y
>
> I got this info from Thomas Backlund from lurking the "expert
> list" earlier this year.
>
> So it would seem *yes* Kaj, it is on by default.
>
> HTH
I appreciate the addition Rick. Let me take this opportunity
to add a caution to your post, but more so to previous replies I
sent in this thread.
** Unless you know what you're doing, don't edit kernel config
files by hand and then compile a kernel **
I do, but then I'm a reckless idiot ;> Many of y'all have
run 'make menuconfig' or 'make xconfig' and noticed that when you
changed somethin, some, sometimes many other options either were
greyed out (disabled), or became enabled.
This automatically protects you against setting conflicting
compile options, and/or automatically presents others
appropriately. This protection is not afforded if you edit
kernel configs manually.
Still as Rick has very well illustrated, you should take a look
and get familiar with the kernel options, features, and
capabilities which are Linux. The very heart of your system, and
a good place to begin diagnosing peculiar problems. A little
knowlege in this basic area will lead you to other involved
processes, like various init functions that have a lot to do with
booting up, or shutting down, and everything in between.
--
Tom Brinkman Corpus Christi, Texas
Proud to be an American
____________________________________________________
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
Join the Club : http://www.mandrakeclub.com
____________________________________________________
