You are not logged in.
Hi,
I can't find out why, but my bluetooth is still "soft blocked". When I run "rfkill unblock all" or "rfkill unblock bluetooth" it is still "Soft blocked: yes". Even with root privileges. Can't
rfkill list
0: samsung-wlan: Wireless LAN
Soft blocked: no
Hard blocked: no
1: samsung-bluetooth: Bluetooth
Soft blocked: yes
Hard blocked: no
2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
lspci
00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b4)
00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b4)
00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b4)
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM65 Express Chipset Family LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller (rev 04)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 04)
01:00.0 Network controller: Intel Corporation Centrino Advanced-N 6230 [Rainbow Peak] (rev 34)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller (rev 06)
03:00.0 USB controller: ASMedia Technology Inc. ASM1042 SuperSpeed USB Host Controller
pacman -Q|grep blue
bluez 5.7-1
bluez-utils 5.7-
systemctl status bluetooth.service
bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled)
Active: active (running) since Mon 2013-09-09 14:59:19 CEST; 19min ago
Docs: man:bluetoothd(8)
Main PID: 353 (bluetoothd)
Status: "Running"
CGroup: name=systemd:/system/bluetooth.service
└─353 /usr/lib/bluetooth/bluetoothd
Sep 09 14:59:19 530uarch bluetoothd[353]: Bluetooth daemon 5.7
Sep 09 14:59:19 530uarch systemd[1]: Started Bluetooth service.
Sep 09 14:59:19 530uarch bluetoothd[353]: Starting SDP server
Sep 09 14:59:19 530uarch bluetoothd[353]: Bluetooth management interface 1.3 initialized
hcitool scan
Device is not available: No such device
hciconfig hci0 up
Can't get device info: No such device
bluetooth
bluetooth = off (software)
cat /etc/default/tlp | grep blue
# Radio devices to enable on startup: bluetooth wifi wwan
DEVICES_TO_ENABLE_ON_STARTUP="wifi bluetooth"
I'm not using connman.
Does anyone know how to solve it? My laptop is Samsung 530U.
Thanks
Last edited by Kotrfa (2013-09-12 06:58:40)
Offline
My rfkill switch sometimes gets stuck and only a reboot helps. Other times it works when I try to unblock / block / unblock / unblock "all" as root (sudo)
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Offline
I tried all of the above and even reboot. Nothing works.
Offline
On my machine, I have a "switch" for my WiFi. I put that in quotes because unlike past Thinkpads, it is actually just a button in function key row. The actual physical switches hard blocked things, but the button only seems to soft block according to rfkill. But even then, I cannot undo this soft block without actually using the button. I can also soft block with rfkill itself, which will allow me to toggle things from the command line. But the button seems to work on some kind of different software level.
So what I'm getting at here is whether you have possibly looked for a button or not. Maybe it is hiding somewhere and you have forgotten about it? I do that kind of crap all the time.
Offline
This laptop doesn't have a direct physical switch for that. Only "XF86WLAN" on Fn+F12 and it does nothing. I think there must be something "hidden" what blocks it.
Edit:
When I run live distribution (xubuntu or lubuntu), bluetooth normally works. Here are some outputs from lubuntu.
hciconfig -a
hci0: Type: BR/EDR Bus: USB
BD Address: 88:53:2E:C1:E4:D5 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING PSCAN
RX bytes:521 acl:0 sco:0 events:27 errors:0
TX bytes:1320 acl:0 sco:0 commands:26 errors:0
Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x59 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'lubuntu-0'
Class: 0x720100
Service Classes: Networking, Object Transfer, Audio, Telephony
Device Class: Computer, Uncategorized
HCI Version: 3.0 (0x5) Revision: 0x1b07
LMP Version: 3.0 (0x5) Subversion: 0xfc00
Manufacturer: Intel Corp. (2)
hcitool dev
Devices:
hci0 88:53:2E:C1:E4:D5
rfkill list
0: samsung-wlan: Wireless LAN
Soft blocked: no
Hard blocked: no
1: samsung-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
2: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
3: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
dpkg -l|grep blue
ii blueman 1.23-0ubuntu4 amd64 A Graphical bluetooth manager
ii bluez 4.101-0ubuntu8b1 amd64 Bluetooth tools and daemons
ii libbluetooth3:amd64 4.101-0ubuntu8b1 amd64 Library to use the BlueZ Linux Bluetooth stack
ii libgnome-bluetooth11 3.6.1-0ubuntu3 amd64 GNOME Bluetooth tools - support library
Last edited by Kotrfa (2013-09-09 16:15:17)
Offline
I wonder if it might have something to do with the rfkill module. Do modinfo -p rfkill. You will see that there are a couple options for the module itself. Maybe setting master_switch_mode=2 might help?
Offline
There must be problem with detecting my bluetooth device. There is no entry which rfkill can (un)block. Samsung-bluetooth is just some rubish. I need to detect my bluetooth device as hci0 as in lubuntu.
Thank you for your answers
Offline
There must be problem with detecting my bluetooth device. There is no entry which rfkill can (un)block. Samsung-bluetooth is just some rubish. I need to detect my bluetooth device as hci0 as in lubuntu.
Thank you for your answers
Here is how it works with my sony-bluetooth:
- if bluetooth is locked, there is only a sony-bluetooth switch
- if bluetooth is unlocked, I get another rfkill switch for hci0
-> make sure bluetooth.service is running
-> bluetoothctl recognizes the device now, hcitool not
-> turn bluetoooth device power on (bluetoothctl --> power on)
-> hcitool dev lists the device.
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Offline
UPDATED POST (Down)
Thanks for answer, but unfortunately no success.
bluetooth.service is loaded and running, acording to:
$systemctl status bluetooth.service
bluetooth.service - Bluetooth service
Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled)
Active: active (running) since Mon 2013-09-09 23:00:20 CEST; 3min 29s ago
Docs: man:bluetoothd(8)
Main PID: 368 (bluetoothd)
Status: "Running"
CGroup: name=systemd:/system/bluetooth.service
└─368 /usr/lib/bluetooth/bluetoothd
Sep 09 23:00:20 530uarch bluetoothd[368]: Bluetooth daemon 5.7
Sep 09 23:00:20 530uarch systemd[1]: Started Bluetooth service.
Sep 09 23:00:20 530uarch bluetoothd[368]: Starting SDP server
Sep 09 23:00:20 530uarch bluetoothd[368]: Bluetooth management interface 1.3 initialized
$dmesg|grep -i blue
[ 3.473824] Bluetooth: Core ver 2.16
[ 3.473978] Bluetooth: HCI device and connection manager initialized
[ 3.473988] Bluetooth: HCI socket layer initialized
[ 3.473991] Bluetooth: L2CAP socket layer initialized
[ 3.474010] Bluetooth: SCO socket layer initialized
[ 3.673306] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 3.673317] Bluetooth: BNEP socket layer initialized
but when I go to bluetoothctl and then try:
$power on
No default controller available
and similiar output is when I try "list, show, select" etc. Bluetoothctl doesn't see it and so hcitool dev:
$hcitool dev
Devices:
UPDATE EDIT:
I tried disable samsung-laptop with command:
rmmod -f samsung-laptop
and now I get different output:
dan@530uarch ~ $ rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
dan@530uarch ~ $ sudo rfkill unblock all
dan@530uarch ~ $ rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
dan@530uarch ~ $ sudo rfkill unblock bluetooth
dan@530uarch ~ $ rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
dan@530uarch ~ $ hciconfig
hci0: Type: BR/EDR Bus: USB
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
DOWN
RX bytes:6 acl:0 sco:0 events:1 errors:0
TX bytes:3 acl:0 sco:0 commands:1 errors:0
dan@530uarch ~ $ hcitool dev
Devices:
dan@530uarch ~ $ bluetoothctl
[bluetooth]# power on
No default controller available
dan@530uarch ~ $ bluetooth
bluetooth = off (software)
dan@530uarch ~ $ hcitool hci0 up
Unknown command - "hci0"
dan@530uarch ~ $ hciconfig hci0 up
Can't init device hci0: Operation not permitted (1)
dan@530uarch ~ $ sudo hciconfig hci0 up
Can't init device hci0: Operation not possible due to RF-kill (132)
I tried uninstall rfkill, but it didn't help. Even when I insert USB bluetooth adapter it is still blocked:
dan@530uarch ~ $ rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
2: hci1: Bluetooth
Soft blocked: yes
Hard blocked: no
dan@530uarch ~ $ rfkill unblock 2
dan@530uarch ~ $ sudo rfkill unblock 2
dan@530uarch ~ $ rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
1: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
2: hci1: Bluetooth
Soft blocked: yes
Hard blocked: no
It works in all other distributions, so there must be mistake in my arch installation. When I boot archlinux installation from USB stick, rfkill can block/unblock bluetooth without problems. Something must block all bluetooth devices.
Last edited by Kotrfa (2013-09-10 14:20:48)
Offline
Why is this marked as [SOLVED] when there is apparently no solution?!
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
I wrote it yesterday to first post on the begining of the thread. Maybe some bold font would help.
SOLUTION:
Delete file /etc/udev/rules.d/bt.rules:
## DISABLE BLUETOOTH
SUBSYSTEM=="rfkill", ATTR{type}=="bluetooth", ATTR{state}="0"
I have no idea, why there was this udev rule. I haven't added it (because I don't know how to write udev rules), there had to be some script (maybe from installation of some pkg), which added it.
Last edited by Kotrfa (2013-09-12 06:54:26)
Offline
Use pacman -Qo /etc/udev/rules.d/bt.rules to see if a package actually owns that crap.
In the future, although I will admit that it is kind of nice when people modify their first post with the final solution, it would be better if you kept the thread flowing in its natural conversation like way.
I think ideally, you should just make a new post with what you found to be the solution. Then on the bottom of the first post, indicate that the solution can be found through a link to that specific post (the date of the post is the link).
Offline
You are right, it would be better. I'm going to repair it.
Btw it is not owned by any of packages.
pacman -Qo /etc/udev/rules.d/bt.rules
error: No package owns /etc/udev/rules.d/bt.rules
Offline