-
Notifications
You must be signed in to change notification settings - Fork 113
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
1.4.0 Firmware issues #346
Comments
The image version is the same for me. I questioned it myself, but it's correct. |
i noticed something else. the resolv.conf has 192.168.0.1 as the 1st IP but my IP range is something else. My DNS is 192.168.11.1 when i set that and save, it doesnt survive a reboot. it resets to 192.168.0.1 |
It works fine for me, For DNS settings to survive a reboot you want to edit |
I have the same issue (Image version showing as 2025-02-17-19-08-3649fe.img) and Check for Updates is failing. Tailscale is also not working. I tried to do: So in 1.3, I needed to run this alternate update just to be able to update the frontend and finally use Tailscale. Does anyone know if this is still working? I don't want to run it this time at the risk of bricking the device since code hasn't been updated since 1.3. |
To check for updates, login to the terminal or ssh & modify the /etc/resolve.conf
the 1st line will default to 192.168.0.1
, if this isn’t your network change accordingly and also add 1.1.1.1 to it. Save. Give it a few seconds and then try again
…________________________________
From: jpgam ***@***.***>
Sent: Wednesday, February 26, 2025 9:03:41 PM
To: sipeed/NanoKVM ***@***.***>
Cc: Ramesh Swamy ***@***.***>; Author ***@***.***>
Subject: Re: [sipeed/NanoKVM] 1.4.0 Firmware issues (Issue #346)
I have the same issue (Image version showing as 2025-02-17-19-08-3649fe.img) and Check for Updates is failing. Tailscale is also not working. I tried to do: python /etc/kvm/update-nanokvm.py and just comes with the same error I've encountered back in firmware version 1.3.
So in 1.3, I needed to run this alternate update<https://github.com/Bengt/NanoKVM-Updater> just to be able to update the frontend and finally use Tailscale. Does anyone know if this is still working? I don't want to run it this time at the risk of bricking the device since code hasn't been updated since 1.3.
—
Reply to this email directly, view it on GitHub<#346 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AGJDKJPUO776MRDVUY37F3L2RZW73AVCNFSM6AAAAABXVWJJFKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOBWGYYTONZVGU>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
[joshuagamboa]joshuagamboa left a comment (sipeed/NanoKVM#346)<#346 (comment)>
I have the same issue (Image version showing as 2025-02-17-19-08-3649fe.img) and Check for Updates is failing. Tailscale is also not working. I tried to do: python /etc/kvm/update-nanokvm.py and just comes with the same error I've encountered back in firmware version 1.3.
So in 1.3, I needed to run this alternate update<https://github.com/Bengt/NanoKVM-Updater> just to be able to update the frontend and finally use Tailscale. Does anyone know if this is still working? I don't want to run it this time at the risk of bricking the device since code hasn't been updated since 1.3.
—
Reply to this email directly, view it on GitHub<#346 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AGJDKJPUO776MRDVUY37F3L2RZW73AVCNFSM6AAAAABXVWJJFKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOBWGYYTONZVGU>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
You can't brick the device. Just toss in a fresh MicroSD card |
That totally worked out! Thanks. |
Has anyone managed to get Tailscale working? |
I upgraded to the 1.4.0 firmware and the "Check for Updates" section says "get version failed" error
this the about NanoKVM
The image version says its "2025-02-17-19-08-3649fe.img" & not 1.4.0
When I try to use the mouse in the browser, it gets kickout of the window and I'm unable to interact with it
The text was updated successfully, but these errors were encountered: