Bug 466560

Summary: "don't know how to make device:" messages
Product: [Fedora] Fedora Reporter: Dawid Pietrala <dafydd>
Component: MAKEDEVAssignee: Chris Lumens <clumens>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: clumens, duck, eparis, harald, ol+redhat, valdis.kletnieks, yusufma77
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-10-14 15:44:42 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
dmesg none

Description Dawid Pietrala 2008-10-10 21:31:25 UTC
Created attachment 320061 [details]
dmesg

Description of problem:

when starting udev, it displays the following messages:

Uruchamianie udev: don't know how to make device "loop1"

don't know how to make device "loop2"

don't know how to make device "loop3"

don't know how to make device "loop4"

don't know how to make device "loop5"

don't know how to make device "loop6"

don't know how to make device "loop7"

don't know how to make device "lp1"

don't know how to make device "lp2"

don't know how to make device "lp3"

don't know how to make device "nvidia1"

don't know how to make device "nvidia2"

don't know how to make device "nvidia3"

it started to do so after latest update. nvidia binary driver ceased to work after the update and i think it can have something to do with that.

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

udev-127-1.fc10.i386

Additional info:

Comment 1 Yusuf Ma 2008-10-12 04:50:59 UTC
I have the same problem except that I don't have those "nvidia" lines. Same udev version here.

Comment 2 Dawid Pietrala 2008-10-12 09:20:18 UTC
it's MAKEDEV to be blamed for that. downgrading worked a treat. however, it's only a workaround. the bug is still valid.

Comment 3 Eric Paris 2008-10-13 19:12:02 UTC
looks to be the same as BZ 466385

Comment 4 Harald Hoyer 2008-10-14 15:44:42 UTC

*** This bug has been marked as a duplicate of bug 466385 ***