Category: Kev’s Blog

Posted on

Revisiting SunPCI driver install on Solaris 10

I’ve posted before on installing the SunPCI drivers on Solaris 10 but skipped a few steps. Sites to download the drivers are limited, but if you Google for the exact file name, you can find some locations, search for SUNWspci3.tar.Z

Unzip the file with:

uncompress *.Z

The untar with:

tar xf SUNWspci_13.tar

The SunPCI card in my Ultra60 is a 1.3 card, not 3, so be careful which package you download. Available options seem to be SUNWspci_13, SUNWspci2, SUNWspci3

Once you’ve untar’ed, run in the same folder:

pkgadd -d .

(not as I said before to cd into the untar’d folder). At this point you should be able to follow the rest of the steps in the previous post.

I’m reinstalling and setting up Solaris 10 on this box since I spent some time installing FreeBSD and then Solaris 8, and decided Solaris 10 was actually the better option, so I’m going that to that again (Solaris 8 I couldn’t get to install).

At some point I must have mounted a shared drive on my NAS to copy files to/from this box, so I’ll also take a look at getting that going again (I don’t think I took any notes), I could have used ftp. Will see what works.

Posted on

Troubleshooting serial terminal connections (VT Serial Terminal, VT132, Packet Radio TNCs)

I’ve been on a serial terminal kick the last few months. I think it started when I picked up a used Sun Ultra 60 and found out you could boot with a serial terminal to diagnose boot issues, and/or logon via a serial terminal. I built a VT132 kit and this has worked well using a regular VGA monitor and USB keyboard, but one thing lead to another and I started shopping ebay for a real DEC VT terminal. These are getting harder to find in working condition and it seems the prices are going up to pretty crazy levels. You can easily get one around $200 to $300, but if you shop around you should be able to get one around $100.

I’ve been able to connect the VT132 to anything so far and get it to work. There are a couple of jumpers on the board to select a straight through or crossover cable connection, if one doesn’t work change it to the other and it will connect. I’ve used it so far to connect to a AEA PK-232 Amateur Radio packet TNC, my Ultra 60, and a PC running Ubuntu.

The VT terminal on the other hand is more tricky. It will connect to the PK-232 and the wifi modem on the VT132, but I have not been able to successfully connect it to do a serial terminal logon to a Raspberry Pi (this was my main goal), or another PC yet.

My suspicion is that the 2 serial cables I have that I’ve been using interchangeably depending on what I’ve connecting too just based on the connectors are not the same. One has DB25 to DB25, the other has DB9 to DB25, so I’ve been picking the one that connects between the two devices. I’ve assumed these are both null modem cables, but I think one is straight through, and I don’t know which is which. I need to test them with a meter to find out.

I also thought the USB to serial connector that I was using on the Raspberry Pi was not working (it was a FTDI chip) so I bought another one using the Prolific chip, and that didn’t work either connecting from the VT Terminal, but it did from the VT132, so I think this is more to do with the serial cable than the Serial USB adapter. I think the clue was that from the VT132 it only worked when I switched the straightthrough to crossover jumpers to crossover, actually the same setting that works with the Ultra 60 too (but not the PK-232).

My next steps are to create a table of all the combinations that work vs don’t work. I also need to test the cables to find out if one is a straight through vs the other being a crossover cable. I think assuming they were the same is not true and this is causing the confusion. I will keep you updated on my findings!

Posted on

“zsh: No match found” error

zsh attempts to expand any potential filename wildcard characters (such as ‘*’ and ‘?’) used in a command before executing it. This can lead to the confusing error “zsh: No match found” error. What makes this confusing is if you’re trying to execute a grep or something where you are trying to find or match something, since the error implies your search is not working, whereas the error is about the patterns zsh is attempting to expand in the command string, and not from executing the command itself.

Depending on what you’re trying to do, the easiest workaround is to wrap parameters in quotes or escape characters like ‘*’ and ‘?’.

e.g. for curl, wrap urls in quotes.

Posted on

Using a Unisys VT terminal with VT132 as a wifi modem

I just picked up a Unisys TO300G VT terminal to use for a few retro projects, and tried connecting it to my VT132 and use it as a wifi AT modem. Initially I wasn’t getting anything echo’d to the screen, then remembered I needed to set the speed to 115200, and then started getting a response from the VT132.

Here’s the menu, with the speed initially at 19200 8N1 :

Now we’ve got responses echoing back but there’s a bunch of CR/LF chars:

Turns out they’re echo’d to the screen if you have the Monitor Mode set to ON, so turning this option off fixed this. Also, the backspace key wasn’t working, and the Recognize Del option set to ON fixed this:

Now using ATD to dial up bbb.fozztexx.com and we’re in business:

Loving the amber glow of the text on this terminal, and the smooth scrolling is <3

Proudly powered by WordPress