You can track progress here Home · sophgo/linux Wiki · GitHub
1 Like
Thanks. So it’s inactive since April? 
1 Like
I think that’s just the Duo-S board. I don’t own the SG2000 but its progress into mainline Linux kernel is possibly tracked under the CV18XX series.
1 Like
Well, this is the one I am interested in because I don’t own any others.
1 Like
The SG SoC would have been classified CV18XX in the past.
Even on the other boards, the best I have seen from mainline kernels is SD Card boot without other major peripherals. Perhaps see how this works for your board, or wait a bit longer.
3 Likes
I had a question regarding the latest couple of images, specifically for the Duo S. I noticed that LED control had been migrated to the Linux LED driver back in April. Did this replace the blink.sh script entirely? I’m trying to turn the blue LED blink off on my Duo S, and I can’t seem to find whatever is controlling it. I checked through all running services in systemctl and didn’t see anything, couldn’t find grep for “led” or “blink” under any running process, and can’t find any blink.sh file anywhere on the system. I’m assuming those are still being controlled by the big C906 core and not the RTOS core. Does anyone know what is controlling them?
2 Likes
It’s using the native kernel support for leds.
Check under the /sys/class/leds/ directory for the led you want to control.
2 Likes
Thank you! That was a fun rabbit hole to go down, I had never considered native kernel led support before. Thanks for the reply and thanks for the awesome images!
1 Like
Is the SSH server started up right after boot? If so, how can I log in to it. I tried debian with password rv and it doesn’t seem to work
1 Like
How have you tried to ssh in? Through USB or LAN?
I normally SSH from a linux terminal with “ssh debian@192.168.1.66” or whatever LAN address my router assigns.
If it is USB it is something like “ssh debian@10.42.0.1” - I can’t recall the exact address.
The USB is pretty much instant after boot and LAN take a few seconds longer for the router.
When you say it doesn’t seem to work, what were the error messages?
1 Like
I connect the board via USB C and try to ssh as you say “ssh debian@10.42.0.*”
However, when using “rv” as a password, it just says permission denied and lets me try again a few more times, before it shuts down completely (due to the many incorrect attempts)
1 Like
If you are getting a “permission denied” error then I think the board is working and ssh is running. The problem is with authentication … I think.
1 Like
Yes, that’s what i thought, but I have been tinkering with the ssh settings in the board, and I have also tried re-flashing the image, and nothing seems to work.
Maybe I should try connecting via LAN, as you said you have done. That’s just plugging the board via Ethernet to the router, right?
By the way, thanks for all the help, I really don’t have the slightest idea of what I am doing
1 Like
Is the UART tty supported in this image? Just curious.
After some more trial and error, i found out the ip listed in the device that appears with the booting of the board is one more of my PC’s ips. So i have been trying to SSH to my own PC using the board password all this time…
Does anyone know the actual IP of the board when connected via USB? If it has one anyways…
1 Like
I just plugged my duo256 (running debian) into my machine (I am running mint 21.3 on my machine) and successfully ssh’d into the board.
If you use the command “ifconfig” or “ip a” on your linux machine or “ipconfig” in a window’s cmd it will show you the ip that the duo has assigned to your computer - don’t use this … it will be 10.42.0.150 or something. You need to log into the duo address which is 10.42.0.1.
1 Like
I’m not sure of the UART … I solved my earlier problems with a fixed MAC a different way.
1 Like
I bet you can try and inspect your networks and IP address info, like using ip addr command.
I think (and I’ve never tried Debian on my Duo S board, tbh), the OS on the board should have its DHCP server configured to offer IP addresses over RNDIS Ethernet-over-USB) interface. Correct me if I’m wrong.
If I’m right, you’re able to receive an IP address (IPv4 and probably IPv6) from it:
$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
…
9: enxf66794a3994f: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
link/ether f6:67:94:a3:99:4f brd ff:ff:ff:ff:ff:ff
inet 192.168.42.229/24 brd 192.168.42.255 scope global dynamic noprefixroute enxf66794a3994f
valid_lft 3207sec preferred_lft 3207sec
inet6 fe80::358f:8fca:e752:dd2d/64 scope link noprefixroute
valid_lft forever preferred_lft forever
And then you can see which hosts are your neighbors on this interface:
$ ip neigh | grep enx
192.168.42.1 dev enx92eb81344835 lladdr fa:a0:f3:1d:57:f5 STALE
And ping them, or connect to them:
$ ping 192.168.42.1
PING 192.168.42.1 (192.168.42.1) 56(84) bytes of data.
64 bytes from 192.168.42.1: icmp_seq=1 ttl=64 time=1.91 ms
64 bytes from 192.168.42.1: icmp_seq=2 ttl=64 time=1.91 ms
^C
--- 192.168.42.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1002ms
rtt min/avg/max/mdev = 1.909/1.910/1.911/0.001 ms
$ ssh root@192.168.42.1
root@192.168.42.1's password:
X11 forwarding request failed on channel 0
[root@milkv-duo]~#
1 Like
That ip, 10.42.0.1 is an ip assigned to my pc. I know because I can’t log in using the board’s credentials, but i can using my own pc’s. Besides, the device has my pc’s name, so there is no doubt. That is using the USB connection. Once i have the chance, i will try the router option just in case it works differently.
2 Likes
I tried everything you did step by step. However, there seems to be no neighbors in the network. I already had a similar idea and pinged every IP on the range the board appeared on, with no luck
1 Like