https://bugzilla.redhat.com/show_bug.cgi?id=1893631
Bug ID: 1893631 Summary: Siig JJ-E01211-S1 MosChip MCS9900 parallel port card not recognized Product: Fedora Version: 33 Hardware: x86_64 OS: Linux Status: NEW Component: kmod Severity: high Assignee: kmod-maint@lists.fedoraproject.org Reporter: ToddAndMargo@zoho.com QA Contact: extras-qa@fedoraproject.org CC: jonathan@jonmasters.org, kmod-maint@lists.fedoraproject.org, skozina@redhat.com, ykaliuta@redhat.com Target Milestone: --- Classification: Fedora
This is reproducible under both Fedora 32 and 33. Please fix on both.
Siig JJ-E01211-S1 Single Parallel Port PCIe Card
https://stage.siig.com/products/it-products/serial-parallel/parallel/pcie/si...
System Requirements: ... Linux kernel 2.6 and later version Works with Linux but not supported
Both Printer Admin (system-config-printer.py) and CUPS (https://127.0.0.1:631) do not find the card.
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 (lp0), but the jobs instantly disappear and nothing shows on the printer's status screen
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
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
https://bugzilla.redhat.com/show_bug.cgi?id=1893631
Yauheni Kaliuta ykaliuta@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |acaringi@redhat.com, | |airlied@redhat.com, | |bskeggs@redhat.com, | |hdegoede@redhat.com, | |itamar@ispbrasil.com.br, | |jarodwilson@gmail.com, | |jeremy@jcline.org, | |jglisse@redhat.com, | |josef@toxicpanda.com, | |kernel-maint@redhat.com, | |lgoncalv@redhat.com, | |linville@redhat.com, | |masami256@gmail.com, | |mchehab@infradead.org, | |mjg59@srcf.ucam.org, | |steved@redhat.com Component|kmod |kernel Assignee|kmod-maint@lists.fedoraproj |kernel-maint@redhat.com |ect.org | Doc Type|--- |If docs needed, set a value
https://bugzilla.redhat.com/show_bug.cgi?id=1893631
--- Comment #1 from Todd ToddAndMargo@zoho.com --- The same problem also exists with this card as well:
https://lavaports.com/serial-parallel-cards/products-pcie-bus-io-cards/paral...
$ lspci -nn | grep -i lava 01:00.0 Serial controller [0700]: Lava Computer mfg Inc Device [1407:dead] 01:00.2 Parallel controller [0701]: Lava Computer mfg Inc Device [1407:a000]
https://bugzilla.redhat.com/show_bug.cgi?id=1893631
--- Comment #2 from Todd ToddAndMargo@zoho.com --- More info on the Lava card:
$ udevadm info -a /dev/lp0 $ udevadm info --attribute-walk /dev/lp0 Unknown device "/dev/lp0": No such device
$ lspci -nn | grep -i lava 01:00.0 Serial controller [0700]: Lava Computer mfg Inc Device [1407:dead] 01:00.2 Parallel controller [0701]: Lava Computer mfg Inc Device [1407:a000]
$ lspci -v 01:00.0 Serial controller: Lava Computer mfg Inc Device dead (prog-if 02 [16550]) Subsystem: Device a000:1000 Flags: fast devsel, IRQ 16 I/O ports at e020 [size=8] Memory at ac003000 (32-bit, non-prefetchable) [size=4K] Memory at ac002000 (32-bit, non-prefetchable) [size=4K] Capabilities: [50] MSI: Enable- Count=1/8 Maskable- 64bit+ Capabilities: [78] Power Management version 3 Capabilities: [80] Express Legacy Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [800] Advanced Error Reporting
01:00.2 Parallel controller: Lava Computer mfg Inc Device a000 (prog-if 03 [IEEE1284]) Subsystem: Device a000:2000 Flags: fast devsel, IRQ 11 I/O ports at e010 [disabled] [size=8] I/O ports at e000 [disabled] [size=8] Memory at ac001000 (32-bit, non-prefetchable) [disabled] [size=4K] Memory at ac000000 (32-bit, non-prefetchable) [disabled] [size=4K] Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [78] Power Management version 3 Capabilities: [80] Express Legacy Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting
https://bugzilla.redhat.com/show_bug.cgi?id=1893631
--- Comment #3 from Todd ToddAndMargo@zoho.com --- This is still an issues as of 5.9.15-200.fc33.x86_64
https://bugzilla.redhat.com/show_bug.cgi?id=1893631
Marc marc.payne@mdpsys.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |marc.payne@mdpsys.co.uk Flags| |needinfo?(ToddAndMargo@zoho | |.com)
--- Comment #4 from Marc marc.payne@mdpsys.co.uk --- I’ve just got hold of a card based on the same MosChip MCS9900 as your SIIG card and am in the process of preparing a patch to enable support for it. I plan to submit it upstream soon.
Do you still have access to the Lava card? If so, I could enable support for that in the same patch. I need to know which chip it’s based on. I can see from the photo on the website you linked that it’s a MosChip but the actual part number is not documented anywhere that I can see. I have an idea which one it is based on the lspci output but would you mind checking the chip on your card?
https://bugzilla.redhat.com/show_bug.cgi?id=1893631
Todd ToddAndMargo@zoho.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(ToddAndMargo@zoho | |.com) |
--- Comment #5 from Todd ToddAndMargo@zoho.com --- Hi Marc,
AWESOME!
I still have the Lava card and I would love to send it to you. If you think it would help, I can dig out the SIIG card and include that as well. Please send me your "shipping" address to my eMail and I will get it/them shipped next Wednesday. Are you America based (no customs issues)?
I won't have access to either card until the day I ship it/them, so I will let you look at chip numbers. It will be interesting to see if lspci gave you the correct number.
-T
https://bugzilla.redhat.com/show_bug.cgi?id=1893631
--- Comment #6 from Marc marc.payne@mdpsys.co.uk --- Todd,
No need to ship the cards to me, I’m over in the UK so it’s best avoided anyway (in terms of cost and complexity). A close-up photo (whenever you can) of the main chip on the Lava card is really all I need – I’ll read the markings from that and look up the datasheet.
Marc
https://bugzilla.redhat.com/show_bug.cgi?id=1893631
--- Comment #7 from Todd ToddAndMargo@zoho.com --- Hi Marc,
The chip is so small on the Lava board that my camera can not catch it.
With a jewels 30X magnifier, it says:
WCH CH382L 508535808
The offer to send them to you still stands. I get my tea from you guys. Takes about four weeks through the post. The other direction should be about the same.
-T
https://bugzilla.redhat.com/show_bug.cgi?id=1893631
--- Comment #8 from Marc marc.payne@mdpsys.co.uk --- Todd,
Ahhh, the CH382L. I have a card based on that chip here. This news has left me surprised, confused and disappointed – all at the same time!
I was expecting the chip to be the MosChip MCS9901. I could see the MosChip logo on the photo of the card on the Lava website and they appear to sell other cards using MosChip chips. From the lspci output you’ll notice that you have a Serial controller in addition to the Parallel controller. The MCS9901 is a lower cost, more limited version of the MCS9900 (the chip on your SIIG card). One of the limitations is the modes of operation – you can’t have the parallel port enabled without having at least one serial port enabled. Since there is no serial port physically present on the card, Lava have set the device ID of the Serial controller to 0xDEAD. The serial driver won’t recognise the device so no ghost /dev/ttyS… device will show up on the system. The subsystem IDs A000:1000 and A000:2000 also match the defaults used by MosChip.
Did you buy the card recently? Was it direct from Lava? I assume it looks physically different to the one pictured on the Lava site? Perhaps they have changed the chip they are using… I can’t explain that lspci output from a CH382L-based card.
My (admittedly brief) experience of the CH382L is not great. Both the datasheet and the manufacturer’s website indicate that the parallel port should support the faster data transfer modes defined by IEEE1284 – EPP and ECP. My card only supports the legacy software controlled SPP mode and that makes it of limited use. It briefly crossed my mind that I might have a defective or fake chip but after downloading and examining the Windows driver direct from WCH I can see that my card is working as it should. Not sure what to say about that…
Marc
https://bugzilla.redhat.com/show_bug.cgi?id=1893631
--- Comment #9 from Todd ToddAndMargo@zoho.com --- Hi Marc,
I purchased it directly for Lava on 2020-10-06.
The picture on https://lavaports.com/serial-parallel-cards/products-pcie-bus-io-cards/paral... does not even look close!
It looks a lot like this one: https://i.ebayimg.com/images/g/kmwAAOSwNJxfJg7g/s-l1600.jpg
It think they changed their design under us.
If having it in your hand would help, the offer still holds.
-T
https://bugzilla.redhat.com/show_bug.cgi?id=1893631
--- Comment #10 from Ben Cotton bcotton@redhat.com --- This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '33'.
Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
https://bugzilla.redhat.com/show_bug.cgi?id=1893631
Todd ToddAndMargo@zoho.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|33 |35
https://bugzilla.redhat.com/show_bug.cgi?id=1893631
Todd ToddAndMargo@zoho.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(marc.payne@mdpsys | |.co.uk)
--- Comment #11 from Todd ToddAndMargo@zoho.com --- Hi Marc,
Have you been able to fix this under Fedora 36?
The offer to send you a bunch of my Parallel cards still stands.
-Todd
https://bugzilla.redhat.com/show_bug.cgi?id=1893631
--- Comment #12 from Ben Cotton bcotton@redhat.com --- This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '35'.
Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version.
Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
https://bugzilla.redhat.com/show_bug.cgi?id=1893631
Ben Cotton bcotton@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |EOL Status|NEW |CLOSED Last Closed| |2022-12-13 15:16:08
--- Comment #13 from Ben Cotton bcotton@redhat.com --- Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.
Fedora Linux 35 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field.
If you are unable to reopen this bug, please file a new report against an active release.
Thank you for reporting this bug and we are sorry it could not be fixed.
kmod-maint@lists.fedoraproject.org
-
bugzilla＠redhat.com