Symbian bluetooth action in portage!

[Paradoxx]

i ned help whit my p3nfsd evrey time im traing to start it i get error


/etc/init.d/symbian start
Can't create device: Address already in use
* Mounting Symbian -p800 device on /mnt/p800 - Please accept the connection on the device...
p3nfsd version 5.13a
Usage: p3nfsd {-series3|-series3a|-series5|-series60|-n9210|-UIQ}
[-v] [-v] [-v] [-nobackground]
[-dir <directory>] [-user <uid>]
[-tty <dev>] [-speed <baud>] [-tcp]
[-conn <prog>] [-disconn <prog>]
[-oldnfsc] [-noflow] [-timeout <msec>]
[-epoc32_filesystem]
Series 3a only with nfsc:
[-wakeup] [-shell prog]
Current settings:
-dir /mnt/psion
-user golab
-tty /dev/ttyS0
-speed 115200
/sbin/runscript.sh: line 117: --: command not found
* Failed to start the symbian service - Please verify your settings in /etc/conf.d/symbian [ !! ]




and /etc/conf.d/symbian luks like

#!/sbin/runscript
# Copyright 1999-2003 Gentoo Technologies, Inc.
# Distributed under the terms of the GNU General Public License v2

#NB! Config is in /etc/conf.d/symbian

depend() {
need modules portmap
}

checkconfig() {
# The following two modules should be given an alias in /etc/modules.d/aliases
# from the symbian ebuild, so they are autoloaded when needed. Perhaps all four...
# modprobe bluez &> /dev/null
# modprobe hci_usb &> /dev/null
modprobe rfcomm &> /dev/null
modprobe l2cap &> /dev/null

if [ ! -e /proc/bluetooth ] ; then

eerror "Bluetooth not supported by the kernel"
return 1
fi

if [ ! -f /proc/bluetooth/rfcomm ] ; then

eerror "Module rfcomm not loaded or compiled into the kernel"
return 1

fi

if [ ! -f /proc/bluetooth/l2cap ] ; then

eerror "Module l2cap not loaded or compiled into the kernel"
return 1

fi

if [ -e /etc/conf.d/symbian ]; then

source /etc/conf.d/symbian

else

eerror "/etc/conf.d/symbian is missing"
return 1

fi

#Replace this with net.hci0 perhaps...
hciconfig hci0 up
rfcomm bind $DEVTYPE $BDADDR $CHANNEL
}

start() {
checkconfig || return 1
ebegin "Mounting Symbian $DEVICE device on $MOUNTDIR - Please accept the connection on the device"
start-stop-daemon --start --quiet --exec /usr/bin/p3nfsd \
-- -quiet -dir $MOUNTDIR -$DEVICE -tty $DEVTYPE
eend $? "Failed to start the symbian service - Please verify your settings in /etc/conf.d/symbian"
}

stop() {
# I have to zap the service after its shut down, because
# start-stop-daemon is retarded
ebegin "Releasing Symbian device from $MOUNTDIR"
/bin/ls $MOUNTDIR/exit &> /dev/null
/etc/init.d/symbian zap &> /dev/null
rfcomm release all
eend $? "Failed to stop the symbian service - Maybe NFS is stuck in the mud again"
}


And /etc/conf.d/symbian



# Specify where in the file system you want your

# device to be mounted. The default is /mnt/psion,

# and does NOT need to be specified.

MOUNTDIR="/mnt/p800"



# Specify your device BDADDR - this is MANDATORY!

# You can find the device BDADDR by issuing the

# command: 'hcitool inq'

BDADDR="00:0A:D9:17:C4:A9"



# Specify what channel you want to use - this is MANDATORY!

# Default for Nokia 3650 / Nokia 7650 / Nokia N-Gage is channel 3

# Default for Ericsson P800 is channel 4

CHANNEL="4"



# Specify what terminal type to use - this is MANDATORY!

# Bluetooth is normally /dev/rfcomm0

# Serial is noramlly /dev/ttyS0

# IrDA is normally /dev/ttyIR0

DEVTYPE="/dev/rfcomm0"

# Specify your device type from the selection below - this is MANDATORY!

# EPOC/16 is -series3 / -series3a

# EPOC/32 is -series5

# Nokia 3650 / Nokia 7650 / Nokia N-Gage (SymbianOS 6.0) is -series60

# Nokia 92X0 (SymbianOS 7.0) is -n9210

# Ericsson P800 (SymbianOS 7.0) is -p800

#

# {series3, series3a, series5, series60, n9210, p800}

#

DEVICE="-p800"


#Not yet used

