[Ubuntu-x-swat] [Bug 2049714] Re: [RPL-P] igt-gpu-tool enablement

2024-04-03 Thread Hector CAO
** Information type changed from Private to Public

** Changed in: intel
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-gpu-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2049714

Title:
  [RPL-P] igt-gpu-tool enablement

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/2049714/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 2049714] Re: [RPL-P] igt-gpu-tool enablement

2024-04-03 Thread Hector CAO
** Changed in: intel-gpu-tools (Ubuntu Noble)
   Status: New => In Progress

** Changed in: intel-gpu-tools (Ubuntu Noble)
 Assignee: (unassigned) => Hector CAO (hectorcao)

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-gpu-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2049714

Title:
  [RPL-P] igt-gpu-tool enablement

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/2049714/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 2049714] Re: [RPL-P] igt-gpu-tool enablement

2024-04-08 Thread Hector CAO
Hi @dongwonk, @chaoqin,

I uploaded a package for Ubuntu 24.04 with the fix at :
https://launchpad.net/~hectorcao/+archive/ubuntu/lp2049714

Could you please take a look and validate it on appropriate hardware ?

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-gpu-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2049714

Title:
  [RPL-P] igt-gpu-tool enablement

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/2049714/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 2049714] Re: [RPL-P] igt-gpu-tool enablement

2024-04-09 Thread Hector CAO
@dongwonk : i see that you are probably testing on jammy, that is the
wrong release, the package to be tested is for 24.04 (you can install it
with the daily build ISO).

regarding the networking problem, that is probably proxy problem, a
work-around is to download the debian package at
https://ppa.launchpadcontent.net/hectorcao/lp2049714/ubuntu/pool/main/i/intel-
gpu-tools/intel-gpu-tools_1.28-1ubuntu1_amd64.deb , and install it with
dpkg

let me know if you have any further question

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-gpu-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2049714

Title:
  [RPL-P] igt-gpu-tool enablement

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/2049714/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 2061324] [NEW] Error when re-building package from source

2024-04-14 Thread Hector CAO
Public bug reported:

When I try to build package from source in Ubuntu Jammy 22.04, i run
into this error:

```
int main(void) {
void *a = (void*) &memfd_create;
long long b = (long long) a;
return (int) b;
}
Compiler stdout:
 
Compiler stderr:
 
Checking for function "memfd_create" : YES 
Configuring config.h using configuration

../lib/meson.build:155:4: ERROR: Function does not take positional arguments.
dh_auto_configure: error: cd build && LC_ALL=C.UTF-8 meson .. 
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
--localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dtests=disabled returned 
exit code 1
make[1]: *** [debian/rules:19: override_dh_auto_configure] Error 255
make[1]: Leaving directory '/home/ubuntu/hector/intel-gpu-tools-1.26'
make: *** [debian/rules:39: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

```

The build command is : dpkg-buildpackage -us -uc -b
Ubuntu release : Jammy 22.04
Meson version : 0.61.2

** Affects: intel-gpu-tools (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-gpu-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2061324

Title:
  Error when re-building package from source

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/2061324/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 2061324] Re: Error when re-building package from source

2024-04-14 Thread Hector CAO
This problem has been fixed upstream:

963917a3565466832a3b2fc22e9285d34a0bf944

lib/meson.build: Fix underscorify call
f.underscorify() is correct, f.underscorify(f) is an error that later
meson versions don't like at all.

Closes: #107
Fixes: 588555f7

See : https://gitlab.freedesktop.org/drm/igt-gpu-
tools/-/commit/963917a3565466832a3b2fc22e9285d34a0bf944

I propose to backport this patch

** Changed in: intel-gpu-tools (Ubuntu)
   Status: New => In Progress

** Changed in: intel-gpu-tools (Ubuntu)
 Assignee: (unassigned) => Hector CAO (hectorcao)

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-gpu-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2061324

Title:
  Error when re-building package from source

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/2061324/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 2061324] Re: Error when re-building package from source

2024-04-14 Thread Hector CAO
The package with proposed fixed for Jammy can be found at:

https://launchpad.net/~hectorcao/+archive/ubuntu/lp2061324

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-gpu-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2061324

Title:
  Error when re-building package from source

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/2061324/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.

2024-04-14 Thread Hector CAO
I was able to reproduce this problen on 22.04

** Changed in: intel-gpu-tools (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-gpu-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1949314

Title:
  intel_gpu_top crashes with intel_gpu_top:
  ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion
  `max_len > 0' failed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 2061324] Re: Error when re-building package from source

2024-04-14 Thread Hector CAO
here is the debdiff of the fix

** Attachment added: "intel-gpu-tools_1.26-2_1.26-2ubuntu1.diff.gz"
   
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/2061324/+attachment/5765373/+files/intel-gpu-tools_1.26-2_1.26-2ubuntu1.diff.gz

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-gpu-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2061324

Title:
  Error when re-building package from source

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/2061324/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.

2024-04-14 Thread Hector CAO
** Changed in: intel-gpu-tools (Ubuntu)
 Assignee: (unassigned) => Hector CAO (hectorcao)

** Changed in: intel-gpu-tools (Ubuntu)
   Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-gpu-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1949314

Title:
  intel_gpu_top crashes with intel_gpu_top:
  ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion
  `max_len > 0' failed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.

2024-04-14 Thread Hector CAO
Here is the debdiff for the proposed fix

** Attachment added: "intel-gpu-tools_1.26-2_1.26-2ubuntu1.diff.gz"
   
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+attachment/5765384/+files/intel-gpu-tools_1.26-2_1.26-2ubuntu1.diff.gz

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-gpu-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1949314

Title:
  intel_gpu_top crashes with intel_gpu_top:
  ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion
  `max_len > 0' failed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1852916] Re: GPU problem, screen flikers a lot on start and log off. Unable to see anything black out.

2024-04-14 Thread Hector CAO
@punisher01 : I think this bug has been reported for the wrong
component,

** Changed in: intel-gpu-tools (Ubuntu)
   Status: New => Invalid

** Changed in: intel-gpu-tools (Ubuntu)
 Assignee: (unassigned) => Hector CAO (hectorcao)

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-gpu-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1852916

Title:
  GPU problem, screen flikers a lot on start and log off. Unable to see
  anything black out.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1852916/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 2061324] Re: Error when re-building package from source

2024-04-15 Thread Hector CAO
** Description changed:

- When I try to build package from source in Ubuntu Jammy 22.04, i run
- into this error:
+ [ Impact ]
+ 
+  Impossible to build the package from source on Ubuntu 22.04, users will get 
+  this error:
  
  ```
  int main(void) {
- void *a = (void*) &memfd_create;
- long long b = (long long) a;
- return (int) b;
- }
+ void *a = (void*) &memfd_create;
+ long long b = (long long) a;
+ return (int) b;
+ }
  Compiler stdout:
-  
+ 
  Compiler stderr:
