LinuxQuestions.org - upgrading to -current broke my bluetooth...

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - upgrading to -current broke my bluetooth... (https://www.linuxquestions.org/questions/slackware-14/upgrading-to-current-broke-my-bluetooth-4175476931/)

upgrading to -current broke my bluetooth...

Hello forum.

I've upgraded from 14.0 to -current on this acer chromebook c7 as it had issues with skype 4.2.xx (from slackbuilds)... asuming some newer libs may be needed to get skype working correctly..

however, now I have no bluetooth. :(

it was workign fine.. just opened bluedevil and rightclick to enable...

anyways.. this is what i have from the console trying to get it work

Code:

bash-4.2# uname -a

Linux chromebook 3.4.0 #1 SMP Tue Aug 27 20:51:28 PDT 2013 i686 Intel(R) Celeron(R) CPU 847 @ 1.10GHz GenuineIntel GNU/Linux

bash-4.2#    

bash-4.2# lsmod | grep blue

bluetooth            142917  11 ath3k,btusb,rfcomm

bash-4.2# 

bash-4.2# dmesg | tail

[  130.286072] ieee80211 phy0: WMM queue=3 aci=1 acm=0 aifs=7 cWmin=15 cWmax=1023 txop=0 uapsd=0

[  130.286082] ieee80211 phy0: WMM queue=1 aci=2 acm=0 aifs=2 cWmin=7 cWmax=15 txop=94 uapsd=0

[  130.286093] ieee80211 phy0: WMM queue=0 aci=3 acm=0 aifs=2 cWmin=3 cWmax=7 txop=47 uapsd=0

[  130.286527] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

[  130.287825] wlan0: dropped frame to 00:1e:e5:87:86:91 (unauthorized port)

[  130.309246] wlan0: moving STA 00:1e:e5:87:86:91 to state 4

[  140.722516] wlan0: no IPv6 routers present

[  154.251201] Bluetooth: RFCOMM socket layer initialized

[  154.251209] Bluetooth: RFCOMM ver 1.11

[  215.341996] EXT4-fs (sdb7): mounted filesystem with ordered data mode. Opts: (null)

bash-4.2# 

bash-4.2# hci

hciattach  hciconfig  hcidump    hcitool    

bash-4.2# hcitool dev

Devices:

bash-4.2# hcitool scan

Device is not available: No such device

bash-4.2# 

bash-4.2# ps fax | grep blue

  532 ?        Ss    0:00 /usr/sbin/bluetoothd

 1102 ?        S      0:00  \_ bluedevil-helper -session 1013f138117115000137902666300000007180022_1379026936_976499

 1121 ?        Sl    0:00  \_ /usr/bin/python /usr/bin/blueman-applet

 1630 pts/1    S+    0:00              \_ grep blue

 1097 ?        S      0:00 /usr/bin/bluedevil-monolithic -session 1013f138117115000137902645500000007180020_1379026936_976493

bash-4.2#

please advice

sadly, because it's -Current and things are ever-evolving in -Current you probably have an incompatibility with a driver module or some software internally, or even a SlackBuild you use may need a rebuild again -Current.

For proper support you should stick to using Slackware 14.0 so your hardware and applications can be properly supported and diagnosed for trouble.

well; don't take me too serious, but thank you for the piece of crap advice of staying in 14.0

as we are "slackware users" we like to check under the hood etc. I have no idea if what im doing here is reporting a bug, of if it just misconfiguration or something... either way, I did to share what's going on with the device

if you re-read my first post, this is an acer C7 chromebook. A piece of crap laptop i bought on a special rebate on 129 + taxes and transformed into a real computer after installing slackware on it. I'm sure that any of the readers of this slackware forum may found pleasant that this machine (under 200 dollars brand new) is fully capable of been a working station...

nevertheless, don't take me too serous

did you perform a fully upgrade to -Current?
Since i saw you are still using 3.4.0 kernel instead of 3.10.11

thank you willy for your interest.

I've haven't touched the kernel as it is the kernel from chromeOS as well as modules and one odd application i didn't know it existed named cgpt... as far as i know, uefi on this machine looks for chromeOS kernel...

something to test on a minimal slack install with the chromeos singing keys and slackware stock kernel... I was planning on doing so this weekend.

anyways, about the upgrade, bluez and others are staying on the same version except for bluedevil as kde change from whatever to 4.10 so the issue is very very odd.

Quote:

Originally Posted by kernel-P4N1C (Post 5026853)

Sorry if you took it the wrong way, but honestly it is more difficult to diagnose -Current compared to the mainstream releases, because of the fact packages get swapped out and upgraded, or even downgraded very often. Even Patrick has warned us about this in the past, same as Eric, Robby, and many others.

Diagnosing -Current is about like sticking a fork into a wall plug to test and see if it has a short. It's a real pain.

Because you avoided updating the kernel, yes, UEFI will look for ChromeOS's kernel, but there are ways to fix the UEFI loader to using the Slackware kernel like using GRUB2 or eLILO to install their own UEFI files, but due to this your BlueTooth stack might not have the right kernel to work with either, meanign the driver will load, but the software can't communicate with it.

Usually all BlueTooth toolkits like BlueDevil and BlueZ have a minimum version of the BlueTooth stack they work with. Check the BlueDevil documentation and see if it has any references to a minimum versioning to which kernel it requires, modules, and any other system daemons needed.

Edit:

From the documentation I have currently from Beyond Linux from Scratch, BlueZ version 4.101 requires at least:

D-Bus-1.6.14
Glib-2.36.4

...to work properly.

-Current at the time has:

BlueZ-4.99

...so you may want to grab the source package and check the dependencies, plus you'll need to check the firmware as well.

correct me if i'm wrong, but you said it's using the default kernel from chrome os?
So, how did you install your Slackware? Did you ran a full installation or perform a partial installation?

Sorry, i'm still confused with your machine configuration

yes, I'm using default chromeOS kernel.

after opening the uefi (aka developer mode) i repartitioned the hdd to ma space for the install. This chromebook has 320 GB hdd; then created 2 gpt partitions on a usb key.. one with 16 mb (for kernel) and formated then other as ext4.

on other machine,

Code:

installpkg --root /usb a/*.*?z

for having a minimal install bootabre usb. on ChromeOS, dump the kernel with config and dd to 16mb partition, set priorities and boot from usb (once the chromebook is in developer mode, ctrl+u)

from usb, loaded another key with the slack tree and did the same installpkg --root thing to the sda7 partition: rebooted to chrome OS, dd the kernel to sda6, made sda6 priority 5 and rebooted.

the system is dual booting chroeme and slacware as I'm using netflix...

now, back to my issue; I was sure it was related to configuration. I did configure everything to my tasty choice before the upgrade... so basically I booted from the usb key, reformat-reinstalled 14 and before went to bed I did the upgrade...

I'm now running -current (except for the kernel) and my bluetooth is working fine.

ic... Then i guess it might be configuration problem, since you don't change the kernel...

it was

as i said, it is working fine now.

back to mainline kernel; I'm still trying to figure out how to do it. I don't want to compile from source. In fact, i have the package installed; i just need to figure out how to load it