Hi,
I have open suse and downloaded a chrome browser to replace mozilla. However I messed something and now my laptop asks linux-smt1 login and password. I have tried old ones but allways login fails. Any solutions.
Hi,
I have open suse and downloaded a chrome browser to replace mozilla. However I messed something and now my laptop asks linux-smt1 login and password. I have tried old ones but allways login fails. Any solutions.
Which version of openSUSE do you have? Which DE are you using (KDE, GNOME, …)?
And how exactly did you install Chrome?
Can you log in to IceWM? (for KDE you have to click the “gear” symbol on the login screen and choose it there)
Can you log in to text mode?
Press Ctrl+Alt+F1 and enter username/password there.
My version: open suse 11.4 “Celadon”-Kernel 2.6.37.6-24-default(tty1)
Chrome I downloaded from google pages, version for open suse/fedora - 32 bit
After long text it asks linux-stm1 login and after that password
cntr+alt+f1 didn’ help
What do you mean with “didn’t help”?
Don’t you get to text mode with Ctrl+Alt+F1?
Or are you unable to login there as well? In this case try to log in as root.
With or without ctr+alt+f1 there comes long text about starting services, failed and skipped services and then welcome words and asking linux-stm1 login and password. When I write password comes info : login incorrect.
Log in root - how?
Type “root” as username (without the quotes of course), the password should be the same.
And if you can’t log in a root due to a forgotten password, then you may reset the root and user passwords by booting to single user mode following the guide at:
https://en.opensuse.org/SDB:Recover_root_password#Single_user_mode
On 2013-07-13 13:46, Arihannu wrote:
> With or without ctr+alt+f1 there comes long text about starting
> services, failed and skipped services and then welcome words and asking
> linux-stm1 login and password. When I write password comes info : login
> incorrect.
You are in emergency mode. Only root login will work, and then you have
to repair the problem.
> Log in root - how?
Enter ‘root’, then root’s password. Yes, you know root’s password,
because you type it to install any software.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
Why do you think he’s in emergency mode?
He’s using 11.4, so no systemd yet, therefore no emergency mode…
It’s just that X fails to start it seems, and login as user is not possible.
@Arihannu:
If you can log in as root, please check if maybe your disk is full:
df -h
I can’t think of anything else that could have happened if you really just installed the Chrome RPM…
And also have a look at /var/log/Xorg.0.log, maybe there’s a clue in there why X refuses to start.
On 2013-07-13 16:16, wolfi323 wrote:
>
> robin_listas;2571562 Wrote:
>> You are in emergency mode. Only root login will work, and then you have
>> to repair the problem.
>>
> Why do you think he’s in emergency mode?
> He’s using 11.4, so no systemd yet, therefore no emergency mode…
Emergency mode predates systemd by 10 years at least.
I think he must be in that mode because he says there are failed
services - or so I understood.
True, in 11.4 emergency mode is very explicit, it says something like
welcome to emergenccy mode and a description of the problem. So maybe it
is not emergency mode, I missed the 11.4 part.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)
Well,
Here are my suggestions…
If you are able to login as root to your machine in any way (Emergency Mode(GUI), Command line only, SSH, etc)
Then you should try to determine exactly what is breaking in your bootup
Immediately after you experience a problem, you can grab the last 100 lines of your syslog which hopefully should be informative
tail -n 100 /var/log/messages
If that isn’t enough and you need the entire boot log, you can write the entire boot log to a file like this (modify filename and path however you wish, eg the example places in /root/Documents) You can then either paste the contents of that file into a post (maybe only relevant parts if you feel up to deciding what is relevant and what isn’t) or SUSE Paste
journalctl -b > /root/Documents/bootlog.txt
Ordinarily downloading and installing Chrome shouldn’t cause a problem, but… who knows…
Typically getting Chrome should start at this page
https://www.google.com/intl/en/chrome/browser/
The link should install the Google Chrome repo and current latest stable browser from that repo.
It could be useful to know what repo actually exists on your machine, from the same console you used above for throubleshooting you can run these commands
The following lists all your repos in detail (the actual URI path)
zypper lr -d
Information about your current installed Chrome
zypper info chrome-stable
If you post the above information
HTH,
TSU
Hm, I thought “emergency mode” was a new concept of systemd.
I can’t remember seeing something like that with sysvinit. Didn’t that just drop back to single user mode in case of failure?
Well, it’s been a while since I last used sysvinit…
True, in 11.4 emergency mode is very explicit, it says something like
welcome to emergenccy mode and a description of the problem.
That’s how it is with systemd. Did sysvinit already act like this?
On 2013-07-14 15:56, wolfi323 wrote:
> Hm, I thought “emergency mode” was a new concept of systemd.
> I can’t remember seeing something like that with sysvinit. Didn’t that
> just drop back to single user mode in case of failure?
> Well, it’s been a while since I last used sysvinit…
I have an 11.4 machine nearby
No, it is not level 1, but similar, even more limited than level 1,
because /usr is not mounted, IIRC (if it uses a separate partition).
>> True, in 11.4 emergency mode is very explicit, it says something like
>> welcome to emergenccy mode and a description of the problem.
> That’s how it is with systemd. Did sysvinit already act like this?
systemv acted much better than systemd. Actually, I have a bugzilla
opened because systemd information when dropped into emergency mode was
insufficient, as compared to the info given by systemv.
Do something to test it: change an entry in fstab to an incorrect one,
so that boot fails. Then boot, and watch what happens: do you see a
message clearly saying that a partition is wrong, can not be mounted?
Later I can find the bugzilla, because that is the test done there.
–
Cheers / Saludos,
Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)