Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #59694 > unrolled thread
| Started by | eHenry Berg <ehenry.berg@gmail.com> |
|---|---|
| First post | 2017-12-17 15:20 +0100 |
| Last post | 2018-06-03 21:10 +0200 |
| Articles | 8 — 4 participants |
Back to article view | Back to linux.debian.kernel
Bug#884601: Raspberry pi 3 and 2 hang at boot with kernel 4.14 eHenry Berg <ehenry.berg@gmail.com> - 2017-12-17 15:20 +0100
Bug#884601: "console=ttyAMA0,115200" --> "console=tty0" Matthias Luescher <lueschem@gmail.com> - 2017-12-27 17:10 +0100
Bug#884601: "console=ttyAMA0,115200" --> "console=tty0" Michael Stapelberg <stapelberg@debian.org> - 2018-01-04 18:10 +0100
Bug#884601: "console=ttyAMA0,115200" --> "console=tty0" Matthias Luescher <lueschem@gmail.com> - 2018-01-05 23:00 +0100
Bug#884601: Raspberry pi 3 and 2 hang at boot with kernel 4.14 eHenry Berg <ehenry.berg@gmail.com> - 2018-01-07 17:30 +0100
Bug#884601: Raspberry pi 3 and 2 hang at boot with kernel 4.14 eHenry Berg <ehenry.berg@gmail.com> - 2018-05-09 21:50 +0200
Bug#884601: Raspberry pi 3 and 2 hang at boot with kernel 4.14 Ben Hutchings <ben@decadent.org.uk> - 2018-05-09 22:40 +0200
Bug#884601: Raspberry pi 3 and 2 hang at boot with kernel 4.14 eHenry Berg <ehenry.berg@gmail.com> - 2018-06-03 21:10 +0200
| From | eHenry Berg <ehenry.berg@gmail.com> |
|---|---|
| Date | 2017-12-17 15:20 +0100 |
| Subject | Bug#884601: Raspberry pi 3 and 2 hang at boot with kernel 4.14 |
| Message-ID | <uXHXj-1IM-5@gated-at.bofh.it> |
Package: linux-image-4.14.0-1-armmp-lpae Version: 4.14.0-1 Firmware branch master: https://github.com/raspberrypi/firmware Debian sid I use HDMI-DVI cable. Unsuccessful bug report of firmware: https://github.com/raspberrypi/firmware/issues/915 cmdline.txt: dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p3 rootfstype=f2fs elevator=deadline rootwait config.txt: device_tree=bcm2837-rpi-3-b.dtb // From 4.13 kernel=vmlinuz-4.13.0-1-armmp-lpae initramfs initrd.img-4.13.0-1-armmp-lpae followkernel // Works very good! config.txt: device_tree=bcm2837-rpi-3-b.dtb // From 4.14 kernel=vmlinuz-4.14.0-1-armmp-lpae initramfs initrd.img-4.14.0-1-armmp-lpae followkernel // Black screen in the middle of the boot, never got kde login. Video of the screen with my camera: Welcome to Debian GNU/Linux Buster/sid! ... Set up automount Aritrary Exectuble File Mounting Kernel Debug File Starting Restore / save Listening on Journal Socket Mounting Huge Pages File Reached target Swap Starting Create list of required Listening on Journal Audit Socket Starting Journal Service vc4 hdmi 3f902000.hdmi: vc4-hdmi-hifi vc4 hdmi 3f902000.hdmi: ASoC: no DMI Mounted Kernel Debug File System-hdmi-hifi // Black screen Best Regards, Evald
[toc] | [next] | [standalone]
| From | Matthias Luescher <lueschem@gmail.com> |
|---|---|
| Date | 2017-12-27 17:10 +0100 |
| Subject | Bug#884601: "console=ttyAMA0,115200" --> "console=tty0" |
| Message-ID | <v1mrf-3SW-15@gated-at.bofh.it> |
| In reply to | #59694 |
[Multipart message — attachments visible in raw view] — view raw
Hi I just faced a similar issue with the arm64 kernel (linux-image-4.14.0-0.bpo.2-arm64). It booted fine with the 4.13 based kernel but it failed after the upgrade to the above mentioned kernel. Since I wanted to debug the stuff I took a closer look at the cmdline.txt file: There I found the config "console=ttyAMA0,115200". This looked wrong to me since ttyAMA0 is the bluetooth device on the Raspberry Pi 3. Therefore I changed it to "console=tty0" and all of a sudden my system booted again with the 4.14 kernel. Another remark: My setup also worked with the 4.14 kernel combined with the device tree binary from the 4.13 kernel. However, I do not like this hack. My full setup is here: https://github.com/lueschem/edi-pi Good luck Matthias
[toc] | [prev] | [next] | [standalone]
| From | Michael Stapelberg <stapelberg@debian.org> |
|---|---|
| Date | 2018-01-04 18:10 +0100 |
| Subject | Bug#884601: "console=ttyAMA0,115200" --> "console=tty0" |
| Message-ID | <v4hbH-8t3-11@gated-at.bofh.it> |
| In reply to | #59780 |
Hi Matthias, Matthias Luescher <lueschem@gmail.com> writes: > I just faced a similar issue with the arm64 kernel > (linux-image-4.14.0-0.bpo.2-arm64). It booted fine with the 4.13 based > kernel but it failed after the upgrade to the above mentioned kernel. Since > I wanted to debug the stuff I took a closer look at the cmdline.txt file: > There I found the config "console=ttyAMA0,115200". This looked wrong to me > since ttyAMA0 is the bluetooth device on the Raspberry Pi 3. Therefore I > changed it to "console=tty0" and all of a sudden my system booted again > with the 4.14 kernel. > > Another remark: My setup also worked with the 4.14 kernel combined with the > device tree binary from the 4.13 kernel. However, I do not like this hack. > > My full setup is here: https://github.com/lueschem/edi-pi Thanks for the details. I just uploaded a new raspi3-firmware package which uses ttyS1 on Linux ≥ 4.14, which is the new device name for the UART on the pin header: https://anonscm.debian.org/cgit/pkg-raspi/raspi3-firmware.git/commit/?id=4da2e6b1576f0a7513bffe7f95882693fdadd7ae -- Best regards, Michael
[toc] | [prev] | [next] | [standalone]
| From | Matthias Luescher <lueschem@gmail.com> |
|---|---|
| Date | 2018-01-05 23:00 +0100 |
| Subject | Bug#884601: "console=ttyAMA0,115200" --> "console=tty0" |
| Message-ID | <v4IbT-JX-1@gated-at.bofh.it> |
| In reply to | #59816 |
[Multipart message — attachments visible in raw view] — view raw
Hi Michael > I just uploaded a new raspi3-firmware package which uses ttyS1 on Linux > ≥ 4.14, which is the new device name for the UART on the pin header: > https://anonscm.debian.org/cgit/pkg-raspi/raspi3-firmware.git/commit/?id= > 4da2e6b1576f0a7513bffe7f95882693fdadd7ae Many thanks - this works great! I just verified it by fetching raspi3-firmware (1.20171201-1) from sid: https://github.com/lueschem/edi-pi/commit/d3a1b5055fa4441b7ce42d6827868bdf8e46fdda Best regards Matthias
[toc] | [prev] | [next] | [standalone]
| From | eHenry Berg <ehenry.berg@gmail.com> |
|---|---|
| Date | 2018-01-07 17:30 +0100 |
| Message-ID | <v5lZE-1Do-5@gated-at.bofh.it> |
| In reply to | #59694 |
Hi,
Thank you for your responses. I used the information from this script
to get a clean Debian environment:
https://www.raspberrypi.org/forums/viewtopic.php?t=104981&p=745746
https://github.com/ShorTie8/my_pi_os
my_pi_os.sh
My /etc/fstab:
#<file system> <dir> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/mmcblk0p1 /boot/firmware vfat noauto,noatime 0 2
/dev/mmcblk0p2 /boot ext2 defaults,noatime 0 0
/dev/mmcblk0p3 / f2fs defaults,noatime 0 0
/dev/sda1 /evsj f2fs defaults,noatime 0 0
My /etc/apt/sources.list:
deb http://ftp.fi.debian.org/debian sid main contrib non-free
deb-src http://ftp.fi.debian.org/debian sid main contrib non-free
Kernel 4.14:
Test1: console=tty0 console=${serial} root=/dev/mmcblk0p3
rootfstype=f2fs rw elevator=deadline fsck.repair=yes net.ifnames=0
rootwait
Test2: dwc_otg.lpm_enable=0 console=tty0 root=/dev/mmcblk0p3
rootfstype=f2fs elevator=deadline rootwait
Test3: rpi2 and rpi3
Test4: .dtb from 4.14 and 4.13.
Test5: Firmware from
anonscm.debian.org/cgit/pkg-raspi/raspi3-firmware.git/tree/boot
Test6: Disabled Sddm i.e. Gui to Cli interface
Test7: /etc/modules: f2fs,vc4; I removed vc4
Test8: Firmware from github.com/raspberrypi/firmware/tree/next
// All tests failed, same unsuccess as before
Kernel 4.13 works!
Another issue and maybe another bug number:
My rpi3 Bluetooth (or wlan) did not work before or now. Installation:
apt-get install firmware-brcm80211
cp from Rasbian /lib/firmware/brcm/brcmfmac43430-sdio.txt to my Debian
/lib/firmware/brcm/brcmfmac43430-sdio.txt // No success
wget -N https://anonscm.debian.org/cgit/pkg-raspi/raspi3-firmware.git/plain/brcm80211/brcmfmac43430-sdio.txt
// No success
Best Regards,
Evald
[toc] | [prev] | [next] | [standalone]
| From | eHenry Berg <ehenry.berg@gmail.com> |
|---|---|
| Date | 2018-05-09 21:50 +0200 |
| Message-ID | <vNDg5-7Gt-3@gated-at.bofh.it> |
| In reply to | #59694 |
Hi, This bug report is about linux-image-armmp-lpae. I tested linux-image-armmp with versions 4.15.0-3 and 4.16.0-1, it works! This bug 884601 can therefore be closed. I am planning to put out a guide for 32-bit and 64-bit how to install Debian desktop on Raspberry, but I have another Debian bug 897925 which means web browsers do not work for 32-bit. Best Regards, Evald
[toc] | [prev] | [next] | [standalone]
| From | Ben Hutchings <ben@decadent.org.uk> |
|---|---|
| Date | 2018-05-09 22:40 +0200 |
| Message-ID | <vNE2t-8bP-7@gated-at.bofh.it> |
| In reply to | #60948 |
[Multipart message — attachments visible in raw view] — view raw
On Wed, 2018-05-09 at 22:44 +0300, eHenry Berg wrote:
> Hi,
>
> This bug report is about linux-image-armmp-lpae. I tested
> linux-image-armmp with versions 4.15.0-3 and 4.16.0-1, it works!
> This bug 884601 can therefore be closed.
The RPi 2 has Cortex-A7 cores, which support LPAE and therefore should
be able to run Debian's armmp-lpae kernel flavour. So although you
have a way to avoid the bug, I think there's still a bug here.
(I'm not sure about RPi 3 as I don't know to what extent ARM supports
running 32-bit kernels on 64-bit cores. I would certainly recommend
using the arm64 kernel.)
Ben.
> I am planning to put out a guide for 32-bit and 64-bit how to install
> Debian desktop on Raspberry, but I have another Debian bug 897925
> which means web browsers do not work for 32-bit.
--
Ben Hutchings
The obvious mathematical breakthrough [to break modern encryption]
would be development of an easy way to factor large prime numbers.
- Bill Gates
[toc] | [prev] | [next] | [standalone]
| From | eHenry Berg <ehenry.berg@gmail.com> |
|---|---|
| Date | 2018-06-03 21:10 +0200 |
| Message-ID | <vWGy5-7rl-1@gated-at.bofh.it> |
| In reply to | #59694 |
I tested version 4.16 with lpae: # apt-get install linux-image-4.16.0-2-armmp-lpae My both Rpi2 and Rpi3 show: # uname -a Linux irena 4.16.0-2-armmp-lpae #1 SMP Debian 4.16.12-1 (2018-05-27) armv7l GNU/Linux # Version 4.16 works with lpae! This bug can therefore be closed. By the way, I made a guide for 32-bit and 64-bit for Debian for Raspberry Pi: https://github.com/evasjo/DebianSbcRaspberry // Evald
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web