UNSOLVED

teedog

updated

22 years ago

T

teedog

11 Posts

0

18779

May 29th, 2004 08:00

Dell Inspiron with broken BIOS detected...

I am running Linux on my Dell Inspiron 600m. My BIOS version is the latest, A11.

When booting up (kernels 2.4 through 2.6.6), I receive the following message:
"Dell Inspiron with broken BIOS detected. Refusing to enable the local APIC."

From what I've found through Google, this seems to be a bug introduced by Dell in newer BIOS versions. There are a few threads on the forums here about the broken BIOS but there is no solution.

On this page http://www.bay-wolf.com/flashbios.htm , it says:
"If you are using Linux on an Inspiron 8000, do not upgrade the BIOS beyond version 17. All of the subsequent BIOS images are flawed. The kernel gives this message - 'Dell Inspiron with broken BIOS detected. Refusing to enable the local APIC.'"

I realize that Dell does not officially support Linux, but fixing a bug in the BIOS is the least they can do to keep us Linux users happy; we are not asking for any documentation or hand-holding here.

Thanks in advance.

Message Edited by teedog on 05-29-2004 02:16 PM

  • HALO PRO

    2 Intern

    •

    357 Posts

    838

    0

    Posted May 29th, 2004 09:00

    The latest 600m bios is A11. Did you maybe get the wrong bios for the wrong system? Also the problem with the new bioses is in video games only!

    Message Edited by HALO PRO on 05-29-2004 06:43 AM

  • teedog

    11 Posts

    838

    0

    Posted May 29th, 2004 17:00

    Sorry, I mistyped. I indeed have A11 installed, which is the latest. Do you not get the broken BIOS message?

    If I run "dmesg", I see the message at the very top when the boot process begins:
    BIOS-provided physical RAM map:
    BIOS-e820: 0000000000000000 - 000000000009f000 (usable)
    BIOS-e820: 000000000009f000 - 00000000000a0000 (reserved)
    BIOS-e820: 0000000000100000 - 0000000027fae000 (usable)
    BIOS-e820: 0000000027fae000 - 0000000028000000 (reserved)
    BIOS-e820: 00000000feda0000 - 00000000fee00000 (reserved)
    BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved)
    639MB LOWMEM available.
    On node 0 totalpages: 163758
    DMA zone: 4096 pages, LIFO batch:1
    Normal zone: 159662 pages, LIFO batch:16
    HighMem zone: 0 pages, LIFO batch:1
    DMI 2.3 present.
    Dell Inspiron with broken BIOS detected. Refusing to enable the local APIC.

    APIC is important not only for gaming. It can help resolve resource conflicts during system load that lead to audio glitches and poor interactive performance. See this page for more info:
    http://www.microsoft.com/whdc/system/sysperf/apic.mspx

    We want APIC enabled if at all possible.

    Message Edited by teedog on 05-29-2004 02:21 PM

  • 838

    0

    Posted May 30th, 2004 09:00

    this is a very common error message in almost all dell laptops I have. IIRC, it's something to do with bad ACPI information in the bios - just buggy. It's a known error so the kernel just works around it.

    It's quite widespread, so I don't see any reason dell will decide to fix it now. Are there any acpi things you can't do? I wouldn't worry about it...

    cheers
  • teedog

    11 Posts

    838

    0

    Posted May 30th, 2004 18:00

    Correct me if I'm wrong, but this is an APIC issue, not ACPI. ACPI, or Advanced Configuration and Power Interface, is working fine on my end (in fact, my 600m runs cooler in Linux than in Windows due to the cpu freq scaling features).

    One of APIC's (not ACPI) functions, as mentioned above, is to resolve resource conflicts, like audio glitches during high system load. The inability to load APIC is not fatal, but there is no reason we should be satisfied with it.

    I don't see how Dell has good reasons not to fix a problem just because it is widespread; isn't the fact that the problem is widespread all the more reason to fix it?

    Message Edited by teedog on 05-30-2004 03:32 PM

  • 838

    0

    Posted May 31st, 2004 06:00

    hmmmmm, ok, now I'm not quite sure on this. On the one hand, what you're saying certainly makes sense - the APIC helps out with interrupt stuff.

    But on the other hand, it's mentioned (at least on my laptop) in the middle of all the ACPI bootup messages. Google is a bit inconclusive. I'm not sure whether lots of people have just confused APIC/ACPI, or if it's accurate, or if it's a single confusion that google searches have propagated. I think that there is some interrupt/IRQ sharing that goes on with ACPI too, so that muddies the waters (in my head at least).

    anyway, you're correct - it's not fatal and it's certainly not optimal. But it's also common and widespread and dell looks unlikely to fix the situation :-(

    if you actually know what the APIC does, please enlighten me - I'm a bit hazy :-)

    cheers
  • 838

    0

    Posted June 8th, 2004 05:00

    Have a look at this page: http://www.hyperdictionary.com/computing/advanced+programmable+interrupt+controller

    As you can see, APIC really exists and it's not just s.th. that has been created because of misspelling.

    APIC = Advanced Programmable Interrupt Controller
    ACPI = Advanced Configuration and Power Interface

    To find out more what APIC does, use "Advanced Programmable Interrupt Controller" as keyword.

    I hope i could help you with this.

  • teedog

    11 Posts

    838

    0

    Posted June 8th, 2004 13:00

    http://www.microsoft.com/whdc/system/sysperf/apic.mspx
    See that page for why APIC is important not only for multi-CPU systems but for single-processor systems as well.

    Message Edited by teedog on 06-08-2004 10:14 AM

  • mjcramer

    4 Posts

    838

    0

    Posted July 3rd, 2004 00:00

    Here, this should explain some of it...

    http://www.ussg.iu.edu/hypermail/linux/kernel/0301.2/0820.html
  • teedog

    11 Posts

    838

    0

    Posted July 5th, 2004 21:00

    Finally, here are instructions for enabling local APIC:
  • teedog

    11 Posts

    183

    0

    Posted July 5th, 2004 21:00

    Instructions for how to enable local APIC:
    http://forums.gentoo.org/viewtopic.php?p=1314030