[Kernel-packages] [Bug 2077795] [NEW] After a weekly update the nvidia-driver-545 that I used because it was the most reliable stopped working and reverted back to nouveau drivers that barely work

2024-08-24 Thread Hassan Williamson
Public bug reported:

Hi, Hope you are keeping well and sorry that I have to post this bug.

First I'll get the 4 questions listed here first, then add more info
afterwards:

1) lsb_release -rd 
Description:Ubuntu 22.04.4 LTS
Release:22.04

2) apt-cache policy nvidia-driver-535
nvidia-driver-535:
  Installed: 535.183.01-0ubuntu0.22.04.1
  Candidate: 535.183.01-0ubuntu0.22.04.1
  Version table:
 *** 535.183.01-0ubuntu0.22.04.1 500
500 http://gb.archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/restricted amd64 
Packages
100 /var/lib/dpkg/status

apt-cache policy nvidia-driver-545
nvidia-driver-545:
  Installed: (none)
  Candidate: 545.29.06-0ubuntu0.22.04.2
  Version table:
 545.29.06-0ubuntu0.22.04.2 500
500 http://gb.archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 
Packages

3) Expected the nvidia-driver-545 to remain installed that I had
previously, and work as normal after the weekly updates.

4) After the weekly updates, the kernel module compile for 545 failed
and reverted back to the nouveau driver which resulted in very red and
yellow toned screen on reboot. Then I had to fumble my way to get the
535 driver barely being able to see what I was typing on screen.

More info:

After a weekly update the nvidia-driver-545 that I used because it was
the most reliable stopped working and reverted back to nouveau drivers
that barely works at all.

When I try to install the 545 driver back, I get compile errors for the
kernel modules.

I know nvidia drivers are always hit or miss on Linux, so I'm not overly
surprised (its why I'm not on the latest).

However, the 535 driver (although works) has issues with rendering some
applications (and show up as a black square), or performance stutters
when watching videos or moving windows around the screen.

The other issues are that 3D rendering, video processing, AI, gaming and
a bunch of other GPU based workflows just don't work well with the 535
driver.

The reason I used the 545 driver was because non of those issues existed
there, and any issues were mild in comparison to the 535 driver.

I'm not sure what has changed between linux-image-6.5.0-45-generic
(previous) and linux-image-6.8.0-40-generic (current), but the change is
obviously affecting the 545 and above drivers. I can also no longer see
the 550 or 555 drivers (which I presume are even worse).

If there is anything I can do to help diagnose the problem, please let
me know and I'll provide anything you need.

Hopefully this gets resolved soon - especially on the LTS branches.


Kind regards,
Haz

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: nvidia-driver-545 (not installed)
ProcVersionSignature: Ubuntu 6.8.0-40.40~22.04.3-generic 6.8.12
Uname: Linux 6.8.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.6
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sat Aug 24 15:42:43 2024
InstallationDate: Installed on 2020-05-22 (1555 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: nvidia-graphics-drivers-545
UpgradeStatus: Upgraded to jammy on 2022-10-04 (689 days ago)

** Affects: nvidia-graphics-drivers-545 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-545 in Ubuntu.
https://bugs.launchpad.net/bugs/2077795

Title:
  After a weekly update the nvidia-driver-545 that I used because it was
  the most reliable stopped working and reverted back to nouveau drivers
  that barely work

Status in nvidia-graphics-drivers-545 package in Ubuntu:
  New

Bug description:
  Hi, Hope you are keeping well and sorry that I have to post this bug.

  First I'll get the 4 questions listed here first, then add more info
  afterwards:

  1) lsb_release -rd 
  Description:  Ubuntu 22.04.4 LTS
  Release:  22.04

  2) apt-cache policy nvidia-driver-535
  nvidia-driver-535:
Installed: 535.183.01-0ubuntu0.22.04.1
Candidate: 535.183.01-0ubuntu0.22.04.1
Version table:
   *** 535.183.01-0ubuntu0.22.04.1 500
  500 http://gb.archive.ubuntu.com/ubuntu jammy-updates/restricted 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/restricted amd64 
Packages
  100 /var/lib/dpkg/status

  apt-cache policy nvidia-driver-545
  nvidia-driver-545:
