[Bug 1876862] Re: Missing v3d driver disables 3D support on RPi4

2020-05-14 Thread Mark Dunn
Thanks, what version will it appear in please, I would like to test it on (Pi4/arm64) The last one that got updated/upgraded was 5.4.0-1011-raspi (which I have ignored so far) NOTE: In order to see this change in the linux config you may want to change linux/drivers/gpu/drm/v3d/kconfig -

[Bug 1875936] [NEW] video acceleration

2020-04-29 Thread Mark Dunn
Public bug reported: Setup: I have installed the latest 20.04 LTS Ubuntu software on my raspberry pi 4b The kernel was 5.4.0-1008.8 in config.txt I have ... dtoverlay=vc4-fkms-v3d max_framebuffers=2 ... I am running ubuntu-desktop Problem: When displaying the

[Bug 1850876] Re: CONFIG_DRM_V3D is disabled for linux-raspi2 of eoan

2020-04-21 Thread Mark Dunn
For 6 months I have been using the raspberry pi kernel grafted onto the rest of Ubuntu to get V3D. It is a shame that 6 month later this is still not fixed. If you can supply a recipe for the building the official ubuntu kernel for the pi I would be willing to try and fix it. -- You received

[Bug 1850876] Re: CONFIG_DRM_V3D is disabled for linux-raspi2 of eoan

2019-12-03 Thread Mark Dunn
I think the original 1013 had flicker and tearing before the screen went blank (the os was still functional - ssh worked). With your image/modules/buildinfo i get: uname -a Linux ubuntu 5.3.0-1013-raspi2 #15+v3d SMP Sun Nov 24 13:41:44 CST 2019 aarch64 aarch64 aarch64 GNU/Linux Enlarging the

[Bug 1850876] Re: CONFIG_DRM_V3D is disabled for linux-raspi2 of eoan

