• Hello, Guest! Welcome back, and be sure to check out this post for more info about the recent service interruption and migration.

TashTalk: Single-Chip LocalTalk Interface


Active member
nothing still in use today talks Phase 1, including the Linux kernel drivers for AppleTalk
Do the kernel drivers even enter into it, though? Netatalk 2.x talks Phase 1, or at least the options make it appear that it does, so if you create a tap and put EtherTalk Phase 1 frames into it, and Netatalk picks them up, what does the kernel know or care?


Well-known member
Both IP and AppleTalk stacks are actually in kernel space; netatalk provides application services but doesn't do actual network-level stuff. This made sense when maximum performance was the goal here. Unfortunately, at this point, all this means it that when the Linux people decide to break the kernel AppleTalk stack again, netatalk stops working and there's nothing much anyone can do about it, especially given the rather dodgy attitude towards patches in the Linux kernel.

This, among other reasons, is why, pace some people, I do not believe that netatalk2, especially on Linux, is a feasible middling- or long-term solution to providing network services to older machines.


Well-known member
For now AppleTalk is saved in Linux kernel. I have it working with a modern Linux on my MacIPRpi. Bug is fixed thanks to a fellow 68kmla member.

But LocalTalk PC Cards stopped to work after Debian 3.0 (Woody). For now I’m testing from Debian 2.2 to Debian 6. As said… will make a separate post about this. Also acquired a DL2000 card which works with COPS driver. Seems more modern then the first LocalTalk PC Cards. I hope to get it working.