|
|
Post by mobluse on Feb 20, 2021 5:58:00 GMT
Do you need to use the A port on the back or could you use the power port? It's easier to find microUSB to A-USB cables, than A to A cables.
I don't have any computer with ordinary Ubuntu installed ─ only Lubuntu 18.04, but I could create a Live USB stick with Ubuntu.
I noticed that I could power a Raspberry Pi Zero WH from the back port connected to the data port of the RPi while THEVIC20 was powered from the power port. That means the Raspberry Pi Zero WH could be the computer sharing its network (provided no OTG problems arise) to e.g. THEVIC20. The RPi is powered even if THEVIC20 is off.
I could not power THEVIC20 from the RPi connected to the USB A port on the back. There might be some current limitation from the RPi data port.
Does XWM use the internal Linux kernel? Why is that? Could one not have a Linux kernel on the USB stick?
|
|
|
|
Post by jj0 on Feb 20, 2021 9:43:15 GMT
Do you need to use the A port on the back or could you use the power port? It's easier to find microUSB to A-USB cables, than A to A cables. You need to use the USB Type A port as that is the one that supports OTG switching between Host mode and Client mode. Note you can still power THE64 from the power port.Lubuntu is based on Ubuntu, if they use the same Network Manager then it should still work OK.This is actually quite a cool idea. You could power the Pi and THE64 from e.g. a dual-port USB PSU so you don't have power issues and use the USB Type A port just for the network connection. You could even build the Pi into the case and connect it to the THE64's USB Type A and power port internally.Yes it does as that is already running. There is a method (called kexec) to replace a running kernel with a new one but that doesn't work on THE64 I think. And as the standard THE64 doesn't boot from USB currently the only way to change the kernel is to install a new one in nanda. This is certainly possible but then you have to consider whether you want to risk that. I've done it with my THE64's, e.g. my Mini now first checks if there's a kernel on a USB drive and if do loads that. I will publish the method on the forum some time when I have it working for the Maxi/VIC-20 as well. |
|
|
|
Post by MeneerJansen on Feb 20, 2021 10:50:16 GMT
I agree you can make changes to XWM if you mount the rootfs as rw. But did you install those themes with apt, apt-get or dpkg, or in another way? I mounted the "rootfs.img" file on my Linux computer. Like described in this here topic. Then I probably did ye olde from the command line: apt-get install I searched for packages apt-cache search package_name
The standard theme looks like Windows 95, I installed something newer. This is my short "tips n' hints" file on it: |
|
|
|
Post by jj0 on Feb 20, 2021 13:15:35 GMT
I agree you can make changes to XWM if you mount the rootfs as rw. But did you install those themes with apt, apt-get or dpkg, or in another way? I mounted the "rootfs.img" file on my Linux computer. Like described in this here topic. Then I probably did ye olde from the command line: apt-get install I searched for packages apt-cache search package_name
The standard theme looks like Windows 95, I installed something newer. This is my short "tips n' hints" file on it: Yes, if you mount it on your Linux computer you won't experience the issue, because then you are using the kernel from that computer. It's only when you run it you run it from THE64 that you will have the issue. |
|
|
|
Post by mobluse on Feb 22, 2021 1:54:59 GMT
Do you need to use the A port on the back or could you use the power port? It's easier to find microUSB to A-USB cables, than A to A cables. You need to use the USB Type A port as that is the one that supports OTG switching between Host mode and Client mode. Note you can still power THE64 from the power port.Lubuntu is based on Ubuntu, if they use the same Network Manager then it should still work OK.This is actually quite a cool idea. You could power the Pi and THE64 from e.g. a dual-port USB PSU so you don't have power issues and use the USB Type A port just for the network connection. You could even build the Pi into the case and connect it to the THE64's USB Type A and power port internally.Yes it does as that is already running. There is a method (called kexec) to replace a running kernel with a new one but that doesn't work on THE64 I think. And as the standard THE64 doesn't boot from USB currently the only way to change the kernel is to install a new one in nanda. This is certainly possible but then you have to consider whether you want to risk that. I've done it with my THE64's, e.g. my Mini now first checks if there's a kernel on a USB drive and if do loads that. I will publish the method on the forum some time when I have it working for the Maxi/VIC-20 as well. I don't have an A to A cable, but I got THEVIC20 RNDIS to register in dmesg on Raspberry Pi Zero W: [ 3195.495006] Indeed it is in host mode hprt0 = 00021501
[ 3195.774837] usb 1-1: new high-speed USB device number 4 using dwc_otg
[ 3195.775097] Indeed it is in host mode hprt0 = 00001101
[ 3196.085772] usb 1-1: New USB device found, idVendor=18d1, idProduct=0001, bcdDevice= 2.33
[ 3196.085810] usb 1-1: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[ 3196.085849] usb 1-1: Product: Android
[ 3196.085866] usb 1-1: Manufacturer: USB Developer
[ 3196.085881] usb 1-1: SerialNumber: 20080411
[ 3196.121175] rndis_host 1-1:1.0 usb0: register 'rndis_host' at usb-20980000.usb-1, RNDIS device, d2:67:4c:b1:7d:feOn THEVIC20 I can type dhclient rndis0. I'm connected to the Raspberry Pi Zero W from a Raspberry Pi 4B. Now I only have to figure out how I manually can configure the RPi0 to share its network to USB. |
|
|
|
Post by jj0 on Feb 22, 2021 7:43:45 GMT
You need to use the USB Type A port as that is the one that supports OTG switching between Host mode and Client mode. Note you can still power THE64 from the power port.Lubuntu is based on Ubuntu, if they use the same Network Manager then it should still work OK.This is actually quite a cool idea. You could power the Pi and THE64 from e.g. a dual-port USB PSU so you don't have power issues and use the USB Type A port just for the network connection. You could even build the Pi into the case and connect it to the THE64's USB Type A and power port internally.Yes it does as that is already running. There is a method (called kexec) to replace a running kernel with a new one but that doesn't work on THE64 I think. And as the standard THE64 doesn't boot from USB currently the only way to change the kernel is to install a new one in nanda. This is certainly possible but then you have to consider whether you want to risk that. I've done it with my THE64's, e.g. my Mini now first checks if there's a kernel on a USB drive and if do loads that. I will publish the method on the forum some time when I have it working for the Maxi/VIC-20 as well. I don't have an A to A cable, but I got THEVIC20 RNDIS to register in dmesg on Raspberry Pi Zero W: [ 3195.495006] Indeed it is in host mode hprt0 = 00021501
[ 3195.774837] usb 1-1: new high-speed USB device number 4 using dwc_otg
[ 3195.775097] Indeed it is in host mode hprt0 = 00001101
[ 3196.085772] usb 1-1: New USB device found, idVendor=18d1, idProduct=0001, bcdDevice= 2.33
[ 3196.085810] usb 1-1: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[ 3196.085849] usb 1-1: Product: Android
[ 3196.085866] usb 1-1: Manufacturer: USB Developer
[ 3196.085881] usb 1-1: SerialNumber: 20080411
[ 3196.121175] rndis_host 1-1:1.0 usb0: register 'rndis_host' at usb-20980000.usb-1, RNDIS device, d2:67:4c:b1:7d:feOn THEVIC20 I can type dhclient rndis0. I'm connected to the Raspberry Pi Zero W from a Raspberry Pi 4B. Now I only have to figure out how I manually can configure the RPi0 to share its network to USB. Do you get an IP address on THEVIC20? If so then you're halfway there. Remember that (unless your Pi Zero acts as DNS server) you need to set a suitable DNS server in /etc/resolv/conf. Also the Pi Zero needs to act as an IP router. If you don't get an IP address you can try to create a bridge between the Pi's wlan0 and it's usb0. Then run dhclient on THE64 and you should get an IP address and nameserver assigned from you internet router. For the Pi to have IP connectivity itself you have to run dhclient on the bridge interface as well. Using the Pi Zero (or any Pi) has the advantage you can use a normal micro-USB to USB data cable. |
|
|
|
Post by mobluse on Feb 23, 2021 1:43:47 GMT
I don't have an A to A cable, but I got THEVIC20 RNDIS to register in dmesg on Raspberry Pi Zero W: [ 3195.495006] Indeed it is in host mode hprt0 = 00021501
[ 3195.774837] usb 1-1: new high-speed USB device number 4 using dwc_otg
[ 3195.775097] Indeed it is in host mode hprt0 = 00001101
[ 3196.085772] usb 1-1: New USB device found, idVendor=18d1, idProduct=0001, bcdDevice= 2.33
[ 3196.085810] usb 1-1: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[ 3196.085849] usb 1-1: Product: Android
[ 3196.085866] usb 1-1: Manufacturer: USB Developer
[ 3196.085881] usb 1-1: SerialNumber: 20080411
[ 3196.121175] rndis_host 1-1:1.0 usb0: register 'rndis_host' at usb-20980000.usb-1, RNDIS device, d2:67:4c:b1:7d:feOn THEVIC20 I can type dhclient rndis0. I'm connected to the Raspberry Pi Zero W from a Raspberry Pi 4B. Now I only have to figure out how I manually can configure the RPi0 to share its network to USB. Do you get an IP address on THEVIC20? If so then you're halfway there. Remember that (unless your Pi Zero acts as DNS server) you need to set a suitable DNS server in /etc/resolv/conf. Also the Pi Zero needs to act as an IP router. If you don't get an IP address you can try to create a bridge between the Pi's wlan0 and it's usb0. Then run dhclient on THE64 and you should get an IP address and nameserver assigned from you internet router. For the Pi to have IP connectivity itself you have to run dhclient on the bridge interface as well. Using the Pi Zero (or any Pi) has the advantage you can use a normal micro-USB to USB data cable. From Raspberry Pi Zero starting with end of dmesg output. I got an IP-number I could ping from RPi0, but `dhclient rndis0` on THEVIC20 doesn't give an IP-number, but I've not configured a bridge. [ 1619.735163] Indeed it is in host mode hprt0 = 00021501
[ 1620.015031] usb 1-1: new high-speed USB device number 3 using dwc_otg
[ 1620.015277] Indeed it is in host mode hprt0 = 00001101
[ 1620.326008] usb 1-1: New USB device found, idVendor=18d1, idProduct=0001, bcdDevice= 2.33
[ 1620.326047] usb 1-1: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[ 1620.326065] usb 1-1: Product: Android
[ 1620.326080] usb 1-1: Manufacturer: USB Developer
[ 1620.326115] usb 1-1: SerialNumber: 20080411
[ 1620.355104] rndis_host 1-1:1.0 usb0: register 'rndis_host' at usb-20980000.usb-1, RNDIS device, 0a:49:21:9b:f1:ab
[email protected]:~ $ ip a
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
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether b8:27:eb:f2:20:d6 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.102/24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0
valid_lft 84672sec preferred_lft 73872sec
inet6 fe80::100d:b9b4:4d2:7a12/64 scope link
valid_lft forever preferred_lft forever
4: usb0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
link/ether 0a:49:21:9b:f1:ab brd ff:ff:ff:ff:ff:ff
inet 169.254.162.119/16 brd 169.254.255.255 scope global noprefixroute usb0
valid_lft forever preferred_lft forever
inet6 fe80::fa0:b27f:bd01:557d/64 scope link
valid_lft forever preferred_lft forever
[email protected]:~ $ ping 169.254.162.119
PING 169.254.162.119 (169.254.162.119) 56(84) bytes of data.
64 bytes from 169.254.162.119: icmp_seq=1 ttl=64 time=0.238 ms
64 bytes from 169.254.162.119: icmp_seq=2 ttl=64 time=0.239 ms
64 bytes from 169.254.162.119: icmp_seq=3 ttl=64 time=0.236 ms
^C
--- 169.254.162.119 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 36ms
rtt min/avg/max/mdev = 0.236/0.237/0.239/0.017 ms
I now have a working USB A to A cable and could connect THEVIC20 to a EeePC 900 with Lubuntu. THEVIC20 is powered from the Eee PC 900 only. I have shared to other computers all ethernet ports since I don't now which one is usb0, but I have no ethernet cable connected. The WiFi uses DHCP. I have the same problem as with RPi0. I get an IP number on the Eee PC, but not on THEVIC20 using `dhclient rndis0`. [ 1590.004163] usb 1-2: new high-speed USB device number 6 using ehci-pci
[ 1590.160945] usb 1-2: New USB device found, idVendor=18d1, idProduct=0001
[ 1590.160953] usb 1-2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[ 1590.160957] usb 1-2: Product: Android
[ 1590.160962] usb 1-2: Manufacturer: USB Developer
[ 1590.160966] usb 1-2: SerialNumber: 20080411
[ 1590.170151] rndis_host 1-2:1.0 usb0: register 'rndis_host' at usb-0000:00:1d.7-2, RNDIS device, 76:6e:c8:c3:3f:e7
[ 1590.446770] IPv6: ADDRCONF(NETDEV_UP): usb0: link is not ready
[ 1635.539209] perf: interrupt took too long (3949 > 3933), lowering kernel.perf_event_max_sample_rate to 50500
[email protected]:~$ ip a
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
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
link/ether 00:22:15:5b:63:36 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:0f:54:16:1c:02 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.148/24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0
valid_lft 83149sec preferred_lft 83149sec
inet6 fe80::9bd5:48c9:8bac:c811/64 scope link noprefixroute
valid_lft forever preferred_lft forever
4: wlan1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:15:af:c6:fd:b7 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.143/24 brd 192.168.1.255 scope global dynamic noprefixroute wlan1
valid_lft 82303sec preferred_lft 82303sec
inet6 fe80::e682:a410:145f:c74d/64 scope link noprefixroute
valid_lft forever preferred_lft forever
6: usb0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 1000
link/ether 76:6e:c8:c3:3f:e7 brd ff:ff:ff:ff:ff:ff
inet 10.42.0.1/24 brd 10.42.0.255 scope global noprefixroute usb0
valid_lft forever preferred_lft forever
inet6 fe80::a909:f21b:131d:242a/64 scope link noprefixroute
valid_lft forever preferred_lft forever
[email protected]:~$ ping 10.42.0.1
PING 10.42.0.1 (10.42.0.1) 56(84) bytes of data.
64 bytes from 10.42.0.1: icmp_seq=1 ttl=64 time=0.073 ms
64 bytes from 10.42.0.1: icmp_seq=2 ttl=64 time=0.094 ms
64 bytes from 10.42.0.1: icmp_seq=3 ttl=64 time=0.095 ms
^C
--- 10.42.0.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2053ms
rtt min/avg/max/mdev = 0.073/0.087/0.095/0.012 msI might experiment some more by e.g. connecting another computer to the real ethernet connector and see if I can use the Eee PC's WiFi from that. On the Eee PC 900 in Lubuntu 18.04 I use `nm-connection-editor`. |
|
|
|
Post by jj0 on Feb 23, 2021 8:55:54 GMT
I don't use Lubuntu but from the info here I gather you need to first connect THEVIC20 tot the PC and start XWM so that OTG mode is active. This should create the 'virtual' usb0 network card on the PC. Then you go to the network manager in Lubuntu (Preferences->Network Connections) and enable sharing on the usb0 device. The sharing will (at least on my Ubuntu) set up the DHCP server on Lubuntu that assigns an IP address to then rndis0 interface on THEVIC20 when dhclient asks for it. |
|
|
|
Post by mobluse on Feb 24, 2021 4:17:02 GMT
I don't use Lubuntu but from the info here I gather you need to first connect THEVIC20 tot the PC and start XWM so that OTG mode is active. This should create the 'virtual' usb0 network card on the PC. Then you go to the network manager in Lubuntu (Preferences->Network Connections) and enable sharing on the usb0 device. The sharing will (at least on my Ubuntu) set up the DHCP server on Lubuntu that assigns an IP address to then rndis0 interface on THEVIC20 when dhclient asks for it. I got THEVIC20 online using the Eee PC 900 with Lubuntu and nameserver work on Internet, but not for the local computers, but I could ssh to the host EeePC. I needed to install dnsmasq. I also run this script on the EeePC: github.com/arpitjindal97/raspbian-recipes/blob/master/wifi-to-eth-route.sh(I changed the nameserver in the script to OpenDNS: 208.67.222.222.) Then I rebooted and didn't run the script, but then it worked anyway due to Lubuntus own system with sharing to other computers. What made it work was probably dnsmasq, but I'm not sure. Before I got usb0 to work I succeeded in connecting a Raspberry Pi with ethernet to the ethernet of the host EeePC and using its WiFi from the client Pi. Then I tried to connect THEVIC20 using Raspberry Pi Zero, but I haven't yet got that to work. It gets an IP number. `ip a` on THEVIC20: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: tunl0: <NOARP> mtu 1480 qdisc noop state DOWN group default
link/ipip 0.0.0.0 brd 0.0.0.0
3: gre0: <NOARP> mtu 1476 qdisc noop state DOWN group default
link/gre 0.0.0.0 brd 0.0.0.0
4: sit0: <NOARP> mtu 1480 qdisc noop state DOWN group default
link/sit 0.0.0.0 brd 0.0.0.0
5: ip6tnl0: <NOARP> mtu 1452 qdisc noop state DOWN group default
link/tunnel6 :: brd ::
6: rndis0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 32:98:8d:08:58:b9 brd ff:ff:ff:ff:ff:ff
inet 192.168.2.6/24 brd 192.168.2.255 scope global rndis0
inet6 fe80::3098:8dff:fe08:58b9/64 scope link
valid_lft forever preferred_lft forever`ip route` on the host Raspberry Pi Zero: default via 192.168.1.1 dev wlan0 proto dhcp src 192.168.1.102 metric 303
169.254.0.0/16 dev usb0 scope link src 169.254.233.237 metric 204
192.168.1.0/24 dev wlan0 proto dhcp scope link src 192.168.1.102 metric 303I use the same script as on EeePC. It's strange that I get an 169.254 address in ip route. `ip a` on the host RPi0: 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
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether b8:27:eb:f2:20:d6 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.102/24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0
valid_lft 85034sec preferred_lft 74234sec
inet6 fe80::100d:b9b4:4d2:7a12/64 scope link
valid_lft forever preferred_lft forever
4: usb0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN group default qlen 1000
link/ether 8e:19:fd:ed:f2:7f brd ff:ff:ff:ff:ff:ff
inet 192.168.2.1/24 brd 192.168.2.255 scope global noprefixroute usb0
valid_lft forever preferred_lft forever
inet 169.254.233.237/16 brd 169.254.255.255 scope global noprefixroute usb0
valid_lft forever preferred_lft forever
inet6 fe80::e216:1e59:e9a0:1aae/64 scope link
valid_lft forever preferred_lft forever`ifconfig -a` on the host RPi0: lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 29596 bytes 1776520 (1.6 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 29596 bytes 1776520 (1.6 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
usb0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.2.1 netmask 255.255.255.0 broadcast 192.168.2.255
inet6 fe80::e216:1e59:e9a0:1aae prefixlen 64 scopeid 0x20<link>
ether 8e:19:fd:ed:f2:7f txqueuelen 1000 (Ethernet)
RX packets 6 bytes 384 (384.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 64 bytes 15783 (15.4 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.102 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::100d:b9b4:4d2:7a12 prefixlen 64 scopeid 0x20<link>
ether b8:27:eb:f2:20:d6 txqueuelen 1000 (Ethernet)
RX packets 1325 bytes 130788 (127.7 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 807 bytes 133532 (130.4 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0I cannot ssh from THEVIC20 to RPi0 using 192.168.2.1. `dhclient rndis0` sets the nameserver to 192.168.2.1 each time I run it even if I set something else. I'm rather close to getting it to work, and it would be a cheap way to get THEVIC20 and THEC64 online to e.g. download files. When I use EeePC as host I can use Dillo as browser, but that doesn't handle JavaScript, but `links` browser does, and I could read this site using `links`. |
|
|
|
Post by spannernick on Feb 24, 2021 15:27:54 GMT
Could you use a USB WIFI Dongle or a USB to RJ45 Adapter(my USB to RJ45 Adapter, it blue, does work on THEC64 Mini FEL MODE) with THEC64 X-Windows Mod, I guess it would depend on if there's a modgel for the kernal and if it works with it or can be modified to work with it, and you would have to have 2 modgets, one of THEC64 Mini and one for THEC64 Maxi cause there kernels are not the same and uses different SoC(System On a Chip, there like ASIC(Application-specific integrated circuit) Chip, which came first..? the Chicken or the Egg, well Commodore did cause of there Chicken Head logo..  got to be funny with Covid 19 around.)...? My USB to RJ45 Adapter  It works on my Sega Mega Drive Mini too with Hackchi installed. |
|
|
|
Post by jj0 on Feb 24, 2021 16:03:53 GMT
Could you use a USB WIFI Dongle or a USB to RJ45 Adapter(my USB to RJ45 Adapter, it blue, does work on THEC64 Mini FEL MODE) with THEC64 X-Windows Mod, I guess it would depend on if there's a modgel for the kernal and if it works with it or can be modified to work with it, and you would have to have 2 modgets, one of THEC64 Mini and one for THEC64 Maxi cause there kernels are not the same and uses different SoC(System On a Chip, there like ASIC(Application-specific integrated circuit) Chip, which came first..? the Chicken or the Egg, well Commodore did cause of there Chicken Head logo.. got to be funny with Covid 19 around.)...? My USB to RJ45 Adapter On the Mini you could use it, if you remember I provided the kernel modules for this one in one of the earlier threads. So all you have to do is replace the asix.ko module that is load in start.sh with the one for this adapter. |
|
|
|
Post by mobluse on Feb 24, 2021 17:44:56 GMT
I noticed that nm-connection-editor (a GUI network manager) that I used to get usb0 to work in Lubuntu on EeePC is also available in Raspberry Pi OS Buster on Raspberry Pi Zero in the package network-manager-gnome. I run my Raspberry Pi Zero W headless without X installed, so I would prefer if I could configure the network on the Pi without using a GUI.
|
|
|
|
Post by mobluse on Feb 24, 2021 18:14:35 GMT
Could you use a USB WIFI Dongle or a USB to RJ45 Adapter(my USB to RJ45 Adapter, it blue, does work on THEC64 Mini FEL MODE) with THEC64 X-Windows Mod, I guess it would depend on if there's a modgel for the kernal and if it works with it or can be modified to work with it, and you would have to have 2 modgets, one of THEC64 Mini and one for THEC64 Maxi cause there kernels are not the same and uses different SoC(System On a Chip, there like ASIC(Application-specific integrated circuit) Chip, which came first..? the Chicken or the Egg, well Commodore did cause of there Chicken Head logo.. got to be funny with Covid 19 around.)...? My USB to RJ45 Adapter On the Mini you could use it, if you remember I provided the kernel modules for this one in one of the earlier threads. So all you have to do is replace the asix.ko module that is load in start.sh with the one for this adapter. Maybe you could use THEC64 MINI as a host providing network using an ethernet adapter to THEVIC20/THEC64 as an rndis client via a USB cable. Preferably one could use the microUSB of THEC64 MINI connected to the back USB-A port of THEVIC20/THEC64 and the whole thing would be powered from THEVIC20/THEC64. Many people who own the full size models also own THEC64 MINI since before. It works powerwise because I tested it using a 2 A power supply and I get pictures from both HDMI ports. I've not tested this further with Linux booted on both machines. |
|
|
|
Post by jj0 on Feb 25, 2021 14:00:14 GMT
I don't use Lubuntu but from the info here I gather you need to first connect THEVIC20 tot the PC and start XWM so that OTG mode is active. This should create the 'virtual' usb0 network card on the PC. Then you go to the network manager in Lubuntu (Preferences->Network Connections) and enable sharing on the usb0 device. The sharing will (at least on my Ubuntu) set up the DHCP server on Lubuntu that assigns an IP address to then rndis0 interface on THEVIC20 when dhclient asks for it. I got THEVIC20 online using the Eee PC 900 with Lubuntu and nameserver work on Internet, but not for the local computers, but I could ssh to the host EeePC. I needed to install dnsmasq. I also run this script on the EeePC: github.com/arpitjindal97/raspbian-recipes/blob/master/wifi-to-eth-route.sh(I changed the nameserver in the script to OpenDNS: 208.67.222.222.) Then I rebooted and didn't run the script, but then it worked anyway due to Lubuntus own system with sharing to other computers. What made it work was probably dnsmasq, but I'm not sure. Before I got usb0 to work I succeeded in connecting a Raspberry Pi with ethernet to the ethernet of the host EeePC and using its WiFi from the client Pi. Then I tried to connect THEVIC20 using Raspberry Pi Zero, but I haven't yet got that to work. It gets an IP number. `ip a` on THEVIC20: <snip>`ip route` on the host Raspberry Pi Zero: <snip>I use the same script as on EeePC. It's strange that I get an 169.254 address in ip route. `ip a` on the host RPi0: <snip>`ifconfig -a` on the host RPi0: <snip>I cannot ssh from THEVIC20 to RPi0 using 192.168.2.1. `dhclient rndis0` sets the nameserver to 192.168.2.1 each time I run it even if I set something else. I'm rather close to getting it to work, and it would be a cheap way to get THEVIC20 and THEC64 online to e.g. download files. When I use EeePC as host I can use Dillo as browser, but that doesn't handle JavaScript, but `links` browser does, and I could read this site using `links`. It's much easier to set up a bridge on the Pi Zero W between (in your case) wlan0 and usb0. I don't have a Pi Zero W but on a Pi Zero with added ethernet adapter and a new, clean RaspberryOS install I followed only the 'Setup the network bridge' part of this instruction, and in addition to the instructions for eth0 I did the same for usb0, creating an automatic bridge between eth0 and usb0. In your case, replace eth0 with wlan0 of course. Now when I run XWM on the Maxi (powered by the Pi Zero's OTG port) the usb0 interface that is created on the Pi Zero is automatically added to the bridge. And because it is bridged with 'the rest of the network' running dhclient on rndis0 on the Maxi gives it an IP-address and nameserver on your local network so you are immediately in business. |
|
|
|
Post by mobluse on Feb 26, 2021 19:35:28 GMT
I got THEVIC20 online using the Eee PC 900 with Lubuntu and nameserver work on Internet, but not for the local computers, but I could ssh to the host EeePC. I needed to install dnsmasq. I also run this script on the EeePC: github.com/arpitjindal97/raspbian-recipes/blob/master/wifi-to-eth-route.sh(I changed the nameserver in the script to OpenDNS: 208.67.222.222.) Then I rebooted and didn't run the script, but then it worked anyway due to Lubuntus own system with sharing to other computers. What made it work was probably dnsmasq, but I'm not sure. Before I got usb0 to work I succeeded in connecting a Raspberry Pi with ethernet to the ethernet of the host EeePC and using its WiFi from the client Pi. Then I tried to connect THEVIC20 using Raspberry Pi Zero, but I haven't yet got that to work. It gets an IP number. `ip a` on THEVIC20: <snip>`ip route` on the host Raspberry Pi Zero: <snip>I use the same script as on EeePC. It's strange that I get an 169.254 address in ip route. `ip a` on the host RPi0: <snip>`ifconfig -a` on the host RPi0: <snip>I cannot ssh from THEVIC20 to RPi0 using 192.168.2.1. `dhclient rndis0` sets the nameserver to 192.168.2.1 each time I run it even if I set something else. I'm rather close to getting it to work, and it would be a cheap way to get THEVIC20 and THEC64 online to e.g. download files. When I use EeePC as host I can use Dillo as browser, but that doesn't handle JavaScript, but `links` browser does, and I could read this site using `links`. It's much easier to set up a bridge on the Pi Zero W between (in your case) wlan0 and usb0. I don't have a Pi Zero W but on a Pi Zero with added ethernet adapter and a new, clean RaspberryOS install I followed only the 'Setup the network bridge' part of this instruction, and in addition to the instructions for eth0 I did the same for usb0, creating an automatic bridge between eth0 and usb0. In your case, replace eth0 with wlan0 of course. Now when I run XWM on the Maxi (powered by the Pi Zero's OTG port) the usb0 interface that is created on the Pi Zero is automatically added to the bridge. And because it is bridged with 'the rest of the network' running dhclient on rndis0 on the Maxi gives it an IP-address and nameserver on your local network so you are immediately in business. How can you connect both the ethernet adapter and the Maxi to the Raspberry Pi Zero? Do you use a USB hub? |
|
|
|
Post by jj0 on Feb 26, 2021 20:02:37 GMT
It's much easier to set up a bridge on the Pi Zero W between (in your case) wlan0 and usb0. I don't have a Pi Zero W but on a Pi Zero with added ethernet adapter and a new, clean RaspberryOS install I followed only the 'Setup the network bridge' part of this instruction, and in addition to the instructions for eth0 I did the same for usb0, creating an automatic bridge between eth0 and usb0. In your case, replace eth0 with wlan0 of course. Now when I run XWM on the Maxi (powered by the Pi Zero's OTG port) the usb0 interface that is created on the Pi Zero is automatically added to the bridge. And because it is bridged with 'the rest of the network' running dhclient on rndis0 on the Maxi gives it an IP-address and nameserver on your local network so you are immediately in business. How can you connect both the ethernet adapter and the Maxi to the Raspberry Pi Zero? Do you use a USB hub? I use an OTG cable (https://en.m.wikipedia.org/wiki/USB_On-The-Go#OTG_micro_cables). |
|
|
|
Post by mobluse on Feb 26, 2021 22:22:51 GMT
How can you connect both the ethernet adapter and the Maxi to the Raspberry Pi Zero? Do you use a USB hub? I use an OTG cable (https://en.m.wikipedia.org/wiki/USB_On-The-Go#OTG_micro_cables). Yes, but do you not need to connect a USB hub to the OTG cable? since you have two devices connected to the Raspberry Pi Zero: ethernet adapter and Maxi. |
|
|
|
Post by jj0 on Feb 26, 2021 22:55:13 GMT
I use an OTG cable (https://en.m.wikipedia.org/wiki/USB_On-The-Go#OTG_micro_cables). Yes, but do you not need to connect a USB hub to the OTG cable? since you have two devices connected to the Raspberry Pi Zero: ethernet adapter and Maxi. It's an OTG cable with two Female Type-A connectors, so I can connect the USB2Ethernet and the Maxi. I think it's the same as a passive HUB. |
|
|
|
Post by spannernick on Mar 3, 2021 20:46:07 GMT
I was thinking, if you could get XWM to use the internet by using a RPI, could you get it to work on VICE too, the VICE that comes with PCU or VICE standalone and connect it to C64 Telnet Billiton Boards Sites .....?
|
|
|
|
Post by jj0 on Mar 3, 2021 21:51:33 GMT
I was thinking, if you could get XWM to use the internet by using a RPI, could you get it to work on VICE too, the VICE that comes with PCU or VICE standalone and connect it to C64 Telnet Billiton Boards Sites .....? I'd probably need to recompile VICE with '--enable-ethernet', I don't think I did that, |
|
|
|
Post by spannernick on Mar 6, 2021 15:04:45 GMT
I had a idea.. I was thinking this takes up 2GB space on your USB Stick or SD Card, I know you can't shrink it but could you unpack it and mount it like we did with VICE and Midnight Commander...?
Then you could use the space that in the XWM folder on the USB Stick instead and could then make the XWM or X smaller and removing stuff we don't need, so all the files from rootfs.img is in a folder called XWM instead, so your would not be using chroot but overmounting Buildroot's folders instead like I did with MC, and users can access the the files for XWM better too, so if they want to change the theme say, what you think JJ...?
|
|
|
|
Post by jj0 on Mar 6, 2021 17:10:49 GMT
I had a idea.. I was thinking this takes up 2GB space on your USB Stick or SD Card, I know you can't shrink it but could you unpack it and mount it like we did with VICE and Midnight Commander...? Then you could use the space that in the XWM folder on the USB Stick instead and could then make the XWM or X smaller and removing stuff we don't need, so all the files from rootfs.img is in a folder called XWM instead, so your would not be using chroot but overmounting Buildroot's folders instead like I did with MC, and users can access the the files for XWM better too, so if they want to change the theme say, what you think JJ...? It's too complicated/ VICE and especially MC are simple programs that use a few libraries so are relatively easy to separate. X-Windows and all the programs you can run while in X-Windows is much too complicated to manage that way. Also is 2GB really that much these days? |
|
got to be funny with Covid 19 around.)...?