I retract my conclusion from my previous mail that the problem was caused by module load order. If I remove alsa modules and slamr and then reinsert the slamr module, the device node now gets created. The difference may be related to the fact that the ungrab_winmodem module was not inserting when I was having problems, and now that it does insert, the problem is gone. If this is the right explanation, I don't know what caused it.
UEVENT[1137876554.146094] add@/module/ungrab_winmodem ACTION=add DEVPATH=/module/ungrab_winmodem SUBSYSTEM=module SEQNUM=703 UEVENT[1137876554.158939] add@/module/slamr ACTION=add DEVPATH=/module/slamr SUBSYSTEM=module SEQNUM=704 UEVENT[1137876554.159497] add@/bus/pci/drivers/slamr ACTION=add DEVPATH=/bus/pci/drivers/slamr SUBSYSTEM=drivers SEQNUM=705 UEVENT[1137876554.162520] add@/class/slamr/slamr0 ACTION=add DEVPATH=/class/slamr/slamr0 SUBSYSTEM=slamr SEQNUM=706 PHYSDEVPATH=/devices/pci0000:00/0000:00:08.0 PHYSDEVBUS=pci PHYSDEVDRIVER=slamr MAJOR=242 MINOR=0 I can't reproduce the conditions in which the device node is not created and request the bug be closed. I appreciate your assistance. Dave PS The crash on the 2.6.15 kernel is most likely related to a problem in alsa that should probably be addressed first. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
