Maybe its a dedicated GPU Fan Controlled by the GPU? Try installing the
lastest Nvidia Drivers, use mainline 4.6 for that and the Nvidia Drivers
ppa.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
The Fans on my ASUS GL502VT Laptop start spinning full speed after about
2 minutes after bootup in default mode. If I boot with nomodeset boot
parameter it seems not to happen. The Device is running the lastest BIOS
by ASUS.
Kernel Version: Ubuntu 4.4.0-31.50-generic 4.4.13
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1607783/+attachment/4709458/+files/Lspci.txt
--
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/1607783
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1607783/+attachment/4709463/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected xenial
** Description changed:
The Fans on my ASUS GL502VT Laptop start spinning full speed after about
2 minutes after bootup in default mode. If I boot with nomodeset boot
parameter it seems not to happen. The Device is running the
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1607783/+attachment/4709460/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1607783/+attachment/4709465/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages,
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1607783/+attachment/4709461/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1607783/+attachment/4709459/+files/Lsusb.txt
--
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/1607783
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1607783/+attachment/4709455/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1607783/+attachment/4709464/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1607783/+attachment/4709454/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1607783/+attachment/4709453/+files/CRDA.txt
--
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/1607783
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1607783/+attachment/4709456/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1607783/+attachment/4709462/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
As this is a brand new device I tried 16.04 LTS first where the bug was
persistent, same for 14.04. But the lastest upstream kernel fixed this.
Thanks for your help.
** Tags added: kernel-fixed-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this
** Package changed: linux (Ubuntu) => powermgmt-base (Ubuntu)
--
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/1878635
Title:
Intel Titan Ridge TB3 USB Controller prevents system from
Public bug reported:
The dmesg log states the following:
PM: Device :0f:00.0 failed to suspend async: error -110
When checking lspci this points to the following device:
0f:00.0 USB controller: Intel Corporation JHL7540 Thunderbolt 3 USB Controller
[Titan Ridge 2C 2018] (rev 06)
which is
The latest Ubuntu 21.10 install still comes with zfs-kmod-2.0.3, which
prevents the system from booting in the first place.
Installing zfs-dkms via the recovery mode, which updates the zfs-kmod to
version 2.0.6, fixed the issue for me.
I hope that the release image of Ubuntu 21.10 will ship with
I also experienced this bug on Ubuntu 21.10 Beta during boot on a fresh
ZFS Install with Encryption.
The only way to boot into GNOME without crashing was booting through
recovery mode.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
*** This bug is a duplicate of bug 1949790 ***
https://bugs.launchpad.net/bugs/1949790
** This bug has been marked a duplicate of bug 1949790
Thunderbolt 3 NIC driver is loaded too early and won't establish connection
--
You received this bug notification because you are a member of
Public bug reported:
I am using a Thunderbolt 3 Pro Dock with a built in Aquantia 10 GBase-T
NIC (atlantic).
The issue is that during boot it only detects the interface as 5 GBe, as seen
in dmesg:
enp11s0: atlantic: link change old 0 new 5000
This prevents the interface from establishing a
Public bug reported:
I am using a Thunderbolt 3 Pro Dock with a built in Aquantia 10 GBase-T
NIC (atlantic).
The issue is that during boot it only detects the interface as 5 GBe, as seen
in dmesg:
enp11s0: atlantic: link change old 0 new 5000
This prevents the interface from establishing a
Was able to reproduce this bug on two of my machines aswell. Both were
using Nvidia 3000 Series graphics. Booting the 5.15.0-18 Kernel or 5.16
Mainline Kernels didn't have this issue.
Seems like only 5.15.0-22 is affected by this bug.
--
You received this bug notification because you are a
Was able to reproduce this issue on two of my machines aswell. Both were
installed in EFI Mode.
Booting the older 5.15.0-18 kernel or 5.16 mainline kernels work around
this issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Public bug reported:
Suspend/Resume and don't seem to work with the shipped 5.15 Kernel.
When rebooting or shutting down the system gets stuck at "Reached
Target: System Poweroff" or "Reboot".
Installing the mainline kernel 5.16.11 fixes this issue and the system
is able to properly
** Also affects: nvidia-graphics-drivers-510 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: nvidia-graphics-drivers-510 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu)
--
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/1960460
Title:
Fails to
I'm using a RTX 3080 Ti on a Z690 Desktop motherboard and enabling the
S0ix option fixed the problem for me.
I've added the following option
"nvidia.NVreg_EnableS0ixPowerManagement=1" to
GRUB_CMDLINE_LINUX_DEFAULT.
--
You received this bug notification because you are a member of Kernel
Try nvidia.NVreg_PreserveVideoMemoryAllocations=1 as suggested by
@vanvugt
You may wanna change the file path of the temporary file thought for
better performance.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Hi Timo,
Upgrading to Mesa 22.2 seems to resolve this issue. Using the packages
from the intel repository (https://dgpu-docs.intel.com/installation-
guides/ubuntu/ubuntu-jammy-arc.html) works as well.
Is it planned to release the updated mesa 22.2 packages to Ubuntu 22.04?
--
You received this
Private bug reported:
When using the latest Linux 6.0.0-1006-oem Kernel, Firefox and Chromium
won't open anymore.
** Affects: linux-oem-6.0 (Ubuntu)
Importance: Undecided
Status: Invalid
** Changed in: linux-oem-6.0 (Ubuntu)
Status: New => Invalid
** Information type
Public bug reported:
The computer is unable to suspend or hibernate, when a DG2 graphics card
is installed and in-use in the system.
When attempting to suspend or hibernate the system will turn off its
screens for a few seconds after which they will light up again.
I am using the latest
Looking forward to linux-oem-6.0 support. Got an A380 and A770 here for
testing purposes.
It seems like the current proposed build of the linux-oem-6.0 kernel
still has some issues in this regard.
--
You received this bug notification because you are a member of Kernel
Packages, which is
Public bug reported:
When using GNOME Shell with Wayland, all application windows become
invisible from time to time. This usually happens right after starting
GNOME Shell for the first time or after having a VRAM intensive
application open, such as a game.
I have installed the latest
I've managed to reproduce this bug on an Arc A380 and Arc A770 GPU. I've
attached the requested lspci output for the A770.
Ubuntu 22.04 has already received a mesa update with backported patches
for DG2 support:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1971712
I haven't tried 22.10
Public bug reported:
DG2 graphics support should be enabled by default, dmesg outputs the
following:
i915 :67:00.0: Your graphics device 56a5 is not properly supported by the
driver in this
kernel version. To force driver probe anyway, use
i915.force_probe=56a5
Are there any plans for providing an i915 DKMS Module with DG2 Support
for oem-5.17?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.17 in Ubuntu.
https://bugs.launchpad.net/bugs/1971712
Title:
Add support for Intel DG2
It seems like there is no more force-probe required for oem-6.1, works
fine out-of-the-box now.
When is the 22.2 mesa from ppa:canonical-x/x-staging going to be
released, currently using the linux-oem-6.1 kernel together with the
23.0 mesa from the Intel Arc package sources.
--
You received
Seems like this issue was caused by nvidia driver remainders, which
caused an instant wake-up after suspend or hibernate.
** Changed in: linux-oem-6.0 (Ubuntu)
Status: New => Incomplete
** Changed in: linux-oem-6.0 (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug
Is this not going to happen?
> kernel: oem-6.0 plus a bunch of backports from 6.1/drm-tip
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1971712
Title:
Add support for Intel
The new firmware package works fine with the 6.0 kernel, it loads the GuC and
HuC Firmware, as seen below:
[4.691687] i915 :03:00.0: [drm] Finished loading DMC firmware
i915/dg2_dmc_ver2_06.bin (v2.6)
[4.702309] i915 :03:00.0: [drm] GuC firmware i915/dg2_guc_70.1.2.bin
version
42 matches
Mail list logo
