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

2020-06-11 Thread Ian Steiger
hello, are there any updates?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1850876

Title:
  CONFIG_DRM_V3D is disabled for linux-raspi2 of eoan

Status in linux-raspi2 package in Ubuntu:
  Fix Released
Status in linux-raspi2 source package in Eoan:
  Triaged

Bug description:
  We enabled DRM_VC4 in the linux-raspi2 of eoan, but disabled the
  DRM_V3D.

  In fact the DRM_V3D is crucial for graphical applications (such as
  ubuntu-desktop :) as it removes the graphical overhead from the cpu to
  the gpu, making the applications work much faster.

  Please refer to https://bugs.launchpad.net/ubuntu/+source/linux-
  raspi2/+bug/1848703/comments/32

  
  [Impact]
  Users reported that we should enable the DRM_V3D, then the GPU will
  be fully used when running "ubuntu-desktop"

  [Fix]
  Enable the DRM_V3D, the v3d.ko will be built

  [Test Case]
  Users already tested it, it worked well.
  
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/comments/36

  [Regression Risk]
  Low, I already did building test for arm64 and armhf, all passed.
  And uers already tested the kernel module, it worked as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


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

2020-06-12 Thread Ian Steiger
@Hui it doesn't work, the about screen in GNOME Settings lists llvmpipe
for graphics, uname -a returns the kernel is 5.4.0-1012-raspi. I will
try a new image and maybe then it will work.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1850876

Title:
  CONFIG_DRM_V3D is disabled for linux-raspi2 of eoan

Status in linux-raspi2 package in Ubuntu:
  Fix Released
Status in linux-raspi2 source package in Eoan:
  Triaged

Bug description:
  We enabled DRM_VC4 in the linux-raspi2 of eoan, but disabled the
  DRM_V3D.

  In fact the DRM_V3D is crucial for graphical applications (such as
  ubuntu-desktop :) as it removes the graphical overhead from the cpu to
  the gpu, making the applications work much faster.

  Please refer to https://bugs.launchpad.net/ubuntu/+source/linux-
  raspi2/+bug/1848703/comments/32

  
  [Impact]
  Users reported that we should enable the DRM_V3D, then the GPU will
  be fully used when running "ubuntu-desktop"

  [Fix]
  Enable the DRM_V3D, the v3d.ko will be built

  [Test Case]
  Users already tested it, it worked well.
  
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/comments/36

  [Regression Risk]
  Low, I already did building test for arm64 and armhf, all passed.
  And uers already tested the kernel module, it worked as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


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

2020-06-12 Thread Ian Steiger
ok i tried on a new install with the proposed updates on, still no luck.
is there maybe a dtoverlay i need to enable?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1850876

Title:
  CONFIG_DRM_V3D is disabled for linux-raspi2 of eoan

Status in linux-raspi2 package in Ubuntu:
  Fix Released
Status in linux-raspi2 source package in Eoan:
  Triaged

Bug description:
  We enabled DRM_VC4 in the linux-raspi2 of eoan, but disabled the
  DRM_V3D.

  In fact the DRM_V3D is crucial for graphical applications (such as
  ubuntu-desktop :) as it removes the graphical overhead from the cpu to
  the gpu, making the applications work much faster.

  Please refer to https://bugs.launchpad.net/ubuntu/+source/linux-
  raspi2/+bug/1848703/comments/32

  
  [Impact]
  Users reported that we should enable the DRM_V3D, then the GPU will
  be fully used when running "ubuntu-desktop"

  [Fix]
  Enable the DRM_V3D, the v3d.ko will be built

  [Test Case]
  Users already tested it, it worked well.
  
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/comments/36

  [Regression Risk]
  Low, I already did building test for arm64 and armhf, all passed.
  And uers already tested the kernel module, it worked as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


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

2020-06-15 Thread Ian Steiger
ok i tested it. it is still using llvmpipe but i think i found the
relevant issue because the driver is there, i checked. issue:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1880125

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1850876

