On Sun, 18 Oct 2020 at 04:09, ToddAndMargo via users <users@xxxxxxxxxxxxxxxxxxxxxxx> 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
Since the card worked for the vendor, it is worth trying to
figure out why yours doesn't. There have been devices that
needed to be enabled by booting DOS or Windows, then booting
linux without cycling the power.
Does your BIOS have parallel port configuration?
Some vendors (Dell, HP) have EUFI diagnostic ssoftware that
may check parallel ports.
George N. White III
_______________________________________________ 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
