Hey George, thanks for your reply! You are correct about the location of the modules ... got it working now. Here's a summary of my experience in the hope that it will benefit someone else:
After installing F17, I couldn't install my beloved, old HP4 parallel port printer with a usb-to-parallel-printer cable. Futzed around with it for a while but couldn't figure it out. (I'm thinking maybe the usb-to-parallel-printer cable failed? Used it before (under F12) with no problems.
So I plugged in a PCI-parallel port card ("SYBA, PCI-Express, 1 Port Parallel Card"). Figured it would "just work" like most of the other hardware devices that I've plugged into my Linux boxes over the years, and tried system-config-printer, but the printer was not detected. And no LPT showed up either.
So I decided to RTFM.
The manual for this parallel card included many different versions of the device. Apparently you need to look at the actual board to see which chip is on the board to find which set of instructions to follow. Mine had a "MosChip MCS9900" chip on board. 99% of those instructions were for a Serial card, but at the very end were the instructions for installing this parallel card:
Steps for setting parallel port :
1. rmmod lp
2. rmmod parport_pc
3. insmod /usr/lib/modules/2.6.15/kernel/drivers/parport/parport_pc io=0xb000 irq=10.
Note: Here, the io and irq should be noted from lspci -v.
Step 1 was no problem.
Step 2 failed because apparently parport_pc was not already installed, which, in retrospect makes sense because the parallel card was not installed in the system when I installed F17. No problem.
Step 3 is where I got confused. Clearly that command wasn't going to work because it was written for some older version of Linux. I searched for "parport_pc" with no luck. But I did find "parport_pc.ko". Some research indicated that this was indeed a kernel module. Some things must have changed since all the other documentation that I had read. George's suggestion above indicated that I was in the right place.
So I did Step 3 with parport_pc.ko, and got no errors.
Tried system-config-printer again and voila! LPT1 showed up! Installed the printer and everything worked perfectly, except nothing would actually print.
Went back to Step 3 and noticed the cryptic note about how the io and irq should be noted from lspci -v. So I did that, and it showed
02:00.0 Parallel controller: NetMos Technology Device 9900 (prog-if 03 [IEEE1284])
Subsystem: Device a000:2000
Flags: bus master, fast devsel, latency 0, IRQ 255
I/O ports at 9c00 [size=8]
I/O ports at 9800 [size=8]
Memory at fdaff000 (32-bit, non-prefetchable) [size=4K]
Memory at fdafe000 (32-bit, non-prefetchable) [size=4K]
Capabilities:  MSI: Enable- Count=1/1 Maskable- 64bit+
Capabilities:  Power Management version 3
Capabilities:  Express Legacy Endpoint, MSI 00
Capabilities:  Virtual Channel
Capabilities:  Advanced Error Reporting
So I repeated Step 2 and then re-did Step 3 with matching parameters like this:
insmod parport_pc.ko io=0x9c00,0x9800 irq=255
ran system-config-printer again and BIG JOY ... the actual MODEL NUMBER of my printer shows up. Completed the install process and everything works perfectly.
Moral of the story #1: RTFM
Moral of the story #2: Follow the actual instructions in TFM
Moral of the story #3: In the old days, the parallel port was at 0x0378 or something like that, and the IRQ was "7". So I expected to see those numbers somewhere in the instructions. Didn't. This was perplexing and slowed me down a bit. These days, PC hardware is completely different from what it used to be, so forget everything you remember from 30 or 20 or even 10 years ago.
Oops, gotta make that persistent:
# cd /etc/sysconfig/modules/
# cp bluezwhatever.modules MyParallelPort.modules (copied an existing script to modify it.)
edited it to add the command to load the driver:
exec modprobe parport_pc.ko io=0x9c00,0x9800 irq=255
# cp the parport_pc.ko file into this directory so the script can find it when it runs. (not sure if this is necessary)
# chmod +x MyParallelPort.modules (make it executable)
Now I'll reboot and see if it sticks...[EDIT#2] Yes!