Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - NomNomNom

Pages: [1]
1
Hi.

Actually, I'm not on Peppermint right now. I'm trying to get this card to work on my netbook with MX-16 installed and someone pointed this thread out to me. I managed to install the driver following the instruction here and the appindicator-crystalhd but it still doesn't work and the indicator behaves the same way it did for the original poster.
This thread is marked as solved but I don't see the original poster saying their card was working in the end or how they got it to work. The discussion becomes about some apt problem that has nothing to do with crystalhd.
madentaiwn, if you still read this forum, is your card working and how did that happen ?
Did anyone get this card to work ?

2
Networking / Re: Bluetooth problemĀ : trying to adapt a debian solution
« on: December 21, 2016, 12:20:09 pm »
Hi, I started this topic but actually my problem had a much simpler solution than I thought. First off, I have Peppermint 6 installed so it's different from pchan's problem. Anyway, I followed the instructions given in the first answer here and it worked.

3
Ok. I thought, even thought these are different distros, the problem would have a similar origin. Thank you for the information.

Does running
Code: [Select]
sudo pactl load-module module-bluetooth-discoverthen trying to pair the headset work ?
I get this :
Code: [Select]
Failure: Module initialization failed

4
Networking / Bluetooth problemĀ : trying to adapt a debian solution
« on: April 04, 2016, 05:33:01 am »
Hi,

I'm having trouble getting my bluetooth headsets to work on Peppermint running on my netbook. I've had the exact same problem on debian on my laptop and managed to fix it using the Troubleshooting part of this tutorial :

Quote
Troubleshooting

Bluetooth headset is connected, but ALSA/PulseAudio fails to pick up the connected device or there's no device to pick. This happens because GDM captures A2DP sink on session start, as GDM needs pulseaudio in the gdm session for accessibility. For example, the screen reader requires it.

In order to prevent GDM from capturing the A2DP sink on session start, edit /var/lib/gdm3/.config/pulse/client.conf (or create it, if it doesn't exist):

Code: [Select]
autospawn = no
daemon-binary = /bin/true

After that you have to grant access to this file to Debian-gdm user:

Code: [Select]
# chown Debian-gdm:Debian-gdm /var/lib/gdm3/.config/pulse/client.conf
In order to auto-connect a2dp for some devices, add this to /etc/pulse/default.pa:

Code: [Select]
load-module module-switch-on-connect
Reboot.

Now the sound device (bluetooth headset) should be accessible through pavucontrol and standard audio device manager.

I found out that the /var/lib/gdm3/.config/pulse/client.conf file was actually located in /etc/pulse/client.conf in Peppermint but I'm stuck at the second part. The Debian-gdm user doesn't seem to exist or it's name is different in Peppermint. :-\

Pages: [1]