Loading ...
Sorry, an error occurred while loading the content.

Debian on Linkstation: modprobe: Can't open dependencies file /lib/modules/2.4.17_mvl21-sandpoint/modules.dep

Expand Messages
  • James Ronald
    I m seeing the following messages in /var/log/daemon.log. Anyone know if it s important and if so how to resolve it or if not how to turn it off? For the most
    Message 1 of 5 , Apr 23, 2005
    • 0 Attachment
      I'm seeing the following messages in /var/log/daemon.log. Anyone know if
      it's important and if so how to resolve it or if not how to turn it off?
      For the most part they are about 15 mins apart but sometime not..

      Apr 23 16:53:11 KURO-BOX modprobe: modprobe: Can't open dependencies file
      /lib/modules/2.4.17_mvl21-sandpoint/modules.dep (No such file or directory)
      Apr 23 17:02:32 KURO-BOX modprobe: modprobe: Can't open dependencies file
      /lib/modules/2.4.17_mvl21-sandpoint/modules.dep (No such file or directory)
      Apr 23 17:02:32 KURO-BOX modprobe: modprobe: Can't open dependencies file
      /lib/modules/2.4.17_mvl21-sandpoint/modules.dep (No such file or directory)
      Apr 23 17:08:01 KURO-BOX modprobe: modprobe: Can't open dependencies file
      /lib/modules/2.4.17_mvl21-sandpoint/modules.dep (No such file or directory)
      Apr 23 17:23:02 KURO-BOX modprobe: modprobe: Can't open dependencies file
      /lib/modules/2.4.17_mvl21-sandpoint/modules.dep (No such file or directory)
      Apr 23 17:38:11 KURO-BOX modprobe: modprobe: Can't open dependencies file
      /lib/modules/2.4.17_mvl21-sandpoint/modules.dep (No such file or directory)

      thanks JR
    • James Ronald
      It looks like creating a symlink may be a solution to this issues as well as others I m not yet aware of. KURO-BOX:/lib/modules/2.4.17_mv121-sandpoint# ln -s
      Message 2 of 5 , Apr 23, 2005
      • 0 Attachment
        It looks like creating a symlink may be a solution to this issues as well as
        others I'm not yet aware of.

        KURO-BOX:/lib/modules/2.4.17_mv121-sandpoint# ln -s 2.4.17_kuro-box
        2.4.17_mv121-sandpoint

        Pretty sure this would not be an issue for those using the Kuro-Box
        firmware.

        JR

        >
        > I'm seeing the following messages in /var/log/daemon.log. Anyone know if
        > it's important and if so how to resolve it or if not how to turn it off?
        > For the most part they are about 15 mins apart but sometime not..
        >
        > Apr 23 16:53:11 KURO-BOX modprobe: modprobe: Can't open dependencies file
        > /lib/modules/2.4.17_mvl21-sandpoint/modules.dep (No such file or
        > directory)
        > Apr 23 17:02:32 KURO-BOX modprobe: modprobe: Can't open dependencies file
        > /lib/modules/2.4.17_mvl21-sandpoint/modules.dep (No such file or
        > directory)
        > Apr 23 17:02:32 KURO-BOX modprobe: modprobe: Can't open dependencies file
        > /lib/modules/2.4.17_mvl21-sandpoint/modules.dep (No such file or
        > directory)
        > Apr 23 17:08:01 KURO-BOX modprobe: modprobe: Can't open dependencies file
        > /lib/modules/2.4.17_mvl21-sandpoint/modules.dep (No such file or
        > directory)
        > Apr 23 17:23:02 KURO-BOX modprobe: modprobe: Can't open dependencies file
        > /lib/modules/2.4.17_mvl21-sandpoint/modules.dep (No such file or
        > directory)
        > Apr 23 17:38:11 KURO-BOX modprobe: modprobe: Can't open dependencies file
        > /lib/modules/2.4.17_mvl21-sandpoint/modules.dep (No such file or
        > directory)
        >
        > thanks JR
        >
        >
        >
        >
        >
        > Yahoo! Groups Links
        >
        >
        >
        >
        >
        >
        >
        >
      • James Stewart
        I don t think I made it clear in the instuctions to copy over the /lib/modules/2.4.17_mv121-sandpoint directory from your old LS file system to the new Debian
        Message 3 of 5 , Apr 23, 2005
        • 0 Attachment
          I don't think I made it clear in the instuctions to copy over the
          /lib/modules/2.4.17_mv121-sandpoint directory from your old LS file
          system to the new Debian one. The poor kernel is simply looking for
          external modules that it might consider loading. In the case of this
          kernel, there isn't much to consider except for the really useful
          loopback device and nfs networking.

          You can grab the tree out of a Buffalo update file that you un-archive
          and pick apart if you don't have it anywhere else.

          --- In LinkStation_General@yahoogroups.com, "James Ronald"
          <jronald@c...> wrote:
          > It looks like creating a symlink may be a solution to this issues as
          well as
          > others I'm not yet aware of.
          >
          > KURO-BOX:/lib/modules/2.4.17_mv121-sandpoint# ln -s 2.4.17_kuro-box
          > 2.4.17_mv121-sandpoint
          >
          > Pretty sure this would not be an issue for those using the Kuro-Box
          > firmware.
          >
          > JR
          >
          > >
          > > I'm seeing the following messages in /var/log/daemon.log. Anyone
          know if
          > > it's important and if so how to resolve it or if not how to turn
          it off?
          > > For the most part they are about 15 mins apart but sometime not..
          > >
          > > Apr 23 16:53:11 KURO-BOX modprobe: modprobe: Can't open
          dependencies file
          > > /lib/modules/2.4.17_mvl21-sandpoint/modules.dep (No such file or
          > > directory)
          > > Apr 23 17:02:32 KURO-BOX modprobe: modprobe: Can't open
          dependencies file
          > > /lib/modules/2.4.17_mvl21-sandpoint/modules.dep (No such file or
          > > directory)
          > > Apr 23 17:02:32 KURO-BOX modprobe: modprobe: Can't open
          dependencies file
          > > /lib/modules/2.4.17_mvl21-sandpoint/modules.dep (No such file or
          > > directory)
          > > Apr 23 17:08:01 KURO-BOX modprobe: modprobe: Can't open
          dependencies file
          > > /lib/modules/2.4.17_mvl21-sandpoint/modules.dep (No such file or
          > > directory)
          > > Apr 23 17:23:02 KURO-BOX modprobe: modprobe: Can't open
          dependencies file
          > > /lib/modules/2.4.17_mvl21-sandpoint/modules.dep (No such file or
          > > directory)
          > > Apr 23 17:38:11 KURO-BOX modprobe: modprobe: Can't open
          dependencies file
          > > /lib/modules/2.4.17_mvl21-sandpoint/modules.dep (No such file or
          > > directory)
          > >
          > > thanks JR
          > >
          > >
          > >
          > >
          > >
          > > Yahoo! Groups Links
          > >
          > >
          > >
          > >
          > >
          > >
          > >
          > >
        • James Ronald
          James, Creating a symbolic link worked as well. Have you compared the two directories? I was under the impression that the kuro-box may be more robust. JR
          Message 4 of 5 , Apr 24, 2005
          • 0 Attachment
            James,

            Creating a symbolic link worked as well. Have you compared the two
            directories? I was under the impression that the kuro-box may be more
            robust.

            JR

            >
            > I don't think I made it clear in the instuctions to copy over the
            > /lib/modules/2.4.17_mv121-sandpoint directory from your old LS file
            > system to the new Debian one. The poor kernel is simply looking for
            > external modules that it might consider loading. In the case of this
            > kernel, there isn't much to consider except for the really useful
            > loopback device and nfs networking.
            >
            > You can grab the tree out of a Buffalo update file that you un-archive
            > and pick apart if you don't have it anywhere else.
            >
            >> It looks like creating a symlink may be a solution to this issues as
            > well as
            >> others I'm not yet aware of.
            >>
            >> KURO-BOX:/lib/modules/2.4.17_mv121-sandpoint# ln -s 2.4.17_kuro-box
            >> 2.4.17_mv121-sandpoint
            >>
            >> Pretty sure this would not be an issue for those using the Kuro-Box
            >> firmware.
            >>
            >> JR
            >> >
            >> > I'm seeing the following messages in /var/log/daemon.log. Anyone
            > know if
            >> > it's important and if so how to resolve it or if not how to turn
            > it off?
            >> > For the most part they are about 15 mins apart but sometime not..
            >> >
            >> > Apr 23 16:53:11 KURO-BOX modprobe: modprobe: Can't open
            > dependencies file
            >> > /lib/modules/2.4.17_mvl21-sandpoint/modules.dep (No such file or
            >> > directory)
            >> > Apr 23 17:02:32 KURO-BOX modprobe: modprobe: Can't open
            > dependencies file
            >> > /lib/modules/2.4.17_mvl21-sandpoint/modules.dep (No such file or
            >> > directory)
            >> > Apr 23 17:02:32 KURO-BOX modprobe: modprobe: Can't open
            > dependencies file
            >> > /lib/modules/2.4.17_mvl21-sandpoint/modules.dep (No such file or
            >> > directory)
            >> > Apr 23 17:08:01 KURO-BOX modprobe: modprobe: Can't open
            > dependencies file
            >> > /lib/modules/2.4.17_mvl21-sandpoint/modules.dep (No such file or
            >> > directory)
            >> > Apr 23 17:23:02 KURO-BOX modprobe: modprobe: Can't open
            > dependencies file
            >> > /lib/modules/2.4.17_mvl21-sandpoint/modules.dep (No such file or
            >> > directory)
            >> > Apr 23 17:38:11 KURO-BOX modprobe: modprobe: Can't open
            > dependencies file
            >> > /lib/modules/2.4.17_mvl21-sandpoint/modules.dep (No such file or
            >> > directory)
            >> >
            >> > thanks JR
          • James Stewart
            ... Yea, you ll find a lot more modules there, but the doesn t mean that they will load. Normally you have to have hooks compiled in the kernel for them.
            Message 5 of 5 , Apr 24, 2005
            • 0 Attachment
              --- In LinkStation_General@yahoogroups.com, "James Ronald"
              <jronald@c...> wrote:
              > James,
              >
              > Creating a symbolic link worked as well. Have you compared the two
              > directories? I was under the impression that the kuro-box may be more
              > robust.

              Yea, you'll find a lot more modules there, but the doesn't mean that
              they will load. Normally you have to have "hooks" compiled in the
              kernel for them. It is possible that they are there but Buffalo then
              didn't bother to include the actual modules. We would have to look at
              the original kernel config file to be sure.

              Or try doing something like: "modprobe -v cdrom" and see if it
              actually loads.

              PS: I reworked documents in the Debian-on-Linkstation section again,
              things are now broken up in separate documents and cleaned up more.
            Your message has been successfully submitted and would be delivered to recipients shortly.