I've been doing the install in Failsafe mode all along, actually. All the machines are the same rev of the BIOS, and the only hardware difference, AFAIK, is the amount of memory. Chris St. Pierre Unix Systems Administrator Nebraska Wesleyan University On Tue, 18 Oct 2005, Stan Glasoe wrote:
On Tuesday 18 October 2005 2:39 pm, Chris St. Pierre wrote:
I'm afraid that didn't work, either. Any other ideas?
Chris St. Pierre Unix Systems Administrator Nebraska Wesleyan University
On Tue, 18 Oct 2005, Steve Graegert wrote:
On 10/18/05, Chris St. Pierre
wrote: I'm afraid not. The one that succeeded had 196 Mb RAM; one that failed also had 196 Mb and the other had 128 Mb. I tried bumping one of the failures up to 320 Mb, but it still didn't work. I know the memory is good, as this box has been housing a production system for nearly six months.
I suspect the device mapper module (dm_mod) to be the culprit. I am not sure if a text-based install is still possible, but if so, try starting the installation in textmod and try to switch to another console an unload (rmmod dm_mod) the device mapper module if loaded. Since I haven't done a text-based installation for years I can't be more precise here. Repeat this procedure before the second CD is read by YaST. Hope this points you to the right direction.
\Steve
Failsafe install choice? If that works then its figuring out which parameter(s) is the problem. Try acpi=off, apm=on first and go from there.
Are these trouble system's BIOS all updated? Are there any known hardware differences between these problem machines and the ones that Just Work(TM)? At this point in the install you aren't at the hardware config for video card, NICs, TV cards, printers, etc IIRC. So I would look for ACPI versus APM, etc.
Stan
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com