Installed: (none)
Candidate: 545.29.06-0ubuntu0.22.04.2
Version table:
   545.29.06-0ubuntu0.22.04.2 500
  500 http://gb.archive.ubuntu.com/ubuntu jammy-updates/restricted 
amd64 Packages

  3) Expected the nvidia-driver-545 to remain installed that I had
  previously, and work as normal after the weekly updates.

  4) After the weekly updates, the kernel module compile for 545 failed
  and r

[Kernel-packages] [Bug 2015228] Re: Bluetooth not working rfkill Soft blocked: yes

2023-04-04 Thread Hassan Williamson
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System
-> About Ubuntu

Description:Ubuntu 22.04.2 LTS
Release:22.04

2) The version of the package you are using, via 'apt-cache policy
pkgname' or by checking in Software Center

bluez:
  Installed: 5.64-0ubuntu1
  Candidate: 5.64-0ubuntu1
  Version table:
 *** 5.64-0ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status
N: Unable to locate package pkgname

3) What you expected to happen

Bluetooth to be able to turn on.

4) What happened instead

Bluetooth remains off and doesn't work with any bluetooth-enabling
device.

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

Title:
  Bluetooth not working rfkill Soft blocked: yes

Status in bluez package in Ubuntu:
  New

Bug description:
  Hi Devs,

  Hope you're all keeping well.

  The problem I have is similar to:
  https://answers.launchpad.net/ubuntu/+question/699306

  Basically Bluetooth doesn't work on installed Ubuntu 22.04.2 neither
  the laptop (Dell Inspirion 7577) internal device (Intel 8265) or a USB
  dongle (not sure it was recommended for raspberry pi and works on
  desktop with 22.04 just fine: 0a12:0001 Cambridge Silicon Radio, Ltd
  Bluetooth Dongle (HCI mode).

  It works fine in a live USB image on the same laptop.

  I get the following with rfkill:

  rfkill list all 
  1: hci1: Bluetooth
Soft blocked: yes
Hard blocked: no
  2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  3: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no

  - Unblocking with rfkill doesn't work
  - Restarting bluetooth doesn't work
  - Getting another device doesn't work

  I recall having issues with WiFi around the time I got the laptop, and
  recall changing settings for that - but I couldn't tell you what they
  were (~2017 ish). Plus I believe I've reinstalled since then due to an
  SSD failure. It has been upgraded from LTS to LTS since 18.04 though.

  Any thoughts, ideas, or questions, I'm more than happy to try
  anything, or even help as much as possible to help get this resolved,
  its been going on for a couple of years now and mainly ignored it
  because I was mostly fine without, but I really need it to work now
  and appreciate any help on this.

  Thanks so much in advance, love you all for the work you do.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87
  Uname: Linux 5.15.0-69-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Tue Apr  4 12:47:27 2023
  InstallationDate: Installed on 2020-04-09 (1089 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Inspiron 7577
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic 
root=UUID=761c1e7a-7759-4f7d-a985-33c7654bccad ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to jammy on 2023-01-12 (82 days ago)
  dmi.bios.date: 03/18/2022
  dmi.bios.release: 1.17
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.17.0
  dmi.board.name: 0XCNGT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.17.0:bd03/18/2022:br1.17:svnDellInc.:pnInspiron7577:pvr:rvnDellInc.:rn0XCNGT:rvrA00:cvnDellInc.:ct10:cvr:sku07FA:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7577
  dmi.product.sku: 07FA
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2015228/+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 2015228] [NEW] Bluetooth not working rfkill Soft blocked: yes

2023-04-04 Thread Hassan Williamson
Public bug reported:

Hi Devs,

Hope you're all keeping well.

The problem I have is similar to:
https://answers.launchpad.net/ubuntu/+question/699306

Basically Bluetooth doesn't work on installed Ubuntu 22.04.2 neither the
laptop (Dell Inspirion 7577) internal device (Intel 8265) or a USB
dongle (not sure it was recommended for raspberry pi and works on
desktop with 22.04 just fine: 0a12:0001 Cambridge Silicon Radio, Ltd
Bluetooth Dongle (HCI mode).

It works fine in a live USB image on the same laptop.

I get the following with rfkill:

rfkill list all 
1: hci1: Bluetooth
Soft blocked: yes
Hard blocked: no
2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
3: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no

- Unblocking with rfkill doesn't work
- Restarting bluetooth doesn't work
- Getting another device doesn't work

I recall having issues with WiFi around the time I got the laptop, and
recall changing settings for that - but I couldn't tell you what they
were (~2017 ish). Plus I believe I've reinstalled since then due to an
SSD failure. It has been upgraded from LTS to LTS since 18.04 though.

Any thoughts, ideas, or questions, I'm more than happy to try anything,
or even help as much as possible to help get this resolved, its been
going on for a couple of years now and mainly ignored it because I was
mostly fine without, but I really need it to work now and appreciate any
help on this.

Thanks so much in advance, love you all for the work you do.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: bluetooth (not installed)
ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87
Uname: Linux 5.15.0-69-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Tue Apr  4 12:47:27 2023
InstallationDate: Installed on 2020-04-09 (1089 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Dell Inc. Inspiron 7577
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-69-generic 
root=UUID=761c1e7a-7759-4f7d-a985-33c7654bccad ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: Upgraded to jammy on 2023-01-12 (82 days ago)
dmi.bios.date: 03/18/2022
dmi.bios.release: 1.17
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.17.0
dmi.board.name: 0XCNGT
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.17.0:bd03/18/2022:br1.17:svnDellInc.:pnInspiron7577:pvr:rvnDellInc.:rn0XCNGT:rvrA00:cvnDellInc.:ct10:cvr:sku07FA:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 7577
dmi.product.sku: 07FA
dmi.sys.vendor: Dell Inc.

** Affects: bluez (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy

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

Title:
  Bluetooth not working rfkill Soft blocked: yes

Status in bluez package in Ubuntu:
  New

Bug description:
  Hi Devs,

  Hope you're all keeping well.

  The problem I have is similar to:
  https://answers.launchpad.net/ubuntu/+question/699306

  Basically Bluetooth doesn't work on installed Ubuntu 22.04.2 neither
  the laptop (Dell Inspirion 7577) internal device (Intel 8265) or a USB
  dongle (not sure it was recommended for raspberry pi and works on
  desktop with 22.04 just fine: 0a12:0001 Cambridge Silicon Radio, Ltd
  Bluetooth Dongle (HCI mode).

  It works fine in a live USB image on the same laptop.

  I get the following with rfkill:

  rfkill list all 
  1: hci1: Bluetooth
Soft blocked: yes
Hard blocked: no
  2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  3: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no

  - Unblocking with rfkill doesn't work
  - Restarting bluetooth doesn't work
  - Getting another device doesn't work

  I recall having issues with WiFi around the time I got the laptop, and
  recall changing settings for that - but I couldn't tell you what they
  were (~2017 ish). Plus I believe I've reinstalled since then due to an
  SSD failure. It has been upgraded from LTS to LTS since 18.04 though.

  Any thoughts, ideas, or questions, I'm more than happy to try
  anything, or even help as much as possible to help get this resolved,
  its been going on for a couple of years now and mainly ignored it
  because I was mostly fine without, but I really need it to work now
  and appreciate any help on this.

  Thanks so much in advance, love you all for the work you do.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-69.76-generic 5.15.87
  Uname: Linux 5.15.0-69-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvi

[Kernel-packages] [Bug 1912773] Re: [MS-7C52, ATI R6xx HDMI, Digital Out, HDMI] No sound at all, second display not working, cpu/agpu performance dropped considerably

2022-02-25 Thread Hassan Williamson
This issue still exists, when trying to figure out why bug #1962308 was
happening, this exact same problem still happens on 5.8.0-63 (originally
reported on 5.8.0-40).

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

Title:
  [MS-7C52, ATI R6xx HDMI, Digital Out, HDMI] No sound at all, second
  display not working, cpu/agpu performance dropped considerably

Status in Linux Firmware:
  New
Status in Mutter:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  After a recent update, I now have a system that can no longer play
  audio (via HDMI), my second monitor (DVI) is no longer being picked
  up, and CPU/AGPU usage has lost a lot of performance (OBS is basically
  unusable at this point).

  Whatever has happened with the recent updates has caused the AMD
  drivers (presumably?) to not work correctly - because it is an AMD
  Ryzen 5 3400g (with no dedicated graphics card).

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  ```
  $ lsb_release -rd
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  ```

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  Not sure which package would be the cause, however these were the
  version that were working prior to the update:

  ```
  libnss-systemd:amd64=245.4-4ubuntu3.3 libudev1:i386=245.4-4ubuntu3.3 
libudev1:amd64=245.4-4ubuntu3.3 libudev-dev:amd64=245.4-4ubuntu3.3 
udev=245.4-4ubuntu3.3 systemd-timesyncd=245.4-4ubuntu3.3 
systemd-sysv=245.4-4ubuntu3.3 libpam-systemd:amd64=245.4-4ubuntu3.3 
systemd=245.4-4ubuntu3.3 libsystemd0:amd64=245.4-4ubuntu3.3 
libsystemd0:i386=245.4-4ubuntu3.3 libapt-pkg6.0:amd64=2.0.2ubuntu0.2 
apt=2.0.2ubuntu0.2 apt-utils=2.0.2ubuntu0.2 
ubuntu-release-upgrader-gtk=1:20.04.29 ubuntu-release-upgrader-core=1:20.04.29 
update-manager=1:20.04.10.1 update-manager-core=1:20.04.10.1 
python3-distupgrade=1:20.04.29 python3-update-manager=1:20.04.10.1 
update-notifier=3.192.30.3 update-notifier-common=3.192.30.3 
libnetplan0:amd64=0.100-0ubuntu4~20.04.3 netplan.io=0.100-0ubuntu4~20.04.3 
mutter-common=3.36.6-1ubuntu0.20.04.2 
gir1.2-mutter-6:amd64=3.36.6-1ubuntu0.20.04.2 
libmutter-6-0:amd64=3.36.6-1ubuntu0.20.04.2 jq=1.6-1 libjq1:amd64=1.6-1 
linux-firmware=1.187.7 linux-generic-hwe-20.04=5.8.0.38.43~20.04.23 
linux-image-generic-hwe-20.04=5.8.0.38.43~20.04.23 
linux-headers-generic-hwe-20.04=5.8.0.38.43~20.04.23 
linux-headers-generic=5.4.0.62.65 linux-libc-dev:amd64=5.4.0-62.70 
mutter=3.36.6-1ubuntu0.20.04.2
  ```

  This list was generated with the command:

  `awk 'BEGIN{ start="0" } { if($0 ~ /Log started: 2021-01-20/) {
  start="1"} if ( start == "1" && $0 ~ /Unpacking.*over/) {gsub(/[\s\t)(
  ]+/,"",$5); printf("%s=%s ", $2 , $5)}}' /var/log/apt/term.log`

  3) What you expected to happen

  Sound and video working via HDMI on primary monitor, second monitor
  displaying (extended) video via DVI. CPU and AGPU being able to render
  via OBS.

  4) What happened instead

  No sound. No second display. Any CPU or AGPU tasks running slower than
  normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  hazrpg 3344 F pulseaudio
   /dev/snd/controlC2:  hazrpg 3344 F pulseaudio
   /dev/snd/controlC0:  hazrpg 3344 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 22 11:51:14 2021
  InstallationDate: Installed on 2020-05-22 (244 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Raven/Raven2/Fenghuang HDMI/DP Audio Controller - HD-Audio 
Generic
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [MS-7C52, ATI R6xx HDMI, Digital Out, HDMI] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.20
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: A320M-A PRO MAX (MS-7C52)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.20:bd09/18/2019:br5.14:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C52:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnA320M-APROMAX

[Kernel-packages] [Bug 1962308] [NEW] Video captures (e.g. webcam, capture card) are being displayed as "Video Capture 3"

2022-02-25 Thread Hassan Williamson
Public bug reported:

This issue seems to have been introduced in 5.13 somewhere, I only had
5.13.0-30 and 5.13.0-28 available in grub on the 5.13 branch to test
against, but in both instances all capture devices are labelled as
"Video Capture 3" where previously it would show the device's actual
name. I do still have 5.8 branch and 5.4 branch, and when testing
against 5.8.0-63 it showed the names correctly everywhere, and likewise
with 5.4.0-64.

The number at the end seems to be the number of devices, even though it
is getting the counted digit and repeating it for all of them.

If I run:

$ v4l2-ctl --list-devices

I get:

Video Capture 3 (usb-:08:00.3-3):
/dev/video2
/dev/video3
/dev/media1

Video Capture 3 (usb-:08:00.3-4):
/dev/video4
/dev/video5
/dev/media2

Video Capture 3 (usb-:08:00.4-1):
/dev/video0
/dev/video1
/dev/media0

The devices I have (from lsusb) are:

Bus 003 Device 004: ID 534d:2109 MACROSILICON 
Bus 003 Device 003: ID 298f:1996 MACROSILICON ShadowCast
Bus 005 Device 002: ID 0458:6006 KYE Systems Corp. (Mouse Systems) AUKEY 
PC-LM1E Camera

Previously the devices would be labelled as:

MACROSILICON
MACROSILICON ShadowCast
AUKEY PC-LM1E Camera

There appears to be a mismatch in the usb bus numbers too. You'll notice
in v4l2-ctl 2 of them are correctly identified as Bus 003 and Device 003
andd 004 respectively (outlined as 00.3-3 and 00.3-4), however the last
device shows 00.4-1 but in lsusb this is received as Bus 005 Device 002
- so it should be 00.5-2 if I'm right in the naming conventions that
should be used.

-

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System
-> About Ubuntu

$ lsb_release -rd
Description:Ubuntu 20.04.4 LTS
Release:20.04

2) The version of the package you are using, via 'apt-cache policy
pkgname' or by checking in Software Center

$ apt-cache policy linux-image-5.13.0-30-generic
linux-image-5.13.0-30-generic:
  Installed: 5.13.0-30.33~20.04.1
  Candidate: 5.13.0-30.33~20.04.1
  Version table:
 *** 5.13.0-30.33~20.04.1 500
500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages
100 /var/lib/dpkg/status

3) What you expected to happen

The labels of the USB devices to show up correctly in Zoom, OBS,
Microsoft Teams, Skype, Cheese, etc so that I can identify which device
to use.

4) What happened instead

The labels are wrong and given a generic "Video Camera 3" label for all
of them - where 3 is the number of devices I have connected.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-30-generic 5.13.0-30.33~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-30-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 25 12:07:37 2022
InstallationDate: Installed on 2020-05-22 (643 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: linux-signed-hwe-5.13
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed-hwe-5.13 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
  Video captures (e.g. webcam, capture card) are being displayed as
  "Video Capture 3"

Status in linux-signed-hwe-5.13 package in Ubuntu:
  New

Bug description:
  This issue seems to have been introduced in 5.13 somewhere, I only had
  5.13.0-30 and 5.13.0-28 available in grub on the 5.13 branch to test
  against, but in both instances all capture devices are labelled as
  "Video Capture 3" where previously it would show the device's actual
  name. I do still have 5.8 branch and 5.4 branch, and when testing
  against 5.8.0-63 it showed the names correctly everywhere, and
  likewise with 5.4.0-64.

  The number at the end seems to be the number of devices, even though
  it is getting the counted digit and repeating it for all of them.

  If I run:

  $ v4l2-ctl --list-devices

  I get:

  Video Capture 3 (usb-:08:00.3-3):
/dev/video2
/dev/video3
/dev/media1

  Video Capture 3 (usb-:08:00.3-4):
/dev/video4
/dev/video5
/dev/media2

  Video Capture 3 (usb-:08:00.4-1):
/dev/video0
/dev/video1
/dev/media0

  The devices I have (from lsusb) are:

  Bus 003 Device 004: ID 534d:2109 MACROSILICON 
  Bus 003 Device 003: ID 298f:1996 MACROSILICON ShadowCast
  Bus 005 Device 002: ID 0458:6006 KYE Systems Corp. (Mouse Systems) AUKEY 
PC-LM1E Camera

  Previously the devices would be labelled as:

  MAC

[Kernel-packages] [Bug 1912773] Re: [MS-7C52, ATI R6xx HDMI, Digital Out, HDMI] No sound at all, second display not working, cpu/agpu performance dropped considerably

2021-01-23 Thread Hassan Williamson
Fixed it! However I'm not sure why the file was created when I'm running
on AMD hardware and requiring the use of the APU.

The bug is that a blacklist file was created in:

/etc/modprobe.d/blacklist-amdgpu.conf

With the following line:

blacklist amdgpu

That obviously prevented the APU drivers to load up, so the HDMI audio
sink could be initialised and prevented GPU rendering.

This problem could likely affect multiple people and are unaware if they
are on a single display and using speakers connected to the motherboard
instead of via other means such as the 3.5mm output, optical, or even
via Bluetooth. Since the system worked otherwise. The only symptom
people on single displays and not using HDMI audio people would
experience is when doing anything CPU or GPU intensive, since I can only
presume the CPU is doing all the legwork to render the display instead
of the APU.

For reference the CPU is a AMD Ryzen 5 3400g with Vega 11 APU, and no
dedicated graphics card.

If anyone needs any additional information, logs, or anything let me
know and I'll be happy to help out where I can. I'm just glad that I got
this resolved, but I'd hate for others to experience the same issues
while updates trickle down (it could also be months before anyone
notices on single display and no HDMI audio setups).

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

Title:
  [MS-7C52, ATI R6xx HDMI, Digital Out, HDMI] No sound at all, second
  display not working, cpu/agpu performance dropped considerably

Status in amd:
  New
Status in Linux Firmware:
  New
Status in Mutter:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After a recent update, I now have a system that can no longer play
  audio (via HDMI), my second monitor (DVI) is no longer being picked
  up, and CPU/AGPU usage has lost a lot of performance (OBS is basically
  unusable at this point).

  Whatever has happened with the recent updates has caused the AMD
  drivers (presumably?) to not work correctly - because it is an AMD
  Ryzen 5 3400g (with no dedicated graphics card).

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  ```
  $ lsb_release -rd
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  ```

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  Not sure which package would be the cause, however these were the
  version that were working prior to the update:

  ```
  libnss-systemd:amd64=245.4-4ubuntu3.3 libudev1:i386=245.4-4ubuntu3.3 
libudev1:amd64=245.4-4ubuntu3.3 libudev-dev:amd64=245.4-4ubuntu3.3 
udev=245.4-4ubuntu3.3 systemd-timesyncd=245.4-4ubuntu3.3 
systemd-sysv=245.4-4ubuntu3.3 libpam-systemd:amd64=245.4-4ubuntu3.3 
systemd=245.4-4ubuntu3.3 libsystemd0:amd64=245.4-4ubuntu3.3 
libsystemd0:i386=245.4-4ubuntu3.3 libapt-pkg6.0:amd64=2.0.2ubuntu0.2 
apt=2.0.2ubuntu0.2 apt-utils=2.0.2ubuntu0.2 
ubuntu-release-upgrader-gtk=1:20.04.29 ubuntu-release-upgrader-core=1:20.04.29 
update-manager=1:20.04.10.1 update-manager-core=1:20.04.10.1 
python3-distupgrade=1:20.04.29 python3-update-manager=1:20.04.10.1 
update-notifier=3.192.30.3 update-notifier-common=3.192.30.3 
libnetplan0:amd64=0.100-0ubuntu4~20.04.3 netplan.io=0.100-0ubuntu4~20.04.3 
mutter-common=3.36.6-1ubuntu0.20.04.2 
gir1.2-mutter-6:amd64=3.36.6-1ubuntu0.20.04.2 
libmutter-6-0:amd64=3.36.6-1ubuntu0.20.04.2 jq=1.6-1 libjq1:amd64=1.6-1 
linux-firmware=1.187.7 linux-generic-hwe-20.04=5.8.0.38.43~20.04.23 
linux-image-generic-hwe-20.04=5.8.0.38.43~20.04.23 
linux-headers-generic-hwe-20.04=5.8.0.38.43~20.04.23 
linux-headers-generic=5.4.0.62.65 linux-libc-dev:amd64=5.4.0-62.70 
mutter=3.36.6-1ubuntu0.20.04.2
  ```

  This list was generated with the command:

  `awk 'BEGIN{ start="0" } { if($0 ~ /Log started: 2021-01-20/) {
  start="1"} if ( start == "1" && $0 ~ /Unpacking.*over/) {gsub(/[\s\t)(
  ]+/,"",$5); printf("%s=%s ", $2 , $5)}}' /var/log/apt/term.log`

  3) What you expected to happen

  Sound and video working via HDMI on primary monitor, second monitor
  displaying (extended) video via DVI. CPU and AGPU being able to render
  via OBS.

  4) What happened instead

  No sound. No second display. Any CPU or AGPU tasks running slower than
  normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  hazrpg 3344 F pulseaudio
   /dev/snd/controlC2:  hazrpg 3344 F pulseaudio
   /dev/snd/controlC0:  hazrpg 3344 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 22 11:51:14 2021
  InstallationDate: Instal

