21–30 of 74 posts
>And then, suddenly.. Caps Lock is blinking and the system is totally frozen :anguished:. So plugging in a brand-name joystick caused a kernel panic. Gross.
so... gross because sony should have better firmware or gross because linux should have a better usb stack, that is, it should never panic the kernel.
Earlier quoted context omitted.
so... gross because sony should have better firmware or gross because linux should have a better usb stack, that is, it should never panic the kernel.
If you stepped into a dog turd and it leaked into your socks do you blame your open source shoe designer or your lazy dog?
Earlier quoted context omitted.
so... gross because sony should have better firmware or gross because linux should have a better usb stack, that is, it should never panic the kernel.
If you stepped into a dog turd and it leaked into your socks do you blame your open source shoe designer or your lazy dog?
>And then, suddenly.. Caps Lock is blinking and the system is totally frozen :anguished:. So plugging in a brand-name joystick caused a kernel panic. Gross.
so... gross because sony should have better firmware or gross because linux should have a better usb stack, that is, it should never panic the kernel.
Edit: Sorry, I take it back: That data is weird, but not malformed; the hardware isn't out of line and I think the driver is fully at fault.
Earlier quoted context omitted.
If you stepped into a dog turd and it leaked into your socks do you blame your open source shoe designer or your lazy dog?
I don't get the analogy. Why is the dog supposed to be lazy? A dog turding on the street is by design. Maybe blaming the lazy dogs owner would be more appropriate.
[flagged]
It's a personal blog and neither you nor anyone else are paying for the work, so... sure?
Earlier quoted context omitted.
If you stepped into a dog turd and it leaked into your socks do you blame your open source shoe designer or your lazy dog?
In what world do you step in your own dog’s shit and blame the dog for being lazy?
Earlier quoted context omitted.
I don't get the analogy. Why is the dog supposed to be lazy? A dog turding on the street is by design. Maybe blaming the lazy dogs owner would be more appropriate.
It's not a good analogy but at the end of the day it's a bad Linux issue. Sony has no obligation to make sure it's driver will never halt a system. Linux does.
You're right, it's not a good analogy. It's barely one at all.
Neat find. What could cause the calibration offset to be zero? Certainly it did not come this way from the factory. Any abuse/misuse of the controller would not cause it either. Ah, I suspect this was a firmware update that got borked somehow. Maybe the cable was disconnected before the update could complete.
A possible explanation can be found on part 4 of this post:
> [...] if the checksum is not valid, there is a loop that clears out the flash [...] I suspect (but haven’t tried yet) that if the battery of the controller dies while it’s writing on the flash, at the next startup the checksum does not match and the DS4 gets totally messed up like this one.
That is, according to that theory, it was trying to write something to the flash (perhaps while pairing?), and part of the write failed because the battery died. On the next boot, it detected a wrong checksum, and erased everything.