sipeed / sipeed/NanoKVM

Ethernet stopped working, and so is the webgui

Open
#596 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
6.5k
Forks
330
Avg merge
1d 19h
Merged PRs (30d)
3

Description

Untill now my new nanokvm did work, but now for some reason it cannot connect to the internet anymore
I see no uplink to the router, but I see that the storage linux gadget function is workin:

Image

So I tried to connect in ssh into it through RNDIS as provided by the docs

Image

But the connection keeps getting refused

Image

So I connected a ch341 clone through usb/uart to the nanokvm, and I can get output, but I also get:
"INII :
ld "acm"
respawning too fast :
disabled for S minutes"

Image

which I don't know what is it? all I could find on google it's about issues of configuration issues for serial interface through virtual machines, which is not the case here?

when rebooting the device, I get
"[SAMPLE COMM ISP Thread]-9S:
= 1920
1080
maix multi—media init 0k
cry release vio 0k
try release venc 0k
ISP Dev O running!
lmf add
udhcpc :
udhcpc :
udhcpc :
udhcpc :
udhcpc :
vi channel..
broadcasting discover
broadcasting discover
broadcasting discover
broadcasting discover
no lease, forking to background"

so it looks like the ethernet/dhcp is failing to initializate?
But I know for sure that the ethernet port of my router, the cable, and dhcp do perfectly work, as with other devices there are no problems, except for the nanokvm....

I don't know what else to do? if it's again an hardware porblem, it's pretty bad, as it's the second device that just fails, the first one burned down through the usb port, the second one (this) worked fine for a while, and now the ethernet port seems to have died

the interface looks OHKO to me, but I may, and I hope that I'm wrong

Image

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the UART boot output, especially the repeated udhcpc discovery failures and refused RNDIS SSH connection, and compare them with the project's networking and SSH/RNDIS documentation. Done means determining whether the fault is configuration/software or failed Ethernet hardware and documenting a reproducible recovery or replacement path.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
embedded-iot, networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.