> Looking at it closer, the smartlink-softmodem-2.9.6-79.i586.rpm installs > a file /etc/modprobe.d/slmodem which contains : > > # slmodem support > alias char-major-212 slamr > alias char-major-213 slusb
This is on 9.1. It configures the module auto-load, i.e. the module gets auto-loaded when first accessed. The first access would be from slmodemd. This is usually the (proper) way modules are loaded on Linux. A modprobe in the init script isn't needed. On 9.2 there's an explicit modprobe in the init script. If a similar change occured in other distros it's more likely the smartlink-softmodem package itself changed and SuSE (like everyone else) updated their version. I was also speculating whether a change in IRQ routing might cause slamr to take much longer to initialise. Why the implicit modprobe in 9.1 works where the explicit one in 9.2 needs a sleep afterwards I don't know, I'd expect the initialisation timing to be identical in both cases. > (however there is a modprobe -r in the stop part of the script - did > this lead to a problem where if you restarted the slmodemd initscript, > that the slamr module would be removed but not reloaded?) No. On 9.1 slamr would always be auto-loaded when needed (that's how the module autoloader works). On 9.2 there's an explicit modprobe in the start part. The diff which I didn't put in yesterday is here: http://volker.dnsalias.net/soft/rpm/suse9.2/slmodemd.diff Volker -- Volker Kuhlmann is possibly list0570 with the domain in header http://volker.dnsalias.net/ Please do not CC list postings to me.