Title:
  CONFIG_DRM_V3D is disabled for linux-raspi2 of eoan

Status in linux-raspi2 package in Ubuntu:
  Fix Released
Status in linux-raspi2 source package in Eoan:
  Triaged

Bug description:
  We enabled DRM_VC4 in the linux-raspi2 of eoan, but disabled the
  DRM_V3D.

  In fact the DRM_V3D is crucial for graphical applications (such as
  ubuntu-desktop :) as it removes the graphical overhead from the cpu to
  the gpu, making the applications work much faster.

  Please refer to https://bugs.launchpad.net/ubuntu/+source/linux-
  raspi2/+bug/1848703/comments/32

  
  [Impact]
  Users reported that we should enable the DRM_V3D, then the GPU will
  be fully used when running "ubuntu-desktop"

  [Fix]
  Enable the DRM_V3D, the v3d.ko will be built

  [Test Case]
  Users already tested it, it worked well.
  
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/comments/36

  [Regression Risk]
  Low, I already did building test for arm64 and armhf, all passed.
  And uers already tested the kernel module, it worked as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


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

2020-06-15 Thread Ian Steiger
still using llvmpipe, if there is any debugging i could do just tell me

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1850876

Title:
  CONFIG_DRM_V3D is disabled for linux-raspi2 of eoan

Status in linux-raspi2 package in Ubuntu:
  Fix Released
Status in linux-raspi2 source package in Eoan:
  Triaged

Bug description:
  We enabled DRM_VC4 in the linux-raspi2 of eoan, but disabled the
  DRM_V3D.

  In fact the DRM_V3D is crucial for graphical applications (such as
  ubuntu-desktop :) as it removes the graphical overhead from the cpu to
  the gpu, making the applications work much faster.

  Please refer to https://bugs.launchpad.net/ubuntu/+source/linux-
  raspi2/+bug/1848703/comments/32

  
  [Impact]
  Users reported that we should enable the DRM_V3D, then the GPU will
  be fully used when running "ubuntu-desktop"

  [Fix]
  Enable the DRM_V3D, the v3d.ko will be built

  [Test Case]
  Users already tested it, it worked well.
  
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/comments/36

  [Regression Risk]
  Low, I already did building test for arm64 and armhf, all passed.
  And uers already tested the kernel module, it worked as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


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

2020-06-16 Thread Ian Steiger
ok after adding that line to the config.txt it works, but GNOME is
glitching with multiple windows open, thats another issue though.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1850876

Title:
  CONFIG_DRM_V3D is disabled for linux-raspi2 of eoan

Status in linux-raspi2 package in Ubuntu:
  Fix Released
Status in linux-raspi2 source package in Eoan:
  Triaged

Bug description:
  We enabled DRM_VC4 in the linux-raspi2 of eoan, but disabled the
  DRM_V3D.

  In fact the DRM_V3D is crucial for graphical applications (such as
  ubuntu-desktop :) as it removes the graphical overhead from the cpu to
  the gpu, making the applications work much faster.

  Please refer to https://bugs.launchpad.net/ubuntu/+source/linux-
  raspi2/+bug/1848703/comments/32

  
  [Impact]
  Users reported that we should enable the DRM_V3D, then the GPU will
  be fully used when running "ubuntu-desktop"

  [Fix]
  Enable the DRM_V3D, the v3d.ko will be built

  [Test Case]
  Users already tested it, it worked well.
  
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/comments/36

  [Regression Risk]
  Low, I already did building test for arm64 and armhf, all passed.
  And uers already tested the kernel module, it worked as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


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

2020-06-16 Thread Ian Steiger
i dont have an idea, all i did to check was glxinfo | grep renderer

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1850876

Title:
  CONFIG_DRM_V3D is disabled for linux-raspi2 of eoan

Status in linux-raspi2 package in Ubuntu:
  Fix Released