-  
- Checking for function "memfd_create" : YES 
+ 
+ Checking for function "memfd_create" : YES
  Configuring config.h using configuration
  
  ../lib/meson.build:155:4: ERROR: Function does not take positional arguments.
  dh_auto_configure: error: cd build && LC_ALL=C.UTF-8 meson .. 
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
--localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dtests=disabled returned 
exit code 1
  make[1]: *** [debian/rules:19: override_dh_auto_configure] Error 255
  make[1]: Leaving directory '/home/ubuntu/hector/intel-gpu-tools-1.26'
  make: *** [debian/rules:39: build] Error 2
  dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
  
  ```
  
- The build command is : dpkg-buildpackage -us -uc -b
- Ubuntu release : Jammy 22.04
- Meson version : 0.61.2
+  The problem comes from the bad call to meson function underscorify in 
+  lib/meson.build
+ 
+  This problem has been fixed upstream:
+ 
+  963917a3565466832a3b2fc22e9285d34a0bf944
+  lib/meson.build: Fix underscorify call
+  f.underscorify() is correct, f.underscorify(f) is an error that later
+  meson versions don't like at all.
+  
+  The proposed fix for Ubuntu consists of backporting this patch.
+ 
+ [ Test Plan ]
+ 
+  Build the package from source on Ubuntu 22.04
+  
+  The build command is : dpkg-buildpackage -us -uc -b
+  Ubuntu release : Jammy 22.04
+  Meson version : 0.61.2
+ 
+ [ Where problems could occur ]
+ 
+  The problem occurs only at build process
+ 
+ [ Other Info ]
+  
+  This issue only happens at build and has been fixed upstream.
+  It is safe to have it in SRU

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-gpu-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2061324

Title:
  Error when re-building package from source

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/2061324/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.

2024-04-15 Thread Hector CAO
** Description changed:

+ [ Impact ]
+ 
+ When resizing the terminal window, intel_gpu_top may crash if the window 
+ becomes small enough. The output when it crashes is:
+ 
+ intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion 
+ `max_len > 0' failed.
+ 
+ 
+ The proposed fix consists of removing the assert() function and only skip 
drawing.
+ 
+ [ Test Plan ]
+ 
+ Run intel_gpu_top inside a console
+ Resize the console with the mouse to it smallest size
+ 
+ [ Where problems could occur ]
+ 
+ The problem occurs when intel_gpu_top try to draw information on the
+ console
+ 
+ [ Other Info ]
+ 
+ This fix should not cause regression on any other feature.
+ 
+ 
+ 
  When resizing the terminal window, intel_gpu_top may crash if the window
  become small enough. The output when it crashes is:
  
  intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion 
`max_len > 0' failed.
  Abortado
  
  I was able to reproduce this crash with tilix and xterm.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: intel-gpu-tools 1.26-2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu72
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Sun Oct 31 21:06:01 2021
  InstallationDate: Installed on 2017-06-13 (1601 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: intel-gpu-tools
  UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago)
  modified.conffile..etc.cron.daily.apport: [deleted]

** Changed in: intel-gpu-tools (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: intel-gpu-tools (Ubuntu Jammy)
     Assignee: (unassigned) => Hector CAO (hectorcao)

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-gpu-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1949314

Title:
  intel_gpu_top crashes with intel_gpu_top:
  ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion
  `max_len > 0' failed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.

2024-04-15 Thread Hector CAO
** Description changed:

  [ Impact ]
  
- When resizing the terminal window, intel_gpu_top may crash if the window 
+ When resizing the terminal window, intel_gpu_top may crash if the window
  becomes small enough. The output when it crashes is:
  
- intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion 
+ intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion
  `max_len > 0' failed.
  
+ The fix has been reported and fixed upstream recently :
+ https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143
  
- The proposed fix consists of removing the assert() function and only skip 
drawing.
+ The proposed fix consists of backporting this fix to affected ubuntu
+ releases : Jammy, Mantic and Noble
  
  [ Test Plan ]
  
  Run intel_gpu_top inside a console
  Resize the console with the mouse to it smallest size
  
  [ Where problems could occur ]
  
  The problem occurs when intel_gpu_top try to draw information on the
  console
  
  [ Other Info ]
  
  This fix should not cause regression on any other feature.
  
  
  
  When resizing the terminal window, intel_gpu_top may crash if the window
  become small enough. The output when it crashes is:
  
  intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion 
`max_len > 0' failed.
  Abortado
  
  I was able to reproduce this crash with tilix and xterm.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: intel-gpu-tools 1.26-2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu72
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Sun Oct 31 21:06:01 2021
  InstallationDate: Installed on 2017-06-13 (1601 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: intel-gpu-tools
  UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago)
  modified.conffile..etc.cron.daily.apport: [deleted]

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-gpu-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1949314

Title:
  intel_gpu_top crashes with intel_gpu_top:
  ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion
  `max_len > 0' failed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.

2024-04-15 Thread Hector CAO
** Description changed:

  [ Impact ]
  
  When resizing the terminal window, intel_gpu_top may crash if the window
  becomes small enough. The output when it crashes is:
  
  intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion
  `max_len > 0' failed.
  
  The fix has been reported and fixed upstream recently :
  https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143
  
- The proposed fix consists of backporting this fix to affected ubuntu
+ The fix has been part of a serie of fixes that improve intel_gpu_top UI
+ behavior for some corner cases :
+ https://patchwork.freedesktop.org/series/124890/
+ 
+ The proposed fix consists of backporting these fixes to affected Ubuntu
  releases : Jammy, Mantic and Noble
  
  [ Test Plan ]
  
  Run intel_gpu_top inside a console
  Resize the console with the mouse to it smallest size
  
  [ Where problems could occur ]
  
  The problem occurs when intel_gpu_top try to draw information on the
  console
  
  [ Other Info ]
  
  This fix should not cause regression on any other feature.
  
  
  
  When resizing the terminal window, intel_gpu_top may crash if the window
  become small enough. The output when it crashes is:
  
  intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion 
`max_len > 0' failed.
  Abortado
  
  I was able to reproduce this crash with tilix and xterm.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: intel-gpu-tools 1.26-2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu72
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Sun Oct 31 21:06:01 2021
  InstallationDate: Installed on 2017-06-13 (1601 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: intel-gpu-tools
  UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago)
  modified.conffile..etc.cron.daily.apport: [deleted]

** Description changed:

  [ Impact ]
  
  When resizing the terminal window, intel_gpu_top may crash if the window
  becomes small enough. The output when it crashes is:
  
  intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion
  `max_len > 0' failed.
  
  The fix has been reported and fixed upstream recently :
  https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143
  
  The fix has been part of a serie of fixes that improve intel_gpu_top UI
  behavior for some corner cases :
  https://patchwork.freedesktop.org/series/124890/
  
  The proposed fix consists of backporting these fixes to affected Ubuntu
- releases : Jammy, Mantic and Noble
+ releases (Jammy, Mantic and Noble)
+ 
+ Tvrtko Ursulin (4):
+   tools/intel_gpu_top: Fix clients header width when no clients
+   tools/intel_gpu_top: Fix client layout on first sample period
+   tools/intel_gpu_top: Optimise interactive display a bit
+   tools/intel_gpu_top: Handle narrow terminals more gracefully
  
  [ Test Plan ]
  
  Run intel_gpu_top inside a console
  Resize the console with the mouse to it smallest size
  
  [ Where problems could occur ]
  
  The problem occurs when intel_gpu_top try to draw information on the
  console
  
  [ Other Info ]
  
  This fix should not cause regression on any other feature.
  
  
  
  When resizing the terminal window, intel_gpu_top may crash if the window
  become small enough. The output when it crashes is:
  
  intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion 
`max_len > 0' failed.
  Abortado
  
  I was able to reproduce this crash with tilix and xterm.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: intel-gpu-tools 1.26-2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu72
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Sun Oct 31 21:06:01 2021
  InstallationDate: Installed on 2017-06-13 (1601 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: intel-gpu-tools
  UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago)
  modified.conffile..etc.cron.daily.apport: [deleted]

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-gpu-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1949314

Title:
  intel_gpu_top crashes with intel_gpu_top:
  ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion
  `max_len > 0' failed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.

2024-04-15 Thread Hector CAO
The fixed is available for Noble at :
https://launchpad.net/~hectorcao/+archive/ubuntu/lp-1949314

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-gpu-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1949314

Title:
  intel_gpu_top crashes with intel_gpu_top:
  ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion
  `max_len > 0' failed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.

2024-04-15 Thread Hector CAO
debdiff for Noble

** Attachment added: "intel-gpu-tools_1.28-1build2_1.28-1ubuntu0.1.diff.gz"
   
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+attachment/5765600/+files/intel-gpu-tools_1.28-1build2_1.28-1ubuntu0.1.diff.gz

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-gpu-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1949314

Title:
  intel_gpu_top crashes with intel_gpu_top:
  ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion
  `max_len > 0' failed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 2049714] Re: [RPL-P] igt-gpu-tool enablement

