Ok, i finally got it. For some reason, the ip which the board was giving to itself was being overridden by some device of my pc. After disabling said device, and rebooting the board, everything seems to work just fine!
Thanks for everything
3 Likes
i am trying to connect a video capture device, to milk v duo 256, i enabled usb, was able to get the usb recognised in lsusb
lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 003: ID 534d:0021 MacroSilicon MS210x Video Grabber [EasierCAP]
root@duo256:/home/debian# v4l2-ctl --list-devices
Cannot open device /dev/video0, exiting.
root@duo256:/home/debian# lsmod | grep uvcvideo
root@duo256:/home/debian# modprobe uvcvideo
modprobe: FATAL: Module uvcvideo not found in directory /lib/modules/5.10.4-20240527-2+
root@duo256:/home/debian# grep -i uvc /boot/config-$(uname -r)
CONFIG_USB_F_UVC=y
CONFIG_USB_CONFIGFS_F_UVC=y
CONFIG_USB_UVCG_SG_TRANSFER=y
root@duo256:/home/debian# lsmod | grep uvc
please help
2 Likes
How much space do you have in /var/cache/apt/archives (run du -sh /var/cache/apt/archives)? Clear package cache with sudo apt clean.
1 Like
Hi,
I’m new to this, so forgive me stipid questions.
Just tried out Build v1.4.0 on a Duo256.
I can log in via SSH over the USB RNDIS connection to IP 10.42.0.1 using Putty on Windows.
-
I do not have any internet access from there. Is that expected?
-
If using the IO-Board, the network port seems to stay dead. The board is doing it’s heartbeat blinking as usually. But I can’t use the USB RNDIS connection if using the IO Board as far as I know. Any trick to get network to work when using the IO Board?
UPDATE: I can log in via SSH. Just the lights on the Ethernet port are not working. That is a loooonng time ago that I saw such a thing. Maybe some Orange PI with an addon board years ago.
It is installing packets as I type. Yeah!
1 Like
Yes, exactly. You either set up routing via RNDIS USB networking interface back thru your bigger computer, or connect it to the real network (Ethernet, for instance).
Could you please try and use this guide?
UPD0: Oh, you managed to make it working? Glad for you!
Yes. Network is working. Installed Pi-hole to see how that works. Actually works. CPU consumption now is at 50% to 60%. Memory usage below 50 Megs.
Trying to get a USB stick mounted. Nothing to be seen under lsblk. I guess I need to do something 
Didn’t find the usb-host.sh on the device. Extracting the buildroot sdk to see if it’s there.
1 Like
root@duo256:/proc/cviusb# echo host > /proc/cviusb/otg_role
root@duo256:/proc/cviusb# cat otg_role
host
root@duo256:/proc/cviusb# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 1 114.6G 0 disk
|-sda1 8:1 1 5.7G 0 part
|-sda2 8:2 1 5M 0 part
|-sda3 8:3 1 300K 0 part
`-sda4 8:4 1 108.9G 0 part
mmcblk0 179:0 0 28.8G 0 disk
|-mmcblk0p1 179:1 0 100M 0 part /boot
`-mmcblk0p2 179:2 0 28.7G 0 part /
That looks promising.
1 Like
I didn’t notice this is a Debian topic.
I now probably want a Debian image too… ;D
1 Like
Oh, and I somehow managed to get it to network with the outer world.
It is sad tho that it makes no sense to get such a board busy building images for Milk-V boards, heh.
Fixed that, now I have. Thanks @Fishwaldo !
UPD0:
Took me some time to find out CV1800B and SG2000 don’t support microSD of 128GB in capacity, 64GB ones work just fine. While SG2002 supports 128GB cards.
But the Duo S doesn’t shut down neither on Buildroot images, nor on these Debian ones, only reboots,
1 Like