This might also work:
echo 0000:01:00.2 > /sys/bus/pci/drivers/parport_pc/bind
I don't know that I (or any of us) know the exact process for adding a
new_id as it is not done often. I found the original design commit
and its process was echo to new_id and then echo 1 > probe_it (does
not exist) so there may be some way to rescan that is not obvious.
Maybe the echo "1407 a000" > new_id first and then the echo to the
bind. Or only the bind may be needed. There seems to be limited
documentation on all of this.
lspci -vvv -s 01:00.0
will show if there is a kernel driver in use and/or a kernel module
for the device.
On Sun, Oct 18, 2020 at 2:09 AM ToddAndMargo via users
<users(a)lists.fedoraproject.org> wrote:
>
> On 2020-10-17 23:23, Samuel Sieb wrote:
> > On 10/17/20 5:55 PM, ToddAndMargo via users wrote:
> >> On 2020-10-17 16:22, Roger Heflin wrote:
> >>> 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.
> >>
> >> It went over my head.
> >
> > echo "1407 A000" > /sys/bus/pci/drivers/parport_pc/new_id
> >
> > Run "journalctl -fa" in another terminal while you do that to see if
it
> > finds anything.
>
> Only thing that showed up was some DHCP stuff
>
> RATS!!
> _______________________________________________
> users mailing list -- users(a)lists.fedoraproject.org
> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> 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@lists.fedoraproject.org