hi Curaga!,
first of all thenks a lot for your attention. Well, at least I learned to make files persistent. In addition I stopped for ever distinguishing between files and folders: the last act in leaving $$ndows. I know that in modprobe.d everything with ".config" will be parsed. However, reading doesn't mean doing! I mean alsa reads and doesn't do! Here an example 15 min. old, I think you will like it:
I boot with the ominous option "kmap=qwertz/de-latin1-nodeadkeys". By getting a perfect X configuration I also got back the us keyboard. Of course: the keyboard section in X. I didn't find a valid reference in our forum and the attempt to get an xorg.conf generated in text modus by X leaded to a crash, believe or not. On the other hand I know that X executes fist the code from xorg.conf, in case the directives are wrong or absent X will use the own configuration. Finally I made the following xorg.conf:
Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "de"
EndSection
I mean that is the entire file, and now: ÜüÄäÖöß~@
I have my german keyboard working! I am sure that will be helpful to many users.
Well, back to alsa, I did take a superficial look to the files discovering that a huge amount of code resides in "/temp". Such files and dirs are just linked to the "official place".
Other code is on place, possibly the "static" one and also possibly the right place to search. But where I was especting value assignments I found "floors" of "conditionals". Logic! This distribution is a little linux jewel and also more complicated.
J need to add that I didn't install the packages alsa-config.tcz and alsaconf.tcz, the included explanation was too cryptic for me.
Finally, perhaps you know some tinycore-alsa-guru and you can ask him, or even better, you will get some brilliant idea: addefinitively my weapons are over!
Hoping in your further help!