Increasing video memory appears to have fixed my problem.
My virtual screen size is 1920x1080 and in virt-manager's Video panel /
XML tab, vgamem was set to the default value of 16384. After increasing
it to 65536, I'm no longer seeing the freeze (though with only a few
minutes of testing, so
Public bug reported:
I'm running a new installation of Ubuntu 22.04 Desktop on a Thinkpad
T450s (core i5-5200, 2 cores / 4 vCPUs, 12 GB memory). Using the virt-
manager GUI, I performed what I believe is a simple, plain-vanilla
installation of an Ubuntu 22.04 guest running under qemu/kvm with 2
I have marked the "Focal" context for this bug as "Fix Released."
Is observing it fixed on Focal sufficient to close it for the "linux-
raspi (Ubuntu)" context?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have verified that the bug is fixed in the most recent software update
on both 32-bit and 64-bit installations of ubuntu 20.04 on a pi 4.
** Changed in: linux-raspi (Ubuntu Focal)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
i can confirm that this bug is FIXED in the 1015 kernel which i
downloaded through the normal software update process.
tested on both 32-bit and 64-bit kernels.
THANKS!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Just checking in to see if there's any ETA on promoting this fix into
focal-updates for the pi 4.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880125
Title:
v3d driver clock problem forces OpenGL
Great!
A 64-bit kernel I built with the same changes also works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880125
Title:
v3d driver clock problem forces OpenGL to use software rendering
To
I'll try 64-bit later today.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880125
Title:
v3d driver clock problem forces OpenGL to use software rendering
To manage notifications about this bug go
I have now built and run a kernel with:
CONFIG_DRM_V3D=m
CONFIG_CLK_RASPBERRYPI=y
CONFIG_ARM_RASPBERRYPI_CPUFREQ=y
in .../focal/debian.raspi/config/config.common.ubuntu and i can confirm
that it fixes the problem.
My debug code shows raspberrypi_clk_probe() successfully adding clock
Re-examining the output of the debug code I added a few weeks ago, I
noticed that I had put a kprintf into clk-
raspberrypi.c/raspberrypi_clk_probe(), and it never was invoked.
Thus, I think you're right that adding:
CONFIG_CLK_RASPBERRYPI=y
CONFIG_ARM_RASPBERRYPI_CPUFREQ=y
has a good chance of
> why do you think it was disabled again?
I was looking in .../focal/debian.raspi/config/...
Investigating this bug is my first foray into the linux kernel source;
I'm not familiar with the details of kernel configuration.
So if it's already enabled in .../focal/arch/arm64/configs/... and has
That commit was 9 weeks and 422 commits ago. At some point after that,
it was disabled again.
There have been a number of commits that mention v3d since then,
including several that mention clocks.
Is it sufficient simply to re-enable CONFIG_CLK_RASPBERRYPI?
--
You received this bug
comment 33 of bug 1850876 mentions dtoverlay=vc4-fkms-v3d.
i have had that line all along in /boot/firmware/usercfg.txt (which is where it
goes on a pi 4).
bug 1850876 references linux-raspi2, and the v2 test kernel is based on
linux 5.3.
i'm running ubuntu 20.04 on a pi 4 - the raspi branch -
** Attachment added: "v3d-clock-problem-debug-excerpts.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1880125/+attachment/5376998/+files/v3d-clock-problem-debug-excerpts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
i'm attaching some small excerpts from dmesg output from some debugging
printk calls i added to the kernel v3d and clock code.
there is another small issue with v3d_platform_drm_probe() - when it
gets -EPROBE_DEFER from devm_clk_get(), it doesn't return -EPROBE_DEFER
to its caller, so
I believe this change is necessary, but not sufficient, to make OpenGL use the
GPU on a pi 4 running 20.04. After making the change and trying it, I filed a
new bug report:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1880125
--
You received this bug notification because you are
i forgot to mention: the relevant device tree file is:
arch/arm/boot/dts/bcm2711-rpi.dtsi
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880125
Title:
v3d driver clock problem forces OpenGL to
Public bug reported:
release: 32-bit ubuntu 20.04 running on a raspberry pi 4
package: linux-raspi 5.4.0.1008.8
I made the configuration change described in:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1876862
and am running a kernel with v3d on a raspberry pi 4.
My domains are part of the 30,000 whose renewals will begin failing on
March 13th, 2019.
Can this be fixed before then?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1745126
Title:
Let's Encrypt
Cubic PPA: I just tried switching between Frequent and All applications
view, and it's working OK for me.
The only change I've made that I can imagine affecting this is my use of
onboard and gnome-shell-extension-onboard, but I think it's unlikely
that that has made a difference.
When I first
This bug affects me, running Ubuntu 18.04 on a Dell Venue 11 pro 7140.
I have a work-around that seems to be working reliably for the "Show
Applications" dots grid button: tap-and-hold until the application icons
appear, then slide your finger up into the dock bar, then release.
This only works
I am getting exactly the same behavior, running Ubuntu 18.04 LiveCD on a
Dell Venue 11 Pro 7140.
Using the touchscreen to click an icon in the dash results in TWO
instances of the given application being created.
Using the touchscreen to click the "Show Applications" icon does nothing
--
You
i have the same behavior, using a Biostar TF7050-M2 motherboard.
my BIOS SATA Operation Mode default value of IDE worked during
install; had to switch it to AHCI for the installed system.
--
CD and DVD drives don't work on Feisty 7.04
https://bugs.launchpad.net/bugs/133142
You received this bug
i should have mentioned that my DVD drive is a SATA drive, samsung SH-
S183L.
--
CD and DVD drives don't work on Feisty 7.04
https://bugs.launchpad.net/bugs/133142
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
i had exactly the same behavior, installing ubuntu 7.04, except that i'm
installing an English language system. i chose skip, and my
installation worked OK.
--
Installation freezes at 83% language packs
https://bugs.launchpad.net/bugs/110260
You received this bug notification because you are a
workaround - i was able to make a partition larger than 200GB by booting
a gparted liveCD 0.3.3.0, which i'd downloaded from sourceforge some
time ago.
--
prepare partition can't create 200Gb paritions
https://bugs.launchpad.net/bugs/107787
You received this bug notification because you are a
26 matches
Mail list logo
