Differences between version 31 and predecessor to the previous major change of TroubleshootingStartUp.
Other diffs: Previous Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 31 | Last edited on Friday, October 21, 2005 2:55:09 pm | by JohnMcPherson | Revert |
| Older page: | version 28 | Last edited on Wednesday, October 19, 2005 8:33:34 pm | by AristotlePagaltzis | Revert |
@@ -7,9 +7,9 @@
Lilo is not correctly set up. (For example, issues with old versions of lilo above block 1024 of the disk drive). See LiloErrorCodes.
!! <tt>Loading Linux.......... Uncompressing the kernel.</tt> (stop)
-# Are you using an InitialRamDisk? If so, do you have <tt>CONFIG_BLK_DEV_RAM</tt> and <tt>CONFIG_BLK_DEV_INITRD</tt> enabled in your kernel?
+# Are you using an InitialRamDisk - initrd(4)
? If so, do you have <tt>CONFIG_BLK_DEV_RAM</tt> and <tt>CONFIG_BLK_DEV_INITRD</tt> enabled in your kernel?
# The kernel was compiled for a different architecture - for example, it has optimisations for [AMD] chips that don't work on an [Intel] chip, or vice-versa. If you changed the architecture of the kernel config (well, for kernel v 2.4 at least), you ''need'' to do a make clean afterwards, otherwise some object files that should be re-compiled aren't.
!! <tt>GRUB</tt> <blinking cursor>
@@ -44,9 +44,9 @@
Various VIA chipset [AMD] Athlon/Duron motherboards (eg KT400, KM266) running kernel 2.4 (e.g. kernel 2.4.21) hang after printing this message. For example, Athlon XP2000+ on an AD77 motherboard (KT400), Athlon XP1800+/XP2400+ on a PC Chips M825L (KM266)). It is caused by [APIC] support in the kernel (not to be confused with [ACPI]). Booting with the <tt>noapic</tt> kernel flag doesn't fix it (although it can make the machine go into an infinite loop printing an error about apic on cpu 0). However, booting with <tt>no__l__apic</tt> kernel flag does in many cases work. Recompiling the kernel without APIC support resolves this. Note that the same motherboards will need the <tt>nolapic</tt> kernel flag to boot Knoppix - otherwise the screen just turns black and the computer hangs.
!! <tt>ACPI: setting ELCR to 0200 (from 1e20)</tt>
-My KT400-based motherboard (that used to give the previous error message under older kernels) hangs immediately after printing this message with [Ubuntu] 5.10's default kernel (2.6.12-6). The message just before it is <tt>ACPI: Looking for DSDT in initrd... not found!</tt> Again, adding <tt>nolapic</tt> to the kernel boot command fixes this. Note that if your distribution uses the <tt>quiet</tt> kernel boot flag to hide all those messages then you'll never know that it's the motherboard
's [ACPI
] support at fault..
.
+My KT400-based motherboard (that used to give the previous error message under older kernels) hangs immediately after printing this message with [Ubuntu] 5.10's default kernel (2.6.12-6). The message just before it is <tt>ACPI: Looking for DSDT in initrd... not found!</tt> Again, adding <tt>nolapic</tt> and <tt>noapic
</tt> to the kernel boot command fixes this. Note that if your distribution uses the <tt>quiet</tt> kernel boot flag to hide all those messages then you'll never know that it's the [BIOS]
's buggy
[APIC
] support at fault. This motherboard is an AD77 flashed with the latest BIOS (2004/11/02) so you will only be able to boot a linux kernel that is compiled or booted without APIC support
.
!! <tt>Warning: unable to open an initial console</tt>
This is usually caused by a failure to find or mount <tt>/dev</tt> or a bad <tt>/dev</tt> being used. When remastering [Knoppix] this can be cause by failing to preserve the special nature of the device files under <tt>/dev</tt> while building remastering. See the <tt>dev</tt> option of mount(8).
