On 11/1/20 11:59 PM, ToddAndMargo via users wrote:
On 2020-11-01 14:13, Samuel Sieb wrote:
> On 10/31/20 11:53 PM, ToddAndMargo via users wrote:
>> # modprobe -r lp
>> # modprobe -r parport_pc
>> # modprobe parport_pc
>> # modprobe lp
>> # echo 9710 9900 > /sys/bus/pci/drivers/parport_pc/new_id
>> But still no lp0 showing in CUPS or Printer Admin (notice
>> I used the Linux term for it!)
> After running the new_id command, do "lspci -k" again and see if it
> picked it up.
All the lcpci command pick it up. They always do. There
is never an instance where they do not.
You're misunderstanding what I meant by "pick it up". I'm looking for a
"Kernel driver in use:" or "Kernel modules:" line which doesn't
be showing up. "lspci" will always show the device because it exists
regardless of whether or not there's a driver for it.
# lspci -k -s 01:00.0
01:00.0 Parallel controller: MosChip Semiconductor Technology Ltd.
MCS9900 Multi-I/O Controller
Subsystem: Device a000:2000
> If not, then try "echo 1 > /sys/bus/pci/rescan" and check
Ran it anyway. No joy.
Strange. I wonder why that isn't working. Given the similar supported
ids, I expected that to work. Sorry, I have no more suggestions.
Btw, your original attempt at using the legacy ports is certainly not
going to work. I saw this in one of your earlier emails:
Region 0: I/O ports at e010 [disabled] [size=8]
Region 1: I/O ports at e000 [disabled] [size=8]
Region 2: Memory at ac001000 (32-bit, non-prefetchable) [disabled]
Region 5: Memory at ac000000 (32-bit, non-prefetchable) [disabled]