10:38 p.m.
Hi All,
Here we go again.
I now have a Siig JJ-E01211-S1 Single Parallel Port PCIe Card
https://stage.siig.com/products/it-products/serial-parallel/parallel/pcie...
System Requirements:
...
Linux kernel 2.6 and later version
Works with Linux but not supported
And Printer Admin and CUPS do not find it.
Troubleshooting:
1) connected a USB to Parallel converter card. Printer work fine
2) boot off of Fedora-Xfce-Live-x86_64-33-1.2.iso. Printer
admin still can't find the card.
3) With
# modprobe -r lp
# modprobe -r parport_pc
# modprobe parport_pc io=0x378 irq=11
# modprobe lp
the card does show up and you can print to it, but
the jobs instantly disappear and nothing shows on
the printer's status screen
What next?
-T
Here is some data on the card
# udevadm info --attribute-walk /dev/lp0
Unknown device "/dev/lp0": No such device
# lspci -nn | grep -i moschip
01:00.0 Parallel controller [0701]: MosChip Semiconductor Technology
Ltd. MCS9900 Multi-I/O Controller [9710:9900]
# lspci -vv -s 01:00.0
01:00.0 Parallel controller: MosChip Semiconductor Technology Ltd.
MCS9900 Multi-I/O Controller (prog-if 03 [IEEE1284])
Subsystem: Device a000:2000
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR- INTx-
Interrupt: pin A routed to IRQ 11
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]
[size=4K]
Region 5: Memory at ac000000 (32-bit, non-prefetchable) [disabled]
[size=4K]
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Address: 0000000000000000 Data: 0000
Capabilities: [78] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA
PME(D0-,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [80] Express (v1) Legacy Endpoint, MSI 00
DevCap: MaxPayload 512 bytes, PhantFunc 0, Latency L0s <1us, L1 <2us
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr+ NonFatalErr- FatalErr- UnsupReq+ AuxPwr- TransPend-
LnkCap: Port #1, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit Latency
L0s <64ns, L1 <1us
ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk-
ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s (ok), Width x1 (ok)
TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt-
Capabilities: [100 v1] Virtual Channel
Caps: LPEVC=0 RefClk=100ns PATEntryBits=1
Arb: Fixed- WRR32- WRR64- WRR128-
Ctrl: ArbSelect=Fixed
Status: InProgress-
VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
Status: NegoPending- InProgress-
VC1: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl: Enable- ID=0 ArbSelect=Fixed TC/VC=00
Status: NegoPending- InProgress-
Capabilities: [800 v1] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF-
MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF-
MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+
MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
AERCap: First Error Pointer: 00, ECRCGenCap- ECRCGenEn- ECRCChkCap-
ECRCChkEn-
MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
HeaderLog: 00000000 00000000 00000000 00000000
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Computers are like air conditioners.
They malfunction when you open windows
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2:14 a.m.
On 10/30/20 8:38 PM, ToddAndMargo via users wrote:
I now have a Siig JJ-E01211-S1 Single Parallel Port PCIe Card
# modprobe -r lp
# modprobe -r parport_pc
# modprobe parport_pc io=0x378 irq=11
# modprobe lp
the card does show up and you can print to it, but
the jobs instantly disappear and nothing shows on
the printer's status screen
Try "lspci -k".
5:39 a.m.
On 2020-10-31 00:14, Samuel Sieb wrote:
On 10/30/20 8:38 PM, ToddAndMargo via users wrote:
> I now have a Siig JJ-E01211-S1 Single Parallel Port PCIe Card
>
> # modprobe -r lp
> # modprobe -r parport_pc
> # modprobe parport_pc io=0x378 irq=11
> # modprobe lp
>
> the card does show up and you can print to it, but
> the jobs instantly disappear and nothing shows on
> the printer's status screen
Try "lspci -k".
# lspci -k -s 01:00.0
01:00.0 Parallel controller: MosChip Semiconductor Technology Ltd.
MCS9900 Multi-I/O Controller
Subsystem: Device a000:2000
4:56 p.m.
On 10/31/20 3:39 AM, ToddAndMargo via users wrote:
On 2020-10-31 00:14, Samuel Sieb wrote:
> On 10/30/20 8:38 PM, ToddAndMargo via users wrote:
>> I now have a Siig JJ-E01211-S1 Single Parallel Port PCIe Card
>>
>> # modprobe -r lp
>> # modprobe -r parport_pc
>> # modprobe parport_pc io=0x378 irq=11
>> # modprobe lp
>>
>> the card does show up and you can print to it, but
>> the jobs instantly disappear and nothing shows on
>> the printer's status screen
What do you mean that it shows up and you can print to it? How are you
configuring it?
> Try "lspci -k".
# lspci -k -s 01:00.0
01:00.0 Parallel controller: MosChip Semiconductor Technology Ltd.
MCS9900 Multi-I/O Controller
Subsystem: Device a000:2000
So it's not getting picked up, which makes sense since that device is
not recognized by the kernel module:
alias: pci:v00009710d00009865sv0000A000sd00002000bc*sc*i*
alias: pci:v00009710d00009865sv0000A000sd00001000bc*sc*i*
alias: pci:v00009710d00009901sv0000A000sd00002000bc*sc*i*
alias: pci:v00009710d00009815sv*sd*bc*sc*i*
alias: pci:v00009710d00009805sv*sd*bc*sc*i*
alias: pci:v00009710d00009755sv*sd*bc*sc*i*
alias: pci:v00009710d00009715sv*sd*bc*sc*i*
alias: pci:v00009710d00009705sv*sd*bc*sc*i*
From your original email, the card would be v00009710d00009900.
Try "echo 9710 9900 > /sys/bus/pci/drivers/parport_pc/new_id".
See what shows up in the journal.
12:53 a.m.
On 2020-10-31 14:56, Samuel Sieb wrote:
On 10/31/20 3:39 AM, ToddAndMargo via users wrote:
> On 2020-10-31 00:14, Samuel Sieb wrote:
>> On 10/30/20 8:38 PM, ToddAndMargo via users wrote:
>>> I now have a Siig JJ-E01211-S1 Single Parallel Port PCIe Card
>>>
>>> # modprobe -r lp
>>> # modprobe -r parport_pc
>>> # modprobe parport_pc io=0x378 irq=11
>>> # modprobe lp
>>>
>>> the card does show up and you can print to it, but
>>> the jobs instantly disappear and nothing shows on
>>> the printer's status screen
What do you mean that it shows up and you can print to it?
If I do the modprobe will above, lpt1 (lp0) shows up in
both printer admin and CUPS. Otherwise not.
It always shows up in lspci
How are you configuring it?
printer admin and CUPS
>> Try "lspci -k".
>
> # lspci -k -s 01:00.0
> 01:00.0 Parallel controller: MosChip Semiconductor Technology Ltd.
> MCS9900 Multi-I/O Controller
> Subsystem: Device a000:2000
So it's not getting picked up, which makes sense since that device is
not recognized by the kernel module:
alias: pci:v00009710d00009865sv0000A000sd00002000bc*sc*i*
alias: pci:v00009710d00009865sv0000A000sd00001000bc*sc*i*
alias: pci:v00009710d00009901sv0000A000sd00002000bc*sc*i*
alias: pci:v00009710d00009815sv*sd*bc*sc*i*
alias: pci:v00009710d00009805sv*sd*bc*sc*i*
alias: pci:v00009710d00009755sv*sd*bc*sc*i*
alias: pci:v00009710d00009715sv*sd*bc*sc*i*
alias: pci:v00009710d00009705sv*sd*bc*sc*i*
From your original email, the card would be v00009710d00009900.
Try "echo 9710 9900 > /sys/bus/pci/drivers/parport_pc/new_id".
See what shows up in the journal.
no parport_pc directory; I have a drivers directory
# echo 9710 9900 > /sys/bus/pci/drivers/parport_pc/new_id
bash: /sys/bus/pci/drivers/parport_pc/new_id: No such file or directory
1:36 a.m.
On 10/31/20 10:53 PM, ToddAndMargo via users wrote:
On 2020-10-31 14:56, Samuel Sieb wrote:
> What do you mean that it shows up and you can print to it?
If I do the modprobe will above, lpt1 (lp0) shows up in
both printer admin and CUPS. Otherwise not.
Why do you say "lpt1"? I have 4 lp[0-3] devices in /dev, but I have no
actual parallel port hardware.
I suspect by force loading the driver with settings like that, it will
assume there's actually a port at that address. It will be writing to
nothing.
> From your original email, the card would be v00009710d00009900.
> Try "echo 9710 9900 > /sys/bus/pci/drivers/parport_pc/new_id".
> See what shows up in the journal.
no parport_pc directory; I have a drivers directory
# echo 9710 9900 > /sys/bus/pci/drivers/parport_pc/new_id
bash: /sys/bus/pci/drivers/parport_pc/new_id: No such file or directory
Was the "parport_pc" driver loaded when you tried that? Try loading the
driver with *no* parameters and then try that command again.
1:50 a.m.
On 2020-10-31 23:36, Samuel Sieb wrote:
> If I do the modprobe will above, lpt1 (lp0) shows up in
> both printer admin and CUPS. Otherwise not.
Why do you say "lpt1"? I have 4 lp[0-3] devices in /dev, but I have no
actual parallel port hardware.
I suspect by force loading the driver with settings like that, it will
assume there's actually a port at that address. It will be writing to
nothing.
It is a CUPS and Printer Admin thing. I find it a bit
annoying myself. They should use Linux terms, not
Windows terms.
See for yourself:
https://ibb.co/Gv770CF
1:08 a.m.
On 10/31/20 11:50 PM, ToddAndMargo via users wrote:
On 2020-10-31 23:36, Samuel Sieb wrote:
>> If I do the modprobe will above, lpt1 (lp0) shows up in
>> both printer admin and CUPS. Otherwise not.
>
> Why do you say "lpt1"? I have 4 lp[0-3] devices in /dev, but I have
> no actual parallel port hardware.
> I suspect by force loading the driver with settings like that, it will
> assume there's actually a port at that address. It will be writing to
> nothing.
It is a CUPS and Printer Admin thing. I find it a bit
annoying myself. They should use Linux terms, not
Windows terms.
See for yourself:
https://ibb.co/Gv770CF
I don't think it's originally a windows term. It's actually "LPT
#1",
similar to the following "Serial Port #1". "LPT" stands for
"line
printer" for those of us old enough to remember when printers could only
do lines of text.
1:45 p.m.
On 2020-11-01 00:08, Samuel Sieb wrote:
On 10/31/20 11:50 PM, ToddAndMargo via users wrote:
> On 2020-10-31 23:36, Samuel Sieb wrote:
>>> If I do the modprobe will above, lpt1 (lp0) shows up in
>>> both printer admin and CUPS. Otherwise not.
>>
>> Why do you say "lpt1"? I have 4 lp[0-3] devices in /dev, but I have
>> no actual parallel port hardware.
>> I suspect by force loading the driver with settings like that, it
>> will assume there's actually a port at that address. It will be
>> writing to nothing.
>
> It is a CUPS and Printer Admin thing. I find it a bit
> annoying myself. They should use Linux terms, not
> Windows terms.
>
> See for yourself:
> https://ibb.co/Gv770CF
I don't think it's originally a windows term. It's actually "LPT
#1",
similar to the following "Serial Port #1". "LPT" stands for
"line
printer" for those of us old enough to remember when printers could only
do lines of text.
I wonder what it was called back in the UNIX days?
2:39 p.m.
On 11/1/20 2:45 PM, ToddAndMargo via users wrote:
On 2020-11-01 00:08, Samuel Sieb wrote:
> On 10/31/20 11:50 PM, ToddAndMargo via users wrote:
>> On 2020-10-31 23:36, Samuel Sieb wrote:
>>>> If I do the modprobe will above, lpt1 (lp0) shows up in
>>>> both printer admin and CUPS. Otherwise not.
>>>
>>> Why do you say "lpt1"? I have 4 lp[0-3] devices in /dev, but I
>>> have no actual parallel port hardware.
>>> I suspect by force loading the driver with settings like that, it
>>> will assume there's actually a port at that address. It will be
>>> writing to nothing.
>>
>> It is a CUPS and Printer Admin thing. I find it a bit
>> annoying myself. They should use Linux terms, not
>> Windows terms.
>>
>> See for yourself:
>> https://ibb.co/Gv770CF
>
> I don't think it's originally a windows term. It's actually "LPT
> #1", similar to the following "Serial Port #1". "LPT"
stands for
> "line printer" for those of us old enough to remember when printers
> could only do lines of text.
I wonder what it was called back in the UNIX days?
According to The Waite
Group's UNIX Primer Plus, Second Edition, it was
called lpr, for line printer.
--doug
_______________________________________________
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
2:42 p.m.
On 2020-11-01 12:39, Doug McGarrett wrote:
>> I don't think it's originally a windows term.
It's actually "LPT
>> #1", similar to the following "Serial Port #1". "LPT"
stands for
>> "line printer" for those of us old enough to remember when printers
>> could only do lines of text.
>
> I wonder what it was called back in the UNIX days?
According to The Waite Group's UNIX Primer Plus, Second Edition, it was
called lpr, for line printer.
--doug
That would explain things!
3:41 p.m.
On Sun, Nov 1, 2020 at 3:43 PM ToddAndMargo via users <
users(a)lists.fedoraproject.org> wrote:
On 2020-11-01 12:39, Doug McGarrett wrote:
>>> I don't think it's originally a windows term. It's actually
"LPT
>>> #1", similar to the following "Serial Port #1".
"LPT" stands for
>>> "line printer" for those of us old enough to remember when
printers
>>> could only do lines of text.
>>
>> I wonder what it was called back in the UNIX days?
> According to The Waite Group's UNIX Primer Plus, Second Edition, it was
> called lpr, for line printer.
ISTR that on my Xenix boxes, the parallel ports were lp0, lp1, etc,
and the default printer was lpr,
(regardless of whether it was a parallel printer, or serial printer)
and was symlinked to the appropriate port
1:53 a.m.
On 2020-10-31 23:36, Samuel Sieb wrote:
> # echo 9710 9900 > /sys/bus/pci/drivers/parport_pc/new_id
> bash: /sys/bus/pci/drivers/parport_pc/new_id: No such file or directory
Was the "parport_pc" driver loaded when you tried that? Try loading the
driver with *no* parameters and then try that command again.
Both.
It is not there after a fresh reboot. Makes sense, it could not find a
parallel port card.
And it did show up when I reset things:
# 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!)
1:08 a.m.
On 10/31/20 11:53 PM, ToddAndMargo via users wrote:
On 2020-10-31 23:36, Samuel Sieb wrote:
>> # echo 9710 9900 > /sys/bus/pci/drivers/parport_pc/new_id
>> bash: /sys/bus/pci/drivers/parport_pc/new_id: No such file or directory
>
> Was the "parport_pc" driver loaded when you tried that? Try loading
> the driver with *no* parameters and then try that command again.
Both.
It is not there after a fresh reboot. Makes sense, it could not find a
parallel port card.
And it did show up when I reset things:
# 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!)
Did anything show up in the journal when you ran that command?
1:46 p.m.
On 2020-11-01 00:08, Samuel Sieb wrote:
On 10/31/20 11:53 PM, ToddAndMargo via users wrote:
> On 2020-10-31 23:36, Samuel Sieb wrote:
>>> # echo 9710 9900 > /sys/bus/pci/drivers/parport_pc/new_id
>>> bash: /sys/bus/pci/drivers/parport_pc/new_id: No such file or directory
>>
>> Was the "parport_pc" driver loaded when you tried that? Try loading
>> the driver with *no* parameters and then try that command again.
>
> Both.
>
> It is not there after a fresh reboot. Makes sense, it could not find
> a parallel port card.
>
> And it did show up when I reset things:
>
> # 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!)
Did anything show up in the journal when you ran that command?
No
1:10 p.m.
On Sun, 1 Nov 2020 at 02:54, ToddAndMargo via users <
users(a)lists.fedoraproject.org> wrote:
On 2020-10-31 23:36, Samuel Sieb wrote:
>> # echo 9710 9900 > /sys/bus/pci/drivers/parport_pc/new_id
>> bash: /sys/bus/pci/drivers/parport_pc/new_id: No such file or directory
>
> Was the "parport_pc" driver loaded when you tried that? Try loading the
> driver with *no* parameters and then try that command again.
Both.
It is not there after a fresh reboot. Makes sense, it could not find a
parallel port card.
And it did show up when I reset things:
# 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!)
There was a discussion of problems with a similar card on LinuxCNC:
https://forum.linuxcnc.org/49-basic-configuration/32089-pcie-parallel-por...
The card worked on some hardware/linux combinations, not others. The chip
may support both serial and
parallel ports, so linux may be sending your print data to the serial
interface.
Also:
https://forum.linuxcnc.org/18-computer/18917-faq-pci-parallel-port-cards
has some recommendations, but CNC
uses bidirectional communication that may not be necessary with an old
printer.
Some hardware gets initialized when the system is powered up and may not be
reset by a reboot. Try a power cycle
instead of a reboot.
--
George N. White III
4:13 p.m.
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. If not, then try "echo 1 > /sys/bus/pci/rescan" and check
again.
1:59 a.m.
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.
# 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
again.
Ran it anyway. No joy.
2:22 a.m.
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
seem to
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
> again.
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]
[size=4K]
Region 5: Memory at ac000000 (32-bit, non-prefetchable) [disabled]
[size=4K]
3:59 a.m.
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.
# lspci -k -s 01:00.0
01:00.0 Parallel controller: MosChip Semiconductor Technology Ltd.
MCS9900 Multi-I/O Controller
Subsystem: Device a000:2000
There is one other possible option to try.
echo "0000:01:00.0" > /sys/bus/pci/drivers/parport_pc/bind
It probably won't work either. I haven't looked at the kernel code, but
I wouldn't be surprised if there is some special code for each device,
so adding a new device won't match any existing checks.
After further research, I found the datasheet for this device is
available. The parallel port should be function 2. I'm not entirely
clear on what that means and the Subsystem line is showing the right
value for the parallel port. Can you show the output of "lspci -nn" for
the other devices around this one? There's also a Linux driver
available at https://www.asix.com.tw/en/support/download if you want to
try it.
12:31 p.m.
On 2020-11-02 01:59, Samuel Sieb wrote:
There's also a Linux driver
available at https://www.asix.com.tw/en/support/download if you want
to
try it.
You have to recompile the linux kernel
3:14 p.m.
On 11/2/20 10:31 AM, ToddAndMargo via users wrote:
On 2020-11-02 01:59, Samuel Sieb wrote:
There's also a Linux driver
> available at https://www.asix.com.tw/en/support/download if you want
> to try it.
You have to recompile the linux kernel
No, you don't. Unpack the tar file, go into the directory and run:
make -C /lib/modules/`uname -r`/build M=$PWD
You will end up with a 99xx.ko file. Do "insmod 99xx.ko". I can't do
that because I have secure boot enabled. You will need to turn it off
if you do. (Or figure out how to sign the module and register the key.)
What about the other info I asked for in the previous email?
4:21 p.m.
On 2020-11-02 13:14, Samuel Sieb wrote:
On 11/2/20 10:31 AM, ToddAndMargo via users wrote:
> On 2020-11-02 01:59, Samuel Sieb wrote:
> There's also a Linux driver
>> available at https://www.asix.com.tw/en/support/download if you want
>> to try it.
>
> You have to recompile the linux kernel
No, you don't.
Their directions said you did. But ...
Unpack the tar file, go into the directory and run:
make -C /lib/modules/`uname -r`/build M=$PWD
You will end up with a 99xx.ko file. Do "insmod 99xx.ko". I can't do
that because I have secure boot enabled. You will need to turn it off
if you do. (Or figure out how to sign the module and register the key.)
What about the other info I asked for in the previous email?
Which one did I miss?
4:33 p.m.
On 11/2/20 2:21 PM, ToddAndMargo via users wrote:
On 2020-11-02 13:14, Samuel Sieb wrote:
> What about the other info I asked for in the previous email?
Which one did I miss?
It was easy to miss in the rest of the text.
Can you show the output of "lspci -nn" for the other devices around this
one?
5:25 p.m.
On 2020-11-02 14:33, Samuel Sieb wrote:
lspci -nn
# lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen
Core Processor Host Bridge/DRAM Registers [8086:5918] (rev 05)
00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics
P630 [8086:591d] (rev 04)
00:14.0 USB controller [0c03]: Intel Corporation 100 Series/C230 Series
Chipset Family USB 3.0 xHCI Controller [8086:a12f] (rev 31)
00:14.2 Signal processing controller [1180]: Intel Corporation 100
Series/C230 Series Chipset Family Thermal Subsystem [8086:a131] (rev 31)
00:15.0 Signal processing controller [1180]: Intel Corporation 100
Series/C230 Series Chipset Family Serial IO I2C Controller #0
[8086:a160] (rev 31)
00:15.1 Signal processing controller [1180]: Intel Corporation 100
Series/C230 Series Chipset Family Serial IO I2C Controller #1
[8086:a161] (rev 31)
00:16.0 Communication controller [0780]: Intel Corporation 100
Series/C230 Series Chipset Family MEI Controller #1 [8086:a13a] (rev 31)
00:16.3 Serial controller [0700]: Intel Corporation 100 Series/C230
Series Chipset Family KT Redirection [8086:a13d] (rev 31)
00:17.0 SATA controller [0106]: Intel Corporation
Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode]
[8086:a102] (rev 31)
00:1c.0 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series
Chipset Family PCI Express Root Port #1 [8086:a110] (rev f1)
00:1c.5 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series
Chipset Family PCI Express Root Port #6 [8086:a115] (rev f1)
00:1c.6 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series
Chipset Family PCI Express Root Port #7 [8086:a116] (rev f1)
00:1c.7 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series
Chipset Family PCI Express Root Port #8 [8086:a117] (rev f1)
00:1d.0 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series
Chipset Family PCI Express Root Port #9 [8086:a118] (rev f1)
00:1f.0 ISA bridge [0601]: Intel Corporation C236 Chipset LPC/eSPI
Controller [8086:a149] (rev 31)
00:1f.2 Memory controller [0580]: Intel Corporation 100 Series/C230
Series Chipset Family Power Management Controller [8086:a121] (rev 31)
00:1f.3 Audio device [0403]: Intel Corporation 100 Series/C230 Series
Chipset Family HD Audio Controller [8086:a170] (rev 31)
00:1f.4 SMBus [0c05]: Intel Corporation 100 Series/C230 Series Chipset
Family SMBus [8086:a123] (rev 31)
00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet
Connection (2) I219-LM [8086:15b7] (rev 31)
01:00.0 Parallel controller [0701]: MosChip Semiconductor Technology
Ltd. MCS9900 Multi-I/O Controller [9710:9900]
6c:00.0 Ethernet controller [0200]: Intel Corporation I210 Gigabit
Network Connection [8086:1533] (rev 03)
6d:00.0 PCI bridge [0604]: Tundra Semiconductor Corp. Device [10e3:8113]
(rev 01)
6f:00.0 USB controller [0c03]: ASMedia Technology Inc. ASM1142 USB 3.1
Host Controller [1b21:1242]
70:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co
Ltd NVMe SSD Controller SM961/PM961 [144d:a804]
8:51 p.m.
On Mon, 2 Nov 2020 18:16:08 -0800
ToddAndMargo via users wrote:
> Ok, so nothing there. Any luck with the driver?
I will have to wait till tomorrow.
So if you can build a working kernel, obviously the thing to
do is make a virtual machine running that kernel and use
pci passthrough to give it control of the card, then remote
print via the virtual machine...
That way updates won't break the printer :-).
1:53 p.m.
On 2020-11-02 18:51, Tom Horsley wrote:
On Mon, 2 Nov 2020 18:16:08 -0800
ToddAndMargo via users wrote:
>> Ok, so nothing there. Any luck with the driver?
>
> I will have to wait till tomorrow.
So if you can build a working kernel, obviously the thing to
do is make a virtual machine running that kernel and use
pci passthrough to give it control of the card, then remote
print via the virtual machine...
That way updates won't break the printer :-).
I am thinking of using the insmod first.
10:01 p.m.
On 2020-11-02 17:04, Samuel Sieb wrote:
On 11/2/20 3:25 PM, ToddAndMargo via users wrote:
> On 2020-11-02 14:33, Samuel Sieb wrote:
>> lspci -nn
>
> # lspci -nn
Ok, so nothing there. Any luck with the driver?
None.
From the readme
Building the Driver and application:
--------------------
Run the following command in the driver source folder:
$ make
[todd@rn6 MosChip.Parallel.Controller]$ cd
MCS99xx_LINUX_Driver_v3.1.0_Source
[todd@rn6 MCS99xx_LINUX_Driver_v3.1.0_Source]$ make
rm -f *.mod.c *.o *.ko .*.cmd *.symvers
make -C /lib/modules/5.8.18-300.fc33.x86_64/build/
SUBDIRS=/home/CDs/Linux/MosChip.Parallel.Controller/MCS99xx_LINUX_Driver_v3.1.0_Source
modules
make[1]: *** /lib/modules/5.8.18-300.fc33.x86_64/build/: No such file or
directory. Stop.
make: *** [Makefile:32: default] Error 2
[todd@rn6 MCS99xx_LINUX_Driver_v3.1.0_Source]$ ls
99xx.c 99xx.h advanced_BR.c gpio_99xx.c ioctl.h Makefile mcs99xx
readme select_BR.c
$ make --debug
GNU Make 4.3
Built for x86_64-redhat-linux-gnu
Copyright (C) 1988-2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Reading makefiles...
Updating makefiles....
Updating goal targets....
File 'default' does not exist.
Must remake target 'default'.
rm -f *.mod.c *.o *.ko .*.cmd *.symvers
make -C /lib/modules/5.8.18-300.fc33.x86_64/build/
SUBDIRS=/home/CDs/Linux/MosChip.Parallel.Controller/MCS99xx_LINUX_Driver_v3.1.0_Source
modules
GNU Make 4.3
Built for x86_64-redhat-linux-gnu
Copyright (C) 1988-2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
make[1]: *** /lib/modules/5.8.18-300.fc33.x86_64/build/: No such file or
directory. Stop.
make: *** [Makefile:32: default] Error 2
12:22 a.m.
On 11/8/20 8:01 PM, ToddAndMargo via users wrote:
On 2020-11-02 17:04, Samuel Sieb wrote:
> On 11/2/20 3:25 PM, ToddAndMargo via users wrote:
>> On 2020-11-02 14:33, Samuel Sieb wrote:
>>> lspci -nn
>>
>> # lspci -nn
>
> Ok, so nothing there. Any luck with the driver?
None.
From the readme
Don't follow the readme. I gave you the command to run:
make -C /lib/modules/`uname -r`/build M=$PWD
1:04 a.m.
On 2020-11-08 22:22, Samuel Sieb wrote:
On 11/8/20 8:01 PM, ToddAndMargo via users wrote:
> On 2020-11-02 17:04, Samuel Sieb wrote:
>> On 11/2/20 3:25 PM, ToddAndMargo via users wrote:
>>> On 2020-11-02 14:33, Samuel Sieb wrote:
>>>> lspci -nn
>>>
>>> # lspci -nn
>>
>> Ok, so nothing there. Any luck with the driver?
>
> None.
>
> From the readme
Don't follow the readme. I gave you the command to run:
make -C /lib/modules/`uname -r`/build M=$PWD
$ cd MCS99xx_LINUX_Driver_v3.1.0_Source
$ make -C /lib/modules/`uname -r`/build M=$PWD
make: *** /lib/modules/5.8.18-300.fc33.x86_64/build: No such file or
directory. Stop.
Dang!
$ ls -al /lib/modules/5.8.18-300.fc33.x86_64/build
lrwxrwxrwx. 1 root root 39 Nov 2 11:22
/lib/modules/5.8.18-300.fc33.x86_64/build ->
/usr/src/kernels/5.8.18-300.fc33.x86_64
1:07 a.m.
On 11/8/20 11:04 PM, ToddAndMargo via users wrote:
On 2020-11-08 22:22, Samuel Sieb wrote:
> On 11/8/20 8:01 PM, ToddAndMargo via users wrote:
>> On 2020-11-02 17:04, Samuel Sieb wrote:
>>> On 11/2/20 3:25 PM, ToddAndMargo via users wrote:
>>>> On 2020-11-02 14:33, Samuel Sieb wrote:
>>>>> lspci -nn
>>>>
>>>> # lspci -nn
>>>
>>> Ok, so nothing there. Any luck with the driver?
>>
>> None.
>>
>> From the readme
>
> Don't follow the readme. I gave you the command to run:
> make -C /lib/modules/`uname -r`/build M=$PWD
$ cd MCS99xx_LINUX_Driver_v3.1.0_Source
$ make -C /lib/modules/`uname -r`/build M=$PWD
make: *** /lib/modules/5.8.18-300.fc33.x86_64/build: No such file or
directory. Stop.
You need to install "kernel-devel".
1:10 a.m.
On 11/8/20 11:07 PM, Samuel Sieb wrote:
On 11/8/20 11:04 PM, ToddAndMargo via users wrote:
> On 2020-11-08 22:22, Samuel Sieb wrote:
>> On 11/8/20 8:01 PM, ToddAndMargo via users wrote:
>>> On 2020-11-02 17:04, Samuel Sieb wrote:
>>>> On 11/2/20 3:25 PM, ToddAndMargo via users wrote:
>>>>> On 2020-11-02 14:33, Samuel Sieb wrote:
>>>>>> lspci -nn
>>>>>
>>>>> # lspci -nn
>>>>
>>>> Ok, so nothing there. Any luck with the driver?
>>>
>>> None.
>>>
>>> From the readme
>>
>> Don't follow the readme. I gave you the command to run:
>> make -C /lib/modules/`uname -r`/build M=$PWD
>
> $ cd MCS99xx_LINUX_Driver_v3.1.0_Source
> $ make -C /lib/modules/`uname -r`/build M=$PWD
> make: *** /lib/modules/5.8.18-300.fc33.x86_64/build: No such file or
> directory. Stop.
You need to install "kernel-devel".
If your running kernel isn't the latest version, then either install the
specific -devel package for your kernel or update your kernel and reboot.
2:16 a.m.
On 2020-11-08 23:07, Samuel Sieb wrote:
On 11/8/20 11:04 PM, ToddAndMargo via users wrote:
> On 2020-11-08 22:22, Samuel Sieb wrote:
>> On 11/8/20 8:01 PM, ToddAndMargo via users wrote:
>>> On 2020-11-02 17:04, Samuel Sieb wrote:
>>>> On 11/2/20 3:25 PM, ToddAndMargo via users wrote:
>>>>> On 2020-11-02 14:33, Samuel Sieb wrote:
>>>>>> lspci -nn
>>>>>
>>>>> # lspci -nn
>>>>
>>>> Ok, so nothing there. Any luck with the driver?
>>>
>>> None.
>>>
>>> From the readme
>>
>> Don't follow the readme. I gave you the command to run:
>> make -C /lib/modules/`uname -r`/build M=$PWD
>
> $ cd MCS99xx_LINUX_Driver_v3.1.0_Source
> $ make -C /lib/modules/`uname -r`/build M=$PWD
> make: *** /lib/modules/5.8.18-300.fc33.x86_64/build: No such file or
> directory. Stop.
You need to install "kernel-devel".
That worked. Thank you!
You would not happen to know the insmod command too?
2:19 a.m.
On 11/9/20 12:16 AM, ToddAndMargo via users wrote:
On 2020-11-08 23:07, Samuel Sieb wrote:
> On 11/8/20 11:04 PM, ToddAndMargo via users wrote:
>> On 2020-11-08 22:22, Samuel Sieb wrote:
>>> Don't follow the readme. I gave you the command to run:
>>> make -C /lib/modules/`uname -r`/build M=$PWD
>>
>> $ cd MCS99xx_LINUX_Driver_v3.1.0_Source
>> $ make -C /lib/modules/`uname -r`/build M=$PWD
>> make: *** /lib/modules/5.8.18-300.fc33.x86_64/build: No such file or
>> directory. Stop.
>
> You need to install "kernel-devel".
That worked. Thank you!
You would not happen to know the insmod command too?
That was also in the same earlier email. Or just look for the .ko file.
insmod 99xx.ko
2:54 a.m.
On 2020-11-09 00:19, Samuel Sieb wrote:
On 11/9/20 12:16 AM, ToddAndMargo via users wrote:
> On 2020-11-08 23:07, Samuel Sieb wrote:
>> On 11/8/20 11:04 PM, ToddAndMargo via users wrote:
>>> On 2020-11-08 22:22, Samuel Sieb wrote:
>>>> Don't follow the readme. I gave you the command to run:
>>>> make -C /lib/modules/`uname -r`/build M=$PWD
>>>
>>> $ cd MCS99xx_LINUX_Driver_v3.1.0_Source
>>> $ make -C /lib/modules/`uname -r`/build M=$PWD
>>> make: *** /lib/modules/5.8.18-300.fc33.x86_64/build: No such file or
>>> directory. Stop.
>>
>> You need to install "kernel-devel".
>
> That worked. Thank you!
>
> You would not happen to know the insmod command too?
That was also in the same earlier email. Or just look for the .ko file.
insmod 99xx.ko
installed without an error message.
lp0 is still not seen.
Was I suppose to do anything else?
2:58 a.m.
On 11/9/20 12:54 AM, ToddAndMargo via users wrote:
On 2020-11-09 00:19, Samuel Sieb wrote:
> On 11/9/20 12:16 AM, ToddAndMargo via users wrote:
>> On 2020-11-08 23:07, Samuel Sieb wrote:
>>> On 11/8/20 11:04 PM, ToddAndMargo via users wrote:
>>>> On 2020-11-08 22:22, Samuel Sieb wrote:
>>>>> Don't follow the readme. I gave you the command to run:
>>>>> make -C /lib/modules/`uname -r`/build M=$PWD
>>>>
>>>> $ cd MCS99xx_LINUX_Driver_v3.1.0_Source
>>>> $ make -C /lib/modules/`uname -r`/build M=$PWD
>>>> make: *** /lib/modules/5.8.18-300.fc33.x86_64/build: No such file
>>>> or directory. Stop.
>>>
>>> You need to install "kernel-devel".
>>
>> That worked. Thank you!
>>
>> You would not happen to know the insmod command too?
>
> That was also in the same earlier email. Or just look for the .ko file.
> insmod 99xx.ko
installed without an error message.
lp0 is still not seen.
Was I suppose to do anything else?
Any log messages?
What about "lspci -k"?
4:22 a.m.
On 2020-11-09 00:58, Samuel Sieb wrote:
On 11/9/20 12:54 AM, ToddAndMargo via users wrote:
> On 2020-11-09 00:19, Samuel Sieb wrote:
>> On 11/9/20 12:16 AM, ToddAndMargo via users wrote:
>>> On 2020-11-08 23:07, Samuel Sieb wrote:
>>>> On 11/8/20 11:04 PM, ToddAndMargo via users wrote:
>>>>> On 2020-11-08 22:22, Samuel Sieb wrote:
>>>>>> Don't follow the readme. I gave you the command to run:
>>>>>> make -C /lib/modules/`uname -r`/build M=$PWD
>>>>>
>>>>> $ cd MCS99xx_LINUX_Driver_v3.1.0_Source
>>>>> $ make -C /lib/modules/`uname -r`/build M=$PWD
>>>>> make: *** /lib/modules/5.8.18-300.fc33.x86_64/build: No such file
>>>>> or directory. Stop.
>>>>
>>>> You need to install "kernel-devel".
>>>
>>> That worked. Thank you!
>>>
>>> You would not happen to know the insmod command too?
>>
>> That was also in the same earlier email. Or just look for the .ko file.
>> insmod 99xx.ko
>
> installed without an error message.
>
> lp0 is still not seen.
>
> Was I suppose to do anything else?
Any log messages?
What about "lspci -k"?
# lspci -k -s 01:00.0
01:00.0 Parallel controller: MosChip Semiconductor Technology Ltd.
MCS9900 Multi-I/O Controller
Subsystem: Device a000:2000
I take it the insmod will be lost after a reboot.
I also did a
# modprobe -r lp
# modprobe -r parport_pc
# modprobe parport_pc
# modprobe lp
No joy there either
4:23 p.m.
On Mon, 2 Nov 2020 at 17:15, Samuel Sieb <samuel(a)sieb.net> wrote:
On 11/2/20 10:31 AM, ToddAndMargo via users wrote:
> On 2020-11-02 01:59, Samuel Sieb wrote:
> There's also a Linux driver
>> available at https://www.asix.com.tw/en/support/download if you want
>> to try it.
>
> You have to recompile the linux kernel
No, you don't. Unpack the tar file, go into the directory and run:
make -C /lib/modules/`uname -r`/build M=$PWD
You will end up with a 99xx.ko file. Do "insmod 99xx.ko". I can't do
that because I have secure boot enabled. You will need to turn it off
if you do. (Or figure out how to sign the module and register the key.)
You may be able to use a Machine Owner Key (MOK). See
https://docs.fedoraproject.org/en-US/Fedora/23/html/System_Administrators...
This process worked for me in Fedora 32 and is the same for other distros.
https://wiki.debian.org/SecureBoot#MOK_-_Machine_Owner_Key
might be useful.
--
George N. White III
1:15 a.m.
On 2020-10-31 14:56, Samuel Sieb wrote:
What do you mean that it shows up and you can print to it?
Ooops. Missed that one. I can configure the printer and
print to it, but nothing shows on the printer's console window.
The print jobs just disappears. CUPS show no pending jobs.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Computers are like air conditioners.
They malfunction when you open windows
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
11:30 p.m.
On 2020-10-30 20:38, ToddAndMargo via users wrote:
1) connected a USB to Parallel converter card. Printer work fine
2) boot off of Fedora-Xfce-Live-x86_64-33-1.2.iso. Printer
admin still can't find the card.
3) With
# modprobe -r lp
# modprobe -r parport_pc
# modprobe parport_pc io=0x378 irq=11
# modprobe lp
the card does show up and you can print to it, but
the jobs instantly disappear and nothing shows on
the printer's status screen
More tests:
4) tried a different parallel port cable with
and without #3 above. no symptom change
5) tested with a uboobo live usb: xubuntu-20.10-desktop-amd64.iso
with and without #3 above. no symptom change
2:29 a.m.
On 2020-10-30 20:38, ToddAndMargo via users wrote:
Hi All,
Here we go again.
I now have a Siig JJ-E01211-S1 Single Parallel Port PCIe Card
https://stage.siig.com/products/it-products/serial-parallel/parallel/pcie...
System Requirements:
...
Linux kernel 2.6 and later version
Works with Linux but not supported
And Printer Admin and CUPS do not find it.
Troubleshooting:
1) connected a USB to Parallel converter card. Printer work fine
2) boot off of Fedora-Xfce-Live-x86_64-33-1.2.iso. Printer
admin still can't find the card.
3) With
# modprobe -r lp
# modprobe -r parport_pc
# modprobe parport_pc io=0x378 irq=11
# modprobe lp
the card does show up and you can print to it, but
the jobs instantly disappear and nothing shows on
the printer's status screen
What next?
-T
Here is some data on the card
# udevadm info --attribute-walk /dev/lp0
Unknown device "/dev/lp0": No such device
# lspci -nn | grep -i moschip
01:00.0 Parallel controller [0701]: MosChip Semiconductor Technology
Ltd. MCS9900 Multi-I/O Controller [9710:9900]
# lspci -vv -s 01:00.0
01:00.0 Parallel controller: MosChip Semiconductor Technology Ltd.
MCS9900 Multi-I/O Controller (prog-if 03 [IEEE1284])
Subsystem: Device a000:2000
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Interrupt: pin A routed to IRQ 11
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]
[size=4K]
Region 5: Memory at ac000000 (32-bit, non-prefetchable) [disabled]
[size=4K]
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Address: 0000000000000000 Data: 0000
Capabilities: [78] Power Management version 3
Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA
PME(D0-,D1-,D2-,D3hot+,D3cold+)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [80] Express (v1) Legacy Endpoint, MSI 00
DevCap: MaxPayload 512 bytes, PhantFunc 0, Latency L0s <1us,
L1 <2us
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr+ NonFatalErr- FatalErr- UnsupReq+ AuxPwr-
TransPend-
LnkCap: Port #1, Speed 2.5GT/s, Width x1, ASPM L0s L1, Exit
Latency L0s <64ns, L1 <1us
ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk-
ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s (ok), Width x1 (ok)
TrErr- Train- SlotClk- DLActive- BWMgmt- ABWMgmt-
Capabilities: [100 v1] Virtual Channel
Caps: LPEVC=0 RefClk=100ns PATEntryBits=1
Arb: Fixed- WRR32- WRR64- WRR128-
Ctrl: ArbSelect=Fixed
Status: InProgress-
VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
Status: NegoPending- InProgress-
VC1: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl: Enable- ID=0 ArbSelect=Fixed TC/VC=00
Status: NegoPSiig JJ-E01211-S1 MosChip MCS9900 parallel port card not
recognizedending- InProgress-
Capabilities: [800 v1] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt-
RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt-
RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt-
RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout-
AdvNonFatalErr+
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout-
AdvNonFatalErr+
AERCap: First Error Pointer: 00, ECRCGenCap- ECRCGenEn-
ECRCChkCap- ECRCChkEn-
MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
HeaderLog: 00000000 00000000 00000000 00000000
I just opened:
Siig JJ-E01211-S1 MosChip MCS9900 parallel port card not recognized:
https://bugzilla.redhat.com/show_bug.cgi?id=1893631
1261
days inactive
1270
days old
42 comments
6 participants
participants (6)
-
Doug McGarrett -
Fulko Hew -
George N. White III -
Samuel Sieb -
ToddAndMargo -
Tom Horsley