Hello Duncan, On Thu, May 24, 2007 11:39, Duncan Sands wrote: > none of the changes that went in recently seem likely to have anything to do > with this. Since the driver usually looks for several firmware files before > locating the right one, one possibility is that the firmware loader is not > aborting immediately if the firmware file doesn't exist, but sits there until > a timeout occurs. You can check this by intercepting udev events using > udevmonitor.
Thanks for the hint. I named the firmware files so it finds it on the first hit, so that wasn't it. The problem turned out to be that I started udevd too late at bootup. It became a problem with newer kernels because they detect the modem sooner, so something probably gave up trying to load the firmware and added a 60 second delay. After fixing it the line is up in 15 seconds. Greetings, Indan ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
