LinuxQuestions.org
Support LQ: Use code LQ3 and save $3 on Domain Registration
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware > Slackware - Installation
User Name
Password
Slackware - Installation This forum is for the discussion of installation issues with Slackware.

Notices


Reply
  Search this Thread
Old 07-02-2016, 03:21 PM   #136
koroki
Member
 
Registered: Mar 2015
Location: Japan
Distribution: Arch Linux
Posts: 30

Rep: Reputation: Disabled

Is the headphones working?
 
Old 07-02-2016, 06:41 PM   #137
ElfShotTheFood
Member
 
Registered: Jul 2014
Location: New Jersey
Distribution: Slackware
Posts: 70

Original Poster
Rep: Reputation: 0
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.

Last edited by ElfShotTheFood; 07-02-2016 at 06:52 PM.
 
Old 07-03-2016, 05:46 AM   #138
koroki
Member
 
Registered: Mar 2015
Location: Japan
Distribution: Arch Linux
Posts: 30

Rep: Reputation: Disabled
Quote:
Originally Posted by ElfShotTheFood View Post
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
 
Old 07-03-2016, 06:06 PM   #139
ElfShotTheFood
Member
 
Registered: Jul 2014
Location: New Jersey
Distribution: Slackware
Posts: 70

Original Poster
Rep: Reputation: 0
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.
 
Old 07-03-2016, 11:48 PM   #140
bassmadrigal
Senior Member
 
Registered: Nov 2003
Location: Newport News, VA
Distribution: Slackware
Posts: 3,064

Rep: Reputation: 1455Reputation: 1455Reputation: 1455Reputation: 1455Reputation: 1455Reputation: 1455Reputation: 1455Reputation: 1455Reputation: 1455Reputation: 1455
Quote:
Originally Posted by ElfShotTheFood View Post
i didn't backup the files i changed in /etc, so i will be reading my own instructions above.
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.
 
Old 07-04-2016, 10:05 PM   #141
ElfShotTheFood
Member
 
Registered: Jul 2014
Location: New Jersey
Distribution: Slackware
Posts: 70

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by bassmadrigal View Post
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
Quote:
Support for the BCM43241 rev B5 chipset was added in early March in the bluetooth-next kernel development tree. It is expected to be officially part of Linux 4.6 or 4.7. Building a custom kernel is required in the meantime, including the following commit: Add BCM2E55 ACPI ID used in Lenovo ThinkPad Tablet 8.

Enabling this Bluetooth chipset is done via the new btattach command, released in BlueZ version 5.37. Until this version is packaged in Debian, instructions about how to build it can be found here Building Bluez 5.37 on Debian Jessie. Once compiled, the btattach command is found in "debian/tmp/usr/bin/".

Then the binary firmware file must be copied in /lib/firmware/brcm/BCM.hcd and can be found on the original Windows partition. It has the following format "BCM4324B5_vvv.www.xxx.yyyy.zzzz.hcd" with the current version being BCM4324B5_002.006.006.0601.1170.hcd .

# cp ./BCM4324B5_002.006.006.0601.1170.hcd /lib/firmware/brcm/BCM.hcd

Finally, Bluetooth can be enabled with btattach (built previously):

# btattach --bredr /dev/ttyS1 -P bcm &
Attaching BR/EDR controller to /dev/ttyS1
Switched line discipline from 0 to 15
Device index 0 attached

Upon each reboot, btattach will have to be entered once again until btattach is fully supported by the Debian boot scripts.
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.
 
Old 07-04-2016, 11:59 PM   #142
bassmadrigal
Senior Member
 
Registered: Nov 2003
Location: Newport News, VA
Distribution: Slackware
Posts: 3,064

Rep: Reputation: 1455Reputation: 1455Reputation: 1455Reputation: 1455Reputation: 1455Reputation: 1455Reputation: 1455Reputation: 1455Reputation: 1455Reputation: 1455
Quote:
Originally Posted by ElfShotTheFood View Post
that sounds kinda cool. is it a local service or yet another cloud thing?
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).
 
Old 07-05-2016, 11:07 PM   #143
ElfShotTheFood
Member
 
