Originally Posted by Larswad

as an intermediate fix you can try installing wizard-mounter.
but that is a gui frontend though, maybe you wanted to use command line only.

Originally Posted by colin.stephane

Ok, I have investigated the problem, and it look like we gona go to a big pain to fix it ...

Well, to be able to mount samba shares (cifs) we need mount.cifs contained in package 'smbfs' that depend himself on package 'samba-common'.

And there is error in postinstallation script of the package 'samba-common', leaving the packages unconfigured.

I have tried to fix it but now the sed regex used in this script was mis-interpreted by busybox sed :-(

I'm trying to do my best but I do not promise anything on this subject ...

A++

Originally Posted by kaos_king

I dont mind gui but I had already tried it, got permissions denied but couldn't figure why.


Seems we need kernel-module-cifs. With this installed I ran the following command and it successfully mounted the drive

Code:

mount -t cifs //192.168.2.2/f$/ /home/user/MyDocs/KaosExt -o user=remote,pass=****

N.B. - I used IP not netbios name, and I dropped off ",ip=192.168.2.2,direct" from the end of the command that I was previously running. Happy now, now just need to search how to write a script that will auto sync.

-bash-2.05b# dpkg -l kernel-module-cifs
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-==============-==============-============================================
pn kernel-module-cifs <none> (no description available)
-bash-2.05b# lsmod | grep cifs
-bash-2.05b# mount -t cifs //192.168.1.2/Vrac /home/user/MyDocs/cifs-mount-testing -o user=myuser,pass=mypass
-bash-2.05b# lsmod | grep cifs
cifs 226904 1
-bash-2.05b# ll /lib/modules/$(uname -r) | grep cifs
-rw-r--r-- 1 root root 268.0k Sep 4 13:08 cifs.ko
-bash-2.05b# uname -a
Linux Nokia-N900 2.6.28.10-power48 #1 PREEMPT Sun Sep 4 12:58:34 CEST 2011 armv7l unknown
-bash-2.05b# mount | grep 192
//192.168.1.2/Vrac on /home/user/MyDocs/cifs-mount-testing type cifs (user=myuser,pass=mypass)
-bash-2.05b#

Originally Posted by colin.stephane

Strange, 'kernel-module-cifs' is related to default kernel (not kernel-power related) ...

On my side it work same (auto-loading) 'cifs' module compiled with kp v48.
A++

Originally Posted by kaos_king

Hmmm, maybe it was simply just the command that was the problem and I've got it wrong about kernel-module-cifs

Originally Posted by colin.stephane

It's easy to verify, just apt-get purge kernel-module-cifs before trying to mount your share ...

Please do it and report, then all users can benefit from this investigation without a doubt leaving ...

A++

Originally Posted by kaos_king

Pffff and there's me hoping for a lazy life

Okay, I went to find out for sure but......

Code:

/home/user # dpkg -l | grep cifs
rc  kernel-module-cifs                                  1.55.0-maemo1-ac0                          CIFS, Samba, Windows File Share support
/home/user # apt-get purge kernel-module-cifs
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Package kernel-module-cifs is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.

So it seems its there but not

Originally Posted by colin.stephane

So I just want to know from where you autoload the cifs.ko module, so, can you please put here the output of :

Originally Posted by colin.stephane

THIS TIME IT'S REALLY FIXED !!!


Fixed my brain, and tracked why reboots occurs when using 'ramzswap.ko' from my precedent integration of freemangordon working module (next time it's better if I don't mix source code ).



Download from here :

This power-kernel contain the working freemangordon ramzswap.ko module directly, no more need to compile yourself under scratchbox or me to provide as external module ...

Changelog :

Latests commits by Pali before he have school obligations (see post #) :

Commits '7ab052e2cf27b79aa8eea32b62f8cde752a87373' & '55fc617b021546d885dc413e15d99690488b3906' :

• Enable patch board-rx51-peripherals.diff again, need for I2C_BOARD_INFO bq27x00_battery module. Now disable autoloading bq27x00_battery module by blacklist. Rename blacklist file to kernel-power.blacklist.
  
  
• Support for binding and unbinding console drivers (CONFIG_VT_HW_CONSOLE_BINDING=y).

New changes by myself :

• Atop kernel patches removed, these are the ones causing camera not working ...
  
  
• Applied 'patch_swap_notify_core_support_2_2.6.28.diff' patch from freemangordon as requested by himself on post #.
  
  
• Applied 'update_mmu_cache_arm.diff' patch from freemangordon as requested by himself on post #.
  
  
• Applied 'fmtx_lock_power.diff' patch from freemangordon as requested by himself on post #.
  
  
• Backported kernel module 'ramzswap' integration for 2.6.28 to build it inline during kernel compilation as requested by freemangordon in this post #.
  
  
• Disabled statistics for the module 'ramzswap' (for performance reasons) as requested by freemangordon in this post #.
  
  
• Added script in '/etc/event.d/fmtxpower with '120' as default value for '/sys/class/i2c-adapter/i2c-2/2-0063/power_level' parameter as requested by freemangordon in this post #.
  
  
• Applied 'dspbridge_ioctl_buffer_overrun.diff' patch from freemangordon as requested by himself on post #.

Done !!!

A++

PS : freemangordon, sorry for all the bad things occurred ...