Hi i have installed suse 10.2 and when i try to shutdown or reboot the machine with anyway(i mean within x mode or directly shutdown -h now or init 6 commands) it doesnt work it freeze i searched a solution in every page of google but i couldnt find anything but strange thing is lots of people have this problem but none of them has solutoion
and i have very limited time because this is a server machine and it has to be up within 2 days
So if anyone helps me i would be very appreciated
Thanks

Here is my system
Suse 10.2 64 bit edition
Intel Pentium D 820(dual core)
ASUS p5ld2-vm board
1024 mb ram
160 gb sata2 hdd

If you are running at run level 5, graphical login, then the delay may be caused by the fact that the X server takes a long long time to shut down on SuSE. I have run SuSE at run level 3, text console login, so when I log in I just have a text console. Then I start X manually. This is how I have found that the X server takes a long time to shut down. When I log off of the machine I first have to stop the X server and then I log out from the text console.

I would say that the X server takes 30 seconds or longer to shut down.

If you change your default run level to 3 you will be able to see if this is your problem.

no i dont think thats the problem i have waited more than 15 minutes but it still just black screen

Given your limited time frame to solve this, and I mean this with all respect and honesty, I would recommend that you use a different distribution. If you had successfully been using some Linux distribution then revert back to that. If you are trying Linux for the first time on this machine then you might want to try Slackware or Debian.

Good luck. I know that working under a deadline can be a problem in the best of circunstances. Trying to solve this could turn into a hobby. If this work is being done for someone else then turning it into a hobby isn't an option.

thanks but actually i dont have that kind of time either
i guess this problem happens because of acpi or local apic support do you know what those actualy work for and how can i get over it

The acpi is the module that actually turns the power off when you shut down the machine.

You can try to boot with the command line parameter noacpi to see if that will help. You can put it into your /boot/grub/menu.lst file. Just add it along with the other parameters on the line used to boot the kernel in the entry that you normally use to boot the system. Then reboot. Try using the reboot command from a terminal instead of using the shutdown command from a GUI.

Here is a list of Linux boot parameters.

http://www.tldp.org/HOWTO/BootPrompt-HOWTO.html

As far as "...not having that kind of time..." when looking for the fastest solution, well, this is going to take as long as it takes whether it fits your schedule or not. I was just trying to help speed up the process.

I hope that the noacpi boot parameter works, but that is entirely dependent on your suspicion that the acpi is the problem. This is how things can become long term projects. You may think that you have the quick answer but if it is wrong then you are tempted to try the next real fix thing and then the next real fix. It doesn't take much to have this sort of thing turn into dozens of attempts trying different things over many days to "fix the real problem". At that point you feel like you definitely don't have the time to try the quick answer, changing distros, so you continue trying to find what specifically is wrong with SuSE when changing to Debian or Slackware would ultimately fix the problem faster.

I'm not trying to be a jerk. I don't want to appear to be rude to you. I'm just talking from 22 years of experience running numerous platforms from CP/M and MS-DOS to VMS to Solaris to Linux, and others. This kind of troubleshooting and fixing the real problem is a common trap for all computer platforms. Of course it is only a problem when you have a short time to fix the problem. If you had six months then the first thing that you tried would definitely fix the problem, guaranteed.

Thanks i really appreciate your help but beside time issue i have several hundred reasons to stick in suse both hardware and software reasons
I tried to close acpi within menu.lst file but nothing changed it still doesnt shutdown or restart then i tried to close acpi support from bios but this time suse didnt open and i hade to take everyting back
I'm still looking for a solution

Have you looked in your /var/log/messages file? There may be some helpful information in there about the shutdown process on your machine.

If there is nothing helpful in /var/log/messages then you could try booting a live CD. That will at least provide you the opportunity to see if the live CD SuSE system works on your hardware, and you can quickly try different Linux distros via live CD to see if they have problems with your hardware.