From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Raghav Gururajan <rvgn@disroot.org>
Cc: help-guix@gnu.org
Subject: Re: Input Attach Service
Date: Thu, 09 May 2019 20:12:47 +0200 [thread overview]
Message-ID: <87lfzfcx9c.fsf@nckx> (raw)
In-Reply-To: <20190509135540.819E130C59@disroot.org>
[-- Attachment #1: Type: text/plain, Size: 360 bytes --]
Raghav,
Raghav Gururajan wrote:
> I tried it. But didn't work. Now the error output line during
> boot " inputattach: invalid type "--w8001"".
Our inputattach says…
--wacom -wacom Wacom W8001
…so I guess it was just renamed since that wiki article was
written.
Then I'm all out of ideas, sorry.
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2019-05-09 18:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 13:55 Input Attach Service Raghav Gururajan
2019-05-09 18:12 ` Tobias Geerinckx-Rice [this message]
2019-05-10 4:03 ` Raghav Gururajan
-- strict thread matches above, loose matches on Subject: below --
2019-05-08 16:39 Raghav Gururajan
2019-05-08 17:08 ` Tobias Geerinckx-Rice
2019-05-09 6:23 ` Raghav Gururajan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lfzfcx9c.fsf@nckx \
--to=me@tobias.gr \
--cc=help-guix@gnu.org \
--cc=rvgn@disroot.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).