<azkali>
Hi, I am currently porting mainline to the nintendo switch, and I am having issues with nouveau due to a gr error, I'd like to know if someone there has been some regression at any level. My rootfs is fedora 37, I am using mesa nvk (based on 23.0.0 iirc) and linux 6.0. I can provide logs if needed
azkali_ has joined #tegra
azkali_ has quit [Client Quit]
azkali has quit [Ping timeout: 276 seconds]
lars_ has joined #tegra
<lars_>
Hello people. I have a weird bootloader issue on a Jetson TX2 based system. I have an A/B boot system using U-Boot and Mender. If I have an active FTDI cable connected to the system when booting for the first time after updating the boot slot the system hangs for several minutes without any output on UART console and finally boots on the old partition. If I do updates without this cable connected everything
<lars_>
works fine.
<lars_>
To clarify: It rolls back if having FTDI cable connected on first boot.
Foxyloxy_ has quit [Remote host closed the connection]
Foxyloxy has joined #tegra
lars_ has quit [Ping timeout: 246 seconds]
azkali has joined #tegra
azkali has quit [Client Quit]
azkali has joined #tegra
azkali has quit [Read error: Connection reset by peer]
hexdump0815 has joined #tegra
<hexdump0815>
azkali: no idea if you are reading this via the weblog - the last mesa version which was working somewhat ok for me on a tegra k1 (chromebook nyan) was 21.0.3, everything after did not work anymore
torez has joined #tegra
gouchi has joined #tegra
gouchi has quit [Remote host closed the connection]