Hello, I've used both FTDI and Prolific USB-serial converters but I had to compile the kernel to get them to work. This is going to depend a lot on your Linux distro. I use Gentoo and make my own kernel. I assume mint wants the modules loaded but evertyhing is already prepared. I would assume the modules need to be loaded, so plug in the adapter and check to see if the modules are there.
lsmod | grep SERIAL For the FTDI, it is called USB_SERIAL_FTDI_SIO, and it needs the USB_SERIAL module as well For the Prolific, it is called USB_SERIAL_PL2303 I generally check them by connecting the M100 and the linux machine together and run telcom on the M100 and something like minicom on linux just to see if what I type on one shows up on the other. Jonathan [email protected] ________________________________________ Från: M100 [[email protected]] för Brian White [[email protected]] Skickat: den 21 december 2017 12:05 Till: [email protected] Ämne: Re: [M100] dlplus on linux mint That's reasonable. I only say those are known vs unknown. I ohmed them all out and mapped the actual connections by hand, not merely used them. For various reasons in each case, I don't think you have to worry about your usb-serial adapter, OS, or the dlplus software. That leaves the hardware of the linux host (old motherboard with bad caps or bad ram etc), or the serial cable, or the m100. You could run memtest86 on the linux box overnight and that should be good enough to vet the host hardware, and you can map out your serial cable and clear that. -- bkw On Dec 21, 2017 3:16 AM, "Peter Vollan" <[email protected]<mailto:[email protected]>> wrote: The problem is, I do not know why my three other cables did not work, so I am skeptical of just spending money for another one. On 20 December 2017 at 21:49, Brian White <[email protected]<mailto:[email protected]>> wrote: > Get one of these cables (one of the 3 "ideal" ones, ie, get the cables2go > one. You almost certainly do not need any different usb-serial adapter, but > if you want then get the ftdi one linked there too. > > I actually use an old and underpowered atom cpu netbook, so, speed/power of > the linux host is not likely an issue. > > I have had zero bad transfers even with no-name prolific adapters (I have > picked up several over time because I use them for all kinds of things for > both work and hobby), and the not-full-handshake monoprice 479 cable, using > dlplus and either teeny or ts-dos, on 2 different m100's, a t102, a t200, > and a 600 (xmodem not tpdd for the 600, but the same cables and linux host) > > This is with various versions of "lubuntu" from 14.04 to 17.10, and usually > using the mainline kernel of the day. (google "ubuntu mainline", takes you > to a site where you can get kernel .debs of the current generic upstream > kernel) as well as the normal stock kernels. > > So maybe just get a serial cable that is guaranteed known to be wired > correctly, and see from there. Without even seeing them I'm not suspicious > of your usb-serial adapters. Although, usb plugs themselves can be pretty > bad. Wobbly bad usb plugs/sockets where the usb plug just doesn't make > reliable good contact are a thing. > > I personally have purchased and tested everything on that page. > > So, if you just want to remove all doubt, get the C2G serial cable and the > Tera Grande usb cable. > > http://tandy.wiki/Model_100_102_200_600_Serial_Cable > > > -- > bkw > > On Dec 20, 2017 10:52 PM, "Peter Vollan" > <[email protected]<mailto:[email protected]>> wrote: >> >> On a positive note, thank you to everyone whose advice helped me to >> finally get Virtual T working on my Linux Mint laptop. >> >> I think I may have said that I had Desklink working, and was >> communicating with my Model 100. Well, I spoke too soon. The best way >> I can explain it is that it seemed to be working, but it is actually >> working sporadically or not at all. The fact that I have had some >> limited success tells me that I am very close, having solved obvious >> problems like permissions on the USB port. The fly in the ointment now >> is the USB to serial adaptor. >> >> I have had three so far, a radio shack model, a Prolific one, and my >> current one, an FTDI model with null modem built in. Here are the >> relevant lines from /etc/modlules: >> >> #usbserial vendor=0x1453 product=0x4026 >> #usbserial vendor=0x067b product=0x2303 >> usbserial vendor=0x0403 product=0x6001 >> >> I realise that this is more of Linux problem than a model T question, >> but it would be just great if I could actually succeed at this >> particular project. I have 3 different USB to serial cables available >> (actually I have three Prolific ones that are supposedly the same >> under the hood).
