Hi mate,
> > I keep getting the following errors in my messages
> > file:
> >
> > Mar 31 19:31:25 pcserv modprobe: modprobe: Can't
> > locate module sound-slot-0
> > Mar 31 19:31:25 pcserv modprobe: modprobe: Can't
> > locate module sound-service-0-0
> >
> > I run RH8 and don't have a sound card
On Mon, 2003-03-31 at 19:34, Michael Mansour wrote:
> Hi,
>
> I keep getting the following errors in my messages
> file:
>
> Mar 31 19:31:25 pcserv modprobe: modprobe: Can't
> locate module sound-slot-0
> Mar 31 19:31:25 pcserv modprobe: modprobe: Can't
> locate module sound-service-0-0
>
> I ru
Hi,
I keep getting the following errors in my messages
file:
Mar 31 19:31:25 pcserv modprobe: modprobe: Can't
locate module sound-slot-0
Mar 31 19:31:25 pcserv modprobe: modprobe: Can't
locate module sound-service-0-0
I run RH8 and don't have a sound card and don't need
one.
How can I turn thes
On Wed, 26 Mar 2003, Michael Fratoni wrote:
>
> Did you run something like mii-tool at that
time? It's the result of some
> application trying to probe ethernet devices 0
-7. I know I can reproduce
> it if I run mii-tool without specifying the
device. Like so:
>
Oops! yes I did. Thank you very
] Behalf Of Michael Fratoni
Sent: Thursday, March 27, 2003 5:19 AM
To: [EMAIL PROTECTED]
Subject: Re: Strange modprobe error logged
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 26 March 2003 07:45 pm, Fred Janssen Groesbeek wrote:
> Hello members of redhat-list,
>
> Th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 26 March 2003 07:45 pm, Fred Janssen Groesbeek wrote:
> Hello members of redhat-list,
>
> There was a strange modprobe error logged on a RH7.3-
> based linuxbox telling it could not probe eth1-eth7
> (See attached excerp
Hello members of redhat-list,
There was a strange modprobe error logged on a RH7.3-
based linuxbox telling it could not probe eth1-eth7
(See attached excerpt from /var/log/messages).
I have no clou what caused it. Since the machine has
only one NIC known as eth0 with alias eth0:0 and alias eth0
Hi Tim,
Thanks for your help. However my source of problem was in the
build stages of the kernel. I had misspecified parallel port
support in the configuration process.
Cheers,
Dominic.
Tim Moore <[EMAIL PROTECTED]> writes:
> > Mar 9 12:57:40 rlevesque modprobe: modprobe: Can't locate mo
> Mar 9 12:57:40 rlevesque modprobe: modprobe: Can't locate module char-major-6
> Mar 9 12:58:12 rlevesque last message repeated 5 times
> Mar 9 12:59:16 rlevesque last message repeated 2 times
[/usr/src/linux/Documentation/devices.txt
...
6 charParallel printer devices
Hi,
I just recompiled the kernel-2.2.17-14. Here what is filling my logs:
Mar 9 12:57:40 rlevesque modprobe: modprobe: Can't locate module char-major-6
Mar 9 12:58:12 rlevesque last message repeated 5 times
Mar 9 12:59:16 rlevesque last message repeated 2 times
etc.
I am trying to find
.
>On Tue, Nov 23, 1999 at 12:15:02PM -0600, Hanigan Family wrote:
>> Hi all,
>> I was looking at my message log and it had alot
>> of entries like the following
>> localhost modprobe:can't locate module sound-service-0-3
>> localhost modprobe: can't locate module sound-slot-0
>> I don't have sou
I have a more general question. Where can I find documentation that
identifies the modprobe major numbers? For example, I'm getting the log
message:
modprobe: can't locate module char-major-108
during a ppp startup. Is there some general way to figure out what
modprobe is looking for based on t
On Tue, Nov 23, 1999 at 12:15:02PM -0600, Hanigan Family wrote:
> Hi all,
> I was looking at my message log and it had alot
> of entries like the following
> localhost modprobe:can't locate module sound-service-0-3
> localhost modprobe: can't locate module sound-slot-0
> I don't have sound on this
Hi all,
I was looking at my message log and it had alot
of entries like the following
localhost modprobe:can't locate module sound-service-0-3
localhost modprobe: can't locate module sound-slot-0
I don't have sound on this system is there anyway to
keep the system from wasting time looking for it
14 matches
Mail list logo