Your message dated Fri, 13 Mar 2020 12:46:10 -0600
with message-id <[email protected]>
and subject line Bug fixed in 1.20200114-2
has caused the Debian Bug report #939728,
regarding raspi3-firmware: serial console device for Raspberry Pi Model B rev 2
is incorrect
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
939728: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939728
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: raspi3-firmware
Version: 1.20190215-1
Dear Maintainer,
The script /etc/kernel/postinst.d/z50-raspi3-firmware selects which
serial device ther kernel should use as the console, and has a
specific check for Linux kernels 4.14 and later:
serial="ttyAMA0,115200"
kernelmajor=$(echo "${latest_kernel_basename}" | sed 's,^vmlinuz-,,g' | cut
-d. -f 1)
kernelminor=$(echo "${latest_kernel_basename}" | cut -d. -f 2)
if [ $kernelmajor -ge 4 ]; then
if [ $kernelminor -ge 14 ]; then
# Since Linux 4.14, /dev/ttyS1 is the UART on the pinheader.
serial="ttyS1,115200"
fi
fi
I have a Raspberry Pi Model B revision 2 which I made work with Buster
by copying the right DTB files into /boot/firmware (details reported
in a separate bug). I have linux-image-4.19.0-5-rpi installed, and no
other kernel version installed, but I get no serial output when I use
the cmdline.txt file generated by the postinst.d script, which
includes "console=tty0 console=ttyS1,115200". If I change it back to
ttyAMA0 by hand, or patch cmdline.txt in a later postinst.d script, I
do get serial output on boot and a login prompt once the system
finishes booting.
This is using physical pins 8 and 10 of header P1.
I don't know if this is because I'm using such an old board. Can you
please further limit the conditions which change the console to ttyS1?
I haven't looked into the question of when it should be ttyS1 and when
it should be ttyAMA0 (I just tried ttyAMA0 and it worked), so I'm
afraid I can't offer any patch which I know will be correct across all
boards.
Thanks for looking into this!
-- System Information:
Debian Release: 10.0
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: armel (armv6l)
Kernel: Linux 4.19.0-5-rpi
Kernel taint flags: TAINT_CRAP
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to
en_US.UTF-8), LANGUAGE=C (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages raspi3-firmware depends on:
ii dosfstools 4.1-2
raspi3-firmware recommends no packages.
raspi3-firmware suggests no packages.
-- Configuration Files:
/etc/default/raspi3-firmware changed:
ROOTPART=UUID=7ffc98fc-1970-4289-a7ed-d89c844c3675
-- no debconf information
--
J.P. Larocque <[email protected]>
--- End Message ---
--- Begin Message ---
Package: raspi-firmware
Version: 1.20200114-2
Hello,
Sorry - As said in 939727, I also didn't check on the BTS for this bug
in time. I'm closing both now - Several months too late for such easy
fixes ☹
The relevant commit for this fix was:
https://salsa.debian.org/debian/raspi-firmware/-/commit/98e4d1ee2d12c6fe710c6cffe5ec62bd955088c8
Thanks,
--- End Message ---
