insmod errors


Results 1 to 4 of 4

Thread: insmod errors

  1. #1
    Join Date
    Aug 2003
    Posts
    47

    insmod errors

    i have slackware 9 installed and a working realtek nic which uses the 8139too driver.
    however, on boot up i get a load of errors from insmod, its seems to be trying all the 8139XX drivers or something.
    here is an eg of the error:

    8139cp: 10/100 pci ethernet driver v0.30
    insmod 8139cp failed
    insmod:/lib/modules/2.4.20/kernel/drivers/net/8139cp.o.gz:init_module: no such device
    hint:insmod errors can be caused by incorrect module parameters including invalid IO or IRQ parameters

    there are a few 8139 drivers, (the one i want is 8139too) and these errors list every 8139xx driver apart from the one i want, this leads me to believe that it goes through all of them until it finds one that works.

    what have i done wrong ?

    cheers

  2. #2
    Join Date
    Dec 1999
    Location
    Toronto
    Posts
    39,320
    Besides the 8139cp module failure, is the correct module (8139too) being loaded correctly?

    lsmod (list loaded modules to check)

    If not, you could try adding

    alias eth0 8130too

    to /etc/modules.conf and then run

    depmod -ae

    (both as root)
    SEARCH FIRST... ASK SECOND Read the JL 'Community Help Posting Guidelines' before posting in the forums.

    Precompiled Redhat NTFS Modules

    Linuxplanet Tutorials

    If Linux doesn't have the solution, you have the wrong problem. ... Please do not send me a PM asking for help...

    Please read the search suggestion thread in JL Ideas

  3. #3
    Join Date
    Aug 2003
    Posts
    47
    yes it gets loaded and the card works fine.
    i think it may be something to do with hotplugging, is there any way i can tell hottpluging thing not to look for the nic?

  4. #4
    Join Date
    Dec 1999
    Location
    Toronto
    Posts
    39,320
    Have a look at /etc/hotplug/blacklist of which mine contains

    #
    # Listing a module here prevents the hotplug scripts from loading it.
    # Usually that'd be so that some other driver will bind it instead,
    # no matter which driver happens to get probed first. Sometimes user
    # mode tools can also control driver binding.
    #
    # Syntax: driver name alone (without any spaces) on a line. Other
    # lines are ignored.
    #

    # uhci ... usb-uhci handles the same pci class
    usb-uhci

    # tulip ... de4x5, xircom_tulip_cb, dmfe (...) handle same devices
    de4x5
    # At least 2.4.3 and later xircom_tulip doesn't have that conflict
    # xircom_tulip_cb
    dmfe

    # Modules for sound devices will be loaded by the alsasound script in
    # /etc/hotplug/usb/. They should not be loaded before rcalsasound has started.
    audio
    snd-usb-audio

    # 8139cp.o is listed only once in modules.pcimap. And for exactly this device
    # there is also an entry with 8139too. I have one bugreport that 8139cp does
    # not work for this card, therefore i add it to the blacklist.
    8139cp
    SEARCH FIRST... ASK SECOND Read the JL 'Community Help Posting Guidelines' before posting in the forums.

    Precompiled Redhat NTFS Modules

    Linuxplanet Tutorials

    If Linux doesn't have the solution, you have the wrong problem. ... Please do not send me a PM asking for help...

    Please read the search suggestion thread in JL Ideas

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •