I had the same problem and I fixed it. It was caused By the yast installer at install time because it mistakenly detected my system as being a symetric multi prossesing system with more than one processor. It accordingly installed and SMP linux kernal instead of the regular one. There are several linux kernals that can be installed but unfortunately in the SuSE 8.0 setup what yast auto detects as far as what kind of mainboard and processors we have is not confirmed with the user before it picks a kernal to install. We should be asked, and also allowed to pick our kernel of choice. Solution. Linux is a modular OS unlike windows and we can find out which kernal the system is using with yast in yast2 software install/remove software the in the catagory system/kernal then verify that you do not have the k_smp kernal installed if it is it will have an i next to it if it is installed then select it to be removed/ deleted AND MAKE SURE TO SELECT k_deflt which is the default kernel for a system with on processor when selected for install it will have an X next to it dont worry it wont hurt anything doing this it is safe as you can boot in safe mode if all else fails and reinstall the kernel This should allow the OS's pm calls to be in the proper format for your mainboard max On Monday 03 June 2002 09:27 pm, Brian Durant wrote:
On Tuesday 04 June 2002 09:26, Thom Nuzum wrote: - I too can't powerdown properly and also changed "apm=on". On shutdown my - system ends as follows: - - "The system will be halted immediately" - "segmentation fault" - "master resource control runlevel 0--reached" - "skipped services in runlevel 0---reached" - - Not sure what's going on but some fan(s) seems to wind down with my - monitor stuck on this last line.My system is dual boot and Win98 shuts - down fine.(Incidentally W98 starts up about 5 times faster now that i - got 256DDR Ram on the Athlon. No noticable increase in my Linux - starting-up.) - Help with shutdown would be appreciated.
Same here with SuSE 7.3 Pro and a Soyo Dragon Plus motherboard and AMD 1800+ XP chip. Nothing so far has helped. Seems like a SUSE <--> BIOS thing. I would have thouhgt that this would have been ironed out in 8.
Brian
-- Remember: Always think positively. You will prevail.