2024-04-15 Thread Hector CAO
** Changed in: intel-gpu-tools (Ubuntu Noble)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-gpu-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2049714

Title:
  [RPL-P] igt-gpu-tool enablement

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/2049714/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.

2024-04-15 Thread Hector CAO
debdiff for noble

** Attachment removed: "intel-gpu-tools_1.28-1build2_1.28-1ubuntu0.1.diff.gz"
   
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+attachment/5765600/+files/intel-gpu-tools_1.28-1build2_1.28-1ubuntu0.1.diff.gz

** Attachment added: "intel-gpu-tools_1.28-1ubuntu0.1_1.28-1ubuntu2.diff.gz"
   
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+attachment/5765627/+files/intel-gpu-tools_1.28-1ubuntu0.1_1.28-1ubuntu2.diff.gz

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-gpu-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1949314

Title:
  intel_gpu_top crashes with intel_gpu_top:
  ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion
  `max_len > 0' failed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.

2024-04-15 Thread Hector CAO
** Changed in: intel-gpu-tools (Ubuntu Mantic)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-gpu-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1949314

Title:
  intel_gpu_top crashes with intel_gpu_top:
  ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion
  `max_len > 0' failed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.

2024-04-15 Thread Hector CAO
** Changed in: intel-gpu-tools (Ubuntu Mantic)
 Assignee: (unassigned) => Hector CAO (hectorcao)

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-gpu-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1949314

Title:
  intel_gpu_top crashes with intel_gpu_top:
  ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion
  `max_len > 0' failed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 2061324] Re: Error when re-building package from source

2024-04-16 Thread Hector CAO
build fix is usually not accepted in SRU, this fix will be part of
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314

** Changed in: intel-gpu-tools (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: intel-gpu-tools (Ubuntu Jammy)
 Assignee: (unassigned) => Hector CAO (hectorcao)

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-gpu-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2061324

Title:
  Error when re-building package from source

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/2061324/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.

2024-04-16 Thread Hector CAO
** Description changed:

  [ Impact ]
  
  When resizing the terminal window, intel_gpu_top may crash if the window
  becomes small enough. The output when it crashes is:
  
  intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion
  `max_len > 0' failed.
  
  The fix has been reported and fixed upstream recently :
  https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143
  
  The fix has been part of a serie of fixes that improve intel_gpu_top UI
  behavior for some corner cases :
  https://patchwork.freedesktop.org/series/124890/
  
  The proposed fix consists of backporting these fixes to affected Ubuntu
  releases (Jammy, Mantic and Noble)
  
  Tvrtko Ursulin (4):
-   tools/intel_gpu_top: Fix clients header width when no clients
-   tools/intel_gpu_top: Fix client layout on first sample period
-   tools/intel_gpu_top: Optimise interactive display a bit
-   tools/intel_gpu_top: Handle narrow terminals more gracefully
+   tools/intel_gpu_top: Fix clients header width when no clients
+   tools/intel_gpu_top: Fix client layout on first sample period
+   tools/intel_gpu_top: Optimise interactive display a bit
+   tools/intel_gpu_top: Handle narrow terminals more gracefully
+ 
+ NOTES:
+ For Noble, all the 4 patches will be backported
+ For Mantic, Jammy, only "tools/intel_gpu_top: Handle narrow terminals more 
gracefully" will be backported because the others are not applicable to 
Jammy/Mantic (related to refactoring that happened after Mantic release)
  
  [ Test Plan ]
  
  Run intel_gpu_top inside a console
  Resize the console with the mouse to it smallest size
  
  [ Where problems could occur ]
  
  The problem occurs when intel_gpu_top try to draw information on the
  console
  
  [ Other Info ]
  
  This fix should not cause regression on any other feature.
  
  
  
  When resizing the terminal window, intel_gpu_top may crash if the window
  become small enough. The output when it crashes is:
  
  intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion 
`max_len > 0' failed.
  Abortado
  
  I was able to reproduce this crash with tilix and xterm.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: intel-gpu-tools 1.26-2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu72
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Sun Oct 31 21:06:01 2021
  InstallationDate: Installed on 2017-06-13 (1601 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: intel-gpu-tools
  UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago)
  modified.conffile..etc.cron.daily.apport: [deleted]

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-gpu-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1949314

Title:
  intel_gpu_top crashes with intel_gpu_top:
  ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion
  `max_len > 0' failed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 2004237] Re: Intel Raptor Lake-P support for intel-media-driver in jammy

2023-04-06 Thread Hector CAO
I did the test on a Raptorlake laptop

ubuntu@ubuntu-Latitude-7440:~$ inxi -G -display
Graphics:
  Device-1: Intel vendor: Dell driver: i915 v: kernel ports: active: eDP-1
empty: DP-1,DP-2,HDMI-A-1 bus-ID: :00:02.0 chip-ID: 8086:a7a0
class-ID: 0300
  Display: server: X.org v: 1.21.1.3 with: Xwayland v: 22.1.1
compositor: gnome-shell v: 42.5 driver: X: loaded: modesetting
unloaded: fbdev,vesa gpu: i915 tty: 207x115
  Monitor-1: eDP-1 model: AU Optronics built: 2022 res: 2560x1600 dpi: 216
gamma: 1.2 size: 301x188mm (11.9x7.4") diag: 355mm (14") ratio: 16:10
modes: 2560x1600
  Message: GL data unavailable in console. Try -G --display
Network:
  Device-1: Intel driver: iwlwifi v: kernel port: N/A bus-ID: :00:14.3
chip-ID: 8086:51f1 class-ID: 0280
  IF: wlp0s20f3 state: up mac: 14:75:5b:5c:6d:4a
  IP v4: 10.102.137.20/22 type: dynamic noprefixroute scope: global
broadcast: 10.102.139.255
  IP v6: fe80::9670:b220:3998:9dcf/64 type: noprefixroute scope: link
  Device-2: Realtek RTL8153 Gigabit Ethernet Adapter type: USB driver: r8152
bus-ID: 3-3:5 chip-ID: 0bda:8153 class-ID:  serial: 01
  IF: enx00e04c6805c6 state: up speed: 1000 Mbps duplex: full
mac: 00:e0:4c:68:05:c6
  IP v4: 10.102.154.191/22 type: dynamic noprefixroute scope: global
broadcast: 10.102.155.255
  IP v6: fe80::dc0b:18f2:2f69:6823/64 type: noprefixroute scope: link
  WAN IP: 211.75.139.217
