Converted post on bluetooth keyboard to HTML
This commit is contained in:
Claudio Maggioni
parent
1002fb23a6
commit
79f78a4a7d
13 changed files with 119 additions and 66 deletions
Binary file not shown.
|
|
@ -8,6 +8,7 @@
|
|||
|
||||
<link rel="stylesheet" href="{{ "/css/main.css" | prepend: site.baseurl }}">
|
||||
<link href='https://fonts.googleapis.com/css?family=Hammersmith+One' rel='stylesheet' type='text/css'>
|
||||
<link href="https://fonts.googleapis.com/css?family=Source+Code+Pro" rel="stylesheet">
|
||||
<link rel="canonical" href="{{ page.url | replace:'index.html','' | prepend: site.baseurl | prepend: site.url }}">
|
||||
<link rel="alternate" type="application/rss+xml" title="{{ site.title }}" href="{{ "/feed.xml" | prepend: site.baseurl | prepend: site.url }}">
|
||||
<link rel="stylesheet" href="//maxcdn.bootstrapcdn.com/font-awesome/4.3.0/css/font-awesome.min.css">
|
||||
|
|
|
|||
|
|
@ -0,0 +1,64 @@
|
|||
---
|
||||
layout: post
|
||||
title: "Get a Bluetooth keyboard work with Arch Linux"
|
||||
date: 2016-07-07 14:49:18 +0200
|
||||
categories: linux
|
||||
---
|
||||
<p>
|
||||
I've recently got a Rapoo E6100. This is a minimal and space saving Bluetooth 3.0 keyboard. If you pair it with Windows 10, it will remain paired after reboot, giving the possibility to use it since the login screen. After installing the Bluetooth stack on my Arch via the <code>bluez</code> and <code>bluez-utils</code> packages I thought the pairing process would be as simple as Windows if I used the KDE GUI menus for Bluetooth management. That's not true. The keyboard, once paired, will reconnect automatically just after <code>plasmashell</code> loaded, leaving me without keyboard during the SDDM login screen and, of course, during a non-graphical session.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
As usual, i've searched help in the ArchWiki, founding <a href="https://wiki.archlinux.org/index.php/Bluetooth_keyboard">this</a> article. With that, i've succesfully reconnected my Bluetooth keyboard using the <code>bluetoothctl</code> utility. The next step was configuring the service for auto connection during boot. I've created the <code>btkbd.conf</code> and the <code>btkbd.service</code> files, enabling the last one with systemd. Let's give a look to the service file:
|
||||
</p>
|
||||
|
||||
<p>
|
||||
{% highlight bash linenos %}
|
||||
[Unit]
|
||||
Description=systemd Unit to automatically start a Bluetooth keyboard
|
||||
Documentation=https://wiki.archlinux.org/index.php/Bluetooth_Keyboard
|
||||
Requires=dbus-org.bluez.service
|
||||
After=dbus-org.bluez.service
|
||||
ConditionPathExists=/etc/btkbd.conf
|
||||
ConditionPathExists=/usr/bin/hcitool
|
||||
ConditionPathExists=/usr/bin/hciconfig
|
||||
|
||||
[Service]
|
||||
Type=oneshot
|
||||
EnvironmentFile=/etc/btkbd.conf
|
||||
ExecStart=/usr/bin/hciconfig ${HCIDEVICE} up
|
||||
# ignore errors on connect, spurious problems with bt?
|
||||
# so start next command with -
|
||||
ExecStart=-/usr/bin/hcitool cc ${BTKBDMAC}
|
||||
|
||||
[Install]
|
||||
WantedBy=multi-user.target
|
||||
{% endhighlight %}
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Line 13 enables the Bluetooth dongle, and line 16 connects it to the keyboard we gave the mac address in <code>/etc/btkbd.conf</code>. This should work flawlessly, right? Of course it doesn't. The service starts before the <code>dbus-org.bluez.service</code> is loaded and fails. However, if the service is started manually after login the Bluetooth keyboard works. After hours of trying figuring out what was wrong I've almost asked for a return on Amazon! The last attempt I made was with sddm disabled and involved built from scratch service:
|
||||
</p>
|
||||
|
||||
<p>
|
||||
{% highlight bash linenos %}
|
||||
[Unit]
|
||||
Description=systemd Unit to automatically start a Bluetooth keyboard
|
||||
|
||||
[Service]
|
||||
Type=oneshot
|
||||
ExecStart=/bin/hciconfig hci0 up
|
||||
ExecStart=/bin/hcitool cc 00:11:22:33:44:55
|
||||
|
||||
[Install]
|
||||
WantedBy=bluetooth.target
|
||||
{% endhighlight %}
|
||||
</p>
|
||||
|
||||
<p>
|
||||
This incredibly worked. I think the problem was that <code>multi-user.target</code> that needs to be reached earlier than <code>bluetooth.target</code>. I got rid of all the tidiness of the ArchWiki solution just to be sure that was not the problem, but I think you can use all of that just correcting <code>WantedBy=</code>. Currently I haven't an ArchWiki account nor a forum one, but as soon as I'll register I'll correct the article.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Last thing: I discovered that my Bluetooth dongle is CSR 8510 A10 based so expect some ramblings about <a href="http://www.0xf8.org/2014/02/the-crux-of-finding-a-hid-proxy-capable-usb-bluetooth-adapter/">hid proxy</a>.
|
||||
</p>
|
||||
|
|
@ -1,51 +0,0 @@
|
|||
---
|
||||
layout: post
|
||||
title: "Get a Bluetooth keyboard work with Arch Linux"
|
||||
date: 2016-07-07 14:49:18 +0200
|
||||
categories: linux
|
||||
---
|
||||
I've recently got a Rapoo E6100. This is a minimal and space saving Bluetooth 3.0 keyboard. If you pair it with Windows 10, it will remain paired after reboot, giving the possibility to use it since the login screen. After installing the Bluetooth stack on my Arch via the `bluez` and `bluez-utils` packages I thought the pairing process would be as simple as Windows if I used the KDE GUI menus for Bluetooth management. That's not true. The keyboard, once paired, will reconnect automatically just after `plasmashell` loaded, leaving me without keyboard during the SDDM login screen and, of course, during a non-graphical session.
|
||||
|
||||
As usual, i've searched help in the ArchWiki, founding [this](https://wiki.archlinux.org/index.php/Bluetooth_keyboard) article. With that, i've succesfully reconnected my Bluetooth keyboard using the `bluetoothctl` utility. The next step was configuring the service for auto connection during boot. I've created the `btkbd.conf` and the `btkbd.service` files, enabling the last one with systemd. Let's give a look to the service file:
|
||||
|
||||
{% highlight bash linenos %}
|
||||
[Unit]
|
||||
Description=systemd Unit to automatically start a Bluetooth keyboard
|
||||
Documentation=https://wiki.archlinux.org/index.php/Bluetooth_Keyboard
|
||||
Requires=dbus-org.bluez.service
|
||||
After=dbus-org.bluez.service
|
||||
ConditionPathExists=/etc/btkbd.conf
|
||||
ConditionPathExists=/usr/bin/hcitool
|
||||
ConditionPathExists=/usr/bin/hciconfig
|
||||
|
||||
[Service]
|
||||
Type=oneshot
|
||||
EnvironmentFile=/etc/btkbd.conf
|
||||
ExecStart=/usr/bin/hciconfig ${HCIDEVICE} up
|
||||
# ignore errors on connect, spurious problems with bt?
|
||||
# so start next command with -
|
||||
ExecStart=-/usr/bin/hcitool cc ${BTKBDMAC}
|
||||
|
||||
[Install]
|
||||
WantedBy=multi-user.target
|
||||
{% endhighlight %}
|
||||
|
||||
Line 13 enables the Bluetooth dongle, and line 16 connects it to the keyboard we gave the mac address in `/etc/btkbd.conf`. This should work flawlessly, right? Of course it doesn't. The service starts before the `dbus-org.bluez.service` is loaded and fails. However, if the service is started manually after login the Bluetooth keyboard works. After hours of trying figuring out what was wrong I've almost asked for a return on Amazon! The last attempt I made was with sddm disabled and involved built from scratch service:
|
||||
|
||||
{% highlight bash linenos %}
|
||||
[Unit]
|
||||
Description=systemd Unit to automatically start a Bluetooth keyboard
|
||||
|
||||
[Service]
|
||||
Type=oneshot
|
||||
ExecStart=/bin/hciconfig hci0 up
|
||||
ExecStart=/bin/hcitool cc 00:11:22:33:44:55
|
||||
|
||||
[Install]
|
||||
WantedBy=bluetooth.target
|
||||
{% endhighlight %}
|
||||
|
||||
This incredibly worked. I think the problem was that `multi-user.target` that needs to be reached earlier than `bluetooth.target`. I got rid of all the tidiness of the ArchWiki solution just to be sure that was not the problem, but I think you can use all of that just correcting `WantedBy=`. Currently I haven't an ArchWiki account nor a forum one, but as soon as I'll register I'll correct the article.
|
||||
|
||||
Let me know in the comments if this solution is well made or if it's just a bodge.
|
||||
Last thing: I discovered that my Bluetooth dongle is CSR 8510 A10 based so expect some ramblings about [hid proxy](http://www.0xf8.org/2014/02/the-crux-of-finding-a-hid-proxy-capable-usb-bluetooth-adapter/).
|
||||
|
|
@ -140,6 +140,10 @@ p:first-child {
|
|||
* Syntax highlighting
|
||||
*/
|
||||
|
||||
pre, code {
|
||||
font-family: "Source Code Pro", monospace;
|
||||
}
|
||||
|
||||
/* Disable borders between line numbers and code when
|
||||
* line numbers are shown */
|
||||
code .rouge-table, code .rouge-table td {
|
||||
|
|
|
|||
|
|
@ -11,6 +11,7 @@
|
|||
|
||||
<link rel="stylesheet" href="/css/main.css">
|
||||
<link href='https://fonts.googleapis.com/css?family=Hammersmith+One' rel='stylesheet' type='text/css'>
|
||||
<link href="https://fonts.googleapis.com/css?family=Source+Code+Pro" rel="stylesheet">
|
||||
<link rel="canonical" href="http://localhost:4000/404.html">
|
||||
<link rel="alternate" type="application/rss+xml" title="maggioni.xyz" href="http://localhost:4000/feed.xml">
|
||||
<link rel="stylesheet" href="//maxcdn.bootstrapcdn.com/font-awesome/4.3.0/css/font-awesome.min.css">
|
||||
|
|
|
|||
|
|
@ -11,6 +11,7 @@
|
|||
|
||||
<link rel="stylesheet" href="/css/main.css">
|
||||
<link href='https://fonts.googleapis.com/css?family=Hammersmith+One' rel='stylesheet' type='text/css'>
|
||||
<link href="https://fonts.googleapis.com/css?family=Source+Code+Pro" rel="stylesheet">
|
||||
<link rel="canonical" href="http://localhost:4000/blog/">
|
||||
<link rel="alternate" type="application/rss+xml" title="maggioni.xyz" href="http://localhost:4000/feed.xml">
|
||||
<link rel="stylesheet" href="//maxcdn.bootstrapcdn.com/font-awesome/4.3.0/css/font-awesome.min.css">
|
||||
|
|
|
|||
|
|
@ -123,6 +123,9 @@ p:first-child {
|
|||
/**
|
||||
* Syntax highlighting
|
||||
*/
|
||||
pre, code {
|
||||
font-family: "Source Code Pro", monospace; }
|
||||
|
||||
/* Disable borders between line numbers and code when
|
||||
* line numbers are shown */
|
||||
code .rouge-table, code .rouge-table td {
|
||||
|
|
|
|||
|
|
@ -6,8 +6,8 @@
|
|||
</description>
|
||||
<link>http://localhost:4000/</link>
|
||||
<atom:link href="http://localhost:4000/feed.xml" rel="self" type="application/rss+xml"/>
|
||||
<pubDate>Tue, 23 Oct 2018 16:47:06 +0200</pubDate>
|
||||
<lastBuildDate>Tue, 23 Oct 2018 16:47:06 +0200</lastBuildDate>
|
||||
<pubDate>Tue, 23 Oct 2018 17:00:52 +0200</pubDate>
|
||||
<lastBuildDate>Tue, 23 Oct 2018 17:00:52 +0200</lastBuildDate>
|
||||
<generator>Jekyll v3.8.4</generator>
|
||||
|
||||
<item>
|
||||
|
|
@ -132,10 +132,15 @@ done</span>
|
|||
|
||||
<item>
|
||||
<title>Get a Bluetooth keyboard work with Arch Linux</title>
|
||||
<description><p>I’ve recently got a Rapoo E6100. This is a minimal and space saving Bluetooth 3.0 keyboard. If you pair it with Windows 10, it will remain paired after reboot, giving the possibility to use it since the login screen. After installing the Bluetooth stack on my Arch via the <code class="highlighter-rouge">bluez</code> and <code class="highlighter-rouge">bluez-utils</code> packages I thought the pairing process would be as simple as Windows if I used the KDE GUI menus for Bluetooth management. That’s not true. The keyboard, once paired, will reconnect automatically just after <code class="highlighter-rouge">plasmashell</code> loaded, leaving me without keyboard during the SDDM login screen and, of course, during a non-graphical session.</p>
|
||||
<description><p>
|
||||
I've recently got a Rapoo E6100. This is a minimal and space saving Bluetooth 3.0 keyboard. If you pair it with Windows 10, it will remain paired after reboot, giving the possibility to use it since the login screen. After installing the Bluetooth stack on my Arch via the <code>bluez</code> and <code>bluez-utils</code> packages I thought the pairing process would be as simple as Windows if I used the KDE GUI menus for Bluetooth management. That's not true. The keyboard, once paired, will reconnect automatically just after <code>plasmashell</code> loaded, leaving me without keyboard during the SDDM login screen and, of course, during a non-graphical session.
|
||||
</p>
|
||||
|
||||
<p>As usual, i’ve searched help in the ArchWiki, founding <a href="https://wiki.archlinux.org/index.php/Bluetooth_keyboard">this</a> article. With that, i’ve succesfully reconnected my Bluetooth keyboard using the <code class="highlighter-rouge">bluetoothctl</code> utility. The next step was configuring the service for auto connection during boot. I’ve created the <code class="highlighter-rouge">btkbd.conf</code> and the <code class="highlighter-rouge">btkbd.service</code> files, enabling the last one with systemd. Let’s give a look to the service file:</p>
|
||||
<p>
|
||||
As usual, i've searched help in the ArchWiki, founding <a href="https://wiki.archlinux.org/index.php/Bluetooth_keyboard">this</a> article. With that, i've succesfully reconnected my Bluetooth keyboard using the <code>bluetoothctl</code> utility. The next step was configuring the service for auto connection during boot. I've created the <code>btkbd.conf</code> and the <code>btkbd.service</code> files, enabling the last one with systemd. Let's give a look to the service file:
|
||||
</p>
|
||||
|
||||
<p>
|
||||
<figure class="highlight"><pre><code class="language-bash" data-lang="bash"><table class="rouge-table"><tbody><tr><td class="gutter gl"><pre class="lineno">1
|
||||
2
|
||||
3
|
||||
|
|
@ -174,9 +179,13 @@ done</span>
|
|||
|
||||
<span class="o">[</span>Install]
|
||||
<span class="nv">WantedBy</span><span class="o">=</span>multi-user.target</pre></td></tr></tbody></table></code></pre></figure>
|
||||
</p>
|
||||
|
||||
<p>Line 13 enables the Bluetooth dongle, and line 16 connects it to the keyboard we gave the mac address in <code class="highlighter-rouge">/etc/btkbd.conf</code>. This should work flawlessly, right? Of course it doesn’t. The service starts before the <code class="highlighter-rouge">dbus-org.bluez.service</code> is loaded and fails. However, if the service is started manually after login the Bluetooth keyboard works. After hours of trying figuring out what was wrong I’ve almost asked for a return on Amazon! The last attempt I made was with sddm disabled and involved built from scratch service:</p>
|
||||
<p>
|
||||
Line 13 enables the Bluetooth dongle, and line 16 connects it to the keyboard we gave the mac address in <code>/etc/btkbd.conf</code>. This should work flawlessly, right? Of course it doesn't. The service starts before the <code>dbus-org.bluez.service</code> is loaded and fails. However, if the service is started manually after login the Bluetooth keyboard works. After hours of trying figuring out what was wrong I've almost asked for a return on Amazon! The last attempt I made was with sddm disabled and involved built from scratch service:
|
||||
</p>
|
||||
|
||||
<p>
|
||||
<figure class="highlight"><pre><code class="language-bash" data-lang="bash"><table class="rouge-table"><tbody><tr><td class="gutter gl"><pre class="lineno">1
|
||||
2
|
||||
3
|
||||
|
|
@ -197,11 +206,15 @@ done</span>
|
|||
|
||||
<span class="o">[</span>Install]
|
||||
<span class="nv">WantedBy</span><span class="o">=</span>bluetooth.target</pre></td></tr></tbody></table></code></pre></figure>
|
||||
</p>
|
||||
|
||||
<p>This incredibly worked. I think the problem was that <code class="highlighter-rouge">multi-user.target</code> that needs to be reached earlier than <code class="highlighter-rouge">bluetooth.target</code>. I got rid of all the tidiness of the ArchWiki solution just to be sure that was not the problem, but I think you can use all of that just correcting <code class="highlighter-rouge">WantedBy=</code>. Currently I haven’t an ArchWiki account nor a forum one, but as soon as I’ll register I’ll correct the article.</p>
|
||||
<p>
|
||||
This incredibly worked. I think the problem was that <code>multi-user.target</code> that needs to be reached earlier than <code>bluetooth.target</code>. I got rid of all the tidiness of the ArchWiki solution just to be sure that was not the problem, but I think you can use all of that just correcting <code>WantedBy=</code>. Currently I haven't an ArchWiki account nor a forum one, but as soon as I'll register I'll correct the article.
|
||||
</p>
|
||||
|
||||
<p>Let me know in the comments if this solution is well made or if it’s just a bodge.
|
||||
Last thing: I discovered that my Bluetooth dongle is CSR 8510 A10 based so expect some ramblings about <a href="http://www.0xf8.org/2014/02/the-crux-of-finding-a-hid-proxy-capable-usb-bluetooth-adapter/">hid proxy</a>.</p>
|
||||
<p>
|
||||
Last thing: I discovered that my Bluetooth dongle is CSR 8510 A10 based so expect some ramblings about <a href="http://www.0xf8.org/2014/02/the-crux-of-finding-a-hid-proxy-capable-usb-bluetooth-adapter/">hid proxy</a>.
|
||||
</p>
|
||||
</description>
|
||||
<pubDate>Thu, 07 Jul 2016 14:49:18 +0200</pubDate>
|
||||
<link>http://localhost:4000/linux/2016/07/07/get-a-bluetooth-keyboard-work-with-arch.html</link>
|
||||
|
|
|
|||
|
|
@ -11,6 +11,7 @@
|
|||
|
||||
<link rel="stylesheet" href="/css/main.css">
|
||||
<link href='https://fonts.googleapis.com/css?family=Hammersmith+One' rel='stylesheet' type='text/css'>
|
||||
<link href="https://fonts.googleapis.com/css?family=Source+Code+Pro" rel="stylesheet">
|
||||
<link rel="canonical" href="http://localhost:4000/">
|
||||
<link rel="alternate" type="application/rss+xml" title="maggioni.xyz" href="http://localhost:4000/feed.xml">
|
||||
<link rel="stylesheet" href="//maxcdn.bootstrapcdn.com/font-awesome/4.3.0/css/font-awesome.min.css">
|
||||
|
|
|
|||
|
|
@ -6,10 +6,11 @@
|
|||
<meta name="viewport" content="width=device-width, initial-scale=1">
|
||||
|
||||
<title>Get a Bluetooth keyboard work with Arch Linux</title>
|
||||
<meta name="description" content="I’ve recently got a Rapoo E6100. This is a minimal and space saving Bluetooth 3.0 keyboard. If you pair it with Windows 10, it will remain paired after reboo...">
|
||||
<meta name="description" content="I've recently got a Rapoo E6100. This is a minimal and space saving Bluetooth 3.0 keyboard. If you pair it with Windows 10, it will remain paired after reboo...">
|
||||
|
||||
<link rel="stylesheet" href="/css/main.css">
|
||||
<link href='https://fonts.googleapis.com/css?family=Hammersmith+One' rel='stylesheet' type='text/css'>
|
||||
<link href="https://fonts.googleapis.com/css?family=Source+Code+Pro" rel="stylesheet">
|
||||
<link rel="canonical" href="http://localhost:4000/linux/2016/07/07/get-a-bluetooth-keyboard-work-with-arch.html">
|
||||
<link rel="alternate" type="application/rss+xml" title="maggioni.xyz" href="http://localhost:4000/feed.xml">
|
||||
<link rel="stylesheet" href="//maxcdn.bootstrapcdn.com/font-awesome/4.3.0/css/font-awesome.min.css">
|
||||
|
|
@ -96,10 +97,15 @@
|
|||
</header>
|
||||
|
||||
<div class="post-content" itemprop="articleBody">
|
||||
<p>I’ve recently got a Rapoo E6100. This is a minimal and space saving Bluetooth 3.0 keyboard. If you pair it with Windows 10, it will remain paired after reboot, giving the possibility to use it since the login screen. After installing the Bluetooth stack on my Arch via the <code class="highlighter-rouge">bluez</code> and <code class="highlighter-rouge">bluez-utils</code> packages I thought the pairing process would be as simple as Windows if I used the KDE GUI menus for Bluetooth management. That’s not true. The keyboard, once paired, will reconnect automatically just after <code class="highlighter-rouge">plasmashell</code> loaded, leaving me without keyboard during the SDDM login screen and, of course, during a non-graphical session.</p>
|
||||
<p>
|
||||
I've recently got a Rapoo E6100. This is a minimal and space saving Bluetooth 3.0 keyboard. If you pair it with Windows 10, it will remain paired after reboot, giving the possibility to use it since the login screen. After installing the Bluetooth stack on my Arch via the <code>bluez</code> and <code>bluez-utils</code> packages I thought the pairing process would be as simple as Windows if I used the KDE GUI menus for Bluetooth management. That's not true. The keyboard, once paired, will reconnect automatically just after <code>plasmashell</code> loaded, leaving me without keyboard during the SDDM login screen and, of course, during a non-graphical session.
|
||||
</p>
|
||||
|
||||
<p>As usual, i’ve searched help in the ArchWiki, founding <a href="https://wiki.archlinux.org/index.php/Bluetooth_keyboard">this</a> article. With that, i’ve succesfully reconnected my Bluetooth keyboard using the <code class="highlighter-rouge">bluetoothctl</code> utility. The next step was configuring the service for auto connection during boot. I’ve created the <code class="highlighter-rouge">btkbd.conf</code> and the <code class="highlighter-rouge">btkbd.service</code> files, enabling the last one with systemd. Let’s give a look to the service file:</p>
|
||||
<p>
|
||||
As usual, i've searched help in the ArchWiki, founding <a href="https://wiki.archlinux.org/index.php/Bluetooth_keyboard">this</a> article. With that, i've succesfully reconnected my Bluetooth keyboard using the <code>bluetoothctl</code> utility. The next step was configuring the service for auto connection during boot. I've created the <code>btkbd.conf</code> and the <code>btkbd.service</code> files, enabling the last one with systemd. Let's give a look to the service file:
|
||||
</p>
|
||||
|
||||
<p>
|
||||
<figure class="highlight"><pre><code class="language-bash" data-lang="bash"><table class="rouge-table"><tbody><tr><td class="gutter gl"><pre class="lineno">1
|
||||
2
|
||||
3
|
||||
|
|
@ -138,9 +144,13 @@
|
|||
|
||||
<span class="o">[</span>Install]
|
||||
<span class="nv">WantedBy</span><span class="o">=</span>multi-user.target</pre></td></tr></tbody></table></code></pre></figure>
|
||||
</p>
|
||||
|
||||
<p>Line 13 enables the Bluetooth dongle, and line 16 connects it to the keyboard we gave the mac address in <code class="highlighter-rouge">/etc/btkbd.conf</code>. This should work flawlessly, right? Of course it doesn’t. The service starts before the <code class="highlighter-rouge">dbus-org.bluez.service</code> is loaded and fails. However, if the service is started manually after login the Bluetooth keyboard works. After hours of trying figuring out what was wrong I’ve almost asked for a return on Amazon! The last attempt I made was with sddm disabled and involved built from scratch service:</p>
|
||||
<p>
|
||||
Line 13 enables the Bluetooth dongle, and line 16 connects it to the keyboard we gave the mac address in <code>/etc/btkbd.conf</code>. This should work flawlessly, right? Of course it doesn't. The service starts before the <code>dbus-org.bluez.service</code> is loaded and fails. However, if the service is started manually after login the Bluetooth keyboard works. After hours of trying figuring out what was wrong I've almost asked for a return on Amazon! The last attempt I made was with sddm disabled and involved built from scratch service:
|
||||
</p>
|
||||
|
||||
<p>
|
||||
<figure class="highlight"><pre><code class="language-bash" data-lang="bash"><table class="rouge-table"><tbody><tr><td class="gutter gl"><pre class="lineno">1
|
||||
2
|
||||
3
|
||||
|
|
@ -161,11 +171,15 @@
|
|||
|
||||
<span class="o">[</span>Install]
|
||||
<span class="nv">WantedBy</span><span class="o">=</span>bluetooth.target</pre></td></tr></tbody></table></code></pre></figure>
|
||||
</p>
|
||||
|
||||
<p>This incredibly worked. I think the problem was that <code class="highlighter-rouge">multi-user.target</code> that needs to be reached earlier than <code class="highlighter-rouge">bluetooth.target</code>. I got rid of all the tidiness of the ArchWiki solution just to be sure that was not the problem, but I think you can use all of that just correcting <code class="highlighter-rouge">WantedBy=</code>. Currently I haven’t an ArchWiki account nor a forum one, but as soon as I’ll register I’ll correct the article.</p>
|
||||
<p>
|
||||
This incredibly worked. I think the problem was that <code>multi-user.target</code> that needs to be reached earlier than <code>bluetooth.target</code>. I got rid of all the tidiness of the ArchWiki solution just to be sure that was not the problem, but I think you can use all of that just correcting <code>WantedBy=</code>. Currently I haven't an ArchWiki account nor a forum one, but as soon as I'll register I'll correct the article.
|
||||
</p>
|
||||
|
||||
<p>Let me know in the comments if this solution is well made or if it’s just a bodge.
|
||||
Last thing: I discovered that my Bluetooth dongle is CSR 8510 A10 based so expect some ramblings about <a href="http://www.0xf8.org/2014/02/the-crux-of-finding-a-hid-proxy-capable-usb-bluetooth-adapter/">hid proxy</a>.</p>
|
||||
<p>
|
||||
Last thing: I discovered that my Bluetooth dongle is CSR 8510 A10 based so expect some ramblings about <a href="http://www.0xf8.org/2014/02/the-crux-of-finding-a-hid-proxy-capable-usb-bluetooth-adapter/">hid proxy</a>.
|
||||
</p>
|
||||
|
||||
</div>
|
||||
|
||||
|
|
|
|||
|
|
@ -10,6 +10,7 @@
|
|||
|
||||
<link rel="stylesheet" href="/css/main.css">
|
||||
<link href='https://fonts.googleapis.com/css?family=Hammersmith+One' rel='stylesheet' type='text/css'>
|
||||
<link href="https://fonts.googleapis.com/css?family=Source+Code+Pro" rel="stylesheet">
|
||||
<link rel="canonical" href="http://localhost:4000/linux/2016/07/12/installing-gentoo-on-a-thinkpad-x60s.html">
|
||||
<link rel="alternate" type="application/rss+xml" title="maggioni.xyz" href="http://localhost:4000/feed.xml">
|
||||
<link rel="stylesheet" href="//maxcdn.bootstrapcdn.com/font-awesome/4.3.0/css/font-awesome.min.css">
|
||||
|
|
|
|||
|
|
@ -10,6 +10,7 @@
|
|||
|
||||
<link rel="stylesheet" href="/css/main.css">
|
||||
<link href='https://fonts.googleapis.com/css?family=Hammersmith+One' rel='stylesheet' type='text/css'>
|
||||
<link href="https://fonts.googleapis.com/css?family=Source+Code+Pro" rel="stylesheet">
|
||||
<link rel="canonical" href="http://localhost:4000/linux/2016/07/28/how-to-rickroll-people-launching-rm-rf-on-your-system.html">
|
||||
<link rel="alternate" type="application/rss+xml" title="maggioni.xyz" href="http://localhost:4000/feed.xml">
|
||||
<link rel="stylesheet" href="//maxcdn.bootstrapcdn.com/font-awesome/4.3.0/css/font-awesome.min.css">
|
||||
|
|
|
|||
Loading…
Reference in a new issue