-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Retry for sdio write errors. #210
Comments
The patch was garbled by the web ui so I opened pull request: With the patch in full. Best regards, Nat |
Sorry acidently clicked on close it should remain open until the pull request has been handled |
reopening... my apologies im a beginner |
Thanks for taking the time to dig in and no need to apologize! I see you tested with the 10/26 release - Is there anyway you could re-test with the latest nightly (without your patch) and see if you experience the same result? We just merged #209 which should help with this case, but it'd be great to know if it did/didnt. Also you say you're running NetBSD on your powerbook? Cool! I thought the NetBSD Wi-Fi driver wasn't compatible or was there an update? Either way any updates to the wiki with any tips or tricks (or prebuilt base image) would be appreciated. |
Confirmed resolved in #209 |
Hi,
I've updated to the latest 2024-10-26 release
And adding clock delay
[SDIO]
AddClockDelay=1
Still resulted in errors in the log.txt
Retrying on SDIO WRITE ERRORS was successful after applying the following patch:
This will retry writing the current block up to 3 times and so far this has been successful reporting no errors on NetBSD-current
BlueSCSI-v2 with wifi Powebook Edition.
20G Image size.
I hope this helps,
Best regards,
Nat
The text was updated successfully, but these errors were encountered: