Bug 858433

Summary: systemd-udevd: ctx=0x7f7cc41115a0 path=/lib/modules/3.6.0-rc2.git2.1.fc18.x86_64/kernel/ *.ko no such file or directory
Product: [Fedora] Fedora Reporter: Jóhann B. Guðmundsson <johannbg>
Component: loraxAssignee: Brian Lane <bcl>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: anaconda-maint-list, bcl, mgracik
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-04 18:15:15 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jóhann B. Guðmundsson 2012-09-18 22:22:00 UTC
Description of problem:

Here we are missing a lot of kernel modules so udev needs to be fixed/adjusted for those.

/sound/pci/hda/snd-hda-codec.ko
/sound/core/snd-pcm.ko
/drivers/media/video/videobuf2-vmalloc.ko
/drivers/edac/edac_core.ko
/drivers/usb/serial/usb_wwan.ko
/kernel/net/bluetooth/bluetooth.ko
/arch/x86/kvm/kvm.ko

Version-Release number of selected component (if applicable):

What ever was used to build anaconda 18.6.8 ( alpha )

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Fedora Admin XMLRPC Client 2013-02-04 15:04:14 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 2 Brian Lane 2013-02-04 18:01:14 UTC
Where are these missing from? Please describe the problem in more detail. Is this still a problem with the current lorax build?

Comment 3 Jóhann B. Guðmundsson 2013-02-04 18:15:15 UTC
This was filed what ca 5 months ago and probably just a fallout from early anaconda builds and I think after discussion in irc what needed to get fixed the rest where just harmless warnings ( if memory serves me correct ). I'll just close it and file another one if I come across this issue again.