Bugzilla – Bug 136843
Installation on HP dx5150 MT fails in 64bit mode
Last modified: 2006-02-15 08:45:00 UTC
Installation of SUSE 10.0-64bit fails on a HP dx5150 MT. After loading the kernel the screen goes black and that's it. Same result with "save settings". 32bit installation works. I've also tested SUSE 9.3-64bit: works also. Details: System: Hewlett Packard hp dx5150 MT (PE679AV) http://h10010.www1.hp.com/wwpc/us/en/sm/WF06a/12454-64287-89301-321860-f49-457124.html Mainboard: MSI MS 7050 BIOS: Phoenix 1.06 (09/07/2005) Chipset: ATI XPress 200 CPU: AMD Athlon64-3000 RAM: 2,5 GB (2*256MB + 2*1GB) HD: Samsung SATA 160 GB (HD160JJ) DVD: Lite-On DVDRW SOHW-1673S output of lspci (SUSE9.3-64bit): 0000:00:00.0 Host bridge: ATI Technologies Inc: Unknown device 5950 (rev 01) 0000:00:01.0 PCI bridge: ATI Technologies Inc: Unknown device 5a3f 0000:00:05.0 PCI bridge: ATI Technologies Inc: Unknown device 5a37 0000:00:12.0 IDE interface: ATI Technologies Inc: Unknown device 4379 0000:00:13.0 USB Controller: ATI Technologies Inc: Unknown device 4374 0000:00:13.1 USB Controller: ATI Technologies Inc: Unknown device 4375 0000:00:13.2 USB Controller: ATI Technologies Inc: Unknown device 4373 0000:00:14.0 SMBus: ATI Technologies Inc: Unknown device 4372 (rev 10) 0000:00:14.1 IDE interface: ATI Technologies Inc: Unknown device 4376 0000:00:14.3 ISA bridge: ATI Technologies Inc: Unknown device 4377 0000:00:14.4 PCI bridge: ATI Technologies Inc: Unknown device 4371 0000:00:14.5 Multimedia audio controller: ATI Technologies Inc: Unknown device 4370 (rev 01) 0000:00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 0000:00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map 0000:00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller 0000:00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 0000:01:05.0 VGA compatible controller: ATI Technologies Inc: Unknown device 5954 0000:01:05.1 Display controller: ATI Technologies Inc: Unknown device 5854 0000:02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5751 Gigabit Ethernet PCI Express (rev 20)
Can you try to experiment with vga=normal, nmi_watchdog=1, acpi=on/off/force to see whether some option is capable of reviving the system or at least capturing a trace? Please report how this goes, if a crash or a panic results, please paste this here.
No feedback as requested in comment #1. Please re-open if problems persist and if more information is available.
These are the last lines of output before the kernel hangs (no errors etc.) when acpi=on & acpi=force: ACPI: Assume root bridge [.\_SB_.PCI0] bus is 0 when acpi=off: PCI: Probing PCI hardware (bus 00)
Sounds like an ACPI issue, then.
Please try the boot params in the following order until you can boot: pci=noacpi, noapic (if it does not help, try both). Have you already installed the latest YOU update kernel, if not, please do so. If it does boot with pci=noacpi, it's likely that this already got fixed. Please reopen if you still encounter problems. BTW: Please also ensure you have the latest BIOS installed.
FYI: Workaround is to specify noapictimer as boot argument Still reproducable with 2.6.13-15.7-default
There are know problems on x86_64 with ATI chipsets. Stuff I know is: wrong time, cannot shutdown, ..., not booting is new but seem to have the same cause: a broken (apic?) timer... Andi has added a patch to current SL 10.1, but it does not work well... I didn't have time to dig in deeper. It would be helpful if you could install the latest 10.1 Open SUSE and report back. Also have a look at #145747 for some boot parameters you might want to play with ... Please also reopen the bug if you still have problems with 10.1.
Besides hanging on boot i did not actually encounter any problems (single core CPU). The noapictimer boot param works around this for all dx5150 that we use. My commend was mostly intended as FYI to document the workaround i found. BTW: Not booting is not exactly new. This bug is about this issue :-) #145747 is locked If i can find some time i'll try to get a SL10.1 beta and check if its fixed. I will re-open the bug then.
Thanks. I changed the product for #145747. Can you now access the bug?
Just tested with SL10.1 beta3. dx5150 boots fine no boot param needed. Time keeping seems ok as well. Could not test beyond install boot due to crash with xfs mount. I can now access #145747, thanks. -> no longer a problem
Please also try beta4 which comes out soon. There are still changes pending as IIRC not all machines work that fine...