[Bug 1755304] Re: Regression: vga term no longer active on Cavium ThunderX
Closing as Invalid, as I believe the problem is in firmware. Will reopen if that proves false. ** Changed in: linux (Ubuntu Artful) Status: Triaged => Invalid ** Changed in: linux (Ubuntu Bionic) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755304 Title: Regression: vga term no longer active on Cavium ThunderX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755304] Re: Regression: vga term no longer active on Cavium ThunderX
What should be happening here is that: 1) The efifb driver initializes, detects a device. 2) The console driver makes the efifb an active console, and output appears 3) Later, the astdrmfb initializes, detects a device 4) The kernel checks for an overlap in the framebuffers used by efifb & astdrmfb, to see if they're actually the same physical device. 5) Overlap is found (they are the same device on ThunderX), so the console driver actives the preferred astdrmfb driver instead 6) Console settings are adjusted, output continues Indeed, this works just like this on a Gigabyte R120 system (same SoC) - but not on the Cavium CRB. The problem appears to be that UEFI on the CRB claims the efi framebuffer start address is at 0x1000 - when it is really at 0x88101000 (that's what the Gigabyte system shows). The kernel assumes this is valid and the efifb driver starts using that memory and the console driver activates this device... but this isn't the real location, so nothing appears on VGA. When the astdrm driver loads, the kernel finds no overlap with the astdrm driver (which is using the correct window), therefore the console does not attempt to switch to it, and we continue to not have output. If I hack the driver to add the 0x8810 prefix, I do begin to see output at step #2 on the CRB, and the remaining steps work as they should. So, my assumption is that the framebuffer base is just truncated in firmware. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755304 Title: Regression: vga term no longer active on Cavium ThunderX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755304] Re: Regression: vga term no longer active on Cavium ThunderX
** Changed in: linux (Ubuntu Artful) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Tags added: artful bionic kernel-da-key -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755304 Title: Regression: vga term no longer active on Cavium ThunderX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755304] Re: Regression: vga term no longer active on Cavium ThunderX
** Changed in: linux (Ubuntu Bionic) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755304 Title: Regression: vga term no longer active on Cavium ThunderX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
