[Bug 1885267] Re: Amd64 ppa kernel mainline build failing self test.
Added Ubuntu Kernel PPA to the notification list. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885267 Title: Amd64 ppa kernel mainline build failing self test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885267] Re: Amd64 ppa kernel mainline build failing self test.
This is not a bug with the kernel, but with the build process for kernels in the mainline ppa. As such, logs from my machine are not relevant, and the original report links to the relevant build logs, and has relevant extracts from those logs. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885267 Title: Amd64 ppa kernel mainline build failing self test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885267] [NEW] Amd64 ppa kernel mainline build failing self test.
Public bug reported: Since kernel 5.6.18 / 5.7.2 and onwards, the amd64 kernel builds (and the s390x builds) in the kernel ppa at https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D are failing self tests "Test amd64/self-tests failed (rc=2, on=amd64, time=0:00:57, log=amd64 /self-tests/log)" The log shows: ++ INSTALL headers CC test_stub.o BINARY test_verifier test_verifier.c:25:10: fatal error: sys/capability.h: No such file or directory 25 | #include | ^~ compilation terminated. make[2]: *** [Makefile:398: /home/kernel/COD/linux/tools/testing/selftests/bpf/test_verifier] Error 1 make[2]: Leaving directory '/home/kernel/COD/linux/tools/testing/selftests/bpf' make[1]: *** [Makefile:157: all] Error 2 make[1]: Leaving directory '/home/kernel/COD/linux/tools/testing/selftests' make: *** [debian/rules.d/1-maintainer.mk:170: compileselftests] Error 2 ** Affects: ubuntu Importance: Undecided Status: New ** Tags: build mainline ppa -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885267 Title: Amd64 ppa kernel mainline build failing self test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1885267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820222] Re: Unable to boot LiveCD ISO from UDF filesystem
It is an UEFI system, but NOT SecureBoot enabled. I understand the reasons why your might not want to do this for SecureBoot enabled systems (I might not like them, but I do understand them). In this case, I get the capability I want by making an ext2-formatted partition on the not-easily-removable persistent storage device and putting the ISO images there. It struck me that it should be possible to use a UDF formatted partition - mainly because I sometimes have to rescue broken systems, and it is convenient to be able to write out ISO files that are larger than 2 Gigabytes on removable media that are 'cross-platform' readable and writeable. Thank you for taking the time to comment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820222 Title: Unable to boot LiveCD ISO from UDF filesystem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1820222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830961] Re: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible]
It is nice to see this resolved for 5.3-rc1. Excuse my ignorance of the process, but will this patch be (perhaps automagically) backported so the next iteration of the 5.2 (and maybe 5.1) stable kernels for amd64 and i386 also get generated successfully? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830961 Title: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect- branch’ and ‘-fcf-protection’ are not compatible] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1830961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837036] Re: Mainline Ubuntu Linux kernel builds failing for >= 5.1.17 and >= 5.2 on AMD64 and i386
*** This bug is a duplicate of bug 1830961 *** https://bugs.launchpad.net/bugs/1830961 According to this comment ( https://www.phoronix.com/forums/forum/software/general-linux-open- source/1113503-linux-5-2-1-released-for-riding-the-latest-stable- kernel?p=1113668#post1113668 )at Phoronix, the underlying cause is: "Ubuntu is using -fcf-protection by default now and that isn't compatible with -mindirect-branch that the kernel uses for retpolines. " Bug 1830961 appears to be an earllier report, so this is a duplicate of that bug, as is bug 1836373 ** This bug has been marked a duplicate of bug 1830961 Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837036 Title: Mainline Ubuntu Linux kernel builds failing for >= 5.1.17 and >= 5.2 on AMD64 and i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837036/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837036] Re: Mainline Ubuntu Linux kernel builds failing for >= 5.1.17 and >= 5.2 on AMD64 and i386
** Tags added: amd64 build kernel mainline -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837036 Title: Mainline Ubuntu Linux kernel builds failing for >= 5.1.17 and >= 5.2 on AMD64 and i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837036/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837036] Re: Mainline Ubuntu Linux kernel builds failing for >= 5.1.17 and >= 5.2 on AMD64 and i386
The bug is in the Ubuntu controlled mainline kernel build system, and a link to the logs generated by that system has been provided. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837036 Title: Mainline Ubuntu Linux kernel builds failing for >= 5.1.17 and >= 5.2 on AMD64 and i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837036/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837036] [NEW] Mainline Ubuntu Linux kernel builds failing for >= 5.1.17 and >= 5.2 on AMD64 and i386
Public bug reported: As subject says, the compiled Ubuntu kernels for >= 5.1.17 and >= 5.2 on AMD64 and i386 are failing to build. Build logs at (for example): https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2.1/BUILD.LOG.amd64 https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2.1/BUILD.LOG.i386 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: i386 ** Tags added: build ** Tags removed: build ** Tags added: i386 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837036 Title: Mainline Ubuntu Linux kernel builds failing for >= 5.1.17 and >= 5.2 on AMD64 and i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837036/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1514120] Re: Ubiquity needs to not disable the LVM and encryption options for dual boot
/boot can be encrypted. See the link you yourself gave two messages above. In my case, I have a non-encrypted EFI System Partition (ESP), with the appropriate UEFI GRUB 2 loader with the LVM and LUKS V1 modules (GRUB 2 does not currently support booting from LUKS2 devices). The rest of the disk is a single LUKS V1 partition. GRUB happily opens this, and finds the LVM set up, and /boot is one of the LVM volumes I have set up (swap is another). The downside of this is that you need to give a LUKS V1 password TWICE: once for GRUB to open the LUKS partition, then the LVM volume and mount /boot; then a second time after GRUB has passed control to the linux kernel in the initramfs as the linux kernel needs to go through the device discovery process and remount the drives. It is possible to set things up so that the linux kernel can open the LUKS partition with a keyfile - the technique is outlined in this linuxquestions.org answer: https://www.linuxquestions.org/questions/linux-security-4/security- implications-of-keyfiles-on-a-luks-encrypted-boot-4175614861 ; and it in turn links to two other documents which describe things in more detail: https://www.pavelkogan.com/2014/05/23/luks-full-disk-encryption/ https://www.pavelkogan.com/2015/01/25/linux-mint-encryption/ The above links point out that when the system is booted, the keyfile is unencrypted with a copy on the ramdisk, which is likely unacceptable to some people. Holding the keyfile on a separate USB drive which can be removed could be a solution for some people. It would be helpful if GRUB2 and other bootloaders had a standard method by which LUKS keys could be passed in a secure manner to the kernel being booted, but that is beyond the scope of this bug. As it is, 'full disk encryption' is significantly less functional on GNU/Linux than Bitlocker is on Microsoft Windows. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1514120 Title: Ubiquity needs to not disable the LVM and encryption options for dual boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1514120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565950] Re: Grub 2 fails to boot a kernel on a luks encrypted volume with Secure Boot enabled
This could affect people using 'non-standard' modules not included in the standard distribution. For example, I use NILFS2 for all my filesystems, and if the signed grubx64.efi does not include that, I won't be able to boot. It might be a bit esoteric, but it points to a general problem: either all possible modules are included in the signed grub64x.efi, which some people might object to on size and/or attack surface grounds, or some are omitted, causing problems for people who wish to boot securely with modules not included in the standard distribution. I vote for including all modules, but I have no problems with the size grub64x.efi becomes, and I'm less worried about the attack surface than some others might be. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565950 Title: Grub 2 fails to boot a kernel on a luks encrypted volume with Secure Boot enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1565950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820222] [NEW] Unable to boot LiveCD ISO from UDF filesystem
Public bug reported: Using Lubuntu 18.04.2 (#lsb_release -a -> Description: Ubuntu 18.04.2 LTS) In order to resolve a problem with booting after 'Software Updater' updated the system, I needed to boot from a LiveCD and chroot to resolve the boot issue. GRUB allows systems to boot from an ISO image located on an accessible filesystem, so if you have sufficient disk space, you do not need to write out to a USB flash drive. I downloaded the Lubuntu 18.0.2 from http://cdimage.ubuntu.com/lubuntu/releases/18.04.2/release/ onto a spare partition formatted as UDF version 2.0.1 and confirmed the integrity of the download with sha256sum On attempting to boot from the ISO directly using GRUB, the boot fails. As I don't have a serial console I can't give the exact error. As I knew I could boot from other ISO images on a separate ext2 partition, I copied the Lubuntu 18.04.2 ISO to the ext2 partition. Attempting to boot with the ISO in this location worked, I got a LiveCD system from which I could then do the necessary chroot operations to get my system working again. GRUB script - fails when ISO is on UDF formatted partition, succeeds when on ext2 partition setparams 'Lubuntu 18.04.2 ISO' insmod iso9660 insmod ext2 insmod udf insmod part_gpt set isofile="/lubuntu-18.04.2-desktop-amd64.iso" loopback loop (hd1,gpt5)$isofile linux (loop)/casper/vmlinuz boot=casper iso-scan/filename=$isofile noprompt noeject toram -- initrd (loop)/casper/initrd I suspect the iso has been produced without including udf filesystem drivers somewhere. I suggest supporting UDF would be helpful as many people use UDF as a cross-platform alternative to FAT as it supports larger file sizes than FAT. ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820222 Title: Unable to boot LiveCD ISO from UDF filesystem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1820222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761751] Re: Black screen on 18.04 + AMD RX460
Problem persists in kernel 4.17-rc6 from http://kernel.ubuntu.com /~kernel-ppa/mainline/v4.17-rc6/ #uname -r 4.17.0-041700rc6-generic #cat /proc/cmdline BOOT_IMAGE=/vmlinuz-4.17.0-041700rc6-generic amdgpu.cik_support=1 radeon.cik_support=0 amdgpu.dc=1 #ls /sys/class/drm card0 card0-eDP-1 card0-HDMI-A-1 renderD128 ttm version <<--***NOTE no VGA*** #dmesg | grep drm [2.326305] [drm] radeon kernel modesetting enabled. [2.327644] fb: switching to radeondrmfb from EFI VGA [2.372539] [drm] amdgpu kernel modesetting enabled. [2.380846] [drm] initializing kernel modesetting (KAVERI 0x1002:0x130A 0x17AA:0x3988 0x00). [2.380878] [drm] register mmio base: 0xF0B0 [2.380880] [drm] register mmio size: 262144 [2.380889] [drm] add ip block number 0 [2.380892] [drm] add ip block number 1 [2.380894] [drm] add ip block number 2 [2.380897] [drm] add ip block number 3 [2.380900] [drm] add ip block number 4 [2.380903] [drm] add ip block number 5 [2.380906] [drm] add ip block number 6 [2.380909] [drm] add ip block number 7 [2.380911] [drm] add ip block number 8 [2.404721] [drm] BIOS signature incorrect 0 0 [2.404832] [drm] vm size is 64 GB, 2 levels, block size is 10-bit, fragment size is 9-bit [2.404855] [drm] Detected VRAM RAM=1024M, BAR=1024M [2.404858] [drm] RAM width 64bits UNKNOWN [2.405130] [drm] amdgpu: 1024M of VRAM memory ready [2.405133] [drm] amdgpu: 3072M of GTT memory ready. [2.405145] [drm] GART: num cpu pages 262144, num gpu pages 262144 [2.405180] [drm] PCIE GART of 1024M enabled (table at 0x00F40004). [2.405266] [drm] Internal thermal controller without fan control [2.405269] [drm] amdgpu: dpm initialized [2.406296] [drm] Found UVD firmware Version: 1.55 Family ID: 9 [2.406649] [drm] Found VCE firmware Version: 50.10 Binary ID: 2 [2.407995] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:3! type 0 expected 3 [2.408115] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:4! type 0 expected 3 [2.408204] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:5! type 0 expected 3 [2.408324] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:6! type 0 expected 3 [2.420247] [drm] Display Core initialized with v3.1.38! [2.426796] [drm] SADs count is: -2, don't need to read it [2.427373] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [2.427379] [drm] Driver supports precise vblank timestamp query. [2.446239] [drm] UVD initialized successfully. [2.561743] [drm] VCE initialized successfully. [2.569100] [drm] fb mappable at 0xA042A000 [2.569106] [drm] vram apper at 0xA000 [2.569109] [drm] size 8294400 [2.569111] [drm] fb depth is 24 [2.569113] [drm]pitch is 7680 [2.569233] fbcon: amdgpudrmfb (fb0) is primary device [2.657000] amdgpu :00:01.0: fb0: amdgpudrmfb frame buffer device [2.678478] [drm] Initialized amdgpu 3.25.0 20150101 for :00:01.0 on minor 0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761751 Title: Black screen on 18.04 + AMD RX460 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761751] Re: Black screen on 18.04 + AMD RX460
Problem persists in kernel 4.16.11 #uname -r 4.16.11-041611-generic #ls /sys/class/drm card0 card0-eDP-1 card0-HDMI-A-1 renderD128 ttm version #dmesg | grep drm [1.783188] [drm] radeon kernel modesetting enabled. [1.784832] fb: switching to radeondrmfb from EFI VGA [1.831813] [drm] amdgpu kernel modesetting enabled. [1.840215] [drm] initializing kernel modesetting (KAVERI 0x1002:0x130A 0x17AA:0x3988 0x00). [1.840237] [drm] register mmio base: 0xF0B0 [1.840239] [drm] register mmio size: 262144 [1.865264] [drm] BIOS signature incorrect 0 0 [1.865367] [drm] vm size is 64 GB, 2 levels, block size is 10-bit, fragment size is 9-bit [1.865387] [drm] Detected VRAM RAM=1024M, BAR=1024M [1.865390] [drm] RAM width 64bits UNKNOWN [1.865779] [drm] amdgpu: 1024M of VRAM memory ready [1.865783] [drm] amdgpu: 3072M of GTT memory ready. [1.865807] [drm] GART: num cpu pages 262144, num gpu pages 262144 [1.865894] [drm] PCIE GART of 1024M enabled (table at 0x00F40004). [1.866040] [drm] Internal thermal controller without fan control [1.866046] [drm] amdgpu: dpm initialized [1.867349] [drm] Found UVD firmware Version: 1.55 Family ID: 9 [1.867789] [drm] Found VCE firmware Version: 50.10 Binary ID: 2 [1.869984] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:3! type 0 expected 3 [1.870074] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:4! type 0 expected 3 [1.870200] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:5! type 0 expected 3 [1.870309] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:6! type 0 expected 3 [1.884255] [drm] Display Core initialized with v3.1.27! [1.891240] [drm] SADs count is: -2, don't need to read it [1.891668] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [1.891674] [drm] Driver supports precise vblank timestamp query. [1.910078] [drm] UVD initialized successfully. [2.02] [drm] VCE initialized successfully. [2.056074] [drm] fb mappable at 0xA042A000 [2.056083] [drm] vram apper at 0xA000 [2.056087] [drm] size 8294400 [2.056090] [drm] fb depth is 24 [2.056093] [drm]pitch is 7680 [2.056218] fbcon: amdgpudrmfb (fb0) is primary device [2.113975] amdgpu :00:01.0: fb0: amdgpudrmfb frame buffer device [2.130285] [drm] Initialized amdgpu 3.23.0 20150101 for :00:01.0 on minor 0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761751 Title: Black screen on 18.04 + AMD RX460 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761751] Re: Black screen on 18.04 + AMD RX460
Problem still exists in 4.16.10 kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16.10/ (#uname -r output is 4.16.10-041610-generic ) dmesg output gives same error output as before when amdgpu.dc=1 [1.866312] [drm] amdgpu: 1024M of VRAM memory ready [1.866316] [drm] amdgpu: 3072M of GTT memory ready. [1.866332] [drm] GART: num cpu pages 262144, num gpu pages 262144 [1.866382] [drm] PCIE GART of 1024M enabled (table at 0x00F40004). [1.866500] [drm] Internal thermal controller without fan control [1.866504] [drm] amdgpu: dpm initialized [1.867685] [drm] Found UVD firmware Version: 1.55 Family ID: 9 [1.868113] [drm] Found VCE firmware Version: 50.10 Binary ID: 2 [1.870125] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:3! type 0 expected 3 [1.870214] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:4! type 0 expected 3 [1.870337] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:5! type 0 expected 3 [1.870445] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:6! type 0 expected 3 [1.880211] [drm] Display Core initialized with v3.1.27! [1.887329] [drm] SADs count is: -2, don't need to read it [1.887755] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [1.887761] [drm] Driver supports precise vblank timestamp query. [1.906232] [drm] UVD initialized successfully. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761751 Title: Black screen on 18.04 + AMD RX460 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761751] Re: Black screen on 18.04 + AMD RX460
Problem still exists in 4.16.9 kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.16.9/ (#uname -r output is 4.16.9-041609-generic ) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761751 Title: Black screen on 18.04 + AMD RX460 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761825] Re: amdgpu.dc fails on AMD (Kaveri) A10-7300
Tested on 4.16.8-041608-generic, and issue remains. See https://bugs.launchpad.net/ubuntu/bionic/+source/linux/+bug/1761751 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761825 Title: amdgpu.dc fails on AMD (Kaveri) A10-7300 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761751] Re: Black screen on 18.04 + AMD RX460
Some information from me, using 4.16.8 kernel System is Lenovo Z50-75 laptop with AMD-A10 cpu (Kaveri) and both HDMI and VGA ports. I use the VGA port to which is connected an Acer X223HQ display, capable of displaying up to 1920x1080. The laptop screen is also 1920x1080 If system is booted with the following kernel options amdgpu.cik_support=1 radeon.cik_support=0 amdgpu.dc=1 I get a black/blank VGA screen. If system is booted with amdgpu.cik_support=1 radeon.cik_support=0 amdgpu.dc=0 I get a working VGA display in addition to the laptop screen. With amdgpu.dc=1 the contents of /sys/class/drm are: card0 card0-eDP-1 card0-HDMI-A-1 renderD128 ttm version With amdgpu.dc=0 the contents of /sys/class/drm are: card0 card0-eDP-1 card0-HDMI-A-1 card0-VGA-1 renderD128 ttm version With amdgpu.dc=0, dmesg lines containing 'drm' are [1.749135] [drm] radeon kernel modesetting enabled. [1.750430] fb: switching to radeondrmfb from EFI VGA [1.795937] [drm] amdgpu kernel modesetting enabled. [1.804524] [drm] initializing kernel modesetting (KAVERI 0x1002:0x130A 0x17AA:0x3988 0x00). [1.804544] [drm] register mmio base: 0xF0B0 [1.804547] [drm] register mmio size: 262144 [1.828764] [drm] BIOS signature incorrect 0 0 [1.829561] [drm] vm size is 64 GB, 2 levels, block size is 10-bit, fragment size is 9-bit [1.829586] [drm] Detected VRAM RAM=1024M, BAR=1024M [1.829589] [drm] RAM width 64bits UNKNOWN [1.829727] [drm] amdgpu: 1024M of VRAM memory ready [1.829731] [drm] amdgpu: 3072M of GTT memory ready. [1.829747] [drm] GART: num cpu pages 262144, num gpu pages 262144 [1.829797] [drm] PCIE GART of 1024M enabled (table at 0x00F40004). [1.829885] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [1.829888] [drm] Driver supports precise vblank timestamp query. [1.829920] [drm] Internal thermal controller without fan control [1.829923] [drm] amdgpu: dpm initialized [1.830640] [drm] amdgpu atom DIG backlight initialized [1.830644] [drm] AMDGPU Display Connectors [1.830647] [drm] Connector 0: [1.830649] [drm] VGA-1 [1.830651] [drm] HPD2 [1.830654] [drm] DDC: 0x1950 0x1950 0x1951 0x1951 0x1952 0x1952 0x1953 0x1953 [1.830657] [drm] Encoders: [1.830659] [drm] CRT1: INTERNAL_UNIPHY2 [1.830661] [drm] CRT1: NUTMEG [1.830663] [drm] Connector 1: [1.830665] [drm] HDMI-A-1 [1.830667] [drm] HPD3 [1.830670] [drm] DDC: 0x1954 0x1954 0x1955 0x1955 0x1956 0x1956 0x1957 0x1957 [1.830673] [drm] Encoders: [1.830675] [drm] DFP1: INTERNAL_UNIPHY2 [1.830677] [drm] Connector 2: [1.830679] [drm] eDP-1 [1.830681] [drm] HPD1 [1.830684] [drm] DDC: 0x194c 0x194c 0x194d 0x194d 0x194e 0x194e 0x194f 0x194f [1.830687] [drm] Encoders: [1.830690] [drm] LCD1: INTERNAL_UNIPHY [1.831974] [drm] Found UVD firmware Version: 1.55 Family ID: 9 [1.832424] [drm] Found VCE firmware Version: 50.10 Binary ID: 2 [1.923930] [drm] UVD initialized successfully. [2.042436] [drm] VCE initialized successfully. [3.097431] [drm] fb mappable at 0xA0428000 [3.097436] [drm] vram apper at 0xA000 [3.097438] [drm] size 8294400 [3.097440] [drm] fb depth is 24 [3.097442] [drm]pitch is 7680 [3.098563] fbcon: amdgpudrmfb (fb0) is primary device [6.593703] amdgpu :00:01.0: fb0: amdgpudrmfb frame buffer device [6.610690] [drm] Initialized amdgpu 3.23.0 20150101 for :00:01.0 on minor 0 With amdgpu.dc=1, dmesg lines containing drm are: [1.768255] [drm] radeon kernel modesetting enabled. [1.770696] fb: switching to radeondrmfb from EFI VGA [1.816131] [drm] amdgpu kernel modesetting enabled. [1.824756] [drm] initializing kernel modesetting (KAVERI 0x1002:0x130A 0x17AA:0x3988 0x00). [1.824788] [drm] register mmio base: 0xF0B0 [1.824791] [drm] register mmio size: 262144 [1.849601] [drm] BIOS signature incorrect 0 0 [1.849724] [drm] vm size is 64 GB, 2 levels, block size is 10-bit, fragment size is 9-bit [1.849746] [drm] Detected VRAM RAM=1024M, BAR=1024M [1.849749] [drm] RAM width 64bits UNKNOWN [1.850061] [drm] amdgpu: 1024M of VRAM memory ready [1.850065] [drm] amdgpu: 3072M of GTT memory ready. [1.850080] [drm] GART: num cpu pages 262144, num gpu pages 262144 [1.850131] [drm] PCIE GART of 1024M enabled (table at 0x00F40004). [1.850256] [drm] Internal thermal controller without fan control [1.850260] [drm] amdgpu: dpm initialized [1.851672] [drm] Found UVD firmware Version: 1.55 Family ID: 9 [1.852176] [drm] Found VCE firmware Version: 50.10 Binary ID: 2 [1.854405] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:3! type 0 expected 3 [1.854493] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector
[Bug 1761825] Re: amdgpu.dc fails on AMD (Kaveri) A10-7300
apport information ** Tags added: apport-collected xenial ** Description changed: Booting kernel 4.16 ( BOOT_IMAGE=/vmlinuz-4.16.0-041600-generic ) with external monitor attached to VGA port of Lenovo Ideapad Z50-75 (AMD Kaveri A10-7300) results in blank external display when amdgpu.ci_support is forced (i.e. radeon disabled). key dmesg messages are: [1.897177] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:3! type 0 expected 3 [1.897266] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:4! type 0 expected 3 [1.897380] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:5! type 0 expected 3 [1.897489] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:6! type 0 expected 3 Kernel boot options are: amdgpu.cik_support=1 radeon.cik_support=0 If I boot the same kernel with the following options: amdgpu.cik_support=1 radeon.cik_support=0 amdgpu.dc=0 The VGA attached display works. Attached in the tar are: version.log - output of cat /proc/version lspci-vnvn.log - output of sudo lscpi -vnvn dmesg_amdgpu.dc-(default-one) - dmesg from boot with amdgpu.cik_support forced and amdgpu.dc left to deafult dmesg_amdgpu.dc-0 - dmesg from boot with amdgpu.cik_support forced and amdgpu.dc disabled + --- + ApportVersion: 2.20.1-0ubuntu2.15 + Architecture: amd64 + CurrentDesktop: LXDE + DistroRelease: Ubuntu 16.04 + InstallationDate: Installed on 2017-09-05 (213 days ago) + InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) + JournalErrors: + Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Failed to search journal ACL: Operation not supported + No journal files were opened due to insufficient permissions. + Package: linux (not installed) + Tags: xenial + Uname: Linux 4.16.0-041600-generic x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip kismet libvirtd lpadmin plugdev sambashare scanner sudo + _MarkForUpload: True ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1761825/+attachment/5104719/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761825 Title: amdgpu.dc fails on AMD (Kaveri) A10-7300 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761825] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1761825/+attachment/5104720/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761825 Title: amdgpu.dc fails on AMD (Kaveri) A10-7300 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761825] [NEW] amdgpu.dc fails on AMD (Kaveri) A10-7300
Public bug reported: Booting kernel 4.16 ( BOOT_IMAGE=/vmlinuz-4.16.0-041600-generic ) with external monitor attached to VGA port of Lenovo Ideapad Z50-75 (AMD Kaveri A10-7300) results in blank external display when amdgpu.ci_support is forced (i.e. radeon disabled). key dmesg messages are: [1.897177] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:3! type 0 expected 3 [1.897266] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:4! type 0 expected 3 [1.897380] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:5! type 0 expected 3 [1.897489] [drm:construct [amdgpu]] *ERROR* construct: Invalid Connector ObjectID from Adapter Service for connector index:6! type 0 expected 3 Kernel boot options are: amdgpu.cik_support=1 radeon.cik_support=0 If I boot the same kernel with the following options: amdgpu.cik_support=1 radeon.cik_support=0 amdgpu.dc=0 The VGA attached display works. Attached in the tar are: version.log - output of cat /proc/version lspci-vnvn.log - output of sudo lscpi -vnvn dmesg_amdgpu.dc-(default-one) - dmesg from boot with amdgpu.cik_support forced and amdgpu.dc left to deafult dmesg_amdgpu.dc-0 - dmesg from boot with amdgpu.cik_support forced and amdgpu.dc disabled ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amdgpu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761825 Title: amdgpu.dc fails on AMD (Kaveri) A10-7300 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761825/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 155099] Re: gparted crashed with SIGSEGV in std::basic_stringchar, std::char_traitschar, std::allocatorchar ::basic_string()
*** This bug is a duplicate of bug 147028 *** https://bugs.launchpad.net/bugs/147028 ** Attachment added: CoreDump.gz http://launchpadlibrarian.net/10084901/CoreDump.gz ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/10084902/Dependencies.txt ** Attachment added: Disassembly.txt http://launchpadlibrarian.net/10084903/Disassembly.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/10084905/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/10084906/ProcStatus.txt ** Attachment added: Registers.txt http://launchpadlibrarian.net/10084907/Registers.txt ** Attachment added: Stacktrace.txt http://launchpadlibrarian.net/10084908/Stacktrace.txt ** Attachment added: ThreadStacktrace.txt http://launchpadlibrarian.net/10084909/ThreadStacktrace.txt -- gparted crashed with SIGSEGV in std::basic_stringchar, std::char_traitschar, std::allocatorchar ::basic_string() https://bugs.launchpad.net/bugs/155099 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 155099] gparted crashed with SIGSEGV in std::basic_stringchar, std::char_traitschar, std::allocatorchar ::basic_string()
*** This bug is a duplicate of bug 147028 *** https://bugs.launchpad.net/bugs/147028 Public bug reported: Binary package hint: gparted Gutsy (7.10) LiveCD, attempting to resize ntfs partition. After (failed) dry run, Gparted crashes ProblemType: Crash Architecture: i386 CrashCounter: 1 Date: Sat Oct 20 21:02:49 2007 DistroRelease: Ubuntu 7.10 ExecutablePath: /usr/bin/gparted NonfreeKernelModules: cdrom Package: gparted 0.3.3-2ubuntu6 PackageArchitecture: i386 ProcCmdline: gparted ProcCwd: /home/ubuntu ProcEnviron: SHELL=/bin/bash PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin LANG=en_US.UTF-8 Signal: 11 SourcePackage: gparted StacktraceTop: std::basic_stringchar, std::char_traitschar, std::allocatorchar ::basic_string () from /usr/lib/libstdc++.so.6 Glib::ustring::ustring () from /usr/lib/libglibmm-2.4.so.1 ?? () ?? () Glib::SignalProxyNormal::slot0_void_callback () Title: gparted crashed with SIGSEGV in std::basic_stringchar, std::char_traitschar, std::allocatorchar ::basic_string() Uname: Linux ubuntu 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux UserGroups: ** Affects: gparted (Ubuntu) Importance: Medium Status: New ** Tags: apport-crash -- gparted crashed with SIGSEGV in std::basic_stringchar, std::char_traitschar, std::allocatorchar ::basic_string() https://bugs.launchpad.net/bugs/155099 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 68212] Re: Bad refresh rate showed in monitor and display setup
I can confirm this problem exists - see extensive documentation at this thread in Ubuntu forums: http://ubuntuforums.org/showthread.php?t=392425 Regards, semreh -- Bad refresh rate showed in monitor and display setup https://launchpad.net/bugs/68212 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
