Go to advanced search

by Forage
Sun Aug 10, 2014 3:35 pm
Forum: General discussion
Topic: USB: device descriptor read/64, error -32
Replies: 7
Views: 19425

Re: USB: device descriptor read/64, error -32

@miamia: did you find a solution to your problem? I've got the same issue, but with a different device. It works fine after a fresh RPi start (unplugging the power) or when reconnecting the device but results in the same errors on reboot. A powered USB hub did not solve the problem, even though most...
by Forage
Sat Mar 22, 2014 9:53 am
Forum: Troubleshooting
Topic: Call for beta testers: FIQ_FSM USB driver rewrite
Replies: 250
Views: 114907

Re: Call for beta testers: FIQ_FSM USB driver rewrite

Update: The BRANCH=next firmware now has a fix for one of the potential sources of the "FIQ reported NYET" messages seen when using a heavily loaded system. It may also fix cases where network devices suddenly stop responding. Unfortunately no success. The network connection still drops after a whi...
by Forage
Thu Mar 20, 2014 7:06 pm
Forum: Troubleshooting
Topic: Call for beta testers: FIQ_FSM USB driver rewrite
Replies: 250
Views: 114907

Re: Call for beta testers: FIQ_FSM USB driver rewrite

Update: The BRANCH=next firmware now has a fix for one of the potential sources of the "FIQ reported NYET" messages seen when using a heavily loaded system. It may also fix cases where network devices suddenly stop responding. Unfortunately no success. The network connection still drops after a whi...
by Forage
Thu Mar 20, 2014 5:27 pm
Forum: Troubleshooting
Topic: Call for beta testers: FIQ_FSM USB driver rewrite
Replies: 250
Views: 114907

Re: Call for beta testers: FIQ_FSM USB driver rewrite

Update: The BRANCH=next firmware now has a fix for one of the potential sources of the "FIQ reported NYET" messages seen when using a heavily loaded system. It may also fix cases where network devices suddenly stop responding. Unfortunately no success. The network connection still drops after a whi...
by Forage
Sun Dec 16, 2012 2:59 pm
Forum: Troubleshooting
Topic: Calling for logs that show -84 or -110 or other SD errors
Replies: 6
Views: 3091

Re: Calling for logs that show -84 or -110 or other SD error

Just in case it helps: By your request in the thread mmc0: Controller never released inhibit bit(s) . Your altered kernel.img file did get rid of the inhibit error. However, it still doesn't get past the mmc0: Timeout waiting for hardware interrupt - cmd13. errors, so I can't provide you with a log.

Go to advanced search