kmod-maint September 2022

kmod-maint@lists.fedoraproject.org

4 discussions

[Bug 1982438] New: [RFE] weak-modules just do initramfs
by bugzilla＠redhat.com 04 Sep '25

04 Sep '25

https://bugzilla.redhat.com/show_bug.cgi?id=1982438 Bug ID: 1982438 Summary: [RFE] weak-modules just do initramfs Product: Fedora Version: rawhide Hardware: All OS: Linux Status: NEW Component: kmod Assignee: kmod-maint(a)lists.fedoraproject.org Reporter: riehecky(a)fnal.gov QA Contact: extras-qa(a)fedoraproject.org CC: jonathan(a)jonmasters.org, kmod-maint(a)lists.fedoraproject.org, skozina(a)redhat.com, ykaliuta(a)redhat.com Target Milestone: --- Classification: Fedora Created attachment 1801653 --> https://bugzilla.redhat.com/attachment.cgi?id=1801653&action=edit Possible patch Description of problem: When loading packages containing external modules, it is helpful if I can just rebuild the initramfs as a separate - direct - step. Version-Release number of selected component (if applicable):29-3.f35 How reproducible:100% Steps to Reproduce: 1. Look for clear way to engage weak-modules just for initramfs 2. 3. Actual results: No entry point Expected results: Simple entry point Additional info: This is most obviously helpful with the EL kernels (and our friends at ELRepo) -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

1 3

[Bug 2024417] New: weak-modules:When the kernel is uninstalled, a message is displayed indicating that the folder cannot be found.
by bugzilla＠redhat.com 25 May '23

25 May '23

https://bugzilla.redhat.com/show_bug.cgi?id=2024417 Bug ID: 2024417 Summary: weak-modules:When the kernel is uninstalled, a message is displayed indicating that the folder cannot be found. Product: Fedora Version: rawhide Status: NEW Component: kmod Assignee: kmod-maint(a)lists.fedoraproject.org Reporter: yangyanchao6(a)huawei.com QA Contact: extras-qa(a)fedoraproject.org CC: jonathan(a)jonmasters.org, kmod-maint(a)lists.fedoraproject.org, skozina(a)redhat.com, ykaliuta(a)redhat.com Target Milestone: --- Classification: Fedora Created attachment 1842466 --> https://bugzilla.redhat.com/attachment.cgi?id=1842466&action=edit Possible patch Description of problem: Check the directory before entering the directory. This prevents alarms from being generated when the kernel is uninstalled. Version-Release number of selected component (if applicable): 29-6.fc36 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2024417

1 2

[Bug 2024409] New: weak-modules:Changing the sorting mode of rpmsort
by bugzilla＠redhat.com 25 May '23

25 May '23

https://bugzilla.redhat.com/show_bug.cgi?id=2024409 Bug ID: 2024409 Summary: weak-modules:Changing the sorting mode of rpmsort Product: Fedora Version: rawhide Status: NEW Component: kmod Assignee: kmod-maint(a)lists.fedoraproject.org Reporter: yangyanchao6(a)huawei.com QA Contact: extras-qa(a)fedoraproject.org CC: jonathan(a)jonmasters.org, kmod-maint(a)lists.fedoraproject.org, skozina(a)redhat.com, ykaliuta(a)redhat.com Target Milestone: --- Classification: Fedora Created attachment 1842464 --> https://bugzilla.redhat.com/attachment.cgi?id=1842464&action=edit Possible patch Description of problem: When the kernel version number contains a mixture of letters and numbers, the original sorting method has a problem. For example: [root@localhost kmod]# cat test 4.19.90-vhulk2108.6.0.h803 4.19.90-2109.1.0.0108 4.19.90-vhulk2109.1.0.h813 [root@localhost kmod]# ./test.sh + cat test + sed -e s/-/../g + sort -n -t. -k1,1 -k2,2 -k3,3 -k4,4 -k5,5 -k6,6 -k7,7 -k8,8 -k9,9 -k10,10 + sed -e's/\.\./-/g' 4.19.90-vhulk2109.1.0.h813 4.19.90-vhulk2108.6.0.h803 4.19.90-2109.1.0.0108 Even if this sort isn't helpful, maybe sort with "sort -V", instead of using "-" replace with ".." would make the code more readable? 29-6.fc36 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. https://bugzilla.redhat.com/show_bug.cgi?id=2024409

1 4

[Bug 1893631] New: Siig JJ-E01211-S1 MosChip MCS9900 parallel port card not recognized
by bugzilla＠redhat.com 13 Dec '22

13 Dec '22

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(a)lists.fedoraproject.org Reporter: ToddAndMargo(a)zoho.com QA Contact: extras-qa(a)fedoraproject.org CC: jonathan(a)jonmasters.org, kmod-maint(a)lists.fedoraproject.org, skozina(a)redhat.com, ykaliuta(a)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/s… 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 -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

1 15

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

kmod-maint September 2022