Drives:
  Local Storage: total: 1.86 TiB used: 14.04 GiB (0.7%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 model: 2400A NVMe Micron 2048GB
size: 1.86 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
lanes: 4 type: SSD serial: 22293B04CD0D rev: 24000800 temp: 26.9 C
scheme: GPT
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 1.86 TiB size: 1.83 TiB (98.37%) used: 14.03 GiB (0.8%)
fs: ext4 dev: /dev/nvme0n1p3 maj-min: 259:3 label: UBUNTU
  ID-2: /boot/efi raw-size: 238.4 MiB size: 238.1 MiB (99.89%)
used: 6.1 MiB (2.5%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1 label: N/A
Sensors:
  System Temperatures: cpu: 26.0 C mobo: N/A
  Fan Speeds (RPM): N/A
ubuntu@ubuntu-Latitude-7440:~$ 

Try vainfo:

ubuntu@ubuntu-Latitude-7440:~$ vainfo
libva info: VA-API version 1.14.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_14
libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
libva info: va_openDriver() returns 1
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_10
libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit

Next step, i install only intel-media-driver from
https://ppa.launchpadcontent.net/tjaalton/ppa/ubuntu:

ubuntu@ubuntu-Latitude-7440:~$ apt policy libigdgmm12
libigdgmm12:
  Installed: 22.1.2+ds1-1
  Candidate: 22.1.2+ds1-1ubuntu0.1~ppa1
  Version table:
 22.1.2+ds1-1ubuntu0.1~ppa1 500
500 https://ppa.launchpadcontent.net/tjaalton/ppa/ubuntu jammy/main 
amd64 Packages
 *** 22.1.2+ds1-1 500
500 http://tw.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
100 /var/lib/dpkg/status


ubuntu@ubuntu-Latitude-7440:~$ apt policy intel-media-va-driver
intel-media-va-driver:
  Installed: 22.3.1+dfsg1-1ubuntu0.1~ppa1
  Candidate: 22.3.1+dfsg1-1ubuntu1
  Version table:
 22.3.1+dfsg1-1ubuntu1 500
500 http://tw.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 
Packages
 *** 22.3.1+dfsg1-1ubuntu0.1~ppa1 500
500 https://ppa.launchpadcontent.net/tjaalton/ppa/ubuntu jammy/main 
amd64 Packages
100 /var/lib/dpkg/status
 22.3.1+dfsg1-1 500
500 http://tw.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages

Now vainfo works !

ubuntu@ubuntu-Latitude-7440:~$ vainfo
libva info: VA-API version 1.14.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_14
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.14 (libva 2.12.0)
vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 22.3.1 ()
vainfo: Supported profile and entrypoints
  VAProfileNone   : VAEntrypointVideoProc
  VAProfileNone   : VAEntrypointStats
  VAProfileMPEG2Simple: VAEntrypointVLD
  VAProfileMPEG2Main  : VAEntrypointVLD
  VAProfileH264Main   : VAEntrypointVLD
  VAProfileH264Main   : VAEntrypointEncSliceLP
  VAProfileH264High   : VAEntrypointVLD
  VAProfileH264High   : VAEntrypointEncSliceLP
  VAProfileJPEGBaseline   : VAEntrypointVLD
  VAProfileJPEGBaseline   : VAEntrypointEncPicture
  VAProfileH264ConstrainedBas

[Ubuntu-x-swat] [Bug 2004237] Re: Intel Raptor Lake-P support for intel-media-driver in jammy

2023-04-18 Thread Hector CAO
@tjaalton : i did not need it to make things work, i might miss anything
?

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-media-driver in Ubuntu.
https://bugs.launchpad.net/bugs/2004237

Title:
  Intel Raptor Lake-P support for intel-media-driver in jammy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-gmmlib/+bug/2004237/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 2004237] Re: Intel Raptor Lake-P support for intel-media-driver in jammy

2023-04-24 Thread Hector CAO
bug fixed on Jammy with intel-media-va-driver-non-free package in
proposed,

ubuntu@ubuntu-Latitude-7440:~$ sudo apt policy intel-media-va-driver-non-free
intel-media-va-driver-non-free:
  Installed: 22.3.1+ds1-1ubuntu0.1
  Candidate: 22.3.1+ds1-1ubuntu0.1
  Version table:
 *** 22.3.1+ds1-1ubuntu0.1 500
500 http://archive.ubuntu.com/ubuntu jammy-proposed/multiverse amd64 
Packages
100 /var/lib/dpkg/status
 22.3.1+ds1-1 500
500 http://tw.archive.ubuntu.com/ubuntu jammy/multiverse amd64 Packages


ubuntu@ubuntu-Latitude-7440:~$ vainfo
libva info: VA-API version 1.14.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_14
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.14 (libva 2.12.0)
vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 22.3.1 ()
vainfo: Supported profile and entrypoints
  VAProfileNone   : VAEntrypointVideoProc
  VAProfileNone   : VAEntrypointStats
  VAProfileMPEG2Simple: VAEntrypointVLD
  VAProfileMPEG2Simple: VAEntrypointEncSlice
  VAProfileMPEG2Main  : VAEntrypointVLD
  VAProfileMPEG2Main  : VAEntrypointEncSlice
  VAProfileH264Main   : VAEntrypointVLD
  VAProfileH264Main   : VAEntrypointEncSlice
  VAProfileH264Main   : VAEntrypointFEI
  VAProfileH264Main   : VAEntrypointEncSliceLP
  VAProfileH264High   : VAEntrypointVLD
  VAProfileH264High   : VAEntrypointEncSlice
  VAProfileH264High   : VAEntrypointFEI
  VAProfileH264High   : VAEntrypointEncSliceLP
  VAProfileVC1Simple  : VAEntrypointVLD
  VAProfileVC1Main: VAEntrypointVLD
  VAProfileVC1Advanced: VAEntrypointVLD
  VAProfileJPEGBaseline   : VAEntrypointVLD
  VAProfileJPEGBaseline   : VAEntrypointEncPicture
  VAProfileH264ConstrainedBaseline: VAEntrypointVLD
  VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
  VAProfileH264ConstrainedBaseline: VAEntrypointFEI
  VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP
  VAProfileVP8Version0_3  : VAEntrypointVLD
  VAProfileHEVCMain   : VAEntrypointVLD
  VAProfileHEVCMain   : VAEntrypointEncSlice
  VAProfileHEVCMain   : VAEntrypointFEI
  VAProfileHEVCMain   : VAEntrypointEncSliceLP
  VAProfileHEVCMain10 : VAEntrypointVLD
  VAProfileHEVCMain10 : VAEntrypointEncSlice
  VAProfileHEVCMain10 : VAEntrypointEncSliceLP
  VAProfileVP9Profile0: VAEntrypointVLD
  VAProfileVP9Profile0: VAEntrypointEncSliceLP
  VAProfileVP9Profile1: VAEntrypointVLD
  VAProfileVP9Profile1: VAEntrypointEncSliceLP
  VAProfileVP9Profile2: VAEntrypointVLD
  VAProfileVP9Profile2: VAEntrypointEncSliceLP
  VAProfileVP9Profile3: VAEntrypointVLD
  VAProfileVP9Profile3: VAEntrypointEncSliceLP
  VAProfileHEVCMain12 : VAEntrypointVLD
  VAProfileHEVCMain12 : VAEntrypointEncSlice
  VAProfileHEVCMain422_10 : VAEntrypointVLD
  VAProfileHEVCMain422_10 : VAEntrypointEncSlice
  VAProfileHEVCMain422_12 : VAEntrypointVLD
  VAProfileHEVCMain422_12 : VAEntrypointEncSlice
  VAProfileHEVCMain444: VAEntrypointVLD
  VAProfileHEVCMain444: VAEntrypointEncSliceLP
  VAProfileHEVCMain444_10 : VAEntrypointVLD
  VAProfileHEVCMain444_10 : VAEntrypointEncSliceLP
  VAProfileHEVCMain444_12 : VAEntrypointVLD
  VAProfileHEVCSccMain: VAEntrypointVLD
  VAProfileHEVCSccMain: VAEntrypointEncSliceLP
  VAProfileHEVCSccMain10  : VAEntrypointVLD
  VAProfileHEVCSccMain10  : VAEntrypointEncSliceLP
  VAProfileHEVCSccMain444 : VAEntrypointVLD
  VAProfileHEVCSccMain444 : VAEntrypointEncSliceLP
  VAProfileAV1Profile0: VAEntrypointVLD
  VAProfileHEVCSccMain444_10  : VAEntrypointVLD
  VAProfileHEVCSccMain444_10  : VAEntrypointEncSliceLP

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-media-driver in Ubuntu.
https://bugs.launchpad.net/bugs/2004237

Title:
  Intel Raptor Lake-P support for intel-media-driver in jammy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-media-driver/+bug/2004237/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : http

[Ubuntu-x-swat] [Bug 2004237] Re: Intel Raptor Lake-P support for intel-media-driver in jammy

2023-04-24 Thread Hector CAO
It also works for the free version of intel media driver

ubuntu@ubuntu-Latitude-7440:~$ sudo apt policy intel-media-va-driver
intel-media-va-driver:
  Installed: 22.3.1+dfsg1-1ubuntu2
  Candidate: 22.3.1+dfsg1-1ubuntu2
  Version table:
 *** 22.3.1+dfsg1-1ubuntu2 500
500 http://archive.ubuntu.com/ubuntu jammy-proposed/universe amd64 
Packages
100 /var/lib/dpkg/status
 22.3.1+dfsg1-1ubuntu1 500
500 http://tw.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 
Packages
 22.3.1+dfsg1-1 500
500 http://tw.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages


ubuntu@ubuntu-Latitude-7440:~$ vainfo
libva info: VA-API version 1.14.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_14
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.14 (libva 2.12.0)
vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 22.3.1 ()
vainfo: Supported profile and entrypoints
  VAProfileNone   : VAEntrypointVideoProc
  VAProfileNone   : VAEntrypointStats
  VAProfileMPEG2Simple: VAEntrypointVLD
  VAProfileMPEG2Main  : VAEntrypointVLD
  VAProfileH264Main   : VAEntrypointVLD
  VAProfileH264Main   : VAEntrypointEncSliceLP
  VAProfileH264High   : VAEntrypointVLD
  VAProfileH264High   : VAEntrypointEncSliceLP
  VAProfileJPEGBaseline   : VAEntrypointVLD
  VAProfileJPEGBaseline   : VAEntrypointEncPicture
  VAProfileH264ConstrainedBaseline: VAEntrypointVLD
  VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP
  VAProfileVP8Version0_3  : VAEntrypointVLD
  VAProfileHEVCMain   : VAEntrypointVLD
  VAProfileHEVCMain   : VAEntrypointEncSliceLP
  VAProfileHEVCMain10 : VAEntrypointVLD
  VAProfileHEVCMain10 : VAEntrypointEncSliceLP
  VAProfileVP9Profile0: VAEntrypointVLD
  VAProfileVP9Profile0: VAEntrypointEncSliceLP
  VAProfileVP9Profile1: VAEntrypointVLD
  VAProfileVP9Profile1: VAEntrypointEncSliceLP
  VAProfileVP9Profile2: VAEntrypointVLD
  VAProfileVP9Profile2: VAEntrypointEncSliceLP
  VAProfileVP9Profile3: VAEntrypointVLD
  VAProfileVP9Profile3: VAEntrypointEncSliceLP
  VAProfileHEVCMain12 : VAEntrypointVLD
  VAProfileHEVCMain422_10 : VAEntrypointVLD
  VAProfileHEVCMain422_12 : VAEntrypointVLD
  VAProfileHEVCMain444: VAEntrypointVLD
  VAProfileHEVCMain444: VAEntrypointEncSliceLP
  VAProfileHEVCMain444_10 : VAEntrypointVLD
  VAProfileHEVCMain444_10 : VAEntrypointEncSliceLP
  VAProfileHEVCMain444_12 : VAEntrypointVLD
  VAProfileHEVCSccMain: VAEntrypointVLD
  VAProfileHEVCSccMain: VAEntrypointEncSliceLP
  VAProfileHEVCSccMain10  : VAEntrypointVLD
  VAProfileHEVCSccMain10  : VAEntrypointEncSliceLP
  VAProfileHEVCSccMain444 : VAEntrypointVLD
  VAProfileHEVCSccMain444 : VAEntrypointEncSliceLP
  VAProfileAV1Profile0: VAEntrypointVLD
  VAProfileHEVCSccMain444_10  : VAEntrypointVLD
  VAProfileHEVCSccMain444_10  : VAEntrypointEncSliceLP

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-media-driver in Ubuntu.
https://bugs.launchpad.net/bugs/2004237

Title:
  Intel Raptor Lake-P support for intel-media-driver in jammy

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-media-driver/+bug/2004237/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 2116923] Re: [SRU] video hardware acceleration codec fails for Intel Arrow lake

