OpenSUSE Install :: Unable To Get The System To Shutdown Or Fully Poweroff Using The Installed OS?
Jan 10, 2011
Built new system and installed openSUSE 11.3 x86_64 with Gnome desktop about 6 weeks ago. Have never been able to get the system to shutdown or fully poweroff using the installed OS. If I use the Knoppix live CD - no problem. System boots up fine and shuts down and powers off correctly. With the installed OS, it originally crashed on shutdown and had to power off using the power button. After trying many things, the OS shuts down, powers off the fans etc, but the keyboard is still lit. I cannot restart the system without turning off power at the power supply. Starting my computer by turning off the power supply switch, waiting
10-12 seconds, turning on the power supply switch and then hitting the power button gets to be very annoying after a few weeks.
Installed KDE and switched to that to see what difference it might make. System does not shutdown, but reboots instead. Switched back to Gnome. Have tried sudo /sbin/shutdown -h now and poweroff. Identical behaviour. System is completely up-to-date. BIOS, kernel, video drivers.
I have a server Hp proliant DL160 G6 with CentOS 5.4 . When I do shutdown -h now it doesn't poweroff.
I try differents options for acpi in menu.lst file. acpi=force, acpi=noacpi,acpi=off,acpi=ht but there's the same problem.
This the stdout when I do shutdown: Halting system... md: stopping all md devices. Completed flushing cache on controller 0 ACPI: PCI interrupt for device 0000:05:00.1 disabled xenbr0: port 2(peth0) entering disabled state ACPI: PCI interrupt for device 0000:05:00.1 disabled Power down. acpi_power_off called
I show you any specific information about my server:
I just did a clean reinstall of Ubuntu (10.04 --> 10.10). After the install, any time I do CPU intensive work, my PC is suddenly shutting down like it's overheating.Everything was working fine for months, and started having problems immediately after the reinstall. so this is not a problem with my hardware, and it's not a problem with my fans needing cleaning -- it's a problem with software. So please don't tell me "that sounds like overheating, clean your fans". Something is different in software-land between 10.04 and 10.10 that is causing this to happen -- I assure you that the upgrade did not magically fill my fans with cat hair.
I have checked my log files, and can't find anything related to overheating -- searches for things related to lm_sensors, "temp", and "thermal" are not turning up anything in the system logs (syslog, kern.log, or messages). I also looked at the logs around the times of the sudden shutdown, and couldn't find anything unusual.How can I diagnose this? I'd like to file a bug report, but since I can't find anything in the logs, I honestly have no idea how to go about providing useful information.Is there anything besides overheating that might be causing my laptop to suddenly shut off?
I am new to opensuse, coming over from debian based systems. However I am having an issue in which my system will not power off on shutdown. Restarts just fine. i get a missing error during shutdown, but there is nothing to relate the error to on that line. Then the shutdown procedes to The System will be halted immediately then hangs. The keyboard powers off and then thats it. All fans are still running. I have searched extensively on this forum and google.
When i shutdown my SuSE 11.2 box with all current updates i have started to notice an error message.Something about failed to unmount, trying remount as read only or something like that.The trouble is its almost the very last message that appears and its not on the screen long enough to read properly.Somewhere is there a logfile that i can recover this error message from so that i can make some sort of an attempt to resolve the issue, post the whole message here in more detail?
I have opensuse 11.4 (Gnome + KDE) installed. The problem is with Gnome. When in KDE, everything works fine. But in gnome, when I shutdown/restart, it merely logs off the session. Then I have to shutdown it from the menu in the login screen.
Does anyone know where there might be a log of the shutdown errors I see flash on the screen when I shutdown the system? I thought they'd be in the warning log. Or is there a way to freeze that screen so I can actually read what is happening?
we have a server running with Suse linux many years. Meanwhile we changed server hardware about 4 times, mostly also updating to newest Suse version. We used to copy group, passwd and shadow to a backup medium, installed the new system and restored those files onto the new system and all was running fine. Now, some weeks ago we installed 11. on new hardware and after restoring those 3 files after rebooting the system hangs when starting GUI. I can boot into runlevel 3 and login with no problem, but when I boot into runlevel 5 mouse and keyboard are frozen. Also when starting GUI from runlevel 3 with startx mouse and keyboard immediately freeze. If I restore the files group, passwd and shadow as they came from fresh new installation I can reboot and login in runlevel 5 without problems.
OK, if I compare the userlist, as it is generated bei installation,there are some usernames I formerly not had in older Suse versions. I don�t know if this can make problems? I tried to edit the files, to combine the system users from 11.2 with the list of local user names from the old system but without success, again the mouse and keyboard freeze.So some questions arise:1) Why now mouse and keyboard freeze in xsystem, when there are changes in the user list (but only in runlevel 5)2) What is the correct way to save and restore users and groups from old to new system. I googled several hours but did not find a smart way. Maybee someon can point me to a link or a howto where I find the solution
just ran the obligatory kernel update for Karmic 9.10 and now my computer doesn't shut down when prompted to do so. It tries...goes through the logoff, makes all the motions and then hangs at the very end.
Reinstalled Ubuntu...same thing after kernel update.
I finally got Ubuntu to run on my laptop. However, I can only get it to run in safe mode. When I turn it on, it goes to the login screen. I select my username, type in my password and press login. Then it either goes back to the login screen after thinking for a while or just gives me the background image. If I select to login in safe mode, I can get to the desktop and everything works fine from there, although in safe mode.Then, when I try to shutdown, it closes everything up and goes black, but doesnt actually turn off. The Caps Lock light blinks.
I did a live upgrade from 11.3 KDE and observe a following issue.When I press the shutdown button on the laptop it initiates the shutdown and shuts down fine but after a significant delay of time (something like 30 seconds). When I click the shutdown button in KDE it initiates the shutdown instantly. This was not the case in 11.3 where the shutdown worked the same regardless of the method that triggered it
I am using Ubuntu 10.04. From last 3-4 days, after updating, I am not able to shutdown the system. I try to use command, but behavior is same Whenever I try to shutdown the system, it exits from desktop environment and a white screen displays on screen. And nothing happened. One time I did wait for 1/2 hr, but system dont seems to power down.
I'm trying to install opensuse 11.4 but I got this error:
"The bootloader is installed on a partition that does not lie entierly below 128 gb. The system might not boot if BIOS support only lba24(result is error 18 during install grub MBR)"
What should I do before click next step to install? I installed opensuse with this error and some times opensuse can boot and some not. At least I was able to boot safemode.
I suspect this is a 'new Grub' problem. I installed OpenSuse 11.2 from DVD into one (sda10) of several partitions (the others containing other operating systems):-
/dev/sda1 * 1 63 506016 6 FAT16 /dev/sda2 64 4865 38572065 5 Extended /dev/sda5 64 960 7205121 7 HPFS/NTFS /dev/sda6 961 1859 7221186 83 Linux /dev/sda7 1860 2759 7229218+ 83 Linux /dev/sda8 2760 3026 2144646 82 Linux swap / Solaris /dev/sda9 3027 3924 7213153+ 83 Linux /dev/sda10 3925 4865 7558551 83 Linux
I use NT Boot Loader for the multi-booting on the basis of chain-loading the boot sector of Linux partitions. (It is not destroyed by MS re-installations; and is actually very easy to use). I also have an older Grub shell boot floppy which can do likewise:- root (hd0,x)chainloader +1 boot FWIW I found the disc partition & boot loader parts of the installation a nightmare. Difficult to know what it is going to do; and I am sure it *did* fiddle with parts I asked it to avoid. Horribly, it did *not* make me a dedicated Suse boot floppy like I checked. (This is always the safest boot option for a new install: it leaves the present boot system intact, and provides an independant way of loading your latest. You can refine things later). I had also checked to have the boot sector on the *root partition*.
I have never been able to get into the Suse. NT Loader does not like the partition boot sector. Nor does (an older) Grub from its boot floppy. I have tried the DVD in 'system repair' mode, when it finds things wrong and corrects them, same next time... It offers a way of directly booting a selected system; that did not work.
Any suggestions? I can provide more precise error msgs, but it is tedious; and system repair from DVD dicey. I feel that *the partition boot sector is not being properly set up*.And I want to be able to make a dedicated boot floppy; how? I have an identical problem with Ubuntu, which makes me think it is related to the 'new' Grub.
When I try to shutdown or reboot from the system menu in Fedora 12, I am returned to the logon prompt. I am able to shutdown and reboot from a terminal window by issuing the shutdown command as the root user.
So I have tried to install from LiveCD and from a LiveUSB stick. Installation goes fine till I get to CUPS daemon. Then I get the wait 30 seconds for CUPS to activate, that never works. Then it pops up with a wait one minute for CUPS to become available. Then it finishes the installation and restarts the system and I get previous installation has failed would you like to retry? It does this over and over again till I get an error with my user name and the mouse and keyboard quit working. I have tried in Failsafe mode, No ACPI, etc. and nothing seems to work. I don't know if it matters but I have an Asus mobo M4A785-M and an AMD Athlon II x3 440 chip. I am just ready to switch to Ubuntu
Has anyone successfully installed openSUSE 11.2 on a Dell PowerEdge 1850 system?Undoubtedly, it wasn't wise to attempt to upgrade from 10.2 to 11.2 but I was forced into it by a security audit of DMZ systems.It didn't go as smoothly as the jump from 9.3 to 10.2.I've spent the better part of a week getting an openSUSE 11.2 system installed.I went back to reiserfs and managed to get through and apply all the updates to openSUSE 11.2 today.When I got to the final reboot, it failed when I attempted to log into the system.Basically, the keyboard and mouse became inoperable.The only way out of this situation is to mash the reset button.
Rebooting into safe-mode and adding level 3 to the safe mode boot options, I get to the point of starting sshd when the lock-up occurs.It looks like X11 is the culprit.Booting a forensics DVD, I find that there is an xorg.conf.installation but no xorg.conf file.The ATI Radeon VE chip set is used on the PowerEdge.From another openSUSE system that I haven't upgraded, I see that X11 was configured for VESA mode. This is, probably, the mode that is needed as console access is, normally, through a KVM.Can anyone provide a way to get past this problem with a workable keyboard and mouse?
It used to be that the dvd menu offered an option to "repair the installed system". THis was really very convenient. The openSUSE 11.3 dvd for x86 now only gives a "system rescue" option which leads to command line directl. Where have been "the repair the installed system" tools? How can we access them now? What is a reasonable set of tips that's supposed to be used after logging into "system rescue"?
LIVECD of 11.3 Gnome works fine in my old PC. I installed several times and each time system freezes/crashes during boot. I am linux newbie, so, I am trying to figure out my problems. In Livecd I noticed Hardware info list's my SATA disk as IDE. Driver Modules: "ata_piix"Attached to: #24 (IDE interface). Is it right? I have posted Hardware information output in 01: None 00.0: 10105 BIOS [Created at bios.186] - Suse 11.3 install problem My machine specs are: Intel DG31PR motherboard, Intel core2duo, 3 GB DDR2 Ram, 250 GB SATA harddisk
but something wrong happened during the installation. and now i don't know hot to install it or remove the broken package cause I get this nvidia-current is broken or not fully installed
how to install the latest version of nvidia drivers ?
ibrahim@ibrahim-laptop:~$ sudo apt-get install --reinstall nvidia-current && sudo dpkg-reconfigure nvidia-curren Reading package lists... Done Building dependency tree Reading state information... Done
I ran a normal "apt-get upgrade" on my 11.04 mythbuntu system yesterday and nvidia-current didn't install properly.Now I can only log into my box using ssh. When I try and run an upgrade I always get the error below:
Code: Reading package lists... Done Building dependency tree
I unable to connect to samba but after change the register (Windows7 - SambaWiki),I could login and map/access the share drive.but when I try to shudown/restart/logoff win7 , the screen just stop with windows logo without the shutdown/restart words coming out.
I'm trying to install a Linksys WUSB600n dual-band USB wireless-N adapter onto a desktop system with opensuse 11.1 installed; this system will be migrating to a back porch with no cabling access, hence the wireless solution. Everything works fine under Windows XP, but on Linux, not so much. Hardware info is as follows; there is no "Wireless LAN" entry, but there is a USB entry:
I'm running a Dell D630 laptop that uses the onboard intel i915 chipset for both audio and video. This is in a docking station that's connected up to a larger monitor. The laptop boots just fine as it has been for quite a while now. I get to the login prompt, enter my credentials and then after pressing enter and it looks like it's going to load my profile, the wallpaper updates but then the screen goes black for a moment and I'm then brought back to the login prompt again. The system is up on the network so I was able to ssh into it and capture the following from the logs during a login attempt.
I just upgraded to jessie (kde) and am not able to fully configure my sound. It was working on wheezy. I have tried alsamixer and managed to get sound (playback & record) through my front case connectors. Can't get anything out of my rear motherboard connectors.I also have a bluetooth headset which I have successfully paired but which doesn't show up as a sound device in pavucontrol.
lspci | grep udio 00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06) 00:1b.0 Audio device: Intel Corporation 9 Series Chipset Family HD Audio Controller
Out of curiosity, can you chainload a Linux system via a Windows executable within Windows at the ordinary desktop?Knowing windows there would be enough holes to write at any memory address without "permission", but can it be done with a humble executable? Or is Windows just too active, without the chance of nothing happening at any one pointo that everything can be exited cleanly non-existent?I'm not asking for a program or guide to do this and neither do I aim to do it. As I've stated it is all out of curiosity on whether or not some sort of protection is in place to stop this kind of thing
i want to install opensuse on my new lap top i partition my hard (600gb) with 5 parts:
c: 97 gb d: 150 gb e: 150 gb f: 100 gb g: 50 gb and 38 gb unlocated part
in opensuse instalation , the yast makes a 2gb for swap 14gb = root , 21 gb = home, but in Instalation Overview under Booting has a red error: the Boot loader Installed On a Partition that does not Lie Entirely Blew 128 GB .The system maight Not Boot;