[Kernel-packages] [Bug 1721909] Re: Goodix GF3208 (fingerprint reader) not being recognised by kernel/system

2019-02-01 Thread Hassan Williamson
Wow, lots of different devices have started shipping the same
fingerprint scanner since I first raised this issue.

Is there anything we can do in the community to help? Clearly there is a
need for this to be included.

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

Title:
  Goodix GF3208 (fingerprint reader) not being recognised  by
  kernel/system

Status in Linux:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Goodix GF3208 is not being recognised by the system (Dell Inspiron
  15 7577). What's worse is that it isn't even showing the manufacturer
  vendor id information when doing:

  $ lsusb
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 27c6:5301
  Bus 001 Device 003: ID 8087:0a2b Intel Corp.
  Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 001 Device 005: ID 0bda:5652 Realtek Semiconductor Corp.
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Note that the vendor id 27c6 should at least say "Shenzhen Huiding
  Technology Co., Ltd." as per
  
https://github.com/torvalds/linux/blob/e19b205be43d11bff638cad4487008c48d21c103/Documentation/devicetree/bindings
  /vendor-prefixes.txt

  Will/has support been made for the Goodix GF3208 Fingerprint
  reader/scanner?

  Thanks in advance,
  Haz

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-35-generic 4.10.0-35.39~16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Oct  7 04:03:25 2017
  InstallationDate: Installed on 2017-10-01 (5 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1721909/+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 1803891] Re: package nvidia-kernel-common-390 390.77-0ubuntu0.18.04.1 failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in packag