2025-07-15 Thread Hector CAO
** Also affects: intel-media-driver (Ubuntu Noble)
   Importance: Undecided
   Status: New

** Changed in: intel-media-driver (Ubuntu Noble)
 Assignee: (unassigned) => Hector CAO (hectorcao)

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-media-driver in Ubuntu.
https://bugs.launchpad.net/bugs/2116923

Title:
  [SRU] video hardware acceleration codec fails for Intel Arrow lake

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-media-driver/+bug/2116923/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 2116923] Re: [SRU] video hardware acceleration codec fails for Intel Arrow lake

2025-07-15 Thread Hector CAO
The package has been uploaded to this PPA :
https://launchpad.net/~hectorcao/+archive/ubuntu/lp2116923

I tested the new package on an Arrowlake platform:

ffmpeg version 6.1.1-3ubuntu5 Copyright (c) 2000-2023 the FFmpeg developers
  built with gcc 13 (Ubuntu 13.2.0-23ubuntu3)
  configuration: --prefix=/usr --extra-version=3ubuntu5 --toolchain=hardened 
--libdir=/usr/lib/x86_64-linux-gnu --incdir=/usr/include/x86_64-linux-gnu 
--arch=amd64 --enable-gpl --disable-stripping --dis\
able-omx --enable-gnutls --enable-libaom --enable-libass --enable-libbs2b 
--enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libdav1d 
--enable-libflite --enable-libfontconfig --enable-libfree\
type --enable-libfribidi --enable-libglslang --enable-libgme --enable-libgsm 
--enable-libharfbuzz --enable-libmp3lame --enable-libmysofa 
--enable-libopenjpeg --enable-libopenmpt --enable-libopus --enabl\
e-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr 
--enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab 
--enable-libvorbis --enable-libvpx --enable-libwebp --e\
nable-libx265 --enable-libxml2 --enable-libxvid --enable-libzimg 
--enable-openal --enable-opencl --enable-opengl --disable-sndio --enable-libvpl 
--disable-libmfx --enable-libdc1394 --enable-libdrm --ena\
ble-libiec61883 --enable-chromaprint --enable-frei0r --enable-ladspa 
--enable-libbluray --enable-libjack --enable-libpulse --enable-librabbitmq 
--enable-librist --enable-libsrt --enable-libssh --enable-\
libsvtav1 --enable-libx264 --enable-libzmq --enable-libzvbi --enable-lv2 
--enable-sdl2 --enable-libplacebo --enable-librav1e --enable-pocketsphinx 
--enable-librsvg --enable-libjxl --enable-shared
  libavutil  58. 29.100 / 58. 29.100
  libavcodec 60. 31.102 / 60. 31.102
  libavformat60. 16.100 / 60. 16.100
  libavdevice60.  3.100 / 60.  3.100
  libavfilter 9. 12.100 /  9. 12.100
  libswscale  7.  5.100 /  7.  5.100
  libswresample   4. 12.100 /  4. 12.100
  libpostproc57.  3.100 / 57.  3.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'input.mp4':
...

[h264_vaapi @ 0x5609a7434bc0] No quality level set; using default (20).
Output #0, mp4, to 'output.mp4':
  Metadata:
major_brand : isom
minor_version   : 512
compatible_brands: isomiso2avc1mp41
encoder : Lavf60.16.100
  Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), vaapi(progressive), 
1280x720 [SAR 1:1 DAR 16:9], q=2-31, 25 fps, 12800 tbn (default)
Metadata:
  creation_time   : 1970-01-01T00:00:00.00Z
  handler_name: VideoHandler
  vendor_id   : [0][0][0][0]
  encoder : Lavc60.31.102 h264_vaapi
  Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, 5.1, fltp, 
341 kb/s (default)
Metadata:
  creation_time   : 1970-01-01T00:00:00.00Z
  handler_name: SoundHandler
  vendor_id   : [0][0][0][0]
  encoder : Lavc60.31.102 aac
