** Changed in: linux-firmware-raspi2 (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848247
Title:
3A+ boot failure on Eoan
To manage
The Eoan Ermine has reached end of life, so this bug will not be fixed
for that release
** Changed in: linux-firmware-raspi2 (Ubuntu Eoan)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux-firmware-raspi2 (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848247
Title:
3A+ boot failure on Eoan
To manage notifications
** Changed in: linux-firmware-raspi2 (Ubuntu Eoan)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848247
Title:
3A+ boot failure on Eoan
To manage
Can confirm that the test kernel from LP: #1848790 comment #11 fixes
boot on 3A+ (remove vc4-fkms-v3d overlay from config.txt too, and boot
operates correctly with framebuffer working). Tested on arm64 3A+ (and
3B, 3B+, 4B); need to test on armhf too.
--
You received this bug notification
** Also affects: linux-firmware-raspi2 (Ubuntu Eoan)
Importance: Undecided
Status: New
** Changed in: linux-firmware-raspi2 (Ubuntu Eoan)
Importance: Undecided => High
** Changed in: linux-firmware-raspi2 (Ubuntu Eoan)
Status: New => Triaged
** Tags removed: rls-ee-incoming
> I mean the simplefb driver in the kernel in the #3, I didn't know
there is a simplefb driver in the uboot too.
Ah, I'm afraid my lack of kernel knowledge is showing there: I didn't
realize the was a simplefb in the kernel! I should've thought given the
kernel starts off looking fine, and only
I mean the simplefb driver in the kernel in the #3, I didn't know there
is a simplefb driver in the uboot too.
So it looks like: uboot.simplefb ---> kernel.simplefb works fine
uboot.simplefb ---> kernel.simplefb > drm_vc4_fb works
fine (but RPI3A+ crash)
I'm at a similar place; currently digging into the simplefb side of
things. My current thoughts are as follows:
1. Ideally I want to ditch the vc4-fkms-v3d overlay; firstly this
resolves the 3A+ booting issue, secondly it's something that should be
an option rather than mandatory to the boot
So far, what I got from investigation is:
After setting vc4-fkms-v3d, the fb driver's sequence is bootloader ->
simplefb -> drm_vc4 fb
Without vc4-fkms-v3d, the sequence is bootloader -> simplefb ->
bcm2708_fb (the screen will flicker when bcm2708_fb takeover the
display)
I will continue
** Tags added: id-5da7195077417327157503f8
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1848247
Title:
3A+ boot failure on Eoan
To manage notifications about this bug go to:
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1848247
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Tags added: eoan rls-ee-incoming
** Changed in: linux-firmware-raspi2 (Ubuntu)
Status: New => Triaged
** Changed in: linux-firmware-raspi2 (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Related to #1847596 - commenting out the vc4-fkms-v3d overlay in
config.txt permits the 3A+ to boot, albeit with corrupted framebuffer.
In other words, solving #1847596 "properly" should also yield a fix for
this.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
14 matches
Mail list logo
