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

Please post output of lspci and lspci -v

Perhaps lspci -vv too

I attach 2 images of different boards Pcie.La board that has Kernel Driver parport_serial(Linuxcnc boots clean without the alarm in question). The board that has the Kernel Driver Serial (Triggers the Alarm in question). Both plates work perfectly.
I insist on the concept of a parallelized serial port. The PCEI architecture is serial and the expansion boards are responsible for parallelizing so that we can have an LPT port at the end. LinuxCNC should contemplate this situation to boot clean without the alarm. Because everything works perfectly.

By your definition of the PCIe being serial, no arguments there, it would be better described as a serialised parallel port. Generally any PCIe card would be described as a serialised device.
A more correct definition is a parallel/serial chip with a PCIe interface. Mesa sells PCIe motion control cards, would you call them serialised motion control cards ? What about GPUs, multilaned serialised devices ? Or look at the RPi 5 with the new RP interface chip, the GPIOs are on this chip which is connected via the PCIe bus, are they part of your serialised definition ?
Generally most people would look at the end point, not the bus of the computer. It's just easier to increase the speed of a serial bus compared to a parallel bus on a PCB. Trace length really comes into play, reflection, termination and many other things are more difficult routing wise with high speed parallel buses.

With regards to the chips used I think you would get a better understanding if you had a look at the data sheets. You'd be surprised the actual functions that these cards can perform. Some go further than just serial or parallel.

As PCW mentioned a change in the definition of the message would sort this out. If you feel strongly enough this should be changed, mention this on the Linuxcnc GitHub, as this is where changes to the code get done.

the point is that Linuxcnc does not find a parallel port, it finds a port that it can use but the kernel driver defines it as serial, it does not matter what is the capacity of the micro that uses the PCIE board, nor does it interest all the capabilities that you mention. Linuxcnc does not know how to solve the situation and gives us an alarm with a dual message, everything works perfectly, we are the ones who have to follow. I'm asking if you can somehow eliminate this situation of alarm or Dual message, I'm not trying to discuss technology, Nothing in the cpus works in Parallel, everything is serial, if you think differently perfect, I have no problem with that, but please don't deviate the reason why this thread was created in the forum. Thanks a lot.

What if you try 0xD010 ?

Reply redacted.

The IRQ32 plate is the one that triggers the ALRMA

PCW gave a very valid solution, so that has been covered.
The driver in use covers both functions of the board, and if you look at the dependencies of the driver you'll see that the parallel part uses parallel port modules.
But that is neither here nor there, the thing is a solution has given and if you really really want a change you'll have to mention on GitHub , as that's where the changes happen. You can go on and on posting messages on the forum but it'll do SFA.
And in reality it is only a minor thing that doesn't affect the functionality. If you get no response from the Devs there's nothing to stop you from cloning the repo, editting the source file and rebuilding from source, the build procedure is very well documented in the docs. I linked to the file where the message comes from, PCW gave a solution, all the hardwork has been done. Now the ball is in your court, if you choose not to do anything,nothing will change, if you choose to get involved and not just complain something may happen.
Or you could attempt to completely rewrite the detection routine.
This is how open source projects move forward. The forums are just really for user support, code stuff usually gets done via the Devs mailing list or via GitHub. Links to these resources can be found on the Linuxcnc home page.