new kernel (2.6.34) issues (wlan / smbfs related)

[kolianto]

hello, just registered in here looking for help or shared discomfort

asus eeepc 900a, atheros wlan. on 2.6.30 no problems at all, could enable/disable the onboard wlan whenever i wanted to, and use it without any issues at all; 2.6.34 will complain about siocsifaddr - no such device error if i happen start with wlan disabled and reenable it when bt is already up and running.

second issue, i can't seem to mount any cifs/smbfs/netbios share on 2.6.34 - it'll just timeout (of course, no firewalls or ipsec or hosts allow/deny are involved). same host on 2.6.30 and the share will get mounted istantly. sup with that? anyone noticed?
thanks

maybe i wasn't clear the first time: it's a bug report - please, dev team, check the kernel config, thanks ;D

[roadkill]

check the blog post it fixed all my problems.

[kolianto]

I've tried the new (July 19th) kernel image, but it's still spewing out its "host is down" nonsense. Switching back to .30 and here we go, I can mount the share again. .34 is still a no-go.

[kolianto]

update: i am able to mount via smbmount and browse with smbclient, but smb4k WILL NOT mount or browse anything under 2.6.34 as per july 19th - no problem at all with 2.6.30.9...

[kolianto]

please, may i have an answer from a maintainer? your .34 kernel build won't let smb4k mount shares neither on cifs nor smbfs

[roadkill]

I don't think it's kernel related, most likely Vista/Windows 7
have a look here [Solved] Windows 7 and Samba Issue - windows-7

[kolianto]

nope, it's not windows related.

i repeat:
on 2.6.30.9 i can mount the remote share instantly from smb4k, on 2.6.34 i can't because of error 112 (host is down). mounting from commandline works, as it does browsing, it's smb4k that won't let me mount the share. please update either the smb4k package to the latest version (that fixes incompatibilities with new smbfstools and cifstools) or revert the kernel option.