Gateway DX4720-03 apic problem
I have a new Gateway DX4720-03 PC and have discovered that it won't install Fedora 10 unless I give the kernel boot option "noapic" or "nolapic".
This system's processor is the Intel Pentium Dual Core E5200.
It would seem that this is either a kernel bug to be fixed, or a documentation bug so users of this machine know about the workaround. I'll report the bug if someone will tell me how.
Quoted 9 lines · On Sun, 25 Jan 2009 11:35:46 -0800 Charles Landau <[email protected]> wrote:
I have a new Gateway DX4720-03 PC and have discovered that it won't install Fedora 10 unless I give the kernel boot option "noapic" or "nolapic".
This system's processor is the Intel Pentium Dual Core E5200.
It would seem that this is either a kernel bug to be fixed, or a documentation bug so users of this machine know about the workaround. I'll report the bug if someone will tell me how.
It should only be necessary if the system has BIOS problems. File a report anyway and include the lspci -vvxxx and dmidecode data as attached files
Quoted 5 lines · Charles Landau
I have a new Gateway DX4720-03 PC and have discovered that it won't install Fedora 10 unless I give the kernel boot option "noapic" or "nolapic".
This system's processor is the Intel Pentium Dual Core E5200.
It would seem that this is either a kernel bug to be fixed, or a documentation bug so users of this machine know about the workaround. I'll report the bug if someone will tell me how.
I think you just did report it :-)
Well, it's something that should be fixed in the kernel, either it's a kernel bug or hardware busted in some way that we should be detecting.
How is it failing to install, is it locking up at some point, etc?
Quoted 5 lines · Robert Hancock
Quoted 4 lines · Charles Landau
I have a new Gateway DX4720-03 PC and have discovered that it won't install Fedora 10 unless I give the kernel boot option "noapic" or "nolapic".
This system's processor is the Intel Pentium Dual Core E5200.
Quoted 13 lines
Quoted 1 line
It would seem that this is either a kernel bug to be fixed, or a documentation bug so users of this machine know about the workaround. I'll report the bug if someone will tell me how.
I think you just did report it :-)
Well, it's something that should be fixed in the kernel, either it's a kernel bug or hardware busted in some way that we should be detecting.
How is it failing to install, is it locking up at some point, etc?
Signature · 4 lines
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
My guess is that anaconda fails at some point regarding storage options.
Quoted 5 lines · Robert Hancock
Quoted 4 lines · Charles Landau
I have a new Gateway DX4720-03 PC and have discovered that it won't install Fedora 10 unless I give the kernel boot option "noapic" or "nolapic".
This system's processor is the Intel Pentium Dual Core E5200.
Quoted 7 lines
Quoted 1 line
It would seem that this is either a kernel bug to be fixed, or a documentation bug so users of this machine know about the workaround. I'll report the bug if someone will tell me how.
I think you just did report it :-)
Well, it's something that should be fixed in the kernel, either it's a kernel bug or hardware busted in some way that we should be detecting.
How is it failing to install, is it locking up at some point, etc?
When I boot off the Fedora 10 full distribution DVD, which I believe is kernel 2.6.27.5, at the first screen, "Welcome to Fedora 10!", I tell it to Install or upgrade, and then I get a variety of errors on the text console, including:
ata1.00 failed to IDENTIFY
and
PNP: PS/2 appears to have AUX port disabled ...
and problems enumerating USB devices, and
ehci_hcd 0000:00:04.1: Unlink after no_IRQ? Controller is probably
using the wrong IRQ.
and
ohci_hcd 0000:00:04.0: Unlink after no_IRQ? Controller is probably
using the wrong IRQ.
after which it does nothing. There is no power to USB and PS/2 devices.
Let me know any other ways I can help you diagnose this.