From ef09e30679745ba1891dce096235cd1b4c898dbb Mon Sep 17 00:00:00 2001 From: Samuel Dionne-Riel Date: Tue, 3 Dec 2019 22:28:41 -0500 Subject: [PATCH] motorola-addison: Remove `console=` argument Ah! It looks like this is not a constant, but a common failure mode among android-based devices! In dmesg: ``` Warning: unable to open an initial console. ``` Simply removing the `console=` fixes the console. See f295dc1739d1776025a1c21e0e3a9e8780a4062a for a similar instance of the issue. --- devices/motorola-addison/default.nix | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/devices/motorola-addison/default.nix b/devices/motorola-addison/default.nix index da273ba8..b0077dcc 100644 --- a/devices/motorola-addison/default.nix +++ b/devices/motorola-addison/default.nix @@ -17,7 +17,17 @@ dev_touchscreen_calibration = ""; dev_keyboard = ""; flash_method = "fastboot"; - kernel_cmdline = "console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=30 msm_rtb.filter=0x237 ehci-hcd.park=3 androidboot.bootdevice=7824900.sdhci lpm_levels.sleep_disabled=1 vmalloc=350M buildvariant=userdebug"; + kernel_cmdline = lib.concatStringsSep " " [ + "androidboot.console=ttyHSL0" + "androidboot.hardware=qcom" + "user_debug=30" + "msm_rtb.filter=0x237" + "ehci-hcd.park=3" + "androidboot.bootdevice=7824900.sdhci" + "lpm_levels.sleep_disabled=1" + "vmalloc=350M" + "buildvariant=userdebug" + ]; generate_bootimg = true; bootimg_qcdt = true; flash_offset_base = "0x80000000";