Vivek Dasmohapatra

Thanks. Looking into it.

Can I double check: The title says the breakage is post `3.6.4` . Does that mean you've seen it in a `3.6.5+` version, or was the first time you saw...

Still looking into this: If it's convenient, could you provide the output of the same command when booted into `3.6.x` (and with a working controller)?

No - I thought (apologies if I got this wrong) that when you booted back into `3.6.x` the controller was working again. Did it just break and stay broken?

From the journal, looks like: ``` PTS: 65E4F1BA, STS: 65E4F1BA [ { "path": "/dev/hidraw3", "vendor_id": 10462, "product_id": 4613, "serial_number": "", "release_number": 512, "manufacturer_string": "Valve Software", "product_string": "Steam Deck Controller", "usage_page":...

Should be `sudo /usr/bin/jupiter-controller-update --check 2>&1 | tee firmware-update.log` Then attach `firmware-update.log`. Or you can omit the `--check` to have it do the full update, but that probably doesn't matter...

> What happened is that I waited foe the issue to happen (First system reboot actually) , after the system went into emergency mode, I fired up the recovery image...

Could anyone who has had this problem let us know exactly what they have? `steamos-systemreport > sysrep.txt` Will tell you (and a bunch of other potentially useful info). Also the...

"Verifying installation" can happen, iirc, if there was an abrupt shutdown or steam didn't get a chance to clean up properly. That part doesn't necessarily indicate a deeper problem. The...

Right now I think the latest main image has only a couple of display blanking/refresh rate related patches over what's in beta.