#PASSWORD=""

#USER=""

SPEED="115200"


do sombodey cnown what is wrong ?
_________________
//Jag är dyslectiker

//pless dount complain im dyslectic


//i whas born in hell im going to hell

[Loke]

I recommend trying to understand exactly what the script tries to automate. I should probably have rewritten the whole thing, but right now I dont have any free time to hack on this - sorry

It is possible to do this manually, and if you figure it out, its much easier to understand what fails.

Sorry, I cant help more. Ill post an update here when I get some free time to improve this further.
_________________
I'm not saying there should be capital punishment for stupidity, I'm saying why don't we take the warning labels off of everything, and let the problem take care of itself?

[kevin_i_orourke]

Is bluez-kernel-2.3 still deprecated?

I've read through bug 18571 and that seems to suggest that with the new ebuilds everything will be OK.

The ebuild for bluez-bluefw still wants to build bluez-kernel though.

[Jhurleston]

I'm a bit new to Linux, Gentoo and this bluetooth stuff.
I made this mistake, before I found out about the advice below.

Is there a solution?

I clicked on the link below, and didn't understand to mutch. I saw the line about the bluetooth fix, does that mean that this bug, has been eliminated?

Also, do the ebuild files, enable me to do a manual fix of the source (src)?

[chomber]

[Josuke]

take a look here

http://datadevil.demon.nl/docs/bluetooth.html
_________________
fletto i muscoli...e sono nel vuoto

[Loke]

I see people still are confused about the --quiet flag given to p3nfsd. I submitted a patch for p3nfsd to accept --quiet flags, so unless your p3nfsd has this patch (which it most certainly does not) it will give an error when giving the --quiet flag.

I promised to start working on this again this xmas, but unfortunately I dont have a bluetooth phone any more So untill I can get a new one, I probably wont be able to test much after all.
_________________
I'm not saying there should be capital punishment for stupidity, I'm saying why don't we take the warning labels off of everything, and let the problem take care of itself?

[Paradoxx]

Loke can u update the howto so it worcs on kernel 2.6.0?
_________________
//Jag är dyslectiker

//pless dount complain im dyslectic


//i whas born in hell im going to hell

[sirro]

I made an ebuild for p3nfsd: https://bugs.gentoo.org/show_bug.cgi?id=37010
If anyone is interested...

[sumC]

Hi all,
Heres a update for 2.6 kernel, although I couldn't get it to work for me

First of all you don't need anything else then

bluez-libs
bluez-utils
bluez-bluefw

The kernel module is part of the mainline kernel. I used 2.6.4 which has the latest bluez kernel drivers.

In the /etc/conf.d/symbian script change these values:
DEVTYPE="/dev/rfcomm0" to "/dev/bluetooth/rfcomm/0"
The location has changed in 2.6

And, CHANNEL="3" to "11"
From p3nfs homepage:
"due to a bug in nfsclient, it was usually 3 on series60 devices and 4 on the p800 up till nfsclient version 2.6. On newer versions it should be 11 if no program occupied this rfcomm port before."

In /etc/init.d/symbian on line:
"if [ ! -f /proc/bluetooth/rfcomm ] ; then"
change the "-f" to "-e"
And remove the -quiet from the start() function as noted earlier in this thread.

Start the nfsclient on the phone and start the deamon.
Theres a message on the phone asking you to accept the connection. Now it should work.

I wasn't that lucky as usual.
The phone ask if I want to accept the connection. As soon as I press yes the client displays "connection closed ( -<some number>)" and the deamon stops with "nfs mount /mnt/nokia: (errno 19) No such device".
I get this error with or without the script and finally gave up.

Heres the exact output:

[Loke]

Ive updated the original post so it works on 2.6.X kernels. Im hoping it works on 2.4.X also, but please report back on this. From a developers point-of-view an init-script should not check if the appropriate modules are loaded, like my symbian init script does. This should be handled by the kernel. Unfortunately, this doesnt always work as it should (for many reasons)

So when the layout in the /proc filesystem changed from 2.4.X to 2.6.X, it broke alot of applications and scripts. If the symbian init script complains about "missing" something, try to comment out that specific check in the script and see if it works. I havent decided yet how to solve this problem, since there are several solutions to the problem. Suggestions are welcome...

Also a note to you Sony Ericsson T610/T630/K700i users. This is intended for symbian devices, and will not work on your models. Perhaps openobex can help you push files over the BT-stack to your phone.
_________________
I'm not saying there should be capital punishment for stupidity, I'm saying why don't we take the warning labels off of everything, and let the problem take care of itself?