in Planet Linux OpenSource Debian Networking ~ read.

Got mad? or Why are modules autoloaded without hotplug or discover?

Today my goal was to get an AVM Fritz!Card running to send SMS via yaps.

Since on the old system is running kernel 2.4.x at the time of setup the only option was to use the capi driver and some hacks with hylafax to get all running. I don't wonna look deeper into the old setup, to prevent to get mad. Anyways ... an other setup was a faxserver. This was implemented also with the capi driver and capisuite.

So I was going straight forward and installed the capi driver on the known way.

Following my own install documentation I was really surprised that the hisax driver was already in place and the capi driver of the card was unable to load.

Okay ... unloading the hisax stuff and loading the fcpci module did work, but the really annoying part was, that the hisax modules got loaded on every reboot. Deleting the modules out of /lib/modules wasn't an option, cause they will reappear with the next kernel update. I decided to purge the hotplug and discover packages, with the result, that the hisax modules got loaded on boot (and other modules) anyways. It was looking like running any discover or hotplug process. So I double checked:

# COLUMNS=200 dpkg -l | grep hotplug
# COLUMNS=200 dpkg -l | grep discover

Hmmm .... I didn't got it. All the modules where auto loaded right before mounting the filesystems..

# ls -la /etc/rcS.d/ | grep -v S[01457] | grep ^l 
lrwxrwxrwx   1 root root   27 May 17 11:28 S20module-init-tools -> ../init.d/module-init-tools
lrwxrwxrwx   1 root root   18 May 17 11:28 S20modutils -> ../init.d/modutils
lrwxrwxrwx   1 root root   20 May 17 11:28 S30checkfs.sh -> ../init.d/checkfs.sh
lrwxrwxrwx   1 root root   19 May 17 11:28 S30procps.sh -> ../init.d/procps.sh
lrwxrwxrwx   1 root root   21 May 17 11:28 S35mountall.sh -> ../init.d/mountall.sh
lrwxrwxrwx   1 root root   15 May 17 11:28 S35quota -> ../init.d/quota
lrwxrwxrwx   1 root root   21 May 17 11:28 S36mountvirtfs -> ../init.d/mountvirtfs
lrwxrwxrwx   1 root root   20 May 17 11:28 S38resolvconf -> ../init.d/resolvconf
lrwxrwxrwx   1 root root   18 May 17 11:28 S39ifupdown -> ../init.d/ifupdown

Okay ... I gave up. If hisax is running, lets check if yaps isn't working with it. I copied the yaps.rc from the running system, modified the MSN and run a test:

Trying to open /dev/ttyI0 for modem standard
Unable to dial E2-0179

Okay ... since in the isdnlog appearing enties from the bus, there must be a pitfall anywhere and I tried to start a connection with minicom .... successfull.

I remembered than there was a problem with the lock-prefix when I did setup yaps some years ago. So I found a lock /var/lock/LCK..isdnctrl0 existing and did set lock-prefix /var/lock/LCK.. in /etc/yaps.rc.

  [Hangup] 
  [Send] ATZ<cr>
  [Expect] ATZ</cr><cr></cr><cr><lf>OK got OK
  </lf></cr>

HAHA!! Mission completed .. :) But the big question is ... why are the modules autoloaded?