From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624
Description of problem:
severn doesn't boot on Shuttle SN41G2.
last visible message:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. insert CD1 and boot
Actual Results: hanged with last visible message:
Expected Results: installation schould have started
AMD 2500 barton
Seagate IDE 120GB 7200rpm
Samsung DVD/CDRW combo
Does booting with 'linux acpi=off' help?
Other useful command line options to try are nofirewire and nousb.
'linux acpi=off' does help
at the first boot after installation
it hangs now at:
setting the hostname
Can you boot the postinstall kernel with 'acpi=off' as well?
Also, can you post the output of 'dmidecode' (from the kernel-utils package)
Didn't get the dmidecode output, but
http://us.shuttle.com/specs2.asp?pro_id=284 says the mainboard in an
"FN41" with North bridge-Nvidia nForce2, South bridge-nVidia MCP-T
the manual says it has an AwardBIOS, so lets try the Award interrupt patch.
Created attachment 93844 [details]
ACPI VT86/Award PCI interrupt patch.
This patch has fixed the ACPI interrupt problem for similar systems.
Please try applying it to a copy of your Severn BETA1 kernel to
see if works for you too:
~/src/linux-2.4.21-20.1.2024.2.1.nptl> patch -Np1 < ./pci_link-severn.patch
patching file arch/i386/kernel/io_apic.c
patching file arch/i386/kernel/mpparse.c
patching file drivers/acpi/pci_irq.c
patching file drivers/acpi/pci_link.c
patching file include/acpi/acpi_drivers.h
Created attachment 94789 [details]
console output from default severn BETA1 CDROM boot
Created attachment 94790 [details]
console messages from severn BETA1 CDROM boot with pci=noacpi
booted successfully, but didn't recognize the on-board Realtek 8201B NIC
for network install.
Created attachment 94791 [details]
console messages from severn BETA1 CDROM boot with acpi=off
added Intel Pro100 NIC, booted acpi=off, and successfully network installed.
Created attachment 94794 [details]
Created attachment 94795 [details]
Created attachment 94796 [details]
dmesg output from booting 2.4.22-1.2051.nptl kernel
went to http://rhn.redhat.com and downloaded the 2.4.22-1.2051.nptl kernel
from channel "Red Hat Linux (Severn) 9.0.93 - Beta Updates"
It booted on this box per the attached console messages.
ACPI: Subsystem revision 20030813
ACPI: Interpreter disabled.
Created attachment 94797 [details]
dmesg output from booting 2.4.22-1.2051.nptl kernel w/ acpi=force
The latest Red Hat kernel also boots if I manually force ACPI to be enabled
with cmdline acpi=force
/proc/interrupts is the same with acpi enabled or disabled, modulo the
the addition of the acpi interrupt:
[root@dhcppc12 shuttle]# cat /proc/interrupts
0: 34366 XT-PIC timer
1: 4 XT-PIC keyboard
2: 0 XT-PIC cascade
3: 0 XT-PIC usb-ohci
4: 307 XT-PIC serial
5: 0 XT-PIC ehci_hcd
8: 1 XT-PIC rtc
9: 53 XT-PIC acpi
10: 3 XT-PIC ohci1394
11: 956 XT-PIC usb-ohci, eth0
12: 36 XT-PIC PS/2 Mouse
14: 4089 XT-PIC ide0
15: 22 XT-PIC ide1
beta2 works fine then I guess ?
beta2 did not recognize my Sony G400 monitor
the rest went fine
The monitor issue is seperate from this bug. Please open a separate bug report
Created attachment 94822 [details]
dmesg output from booting 2.4.22-1.2061.nptl w/ acpi=force
yes, Fedora beta2 boots fine with acpi=force.
This option is needed because the kernel shipped with acpi_disabled by default.
Does it boot & work ok without acpi too ?