| 3 Apr 2025 |
 K900 | Looks nicer, I guess | 09:42:44 |
| 20 May 2021 |
|  John Ericson changed their display name from Ericson2314 to John Ericson. | 07:38:18 |
| 3 Apr 2025 |
 eliasp | I've seen it offers a fancy cat-featured splash menu! 😆 | 09:43:21 |
| 20 May 2021 |
|  ma27 joined the room. | 07:40:18 |
| 3 Apr 2025 |
 Arian | Sold | 10:10:36 |
| 20 May 2021 |
|  Alyssa Ross joined the room. | 07:46:54 |
| 3 Apr 2025 |
| Arian | Limine supports bios unlike sdboot | 10:10:49 |
| 20 May 2021 |
|  lovesegfault joined the room. | 08:08:38 |
| 3 Apr 2025 |
|  dblsaiko ⚧︎ 🔪 changed their display name from dblsaiko to dblsaiko 🔪. | 12:51:44 |
| 20 May 2021 |
|  bbigras joined the room. | 10:12:58 |
| 3 Apr 2025 |
|  2xsaiko (moved! @saiko:knifepoint.net) changed their display name from 2xsaiko to 2xsaiko (moved! @saiko:knifepoint.net). | 12:52:00 |
 @rosscomputerguy:matrix.org | How does one get a debug stack trace with coredumpctl and environment.enableDebugInfo? | 15:43:28 |
| 20 May 2021 |
|  flokli joined the room. | 10:23:40 |
| 3 Apr 2025 |
| K900 | coredumpctl debug | 16:03:13 |
| 20 May 2021 |
|  primeos joined the room. | 10:32:01 |
| 4 Apr 2025 |
 ElvishJerricco | I've been trying to figure out why the systemd-shutdown test is failing, and apparently it's because of this: https://github.com/NixOS/nixpkgs/pull/387836 | 06:37:12 |
| 20 May 2021 |
| flokli set a profile picture. | 10:38:17 |
| 4 Apr 2025 |
| ElvishJerricco | which I'm pretty sure means that having console=ttyS0 as the last console parameter was critical to its functioning | 06:37:56 |
| 20 May 2021 |
 @grahamc:nixos.org | me too | 11:01:53 |
| 4 Apr 2025 |
| ElvishJerricco | which has set me down a small rabbit hole about how console= actually works | 06:38:09 |
| 20 May 2021 |
 Mic92 | homesick for ward? | 12:17:04 |
| 4 Apr 2025 |
| ElvishJerricco | and I hate it | 06:38:10 |
| 20 May 2021 |
| Mic92 | * homesick for what? | 12:17:20 |
| 4 Apr 2025 |
| ElvishJerricco |
You can specify multiple console= options on the kernel command line.
The behavior is well defined when each device type is mentioned only once. In this case, the output will appear on all requested consoles. And the last device will be used when you open /dev/console. So, for example:
console=ttyS1,9600 console=tty0
defines that opening /dev/console will get you the current foreground virtual console, and kernel messages will appear on both the VGA console and the 2nd serial port (ttyS1 or COM2) at 9600 baud.
The behavior is more complicated when the same device type is defined more times. In this case, there are the following two rules:
- The output will appear only on the first device of each defined type.
2/ /dev/console will be associated with the first registered device. Where the registration order depends on how kernel initializes various subsystems.This rule is used also when the last console= parameter is not used for other reasons. For example, because of a typo or because the hardware is not available.
The result might be surprising. For example, the following two command lines have the same result:
console=ttyS1,9600 console=tty0 console=tty1
console=tty0 console=ttyS1,9600 console=tty1
| 06:39:55 |
| 20 May 2021 |
 andi- | I am guessing IRC | 12:39:27 |
| 4 Apr 2025 |
| ElvishJerricco | *
You can specify multiple console= options on the kernel command line.
The behavior is well defined when each device type is mentioned only once. In this case, the output will appear on all requested consoles. And the last device will be used when you open /dev/console. So, for example:
console=ttyS1,9600 console=tty0
defines that opening /dev/console will get you the current foreground virtual console, and kernel messages will appear on both the VGA console and the 2nd serial port (ttyS1 or COM2) at 9600 baud.
The behavior is more complicated when the same device type is defined more times. In this case, there are the following two rules:
- The output will appear only on the first device of each defined type.
- /dev/console will be associated with the first registered device. Where the registration order depends on how kernel initializes various subsystems.This rule is used also when the last console= parameter is not used for other reasons. For example, because of a typo or because the hardware is not available.
The result might be surprising. For example, the following two command lines have the same result:
console=ttyS1,9600 console=tty0 console=tty1
console=tty0 console=ttyS1,9600 console=tty1
| 06:40:07 |
| 20 May 2021 |
|  kevincox joined the room. | 13:25:08 |
| 4 Apr 2025 |
| ElvishJerricco | *
You can specify multiple console= options on the kernel command line.
The behavior is well defined when each device type is mentioned only once. In this case, the output will appear on all requested consoles. And the last device will be used when you open /dev/console. So, for example:
console=ttyS1,9600 console=tty0
defines that opening /dev/console will get you the current foreground virtual console, and kernel messages will appear on both the VGA console and the 2nd serial port (ttyS1 or COM2) at 9600 baud.
The behavior is more complicated when the same device type is defined more times. In this case, there are the following two rules:
- The output will appear only on the first device of each defined type.
- /dev/console will be associated with the first registered device. Where the registration order depends on how kernel initializes various subsystems.This rule is used also when the last console= parameter is not used for other reasons. For example, because of a typo or because the hardware is not available.
The result might be surprising. For example, the following two command lines have the same result:
console=ttyS1,9600 console=tty0 console=tty1
console=tty0 console=ttyS1,9600 console=tty1
| 06:40:25 |
| 20 May 2021 |
|  scott joined the room. | 13:29:24 |
| 4 Apr 2025 |
| ElvishJerricco | *
You can specify multiple console= options on the kernel command line.
The behavior is well defined when each device type is mentioned only once. In this case, the output will appear on all requested consoles. And the last device will be used when you open /dev/console. So, for example:
console=ttyS1,9600 console=tty0
defines that opening /dev/console will get you the current foreground virtual console, and kernel messages will appear on both the VGA console and the 2nd serial port (ttyS1 or COM2) at 9600 baud.
The behavior is more complicated when the same device type is defined more times. In this case, there are the following two rules:
- The output will appear only on the first device of each defined type.
- /dev/console will be associated with the first registered device. Where the registration order depends on how kernel initializes various subsystems.This rule is used also when the last console= parameter is not used for other reasons. For example, because of a typo or because the hardware is not available.
The result might be surprising. For example, the following two command lines have the same result:
console=ttyS1,9600 console=tty0 console=tty1
console=tty0 console=ttyS1,9600 console=tty1
| 06:40:43 |
