Kernel 5.10 - RPI1 + Kodi no longer usable because the connection to the screen always breaks down
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- linux
- Domain
- operating-systems
Research direction
The report compares kernel 5.10.14 with 5.4 on an RPI1 running Kodi and HDMI at 1080p, using bcmrpi_defconfig. Start by reproducing the display failure with both kernel versions and inspect dmesg and syslog, which the report says contain no useful errors. Done means identifying the regression or a confirmed configuration cause so the HDMI connection remains usable.
Written by the indexing model from the issue text.
Description
For days I've been trying in vain to get the kernel 5.10 (currently .14) and Kodi to work.
The connection to the screen (HDMI 1080p 50 or 60Hz) keeps breaking down and the TV finally reports 'No signal'.
Unfortunately there is nothing in the logs (neither dmesg nor syslog reports anything).
Using kernel 5.4 everything works fine of course. The 5.10 kernel was built with bcmrpi_defconfig, only BTRFS is builtin because BTRFS is used as root filesystem.
Trying with cma=xxx did not change anything
Did I miss something or is the kernel 5.10 currently really almost unusable?
(see also https://github.com/raspberrypi/linux/issues/4112)
- Dominant language
- C
- Stars
- 13.2k
- Forks
- 5.5k
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 21
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from raspberrypi/linux
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raspberrypi/linux#7415 · 2 comments · 1 reaction ·
-
rp1-cfe doesn't forward V4L2_EVENT_SOURCE_CHANGE event from csi-2 sensor driver to userspace app Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
raspberrypi/linux#7399 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
raspberrypi/linux#7357 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raspberrypi/linux#7054 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
raspberrypi/linux#7634 · 8 comments · 1 reaction ·
All issues in raspberrypi/linux
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
zephyrproject-rtos/zephyr#119726 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
api7/lua-resty-saml#63 ·
-
[Bounty proposal] fix(web): memory insights count an evening memory on the next day ($25 proposed) Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
BasedHardware/omi#15320 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
[adam] AdamNet network read doesn't cap to MAX_ADAM_PACKET_LEN, overflows client receive buffers Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
FujiNetWIFI/fujinet-firmware#1649 · 2 comments ·