From: Frank Jacobberger <f1j@xmission.com>
To: linux-kernel@vger.kernel.org
Subject: test13-pre5 + char-major-145??
Date: Fri, 29 Dec 2000 14:07:57 -0700 [thread overview]
Message-ID: <3A4CFD2D.F7DE3125@xmission.com> (raw)
Please help me explain why I'm getting the following
modprobe reply on boot up after kernel test13-pre5
loads:
modprobe: Can't locate module char-major-145
>From /usr/src/linux/Documentation/devices.txt
10 char Non-serial mice, misc features
145 = /dev/hfmodem Soundcard shortwave modem control {2.6}
My modules.conf:
-----------------------------------
alias eth0 rtl8139
alias eth1 rtl8139
alias parport_lowlevel parport_pc
alias sound-slot-0 emu10k1
alias usb-controller usb-uhci
-----------------------------------
What may be calling this? Any advice where to go ferreting?
Thanks,
Frank
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-12-29 21:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-29 21:07 Frank Jacobberger [this message]
2000-12-29 22:35 ` test13-pre5 + char-major-145?? Keith Owens
-- strict thread matches above, loose matches on Subject: below --
2000-12-29 21:38 Bernd Eckenfels
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3A4CFD2D.F7DE3125@xmission.com \
--to=f1j@xmission.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox