| Summary: | udev-114 missing /dev/lp0 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Henning Ryll <henning.ryll> |
| Component: | [OLD] Core system | Assignee: | udev maintainers <udev-bugs> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | CC: | m.debruijne |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
output og dmesg
kernel config dmesg after rmmod and modprobe parport /var/log/dmesg after reboot |
||
|
Description
Henning Ryll
2007-09-18 17:44:53 UTC
Does /sys contains anything with name lp0 - like /sys/class/printer/lp0. If yes, then udevinfo -a -p <PATH> could help. (In reply to comment #1) > Does /sys contains anything with name lp0 - like /sys/class/printer/lp0. > > If yes, then > udevinfo -a -p <PATH> > could help. > Sorry, there is no directory /sys/class/printer/ .. Adding usb devices i.e. my usbstick works fine. I'm getting a new device /dev/usbstick as defined in my local-udev-rules. But i find parport here: me # find /sys -iname 'parport*' /sys/module/parport_pc /sys/module/parport /sys/module/parport/holders/parport_pc /sys/bus/pnp/drivers/parport_pc /sys/bus/pci/drivers/parport_pc /sys/bus/platform/drivers/parport_pc me # udevinfo -a -p /sys/bus/pci/drivers/parport_pc Udevinfo starts with ... parent device. looking at device '/bus/pci/drivers/parport_pc': KERNEL=="parport_pc" SUBSYSTEM=="drivers" DRIVER=="" looking at parent device '/bus/pci/drivers': KERNELS=="drivers" SUBSYSTEMS=="" DRIVERS=="" looking at parent device '/bus/pci': KERNELS=="pci" SUBSYSTEMS=="subsystem" DRIVERS=="" ATTRS{drivers_autoprobe}=="1" Please attach kernel-config and dmesg output also. Created attachment 131384 [details]
output og dmesg
Created attachment 131385 [details]
kernel config
Created attachment 131387 [details]
dmesg after rmmod and modprobe parport
Your first dmesg attachement is useless, as the ringbuffer is filled with just usb-storage messages. Either attach dmesg from right after booting (if messages are not yet overwritten), or /var/log/dmesg if it exists and contains useful data. As I still do not see any problems maybe it helps to run udevmonitor --env while loading the module. Issue I see: you have enabled parport ide drivers. Created attachment 131429 [details]
/var/log/dmesg after reboot
me # udevmonitor --env
udevmonitor will print the received events for:
UDEV the event which udev sends out after rule processing
UEVENT the kernel uevent
UEVENT[1190306827.796019] add /module/parport (module)
ACTION=add
DEVPATH=/module/parport
SUBSYSTEM=module
SEQNUM=913
UEVENT[1190306827.797691] add /module/parport_pc (module)
ACTION=add
DEVPATH=/module/parport_pc
SUBSYSTEM=module
SEQNUM=914
UEVENT[1190306827.798404] add /bus/platform/drivers/parport_pc (drivers)
ACTION=add
DEVPATH=/bus/platform/drivers/parport_pc
SUBSYSTEM=drivers
SEQNUM=915
UEVENT[1190306827.798954] add /bus/pnp/drivers/parport_pc (drivers)
ACTION=add
DEVPATH=/bus/pnp/drivers/parport_pc
SUBSYSTEM=drivers
SEQNUM=916
UEVENT[1190306827.800411] add /bus/pci/drivers/parport_pc (drivers)
ACTION=add
DEVPATH=/bus/pci/drivers/parport_pc
SUBSYSTEM=drivers
SEQNUM=917
(In reply to comment #8) > Created an attachment (id=131429) [edit] > /var/log/dmesg after reboot > > me # udevmonitor --env > udevmonitor will print the received events for: > UDEV the event which udev sends out after rule processing > UEVENT the kernel uevent > > UEVENT[1190306827.796019] add /module/parport (module) > ACTION=add > DEVPATH=/module/parport > SUBSYSTEM=module > SEQNUM=913 > > UEVENT[1190306827.797691] add /module/parport_pc (module) > ACTION=add > DEVPATH=/module/parport_pc > SUBSYSTEM=module > SEQNUM=914 > > UEVENT[1190306827.798404] add /bus/platform/drivers/parport_pc (drivers) > ACTION=add > DEVPATH=/bus/platform/drivers/parport_pc > SUBSYSTEM=drivers > SEQNUM=915 > > UEVENT[1190306827.798954] add /bus/pnp/drivers/parport_pc (drivers) > ACTION=add > DEVPATH=/bus/pnp/drivers/parport_pc > SUBSYSTEM=drivers > SEQNUM=916 > > UEVENT[1190306827.800411] add /bus/pci/drivers/parport_pc (drivers) > ACTION=add > DEVPATH=/bus/pci/drivers/parport_pc > SUBSYSTEM=drivers > SEQNUM=917 > The udevmonitor log first shows: Only the driver gets loaded (and listed in sysfs). No other device dirs get created - so udev cannot create device nodes in /dev. Second: I see no udev events - do you have udevd running? My guess is: It can have something todo with parport IDE catching the parpart. Did you compile "Parallel printer support". I guess the module-name will be printer or lp. After starting udevmonitor, I found, that there are no messages when I do 'modprobe lp' So I decided to a 'make clean' and rebuild my kernel and all modules using my last kernel config file. I don't know why but after rebooting my machine everything works fine ?! The bug should be closed now ... Matthias, vielen Dank für deine Mühen. Gruß Henning |
