Arch Linux keeps printing out weird characters in tty [duplicate]

up vote
1
down vote

favorite

This question already has an answer here:

^@ spam in tty (but seems to be system-wide)

1 answer

I cannot login to my Arch Linux machine because the tty keeps getting filled with ^@ characters, and therefore I cannot enter my username or password. What's wrong?

edited Oct 11 '17 at 13:32

Renan

14.2k65274

asked Oct 10 '17 at 7:35

Sebastian Karlsson

marked as duplicate by Wieland, Stephen Rauch, Hauke Laging, roaima, Jeff Schaller Dec 17 '17 at 22:24

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

migrated from stackoverflow.com Oct 11 '17 at 11:42

This question came from our site for professional and enthusiast programmers.

add a commentÂ |Â

up vote
1
down vote

favorite

This question already has an answer here:

^@ spam in tty (but seems to be system-wide)

1 answer

I cannot login to my Arch Linux machine because the tty keeps getting filled with ^@ characters, and therefore I cannot enter my username or password. What's wrong?

edited Oct 11 '17 at 13:32

Renan

14.2k65274

asked Oct 10 '17 at 7:35

Sebastian Karlsson

marked as duplicate by Wieland, Stephen Rauch, Hauke Laging, roaima, Jeff Schaller Dec 17 '17 at 22:24

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

migrated from stackoverflow.com Oct 11 '17 at 11:42

This question came from our site for professional and enthusiast programmers.

add a commentÂ |Â

up vote
1
down vote

favorite

This question already has an answer here:

^@ spam in tty (but seems to be system-wide)

1 answer

I cannot login to my Arch Linux machine because the tty keeps getting filled with ^@ characters, and therefore I cannot enter my username or password. What's wrong?

edited Oct 11 '17 at 13:32

Renan

14.2k65274

asked Oct 10 '17 at 7:35

Sebastian Karlsson

This question already has an answer here:

^@ spam in tty (but seems to be system-wide)

1 answer

I cannot login to my Arch Linux machine because the tty keeps getting filled with ^@ characters, and therefore I cannot enter my username or password. What's wrong?

This question already has an answer here:

^@ spam in tty (but seems to be system-wide)

1 answer

arch-linux tty

edited Oct 11 '17 at 13:32

Renan

14.2k65274

asked Oct 10 '17 at 7:35

Sebastian Karlsson

edited Oct 11 '17 at 13:32

Renan

14.2k65274

asked Oct 10 '17 at 7:35

Sebastian Karlsson

edited Oct 11 '17 at 13:32

Renan

14.2k65274

edited Oct 11 '17 at 13:32

Renan

14.2k65274

edited Oct 11 '17 at 13:32

Renan

14.2k65274

asked Oct 10 '17 at 7:35

Sebastian Karlsson

asked Oct 10 '17 at 7:35

Sebastian Karlsson

asked Oct 10 '17 at 7:35

Sebastian Karlsson

marked as duplicate by Wieland, Stephen Rauch, Hauke Laging, roaima, Jeff Schaller Dec 17 '17 at 22:24

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

migrated from stackoverflow.com Oct 11 '17 at 11:42

This question came from our site for professional and enthusiast programmers.

marked as duplicate by Wieland, Stephen Rauch, Hauke Laging, roaima, Jeff Schaller Dec 17 '17 at 22:24

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

migrated from stackoverflow.com Oct 11 '17 at 11:42

This question came from our site for professional and enthusiast programmers.

add a commentÂ |Â

3 Answers
3

active

oldest

votes

up vote
2
down vote

Can you ssh into your machine? If you can, try entering

sudo dmesg -n 1

That will block messages from the kernel. Might not help but worth a try

answered Oct 11 '17 at 7:42

user255114

add a commentÂ |Â

up vote
1
down vote

Some protocols use the NUL for keep alives. You could try to set a high keep alive to circumvent this behaviour. E.g. in iTerm2 there is an option called "When idle, sent Ascii code".

0 (null, NUL, , ^@), originally intended to be an ignored character, but now used by many programming languages to mark the end of a string.

