CH382L, M.2 to PCIe adapter on SBC not recognised by Linuxcnc

If you have a pc you can insert the card into you could boot linuxcnc live and see if the card is recognised.

Thank you for your suggestion. I was going to do that, but then the PC started having an issue as it wasn't booting. After numerous tries it somehow opened and I booted with live linuxcnc. I executed test commands for parallel port and thankfully I saw the card was registered as parport0, unsurprisingly with the same adress as in Windows. I was going to run parallel port tester program and check pin voltages but then PC started malfunctioning again and now it is not opening again.

I will have to investigate further about the issue with the PC indeed or just move to a newer one as that one was old and a bit problematic anyway, but with a working PC system should run fine from now on I suppose. Please correct me if I am wrong but I don't think a driver installation is needed in this case as it is recognised as parport.

So the issue with my original problematic setup was probably that M.2 to PCIe adapter isn't supported in my use case. It was an adventurous try but I'd like to move to linuxcnc anyway so I will stick to a working way. Thank you all for your help.

I have found a way to get my CH382L cards to work

I discovered this thread:
www.linux.org/threads/solved-unable-to-f...nc-as-parport.24355/

The solution for me was (paraphrasing from linked thread)

sudo <editor of choice> /etc/modprobe.d/alsa-base.conf

add these lines to the file with your serial address where it says io=0xb100 In my case and the responder to the thread it was the second address:

# LPC parport to PCI-E card
alias parport_low level parport_pc
options parport_pc io=0xb100 irq=18,auto

Then reboot

Now the parport is recognized by parport_pc
You will not see any difference in lspci -v output

Damn, that is .... strange, but it works !
Alsa is used for sound/audio subsystem on Linux, so nice workaround, for sure.

You can put basically any modprobe options in there for anything and it load the module with the parameters.
The file could be called "dumb_effing_card.conf" with the entries for the adapter and it'd work. It just makes life easier having the parameters in a file with descriptive name. If you have a few different modules that need custom params it just makes it easier 6 months down the road.