Status in linux-raspi2 source package in Eoan:
  Triaged

Bug description:
  We enabled DRM_VC4 in the linux-raspi2 of eoan, but disabled the
  DRM_V3D.

  In fact the DRM_V3D is crucial for graphical applications (such as
  ubuntu-desktop :) as it removes the graphical overhead from the cpu to
  the gpu, making the applications work much faster.

  Please refer to https://bugs.launchpad.net/ubuntu/+source/linux-
  raspi2/+bug/1848703/comments/32

  
  [Impact]
  Users reported that we should enable the DRM_V3D, then the GPU will
  be fully used when running "ubuntu-desktop"

  [Fix]
  Enable the DRM_V3D, the v3d.ko will be built

  [Test Case]
  Users already tested it, it worked well.
  
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/comments/36

  [Regression Risk]
  Low, I already did building test for arm64 and armhf, all passed.
  And uers already tested the kernel module, it worked as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


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

2020-06-16 Thread Ian Steiger
window glitching does not happen in XFCE, seems like a GNOME problem

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1850876

Title:
  CONFIG_DRM_V3D is disabled for linux-raspi2 of eoan

Status in linux-raspi2 package in Ubuntu:
  Fix Released
Status in linux-raspi2 source package in Eoan:
  Triaged

Bug description:
  We enabled DRM_VC4 in the linux-raspi2 of eoan, but disabled the
  DRM_V3D.

  In fact the DRM_V3D is crucial for graphical applications (such as
  ubuntu-desktop :) as it removes the graphical overhead from the cpu to
  the gpu, making the applications work much faster.

  Please refer to https://bugs.launchpad.net/ubuntu/+source/linux-
  raspi2/+bug/1848703/comments/32

  
  [Impact]
  Users reported that we should enable the DRM_V3D, then the GPU will
  be fully used when running "ubuntu-desktop"

  [Fix]
  Enable the DRM_V3D, the v3d.ko will be built

  [Test Case]
  Users already tested it, it worked well.
  
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/comments/36

  [Regression Risk]
  Low, I already did building test for arm64 and armhf, all passed.
  And uers already tested the kernel module, it worked as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1848790] Re: USB not working under arm64 on Pi4

2019-11-17 Thread Ian Steiger
updated my install, removed config.txt entry, available on stable

** Changed in: linux-raspi2 (Ubuntu Eoan)
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1848790

Title:
  USB not working under arm64 on Pi4

Status in linux-raspi2 package in Ubuntu:
  Confirmed
Status in linux-raspi2 source package in Eoan:
  Fix Released

Bug description:
  Ubuntu 19.10 arm64 on a Raspberry Pi 4 does not recognize a keyboard
  which works successfully on the same Raspberry Pi 4 with Ubuntu 19.10
  armhf. Both USB hubs (2 and 3) were tested, without the OS seeing the
  keyboard on either. Booting the arm64 image on a Raspberry Pi 3, the
  keyboard worked successfully.

  Output of lsusb under arm64 on a Pi 3:

  ubuntu@ubuntu:~$ lsusb
  Bus 001 Device 007: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard
  Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 
Fast Ethernet Adapter
  Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Output of lsusb under armhf on a Pi 4 (same keyboard attached):

  ubuntu@ubuntu:~$ lsusb
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard
  Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Output of lsusb under arm64 on the same Pi 4 (same keyboard attached):

  ubuntu@ubuntu:~$ lsusb
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  The fact even the VIA Labs hub doesn't show up (which is built in)
  suggests the kernel is (for some reason) unable to enumerate anything
  against the USB hubs.

  
  == Temporary Workaround ==

  As noted by various people below, the following line can be added to
  the "usercfg.txt" file on the boot partition:

  total_mem=3072

  This will limit the available RAM to 3Gb, but otherwise things should
  operate normally. Note that this bug does not affect Pi 4Bs with less
  than 4Gb of RAM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp