• Willkommen im Linux Club - dem deutschsprachigen Supportforum für GNU/Linux. Registriere dich kostenlos, um alle Inhalte zu sehen und Fragen zu stellen.

SE K750i findet openSuSE nicht :-(

gandalfsz

Newbie
Mein K750i findet meinen PC nicht. Mit dem gleichen Bluetoothdongle gings auf nem anderen PC. Der PC erkennt das Handy. Ich verwende KDE 3.5.5 "release 45"
mfg Daniel
 
OP
G

gandalfsz

Newbie
Das ist das was ich herausgefunden hab:

Code:
daniel@linux-danielzimmer:~> kbluetooth -v
Qt: 3.3.7
KDE: 3.5.5 "release 45"
KBluetooth:
daniel@linux-danielzimmer:~>

mfg Daniel
 

stka

Guru
Also wir das Handy doch erkannt. Welche Suse Version hast du installiert? Hast du die Dateien im Verzeichnis /etc/bluetoth angepasst?
 

stka

Guru
Also wir das Handy doch erkannt. Welche Suse Version hast du installiert? Hast du die Dateien im Verzeichnis /etc/bluetooth angepasst?
 
OP
G

gandalfsz

Newbie
opensuse 10.2.
hier mein /etc/bluetooth:
hcid.conf:
Code:
#
# HCI daemon configuration file.
#

# HCId options
options {
	# Automatically initialize new devices
	autoinit yes;

	# Security Manager mode
	#   none - Security manager disabled
	#   auto - Use local PIN for incoming connections
	#   user - Always ask user for a PIN
	#
	security auto;

	# Pairing mode
	#   none  - Pairing disabled
	#   multi - Allow pairing with already paired devices
	#   once  - Pair once and deny successive attempts
	pairing multi;

	# Default PIN code for incoming connections
	passkey "****";
}

# Default settings for HCI devices
device {
	# Local device name
	#   %d - device id
	#   %h - host name
	name "SuSEDaniel";

	# Local device class
	# e.g.
	#  0xsss100 = Computer
	#  0xsss104 = Computer Desktop
	#  0xsss108 = Computer Server
	#  0xsss10c = Computer Laptop
	# The 'sss' above defines the service-class (not quite, only the
	# first 11 bits, the next 11 define the device-class, than 2 format bits.)
	# See https://www.bluetooth.org/foundry/assignnumb/document/baseband
	# for more information.
	# 0x100bbb stands for "Object Transfer  (v-Inbox, v-Folder, ...)"
	# 0x020bbb stands for "Networking (LAN, Ad hoc, ...)"
	class 0x7f0100;

	# Default packet type
	#pkt_type DH1,DM1,HV1;

	# Inquiry and Page scan
	# valid parameters: enable | disable
	iscan enable;
	pscan enable;

	# Default link mode
	#   none   - no specific policy 
	#   accept - always accept incoming connections
	#   master - become master on incoming connections,
	#            deny role switch on outgoing connections
	lm accept;

	# Default link policy
	#   none    - no specific policy
	#   rswitch - allow role switch
	#   hold    - allow hold mode
	#   sniff   - allow sniff mode
	#   park    - allow park mode
	lp rswitch,hold,sniff,park;
}

und rfcom.conf
Code:
#
# RFCOMM configuration file.
#

#rfcomm0 {
#	# Automatically bind the device at startup
#	bind no;
#
#	# Bluetooth address of the device
#	device 11:22:33:44:55:66;
#
#	# RFCOMM channel for the connection
#	channel	1;
#
#	# Description of the connection
#	comment "Example Bluetooth device";
#}
 

stka

Guru
deine rfcom.conf ist auch nicht richtig, die sollte so aussehen:
#
# RFCOMM configuration file.
#

rfcomm0 {
# # Automatically bind the device at startup
bind yes;
#
# # Bluetooth address of the device
device 00:1A:75:C1:CD:16;
#
# # RFCOMM channel for the connection
channel 1;
#
# # Description of the connection
comment "Mein Handy";
}
 
Oben