First, on the way you use the CODE tags. That is fine, but it is much easier for you to extend your mouse sweep a little bit and include the command (and the prompt before it and even the prompt after the output) in your copy/paste. It will spare you the explaining of “lsusb returns” because it is already there between the code tags. And it will not alone show us exactly what command with what options you used (showing any typos), but the prompts will tell us it is complete, if you were root or not and what your working directory was. All included for almost the saame price 
My interpretation from what you posted:
The dmesg shows:
New USB device found, idVendor=14cd, idProduct=125c
And when you then look at the messages about sd 2:0:0:0 that ollow, you will see that it is found to be mass storage and given the id sdb.
In the lsusb you see
Bus 002 Device 006: ID 14cd:125c Super Top
which must be your device (same Vendor and Product code).
Finaly your fdisk show /dev/sdb but without any partitiioning.
My first conclusion is that your conclusion
the card is not recognized, I plugged in and is not detected at all,
is not true. The system detects it.
I checked on an SD card here, but that one is partitioned with one partition. So it seems that your partition table is overwritten for some reason.
You should be able to put a new partition table on it by using tools like fdisk, but also YaST > System > Partitioning…
And that brings us to the post of @vazhavandan. You should see that sdb there. Isn’t that not the case?
You can then create a partition on it (only one, with the maximum (the default I guess) size.
The problem is then if you want to create a file system on it. Mostly those cards are used in devices that use file systems of the FAT family and it realy depends on what you want to do with it. In any case, creating a FAT/VFAT/… or other MS file system on it is probably better done on a MS system. So here on openSUSE using YaST, it maybe better to check “do not format” when creating the partition table.
For something completely different!
I do not kow what those messages
hub 1-0:1.0: over-current condition on port 3
mean. Maybe you should ask in the Hardware forum.