frame=0 fps=0.0 q=0.0 size=   0kB time=00:00:00.55 bitrate=   
0.7kbits/s speed=16.1x^M[out#0/mp4 @ 0x5609a73ed540] video:1870kB 
audio:226kB subtitle:0kB other streams:0kB global headers:0kB \
muxing overhead: 0.239672%
frame=  132 fps=0.0 q=-0.0 Lsize=2101kB time=00:00:05.29 
bitrate=3252.5kbits/s speed=  20x
[aac @ 0x5609a836a000] Qavg: 1497.779

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-media-driver in Ubuntu.
https://bugs.launchpad.net/bugs/2116923

Title:
  [SRU] video hardware acceleration codec fails for Intel Arrow lake

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-media-driver/+bug/2116923/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 2116923] Re: [SRU] video hardware acceleration codec fails for Intel Arrow lake

2025-07-15 Thread Hector CAO
** Description changed:

  [ Impact ]
  
   * Users cannot use iGPU for video codec (encode/decode) on Intel Arrowlake 
CPUs
     on Ubuntu Noble 24.04
  
-  * To enable this support, we need to backport this commit 
-
https://github.com/intel/media-driver/commit/95cbfce81cafa3c24d9d4601d41a855093bc51fb
- 
-  * This commit has been added in the media driver 24.2.0, as a consequence, 
it 
-is already available starting from Plucky. This SRU only affects Ubuntu 
Noble 
-24.04.  
+  * To enable this support, we need to backport this commit
+    
https://github.com/intel/media-driver/commit/95cbfce81cafa3c24d9d4601d41a855093bc51fb
+ 
+  * This commit has been added in the intel-media-driver 24.2.0, as a 
+consequence, it is already available starting from Plucky. This SRU only 
+affects Ubuntu Noble 24.04 that has an older version (24.1.0).
  
  [ Test Plan ]
  
   * sudo apt install -y intel-media-va-driver ffmpeg vainfo
   * sudo vainfo
  
  error: XDG_RUNTIME_DIR is invalid or not set in the environment.
  error: can't connect to X server!
  libva info: VA-API version 1.22.0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
  libva info: Found init function __vaDriverInit_1_22
  libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
  libva info: va_openDriver() returns 1
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_20
  libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
  libva info: va_openDriver() returns -1
  vaInitialize failed with error code -1 (unknown libva error),exit
  
   * wget -O input.mp4 
https://www.sample-videos.com/video321/mp4/720/big_buck_bunny_720p_1mb.mp4
   * sudo ffmpeg -hwaccel vaapi -hwaccel_output_format vaapi -i input.mp4 -c:v 
h264_vaapi output.mp4
  
  ffmpeg version 6.1.1-3ubuntu5 Copyright (c) 2000-2023 the FFmpeg developers
    built with gcc 13 (Ubuntu 13.2.0-23ubuntu3)
  ...
  [AVHWDeviceContext @ 0x5eb7598e5e40] libva: 
/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
  [AVHWDeviceContext @ 0x5eb7598e5e40] libva: 
/usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
  [AVHWDeviceContext @ 0x5eb7598e5e40] Failed to initialise VAAPI connection: 