2019-11-29 Thread Mark Dunn
short version: With raspberry pi 4: your binaries applied (https://people.canonical.com/~hwang4/v3d-fix/) The screen flickers then blanks I installed an built the latest mesa The screen flickers then blanks Back to the raspberry pi kernel (4.19) Which still works... long version: downloaded

[Bug 1850876] Re: CONFIG_DRM_V3D is disabled for linux-raspi2 of eoan

2019-11-13 Thread Mark Dunn
I tried upgrading from eoan-proposed, but it isn't there yet on the arm64 when is the next release please ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850876 Title: CONFIG_DRM_V3D is disabled

[Bug 1848703] Re: Raspberry Pi 4 - USB Bus not detecting any devices

2019-10-31 Thread Mark Dunn
*** This bug is a duplicate of bug 1848790 *** https://bugs.launchpad.net/bugs/1848790 I have tried the v3d.ko with latest stable version of mesa 19.2 Which works well. glxinfo is the application to show everything is working and it produces ...Accelerated: yes for a fast

[Bug 1848703] Re: Raspberry Pi 4 - USB Bus not detecting any devices

2019-10-30 Thread Mark Dunn
*** This bug is a duplicate of bug 1848790 *** https://bugs.launchpad.net/bugs/1848790 Thank you for your help so far... I want (and I have got) dtoverlay=vc4-fkms-v3d I want (and I have got) the vm4 drm driver /lib/modules/5.3.0-1008-raspi2/kernel/drivers/gpu/drm/vc4/vc4.ko I

[Bug 1848703] Re: Raspberry Pi 4 - USB Bus not detecting any devices

2019-10-30 Thread Mark Dunn
*** This bug is a duplicate of bug 1848790 *** https://bugs.launchpad.net/bugs/1848790 OK, with your new "roll up" things are looking quite good, however your config.txt contains dtoverlay=vc4-fkms-v3d I can also see the matching device tree binary object vc4-fkms-v3d.dtbo In

[Bug 1848703] Re: Raspberry Pi 4 - USB Bus not detecting any devices

2019-10-29 Thread Mark Dunn
*** This bug is a duplicate of bug 1848790 *** https://bugs.launchpad.net/bugs/1848790 Thanks. ubuntu@ubuntu:~$ sudo dpkg -i linux-image-5.3.0-1008-raspi2_5.3.0-1008.9+newupdate_arm64.deb (Reading database ... 97816 files and directories currently installed.) Preparing to unpack

[Bug 1848703] Re: Raspberry Pi 4 - USB Bus not detecting any devices

2019-10-29 Thread Mark Dunn
*** This bug is a duplicate of bug 1848790 *** https://bugs.launchpad.net/bugs/1848790 hmm, not what I expected... ubuntu@ubuntu:~$ uname -a Linux ubuntu 5.3.0-1008-raspi2 #9-Ubuntu SMP Fri Oct 18 13:26:35 UTC 2019 aarch64 aarch64 aarch64 GNU/Linux total_mem=3072 still fixes it **

[Bug 1848703] Re: Raspberry Pi 4 - USB Bus not detecting any devices

2019-10-29 Thread Mark Dunn
*** This bug is a duplicate of bug 1848790 *** https://bugs.launchpad.net/bugs/1848790 Sorry, my mistake I missed this: Ignoring old or unknown version 5.3.0-1008-raspi2 (latest is 5.3.0-1009-raspi2) /etc/kernel/postinst.d/zz-flash-kernel: I have proposed in my sources.list so it ignored

[Bug 1848703] Re: Raspberry Pi 4 - USB Bus not detecting any devices

2019-10-28 Thread Mark Dunn
*** This bug is a duplicate of bug 1848790 *** https://bugs.launchpad.net/bugs/1848790 I have a PI 4 (4GB) I loaded and installed the arm64 eoan USB didn't work, ssh did I set total_mem=1024 USB worked I set total_mem=3072 USB failed I set total_mem=1024 and loaded the linux image: wget

[Bug 1516014] Re: grub-probe fails with "no directory"

2015-11-23 Thread Mark Dunn
Checked with "grub-probe -v" today and got: grub-probe: info: /dev/sda is a parent of /dev/sda. grub-probe: info: opening hd0. grub-probe: info: drive = 0. grub-probe: info: the size of hd0 is 125045424. grub-probe: error: unknown filesystem. Changed type from ext4 to ext2 and grub-update works

[Bug 1516014] Re: grub-probe fails with "no directory"

2015-11-13 Thread Mark Dunn
I can run apport-collect, but it won't go through the proxy (I already tried http_proxy and https_proxy). Is there a way of doing this offline and then sending the report manually? ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because

[Bug 1516014] [NEW] grub-probe fails with "no directory"

2015-11-13 Thread Mark Dunn
Public bug reported: 1) Description:Ubuntu 14.04.3 LTS Release:14.04 2) grub2 2.02~beta2-9ubuntu1.4 linux-image-3.13.0-68-generic3.13.0-68.111 linux-image-extra-3.13.0-68-generic 3.13.0-68.111

[Bug 1448254] Re: openvswitch systemd unit file ordering wrong

2015-08-25 Thread Mark Dunn
Sorry, lost track of the bug as it fell into 100 papercuts... if it helps I solved my ordering problem by modifying the /lib/systemd/sysytem/openvswitch-nonetwork.service as follows [Unit] Description=Open vSwitch Internal Unit PartOf=openvswitch-switch.service # Without

[Bug 1448254] Re: openvswitch systemd unit file ordering wrong

2015-08-25 Thread Mark Dunn
Sorry, lost track of the bug as it fell into 100 papercuts... if it helps I solved my ordering problem by modifying the /lib/systemd/sysytem/openvswitch-nonetwork.service as follows [Unit] Description=Open vSwitch Internal Unit PartOf=openvswitch-switch.service # Without

[Bug 1448254] Re: openvswitch systemd unit file ordering wrong

2015-07-01 Thread Mark Dunn
I have a the same problem. In systemd, there are two files openvswitch-nonetwork.service openvswitch-switch.service which are supposed to fix this problem I am testing OpenStack with VXLAN and require sudo ovs-vsctl add-br br-eth2 sudo ovs-vsctl set port br-eth2 tag=2001 sudo ovs-vsctl add-port

[Bug 1448254] Re: openvswitch systemd unit file ordering wrong

2015-07-01 Thread Mark Dunn
I have a the same problem. In systemd, there are two files openvswitch-nonetwork.service openvswitch-switch.service which are supposed to fix this problem I am testing OpenStack with VXLAN and require sudo ovs-vsctl add-br br-eth2 sudo ovs-vsctl set port br-eth2 tag=2001 sudo ovs-vsctl add-port