Fedora :: F15 - Get The Box To Not Restart After Powering Down?
Jul 20, 2011
I've just installed F15 graphical desktop on a brand new 64-bit box. When I use the Alt key in the User menu to display the shutdown options and click the "Power Off" option, the box shuts down, but then immediately restarts. Is that supposed to happen? How do I get the box to not restart after powering down? Kernel is 2.6.38.6-26.rc1.fc15.x86_64. The box also auto-restarts after root command shutdown -h now
i have installed fedora 12(from dvd) on my laptop having window 7 OS as deafult(intel processor i330)I wanted dual boot up, so I shrink the existing C partition using window using Disk Management. And then delete the newly created volume.And install feora 12(64 bit) with option "using free space".Clean installation of fedora.But when I tried to boot window as it was not able find any window OS.Although from linux all hardrive is coming as one file system and all data on Drive are intact i.e not data is lost
Ubuntu randomly switches off. I eventually found out that it happens when my system is over loading. If my memory goes up to 100% use or CPU, Ubuntu powers off. If there some software that I can download to prevent my system from using 100% of its power, so it doesn't power off?
I'm building up an old PC for a friend. The PCs hardware is quite old. I decided Xubuntu would be appropriate - works well! Currently the only issue I'm having with it is that it does not shut down correctly. The last message I receive is "System Halted!" which stays on screen while the rest of the system is unresponsive. Initially I thought this was an ACPI issue, I was told to add acpi=force and lapic to the boot options but unfortunately this has not fixed the error.I'm really stumped with this issue. By coincidence I have a similar motherboard (May even be the same mobo) in a different PC which had the same issue but insisted that ACPI needed to be forced because the BIOS was older than 2000 (1997).
Because I'm stumped, have some output from various commands I've ran. Code: ~$ lspci 00:00.0 Host bridge: Silicon Integrated Systems [SiS] 730 Host (rev 02)
I'm running CentOS 5.5 x64 and have just installed VMWare Server 1. I am able to create a new Virtual Machine, but when I go to power on the VM in order to install the OS (windows server 2003), either the host crashes/reboots (with "Run in Debugging Mode" turned on) or the VM simply does not start (with that Debugging box unchecked) and in the log there is an error along the lines of VMware Server unrecoverable error (vmx)
I have a server that only runs durring the hours the house is asleep, to avoid bandwidth hogging. I know there are ways to prevent bandwidth hogging, but I figured I'd kill two birds with one stone. My other goal is also to reduce power and cooling costs. My two computers between them make a very nice space heater in the winter, in summer they make it sweltering in my room.I'm sure it would be trivial to get the sever to power itself off every morning, but is it possible to get it to power itself on at bedtime? If not, I do have Wake on Lan working, is there a windows program that would allow me to send a wake on lan signal every day and then shutdown windows
I have just finished the upgrade of the latest version and I'm at the point of my system restating.
My system automatically tried to restart but on the restart I got the 'terminal' view. It stopped when asking for my username (it never normally asks for this before the grub menu) and then password. I didn't get any further than that.
I now have on my screen (still in the terminal view before the grub menu)
"name@name-desktop:...$ "
I'm on my phone now so I don't actually have the symbol for before the dollar sign but your know what it is. The raised S on a 90 degree angle.
I have a suspend problem in my laptop. Sometimes, when resuming from suspend, the network adapter is down (that is, the network does not work and the light of the network adapter is off). Restarting the network service doesn't work, because I think that the system forgot about the hardware, and probably the driver should be reloaded.Does anyone knows how to do that?(ps. /etc/init.d/networking restart does not work, because the hardware driver is not being recognized anymore).
i have installed dhcp,there i declared the subnet and network,i used command include "/etc/dhcpd.conf.jutu1"; to start and other files, but it show me this error when i want to restart the DHCP, if you need more information contact me, i have configured this file too jutu1, but it don't let me to restart dhcp from /etc/init.d/dhcpd restart, this show me this message
Whenever I choose "Restart" from the GDM screen, GDM appears to shutdown, and the first TTY is displayed with a login prompt at the bottom (assuming I haven't used that TTY). I am by no estimation a patient individual, but I waited a solid minute or two for something to happen, but nothing ever did. I end up logging in as root on that TTY and running "shutdown -r now" to get the job done. This is a shared computer, and ideally any user should be able to perform shutdown options graphically from GDM.The only mentioned workaround doesn't apply to me as I am using the nvidia driver, not intel.
I installed GNOME shell and now I can't login after restarting the computer. It brings up the login screen and I can enter my password, but it just goes back to the login screen. I would like to stop GDM and run X -config to see if that straightens out the problem
whats the difference between restarting/stopping apache using 'service httpd restart/stop' and apachectl restart/stop. I know that using 'service httpd restart' is actually a script in /etc/init.d/httpd but what about apachectl?
1). Since last few days my firefox does not restart. In order to restart, I have to remove .parentlock even when I closed the firefox properly after my previous run
Firefox restarts happily when it crashes, and after two crashes, it apologizes but crashes the third and fourth time :-)
2). The other problem is that it crashes a lot on applets.. I use my school blackboard which uses applets a lot (for different utilities), and it crashes 1 out of 5 times on running an applet. I think it due to the IcedTea and/or Java (TM) plugin 1.6.0_06-b02. I have both plugins enabled in Firefox plugins list.
I have installed Fedora 12 as a clean installl, everything worked perfect. But lately either after installing an update or making some parameter changes, while restarting my system it just comes up with lots of error messages and crashes. I have to press the switch off button to shutdown. I don't know from where to get that error message to post here
When I close the lid on my Dell Latitude e6510 running Fedora 14/Gnome, the machine seems to suspend correctly. When I reopen the lid or otherwise try to awaken it, I get a text screen showing:
I am running with Linux installed on an external Passport drive, selected via F12 during startup.
A little be confused, as the debian way is not working (like sudo service gdm3 restart) and by the fact that I can not find solution in the internet All I could find is such command like "stop prefdm" which is also not working
When I try to logout, it tells that you "will be automaticallyed out after 60 seconds"..and there are two buttons there. one is to "cancel", one is to "logout". Even if I press the logout button, it will logout after only a minute. My question is that how to logout instantaneously (without waiting for 60 seconds).The same problem happens when i try to poweroff or restart the computer. It will do it only after 60 seconds. Who in the world would like a machine which does things according to its wish, rather than execute your command?
i'm new on board and new for linux.i installed fc 9, and it's look ok. i want to use stutic ip,so i did what i find here:uote:First, NetworkManager and static ip addresses do not get along. If you want to use static ip addresses, turn off the NM services by going to "system->administration->services" and disable the NM services and reboot.Next, goto "system->admin->network", highlight your device and click the "edit" tab and configure the device. Uncheck the "controlled by NM option" and "automatically obtain ip address" BUT then place a check in the "allow users to control" and "activate on boot"Then click the "dns" tab and fill in your dns servers ip addresses.the problem is that is no internet connection after reboot. than i go to system->admin->network,and activate the device and all ok.
Does anyone know how to schedule a Fedora box to automaticly shutdown and then resume later at a specific time?Shutting down is easy, but I have found nothing about the restarting part.
When I select restart from the shut down menu sometimes instead of shutting the system down it insteads just ends my session and logs me out (which leads me to believe perhaps my session is crashing when it tries to reboot?
im just stating in fedora..why does i cant restart/start/stop my /etc/rc.d/init.d/smb ? actually i notice that there are no "smb" or "samba" file exist in my /etc/rc.d/init.d/ or in /etc/init.d/
and there is no smb or samba found in my /sbin/chkconfig but i have my samba installed. Im using fedora 10
I'm having a weird issue, I have Virtualbox 3.1 installed on the Fedora 12 and everytime I restart the "/dev/vboxdrv" gets deleted so every time I need to run "/etc/init.d/vboxdrv setup".
If I want to swap from wired to wireless I have to restart my laptop. If I just flip the wireless switch on at the side it does not seem to recognise that I have wirless capabilities, I have to restart with the switch set to on.
I have a server box running F12. Whenever networking is lost up-stream, obviously, my box loses it and the networking icon gets the "red" cancellation sign over it.Now, when up-stream connectivity returns, Fedora does not auto-connect. Instead I have to manually go to my office (grrrr), and simply click on the networking icon, click on the unselected radio button next to eth0 (its the only network interface), and I'm good again.To save me future weekend trips to the office.... How can I make sure this happens automatically
Done a fresh install of Fedora 13 - it's the only os on the computer. Everything appeared to go well, but I'm unable to restart the computer. It gets to a point where it says restarting and just hangs there. Had a bit of a search through the forums and I see this was a problem for some people with earlier versions but haven't seen much mention past Fedora 10, and there doesn't seem to be a universal fix that's worked for everyone so not sure what I should be doing. There was some mention of the problem being related to nvidia drivers, but my video card is an ATI 4850 so that seems to rule that out as a possible cause. I've had several years using Linux (mostly Ubuntu and openSUSE) but hardly any experience with Fedora.
When I shut down the computer, then turn it back on- everything goes fine- system loads, no errors.BUTWhen I am in a turned on system, and I ask it to restart (reboot), when the machine restarts and the system starts loading- I get a kernel panic. Every single time- but only when I ask the machine to restart. If it helps, the error didn't appear on Fedora 14.
To make it more colorful- the same situation happens with my Ubuntu 11.04 (I have triple boot- Fedora, Windows and Ubuntu- I am learning Fedora to switch from Ubuntu). When I had Ubuntu 10.10- all was ok- when put 11.04- the error is the same- I can't restart my PC properly. The only system that loads as it should every time is Windows 7.Could anyone pls help me? My guess is that it's some kind of kernel change, because the error didn't show up in the previous versions of both systems (Fedora and Ubuntu).Did memtest (after 12 passes there were still no errors), tried acpi options, modeset, nomodeset (using grub2)- all for nothing.
Today I updated my system, I noticed that KDE would be upgraded to 4.3. Upon restart of my computer my wireless didn't work (and still doesn't) and I cannot use the desktop effects anymore (probably the graphics driver). Is there any way I can fix those problems, or downgrade my system so everything just works? I'm using Fedora 11 KDE (64-bits). And I've kept a list of all updates. Ok, I figured that it was a different version of the kernel, the update set the other kernel to default. I'm back to 2.6.29.6-217.2.8.fc11.x86_64 and everything works.