answered Oct 11 '17 at 11:07

Gustav

add a commentÂ |Â

up vote
0
down vote

Solved it by running:

rmmod peaq_wmi
rmmod input_polldev

answered Dec 17 '17 at 19:32

Sebastian

add a commentÂ |Â

3 Answers
3

active

oldest

votes

3 Answers
3

active

oldest

votes

up vote
2
down vote

Can you ssh into your machine? If you can, try entering

sudo dmesg -n 1

That will block messages from the kernel. Might not help but worth a try

answered Oct 11 '17 at 7:42

user255114

add a commentÂ |Â

up vote
2
down vote

Can you ssh into your machine? If you can, try entering

sudo dmesg -n 1

That will block messages from the kernel. Might not help but worth a try

answered Oct 11 '17 at 7:42

user255114

add a commentÂ |Â

up vote
2
down vote

Can you ssh into your machine? If you can, try entering

sudo dmesg -n 1

That will block messages from the kernel. Might not help but worth a try

answered Oct 11 '17 at 7:42

user255114

Can you ssh into your machine? If you can, try entering

sudo dmesg -n 1

That will block messages from the kernel. Might not help but worth a try

answered Oct 11 '17 at 7:42

user255114

answered Oct 11 '17 at 7:42

user255114

answered Oct 11 '17 at 7:42

user255114

answered Oct 11 '17 at 7:42

user255114

add a commentÂ |Â

up vote
1
down vote

Some protocols use the NUL for keep alives. You could try to set a high keep alive to circumvent this behaviour. E.g. in iTerm2 there is an option called "When idle, sent Ascii code".

0 (null, NUL, , ^@), originally intended to be an ignored character, but now used by many programming languages to mark the end of a string.

answered Oct 11 '17 at 11:07

Gustav

add a commentÂ |Â

up vote
1
down vote

Some protocols use the NUL for keep alives. You could try to set a high keep alive to circumvent this behaviour. E.g. in iTerm2 there is an option called "When idle, sent Ascii code".

0 (null, NUL, , ^@), originally intended to be an ignored character, but now used by many programming languages to mark the end of a string.

answered Oct 11 '17 at 11:07

Gustav

add a commentÂ |Â

up vote
1
down vote

Some protocols use the NUL for keep alives. You could try to set a high keep alive to circumvent this behaviour. E.g. in iTerm2 there is an option called "When idle, sent Ascii code".

0 (null, NUL, , ^@), originally intended to be an ignored character, but now used by many programming languages to mark the end of a string.

answered Oct 11 '17 at 11:07

Gustav

Some protocols use the NUL for keep alives. You could try to set a high keep alive to circumvent this behaviour. E.g. in iTerm2 there is an option called "When idle, sent Ascii code".

0 (null, NUL, , ^@), originally intended to be an ignored character, but now used by many programming languages to mark the end of a string.

answered Oct 11 '17 at 11:07

Gustav

answered Oct 11 '17 at 11:07

Gustav

answered Oct 11 '17 at 11:07

Gustav

answered Oct 11 '17 at 11:07

Gustav

add a commentÂ |Â

up vote
0
down vote

Solved it by running:

rmmod peaq_wmi
rmmod input_polldev

answered Dec 17 '17 at 19:32

Sebastian

add a commentÂ |Â

up vote
0
down vote

Solved it by running:

rmmod peaq_wmi
rmmod input_polldev

answered Dec 17 '17 at 19:32

Sebastian

add a commentÂ |Â

up vote
0
down vote

Solved it by running:

rmmod peaq_wmi
rmmod input_polldev

answered Dec 17 '17 at 19:32

Sebastian

Solved it by running:

rmmod peaq_wmi
rmmod input_polldev

answered Dec 17 '17 at 19:32

Sebastian

answered Dec 17 '17 at 19:32

Sebastian

answered Dec 17 '17 at 19:32

Sebastian

answered Dec 17 '17 at 19:32

Sebastian

add a commentÂ |Â

搜尋此網誌

mjhjmtu