Search results

Before I let the smoke out of something, is it safe to directly connect the tasktalk hat to an Apple //gs serial port - or do I need the localtalk transformers + phone wire in between?

I reflashed the SD card with the current 32-bit Raspbian and started working through the recipe. There appears to be a step missing. I have created the /etc/network/interfaces.d/br0 file per instructions, disabled dhcpcd using systemctl and rebooted. Now I have no networking. None of the...

I'm throwing in the towel for now. The writeup I'm trying to follow assumes Raspbian with systemd and I'm running Void Linux. For example, there is no /etc/network/interfaces.d directory in which to create the br0 specification. Clearly this effort will need to wait until the Void Linux folks...

From what I've read here, the issue is centered around the Wifi access point behavior during frame translation. I have a GL.inet router, which is Linux based and hopefully won't exhibit this problem. I'm using Tashtalk with a Pi Zero W and I'm not sure whether it supports a USB<-->ethernet...

Thanks - off I go! Thanks!

That's terrific news. I assume this update would be to a beta or testing release, correct? Where do they publish those?

I'll give that long set of directions a shot. Couple of questions: Can 'wlan0' be substituted for 'eth0' in order to use Wifi? With dhcpcd disabled, how does the RPi get assigned an IP address?

Well, that would explain it... In reading the preceeding pages of this topic I get the impression that the more common tun/tap utilities can also do the trick, but if the recipe is there I must have missed it. Can this work, or do I need to pickup a 64-bit RPi?

]$ modprobe macvtap modprobe: FATAL: Module macvtap not found in directory /lib/modules/6.1.69_1 Blast. Once again, the xbps-query tool finds nothing. How exactly does one get it to accept a wildcard?

I'm sorry for being dense, but I've read through this topic twice and it's totally unclear what - if anything - I can do to attempt bridging through the wifi connection. I'm far from a newbie, but I'm also not a networking expert and generally find the linux tap/routing documentation...

Ok.. That comes to a screeching halt on the first step: $ sudo ip link add link wlan0 name macvtap0 type macvtap Error: Unknown device type. Any input on this appreciated!

And - success! The major obstacle was figuring out the missing pyserial dependency on Void Linux. It's not part of the base Python 3 install and the xbps-query tool simply could not find it (must be something I'm misunderstanding about it). Finally, by sheer luck, I guessed the correct...

I'm trying to join the party, but need some more grounding in the fundamentals. For starters, what is the code in the tashtalk Git project as compared to tashrouter? Are they both needed? The tashtalkd code appears to want the name of an interface, but I do not know what it should be showing...

I'm able to mount the larger extracted image (HD1..) from my A/UX boot drive but fsck reports it as badly damaged. Anyone else see this issue? It does mount without complaint and I'm able to see the contents. Is it possibly too large for the OEM fsck tool to handle properly?

Fair enough. The GNU build system is dark, deep and impenetrable. The four or five folks who really understand it deeply aren't going to help with debugging. I suspect it's time to put a gun to my head and upgrade. As I wrote in the Github issue the same problem exists on the upstream HEAD.

@slipperygrey Did you ever get to the bottom of this error? I'm seeing the same thing when building on Ubuntu 18.04.

According to the A/UX FAQ, it is not strictly necessary to boot from System 7.0 and that turns out to be correct. I updated my MacPartition to 7.5.5, removing the A/UX Start alias from the Startup Items folder. This is a great dual boot environment. When I boot with no other action taken, it...