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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