2019-01-15 Thread Hassan Williamson
I got the same as above, except I'm coming from 16.04.5.

The other thing is I only upgrade from 16.04.5 because I couldn't
actually boot into it. See bug here:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1800250

I had to upgrade using the debian-method because all normal Ubunutu
upgrade paths would not work for me - and although I'm not one to give
up a fight on fixing a bug, I had to because I need this system for
work.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/1803891

Title:
  package nvidia-kernel-common-390 390.77-0ubuntu0.18.04.1 failed to
  install/upgrade: trying to overwrite
  '/lib/udev/rules.d/71-nvidia.rules', which is also in package
  nvidia-384 384.130-0ubuntu0.16.04.1

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed

Bug description:
  upgrade from 16.04.03 > 18.04.01

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: nvidia-kernel-common-390 390.77-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160
  Uname: Linux 4.4.0-139-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Sun Nov 18 17:07:05 2018
  Dependencies:
   
  ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which 
is also in package nvidia-384 384.130-0ubuntu0.16.04.1
  InstallationDate: Installed on 2013-10-12 (1862 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: nvidia-graphics-drivers-390
  Title: package nvidia-kernel-common-390 390.77-0ubuntu0.18.04.1 failed to 
install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which 
is also in package nvidia-384 384.130-0ubuntu0.16.04.1
  UpgradeStatus: Upgraded to bionic on 2018-11-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1803891/+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 1650956] Re: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'

2017-10-06 Thread Hassan Williamson
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.3 LTS
Release:16.04
Codename:   xenial
-
$ uname -a
Linux shark 4.10.0-35-generic #39~16.04.1-Ubuntu SMP Wed Sep 13 09:02:42 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux
-

This also affects me, I see:

$ dmesg| grep normal
[0.037054] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'

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

Title:
  ENERGY_PERF_BIAS: Set to 'normal', was 'performance'

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [0.018601] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
  [0.018602] ENERGY_PERF_BIAS: View and update with 
x86_energy_perf_policy(8)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.9.0-11-generic 4.9.0-11.12
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D3p:   caravena   2073 F...m pulseaudio
   /dev/snd/controlC0:  caravena   2073 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Dec 18 17:10:18 2016
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2015-07-26 (511 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.9.0-11-generic 
root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.9.0-11-generic N/A
   linux-backports-modules-4.9.0-11-generic  N/A
   linux-firmware1.162
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2016-10-29 (50 days ago)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1650956/+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