Registered: Jul 2014
Location: New Jersey
Distribution: Slackware
Posts: 70

Original Poster
Rep: Reputation: 0
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.

Quote:
Scope (_SB.URT1)
{
Device (BTH0)
{
Name (_HID, "BCM2E39" /* Broadcom BT Serial Bus Driver over UART Bus Enumerator */) // _HID: Hardware ID
Name (_DEP, Package (0x03) // _DEP: Dependencies
{
GPO0,
GPO2,
URT1
})
Method (_STA, 0, NotSerialized) // _STA: Status
{
Return (0x0F)
}

Method (_CRS, 0, NotSerialized) // _CRS: Current Resource Settings
{
Name (UBUF, ResourceTemplate ()
{
UartSerialBus (0x0001C200, DataBitsEight, StopBitsOne,
0xFC, LittleEndian, ParityTypeNone, FlowControlHardware,
0x0020, 0x0020, "\\_SB.URT1",
0x00, ResourceConsumer, ,
)
Interrupt (ResourceConsumer, Edge, ActiveHigh, ExclusiveAndWake, ,, )
{
0x00000046,
}
GpioIo (Exclusive, PullDefault, 0x0000, 0x0000, IoRestrictionOutputOnly,
"\\_SB.GPO0", 0x00, ResourceConsumer, ,
)
{ // Pin list
0x0034
}
GpioIo (Exclusive, PullDefault, 0x0000, 0x0000, IoRestrictionOutputOnly,
"\\_SB.GPO2", 0x00, ResourceConsumer, ,
)
{ // Pin list
0x0009
}
})
Name (PBUF, ResourceTemplate ()
{
UartSerialBus (0x0001C200, DataBitsEight, StopBitsOne,
0xFC, LittleEndian, ParityTypeNone, FlowControlNone,
0x0020, 0x0020, "\\_SB.URT1",
0x00, ResourceConsumer, ,
)
Interrupt (ResourceConsumer, Edge, ActiveHigh, ExclusiveAndWake, ,, )
{
0x00000046,
}
GpioIo (Exclusive, PullDefault, 0x0000, 0x0000, IoRestrictionOutputOnly,
"\\_SB.GPO2", 0x00, ResourceConsumer, ,
)
{ // Pin list
0x0009
}
GpioIo (Exclusive, PullDefault, 0x0000, 0x0000, IoRestrictionOutputOnly,
"\\_SB.GPO0", 0x00, ResourceConsumer, ,
)
{ // Pin list
0x0034
}
})
Return (UBUF) /* \_SB_.URT1.BTH0._CRS.UBUF */
}
}
}

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...

Last edited by ElfShotTheFood; 07-05-2016 at 11:08 PM.
 
Old 07-10-2016, 03:56 PM   #144
ElfShotTheFood
Member
 
Registered: Jul 2014
Location: New Jersey
Distribution: Slackware
Posts: 70

Original Poster
Rep: Reputation: 0
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.
 
Old 07-10-2016, 04:08 PM   #145
koroki
Member
 
Registered: Mar 2015
Location: Japan
Distribution: Arch Linux
Posts: 30

Rep: Reputation: Disabled
The problems with the stylus persist in Arch also. I suppose taht nobody check it.
 
Old 07-19-2016, 05:23 PM   #146
ElfShotTheFood
Member
 
Registered: Jul 2014
Location: New Jersey
Distribution: Slackware
Posts: 70

Original Poster
Rep: Reputation: 0
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.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: Rugged Bay Trail COM offers soldered RAM LXer Syndicated Linux News 0 03-24-2014 11:53 PM
LXer: Mini COM Express module runs Linux on the Bay Trail LXer Syndicated Linux News 0 03-18-2014 09:00 AM
LXer: Intel Bay Trail NUC Linux Performance Preview LXer Syndicated Linux News 0 02-13-2014 05:00 AM
LXer: Bay Trail-I Mini-ITX boards go big on expansion LXer Syndicated Linux News 0 02-01-2014 05:00 PM


All times are GMT -5. The time now is 02:00 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration