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.

Brain maybe you should just use windows then so you will have nothing to wine about or find out what kernel package you have installed and if it is the SMP kernel. As far as the rest of your reply it is irrational and therefore i do not understand it. Both happend to me with SuSE 7.3 and 8.0 but I corrected the problem in both cases it is an apic/apm issue in the case of 7.3 when forced to use install in safe mode APM was disabled in 8 it is a kernel selection problem. The point is if you are not willing to get off your ass and fix it in SuSE 7.3 or 8 then dont whine about it. Just use a newbie OS like Windoze. On Monday 03 June 2002 10:38 pm, Brian Durant wrote:

On Tuesday 04 June 2002 12:07, Max Webb wrote: - 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

In my case, I did post that I am using SuSE 7.3 Pro. I found nothing with k_smp in YAST 2 either. My point wasn't to commandeer the thread, though getting the problem solved would be nice ;-) My point was simply that the problem exists in 7.3 and here we are and 8 does the same thing. Anyone looking for another reason not to upgrade?

Cheers,

Brian

-- Remember: Always think positively. You will prevail.

Hey this guy takes up space on the list telling us how great windoze is and how SuSE Linux sucks. When offered a solution to his so called problem with SuSE linux he doesnt seem interested in getting of his ass to fix the problem. He just wants to whine and tell us how great 98 is. No one is flaming anyone. This is not a Windoze forum nor a Forum for redhat whiners. You either want to solve a problem in life or just act like you do and whine. Linux is an advanced OS and as such is more complicated. Things that are more complex are more prone to problem because of the increased amount of variabled involved. Bye the way, many people have problems with Windoze installs too ... far worse than anything mentioned here. On Monday 03 June 2002 11:07 pm, Matthew Johnson wrote:

On Monday 03 June 2002 22:48, Max Webb wrote:

...

Brain maybe you should just use windows then so you will have nothing to wine about or find out what kernel package you have installed and if it is the SMP kernel. As far as the rest of your reply it is irrational and therefore i do not understand it. Both happend to me with SuSE 7.3 and 8.0 but I corrected the problem in both cases it is an apic/apm issue in the case of 7.3 when forced to use install in safe mode APM was disabled in 8 it is a kernel selection problem. The point is if you are not willing to get off your ass and fix it in SuSE 7.3 or 8 then dont whine about it. Just use a newbie OS like Windoze.

Who is called Brain here? Not sure I see anyone by that name...

Seriously, no need to flame the poor guy just because he may not fully have understood. Can you please cut out the "shutup newbie and get off your ass and use Windoze" bit as its not helping. Only thing that helps newebies is patience and the correct information.

Brian, try yast again. Or yast2. It is indeed in there what you seek, try going a little slower, but I believe from the top of my head that it is in one of the development directories.

Matt

-- Remember: Always think positively. You will prevail.

On Tuesday 04 June 2002 13:36, usb wrote: - Think it is a kernel ACPI problem. Bingo. It dates back to at least SuSE 7.3. I have some old e-mails on the issue or you can look in the archives under "Reboot after SuSE Shutdown.". Nils sent the following on the issue: Start up menuconfig or xconfig. In General Setup Power management ACPI Support set Y ACPI Bus management set Y System set Y Processor set Y While it stopped my dual boot box from rebooting, I haven't as of yet been able to get it to shutdown automatically Brian

On Tuesday 04 June 2002 13:37, Max Webb wrote: - Ps if you want to know who brian is or the extent of the thread please the - archives Excuse me? Please the archives, what? Well, for your information Mr. Dyslexia, I posted once to this tread. I don't know why you have an attitude problem and quite frankly, don't care. You aren't contributing anything to this thread and I certainly have no intention of taking over a thread that isn't mine. I was simply commenting on that this problem seems to have been carried over from SuSE 7.3. Brian

Brain maybe you should just use windows then so you will have nothing to wine about or find out what kernel package you have installed and if it is the SMP kernel. As far as the rest of your reply it is irrational and therefore i do not understand it. Both happend to me with SuSE 7.3 and 8.0 but I corrected the problem in both cases it is an apic/apm issue in the case of 7.3 when forced to use install in safe mode APM was disabled in 8 it is a kernel selection problem. The point is if you are not willing to get off your ass and fix it in SuSE 7.3 or 8 then dont whine about it. Just use a newbie OS like Windoze.

On Monday 03 June 2002 10:38 pm, Brian Durant wrote:

...

On Tuesday 04 June 2002 12:07, Max Webb wrote: - 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

In my case, I did post that I am using SuSE 7.3 Pro. I found nothing with k_smp in YAST 2 either. My point wasn't to commandeer the thread, though getting the problem solved would be nice ;-) My point was simply that

