Is the headphones working?

it didn't work automatically, i had to go into the pulseaudio mixer's output devices tab and select headphones. then it worked fine.


turn down the volume a bit before turning on the headphones, my kids turtle beach gaming headset is what was handy to test it with and it was rather loud.


i also had to run alsactl restore manually, i thought that was in an init script somewhere...
edit: rc.alsa just needs to be made executable.

In my case, headphones doesn't work even if I turn it in pulseaudio. I hope that your new kernel was the solution :)

added the intel crystal cove pmic modules and now i have battery status. i need to prune the extra stuff out of the .config sometime soon.




almost two years since this adventure started.

Might be worth looking into etckeeper. I'm just starting with it, but it basically allows you to set up your /etc folder as a git instance (with proper permissions), so you can track any changes you made.

that sounds kinda cool. is it a local service or yet another cloud thing?



getting the sound working has given me a kick in the rump to look into bluetooth again. some relevant links are


https://wiki.debian.org/InstallingDe...inkpad/Tablet8
the btattach command is not present in slackware for some reason even though it has the latest version of bluez.. i have a whole bunch of hcd files from my windows partition from win8.1, i did not yet search the other m80ta i have that is "upgraded" to win10.


http://askubuntu.com/questions/63233...king-on-ubuntu not the same adapter but a similar problem

http://www.spinics.net/lists/linux-b.../msg66014.html i guess i need to learn about dsdt and figure out if this tablets id's are part of the driver.

It can be either. By default, it'll just create a git repo of your /etc/ directory. Then when you make changes, you just run etckeeper commit "Commit message here". Then it keeps all your changes separate (assuming you're good enough about committing all the changes when they happen so they can be easily referenced later). You're able to set it up to push those to a remote repository (I'd highly suggest using a private repo, as this contains important information on your system).

I have mine set up with a private repo on github (requires a $7/month subscription). I have 3 computers being tracked on there currently, and it makes it really easy to push one change to another computer or set up a ton of those commits into one patch you can apply to a new system (like all my /etc/profile changes).

ok, so i learned a bit about dsdt and came up with the dsdt.dsl file that contains this section about "BCM2E39" which i believe is the bluetooth module.


not that i have much idea what any of that means, but i checked the kernel source /drivers/bluetooth/hci_bcm.c file and the "BCM2E39" is listed in the device id section for 4.7-rc5. so in theory it should be able to work if the right firmware is found... i guess i will try the ubuntu live disc and see if i can make it work there, when time allows.

i tried to compile bluez in order to get the btattach command but the compile failed...

i hate to say it, but the latest ubuntu-studio installs correctly as long as it has a working internet connection. i used a usb nic and it did not fail during install, it set up the boot loader to multi boot with win10, and the on screen keyboard is available at login via a taskbar menu. i did not get bluetooth to work, but that could be because it was running a 4.4 kernel, and i did not try to make the audio work, but i assume it will with the same fix. the issue with the stylus and touchscreen killing each other was there just like with slack, so it is definitely a distro-agnostic problem. i probably should have paid more attention to what it did with the efi system partition before i blew it out and installed slack, oh well.

The problems with the stylus persist in Arch also. I suppose taht nobody check it.

i had to disable the kernel support for intel crystal cove pmic because it was causing the stylus to drop out, even with the touchscreen disabled. not sure why that would cause a problem, but the stylus was rock solid before i enabled it, and it is rock solid again since i disabled it. no battery status info for me.