[opensuse] Trouble installing openSuSE 10.2 due to pci_init
Hello: I am having difficulty upgrading my openSuSE 10.1 installation to openSuSE 10.2. In fact, my difficult arises from the fact that I cannot reliably boot into the installation program. Background: (1) I have a Tyan K8HM 3892S motherboard and two dual-core Opterons. (2) I installed the latest BIOS (1.05). I tried a number of BIOS settings but they are currently set to "optimal defaults". (3) openSuSE 10.1 runs without any known problems. Originally I had the double realtime clock issue but a previous BIOS update fixed that. (4) I'm using the openSuSE 10.2 install DVD. I checked the MD5 and it matched. I have also burned a number of DVDs, even using different programs and the behavior is consistent. Issue: (1) The DVD starts to boot. In fact I can get to the "main screen" where I can select to "Boot from the Hard Drive", "Install", ... (2) When I select install to start the upgrade, usually the system hangs. (3) I installed using text mode and the initcall_debug kernel option and I can see progress up until the following: Calling initcall 0xffffffff80317987: pci_init +0x0/0x2b() What I find weird is that sometimes the system will get into the install program, but the vast majority of the time it will not. So it's intermittent. I haven't been able to identify any pattern that I can use to predict whether it'll work on any given boot sequence. Does anyone have any suggestions? This isn't a crisis since I have 10.1 working well, it's just that I really wanted to upgrade to 10.2. Of course I'm willing to provide additional information to the best of my ability. I'm somewhat competent, but must admit that I'm a little out of my comfort zone. Any help or suggestions would be greatly appreciated. Thank you. Brian Schang -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
brian_linux wrote:
Any help or suggestions would be greatly appreciated.
Did you try a media check? You can do that in Yast in any working SUSE system. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
James (et al): Sunday, January 21, 2007, 11:32:03 AM, you wrote:
Did you try a media check? You can do that in Yast in any working SUSE system.
Thanks for the response. Yes I checked the media, it's clean. Any other thoughts? -- Brian -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 21 January 2007 10:20, brian_linux wrote:
Hello:
I am having difficulty upgrading my openSuSE 10.1 installation to openSuSE 10.2. In fact, my difficult arises from the fact that I cannot reliably boot into the installation program.
Background: (1) I have a Tyan K8HM 3892S motherboard and two dual-core Opterons. (2) I installed the latest BIOS (1.05). I tried a number of BIOS settings but they are currently set to "optimal defaults". (3) openSuSE 10.1 runs without any known problems. Originally I had the double realtime clock issue but a previous BIOS update fixed that. (4) I'm using the openSuSE 10.2 install DVD. I checked the MD5 and it matched. I have also burned a number of DVDs, even using different programs and the behavior is consistent.
Issue: (1) The DVD starts to boot. In fact I can get to the "main screen" where I can select to "Boot from the Hard Drive", "Install", ... (2) When I select install to start the upgrade, usually the system hangs. (3) I installed using text mode and the initcall_debug kernel option and I can see progress up until the following:
Calling initcall 0xffffffff80317987: pci_init +0x0/0x2b()
What I find weird is that sometimes the system will get into the install program, but the vast majority of the time it will not. So it's intermittent. I haven't been able to identify any pattern that I can use to predict whether it'll work on any given boot sequence.
Does anyone have any suggestions? This isn't a crisis since I have 10.1 working well, it's just that I really wanted to upgrade to 10.2.
Brian Schang
You probably need to provide a kernel boot parameter during install such as nosmp, acpi=off, noapic, etc. You didn't say whether you tried the Failsafe mode install. If Failsafe works then you know its most likely ACPI, APIC or interrupt related. This may only need to be done for the install/upgrade. Stan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Stan: Sunday, January 21, 2007, 1:06:14 PM, you wrote:
You probably need to provide a kernel boot parameter during install such as nosmp, acpi=off, noapic, etc. You didn't say whether you tried the Failsafe mode install. If Failsafe works then you know its most likely ACPI, APIC or interrupt related. This may only need to be done for the install/upgrade.
Thanks for the feedback. I'm sorry that I didn't provide more details. Anyway, I did have success getting the installer to run reliably when I used the 'noapic' option. However given that I have a multiple CPU machine, I was reluctant to get too excited when it seemed to work. I understand what you're saying, but at the same time I'm confused. Please help me understand; I've assumed that if I need to use 'noapic' to get the kernel on the install DVD to run than I would also need it to get the final installed kernel to run also. Why is it that I might only need 'noapic' during the update? Thanks again. -- Brian -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 21 January 2007 13:29, Brian S. Schang wrote:
Thanks for the feedback. I'm sorry that I didn't provide more details.
Anyway, I did have success getting the installer to run reliably when I used the 'noapic' option. However given that I have a multiple CPU machine, I was reluctant to get too excited when it seemed to work.
I understand what you're saying, but at the same time I'm confused. Please help me understand; I've assumed that if I need to use 'noapic' to get the kernel on the install DVD to run than I would also need it to get the final installed kernel to run also. Why is it that I might only need 'noapic' during the update?
Thanks again. Brian
There's no way to have available all possible driver combinations during install. Using kernel boot parameters during install gives the system a chance at getting the basics installed, figuring out what hardware there is and installing those drivers prior to the first real boot. On my now ancient system I used to have to install with failsafe but since 9.3 or so my drivers have become more mainstream and everything loads very well now. Try Failsafe for install. If that works, great. The Failsafe parameters are not permanent. The install will try to get the kernel boot commands right for that system. For reliable operation this system may need specific kernel boot commands such as 'noapic' or 'acpi=off' or whatever. Failsafe also includes 'nosmp' which makes the install run on 1 processor. Maybe install isn't smp aware/capable on your system. Stan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
Brian S. Schang -
brian_linux
-
James Knott -
S Glasoe