-
Notifications
You must be signed in to change notification settings - Fork 35
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
Bug - xell hangs on initiliazing dhcp if ethernet cable is plugged in #55
Comments
It not a thing I can fix. Your network has something funky that XeLL doesn't like. |
can't open issue on that repo, heard people verify that this doesn't happen on the free60 version because of this patch lwip-tcpip/lwip@1eeb70f please consider compiling your xell with this |
I'll check this out and send you a test image shortly. Thanks. J |
Dang, GitHub doesn't allow issues on forks. Sorry about the confusion. |
Sorry for the delay, been busy with work. This is still on my list. |
no problem, thanks for your work. |
Free60 lwIP does not include that fix. But I'll try building with 1.4.1. You can test? |
yeah i can test |
Any updates? |
Similar to the user that created this issue, my consoles freezes during DHCP initialisation. Considering the patch lwip-tcpip/lwip@1eeb70f I temporarily changed my DHCP server settings to only include one DNS server rather than two and the console no longer freezes.
Isn't the version of IwIP used dependent on the library version installed on the build system? Other than the readme, I don't see anything in the xell-reloaded repository referencing to a specific version of lwip. |
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behaviour:
Expected behaviour
xell should work
Screenshots
Additional context
this is an RGH3 corona 4GB system, xell works if the ethernet cable remains unplugged.
The text was updated successfully, but these errors were encountered: