PCIe - No parport registered at "0x " . This is not Always an error.Continuing.

tommylight wrote:

ContinenteCNC wrote:

I wonder if there is a way to force these Sunix cards to load parport_pc driver and module from the I/O ports address?

So it will showup in dmesg as a proper enumerated parallel port.

Why?
I had two of those, both showed everything on 2 different PC's, but 1 did not show driver and kernel module on a 3'rd PC. Same card did show on 1 PC and did not show on another PC.
On the PC that did not show modules another PCI card did not show modules loaded, after showing them and working for years.
All this points to something in BIOS causing that, but i am out of luck as i can not find any more of those Sunix cards.
Here is one example of it showing modules loaded
forum.linuxcnc.org/10-advanced-configura...uing?start=20#324494

I thought it might be something trivial to do, but if it is not, nevermind. It is marginally more convenient to find base, extended addresses and available modes (they showup in dmesg and /proc/sys/dev/parport/parport*)

And the bash script I wrote to automate reports assumes it is an enumerated port. If its not, it won't work. 

I tried using modprobe, setpci and some others, but linux is high in my list of "things I like doing, but I'm also bad at doing".

unknown wrote:

First thing you need to do is get the pci_id.

modinfo parport_pc

That will show you a list of PCI IDs and module parameters.

Then you can use modprobe to load partport_pc using the parameter that's required to set the address of the card.

Now whether the kernel module loads automatically for that card will depend on whether the PCI ID is a match with the driver.
If you can give me your kernel version and PCI ID of the card I can check the kernel sources and see if I can find a match. If not for the kernel you're running but one that might.
In all honesty for the headaches that a parallel port can cause a mesa 7i92 plugged into your existing breakout boards is a better solution. Latency isn't a problem, migration to a another PC is easier.
But I get that parallel port cards can be cheaper.

I love mesa cards, but unfortunately I can only use them in high end projects. Things get expensive really fast bellow equator line. 

I believe I have attached everthing you've asked. Let me know if you need some more info. Thanks!

That would be great!

I don't know if it helps, but if so I can install 2 Sunix cards (one PCI and one PCIe) and share with you a anydesk login.

Just as I thought it's a kernel version thing.
PCI ID 1fd4-1999 is only supported from 5.4 up
The driver is acually parport_serial.
Good info here, linux-hardware.org/?id=pci:1fd4-1999-1fd4-0100

That's why the PCI ID the most important bit of info.

You an Aussie as well ?

hmm, interesting finding.

Why does it use parport_serial if it is only a single parallel port with no serial ports? Or it has nothing to do?

What do you suggest as next step? Update linuxcnc to 2.9 or just the kernel?

(By the way, I am not an Aussie, I am Brazilian... Just 180 degrees apart xD)

OK.

The Linux Kernel loads drivers based on the PCI ID, there's nothing special about it. If it sees a particular PCI ID it loads the driver that matches.
So the reason lInux will load the parport_serial is because that's what the card is reporting.

For Tommy, I replied with what might be the issue directly under your post. But without the PCI ID, end manufactures can change this usually via an eeprom or maybe some other method, there's not enough info to go on.

Just gone 3pm here in Sydney.

No something interesting.

I worked on a little project using an FPGA dev board to run MESA's hostmot2 firmware. First attempt was based on the 7c81 using either SPI (raspberry pi) or EPP (best on motherboard based parallel ports). The issue with the board I used is that the EEPROM need to be changed and the headers were already soldered on.
That same hardware can also be used with the LinuxcncRIO project.

Another project I had a go at was modding the 7i90 Smart serial firmware to support 4 encoders to run on a dev board.

For my latest I've grabbed a different dev board (eeprom is correct size & bought with the headers unslodered, but this time I'll be trying a Ethernet interface, chip is same as use on the Mesa products, so no having to rewrite a driver, which requires a couple of steps, first being working out the instructions of the softcore, working how the driver talks to the chip and then how it integrates with the rest.

Some pics, 2x17 ports from breakout boards (mesa 25 pin daughter boards can be used as well) and 4 extra pins for 2 smart serial ports or extra I\O.

First off is the FPGA from aliexpress:
 

The Ethernet board, this is experiment only, the FPGA board sits on top, disregard the type of 2x25 headers they can be changed to suit. Should have the boards in a couple of weeks.
 

One of the daughter boards from the orignal project.