On Sat, 21 Jan 2006, Eduard Bloch wrote: > tags 348975 + moreinfo > thanks > > May be an udev problem (which version? Upgrade to 0.080).
udev 0.081 > b) watching output of "udevmonitor --env" while slamr loads. It should > print MAJOR and MINOR numbers somewhere. UEVENT[1137873319.226625] add@/class/slamr/slamr0 ACTION=add DEVPATH=/class/slamr/slamr0 SUBSYSTEM=slamr SEQNUM=661 PHYSDEVPATH=/devices/pci0000:00/0000:00:08.0 PHYSDEVBUS=pci PHYSDEVDRIVER=slamr MAJOR=242 MINOR=0 # lspci | grep :08 0000:00:08.0 Modem: ALi Corporation M5457 AC'97 Modem Controller On the other hand, if I load slamr via /etc/modules before alsa, and then run "/etc/init.d/sl-modem-daemon start" before unloading and reloading any of the modules, the device does get created, with a major 136 instead: crw-rw---- 1 root dialout 136, 0 2006-01-21 12:27 /dev/ttySL0 This is promising. I should mention that when I then start wvdial to access the modem, I get a solid lockup and have to do a hard reset. As for kernel 2.6.15, I get an oops when the slamr module (yes, built for 2.6.15 of course) is inserted -- here's a bit of it: Call Trace: [<e0ab4eb8>] SetProp__13ModemInstanceUlUl+0x54/0x17c [slamr] [<c0222027>] class_device_create+0x6d/0x95 [<e09fc2db>] amrmo_pci_probe+0x2db/0x33b [slamr] [<c01d7939>] __pci_device_probe+0x32/0x41 [<c01d7967>] pci_device_probe+0x1f/0x34 [<c022127b>] driver_probe_device+0x32/0x7c [<c022131c>] __driver_attach+0x0/0x36 [<c0221340>] __driver_attach+0x24/0x36 [<c0220b7c>] bus_for_each_dev+0x46/0x6c [<c0221366>] driver_attach+0x14/0x18 [<c022131c>] __driver_attach+0x0/0x36 [<c0220ef8>] bus_add_driver+0x54/0x96 [<c01d7b39>] __pci_register_driver+0x75/0x88 [<e09fc38c>] amrmo_init+0x51/0xaf [slamr] [<c012b422>] sys_init_module+0xb3/0x1ae [<c0102b83>] sysenter_past_esp+0x54/0x75 Code: c1 f9 1f ff 74 24 08 ff 74 24 10 55 ff 74 24 0c 51 52 ff 74 24 1c 56 e8 44 f9 ff ff 89 c6 89 df 83 c4 20 ff 44 24 30 8b 44 24 30 <8a> 00 84 c0 0f 85 48 fc ff ff 3b 74 24 04 77 05 c6 06 00 eb 0e <6>ST7554 USB Modem. usbcore: registered new driver ST7554 USB Modem This happens whether I attempt to load the modem during boot or after. Anyway, my initially reported problem concerned the device node on 2.6.12, and that problem does appear to be triggered if alsa is loaded before slamr. This is an acceptable behavior for the moment, so you can close the report if you like. (I'm not going to pursue this further right now, as I don't need the modem until July.) Dave -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
