On Fri, Dec 15, 2023 at 5:37 PM Christian König
wrote:
>
> I have no idea :)
>
> From the logs I can see that the AMDGPU now has the proper BARs assigned:
>
> [5.722015] pci :03:00.0: [1002:73df] type 00 class 0x038000
> [5.722051] pci :03:00.0: reg 0x10: [mem
>
Am 15.12.23 um 12:45 schrieb Mikhail Gavrilov:
On Tue, Feb 28, 2023 at 5:43 PM Christian König
wrote:
The point is it doesn't need to talk to the amdgpu hardware. What it
does is that it talks to the good old VGA/VESA emulation and that just
happens to be still enabled by the BIOS/GRUB.
And
On Tue, Feb 28, 2023 at 5:43 PM Christian König
wrote:
>
> The point is it doesn't need to talk to the amdgpu hardware. What it
> does is that it talks to the good old VGA/VESA emulation and that just
> happens to be still enabled by the BIOS/GRUB.
>
> And that VGA/VESA emulation doesn't need any
Am 28.02.23 um 10:52 schrieb Mikhail Gavrilov:
On Mon, Feb 27, 2023 at 3:22 PM Christian König
Unfortunately yes. We could clean that up a bit more so that you don't
run into a BUG() assertion, but what essentially happens here is that we
completely fail to talk to the hardware.
In this
On Mon, Feb 27, 2023 at 3:22 PM Christian König
>
> Unfortunately yes. We could clean that up a bit more so that you don't
> run into a BUG() assertion, but what essentially happens here is that we
> completely fail to talk to the hardware.
>
> In this situation we can't even re-enable vesa or
Am 24.02.23 um 17:21 schrieb Mikhail Gavrilov:
On Fri, Feb 24, 2023 at 8:31 PM Christian König
wrote:
Sorry I totally missed that you attached the full dmesg to your original
mail.
Yeah, the driver did fail gracefully. But then X doesn't come up and
then gdm just dies.
Are you sure that
On Fri, Feb 24, 2023 at 8:31 PM Christian König
wrote:
>
> Sorry I totally missed that you attached the full dmesg to your original
> mail.
>
> Yeah, the driver did fail gracefully. But then X doesn't come up and
> then gdm just dies.
Are you sure that these messages should be present when the
Am 24.02.23 um 13:29 schrieb Christian König:
Am 24.02.23 um 09:38 schrieb Mikhail Gavrilov:
On Fri, Feb 24, 2023 at 12:13 PM Christian König
wrote:
Hi Mikhail,
this is pretty clearly a problem with the system and/or it's BIOS and
not the GPU hw or the driver.
The option pci=nocrs makes the
Hi Mikhail,
this is pretty clearly a problem with the system and/or it's BIOS and
not the GPU hw or the driver.
The option pci=nocrs makes the kernel ignore additional resource windows
the BIOS reports through ACPI. This then most likely leads to problems
with amdgpu because it can't bring
Am 24.02.23 um 09:38 schrieb Mikhail Gavrilov:
On Fri, Feb 24, 2023 at 12:13 PM Christian König
wrote:
Hi Mikhail,
this is pretty clearly a problem with the system and/or it's BIOS and
not the GPU hw or the driver.
The option pci=nocrs makes the kernel ignore additional resource windows
the
On Fri, Feb 24, 2023 at 12:13 PM Christian König
wrote:
>
> Hi Mikhail,
>
> this is pretty clearly a problem with the system and/or it's BIOS and
> not the GPU hw or the driver.
>
> The option pci=nocrs makes the kernel ignore additional resource windows
> the BIOS reports through ACPI. This then
Hi Mikhail,
this is pretty clearly a problem with the system and/or it's BIOS and
not the GPU hw or the driver.
The option pci=nocrs makes the kernel ignore additional resource windows
the BIOS reports through ACPI. This then most likely leads to problems
with amdgpu because it can't bring
Hi,
I have a laptop ASUS ROG Strix G15 Advantage Edition G513QY-HQ007. But
it is impossible to use without AC power because the system losts nvme
when I disconnect the power adapter.
Messages from kernel log when it happens:
nvme nvme0: controller is down; will reset: CSTS=0x,
13 matches
Mail list logo
