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

Since 2008 I have been using linuxcnc, I remember running into a problem in the G85 code (it was malfunctioning). I am an expert in cnc technology and I am very used to the G-code in all the controllers that exist. I remember entering the forum and raising the problem and it was immediately solved. This experience was never repeated. I'm not complaining, I'm posing a problem! It seems that for some members (luckily not all) the linuxcnc Forum has become a place where users must have knowledge of github, programming, compilation, editing, etc. every time the solution to a problem is blocked. In order for linuxcnc to continue improving, they must accept the Forum as a place where they can find the problems to be solved, because this is where the users who are using the application are located. I'm really tired of members who impose their hierarchy of knowledge on those who don't have it.
For my part, nothing more to talk about in this thread. Thank you!!!

Offensive ?
Pointing out someone didn't want to lift a finger to sort the issue out even after they were given the solution ?
What really got my goat was the OP was the one with the issue, the OP had all the information available. If I was to raise an issue on GitHub, I would need to get my tower out storage, install a PCIe card, create a config and attempt to replicate the issue. Now how many cards would I need to try ?
So I'd put in a hour or two of my time for something the OP could of done in the time he made the post to say he had nothing more to say or make the report. And if it didn't get actioned straight away and new packages put up with their time frame the OP would not be satisfied.


Tho to tell the truth I wasn't surprised at considering the attitude.

As I stated before, a driver will load if there is a matching PCI ID for the hardware. I even gave the instruction that will show how to figure this out. Now if for some reason or another the people involved with producing or wholesaling the board decide for whatever reason to change the PCI ID and the driver doesn't know about it the driver won't load, it's not rocket science. Anyone who has anything to do with computer hardware knows that companies will change chipsets with models and give them new revision numbers, this was a thing to look for in the early days of wifi support in Linux, buy 2 models of the same card and one driver would work another wouldn't due to a change of chipset and PCI ID.

I'd check the kernel Configs to see what if any parallel ports are being left out.
Who ever built the kernel may have decided to include support for parallel ports, as we're probably the only old fellas that use them.
You should be able to grep the kernel config file that is in the boot directory.

tommylight wrote:

I think i should do a summary of the Sunix PCI-E card as the info got scattered in pieces, so:
I had one, it works perfectly but:
In a Lenovo PC it show the warning when LinuxCNC starts, but it works fine
In another PC with Asus Prime Z270 board, it shows no warning and no ................................
IT JUST dawned on me:
It will show the warning on older kernels, it will not show on new-er kernels!!!
Lenovo has Mint 19.3, the Asus has Mint 21.3, the friend with the same model cards has LMDE 6
Ok just checked the original post and it is Debian 12 so most probably 6.1.nn kernel, should be the same as in LMDE 6, so there goes my joy, oh hell, back to more testing!

It happend to me as well. LinuxCNC 2.8.4 / Debian Buster (live install) / Dell Optiplex 760 / Card chipset: Sunix SUN2212 (PCIe)

The message shows up when I try to run the parallel port tester. The address appear in lspci -v, the port works just fine, all inputs and outputs in all modes, but it won't show as a parallel port in ioports nor in dmesg.

However, for the Moschic MCS9805CV (PCI) it behaves as intended. Port not only works, but it shows as a parallel port in ioports and dmesg.