Siduction Forum
Siduction Forum => Installation - Support => Topic started by: orca on 2013/08/11, 04:44:17
-
Hi there
The subject is self-explanatory I guess: I have recently installed siduction from a spare working live dvd of ridersonthestorm (the one I had of firestarter did not boot...). Right after installation, I tried to issue shutdown -h now, as root, and the desktop did turn off, but almost instantly booted again, like a zombie. No matter what I tried (even the KDE main menu icon for Shutdown), the only way it really works is pressing off the power button. Any tips?
My desktop has an Intel DH87MC motherboard.
Thanks for any help
-
...I tried to issue shutdown -r now, as root, and the desktop did turn off, but almost instantly booted again,...
What else did you expect? "-r" stands for "reboot", but if you wanted to shutdown and hold/stop you have to issue:
shutdown -h now
-
...I tried to issue shutdown -r now, as root, and the desktop did turn off, but almost instantly booted again,...
What else did you expect? "-r" stands for "reboot", but if you wanted to shutdown and hold/stop you have to issue:
shutdown -h now
I think 'sudo halt' will shutdown as well ...
-
Thanks michaa7 and farinet: I had a typo in my post subject. It should really be shutdown -h now (as michaa7 warned). Sorry; I have now edited the subject accordingly.
But the issue persists: either, as root, typing shutdown -h now, or, as normal user, from the KDE main menu, through its Shutdown icon, I am not able to really definitely power off the machine, as it always reboots...
Thanks again
-
Ok, this now makes sense, and yes, you have a problem.
I wonder what you mean by "pressing off the power button". Is this a *clean* shutdown? I doubt it.
To me it seems you have a mobo with a broken BIOS/ACPI . And the problem you mention in this other thread here seems to prove that.
A quick Google search (Intel DH87MC shutdown) indicates my guess is right:
http://forums.opensuse.org/english/get-technical-help-here/install-boot-login/488808-shutdown-troubles.html
Did you install any other OS/linux with a working shutdown?
If I am right you need a BIOS update or you need to complain at the vendor or direcly on INTEL.
-
?
shutdown -P
?
-
Hi michaa7
"Pressing off the power button" means what you guessed: physical pulling down the power button for some seconds; it is the only way I can manage to really turn off completely and definitely the machine...
I have no other operating system installed, only siduction ridersonthestorm, which, in fact, I just dist-upgraded right now (apparently with no issues, but this shutdown bug persisting).
So it seems I should give the BIOS update a try. Does this usually go without any issues or should I be prepared to have some surprises, the worst being unbootability???
Thnaks again!
-
...Does this usually go without any issues or should I be prepared to have some surprises, the worst being unbootability???
...
It "usually" should work, but not even the manufacturer will give you a guarantee. Maybe it's worth to first ask the manufacturer if this bug is known AND fixed?
Good luck ;-)
-
I think 'sudo halt' will shutdown as well ...
Actually, that won't work
siduction is not ubuntu ... therefore sudo is useless, unless you manually configure it ... ouch :)
-
How about the simple "init 0" as root?
Tim
-
I think 'sudo halt' will shutdown as well ...
Actually, that won't work
siduction is not ubuntu ... therefore sudo is useless, unless you manually configure it ... ouch :)
I do not remember i ever did a visudo on this siductionbox but sudo works :shock: :shock: :?: :?:
-
I think 'sudo halt' will shutdown as well ...
Actually, that won't work
siduction is not ubuntu ... therefore sudo is useless, unless you manually configure it ... ouch :)
I do not remember i ever did a visudo on this siductionbox but sudo works :shock: :shock: :?: :?:
Well, you did something, my latest build is
Desktop: KDE 4.10.5 Distro: siduction 13.0.5 PaintItBlack - kde - (201308031300)
and every build before that
piper@x1:~$ sudo apt-get install freedink
We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
[sudo] password for piper:
Sorry, user piper is not allowed to execute '/usr/bin/apt-get install' as root on x1.
piper@x1:~$
piper@x1:~$ sudo apt-get update
[sudo] password for piper:
Sorry, user piper is not allowed to execute '/usr/bin/apt-get update' as root on x1.
piper@x1:~$ sudo apt-get dist-upgrade
[sudo] password for piper:
Sorry, user piper is not allowed to execute '/usr/bin/apt-get dist-upgrade' as root on x1.
piper@x1:~$
Unless someone can prove me wrong, sudo does not work out of the box in siduction (this goes back to kanotix, sidux, and aptosid)
I have been building for a long time now and have yet to see sudo work out of the box on a clean install (live cd does not count)
-
Yep, i think so, obviously. For sure you're way way more knowledged than me. I just checked sudo visudo and i saw that me, as a user, is in there with root access rights.
Just a question, how is (or has been) the default root access in siduction? Su + pswd in a terminal ? For what i can think, is it possible it came with some dist-upgrade done via smxi? (Btw, as far as i remember, sudo is there also in crunchbang, which is wheezy based, mine then, is pointing to sid . . .)
-
Sudo is not configured with siduction (=here on my computer).
So the only thing you can assume about your systerm is: It's borked. Because if it wasn't you but smxi or some crunchbang-wheezy-thingy to configure it who now knows what's going on on your system?
-
su is the default in siduction, since you use smxi, I stop support right here, maybe someone else can help
-
Sudo is not configured with siduction (=here on my computer).
So the only thing you can assume about your systerm is: It's borked. Because if it wasn't you but smxi or some crunchbang-wheezy-thingy to configure it who now knows what's going on on your system?
You're right. Obviously, i changed that on my own; looked on the date, when the sudoers file was changed or created (i think since i was used to by crunchbang). Sorry for the confusion.
But, just a practical question. How would you in a default siduction setup execute commands like 'sudo service tor restart' or thatlike?
PS. I do not remember anymore, but during the installation of razorqt-firestarter from the live-dvd are you asked for a separate root password?
-
su is the default in siduction, since you use smxi, I stop support right here, maybe someone else can help
I used smxi to have an install of fglrx on an old HP-Pavilion which didn't pass thru well with the legacy driver from the debian repositories (but that did not work; smxi told me, that the graphic card is too old :-( )
-
if you don't use sudo, just become root with su and than execute the command without sudo in front of it.
-
...i changed that on my own; looked on the date, when the sudoers file was changed or created (i think since i was used to by crunchbang). Sorry for the confusion.
...
PS. I do not remember anymore, but during the installation of razorqt-firestarter from the live-dvd are you asked for a separate root password?
Sure you were asked for a root password at installation time. How else did you configure sudo *without* a root password? How can this be possible? If you discovered a way to do so we all can throw away our installations seen from a security perspective.
But, just a practical question. How would you in a default siduction setup execute commands like 'sudo service tor restart' or thatlike?
dieres did answer that. You become root.
But really, didn't you know how to become root? Given your other threads which give the impression of an somewhat skilled user I can't believe what you write here.
But at least this lesson should be clear now: Your system is unsupportable.
You should delete your system and reinstall by following the given instructions. Beforehand buy a stone in which you carve: "I never configure sudo again".
-
Oh no . . . :(
If, i think, i hope, there should be a way to reset the system back to siuction like without deleting it, isn't it? But for sure, coming from years with (l)ubuntu sudo is somewhat subcutaneous. ;)
PS. The reasons given here (https://wiki.debian.org/sudo) are not valid?
-
If, i think, i hope, there should be a way to reset the system back to siduction like without deleting it, isn't it?
Sure -- the only thing that is needed is the list of every change made to the default configuration of your system. :roll:
You can lose a lot of time chasing mysteries on a system of unknown configuration -- it's your computer, maybe you can back out enough, and replace enough, to get it working normally. The problem is, you can never really be certain. Then the next time something unexpected happens, you are doomed to wonder about the non-standard bits that you thought you fixed.
A reinstallation of the OS, on a machine with a separate partition for /home, takes only a few minutes, plus some updating and configuration time. For sure you can have everything that you have now in a couple of hours, and no future questions about mystery breakages.
-
...
PS. The reasons given here (https://wiki.debian.org/sudo) are not valid?
In theory yes, in practice NO.
Can't you still *see* what amount off effort it took for *you* to recall the history of your configuration (not to mention the confusion for the reader)? This is just an example how sudo obfuscates things where a bright (over-) view is required.
-
May i reply in the same way? In theory yes, in practice no ... If i'd be systematical probably i'd keep track of all what i do but . . . ;) Frankly, do you? E.g., generally, i've an idea what i did tweaking the powermanagement settings, but step by step i would be unable to track all (and that does not regard absolutely the general problem sudo/no sudo).
A practical question in my fluxbox menu i defined some shortcuts like:
Shutdown: qterminal --execute "sudo halt"
Which aks me the pswd and then shuts down the system.
What would be the equivalent without sudo? Is there a way to concatenate the root call with the execution of halt in *ONE* line so that fluxbox would understand it?
-
en:
There is no way to shutdown without sudo, but you may shutdown using the powerbutton instead. To be able to do so you first need to install acpid. You can configure the power botton for different events (like shutdown, reboot ...). I did it with the help of the user of an other (german) forum (link down here in the german part). If someone needs it translated please ask.
de:
Ich wollte in der sudo diskussion schon darauf zu sprechen kommen, weil shutdown unter fluxbox als user (ohne sudo) ja nicht geht sondern man nur über den umweg des jeweiligen loginmanagers herunterfahren kann. Ich war damals versucht mich doch mit sudo zu befassen, fand aber gott sei dank eine andere lösung (die dir möglichweise nicht behagt). Dennoch fahre ich seit dem den rechner mit dem power knopf herunter. Dazu muß du acpid installieren und konfigurieren (der knopf ist so sogar für unterschiedliche ereignisse konfigurierbar).
Wie das geht kannst du hier nachlesen, das gibt dir auch gleich einen eindruck der mir nachgesagten fähigkeiten ;-):
http://debianforum.de/forum/viewtopic.php?t=120542&p=768041
definitiv hilfreich sind die antworten von rendegast
-
If i'd be systematical probably i'd keep track of all what i do but . . . ;) Frankly, do you?
No, of course not.
So, to avoid destruction, I do not enable any third party repositories, except the debian mmo repo occasionally, and I never install downloaded tarball stuff (except vmware which I really need).
With smxi installed, and we don't know what else, your system configuration is "contaminated" -- it has changes made that no one can be certain about, and therefore no one can offer to support or fix it.
-
I did not install the liquorix repositories, only the script, mainly to install - without success finally - the catalyst driver ...
-
en:
There is no way to shutdown without sudo [. . .]
Not even as root?
Wie das geht kannst du hier nachlesen, das gibt dir auch gleich einen eindruck der mir nachgesagten fähigkeiten ;-): http://debianforum.de/forum/viewtopic.php?t=120542&p=768041
definitiv hilfreich sind die antworten von rendegast
Thanks for the link. I should look closer to the acpi scripts anyway, may be i'll find something there to solve the powermanagement problems i've (not anymore on the HP running razorqt but on a samsung running crunchbang pointing to sid). But: What the hell is the mc method? ;)
Cheers.
-
en:
There is no way to shutdown without sudo [. . .]
Not even as root?
As root you can, sure.
...What the hell is the mc method? ;)
type "mc" in your terminal and see ;-)
In this context it refers to proposed possibilities on how to unpack some packages. On commandline it is comfy to use mc as it allows for browsing the content of *.deb archives and extracting single files, IIRC.
-
Then, i presume, the above quoted fluxbox shortcut to shut down from within the flubox environment should be:
gksu "qterminal -e halt"
(Or is 'halt' siduction coherencewise not acceptable too by some reason?)
And oh, i see, mc, that's the linux version of Norton Commander ... :D
-
I absolutely have not the slightes clue whether or not this fluxbox shortcut is working. But if so, let us know.
BTW, I don't know "qterminal", do you know "konsole"?
And yes, mc is a must have ;-) .
-
In the fluxbox menu i've now 3 shortcuts using gksu and all work!
SUSPEND:
gksu "qterminal -e pm-suspend"&exit
REBOOT:
gksu "qterminal --execute reboot"
SHUTDOWN:
gksu "qterminal --execute halt"
PS. May be it's an overkill to ask for pswd to go to suspend; but practically it can be done too or by closing the lid or by (default for the HP Pavilion) keyboard shortcut (FN+F5).
-
Thanks for sharing this with us.
But for all those shortcuts to work you need to issue the *root* password. Shutdown/reboot with acpid does not require a p/w.
-
True, and i'll look closer to the acpid scripts in the near future. Generally, i don't mind to have to put in pswd for shutdown or reboot in a prospective of security
-
Oh, since i'd problems with an installation the firestarter nox (graphics completely distorted) i studied a bit the manual. And what did i find? :shock:
Under the title: siduction-*.iso - Live Mode root password there is written:
To set a (temporary) root-password
Open a console/ shell:
siduction@0[siduction]$ sudo passwd
Enter new UNIX password:
Retype new UNIX password:
passwd: password updated successfully
siduction@0[siduction]$
;) ;)
-
Oh, since i'd problems with an installation the firestarter nox (graphics completely distorted) i studied a bit the manual. And what did i find? :shock:
Under the title: siduction-*.iso - Live Mode root password there is written:
To set a (temporary) root-password
Open a console/ shell:
siduction@0[siduction]$ sudo passwd
Enter new UNIX password:
Retype new UNIX password:
passwd: password updated successfully
siduction@0[siduction]$
;) ;)
Which was already mentioned in this thread on page 1
I have been building for a long time now and have yet to see sudo work out of the box on a clean install (live cd does not count)
Even in live mode, I still don't/won't use sudo