[Ubuntu-x-swat] [Bug 1821882] Re: Screen is very dark and brightness cannot be adjusted
** Tags added: ce-qa-concern -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1821882 Title: Screen is very dark and brightness cannot be adjusted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1821882/+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 1821882] Re: Screen is very dark and brightness cannot be adjusted
I tried the same while blacklisting nouveau driver in grub: $ cat /proc/cmdline BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash modprobe.blacklist=nouveau --- This time, I have "acpi_video0" in /sys/class/backlight, but the result is the same. The screen is very dark. /sys/class/backlight/acpi_video0/brightness is 100 by default. I can modify this value with $ sudo su # echo 60 > /sys/class/backlight/acpi_video0/brightness and the brightness actually changes to something even darker. If I try to set it over 100, I get: write error: Invalid argument -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1821882 Title: Screen is very dark and brightness cannot be adjusted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1821882/+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 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870
Xubuntu daily images are still missing the fix for bug 1819943. So please wait until a newer image is available which includes that fix before retesting. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1821609 Title: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1821609/+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 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870
stranger and stranger .. if you install kernel 5.0.0-8.9 at the first boot into any new install partition before changing any thing else .. it does not fix the issue .. once you return sda1 to being grub master .. neither sda7 nor sda6 will keep lightdm running ..both briefly flash lightdm login screen and then blank out screen , briefly showing a cursor .. a long hold down of power button does eventually powerdown machine .. note: can't even get to consoles .. not a nice fail. note resetting grub back to the "new install version" works but there is a stutter in lightdm .. it shows briefly blanks for 2 seconds then shows again and and you can login.. only other way into partition is through recovery boot option, or via a chroot. this is now using xubuntu-am64-desktop.iso -beta version ( two installs sda6 and sda7 ) I'm beginning to think that using a chroot to reinstall/or update the kernel might be a "work around only" for the issue .. as a native update does not work .. I'm going to test this further .. replace sda6 and sda7 sequentially and see what happens using chroots for updates more later .. any ideas what else to look for or check? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1821609 Title: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1821609/+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 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1821609 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1821609 Title: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1821609/+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 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870
okay still bug present in xubuntu-disco-amd64-desktop-beta.. still uses kernel 5.0.0-7 updating from proposed with kernel 5.0.0-8.9 it works properly i.e. any linux os partion can be used to install grub and another partion with linux can be selected and boot normally e.g. beta install is on sda7 another linux os version is on sda1 which is used to install grub to /dev/sda thus sda1 is master/main linix os used .. the beta on sda7 will start lightdm but it flickers on and dies when using kernel 5.0.0-7 but when using kernel 5.0.0-8.9 it works properly lightdm stays running and does not even flicker... the only apparent difference is the kernel selected .. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1821609 Title: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1821609/+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 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870
** This bug is no longer a duplicate of bug 1819943 intel video driver not installed by default in ubuntu 19.04 (Disco) [needed for graphics support on Intel Core 2 Duo systems] -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1821609 Title: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1821609/+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 1821505] Re: [radeon] screen cannot be turned back on after some time of inactivity
I believe this is a bug of higher importance as it makes 16.04 LTS in standard configuration (with enabled screen blanking) unusable on the ATI Radeon cards. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1821505 Title: [radeon] screen cannot be turned back on after some time of inactivity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1821505/+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 1821505] Re: [radeon] screen cannot be turned back on after some time of inactivity
Here is the workaround for the problem: The bug is in the package xserver-xorg-video-radeon 7.7.0, it is fixed in the later versions. Until it is fixed in 16.04 LTS, take the package from the newer releases. In this example, we'll pull it from 16.10 (Yakkety Yak): a) add the line at the end of the /etc/apt/sources.list file: deb http://old-releases.ubuntu.com/ubuntu yakkety main b) add file "yakkety.pref" to the /etc/apt/preferences.d c) sudo apt-get update - this will load new repostiory and refresh the preferences d) sudo apt-get upgrade - this will pull xserver-xorg-video-radeon package v7.7.1, with fixed bug. e) log out from X That's it. After login, wait for the screen blank and wake it with key press or mouse action. ** Description changed: When using my AMD Radeon X1300 card, if the screen turns off due to inactivity, it cannot be woken up by moving the mouse or by hitting a key. - WORKAROUND: Type in a terminal: + If you type in a terminal: xset -display :0.0 dpms force off + you can wake the screen normally. - WORKAROUND: Typing the following in a terminal turns my screen off, and after typing this line, the screen can be woken up by moving the mouse or by hitting a key: + Typing the following in a terminal turns my screen off, and after typing this line, the screen can be woken up by moving the mouse or by hitting a key: gnome-screensaver-command -a - WORKAROUND: When I restart the display manager via ssh with another - computer, the screen then comes to life again and I can log back in. + When I restart the display manager via ssh with another computer, the + screen then comes to life again and I can log back in. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-143.169-generic 4.4.170 Uname: Linux 4.4.0-143-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Mar 24 11:11:17 2019 DistUpgraded: 2019-03-20 18:17:04,395 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] [1002:7187] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd RV516 [Radeon X1300/X1550 Series] [1458:215c] InstallationDate: Installed on 2010-05-13 (3236 days ago) InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release amd64 (20100427) MachineType: FUJITSU SIEMENS ESPRIMO E5720 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-143-generic root=/dev/mapper/orao-root ro rootfstype=ext4 quiet SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2019-03-20 (3 days ago) dmi.bios.date: 02/05/2009 dmi.bios.vendor: FUJITSU SIEMENS // Phoenix Technologies Ltd. dmi.bios.version: 6.00 R1.18.2594.A1 dmi.board.name: D2594-A1 dmi.board.vendor: FUJITSU SIEMENS dmi.board.version: S26361-D2594-A1 dmi.chassis.type: 3 dmi.chassis.vendor: FUJITSU SIEMENS dmi.modalias: dmi:bvnFUJITSUSIEMENS//PhoenixTechnologiesLtd.:bvr6.00R1.18.2594.A1:bd02/05/2009:svnFUJITSUSIEMENS:pnESPRIMOE5720:pvr:rvnFUJITSUSIEMENS:rnD2594-A1:rvrS26361-D2594-A1:cvnFUJITSUSIEMENS:ct3:cvr: dmi.product.name: ESPRIMO E5720 dmi.sys.vendor: FUJITSU SIEMENS version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Mar 24 11:06:06 2019 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Receiver KEYBOARD, id 8 inputLogitech USB Receiver KEYBOARD, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon ** Attachment added: "apt preferences file for Yakkety Yak" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/1821505/+attachment/5249927/+files/yakkety.pref -- You received this bug notification becaus
[Ubuntu-x-swat] [Bug 1821820] Re: Cannot boot or install - have to use nomodeset
** Attachment added: "boot with the drm boot parameter but without nomodeset" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1821820/+attachment/5249898/+files/hang.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1821820 Title: Cannot boot or install - have to use nomodeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1821820/+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 1821820] Re: Cannot boot or install - have to use nomodeset
** Attachment added: "dmesg with nomodeset" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1821820/+attachment/5249897/+files/nomodeset.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1821820 Title: Cannot boot or install - have to use nomodeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1821820/+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 1813423] Re: Frequent system freezing with i915 error "*ERROR* Atomic update failure on pipe A"
Having same issue, freeze without any changes on screen, on Ubuntu 18.10, Dell Precision 5530. It only started recently after I encrypted my home directory and swap but I don't know if that's related. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1813423 Title: Frequent system freezing with i915 error "*ERROR* Atomic update failure on pipe A" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813423/+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 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870
*** This bug is a duplicate of bug 1819943 *** https://bugs.launchpad.net/bugs/1819943 addional clarification .. if sda6 (recovery booted or chrooted) installed grub then sda6 boots with some brief flashing normally. if sda7 or sda1 (recovery booted or chrooted or a normal boot for sda1) installed grub then sda6 would boot and lighjtdm would briefly flash onto screen and the disappear (blank screen) showing just aflashing underline cursor. so xorg video drivers appear NOT to be involved. except maybe as kernel i915 modules missing I have not checked -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1821609 Title: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1821609/+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 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870
*** This bug is a duplicate of bug 1819943 *** https://bugs.launchpad.net/bugs/1819943 this effected only the more recent installs you have miss understood the details in the initial report .. the system would boot normally as long as the grub used (installed) was from the install partition (sda6 or sda7) .. if another partition was used to install grub the lightdm would appear briefly and then crash or vanish to a underline flashing cursor the video system did work it would flash once on start-up but come back in about 5 seconds or less is the correct (ie this partition installed the grub version used) the main sda1 partition always worked .. only difference was the kernel image used .. I have not yet checked to see if the sda1 5.0.0.7 image fails currently but it worked fine before. the installation of the newer video drivers did not fix this issue!!! It remained as long as a 5.0.0.7 kernel was selected to boot sda6 or sda7 sda1 was not effected. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1821609 Title: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1821609/+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 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870
*** This bug is a duplicate of bug 1819943 *** https://bugs.launchpad.net/bugs/1819943 ** Summary changed: - lightdm login screen never appears on Intel(R) Core(TM)2 Duo CPU T5870 + lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1821609 Title: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1821609/+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 1821882] [NEW] Screen is very dark and brightness cannot be adjusted
Public bug reported: Device: Dell Precision 7530 In the BIOS, the Switchable Graphics option is deactived, which means only the nVidia GPU is used. When booting 19.04 beta live USB, the screen becomes very dark and brightness cannot be adjusted. (The same issue happens with 18.04.2) There is only a "nv_backlight" in /sys/class/backlight/ (i.e. no intel_backlight): $ ll /sys/class/backlight/ total 0 drwxr-xr-x 2 root root 0 Mar 27 09:36 ./ drwxr-xr-x 74 root root 0 Mar 27 09:28 ../ lrwxrwxrwx 1 root root 0 Mar 27 09:28 nv_backlight -> ../../devices/pci:00/:00:01.0/:01:00.0/drm/card0/card0-eDP-1/nv_backlight/ Trying to manually change brightness doesn't do anything: $ sudo su root@ubuntu:/home/ubuntu# cd /sys/class/backlight/nv_backlight root@ubuntu:/sys/class/backlight/nv_backlight# ll total 0 drwxr-xr-x 3 root root0 Mar 27 09:28 ./ drwxr-xr-x 4 root root0 Mar 27 09:28 ../ -r--r--r-- 1 root root 4096 Mar 27 09:37 actual_brightness -rw-r--r-- 1 root root 4096 Mar 27 09:37 bl_power -rw-r--r-- 1 root root 4096 Mar 27 09:28 brightness lrwxrwxrwx 1 root root0 Mar 27 09:37 device -> ../../card0-eDP-1/ -r--r--r-- 1 root root 4096 Mar 27 09:28 max_brightness drwxr-xr-x 2 root root0 Mar 27 09:28 power/ lrwxrwxrwx 1 root root0 Mar 27 09:28 subsystem -> ../../../../../../../../class/backlight/ -r--r--r-- 1 root root 4096 Mar 27 09:28 type -rw-r--r-- 1 root root 4096 Mar 27 09:28 uevent root@ubuntu:/sys/class/backlight/nv_backlight# cat actual_brightness 100 root@ubuntu:/sys/class/backlight/nv_backlight# cat brightness 100 root@ubuntu:/sys/class/backlight/nv_backlight# cat max_brightness 100 root@ubuntu:/sys/class/backlight/nv_backlight# echo 50 > brightness root@ubuntu:/sys/class/backlight/nv_backlight# cat brightness 50 Although the value is changed, the screen brightness doesn't change. in dmesg, I can see the following: [0.241878] ACPI: Added _OSI(Module Device) [0.241878] ACPI: Added _OSI(Processor Device) [0.241878] ACPI: Added _OSI(3.0 _SCP Extensions) [0.241878] ACPI: Added _OSI(Processor Aggregator Device) [0.241878] ACPI: Added _OSI(Linux-Dell-Video) [0.241878] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio) [0.241878] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics) [0.286326] ACPI BIOS Error (bug): Failure creating [\_SB.PCI0.XHC.RHUB.HS01._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324) [0.286332] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20181213/psobject-221) [0.286334] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.286336] ACPI BIOS Error (bug): Failure creating [\_SB.PCI0.XHC.RHUB.HS01._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324) [0.286339] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20181213/psobject-221) [0.286340] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.287096] ACPI BIOS Error (bug): Failure creating [\_SB.PCI0.XHC.RHUB.HS02._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324) [0.287099] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20181213/psobject-221) [0.287101] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.287102] ACPI BIOS Error (bug): Failure creating [\_SB.PCI0.XHC.RHUB.HS02._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324) [0.287105] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20181213/psobject-221) [0.287106] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.287858] ACPI BIOS Error (bug): Failure creating [\_SB.PCI0.XHC.RHUB.HS03._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324) [0.287861] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20181213/psobject-221) [0.287863] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.287864] ACPI BIOS Error (bug): Failure creating [\_SB.PCI0.XHC.RHUB.HS03._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324) [0.287867] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20181213/psobject-221) [0.287869] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.288614] ACPI BIOS Error (bug): Failure creating [\_SB.PCI0.XHC.RHUB.HS04._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324) [0.288617] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20181213/psobject-221) [0.288619] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.288620] ACPI BIOS Error (bug): Failure creating [\_SB.PCI0.XHC.RHUB.HS04._PLD], AE_ALREADY_EXISTS (20181213/dswload2-324) [0.288623] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20181213/psobject-221) [0.288625] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.289376] ACPI BIOS Error (bug): Failure creating [\_SB.PCI0.XHC.RHUB.HS05._UPC], AE_ALREADY_EXISTS (20181213/dswload2-324) [0.289379] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20181213/psobject-221) [0.289381] ACPI: Skipping parse of AML opcode: Method (0x0014) [0.289382] ACPI BIOS Error (bug): Failure creating [\_SB.PCI0.XHC.RHUB
[Ubuntu-x-swat] [Bug 1821863] Re: Need to add Intel CML related pci-id's
** Summary changed: - Need to add Intel CML related pci-id's to the oem-kernel + Need to add Intel CML related pci-id's ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Also affects: libdrm (Ubuntu) Importance: Undecided Status: New ** Description changed: Please make it happen in the coming oem-kernel as there will be a flood of Intel CML platforms that would need it. Thank you. + + The same is needed for the rest of the stack. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1821863 Title: Need to add Intel CML related pci-id's To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1821863/+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
