I have before on opensuse used this keycombination, but I cant login it seems anymore.
When I start a konsole through the desktop no problem.
But after ctrl + alt + F5
I tried:
root
su
su -
My name, as shown when I log in.
Everytime it says login incorrect.
Did you try other terminals like ctrl-alt-F1???
Sure it is not a cap lock problem?? Remember names and passwords are case sensitive
There is no user “su”, nor is there a user “su -”, so it’s no wonder that doesn’t work.
“root” might have a different password.
But what do you mean with “My name, as shown when I log in”?
You need to enter the username of course, not your real name… 
So, you can login to X, but not to a text mode console?
Do you have auto-login enabled? Then try to logout, can you login again?
In addition to what gogalthorp wrote, also consider that Num-Lock is normally turned off in text mode. So if your password contains digits, that might be the problem. And the keyboard layout settings might be different as well, so try to enter your password instead of the username (to see what your typing) and check whether it is really correct.
PS: I can login on tty5 just fine. So that’s not a feature that got removed or something like that…
If you typed your name with an Uppercase letter while installing, and you made no other changes, by default openSUSE will change it to all lower case, ie:
If I entered my name as Gerry while installing, the display name would still be Gerry, but the User name would be gerry
To log in at a terminal, I need to enter gerry for the username, not Gerry
Perhaps that is your problem.
I first tried my name lower case. uppercase, only the frist letter uppercase.
The same name I see on the log on screen.
The password cant be wrong, because I type that everyday, because I have autologon disabled.
I openend yast, to check my name.
It seems right.
But I notice something weird.
At the password field there are 6 dots, but my password is longer. Is this causing the problem ?
it does not matter if I use ctrl alt F1 or F5.
No.
Not only does it hide the password with dots, but it also hides the length of the password from prying eyes by only giving 6 dots, no matter how long your password is.
Did you try changing your password? If not, try to change it and see what happens.
On 2014-12-09 04:16, Gps2010 wrote:
>
> I first tried my name lower case. uppercase, only the frist letter
> uppercase.
> The same name I see on the log on screen.
What about the keyboard layout in text mode, is it correct? It affects
password entry (the name you can see, not the psswd).
You can try by typing, without enter, the password on the login field.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
Thank you.
When I tried what you sugested, I found out that the numpad is not working right on that console. rotfl!
it does not give numbers but weird stuff. ( num lock is on )
Then I tried using the numbers above the letters (not the numpad) and I could log in rotfl!
Does this mean there is something wrong with the keyboard layout in text mode ?
Solved completely now! rotfl!
Google is your friend (sometimes)
System setting, input devices.
I changed it from 101 to a 104 keys keyboard.
I used google, and pictures of keyboards layouts to determine which one I have. ( some dell keyboard )
I first googled 101 keys, and those looked different. Same for 102 and 103.
Then 104 and bingo.
I used an usb keyboard before, but that one gave up after more then 10 years.
Replaced it with this one. An dell with a ps2 ? connection.
At first I thought there were no problems, all seems to work fine in yast (US international), but there is a KDE setting menu too.
After changing the KDE option to 104 all is working as it should again, also in text mode.
We were suspecting that something like this was going on.lol!
So pleased to hear you have it solved.
At first I thought there were no problems, all seems to work fine in yast (US international), but there is a KDE setting menu too.
After changing the KDE option to 104 all is working as it should again, also in text mode.
Makes a lot of sense, now.
Congratulations.
It was very frustrating at first.
What do mean log in incorrect ? ( stupid computer >:( ) I am typing that bloody password every day.
Even went to the log in screen to check my name LOL
And the fact that I could log in as root, su, password, in the console from the kde desktop, only added to my confusion.
I think the problem origenated because this is not being an usb keyboard.
Before I had some packard bell multimedia USB keyboard, and even some of the extra keys worked. ( the on off switch to name one)
I can now even use this again: € the euro symbol.
For other having issues with the € symbol, first thing to try is not to use the left alt key but the right alt key. ( and the 5 key, not from the numpad )
In windows there is no difference between them, on Linux there is.
And on this keyboard they also have different names.
One is alt, the other the right one is Alt Gr.
You do not see this anymore on modern keyboards.
On 2014-12-11 02:06, Gps2010 wrote:
>
> Google is your friend (sometimes)
>
> System setting, input devices.
>
> I changed it from 101 to a 104 keys keyboard.
AH! Very curious your problem.
> At first I thought there were no problems, all seems to work fine in
> yast (US international), but there is a KDE setting menu too.
> After changing the KDE option to 104 all is working as it should again,
> also in text mode.
Yes, the text mode keyboard is only set in yast (or with some command
unfamiliar to me). In graphics mode, you can bypass that setting and use
a different one. I thought that might be your problem. Well, not
exactly, but related 
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
And the problem is back…
I checked of course this thread, but its still set to the generic 104 keys. :\
Because of reading this topic, I tried it with the numbers not from the numpad, and I could log in.
Found out something interesting, at least to me.
ctrl+alt+ F5
su password, that does not work
What does work is log in as user, en then do su and password.
What also works after init 3:
root
password.
This has been nagging at me for some time.
I was 100% sure I used root password before on openSUSE.
I did however not remember the init 3 part. (exits the desktop and x server)
So tried again sh NIVIDIA, because before init 3 it was complaining I was still running X server.
Bloody computer was of course right. ctrl+alt+F5 does give you a terminal but it wont stop the desktop.
Still I failed at installing the nvidia driver.
It complains about an openSUSE package: | nvidia-gfxG03-kmp-desktop
|
|
Then the nvidia driver sugested to do zypper update nvidia-gfx-kmp
That did not work either as I expected. Because it checked the installed driver and ended with nothing to do.
Do you guys know that feeling ?
I am gonna fine tune my pc with an axe 
For now I am gonna look at, install nvidia drivers the hardway.
I can of course remove nvidia-gfx-kmp through yest, but first I will do some reading before I mess things up.
It would not be the first time I tried to install prop, drivers and ended up with no desktop.
Some people might start to wonder why ?
Why do you want newer nvidia drivers then provided by openSUSE.
It was one of the solutions offered on this forum, for xbmc missing text in the menus.
https://forums.opensuse.org/showthread.php/498989-13-1-NVIDIA-libGL-renderer-problem
Back on topic
root
password
works after init 3.
( init 5 is go back to the “normal” runlevel.)
On init 5
root
password
does not work.
Problem solved, ty to a dutch Linux forum and a user currently using Ubuntu.
Don’t get me wrong, this is not an attack on this forum. But that dutch forum has a few longtime Linux users.
Some also work with Linux professional, and to name one distro they used years ago, Slackware, our mommy. 
From the days when, if you used Linux you had to compile most or all yourself.
Back to openSUSE and the solution for me.
After ctrl +alt+ F5 press the numlock key. In my case this means, the numlock led goes out, but the numpad is working as it should. rotfl!
LOL.
So the problem was user error.
I would never run into that problem, because I don’t use the numeric keypad for passwords. I use it to enter data into a spreadsheet, or when doing something numeric (playing sudoku, for example). But, for ordinary mixed typing, I use the regular keys.
On 2014-12-21 14:56, Gps2010 wrote:
>
> Problem solved, ty to a dutch Linux forum and a user currently using
> Ubuntu.
Well, a different group of people may have different experiences, may
have seen the problem before. And if they use another language, they
also use another keyboard. Of course we don’t feel bad about that
> Back to openSUSE and the solution for me.
> After ctrl +alt+ F5 press the numlock key. In my case this means, the
> numlock led goes out, but the numpad is working as it should. rotfl!
Have a look at the file “/etc/sysconfig/keyboard”. This line:
KBD_NUMLOCK=“yes”
It is probably set to “bios”.
–
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)
This doesn’t work in 13.2 (again, it already didn’t work in 12.1 and 12.2… :-/):
http://bugzilla.opensuse.org/show_bug.cgi?id=901916
The reason is that systemd-vconsole-setup now takes care of enabling NumLock (before it was /etc/init.d/kbd which doesn’t exist any more), but this is started already before the real rootfs is mounted and /etc/sysconfig/keyboard is missing from the initrd.
You can add it with “sudo dracut --force -I /etc/sysconfig/keyboard” though, then NumLock should be turned on automatically.
For some reason this still won’t work for text mode though (didn’t in 13.1 and earlier either), but the login prompt would at least say “Hint: NumLock is OFF”, although the NumLock LED will stay on.
Thanks, without out looking I know its set to bios.
Which works fine for the desktop, but clearly not on the commandline.
So I should change that to yes ? ( and maybe turn if off in the bios ? )
No, this won’t have any effect.
See my previous post.
Yes I am still on 13.1 so I can confirm its not a new bug.
And I do not remember when, but I remember switching it on in the bios, and in kde.
Probably even before release 13.1 though. ( the bios part)