[Bug 2024409] New: weak-modules:Changing the sorting mode of rpmsort
by bugzilla@redhat.com
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
11 months, 1 week
[Bug 1893631] New: Siig JJ-E01211-S1 MosChip MCS9900 parallel port
card not recognized
by bugzilla@redhat.com
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...
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 year, 4 months
[Bug 1943856] New: kmod-nvidia fails with unknown symbols and no
such file
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1943856
Bug ID: 1943856
Summary: kmod-nvidia fails with unknown symbols and no such
file
Product: Fedora
Version: 34
Status: NEW
Component: kmod
Assignee: kmod-maint(a)lists.fedoraproject.org
Reporter: plarsen(a)redhat.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
Description of problem:
When running an update that includes kmod-nvidia (version 5.11.6-300.fc34 in
this case) I get a long list of errors:
Running scriptlet: kmod-nvidia-5.11.6-300.fc34.x86_64-3:460.56-1.fc34.x86_64
63/79
depmod: ERROR: fstatat(5, nvidia-modeset.ko): No such file or directory
depmod: ERROR: fstatat(5, nvidia.ko): No such file or directory
depmod: ERROR: fstatat(5, nvidia-uvm.ko): No such file or directory
depmod: ERROR: fstatat(5, nvidia-drm.ko): No such file or directory
depmod: ERROR: fstatat(7, ds2490.ko.xz): No such file or directory
depmod: ERROR: fstatat(7, ds2482.ko.xz): No such file or directory
depmod: ERROR: fstatat(7, w1_ds2408.ko.xz): No such file or directory
depmod: ERROR: fstatat(7, w1_ds2433.ko.xz): No such file or directory
depmod: ERROR: fstatat(7, w1_ds28e04.ko.xz): No such file or directory
depmod: ERROR: fstatat(7, w1_ds2781.ko.xz): No such file or directory
depmod: ERROR: fstatat(7, w1_ds2423.ko.xz): No such file or directory
depmod: ERROR: fstatat(7, w1_ds2760.ko.xz): No such file or directory
depmod: ERROR: fstatat(7, w1_ds2780.ko.xz): No such file or directory
depmod: ERROR: fstatat(7, w1_ds2431.ko.xz): No such file or directory
depmod: ERROR: fstatat(7, w1_smem.ko.xz): No such file or directory
depmod: ERROR: fstatat(7, w1_therm.ko.xz): No such file or directory
depmod: ERROR: fstatat(7, slip.ko.xz): No such file or directory
depmod: ERROR: fstatat(7, slcan.ko.xz): No such file or directory
depmod: ERROR: fstatat(8, ems_pci.ko.xz): No such file or directory
depmod: ERROR: fstatat(8, plx_pci.ko.xz): No such file or directory
depmod: ERROR: fstatat(8, kvaser_pci.ko.xz): No such file or directory
depmod: ERROR: fstatat(8, ems_usb.ko.xz): No such file or directory
depmod: ERROR: fstatat(8, esd_usb2.ko.xz): No such file or directory
depmod: ERROR: fstatat(8, c_can_platform.ko.xz): No such file or directory
depmod: ERROR: fstatat(7, trancevibrator.ko.xz): No such file or directory
depmod: ERROR: fstatat(7, stinger.ko.xz): No such file or directory
depmod: ERROR: fstatat(7, turbografx.ko.xz): No such file or directory
depmod: ERROR: fstatat(7, spaceball.ko.xz): No such file or directory
depmod: ERROR: fstatat(7, db9.ko.xz): No such file or directory
depmod: ERROR: fstatat(7, zhenhua.ko.xz): No such file or directory
depmod: ERROR: fstatat(7, walkera0701.ko.xz): No such file or directory
depmod: ERROR: fstatat(8, iforce.ko.xz): No such file or directory
depmod: ERROR: fstatat(7, magellan.ko.xz): No such file or directory
depmod: ERROR: fstatat(7, spaceorb.ko.xz): No such file or directory
depmod: ERROR: fstatat(7, twidjoy.ko.xz): No such file or directory
depmod: ERROR: fstatat(7, warrior.ko.xz): No such file or directory
depmod: ERROR: fstatat(6, tcp_vegas.ko.xz): No such file or directory
depmod: ERROR: fstatat(6, tcp_yeah.ko.xz): No such file or directory
depmod: ERROR: fstatat(6, tcp_lp.ko.xz): No such file or directory
depmod: ERROR: fstatat(6, tcp_westwood.ko.xz): No such file or directory
depmod: ERROR: fstatat(6, tcp_bic.ko.xz): No such file or directory
depmod: ERROR: fstatat(6, tcp_htcp.ko.xz): No such file or directory
depmod: ERROR: fstatat(6, tcp_veno.ko.xz): No such file or directory
depmod: ERROR: fstatat(6, tcp_hybla.ko.xz): No such file or directory
depmod: ERROR: fstatat(6, tcp_scalable.ko.xz): No such file or directory
depmod: ERROR: fstatat(6, tcp_illinois.ko.xz): No such file or directory
depmod: ERROR: fstatat(6, tcp_highspeed.ko.xz): No such file or directory
depmod: WARNING: /lib/modules/5.11.6-300.fc34.x86_64/extra/v4l2loopback.ko.xz
needs unknown symbol video_ioctl2
depmod: WARNING: /lib/modules/5.11.6-300.fc34.x86_64/extra/v4l2loopback.ko.xz
needs unknown symbol v4l2_ctrl_handler_init_class
depmod: WARNING: /lib/modules/5.11.6-300.fc34.x86_64/extra/v4l2loopback.ko.xz
needs unknown symbol video_devdata
depmod: WARNING: /lib/modules/5.11.6-300.fc34.x86_64/extra/v4l2loopback.ko.xz
needs unknown symbol v4l2_ctrl_new_custom
depmod: WARNING: /lib/modules/5.11.6-300.fc34.x86_64/extra/v4l2loopback.ko.xz
needs unknown symbol video_unregister_device
depmod: WARNING: /lib/modules/5.11.6-300.fc34.x86_64/extra/v4l2loopback.ko.xz
needs unknown symbol video_device_alloc
depmod: WARNING: /lib/modules/5.11.6-300.fc34.x86_64/extra/v4l2loopback.ko.xz
needs unknown symbol v4l2_device_register
depmod: WARNING: /lib/modules/5.11.6-300.fc34.x86_64/extra/v4l2loopback.ko.xz
needs unknown symbol __video_register_device
depmod: WARNING: /lib/modules/5.11.6-300.fc34.x86_64/extra/v4l2loopback.ko.xz
needs unknown symbol v4l2_ctrl_handler_free
depmod: WARNING: /lib/modules/5.11.6-300.fc34.x86_64/extra/v4l2loopback.ko.xz
needs unknown symbol v4l2_device_unregister
depmod: WARNING: /lib/modules/5.11.6-300.fc34.x86_64/extra/v4l2loopback.ko.xz
needs unknown symbol video_device_release
The errors seems to happen regardless of what module is being built.
Version-Release number of selected component (if applicable):
fc34-preview/beta
How reproducible:
Every update of kmod modules.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
1 year, 10 months
[Bug 1951176] systemd-modules-load "Failed to find module 'msr'"
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1951176
--- Comment #3 from Ben Cotton <bcotton(a)redhat.com> ---
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on
2022-06-07.
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 '34'.
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 34 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.
--
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=1951176
1 year, 11 months