Vagrant Cascadian <[email protected]> writes: > My hunch is guix is setting up a getty on the default console > /dev/console (specified on the kernel commandline as > console=ttymxc1,115200), and it is also defined in your > agetty-service-type as /dev/ttymxc1 ... and the two gettys do not > realize they are effectively talking to the same device and get in each > other's way. > > To test if that is the case, try disabling the agetty-service-type (or > not defining the console in kernel-arguments, but then you would miss > kernel messages)... and if you still get a working console, yay? :)
Hi Vagrant! Your hunch was correct. Removing `agetty-service-type` indeed resolve the problem. I think i have a fundamental misconception on how console/tty configuration works. I was under the assumption that i need to setup the `console` boot parameter in order to get early kernel message logging on my uart port but still have to setup agetty on the same ttymxc1 in order to spawn a login prompt. Looks like that this is not the case. Thanks for your quick reply. -- Best regards Christoph Buck <[email protected]> GnuPG key: https://web.icepic.de/public_key.txt FingerPrint: B43F 4D2B 2017 E715 36C0 03C6 B8BB BCDE CD00 3305