It sounds like an acpi issue to me. If you have an acpi system, you need to enable it in the kernel (which it is in SuSE 8 by default) and also have power management enabled. Try adding "enableapic" to the "append" line in /etc/lilo.conf then run/bin/lilo That may help. However, acpi in SuSE's 2.4.18 kernel seems flawed in some way to me: I can't get it to work properly and it won't patch with the usual acpi patches from Sourceforge, so I've now given up and gone back to Debian for my laptop, which is has an acpi bios. David -----Original Message----- From: Thom Nuzum [mailto:nuzum@earthlink.net] Sent: 04 June 2002 12:47 To: hbwebb@citlink.net Cc: durant@cbn.net.id; SuSE Linux-e Subject: Re: [SLE] Can't Powerdown SuSE 8.0? I do have k_deflt installed and also the Nvidia kernal. Everything else is not installed. I thus do not have a kernal issue and am using the same system as Brian (Athlon XP 1800 Soyo mother). Any other ideas? or is there something in apic/apm other than the lilo.conf I am missing? thanks On Tue, 2002-06-04 at 01:48, Max Webb wrote: the

...

problem exists in 7.3 and here we are and 8 does the same thing. Anyone looking for another reason not to upgrade?

Cheers,

Brian

-- Remember: Always think positively. You will prevail.

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com

-----Original Message----- From: Brian Durant [mailto:durant@cbn.net.id] Sent: 05 June 2002 05:14 To: SuSE Linux-e Subject: Re: [SLE] Can't Powerdown SuSE 8.0? On Tuesday 04 June 2002 21:30, David Robertson wrote: - It sounds like an acpi issue to me. If you have an acpi system, you need to - enable it in the kernel (which it is in SuSE 8 by default) and also have - power management enabled. Try adding "enableapic" to the "append" line in - /etc/lilo.conf then run/bin/lilo - - That may help. However, acpi in SuSE's 2.4.18 kernel seems flawed in some - way to me:

I have done that without success. I too believe that there is a kernel issue here. As I stated in an earlier e-mail, this issue goes back to at least SuSE 7.3

Cheers,

Brian

I agree. Sorry - I don't have any more suggestions really. I've always understood that acpi and apm were sort of mutually exclusive - whichever gets loaded first is used. I found, however, that I needed acpi built in to the kernel, as well as apm bios, and then power management, including shutting down was fine. In the append line of lilo.conf, I then just had "enableapic" (not "enableacpi") and no reference to apm. With SuSE 7.3, I was able to patch a vanilla 2.4.18 kernel with the acpi patches from Sourceforge and get the system running perfectly. I haven't been able to do that with 8.0: the default kernel won't accept the patches and I can't get the system to run with a patched vanilla kernel. So, I've gone over to Debian for my "legacy-free, acpi-enabled, Toshiba, Linux-very-unfriendly" laptop, because of its greater flexibility and, yes, ease of running/maintenance. I'm disappointed - I've always liked SuSE and I'm keeping it on my home PC because my 11 year-old daughter really likes it (or likes green geckos, I think!). I find 8.0 to be inflexible, slow and very buggy - definitely my worst experience with SuSE so far. Judging from some of the posts in this list, I'm not alone in that view. And why oh why did they get rid of YaST1? David

Hi there; I haven't reading the nice flame errupting after this message, so I am not sure if I am going to tell you anything new. In your place I would make sure I am using APM, not ACPI and add these startup parameters to my kernel: apm=on apm=power-off BTW, this forces to shutdown even my 8.0 box (MB Abit TH7-II) with the incorrectly installed SMP kernel. Have a nice time, Jakub On 3 Jun 2002, 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.

On Wed, 2002-05-29 at 04:04, Jostein Berntsen wrote:

...

Hi,

You could check if APM is enabled in your kernel:

http://brenner.chemietechnik.uni-dortmund.de/sdb/en/html/apm.html

Regards,

Jostein

...

===== Original Message From Marc Boorshtein ===== I have SuSE 8.0 installed. When I shutdown the system, it won't power down. I looked in lilo.conf and tried setting append="apm=on", but that didn't help it. Any help would be greatly appreciated.

Marc Boorshtein

--=-HJNVbzfgJFlLiIOurwYX Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org

iD8DBQA89FSSlngxtbePWOERApCXAKCiQ/BIqBB973V09kq0e1uoEyfJqwCbBAdD wQ1PWToxpbSx5sC3OLJ1HoU=tnV4 -----END PGP SIGNATURE-----

--=-HJNVbzfgJFlLiIOurwYX--

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com