1. Forum
  2. Usenet
  3. LINUX.DEBIAN.BUGS.DIST

  • Bug#265557: cannot disable automatic HiSax startup

    From Florian Effenberger@1:229/2 to All on Fri Aug 13 21:00:11 2004
    From: [email protected]

    Package: isdnutils-base
    Version: 1:3.3.0.20040704-0.4

    I don't know if this is the right package to file the bug report to, but
    I cannot disable the automatic HiSax startup. I have a AVM Fritz!Card
    PCI which is detected by HiSax, but does not work. If I rmmod the HiSax
    drivers and modprobe again with options type=27, it works just fine. So
    I guess the automatic hardware detected runs bogus here and uses the ISA
    card.

    Where can I disable the automatic HiSax startup? I tried /etc/hotplug/blacklist, /etc/discover.conf, boot prompt and disabling /etc/init.d/isdnutils, but nothings seems to work. Maybe the hardware
    detection lies in the kernel?


    --
    To UNSUBSCRIBE, email to [email protected]
    with a subject of "unsubscribe". Trouble? Contact [email protected]

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From Paul Slootman@1:229/2 to Florian Effenberger on Fri Aug 13 21:00:24 2004
    From: [email protected]

    On Fri 13 Aug 2004, Florian Effenberger wrote:

    I don't know if this is the right package to file the bug report to, but
    I cannot disable the automatic HiSax startup. I have a AVM Fritz!Card
    PCI which is detected by HiSax, but does not work. If I rmmod the HiSax drivers and modprobe again with options type=27, it works just fine. So
    I guess the automatic hardware detected runs bogus here and uses the ISA card.

    There is no automatic hardware detection in HiSax, unfortunately...
    You need to configure the module tool (module-init-tools for kernel 2.6, modutils for 2.4) so that the correct type=27 parameter is passed to
    HiSax when the module is loaded. As you say you first need to unload
    hisax, you're probably running a 2.6 kernel as there modules stay loaded
    even if no hardware is detected. In that case, add a file to
    /etc/modprobe.d/ with the contents:

    options hisax type=27 protocol=2

    and run update-modules

    Where can I disable the automatic HiSax startup? I tried /etc/hotplug/blacklist, /etc/discover.conf, boot prompt and disabling /etc/init.d/isdnutils, but nothings seems to work. Maybe the hardware detection lies in the kernel?

    It's not a "startup" what you mean, I think; if you mean the loading of
    the module, remove the line "hisax" from /etc/modules ...


    Paul Slootman


    --
    To UNSUBSCRIBE, email to [email protected]
    with a subject of "unsubscribe". Trouble? Contact [email protected]

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From Paul Slootman@1:229/2 to Florian Effenberger on Fri Aug 13 21:20:06 2004
    From: [email protected]

    On Fri 13 Aug 2004, Florian Effenberger wrote:

    thanks for the fast reply! I run kernel 2.6.7, that's correct. Where is
    the hisax module loaded? I grepped the whole /etc directory, and there
    is no occurence that starts HiSax. Only one occurence is in /etc/isdn/init.d.functions.

    That's what I am wondering about. *WHY* is HiSax started and from where?

    It's loaded together with all other modules listed in /etc/modules by
    the script /etc/rcS.d/S20module-init-tools


    Paul Slootman


    --
    To UNSUBSCRIBE, email to [email protected]
    with a subject of "unsubscribe". Trouble? Contact [email protected]

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From Paul Slootman@1:229/2 to Florian Effenberger on Fri Aug 13 21:30:11 2004
    From: [email protected]

    On Fri 13 Aug 2004, Florian Effenberger wrote:

    It's loaded together with all other modules listed in /etc/modules by
    the script /etc/rcS.d/S20module-init-tools

    /etc/modules has no entry called "hisax" or "isdn"... what else could it

    Hmmm...

    be? Is hisax automatically started by some other entry in /etc/modules?

    Or is it not compiled as module, but fixed in the kernel?

    It's not fixed in the kernel,. otherwise you couldn't unload it.
    Perhaps automatic module loading is enabled in your system (either in
    the kernel, or in the modules file by the word "auto"). Or perhaps the
    hotplug system is trying to be smart (I'm not familiar with that).

    However, by adding the line "hisax" to /etc/modules, and adding the
    modprobe.d file hisax will be loaded by the S20module-init-tools script,
    with the correct parameters. Otherwise you need to find out what is
    loading hisax. In any case, it's not isdnutils.


    Paul Slootman


    --
    To UNSUBSCRIBE, email to [email protected]
    with a subject of "unsubscribe". Trouble? Contact [email protected]

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From Florian Effenberger@1:229/2 to All on Fri Aug 13 23:50:16 2004
    From: [email protected]

    Hi there,

    However, by adding the line "hisax" to /etc/modules, and adding the modprobe.d file hisax will be loaded by the S20module-init-tools script,
    with the correct parameters. Otherwise you need to find out what is
    loading hisax. In any case, it's not isdnutils.

    Is modprobe.d new? Never heard of it before, just used /etc/modules
    Will have a look at this tomorrow.

    Thanks! ;)
    Florian


    --
    To UNSUBSCRIBE, email to [email protected]
    with a subject of "unsubscribe". Trouble? Contact [email protected]

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)
  • From Florian Effenberger@1:229/2 to All on Mon Aug 16 14:00:20 2004
    From: [email protected]

    Hi Paul,

    thanks for your feedback. I added a file /etc/modprobe.d/hisax with the following contents:

    ===
    options hisax type=27 protocol=2
    ===

    Seems to work fine. However, I have no clue why HiSax is started
    automatically, even without any references to it. I found no "auto" In /etc/modules.conf.

    Should this one be reassigned to the kernel team?

    Thanks!
    Florian


    --
    To UNSUBSCRIBE, email to [email protected]
    with a subject of "unsubscribe". Trouble? Contact [email protected]

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)