Serial port only recognized with acpi=off boot flag
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
I have a computer with a skylake motherboard (ASRock IMB-195), and I'm trying to use the on-board serial port (/dev/ttyS0). I'm using Ubuntu Server with Linux Kernel 4.4.0-72.
If I boot with acpi=off, I get the following output (dmesg):
Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
serial8250: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
serial8250: ttyS2 at I/O 0x3e8 (irq = 3, base_baud = 115200) is a 16550A
serial8250: ttyS3 at I/O 0x2e8 (irq = 3, base_baud = 115200) is a 16550A
with acpi on:
Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Completely disabling ACPI is very suboptimal (can't reboot without manually power cycling for example).
Is there a way to disable the parts of ACPI that are preventing the serial driver from working?
ubuntu serial-port acpi
add a comment |
up vote
1
down vote
favorite
I have a computer with a skylake motherboard (ASRock IMB-195), and I'm trying to use the on-board serial port (/dev/ttyS0). I'm using Ubuntu Server with Linux Kernel 4.4.0-72.
If I boot with acpi=off, I get the following output (dmesg):
Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
serial8250: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
serial8250: ttyS2 at I/O 0x3e8 (irq = 3, base_baud = 115200) is a 16550A
serial8250: ttyS3 at I/O 0x2e8 (irq = 3, base_baud = 115200) is a 16550A
with acpi on:
Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Completely disabling ACPI is very suboptimal (can't reboot without manually power cycling for example).
Is there a way to disable the parts of ACPI that are preventing the serial driver from working?
ubuntu serial-port acpi
First step would be to comparedmesg
after boot with and withoutacpi=off
, and see what goes wrong. There are also tools to decode the ACPI tables (but the ACPI spec is difficult, this isn't fun).
– dirkt
Nov 27 at 7:39
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I have a computer with a skylake motherboard (ASRock IMB-195), and I'm trying to use the on-board serial port (/dev/ttyS0). I'm using Ubuntu Server with Linux Kernel 4.4.0-72.
If I boot with acpi=off, I get the following output (dmesg):
Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
serial8250: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
serial8250: ttyS2 at I/O 0x3e8 (irq = 3, base_baud = 115200) is a 16550A
serial8250: ttyS3 at I/O 0x2e8 (irq = 3, base_baud = 115200) is a 16550A
with acpi on:
Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Completely disabling ACPI is very suboptimal (can't reboot without manually power cycling for example).
Is there a way to disable the parts of ACPI that are preventing the serial driver from working?
ubuntu serial-port acpi
I have a computer with a skylake motherboard (ASRock IMB-195), and I'm trying to use the on-board serial port (/dev/ttyS0). I'm using Ubuntu Server with Linux Kernel 4.4.0-72.
If I boot with acpi=off, I get the following output (dmesg):
Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
serial8250: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
serial8250: ttyS2 at I/O 0x3e8 (irq = 3, base_baud = 115200) is a 16550A
serial8250: ttyS3 at I/O 0x2e8 (irq = 3, base_baud = 115200) is a 16550A
with acpi on:
Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Completely disabling ACPI is very suboptimal (can't reboot without manually power cycling for example).
Is there a way to disable the parts of ACPI that are preventing the serial driver from working?
ubuntu serial-port acpi
ubuntu serial-port acpi
asked Apr 20 '17 at 13:47
Magneon
62
62
First step would be to comparedmesg
after boot with and withoutacpi=off
, and see what goes wrong. There are also tools to decode the ACPI tables (but the ACPI spec is difficult, this isn't fun).
– dirkt
Nov 27 at 7:39
add a comment |
First step would be to comparedmesg
after boot with and withoutacpi=off
, and see what goes wrong. There are also tools to decode the ACPI tables (but the ACPI spec is difficult, this isn't fun).
– dirkt
Nov 27 at 7:39
First step would be to compare
dmesg
after boot with and without acpi=off
, and see what goes wrong. There are also tools to decode the ACPI tables (but the ACPI spec is difficult, this isn't fun).– dirkt
Nov 27 at 7:39
First step would be to compare
dmesg
after boot with and without acpi=off
, and see what goes wrong. There are also tools to decode the ACPI tables (but the ACPI spec is difficult, this isn't fun).– dirkt
Nov 27 at 7:39
add a comment |
1 Answer
1
active
oldest
votes
up vote
2
down vote
You can try "acpi=noirq" instead. That's the only way I can get my ttyS0 to work with Serial-Over-Lan on an Intel AMT platform. It doesn't seem to have any ill effects but if anyone else knows a better solution, please share.
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
You can try "acpi=noirq" instead. That's the only way I can get my ttyS0 to work with Serial-Over-Lan on an Intel AMT platform. It doesn't seem to have any ill effects but if anyone else knows a better solution, please share.
add a comment |
up vote
2
down vote
You can try "acpi=noirq" instead. That's the only way I can get my ttyS0 to work with Serial-Over-Lan on an Intel AMT platform. It doesn't seem to have any ill effects but if anyone else knows a better solution, please share.
add a comment |
up vote
2
down vote
up vote
2
down vote
You can try "acpi=noirq" instead. That's the only way I can get my ttyS0 to work with Serial-Over-Lan on an Intel AMT platform. It doesn't seem to have any ill effects but if anyone else knows a better solution, please share.
You can try "acpi=noirq" instead. That's the only way I can get my ttyS0 to work with Serial-Over-Lan on an Intel AMT platform. It doesn't seem to have any ill effects but if anyone else knows a better solution, please share.
answered Nov 27 at 2:36
Neal
212
212
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2funix.stackexchange.com%2fquestions%2f360193%2fserial-port-only-recognized-with-acpi-off-boot-flag%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
First step would be to compare
dmesg
after boot with and withoutacpi=off
, and see what goes wrong. There are also tools to decode the ACPI tables (but the ACPI spec is difficult, this isn't fun).– dirkt
Nov 27 at 7:39