1407:A000 is not listed in the driver. That is what the driver uses to load and determine it can handle the device. If it is not in that list the driver believes it is not able to operate it. Vendor will change the pciid if they change the device in some way (or they can change it if the want to at random). you can find a "new_id" in /sys under a parport_pc directory and echo the id you have for this board assuming the driver can drive it (it probably can). I am not sure of the format of the ID to be echo'ed but google should be able answer. A modprobe + the echo will have to be done on each reboot. On Sat, Oct 17, 2020 at 4:55 PM ToddAndMargo via users <users@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > > On 2020-10-17 14:47, George N. White III wrote: > > You might also try booting a Fedora Live USB to duplicate the vendor's > > setup. > > > That is a great idea. I have been waiting on it till > I see what folks had to say here first > > If it works, what data should I collect? > _______________________________________________ > users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