-1 (unknown libva error).
  Device creation failed: -5.
  No device available for decoder: device type vaapi needed for codec h264.
  [vist#0:0/h264 @ 0x5eb759938540] Hardware device setup failed for decoder: 
Input/output error
  [vost#0:0/h264_vaapi @ 0x5eb75993e880] Error initializing a simple filtergraph
  Error opening output file output.mp4.
  Error opening output files: Input/output error
  
  [ Where problems could occur ]
  
    * Since we backport only a commit that adds some device IDs, no
  agressions are expected
  
  [ Other Info ]

** Description changed:

  [ Impact ]
  
   * Users cannot use iGPU for video codec (encode/decode) on Intel Arrowlake 
CPUs
     on Ubuntu Noble 24.04
  
   * To enable this support, we need to backport this commit
     
https://github.com/intel/media-driver/commit/95cbfce81cafa3c24d9d4601d41a855093bc51fb
  
-  * This commit has been added in the intel-media-driver 24.2.0, as a 
-consequence, it is already available starting from Plucky. This SRU only 
-affects Ubuntu Noble 24.04 that has an older version (24.1.0).
+  * This commit has been added in the intel-media-driver 24.2.0, as a
+    consequence, it is already available starting from Plucky. This SRU only
+    affects Ubuntu Noble 24.04 that has an older version (24.1.0).
  
  [ Test Plan ]
  
   * sudo apt install -y intel-media-va-driver ffmpeg vainfo
   * sudo vainfo
  
  error: XDG_RUNTIME_DIR is invalid or not set in the environment.
  error: can't connect to X server!
  libva info: VA-API version 1.22.0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
  libva info: Found init function __vaDriverInit_1_22
  libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
  libva info: va_openDriver() returns 1
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_20
  libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
  libva info: va_openDriver() returns -1
  vaInitialize failed with error code -1 (unknown libva error),exit
  
   * wget -O input.mp4 
https://www.sample-videos.com/video321/mp4/720/big_buck_bunny_720p_1mb.mp4
   * sudo ffmpeg -hwaccel vaapi -hwaccel_output_format vaapi -i input.mp4 -c:v 
h264_vaapi output.mp4
  
  ffmpeg version 6.1.1-3ubuntu5 Copyright (c) 2000-2023 the FFmpeg developers
    built with gcc 13 (Ubuntu 13.2.0-23ubuntu3)
  ...
  [AVHWDeviceContext @ 0x5eb7598e5e40] libva: 
/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
  [AVHWDeviceContext @ 0x5eb7598e5e40] libva: 
/usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
  [AVHWDeviceContext @ 0x5eb7598e5e40] Fa

[Ubuntu-x-swat] [Bug 2098420] Re: [SRU] Bump media driver version to 24.4.4 in Oracular

2025-07-15 Thread Hector CAO
Oracular has reached EOL, this issue won't be fixed

** Changed in: intel-media-driver (Ubuntu)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-media-driver in Ubuntu.
https://bugs.launchpad.net/bugs/2098420

Title:
  [SRU] Bump media driver version to 24.4.4 in Oracular

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-media-driver/+bug/2098420/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 2116923] [NEW] [SRU] video hardware acceleration codec fails for Intel Arrow lake

2025-07-15 Thread Hector CAO
Public bug reported:

[ Impact ]

 * Users cannot use iGPU for video codec (encode/decode) on Intel Arrowlake CPUs
   on Ubuntu Noble 24.04

 * To enable this support, we need to backport this commit 
   
https://github.com/intel/media-driver/commit/95cbfce81cafa3c24d9d4601d41a855093bc51fb

 * This commit has been added in the media driver 24.2.0, as a consequence, it 
   is already available starting from Plucky. This SRU only affects Ubuntu 
Noble 
   24.04.  

[ Test Plan ]

 * sudo apt install -y intel-media-va-driver ffmpeg vainfo
 * sudo vainfo

error: XDG_RUNTIME_DIR is invalid or not set in the environment.
error: can't connect to X server!
libva info: VA-API version 1.22.0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_22
libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
libva info: va_openDriver() returns 1
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
libva info: Found init function __vaDriverInit_1_20
libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
libva info: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit

 * wget -O input.mp4 
https://www.sample-videos.com/video321/mp4/720/big_buck_bunny_720p_1mb.mp4
 * sudo ffmpeg -hwaccel vaapi -hwaccel_output_format vaapi -i input.mp4 -c:v 
h264_vaapi output.mp4

ffmpeg version 6.1.1-3ubuntu5 Copyright (c) 2000-2023 the FFmpeg developers
  built with gcc 13 (Ubuntu 13.2.0-23ubuntu3)
...
[AVHWDeviceContext @ 0x5eb7598e5e40] libva: 
/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
[AVHWDeviceContext @ 0x5eb7598e5e40] libva: 
/usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
[AVHWDeviceContext @ 0x5eb7598e5e40] Failed to initialise VAAPI connection: -1 
(unknown libva error).
Device creation failed: -5.
No device available for decoder: device type vaapi needed for codec h264.
[vist#0:0/h264 @ 0x5eb759938540] Hardware device setup failed for decoder: 
Input/output error
[vost#0:0/h264_vaapi @ 0x5eb75993e880] Error initializing a simple filtergraph
Error opening output file output.mp4.
Error opening output files: Input/output error

[ Where problems could occur ]

  * Since we backport only a commit that adds some device IDs, no
agressions are expected

[ Other Info ]

** Affects: intel-media-driver (Ubuntu)
 Importance: Undecided
 Assignee: Hector CAO (hectorcao)
 Status: New

** Changed in: intel-media-driver (Ubuntu)
 Assignee: (unassigned) => Hector CAO (hectorcao)

** Description changed:

  [ Impact ]
  
-  * Users cannot use iGPU for video codec (encode/decode) on Intel Arrowlake 
CPUs
-on Ubuntu Noble 24.04
+  * Users cannot use iGPU for video codec (encode/decode) on Intel Arrowlake 
CPUs
+    on Ubuntu Noble 24.04
+ 
+  * To enable this support, we need to backport this commit 
+
https://github.com/intel/media-driver/commit/95cbfce81cafa3c24d9d4601d41a855093bc51fb
+ 
+  * This commit has been added in the media driver 24.2.0, as a consequence, 
it 
+is already available starting from Plucky. This SRU only affects Ubuntu 
Noble 
+24.04.  
  
  [ Test Plan ]
  
-  * sudo apt install -y intel-media-va-driver ffmpeg vainfo
-  * sudo vainfo
+  * sudo apt install -y intel-media-va-driver ffmpeg vainfo
+  * sudo vainfo
  
  error: XDG_RUNTIME_DIR is invalid or not set in the environment.
  error: can't connect to X server!
  libva info: VA-API version 1.22.0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
  libva info: Found init function __vaDriverInit_1_22
  libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
  libva info: va_openDriver() returns 1
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_20
  libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
  libva info: va_openDriver() returns -1
  vaInitialize failed with error code -1 (unknown libva error),exit
  
-  * wget -O input.mp4 
https://www.sample-videos.com/video321/mp4/720/big_buck_bunny_720p_1mb.mp4
-  * sudo ffmpeg -hwaccel vaapi -hwaccel_output_format vaapi -i input.mp4 -c:v 
h264_vaapi output.mp4
+  * wget -O input.mp4 
https://www.sample-videos.com/video321/mp4/720/big_buck_bunny_720p_1mb.mp4
+  * sudo ffmpeg -hwaccel vaapi -hwaccel_output_format vaapi -i input.mp4 -c:v 
h264_vaapi output.mp4
  
  ffmpeg version 6.1.1-3ubuntu5 Copyright (c) 2000-2023 the FFmpeg developers
-   built with gcc 13 (Ubuntu 13.2.0-23ubuntu3)
+   built with gcc 13 (Ubuntu 13.2.0-23ubuntu3)
  ...
  [AVHWDeviceContext @ 0x5eb7598e5e40] libva: 
/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
  [AVHWDeviceContext @ 0x5eb7598e5e40] libva: 
/usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
  [AVHWDeviceContext @ 0x5eb7598e5e40] Failed to initialise VAAPI connection: 
-1 (unknow

[Ubuntu-x-swat] [Bug 2116923] Re: [SRU] video hardware acceleration codec fails for Intel Arrow lake

2025-07-22 Thread Hector CAO
** Changed in: intel-media-driver (Ubuntu)
   Status: New => Fix Committed

** Changed in: intel-media-driver (Ubuntu Noble)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-media-driver in Ubuntu.
https://bugs.launchpad.net/bugs/2116923

Title:
  [SRU] video hardware acceleration codec fails for Intel Arrow lake

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-media-driver/+bug/2116923/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 2116923] Re: [SRU] video hardware acceleration codec fails for Intel Arrow lake

2025-07-22 Thread Hector CAO
** Changed in: intel-media-driver (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-media-driver in Ubuntu.
https://bugs.launchpad.net/bugs/2116923

Title:
  [SRU] video hardware acceleration codec fails for Intel Arrow lake

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-media-driver/+bug/2116923/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 2116923] Re: [SRU] video hardware acceleration codec fails for Intel Arrow lake

2025-07-30 Thread Hector CAO
** Description changed:

  [ Impact ]
  
   * Users cannot use iGPU for video codec (encode/decode) on Intel Arrowlake 
CPUs
     on Ubuntu Noble 24.04
  
   * To enable this support, we need to backport this commit
     
https://github.com/intel/media-driver/commit/95cbfce81cafa3c24d9d4601d41a855093bc51fb
  
   * This commit has been added in the intel-media-driver 24.2.0, as a
     consequence, it is already available starting from Plucky. This SRU only
     affects Ubuntu Noble 24.04 that has an older version (24.1.0).
  
  [ Test Plan ]
  
   * sudo apt install -y intel-media-va-driver ffmpeg vainfo
-  * sudo vainfo
+ 
+  VAINFO
+  
+  
+  * vainfo
  
  error: XDG_RUNTIME_DIR is invalid or not set in the environment.
  error: can't connect to X server!
  libva info: VA-API version 1.22.0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
  libva info: Found init function __vaDriverInit_1_22
  libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
  libva info: va_openDriver() returns 1
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_20
  libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
  libva info: va_openDriver() returns -1
  vaInitialize failed with error code -1 (unknown libva error),exit
+ 
+ We can see that vainfo is unable to list all the supported profiles and 
endpoints.
+ A successful action has the output similar to below:
+ 
+ ubuntu@ubuntu:~$ sudo vainfo
+ error: XDG_RUNTIME_DIR is invalid or not set in the environment.
+ X11 connection rejected because of wrong authentication.
+ error: can't connect to X server!
+ libva info: VA-API version 1.22.0
+ libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
+ libva info: Found init function __vaDriverInit_1_20
+ libva info: va_openDriver() returns 0
+ vainfo: VA-API version: 1.22 (libva 2.12.0)
+ vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 24.1.0 ()
+ vainfo: Supported profile and entrypoints
+   VAProfileNone   :   VAEntrypointVideoProc
+   VAProfileMPEG2Simple:   VAEntrypointVLD
+   VAProfileMPEG2Main  :   VAEntrypointVLD
+   VAProfileH264Main   :   VAEntrypointVLD
+   VAProfileH264Main   :   VAEntrypointEncSlice
+   VAProfileH264High   :   VAEntrypointVLD
+   VAProfileH264High   :   VAEntrypointEncSlice
+   VAProfileJPEGBaseline   :   VAEntrypointVLD
+ ...
+ 
+ 
+ FFMPEG
+ 
+ 
+ We can use FFMPEG to test the hardware decoding/encode
+ On the platform without the fix, FFMPEG fails with the error message:
+ 
+ [vost#0:0/h264_vaapi @ 0x5eb75993e880] Error initializing a simple
+ filtergraph
+ 
+ Steps:
  
   * wget -O input.mp4 
https://www.sample-videos.com/video321/mp4/720/big_buck_bunny_720p_1mb.mp4
   * sudo ffmpeg -hwaccel vaapi -hwaccel_output_format vaapi -i input.mp4 -c:v 
h264_vaapi output.mp4
  
  ffmpeg version 6.1.1-3ubuntu5 Copyright (c) 2000-2023 the FFmpeg developers
    built with gcc 13 (Ubuntu 13.2.0-23ubuntu3)
  ...
  [AVHWDeviceContext @ 0x5eb7598e5e40] libva: 
/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
  [AVHWDeviceContext @ 0x5eb7598e5e40] libva: 
/usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
  [AVHWDeviceContext @ 0x5eb7598e5e40] Failed to initialise VAAPI connection: 
-1 (unknown libva error).
  Device creation failed: -5.
  No device available for decoder: device type vaapi needed for codec h264.
  [vist#0:0/h264 @ 0x5eb759938540] Hardware device setup failed for decoder: 
Input/output error
  [vost#0:0/h264_vaapi @ 0x5eb75993e880] Error initializing a simple filtergraph
  Error opening output file output.mp4.
  Error opening output files: Input/output error
  
+ 
  [ Where problems could occur ]
  
-   * Since we backport only a commit that adds some device IDs, the risk to 
have 
- regressions is small.
- However, since we enable the platform with media features by adding 
- the needed device IDs, it might exhibit bugs that are masked so far 
because
- the features are not enabled. 
+   * Since we backport only a commit that adds some device IDs, the risk to 
have
+ regressions is small.
+ However, since we enable the platform with media features by adding
+ the needed device IDs, it might enable some code paths and exhibit bugs 
that 
+ are masked without the fix.
+ One way to make sure we do not have big regression is to make sure we can 
+ playback a mp4 video (https://test-videos.co.uk/bigbuckbunny/mp4-h265)
+ 
  
  [ Other Info ]

** Description changed:

  [ Impact ]
  
   * Users cannot use iGPU for video codec (encode/decode) on Intel Arrowlake 
CPUs
     on Ubuntu Noble 24.04
  
   * To enable this support, we need to backport this commit
     
https://github.com/intel/media-driv

[Ubuntu-x-swat] [Bug 2116923] Re: [SRU] video hardware acceleration codec fails for Intel Arrow lake

2025-07-31 Thread Hector CAO
** Description changed:

  [ Impact ]
  
   * Users cannot use iGPU for video codec (encode/decode) on Intel Arrowlake 
CPUs
     on Ubuntu Noble 24.04
  
   * To enable this support, we need to backport this commit
     
https://github.com/intel/media-driver/commit/95cbfce81cafa3c24d9d4601d41a855093bc51fb
  
   * This commit has been added in the intel-media-driver 24.2.0, as a
     consequence, it is already available starting from Plucky. This SRU only
     affects Ubuntu Noble 24.04 that has an older version (24.1.0).
  
  [ Test Plan ]
  
   $ sudo apt install -y intel-media-va-driver ffmpeg vainfo
  
   VAINFO
   
  
   $ vainfo
  
  error: XDG_RUNTIME_DIR is invalid or not set in the environment.
  error: can't connect to X server!
  libva info: VA-API version 1.22.0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
  libva info: Found init function __vaDriverInit_1_22
  libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
  libva info: va_openDriver() returns 1
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_20
  libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
  libva info: va_openDriver() returns -1
  vaInitialize failed with error code -1 (unknown libva error),exit
  
  We can see that vainfo is unable to list all the supported profiles and 
endpoints.
  A successful action has the output similar to below:
  
  $ vainfo
  error: XDG_RUNTIME_DIR is invalid or not set in the environment.
  X11 connection rejected because of wrong authentication.
  error: can't connect to X server!
  libva info: VA-API version 1.22.0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
  libva info: Found init function __vaDriverInit_1_20
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 1.22 (libva 2.12.0)
  vainfo: Driver version: Intel iHD driver for Intel(R) Gen Graphics - 24.1.0 ()
  vainfo: Supported profile and entrypoints
    VAProfileNone   :   VAEntrypointVideoProc
    VAProfileMPEG2Simple:   VAEntrypointVLD
    VAProfileMPEG2Main  :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointVLD
    VAProfileH264Main   :   VAEntrypointEncSlice
    VAProfileH264High   :   VAEntrypointVLD
    VAProfileH264High   :   VAEntrypointEncSlice
    VAProfileJPEGBaseline   :   VAEntrypointVLD
  ...
  
  FFMPEG
  
  
  We can use FFMPEG to test the hardware decoding/encode
  On the platform without the fix, FFMPEG fails with the error message:
  
  [vost#0:0/h264_vaapi @ 0x5eb75993e880] Error initializing a simple
  filtergraph
  
  Steps:
  
   * wget -O input.mp4 
https://www.sample-videos.com/video321/mp4/720/big_buck_bunny_720p_1mb.mp4
-  * sudo ffmpeg -hwaccel vaapi -hwaccel_output_format vaapi -i input.mp4 -c:v 
h264_vaapi output.mp4
+  * ffmpeg -hwaccel vaapi -hwaccel_output_format vaapi -i input.mp4 -c:v 
h264_vaapi output.mp4
  
  ffmpeg version 6.1.1-3ubuntu5 Copyright (c) 2000-2023 the FFmpeg developers
    built with gcc 13 (Ubuntu 13.2.0-23ubuntu3)
  ...
  [AVHWDeviceContext @ 0x5eb7598e5e40] libva: 
/usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
  [AVHWDeviceContext @ 0x5eb7598e5e40] libva: 
/usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
  [AVHWDeviceContext @ 0x5eb7598e5e40] Failed to initialise VAAPI connection: 
-1 (unknown libva error).
  Device creation failed: -5.
  No device available for decoder: device type vaapi needed for codec h264.
  [vist#0:0/h264 @ 0x5eb759938540] Hardware device setup failed for decoder: 
Input/output error
  [vost#0:0/h264_vaapi @ 0x5eb75993e880] Error initializing a simple filtergraph
  Error opening output file output.mp4.
  Error opening output files: Input/output error
  
  [ Where problems could occur ]
  
    * Since we backport only a commit that adds some device IDs, the risk to 
have
  regressions is small.
  However, since we enable the platform with media features by adding
  the needed device IDs, it might enable some code paths and exhibit bugs 
that
  are masked without the fix.
  One way to make sure we do not have big regression is to make sure we can
  playback a mp4 video (https://test-videos.co.uk/bigbuckbunny/mp4-h265)
  
  [ Other Info ]

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-media-driver in Ubuntu.
https://bugs.launchpad.net/bugs/2116923

Title:
  [SRU] video hardware acceleration codec fails for Intel Arrow lake

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-media-driver/+bug/2116923/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launch

[Ubuntu-x-swat] [Bug 2116923] Re: [SRU] video hardware acceleration codec fails for Intel Arrow lake

2025-07-30 Thread Hector CAO
Thanks @raof

1) Indeed, this is not neccessary to run vainfo as root,
I had to use sudo because I was connected to the platform by SSH
Let me update the bug description accordingly

2) Yes, I will update the test plan to make the success case more
explicit

3) I agree, let me update the bug description

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-media-driver in Ubuntu.
https://bugs.launchpad.net/bugs/2116923

Title:
  [SRU] video hardware acceleration codec fails for Intel Arrow lake

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-media-driver/+bug/2116923/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 2116923] Re: [SRU] video hardware acceleration codec fails for Intel Arrow lake

2025-08-04 Thread Hector CAO
Hello Andreas

Thanks for having accepted and moved the package in -proposed.

I did the following successful verifications on an Arrowlake platform:

1) verifiy that video playback feature works well without any regressions
2) verify that we can take advantage of the hardware decode at video conversion 
with ffmpeg

1)

$ wget 
https://test-videos.co.uk/vids/bigbuckbunny/mp4/h265/1080/Big_Buck_Bunny_1080_10s_5MB.mp4
$ ffmlay Big_Buck_Bunny_1080_10s_5MB.mp4

I observed that the video playback works

2)

$ wget 
https://test-videos.co.uk/vids/bigbuckbunny/mp4/h265/1080/Big_Buck_Bunny_1080_10s_5MB.mp4
$ ffmpeg -hwaccel vaapi -hwaccel_output_format vaapi -i 
Big_Buck_Bunny_1080_10s_5MB.mp4 -c:v h264_vaapi output.mp4

with intel_gpu_top command, I observed that the iGPU video engine is
being used

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-media-driver in Ubuntu.
https://bugs.launchpad.net/bugs/2116923

Title:
  [SRU] video hardware acceleration codec fails for Intel Arrow lake

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-media-driver/+bug/2116923/+subscriptions


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp