|
Post by MeneerJansen on Aug 26, 2020 15:42:13 GMT
Finally remove spaces and paste into gamecontrollerdb.txt: 03000000C0160000DC27000001010000
Check if it's 32 numbers in length. It's right, aint it? It looks fine to me except that it's in uppercase. Not sure if that matters though. Bloody hell!!!! Aaaaaaaaaaarrrghhhhhhhhhhhhhhhhhhh! I've been using Linux as my default OS for the past 15 years (i.e. on a daily basis). I've been an active member of the NedLinux Forum when it was still up helping starting users to "get used to" Linux. I knew Linux is case sensitive, but THAT case sensitive...!? I blame myself for being a stupid idiot, ha ha. I should have known better. Anyway, thank you very much for that remark: it did the trick! I'm now playing my C64 w/ my 37 year old trusted Atari joystick (which will probably break within a few days, ha ha). We are nowhere in this world without a little help, even if it seems trivial. This would have got me puzzling for weeks man! Kudo's to you
|
|
|
Post by jj0 on Aug 26, 2020 18:34:19 GMT
It looks fine to me except that it's in uppercase. Not sure if that matters though. Bloody hell!!!! Aaaaaaaaaaarrrghhhhhhhhhhhhhhhhhhh! I've been using Linux as my default OS for the past 15 years (i.e. on a daily basis). I've been an active member of the NedLinux Forum when it was still up helping starting users to "get used to" Linux. I knew Linux is case sensitive, but THAT case sensitive...!? I blame myself for being a stupid idiot, ha ha. I should have known better. Anyway, thank you very much for that remark: it did the trick! I'm now playing my C64 w/ my 37 year old trusted Atari joystick (which will probably break within a few days, ha ha). We are nowhere in this world without a little help, even if it seems trivial. This would have got me puzzling for weeks man! Kudo's to you Dankjewel 😂. Met welk spel ga je je joystick kapotmaken?
|
|
|
Post by MeneerJansen on Aug 27, 2020 10:45:56 GMT
Bloody hell!!!! Aaaaaaaaaaarrrghhhhhhhhhhhhhhhhhhh! I've been using Linux as my default OS for the past 15 years (i.e. on a daily basis). I've been an active member of the NedLinux Forum when it was still up helping starting users to "get used to" Linux. I knew Linux is case sensitive, but THAT case sensitive...!? I blame myself for being a stupid idiot, ha ha. I should have known better. Anyway, thank you very much for that remark: it did the trick! I'm now playing my C64 w/ my 37 year old trusted Atari joystick (which will probably break within a few days, ha ha). We are nowhere in this world without a little help, even if it seems trivial. This would have got me puzzling for weeks man! Kudo's to you Dankjewel 😂. Met welk spel ga je je joystick kapotmaken? Ha ha, thanks fellow Dutch man. Probably '(Way of the) Exploding Fist' or 'Bruce Lee'.
|
|
|
Post by jj0 on Aug 27, 2020 11:39:53 GMT
Dankjewel 😂. Met welk spel ga je je joystick kapotmaken? Ha ha, thanks fellow Dutch man. Probably '(Way of the) Exploding Fist' or 'Bruce Lee'. Excellent choices!
|
|
|
Post by MeneerJansen on Sept 9, 2020 13:05:39 GMT
I have a C64 Maxi and I'm trying to install some software on the Linux X Windows Mod. I followed the following procedure from the top post: It appears to work fine (I'm "inside" the rootfs.img). However I do not have an internet connection and therefore installing software is pretty hard. The error I get is:
ifconfig Warning: cannot open /proc/net/dev (No such file or directory). Limited output.
Am I doing something wrong?
|
|
|
Post by jj0 on Sept 10, 2020 11:42:24 GMT
I have a C64 Maxi and I'm trying to install some software on the Linux X Windows Mod. I followed the following procedure from the top post: It appears to work fine (I'm "inside" the rootfs.img). However I do not have an internet connection and therefore installing software is pretty hard. The error I get is: ifconfig Warning: cannot open /proc/net/dev (No such file or directory). Limited output.
Am I doing something wrong? I also get the same error message with ipconfig in the chroot environment but the network works fine: # ifconfig Warning: cannot open /proc/net/dev (No such file or directory). Limited output. # ping www.thec64community.online PING www.thec64community.online (104.18.123.189) 56(84) bytes of data. 64 bytes from 104.18.123.189: icmp_seq=1 ttl=59 time=14.6 ms 64 bytes from 104.18.123.189: icmp_seq=2 ttl=59 time=9.71 ms 64 bytes from 104.18.123.189: icmp_seq=3 ttl=59 time=11.8 ms 64 bytes from 104.18.123.189: icmp_seq=4 ttl=59 time=10.1 ms ^C --- www.thec64community.online ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3004ms rtt min/avg/max/mdev = 9.717/11.615/14.688/1.951 ms # apt update Hit http://security.debian.org jessie/updates InRelease Ign http://ftp.uk.debian.org jessie InRelease Hit http://ftp.uk.debian.org jessie-updates InRelease Hit http://ftp.uk.debian.org jessie Release.gpg Hit http://ftp.uk.debian.org jessie Release Hit http://security.debian.org jessie/updates/main Sources Hit http://security.debian.org jessie/updates/contrib Sources Hit http://security.debian.org jessie/updates/non-free Sources Hit http://security.debian.org jessie/updates/main armhf Packages Hit http://security.debian.org jessie/updates/contrib armhf Packages Hit http://security.debian.org jessie/updates/non-free armhf Packages Hit http://security.debian.org jessie/updates/contrib Translation-en Hit http://security.debian.org jessie/updates/main Translation-en Hit http://ftp.uk.debian.org jessie-updates/main Sources Hit http://security.debian.org jessie/updates/non-free Translation-en Hit http://ftp.uk.debian.org jessie-updates/contrib Sources Hit http://ftp.uk.debian.org jessie-updates/non-free Sources Hit http://ftp.uk.debian.org jessie-updates/main armhf Packages Hit http://ftp.uk.debian.org jessie-updates/contrib armhf Packages Hit http://ftp.uk.debian.org jessie-updates/non-free armhf Packages Hit http://ftp.uk.debian.org jessie-updates/contrib Translation-en Hit http://ftp.uk.debian.org jessie-updates/main Translation-en Hit http://ftp.uk.debian.org jessie-updates/non-free Translation-en Hit http://ftp.uk.debian.org jessie/main Sources Hit http://ftp.uk.debian.org jessie/contrib Sources Hit http://ftp.uk.debian.org jessie/non-free Sources Hit http://ftp.uk.debian.org jessie/main armhf Packages Hit http://ftp.uk.debian.org jessie/contrib armhf Packages Hit http://ftp.uk.debian.org jessie/non-free armhf Packages Hit http://ftp.uk.debian.org jessie/contrib Translation-en Hit http://ftp.uk.debian.org jessie/main Translation-en Hit http://ftp.uk.debian.org jessie/non-free Translation-en Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. #
Can you ping anything?
|
|
|
Post by MeneerJansen on Sept 10, 2020 13:19:34 GMT
Unfortunately, no. Output of ping: # ping www.thec64community.online ping: unknown host www.thec64community.online root@Desktop-PC:/#
I am behind a VPN. But if I disable the VPN (and wait for my internet connection to be up again), same thing.
|
|
|
Post by jj0 on Sept 10, 2020 16:02:29 GMT
Unfortunately, no. Output of ping: # ping www.thec64community.online ping: unknown host www.thec64community.online root@Desktop-PC:/#
I am behind a VPN. But if I disable the VPN (and wait for my internet connection to be up again), same thing. Hmmm... It works for me on Ubuntu 20.04 Can you do the following both before and after chrooting: # cat /etc/resolv.conf
and
# ip a
You can also try to mount various system directories before chrooting: sudo su mount -t proc proc /tmp/chroot/proc mount -t devtmpfs devtmpfs /tmp/chroot/dev mkdir /tmp/chroot/dev/pts mount -t devpts devpts /tmp/chroot/dev/pts mkdir /tmp/chroot/dev/shm mount -t tmpfs tmpfs /tmp/chroot/dev/shm mount -t tmpfs tmpfs /tmp/chroot/tmp mkdir -p /tmp/log mount --bind /tmp/log /tmp/chroot/var/log mount --bind /sys /tmp/chroot/sys mount --bind /run /tmp/chroot/run
chroot /mnt /bin/bash
|
|
|
Post by MeneerJansen on Sept 14, 2020 13:03:02 GMT
Unfortunately, no. Output of ping: # ping www.thec64community.online ping: unknown host www.thec64community.online root@Desktop-PC:/#
I am behind a VPN. But if I disable the VPN (and wait for my internet connection to be up again), same thing. Hmmm... It works for me on Ubuntu 20.04 Can you do the following both before and after chrooting: # cat /etc/resolv.conf
and
# ip a
You can also try to mount various system directories before chrooting: sudo su mount -t proc proc /tmp/chroot/proc mount -t devtmpfs devtmpfs /tmp/chroot/dev mkdir /tmp/chroot/dev/pts mount -t devpts devpts /tmp/chroot/dev/pts mkdir /tmp/chroot/dev/shm mount -t tmpfs tmpfs /tmp/chroot/dev/shm mount -t tmpfs tmpfs /tmp/chroot/tmp mkdir -p /tmp/log mount --bind /tmp/log /tmp/chroot/var/log mount --bind /sys /tmp/chroot/sys mount --bind /run /tmp/chroot/run
chroot /mnt /bin/bash Sorry for not replying sooner: I didn't get an e-mail notification of your reply (in this forum the notification sometimes works, sometimes it doesn't). That tip of yours about the resolv.conf file and this topic about internet access inside a chroot awoke me. The VPN that I use (of course) alters my resolv.conf. In weird ways. You need a working copy of resolv.conf in the chroot/ rootfs.img. So outside of the chroot I did: sudo cp /etc/resolv.conf /mnt/temp/etc/
(I mounted rootfs.img in /mnt/temp/). And now it works! Thanks again. Do you know how to get internet on The C64 with a Wifi USB dongle? I have a Wifi dongle that works in Linux. Wonder how to get it working on The C64...
|
|
|
Post by jj0 on Sept 14, 2020 19:11:28 GMT
Hmmm... It works for me on Ubuntu 20.04 Can you do the following both before and after chrooting: # cat /etc/resolv.conf
and
# ip a
You can also try to mount various system directories before chrooting: <snip> Sorry for not replying sooner: I didn't get an e-mail notification of your reply (in this forum the notification sometimes works, sometimes it doesn't). That tip of yours about the resolv.conf file and this topic about internet access inside a chroot awoke me. The VPN that I use (of course) alters my resolv.conf. In weird ways. You need a working copy of resolv.conf in the chroot/ rootfs.img. So outside of the chroot I did: sudo cp /etc/resolv.conf /mnt/temp/etc/
(I mounted rootfs.img in /mnt/temp/). And now it works! Thanks again. Do you know how to get internet on The C64 with a Wifi USB dongle? I have a Wifi dongle that works in Linux. Wonder how to get it working on The C64... Nice to see that it works now. To get wireless working on tho Maxi could be a bit of a struggle: - First you need to manually install the wireless tools framework (a.o. wpa_supplicant). If you can figure out what these are exactly you might be able to copy them from XWM
- Then you need a kernel driver for your particular Wifi dongle. This needs to be compiled specifically for the Maxi's kernel. But so far not all kernel modules that I've compiled for the Maxi work, as i/we don't have the source code + configuration used for the Maxi's kernel so I've been using some generic Allwinner SDK's. But if you can provide the brand, type and chipset of your Wifi dongle I'd be happy to see whether there is a kernel module for it whether it compiles and loads without error.
- Then you need to configure wpa_suplicant.conf an make at all start at boot
It might be slightly easier to load the (currently hypothetical) Wifi dongle kernel module befor starting XWM and then try if it works in XWM as XWM already has the necessary wireless tools framework installed.
|
|
|
Post by MeneerJansen on Sept 14, 2020 20:55:20 GMT
Nice to see that it works now. To get wireless working on tho Maxi could be a bit of a struggle: - First you need to manually install the wireless tools framework (a.o. wpa_supplicant). If you can figure out what these are exactly you might be able to copy them from XWM
- Then you need a kernel driver for your particular Wifi dongle. This needs to be compiled specifically for the Maxi's kernel. But so far not all kernel modules that I've compiled for the Maxi work, as i/we don't have the source code + configuration used for the Maxi's kernel so I've been using some generic Allwinner SDK's. But if you can provide the brand, type and chipset of your Wifi dongle I'd be happy to see whether there is a kernel module for it whether it compiles and loads without error.
- Then you need to configure wpa_suplicant.conf an make at all start at boot
It might be slightly easier to load the (currently hypothetical) Wifi dongle kernel module befor starting XWM and then try if it works in XWM as XWM already has the necessary wireless tools framework installed.
Didn't realize it could be that difficult. I managed to install Synaptic in the chroot and I can run that with it's GUI from the chroot. So installing software is not that hard now. I tried to install a driver/firmware for my Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter (kernal driver: rtl8192cu) via this tutorial. Appeared to go okay, but the light did not go up when I inserted the USB wifi dongle. Thanks to your post I know why. You do not have to go to a lot of trouble to try to get Wifi working for me. What exactly do you mean by XWM? Do you think that a "usb to wired ethernet" adapter like this one would be easier to get internet with on The C64?
|
|
|
Post by jj0 on Sept 15, 2020 7:22:01 GMT
Nice to see that it works now. To get wireless working on tho Maxi could be a bit of a struggle: - First you need to manually install the wireless tools framework (a.o. wpa_supplicant). If you can figure out what these are exactly you might be able to copy them from XWM
- Then you need a kernel driver for your particular Wifi dongle. This needs to be compiled specifically for the Maxi's kernel. But so far not all kernel modules that I've compiled for the Maxi work, as i/we don't have the source code + configuration used for the Maxi's kernel so I've been using some generic Allwinner SDK's. But if you can provide the brand, type and chipset of your Wifi dongle I'd be happy to see whether there is a kernel module for it whether it compiles and loads without error.
- Then you need to configure wpa_suplicant.conf an make at all start at boot
It might be slightly easier to load the (currently hypothetical) Wifi dongle kernel module befor starting XWM and then try if it works in XWM as XWM already has the necessary wireless tools framework installed.
Didn't realize it could be that difficult. I managed to install Synaptic in the chroot and I can run that with it's GUI from the chroot. So installing software is not that hard now. I tried to install a driver/firmware for my Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter (kernal driver: rtl8192cu) via this tutorial. Appeared to go okay, but the light did not go up when I inserted the USB wifi dongle. Thanks to your post I know why. You do not have to go to a lot of trouble to try to get Wifi working for me. What exactly do you mean by XWM? Do you think that a "usb to wired ethernet" adapter like this one would be easier to get internet with on The C64? XWM = 'THEC64 X-Windows Mod' I have the USB2Ethernet adapter from your link (or at least it looks the same), it works great on the Mini for which the kernel source is available so it was easy to compile the required module. For the Maxi I haven't been able to get a working kernel module/driver, the variants I've tried all crash. But if/when the kernel source for the Maxi is available it should be possible to get a working driver.
|
|
|
Post by spannernick on Oct 30, 2020 12:01:18 GMT
This now can be run in PCU and by pressing CTRL-F7, but its not included, you need to put it `rootfs.img` in `Carousel_Games/Options/X-Windows Mod/`
PCU is on my sig below..
|
|
|
Post by mobluse on Dec 28, 2020 23:27:48 GMT
I have the USB2Ethernet adapter from your link (or at least it looks the same), it works great on the Mini for which the kernel source is available so it was easy to compile the required module. For the Maxi I haven't been able to get a working kernel module/driver, the variants I've tried all crash. But if/when the kernel source for the Maxi is available it should be possible to get a working driver. I have a usb-ethernet dongle, but it doesn't work out of the box with XWM on THEC64 MINI. Maybe you could help me with drivers. It works in the latest and most updated Raspberry Pi OS on Raspberry Pi 4 B 8 GB RAM. On Raspberry Pi: dmesg: [148019.376391] usb 1-1.3.4: new high-speed USB device number 23 using xhci_hcd [148019.489068] usb 1-1.3.4: New USB device found, idVendor=0b95, idProduct=772b, bcdDevice= 0.02 [148019.489088] usb 1-1.3.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [148019.489101] usb 1-1.3.4: Product: AX88772C [148019.489113] usb 1-1.3.4: Manufacturer: ASIX Elec. Corp. [148019.489124] usb 1-1.3.4: SerialNumber: 00000A [148019.909864] asix 1-1.3.4:1.0 eth1: register 'asix' at usb-0000:01:00.0-1.3.4, ASIX AX88772B USB 2.0 Ethernet, 00:00:10:00:50:52 [148021.606422] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready [148021.609696] asix 1-1.3.4:1.0 eth1: link up, 100Mbps, full-duplex, lpa 0x5DE1 lsusb: Bus 001 Device 023: ID 0b95:772b ASIX Electronics Corp. AX88772B ip a: 6: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 00:00:10:00:50:52 brd ff:ff:ff:ff:ff:ff inet 192.168.1.136/24 brd 192.168.1.255 scope global dynamic noprefixroute eth1 valid_lft 85982sec preferred_lft 75182sec inet6 fe80::889f:4446:6107:84f9/64 scope link valid_lft forever preferred_lft forever On THEC64 MINI it only shows up in lsusb, but nothing happens in dmesg and ip a or ifconfig -a doesn't get any IP number.
|
|
|
Post by jj0 on Dec 29, 2020 9:13:54 GMT
I have the USB2Ethernet adapter from your link (or at least it looks the same), it works great on the Mini for which the kernel source is available so it was easy to compile the required module. For the Maxi I haven't been able to get a working kernel module/driver, the variants I've tried all crash. But if/when the kernel source for the Maxi is available it should be possible to get a working driver. I have a usb-ethernet dongle, but it doesn't work out of the box with XWM on THEC64 MINI. Maybe you could help me with drivers. It works in the latest and most updated Raspberry Pi OS on Raspberry Pi 4 B 8 GB RAM. On Raspberry Pi: dmesg: [148019.376391] usb 1-1.3.4: new high-speed USB device number 23 using xhci_hcd [148019.489068] usb 1-1.3.4: New USB device found, idVendor=0b95, idProduct=772b, bcdDevice= 0.02 [148019.489088] usb 1-1.3.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [148019.489101] usb 1-1.3.4: Product: AX88772C [148019.489113] usb 1-1.3.4: Manufacturer: ASIX Elec. Corp. [148019.489124] usb 1-1.3.4: SerialNumber: 00000A [148019.909864] asix 1-1.3.4:1.0 eth1: register 'asix' at usb-0000:01:00.0-1.3.4, ASIX AX88772B USB 2.0 Ethernet, 00:00:10:00:50:52 [148021.606422] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready [148021.609696] asix 1-1.3.4:1.0 eth1: link up, 100Mbps, full-duplex, lpa 0x5DE1 lsusb: Bus 001 Device 023: ID 0b95:772b ASIX Electronics Corp. AX88772B ip a: 6: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 00:00:10:00:50:52 brd ff:ff:ff:ff:ff:ff inet 192.168.1.136/24 brd 192.168.1.255 scope global dynamic noprefixroute eth1 valid_lft 85982sec preferred_lft 75182sec inet6 fe80::889f:4446:6107:84f9/64 scope link valid_lft forever preferred_lft forever On THEC64 MINI it only shows up in lsusb, but nothing happens in dmesg and ip a or ifconfig -a doesn't get any IP number. Can you check whether it works when you boot the Mini in FEL mode? I included a relatively recent ASIX driver in it. If it works then you can use that driver but you have to load it before starting XWM. I can provide an updated XWM that includes module loading before starting XWM.
|
|
|
Post by jj0 on Dec 29, 2020 11:25:43 GMT
I have a usb-ethernet dongle, but it doesn't work out of the box with XWM on THEC64 MINI. Maybe you could help me with drivers. It works in the latest and most updated Raspberry Pi OS on Raspberry Pi 4 B 8 GB RAM. On Raspberry Pi: dmesg: [148019.376391] usb 1-1.3.4: new high-speed USB device number 23 using xhci_hcd [148019.489068] usb 1-1.3.4: New USB device found, idVendor=0b95, idProduct=772b, bcdDevice= 0.02 [148019.489088] usb 1-1.3.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [148019.489101] usb 1-1.3.4: Product: AX88772C [148019.489113] usb 1-1.3.4: Manufacturer: ASIX Elec. Corp. [148019.489124] usb 1-1.3.4: SerialNumber: 00000A [148019.909864] asix 1-1.3.4:1.0 eth1: register 'asix' at usb-0000:01:00.0-1.3.4, ASIX AX88772B USB 2.0 Ethernet, 00:00:10:00:50:52 [148021.606422] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready [148021.609696] asix 1-1.3.4:1.0 eth1: link up, 100Mbps, full-duplex, lpa 0x5DE1 lsusb: Bus 001 Device 023: ID 0b95:772b ASIX Electronics Corp. AX88772B ip a: 6: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 00:00:10:00:50:52 brd ff:ff:ff:ff:ff:ff inet 192.168.1.136/24 brd 192.168.1.255 scope global dynamic noprefixroute eth1 valid_lft 85982sec preferred_lft 75182sec inet6 fe80::889f:4446:6107:84f9/64 scope link valid_lft forever preferred_lft forever On THEC64 MINI it only shows up in lsusb, but nothing happens in dmesg and ip a or ifconfig -a doesn't get any IP number. Can you check whether it works when you boot the Mini in FEL mode? I included a relatively recent ASIX driver in it. If it works then you can use that driver but you have to load it before starting XWM. I can provide an updated XWM that includes module loading before starting XWM. I found out I have the same network adapter and it works in the FEL mode. If you unzip the attached zipfile on the root of your XWM USB stick it will add a modules directory with various USB2Ethernet adapter modules and it will replace start.sh, adding loading of the ASIX driver. To get an IP address and allow DNS name resolution once XWM is started you will need to run 'dhclient eth0' in a terminal window. Note: - For whatever reason ping doesn't work - The rootfs.img is now mounted read/write because dhclient needs to be able to write to /etc/resolv.conf. If you're always using your home network then you'll only need to have this written once and you could change the mount back to read-only in start.sh. Attachments:XWMusbethernet.zip (966.53 KB)
|
|
|
Post by spannernick on Dec 29, 2020 14:20:16 GMT
This would not work in XWM in PCUAE because the rootfs.img needs to be mounted as rw, it don't work if it mounted as ro, it can't read the img, comes up with a error and don't load, it probably the loop device its using so you can see USB Stick in File Loader and Media Access.
|
|
|
Post by mobluse on Dec 30, 2020 1:28:11 GMT
Can you check whether it works when you boot the Mini in FEL mode? I included a relatively recent ASIX driver in it. If it works then you can use that driver but you have to load it before starting XWM. I can provide an updated XWM that includes module loading before starting XWM. I found out I have the same network adapter and it works in the FEL mode. If you unzip the attached zipfile on the root of your XWM USB stick it will add a modules directory with various USB2Ethernet adapter modules and it will replace start.sh, adding loading of the ASIX driver. To get an IP address and allow DNS name resolution once XWM is started you will need to run 'dhclient eth0' in a terminal window. Note: - For whatever reason ping doesn't work - The rootfs.img is now mounted read/write because dhclient needs to be able to write to /etc/resolv.conf. If you're always using your home network then you'll only need to have this written once and you could change the mount back to read-only in start.sh. Thanks! This works and is very stable, but some things are very slow, e.g. apt update and aptitude. Maybe it could be faster if I only load a minimal set of modules. I could run the web browser Dillo with some sites, but not with this, because then Cloudflare gave an error 403. I could also log in to other computers using telnet and ssh.
|
|
|
Post by MeneerJansen on Dec 30, 2020 10:44:30 GMT
Thanks! This works and is very stable, but some things are very slow, e.g. apt update and aptitude. Maybe it could be faster if I only load a minimal set of modules. I could run the web browser Dillo with some sites, but not with this, because then Cloudflare gave an error 403. I could also log in to other computers using telnet and ssh. You you know where you bought that network adapter? Aliexpress? Is it this one:
|
|
|
Post by spannernick on Dec 30, 2020 11:51:34 GMT
Would this work on THEC64 Maxi, well I know the driver will not because its for the Mini's kernel, so can a driver be made for THEC64 Maxi for XWM..?
|
|
|
Post by mobluse on Dec 30, 2020 13:13:36 GMT
Thanks! This works and is very stable, but some things are very slow, e.g. apt update and aptitude. Maybe it could be faster if I only load a minimal set of modules. I could run the web browser Dillo with some sites, but not with this, because then Cloudflare gave an error 403. I could also log in to other computers using telnet and ssh. You you know where you bought that network adapter? Aliexpress? Is it this one: It was this that I bought: AX88772B from www.electrokit.com/produkt/usb-till-ethernet-adapter-ax88772b/ . The company that makes them or at least the chips: www.asix.com.tw/en .
|
|
|
Post by MeneerJansen on Dec 30, 2020 13:38:38 GMT
Thanks.
|
|
|
Post by jj0 on Dec 30, 2020 13:43:11 GMT
Would this work on THEC64 Maxi, well I know the driver will not because its for the Mini's kernel, so can a driver be made for THEC64 Maxi for XWM..? No, not until we have the source and kernel .config
|
|
|
Post by jj0 on Dec 30, 2020 13:45:06 GMT
Thanks! This works and is very stable, but some things are very slow, e.g. apt update and aptitude. Maybe it could be faster if I only load a minimal set of modules. I could run the web browser Dillo with some sites, but not with this, because then Cloudflare gave an error 403. I could also log in to other computers using telnet and ssh. You you know where you bought that network adapter? Aliexpress? Is it this one: The driver for that one is included in the zip file as well I think, I have that one as well. You just have to try which driver to load in start.sh.
|
|
|
Post by jj0 on Dec 30, 2020 13:46:46 GMT
I found out I have the same network adapter and it works in the FEL mode. If you unzip the attached zipfile on the root of your XWM USB stick it will add a modules directory with various USB2Ethernet adapter modules and it will replace start.sh, adding loading of the ASIX driver. To get an IP address and allow DNS name resolution once XWM is started you will need to run 'dhclient eth0' in a terminal window. Note: - For whatever reason ping doesn't work - The rootfs.img is now mounted read/write because dhclient needs to be able to write to /etc/resolv.conf. If you're always using your home network then you'll only need to have this written once and you could change the mount back to read-only in start.sh. Thanks! This works and is very stable, but some things are very slow, e.g. apt update and aptitude. Maybe it could be faster if I only load a minimal set of modules. I could run the web browser Dillo with some sites, but not with this, because then Cloudflare gave an error 403. I could also log in to other computers using telnet and ssh. Nice that it works. I think the slowness is caused by it being on USB mostly. Also lack of memory. E.g. Firefox doesn't even load.
|
|
|
Post by jj0 on Dec 31, 2020 12:03:44 GMT
You you know where you bought that network adapter? Aliexpress? Is it this one: The driver for that one is included in the zip file as well I think, I have that one as well. You just have to try which driver to load in start.sh. Mine is idVendor=0424, idProduct=7500, 'smsc75xx USB 2.0 Gigabit Ethernet' so not exactly the same as yours. But if you use 'smsc75xx.ko' instead of 'asix.ko' in start.sh then it might work. Only on the Mini of course.
|
|
|
Post by mobluse on Feb 18, 2021 23:40:29 GMT
Thanks! This works and is very stable, but some things are very slow, e.g. apt update and aptitude. Maybe it could be faster if I only load a minimal set of modules. I could run the web browser Dillo with some sites, but not with this, because then Cloudflare gave an error 403. I could also log in to other computers using telnet and ssh. Nice that it works. I think the slowness is caused by it being on USB mostly. Also lack of memory. E.g. Firefox doesn't even load. It's faster to update if the USB stick is directly connected to the THEC64 MINI ─ maybe my USB hub was slow ─ even though it claims to be USB2. I get less errors with certificates on web sites if I set time and date first using: date MMDDhhmmYY e.g. date 0219003421. I tried to install fake-hwclock (which is in the Debian Jessie repos), but that didn't work (it works on Raspberry Pi). I also tried to use my USB stick with network on THEVIC20, but then it didn't boot. I had to comment the lines related to network in start.sh in order for it to boot. # Load asix usb network driver and bring up interface #/mnt/modules/insmod -f /mnt/modules/mii.ko #/mnt/modules/insmod -f /mnt/modules/usbnet.ko #/mnt/modules/insmod -f /mnt/modules/asix.ko #ifup -a Is it possible to sense what model the start.sh script is running on (THEC64 MINI or THEC64 full size, or THEVIC20)? because then I could have some conditional statement that would not load network modules on non MINI. BTW could I, who have an ASIX network adapter, remove the lines mii.ko or usbnet.ko from start.sh when I use the MINI, and have the network still working? You said one could not get network to work on THEC64 (full size) and THEVIC20 without some source code and kernel config. It is possible to order the source code from RGL for £5 (see bottom of licenses for address), but I read people had already tried that without success, but maybe someone in UK could try again (because it's difficult to get money orders from abroad), and get the source code for the latest released firmware. Maybe the first request got lost in the mail.
|
|
|
Post by jj0 on Feb 19, 2021 7:34:52 GMT
Nice that it works. I think the slowness is caused by it being on USB mostly. Also lack of memory. E.g. Firefox doesn't even load. It's faster to update if the USB stick is directly connected to the THEC64 MINI ─ maybe my USB hub was slow ─ even though it claims to be USB2. I get less errors with certificates on web sites if I set time and date first using: date MMDDhhmmYY e.g. date 0219003421. I tried to install fake-hwclock (which is in the Debian Jessie repos), but that didn't work (it works on Raspberry Pi). Instead of manually setting the time you could also install ntpdate and run it against your favourite internet time server: # apt install ntpdate # ntpdate pool.ntp.org If necessary you can first set the timezone with: # dpkg-reconfigure tzdata It's possible to check what model the script is running on, in fact both my 'full blown VICE' fake update script and spannernick 's PCUAE do this already. Mii.ko and usbnet.ko are required for any USB network driver to function. grasshopper has requested the source, AFAIK it wasn't lost in the mail, but he hasn't received any source code yet. RGL seem to not really care all that much about complying with the GPL in a speedy manner. They probably focus on new product development and firmware updates. There is however a way to get networking to work on the Maxi models (incl THEVIC20), by powering them from your PC's USB port and enabling the OTG networking from the Maxi. This is what I already do with the FEL-mode rescue method for the Maxi's and as it happens I have been working on incorporating it in XWM as well. If you use this updated start.sh (2.48 KB) then you can try it out. For networking to work you will need to configure your PC to share its network with the OTG network adapter. In my Ubuntu Linux that's easy, just go into the Network Manager and set the interface that has appeared to 'Shared to other computers'. After that run dhclient on the Maxi and it will get an IP address. For DNS to work you will still need to edit the /etc/resolv.conf file and change the IP address there to a working nameserver as Ubuntu doesn't provide name resolution with the network sharing. In Windows this is probably also possible to set up but I haven't looked into it. If you get this working then it would be nice if you can provide a description. <EDIT> Btw, you can't update/install software via apt, apt-get or dpkg in XWM on the Maxi, for some reason RGL have disabled file locking in the Maxi's kernel so apt/apt-get/dpkg error out with being unable to lock the various lockfiles after creating them. Good luck with it and I hope you have fun trying.
|
|
|
Post by MeneerJansen on Feb 19, 2021 12:48:33 GMT
There is however a way to get networking to work on the Maxi models (incl THEVIC20), by powering them from your PC's USB port and enabling the OTG networking from the Maxi. This is what I already do with the FEL-mode rescue method for the Maxi's and as it happens I have been working on incorporating it in XWM as well. If you use this updated View Attachment then you can try it out. That file can only be downloaded if you're logged in a a member. Just FYI. <EDIT> Btw, you can't update/install software via apt, apt-get or dpkg in XWM on the Maxi, for some reason RGL have disabled file locking in the Maxi's kernel so apt/apt-get/dpkg error out with being unable to lock the various lockfiles after creating them. Good luck with it and I hope you have fun trying. I don't know what you mean exactly but I managed on my 'The C64 Maxi' to install stuff (themes etc.) permanently. You have to mount the file system as writable instead of read-only. Do that like this (learned it from you): in 'start.sh' on the USB drive change the 'mount -o ro /mnt/rootfs.img /tmp/chroot' to 'mount -o rw /mnt/rootfs.img /tmp/chroot' to make it writable.
|
|
|
Post by jj0 on Feb 19, 2021 13:01:50 GMT
There is however a way to get networking to work on the Maxi models (incl THEVIC20), by powering them from your PC's USB port and enabling the OTG networking from the Maxi. This is what I already do with the FEL-mode rescue method for the Maxi's and as it happens I have been working on incorporating it in XWM as well. If you use this updated View Attachment then you can try it out. That file can only be downloaded if you're logged in a a member. Just FYI. Ok, thanks. Nothing I can do about that, but if it helps getting more members than I have no problem with it 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?
|
|