DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have small computer as home server with debian.
Motherboard Gigabyte Z87N-WIFI
CPU - Intel core i3 4330
And I have some problems with this configuration.
I'm not using videocard, keyboard, mouse, monitor, any, only case with hardware and lan-cable.
Via console i'm working with this 'server' but I can't reboot or shutdown it.
When I try to do this, I have lost connection but hardware stil works.
The same when I try to power off with user interface. I see stopping debian and black screen, but computer stil works. I thought maybe it was hardware probleme, but with windows OS computer work as need.
There is clean install, empty SSD and empty HDD (ext4 both), sdd - /, hdd - home, ssd (efi volume, swap, ext4)
Without any USB or other plugged devices.
Installed from USB holder with dvd emulator.
Distribution: Debian Testing, Stable, Sid and Manjaro, Mageia 3, LMDE
Posts: 2,628
Rep:
I think I would try the command "halt" to shut down.
Would really like to know how you are getting into the server. There could be a problem with your chroot commands that are only allowing you some access and not other access. While I think this may not be real likely it should be elimenated as a cause.
If you are not chrooting I am not sure what the problem is at all.
If you are going over a lan I assume you are using an ssh connection. I have never tried to shut anything down with ssh straight up.
Your bios is going to have to be setup to permit remote startup, I think, at the least. Can't help at all with that as I am too paranoid to enable that.
It is just about impossible to figure out your problem without knowing exactly how you are communicating with the server when you are trying to shut it down.
3 Steps:
1) Via SSH with root account, I've worked with server. After send command to reboot or shutdown I lost connection and can't return access to server, because OS off, hardware still works.
2) With display, keyboard, mouse, with internal video card. Login to account, work, logout. Try to make reboot or shutdown in menu. I see black screen, hardware still works.
3) Install windows 7 to check another OS with the same hardware. Reboot and shutdown works good.
Command 'halt' - works!
But how can I reboot the system?
Last edited by labor; 04-06-2014 at 04:32 AM.
Reason: halt
If your booting from a live CD I ran into the same problem. I open a terminal and did a passwd added a root user and then assumed root then gave the command reboot. Funny thing is when booting the Iso image from Grub2 and not a thumb drive image I did not have a problem very strange. Like I have said before I really wish Debian would polish up that stable "Live" system.
for the OS to actually power off the machine you need to have acpi installed. To see if this is the case for you, please run the following two commands and post the output.
Code:
dpkg -l '*acpi*'
grep acpi /var/log/dmesg
Depending on your setup, you may need to be root to read /var/log/dmesg
Depending on your setup, you may need to be root to read /var/log/dmesg
Evo2.
FYI, pretty much any modern distribution sets /var/log readable by root only. dmesg can be run by any user.
Quote:
Originally Posted by labor
But how can I reboot the system?
with the command
Code:
$ reboot
run as root.
I had this problem a while back and it was an issue with PolicyKit and gdm3 not playing nice for whatever reason. An update eventually fixed it.
Quote:
Originally Posted by Drakeo
Like I have said before I really wish Debian would polish up that stable "Live" system.
Easier said than done. It's a lot of shell scripts to provide the functionality of a regular system in a small and portable package, it's always going to have it's quirks unfortunately. Although I agree the bootloader should not make a difference.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.