Documented work-around so closing as 'Fix Released'. Please open a new
bug report if you still encounter the problem.
** Changed in: linux-raspi (Ubuntu Focal)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@Juerg,
Is it correct that all that is required to make v3d driver work on armhf
pi3+b is to modify the /boot/firmware/usercfg.txt to include:
dtoverlay=vc4-kms-v3d,cma-64,cma-128
@Jon,
Note that the pi-gadget default uses fkms, not kms. For example the 18 armhf:
-
From: boun...@canonical.com On Behalf Of Kyle Nitzsche
Sent: Friday, September 25, 2020 2:54 PM
To: Jonathan Watson
Subject: [Bug 1889223] Re: vc4-kms-v3d boot failure focal armhf preinstalled
server
- - - external message, proceed with caution - - -
OK, so you are saying it is really
OK, so you are saying it is really not a kernel fix but is rather an
enablement file change/config. thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889223
Title:
vc4-kms-v3d boot failure
What fix? The fix is to limit the cma size as indicated in the previous
comments.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889223
Title:
vc4-kms-v3d boot failure focal armhf preinstalled
Hi, a fix for this is needed for an important project. Can we please get
a sense of the expected time frame for the fix landing?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889223
Title:
Qt responded and thinks cma-128 will work for our application.
I modified our Pi test unit to use the original Ubuntu 20.04 .dtbo file
and booted successfully when I used the dtoverlay=vc4-kms-v3d,cma-64
setting.
I will test our UI with this configuration early next week.
--
You received this
OK, we will try CMA-128 not sure if it will matter for our
application since we aren't doing complex 3D rendering.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889223
Title:
vc4-kms-v3d boot
>From my testing cma-128 is the largest that worked.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889223
Title:
vc4-kms-v3d boot failure focal armhf preinstalled server
To manage notifications
I will test that with the default .dtbo file and see if it works for us.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889223
Title:
vc4-kms-v3d boot failure focal armhf preinstalled server
To
Using 256MB for CMA seems problematic for the armhf kernel. A work-
around is to lower it like so:
dtoverlay=vc4-kms-v3d,cma-64
** Changed in: linux-raspi (Ubuntu Focal)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The above are benign warnings that should actually be suppressed.
I confirmed the issue: Fails on armhf, works on arm64.
** Changed in: linux-raspi (Ubuntu Focal)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Also affects: linux-raspi (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux-raspi (Ubuntu)
Status: New => Invalid
** Changed in: linux-raspi (Ubuntu Focal)
Assignee: (unassigned) => Juerg Haefliger (juergh)
--
You received this bug notification
Project noticed this frame buffer "failed" message in boot console and
we are not sure if it is problem or not:
Starting kernel ...
[0.313431] kobject_add_internal failed for 3e812000.framebuffer with
-EEXIST, don't try to register things with the same name in the same
directory.
[
I was able to confirm that if I started from a clean install of Ubuntu
20.04 I could copy the 18.04 .dtbo file per the workaround described
above and get the board to boot with the usercfg.txt / dtoverlay=vc4
-kms-v3d setting in place.
I was unable to make it work on my initial install, which I
15 matches
Mail list logo
