Why, when I shell out with Ctrl-Alt-F2, does my GUI login not work?
What's the trick __{{emoticon}}__
topic title: Login on shell-out won't function
-
Posts: 54
- Joined: 30 May 2010
-
anticapitalista
Posts: 5,955
- Site Admin
- Joined: 11 Sep 2007
#2
Shell out with Ctrl-Alt-F1
-
Posts: 54
- Joined: 30 May 2010
#3
Did so -- I still get"Login incorrect"anticapitalista wrote:Shell out with Ctrl-Alt-F1
-
Posts: 516
- Site Admin
- Joined: 01 Oct 2007
#4
Don't know if this helps, but depends on what you do while you shell out, if I ctrl-alt-f1, do some maintaince and then want to get back to the desktop, just ctrl-alt-f7 gets back, if I login as root after ctrl-alt-f1, I usually kill slim by:
/etc/init.d/slim stop
after running a du or others, when done I will then
/etc/init.d/slim start
which will then get me back to my slim login.
clear as mud?
cheers,
oldhoghead
/etc/init.d/slim stop
after running a du or others, when done I will then
/etc/init.d/slim start
which will then get me back to my slim login.
clear as mud?
cheers,
oldhoghead
-
Posts: 54
- Joined: 30 May 2010
#5
As soon as I shell out on F1 to F6, the prompt asking for my login appears.
I cannot do anything since I cannot log in!
Is this normal?
(I appreciate your suggestion, however, oldhoghead!)
I cannot do anything since I cannot log in!
Is this normal?
(I appreciate your suggestion, however, oldhoghead!)
-
Posts: 1,228
- Joined: 15 Jun 2008
#6
This isn't normal.
Sorry for the stupid question but isn't it a case of CapsLock being activated/deactivated?
Sorry for the stupid question but isn't it a case of CapsLock being activated/deactivated?
-
Posts: 54
- Joined: 30 May 2010
#7
CapsLock is off
I keep NumLock on for login purposes, though
I keep NumLock on for login purposes, though
-
Posts: 516
- Site Admin
- Joined: 01 Oct 2007
#8
SaminBare,
I agree with secipolla, this is not normal, what ever username and password you use for a regular gui login should work when in shell (Ctrl-Alt-F1), the root password should work when you login in shell (Ctrl-Alt-F1) as root, if these are not working, then there are some probable causes, so to eliminate some obvious culprits,
1) did you verify the md5sum on the iso and the burned cd?
2) don't burn a cdrw, as they sometimes cause failures (learned this the hard way)
If 1,2 are not the issue then maybe reset the password and see if that works.
open terminal
sux
(root password)
then type:
passwd username (use your username)
you'll get a prompt to change password and a second one to verify.
If you want to change the root password, then substitute root for username
sux
(root password)
then type:
passwd root
you'll get a prompt to change password and a second one to verify
cheers,
oldhoghead
I agree with secipolla, this is not normal, what ever username and password you use for a regular gui login should work when in shell (Ctrl-Alt-F1), the root password should work when you login in shell (Ctrl-Alt-F1) as root, if these are not working, then there are some probable causes, so to eliminate some obvious culprits,
1) did you verify the md5sum on the iso and the burned cd?
2) don't burn a cdrw, as they sometimes cause failures (learned this the hard way)
If 1,2 are not the issue then maybe reset the password and see if that works.
open terminal
sux
(root password)
then type:
passwd username (use your username)
you'll get a prompt to change password and a second one to verify.
If you want to change the root password, then substitute root for username
sux
(root password)
then type:
passwd root
you'll get a prompt to change password and a second one to verify
cheers,
oldhoghead
-
Posts: 54
- Joined: 30 May 2010
#9
"I agree with secipolla, this is not normal, what ever username and password you use for a regular gui login should work when in shell (Ctrl-Alt-F1), the root password should work when you login in shell (Ctrl-Alt-F1) as root . . ." Quoting oldhoghead, above
I attempted to verify MD5 (which I obtained from same source as downloaded ISO) but could not discern how to compare it to the ISO on an external HD ( the same ISO burned to CD and installed) since I do not have k3b to generate the MD5 directly from the image. Is there an alternative I'm ignorant of?
CD the image was burned to is not cd-rw, but -ro .
Just to eliminate them as possibilities, I opened Terminal and changed both Login and root passwords, as you wrote above.
Unfortunately, the issue remains the same --"Cannot Login with username and password . . ." in the shell accessed with Ctrl-Alt-F1(thru F6).
This is so similar to mikeg's post of 19 Apr 10, In the New Users forum that I sent a PM to him asking if he considered the post (last thread on 10 May 10) as dead -- so that I would know which way to proceed, publically or privately. He, mikeg, replied that
"AntiX does not allow a user with the slim desktop to login as root."
I must agree with his statement -- but why is this so? If this behavior/policy"is not normal," why does it persist?
Could it have anything to do with the file system I formatted the partitions with -- ext4?
I attempted to verify MD5 (which I obtained from same source as downloaded ISO) but could not discern how to compare it to the ISO on an external HD ( the same ISO burned to CD and installed) since I do not have k3b to generate the MD5 directly from the image. Is there an alternative I'm ignorant of?
CD the image was burned to is not cd-rw, but -ro .
Just to eliminate them as possibilities, I opened Terminal and changed both Login and root passwords, as you wrote above.
Unfortunately, the issue remains the same --"Cannot Login with username and password . . ." in the shell accessed with Ctrl-Alt-F1(thru F6).
This is so similar to mikeg's post of 19 Apr 10, In the New Users forum that I sent a PM to him asking if he considered the post (last thread on 10 May 10) as dead -- so that I would know which way to proceed, publically or privately. He, mikeg, replied that
"AntiX does not allow a user with the slim desktop to login as root."
I must agree with his statement -- but why is this so? If this behavior/policy"is not normal," why does it persist?
Could it have anything to do with the file system I formatted the partitions with -- ext4?
-
Posts: 1,228
- Joined: 15 Jun 2008
#10
You can't login as root to the desktop. IDK if it's the default in SLiM or if it's an antiX specific setting. But you should be able to login as any user to the console (Ctrl+Alt+F1-F6).
I've did it right now, Ctrl+Alt+F2, logged as root then Ctrl+Alt+F7 to come back here.
I've did it right now, Ctrl+Alt+F2, logged as root then Ctrl+Alt+F7 to come back here.
-
Posts: 54
- Joined: 30 May 2010
#11
I may have confused the issue -- I AM able login as root in Terminal and bash.
However, I am NOT able to login to the console (Ctrl+Alt+F1-F6).
Furthermore,since performing an upgrade I am no longer able to access the console with Ctrl-
Alt-F1 (thru F6). This is a new development I just discovered.
However, I am NOT able to login to the console (Ctrl+Alt+F1-F6).
Furthermore,since performing an upgrade I am no longer able to access the console with Ctrl-
Alt-F1 (thru F6). This is a new development I just discovered.
-
Posts: 516
- Site Admin
- Joined: 01 Oct 2007
#12
SaminBare,
First you must verify that the iso is correct,
see here:
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.mepis.org/docs/en/index.php/Check_the_integrity_of_the_downloaded_file"
linktext was:"http://www.mepis.org/docs/en/index.php/ ... oaded_file"
====================================
after that, then
There are a couple of ways to verify the iso burn on the cd,
take a look here:
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.mepis.org/docs/en/index.php/Checking_the_integrity_of_a_Live_CD"
linktext was:"http://www.mepis.org/docs/en/index.php/ ... _a_Live_CD"
====================================
You will have to identify the correct device for you cd rom, since this is antiX and no k3b, I insert the livecd, using rox filer, (don't mount the cd) I right click on /media/cdrom then under Mount point 'cdrom' and click on properties, and I can see the mount point type is /dev/hdc, In terminal I can then use the command:
bobbylee@antiX1lee:~$ md5sum /dev/hdc
and it returns this:
3e0b44b9830346a42e81f1105925d8a3 /dev/hdc
bobbylee@antiX1lee:~$
however, if I have a bad burn, and even though it will boot and install, when I run an md5sum on it
I may get this,
bobbylee@antiX1lee:~$ md5sum /dev/hdc
md5sum: /dev/hdc: Input/output error
or I could even get a sum that is a mismatch,
The only way to know for sure is to verify the iso and the burned cd.
I would venture to say that you had a bad burn, or an iso because the issue you first posted about is not normal.
cheers,
oldhoghead
First you must verify that the iso is correct,
see here:
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.mepis.org/docs/en/index.php/Check_the_integrity_of_the_downloaded_file"
linktext was:"http://www.mepis.org/docs/en/index.php/ ... oaded_file"
====================================
after that, then
There are a couple of ways to verify the iso burn on the cd,
take a look here:
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.mepis.org/docs/en/index.php/Checking_the_integrity_of_a_Live_CD"
linktext was:"http://www.mepis.org/docs/en/index.php/ ... _a_Live_CD"
====================================
You will have to identify the correct device for you cd rom, since this is antiX and no k3b, I insert the livecd, using rox filer, (don't mount the cd) I right click on /media/cdrom then under Mount point 'cdrom' and click on properties, and I can see the mount point type is /dev/hdc, In terminal I can then use the command:
bobbylee@antiX1lee:~$ md5sum /dev/hdc
and it returns this:
3e0b44b9830346a42e81f1105925d8a3 /dev/hdc
bobbylee@antiX1lee:~$
however, if I have a bad burn, and even though it will boot and install, when I run an md5sum on it
I may get this,
bobbylee@antiX1lee:~$ md5sum /dev/hdc
md5sum: /dev/hdc: Input/output error
or I could even get a sum that is a mismatch,
The only way to know for sure is to verify the iso and the burned cd.
I would venture to say that you had a bad burn, or an iso because the issue you first posted about is not normal.
cheers,
oldhoghead
-
Posts: 1,228
- Joined: 15 Jun 2008
#13
Also this is how I burn isos
If you have more than one drive you can run 'wodim --devices' to see how they are seen, here I use
Code: Select all
wodim -sao speed=4 antiX-M8.5.iso
Code: Select all
wodim dev='/dev/scd0' -sao speed=4 antiX-M8.5.iso
-
Posts: 516
- Site Admin
- Joined: 01 Oct 2007
#14
secipolla,
Nice! __{{emoticon}}__ Learn something valuable everyday, thanks for an eaiser method.
cheers,
oldhoghead
Nice! __{{emoticon}}__ Learn something valuable everyday, thanks for an eaiser method.
cheers,
oldhoghead
-
Posts: 54
- Joined: 30 May 2010
#15
Thank you , oldhoghead and secipolla --
md5sum /dev/sr0 => md5sum: /dev/sr0: Input/ouput error
Indeed, it was a bad burn. So, it is back to ground zero.
I've backed up and will use the cli as sedipolla indicated to burn another iso to cd
i found anticapitalista's reference to it and looked up
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://smxi.org/site/smxi-story.htm"
linktext was:"http://smxi.org/site/smxi-story.htm"
====================================
I will use the script next time for upgrades. Learning is good, even if time-consuming and frustratin'!
Any recommendations on how best to proceed? Just write a new partition table and go from there?
Otra vez -- Gracias amigos! (Oh yeah -- no ASCII characters for Spanish puctuation inherent in linux, are there?)
md5sum /dev/sr0 => md5sum: /dev/sr0: Input/ouput error
Indeed, it was a bad burn. So, it is back to ground zero.
I've backed up and will use the cli as sedipolla indicated to burn another iso to cd
i found anticapitalista's reference to it and looked up
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://smxi.org/site/smxi-story.htm"
linktext was:"http://smxi.org/site/smxi-story.htm"
====================================
I will use the script next time for upgrades. Learning is good, even if time-consuming and frustratin'!
Any recommendations on how best to proceed? Just write a new partition table and go from there?
Otra vez -- Gracias amigos! (Oh yeah -- no ASCII characters for Spanish puctuation inherent in linux, are there?)