hello. Another thing to try is to see if you can get to the boot prompt and boot the kernel with various options, i.e. -a, -c, and possibly -2, to disable acpi. If -c gets you to a driver selection prompt, then you know the kernel is loaded and ready for you to disable drivers. If you don't get that far, then I'd say it's a boot loader issue. It could be the way the boot loader interacts with the BIOS, but without more info, it's hard to know what, exactly, is going wrong. -Brian
- debugging a kernel that doesn't start Edgar Fuß
- Re: debugging a kernel that doesn't start Robert Swindells
- Re: debugging a kernel that doesn't start Edgar Fuß
- Re: debugging a kernel that doesn't start Mouse
- Re: debugging a kernel that doesn't start Manuel Bouyer
- Re: debugging a kernel that doesn't start Robert Swindells
- Re: debugging a kernel that doesn't start Brian Buhrow
- Re: debugging a kernel that doesn't start Manuel Bouyer
- Re: debugging a kernel that doesn't start Edgar Fuß
- Re: debugging a kernel that doesn't start Manuel Bouyer
- Re: debugging a kernel that doesn't start tlaronde
- Re: debugging a kernel that doesn't start Kengo NAKAHARA
- Re: debugging a kernel that doesn't start Edgar Fuß