mythbuntu 12 - lirc device doesn't appear to even exist
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I'm trying to get a new installation of Mythbuntu working. So far, everything is OK except the remote. The sensor for the remote is on my Hauppauge WinTV HVR 1250.
First I tried to run irw
to see what was being picked up by the sensor:
$ irw
connect: No such file or directory
Then trying to run lircd gives:
$ lircd start$ lircd start
lircd: can't open or create /var/run/lirc/lircd.pid
I look for any lirc
devices and find there are none:
$ ls /dev/li*
ls: cannot access /dev/li*: No such file or directory
Just to be sure, I check in /proc/bus/input/devices
, which shows me two powerbuttons (not sure why), kbd and mouse dev, and the audio devs. Nothing for the IR receiver on the tuner card (which I thought was strange because shouldn't the tuner show up here?).
$ cat /proc/bus/input/devices
I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
U: Uniq=
H: Handlers=kbd event0
B: PROP=0
B: EV=3
B: KEY=10000000000000 0
I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
U: Uniq=
H: Handlers=kbd event1
B: PROP=0
B: EV=3
B: KEY=10000000000000 0
I: Bus=0003 Vendor=099a Product=7202 Version=0111
N: Name="Wireless Keyboard/Mouse"
P: Phys=usb-0000:00:10.1-2/input0
S: Sysfs=/devices/pci0000:00/0000:00:10.1/usb8/8-2/8-2:1.0/input/input2
U: Uniq=
H: Handlers=sysrq kbd event2
B: PROP=0
B: EV=120013
B: KEY=1000000000007 ff9f207ac14057ff febeffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=7
I: Bus=0003 Vendor=099a Product=7202 Version=0111
N: Name="Wireless Keyboard/Mouse"
P: Phys=usb-0000:00:10.1-2/input1
S: Sysfs=/devices/pci0000:00/0000:00:10.1/usb8/8-2/8-2:1.1/input/input3
U: Uniq=
H: Handlers=kbd mouse0 event3
B: PROP=0
B: EV=1f
B: KEY=4837fff072ff32d bf54444600000000 70001 20c100b17c000 267bfad9415fed 9e168000004400 10000002
B: REL=143
B: ABS=100000000
B: MSC=10
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HD-Audio Generic Line"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:14.2/sound/card0/input4
U: Uniq=
H: Handlers=event4
B: PROP=0
B: EV=21
B: SW=2000
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HD-Audio Generic Front Mic"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:14.2/sound/card0/input5
U: Uniq=
H: Handlers=event5
B: PROP=0
B: EV=21
B: SW=10
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HD-Audio Generic Rear Mic"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:14.2/sound/card0/input6
U: Uniq=
H: Handlers=event6
B: PROP=0
B: EV=21
B: SW=10
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HD-Audio Generic Front Headphone"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:14.2/sound/card0/input7
U: Uniq=
H: Handlers=event7
B: PROP=0
B: EV=21
B: SW=4
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HD-Audio Generic Line-Out"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:14.2/sound/card0/input8
U: Uniq=
H: Handlers=event8
B: PROP=0
B: EV=21
B: SW=40
According to dmesg
, the driver was registered, but it doesn't look like any devices was associated with the driver:
$ dmesg | grep irc
[ 10.631162] lirc_dev: IR Remote Control driver registered, major 249
So far, I've seen a number of forum pages suggesting that I use some trick to create a link between /dev/lirc
and some other device that is the REAL IR sensor, like /dev/event5
, but those cases assume that the real device is shown from /proc/bus/input/devices
, and I don't see any such device there.
Any suggestions on how to fix or further diagnose this?
FWIW, it seems like this question describes a similar problem, but has no solution yet:
Tracing IR to Hauppage remote on Mythbuntu 12.04
input-devices mythbuntu devices lirc
add a comment |
I'm trying to get a new installation of Mythbuntu working. So far, everything is OK except the remote. The sensor for the remote is on my Hauppauge WinTV HVR 1250.
First I tried to run irw
to see what was being picked up by the sensor:
$ irw
connect: No such file or directory
Then trying to run lircd gives:
$ lircd start$ lircd start
lircd: can't open or create /var/run/lirc/lircd.pid
I look for any lirc
devices and find there are none:
$ ls /dev/li*
ls: cannot access /dev/li*: No such file or directory
Just to be sure, I check in /proc/bus/input/devices
, which shows me two powerbuttons (not sure why), kbd and mouse dev, and the audio devs. Nothing for the IR receiver on the tuner card (which I thought was strange because shouldn't the tuner show up here?).
$ cat /proc/bus/input/devices
I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
U: Uniq=
H: Handlers=kbd event0
B: PROP=0
B: EV=3
B: KEY=10000000000000 0
I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
U: Uniq=
H: Handlers=kbd event1
B: PROP=0
B: EV=3
B: KEY=10000000000000 0
I: Bus=0003 Vendor=099a Product=7202 Version=0111
N: Name="Wireless Keyboard/Mouse"
P: Phys=usb-0000:00:10.1-2/input0
S: Sysfs=/devices/pci0000:00/0000:00:10.1/usb8/8-2/8-2:1.0/input/input2
U: Uniq=
H: Handlers=sysrq kbd event2
B: PROP=0
B: EV=120013
B: KEY=1000000000007 ff9f207ac14057ff febeffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=7
I: Bus=0003 Vendor=099a Product=7202 Version=0111
N: Name="Wireless Keyboard/Mouse"
P: Phys=usb-0000:00:10.1-2/input1
S: Sysfs=/devices/pci0000:00/0000:00:10.1/usb8/8-2/8-2:1.1/input/input3
U: Uniq=
H: Handlers=kbd mouse0 event3
B: PROP=0
B: EV=1f
B: KEY=4837fff072ff32d bf54444600000000 70001 20c100b17c000 267bfad9415fed 9e168000004400 10000002
B: REL=143
B: ABS=100000000
B: MSC=10
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HD-Audio Generic Line"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:14.2/sound/card0/input4
U: Uniq=
H: Handlers=event4
B: PROP=0
B: EV=21
B: SW=2000
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HD-Audio Generic Front Mic"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:14.2/sound/card0/input5
U: Uniq=
H: Handlers=event5
B: PROP=0
B: EV=21
B: SW=10
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HD-Audio Generic Rear Mic"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:14.2/sound/card0/input6
U: Uniq=
H: Handlers=event6
B: PROP=0
B: EV=21
B: SW=10
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HD-Audio Generic Front Headphone"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:14.2/sound/card0/input7
U: Uniq=
H: Handlers=event7
B: PROP=0
B: EV=21
B: SW=4
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HD-Audio Generic Line-Out"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:14.2/sound/card0/input8
U: Uniq=
H: Handlers=event8
B: PROP=0
B: EV=21
B: SW=40
According to dmesg
, the driver was registered, but it doesn't look like any devices was associated with the driver:
$ dmesg | grep irc
[ 10.631162] lirc_dev: IR Remote Control driver registered, major 249
So far, I've seen a number of forum pages suggesting that I use some trick to create a link between /dev/lirc
and some other device that is the REAL IR sensor, like /dev/event5
, but those cases assume that the real device is shown from /proc/bus/input/devices
, and I don't see any such device there.
Any suggestions on how to fix or further diagnose this?
FWIW, it seems like this question describes a similar problem, but has no solution yet:
Tracing IR to Hauppage remote on Mythbuntu 12.04
input-devices mythbuntu devices lirc
add a comment |
I'm trying to get a new installation of Mythbuntu working. So far, everything is OK except the remote. The sensor for the remote is on my Hauppauge WinTV HVR 1250.
First I tried to run irw
to see what was being picked up by the sensor:
$ irw
connect: No such file or directory
Then trying to run lircd gives:
$ lircd start$ lircd start
lircd: can't open or create /var/run/lirc/lircd.pid
I look for any lirc
devices and find there are none:
$ ls /dev/li*
ls: cannot access /dev/li*: No such file or directory
Just to be sure, I check in /proc/bus/input/devices
, which shows me two powerbuttons (not sure why), kbd and mouse dev, and the audio devs. Nothing for the IR receiver on the tuner card (which I thought was strange because shouldn't the tuner show up here?).
$ cat /proc/bus/input/devices
I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
U: Uniq=
H: Handlers=kbd event0
B: PROP=0
B: EV=3
B: KEY=10000000000000 0
I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
U: Uniq=
H: Handlers=kbd event1
B: PROP=0
B: EV=3
B: KEY=10000000000000 0
I: Bus=0003 Vendor=099a Product=7202 Version=0111
N: Name="Wireless Keyboard/Mouse"
P: Phys=usb-0000:00:10.1-2/input0
S: Sysfs=/devices/pci0000:00/0000:00:10.1/usb8/8-2/8-2:1.0/input/input2
U: Uniq=
H: Handlers=sysrq kbd event2
B: PROP=0
B: EV=120013
B: KEY=1000000000007 ff9f207ac14057ff febeffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=7
I: Bus=0003 Vendor=099a Product=7202 Version=0111
N: Name="Wireless Keyboard/Mouse"
P: Phys=usb-0000:00:10.1-2/input1
S: Sysfs=/devices/pci0000:00/0000:00:10.1/usb8/8-2/8-2:1.1/input/input3
U: Uniq=
H: Handlers=kbd mouse0 event3
B: PROP=0
B: EV=1f
B: KEY=4837fff072ff32d bf54444600000000 70001 20c100b17c000 267bfad9415fed 9e168000004400 10000002
B: REL=143
B: ABS=100000000
B: MSC=10
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HD-Audio Generic Line"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:14.2/sound/card0/input4
U: Uniq=
H: Handlers=event4
B: PROP=0
B: EV=21
B: SW=2000
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HD-Audio Generic Front Mic"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:14.2/sound/card0/input5
U: Uniq=
H: Handlers=event5
B: PROP=0
B: EV=21
B: SW=10
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HD-Audio Generic Rear Mic"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:14.2/sound/card0/input6
U: Uniq=
H: Handlers=event6
B: PROP=0
B: EV=21
B: SW=10
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HD-Audio Generic Front Headphone"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:14.2/sound/card0/input7
U: Uniq=
H: Handlers=event7
B: PROP=0
B: EV=21
B: SW=4
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HD-Audio Generic Line-Out"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:14.2/sound/card0/input8
U: Uniq=
H: Handlers=event8
B: PROP=0
B: EV=21
B: SW=40
According to dmesg
, the driver was registered, but it doesn't look like any devices was associated with the driver:
$ dmesg | grep irc
[ 10.631162] lirc_dev: IR Remote Control driver registered, major 249
So far, I've seen a number of forum pages suggesting that I use some trick to create a link between /dev/lirc
and some other device that is the REAL IR sensor, like /dev/event5
, but those cases assume that the real device is shown from /proc/bus/input/devices
, and I don't see any such device there.
Any suggestions on how to fix or further diagnose this?
FWIW, it seems like this question describes a similar problem, but has no solution yet:
Tracing IR to Hauppage remote on Mythbuntu 12.04
input-devices mythbuntu devices lirc
I'm trying to get a new installation of Mythbuntu working. So far, everything is OK except the remote. The sensor for the remote is on my Hauppauge WinTV HVR 1250.
First I tried to run irw
to see what was being picked up by the sensor:
$ irw
connect: No such file or directory
Then trying to run lircd gives:
$ lircd start$ lircd start
lircd: can't open or create /var/run/lirc/lircd.pid
I look for any lirc
devices and find there are none:
$ ls /dev/li*
ls: cannot access /dev/li*: No such file or directory
Just to be sure, I check in /proc/bus/input/devices
, which shows me two powerbuttons (not sure why), kbd and mouse dev, and the audio devs. Nothing for the IR receiver on the tuner card (which I thought was strange because shouldn't the tuner show up here?).
$ cat /proc/bus/input/devices
I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
U: Uniq=
H: Handlers=kbd event0
B: PROP=0
B: EV=3
B: KEY=10000000000000 0
I: Bus=0019 Vendor=0000 Product=0001 Version=0000
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
U: Uniq=
H: Handlers=kbd event1
B: PROP=0
B: EV=3
B: KEY=10000000000000 0
I: Bus=0003 Vendor=099a Product=7202 Version=0111
N: Name="Wireless Keyboard/Mouse"
P: Phys=usb-0000:00:10.1-2/input0
S: Sysfs=/devices/pci0000:00/0000:00:10.1/usb8/8-2/8-2:1.0/input/input2
U: Uniq=
H: Handlers=sysrq kbd event2
B: PROP=0
B: EV=120013
B: KEY=1000000000007 ff9f207ac14057ff febeffdfffefffff fffffffffffffffe
B: MSC=10
B: LED=7
I: Bus=0003 Vendor=099a Product=7202 Version=0111
N: Name="Wireless Keyboard/Mouse"
P: Phys=usb-0000:00:10.1-2/input1
S: Sysfs=/devices/pci0000:00/0000:00:10.1/usb8/8-2/8-2:1.1/input/input3
U: Uniq=
H: Handlers=kbd mouse0 event3
B: PROP=0
B: EV=1f
B: KEY=4837fff072ff32d bf54444600000000 70001 20c100b17c000 267bfad9415fed 9e168000004400 10000002
B: REL=143
B: ABS=100000000
B: MSC=10
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HD-Audio Generic Line"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:14.2/sound/card0/input4
U: Uniq=
H: Handlers=event4
B: PROP=0
B: EV=21
B: SW=2000
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HD-Audio Generic Front Mic"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:14.2/sound/card0/input5
U: Uniq=
H: Handlers=event5
B: PROP=0
B: EV=21
B: SW=10
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HD-Audio Generic Rear Mic"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:14.2/sound/card0/input6
U: Uniq=
H: Handlers=event6
B: PROP=0
B: EV=21
B: SW=10
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HD-Audio Generic Front Headphone"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:14.2/sound/card0/input7
U: Uniq=
H: Handlers=event7
B: PROP=0
B: EV=21
B: SW=4
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="HD-Audio Generic Line-Out"
P: Phys=ALSA
S: Sysfs=/devices/pci0000:00/0000:00:14.2/sound/card0/input8
U: Uniq=
H: Handlers=event8
B: PROP=0
B: EV=21
B: SW=40
According to dmesg
, the driver was registered, but it doesn't look like any devices was associated with the driver:
$ dmesg | grep irc
[ 10.631162] lirc_dev: IR Remote Control driver registered, major 249
So far, I've seen a number of forum pages suggesting that I use some trick to create a link between /dev/lirc
and some other device that is the REAL IR sensor, like /dev/event5
, but those cases assume that the real device is shown from /proc/bus/input/devices
, and I don't see any such device there.
Any suggestions on how to fix or further diagnose this?
FWIW, it seems like this question describes a similar problem, but has no solution yet:
Tracing IR to Hauppage remote on Mythbuntu 12.04
input-devices mythbuntu devices lirc
input-devices mythbuntu devices lirc
edited Apr 13 '17 at 12:24
Community♦
1
1
asked Sep 19 '12 at 2:40
FrustratedWithFormsDesignerFrustratedWithFormsDesigner
143210
143210
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
lirc isn't running because you are trying to start it as a regular user instead of root. That is why there are no lirc devices. irw needs to be run after lirc has been started, you will only get irw to show responses from the remote if lirc has been successfully started.
You need to start lirc as root, e.g.
sudo lircd start
Though I always use
sudo service lirc start
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f190392%2fmythbuntu-12-lirc-device-doesnt-appear-to-even-exist%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
lirc isn't running because you are trying to start it as a regular user instead of root. That is why there are no lirc devices. irw needs to be run after lirc has been started, you will only get irw to show responses from the remote if lirc has been successfully started.
You need to start lirc as root, e.g.
sudo lircd start
Though I always use
sudo service lirc start
add a comment |
lirc isn't running because you are trying to start it as a regular user instead of root. That is why there are no lirc devices. irw needs to be run after lirc has been started, you will only get irw to show responses from the remote if lirc has been successfully started.
You need to start lirc as root, e.g.
sudo lircd start
Though I always use
sudo service lirc start
add a comment |
lirc isn't running because you are trying to start it as a regular user instead of root. That is why there are no lirc devices. irw needs to be run after lirc has been started, you will only get irw to show responses from the remote if lirc has been successfully started.
You need to start lirc as root, e.g.
sudo lircd start
Though I always use
sudo service lirc start
lirc isn't running because you are trying to start it as a regular user instead of root. That is why there are no lirc devices. irw needs to be run after lirc has been started, you will only get irw to show responses from the remote if lirc has been successfully started.
You need to start lirc as root, e.g.
sudo lircd start
Though I always use
sudo service lirc start
edited Sep 13 '13 at 12:58
answered Sep 6 '13 at 9:27
MossyMossy
262
262
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f190392%2fmythbuntu-12-lirc-device-doesnt-appear-to-even-exist%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown