Hi everybody!
I've a very strange and annoying problem: I have two different kernels in my slackware box; the first one is the pre-compiled 2.6.24.7-smp and the other is a custom self-compiled 2.6.27 kernel.
When I use the static binary of skype happens that with the pre-compiled kernel the login process works simply fine, but with my compiled kernel came out an error claiming for incorrect password (of course I know that my password is correct) even if internet works perfectly.
Is there a special setting to put into kernel's configuration to make skype login working? I really don't know how to address this issue.
Thanks very much for attention,

Karimo

Off hand I'd say to check the kernel options in the networking section -you've probably left out something there which is needed.

I've activated almost all related to networking and ieee80211 stack (I'm connecting through wifi) with no result.
What's happening????

Maybe something in the cryptography section, things like md5, sha1 sums (i.e. hash functions)?

Compare the config file of the kernel that works with the one you compiled (try 'diff') and check what you have changed / left out in your kernel.

It's a pre-compiled standard linux kernel (all the world is compiled in it xD)

Incredible...I've compiled in the new kernel quite all of the crypt chipers and algorithms...NOTHING...
no way...

The pre-compiled kernels in Slackware come with config files - see the /boot directory.

Sounds like you are running the huge kernel - this will have everything compiled in. Nevertheless you have removed something that is causing a problem. This will get you a copy of the running kernel

You may thenObviously replacing $wherever-mysources-are with something meaningful. You could do this on the kernel that works for you and then try removing bits at a time and checking it still works. Long winded maybe but it's not easy to say just what is giving Skype problems.

I've configured the nwtworking/crypt parts of the new kernel just like a working one with no result. I'm gonna sniff with wireshark what's happening...any other suggestion?

In Skype forums I found this thread about mysterious login failures. They mention Slackware and Gentoo systems but the cause is unknown (and no reference to the new kernel). But they mention Skype attempting to connect to a possibly wrong IP (I can't image how that could be, but...). Here it is:

http://forum.skype.com/index.php?showtopic=222461

Not a wrong IP but somehow a broken login server or peer. This has to be tracked by people who does have the problem i.e. trying to login from different location (net) / tracking the network packet flow.

regards

If it helps at all I am running the Slackbuild skype package fine on slack 12.2RC1 with the generic smp kernel.

And I also have it running fine on my 12.1 generic-smp kernel aswell with the same Slackbuild.