-
Notifications
You must be signed in to change notification settings - Fork 395
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Backport 6.1 to kirkstone -> no serial console #1222
Comments
@nandra Maybe it requires a bootloader update, too. Could you cross-check a RaspberryOS? That is strange, though, as I know people booting it fine - even though I haven't tested it until now. |
@agherzan I've checked and rpi-firmware is same on kirkstone & master if you mean by "bootloader update" |
Looks like
So udev on kirkstone is setting up a serial on uart, presumably the master branch is not doing this. About to attempt porting 6.1 to kirkstone myself so I can check this, but you can compare kirkstone_99-com.rules.txt EDIT: Master is in fact pulling this file from upstream as of this commit. |
@nandra were you able to boot a 6.1 Linux kernel from the kirkstone branch? I'm not having much success with that. I don't get any kernel log output on the serial console. |
@yayay Please try to update also rpi firmware (bootfiles). It should work then. |
@nandra I see. |
In my case, the kernel was panicking early in the boot process during a USB controller init and I wasn't getting the printout on serial console because tty numbering has changed for some reason. |
Hi, I'm using kirkstone release of this layer in my project but would like to use new kernel 6.1. I've backported it to my layer (basically took it from master branch). Kernel seems to boot but I cannot see any output on serial console. In kirkstone I've set
console=ttyAMA0,115200
in cmdline.txt file. Does something changed between kernel releases? I've tried to change toconsole=ttyS0,155200
but witout success. Any ideas what else I can check please? Thanks.The text was updated successfully, but these errors were encountered: