From: "Timothy A. DeWees" <whtdrgn@mail.cannet.com>
To: Lukasz Gogolewski <lucas@supremedesigns.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: problems with sblive as well as 3com 3c905
Date: Wed, 31 Jan 2001 16:23:44 -0500 [thread overview]
Message-ID: <003701c08bcc$19b8bae0$7930000a@hcd.net> (raw)
In-Reply-To: <3A787D97.CBF7B327@supremedesigns.com>
You need to create a symlink
ln -s /lib/modules/2.4.1/kernel/drivers/net /lib/modules/2.4.1/net
That will fix the nic, I am not sure about sound. You may need to
create a misc link like
ln -s /lib/modules/2.4.1/kernel/drivers/misc /lib/modules/2.4.1/misc
----- Original Message -----
From: "Lukasz Gogolewski" <lucas@supremedesigns.com>
To: <linux-kernel@vger.kernel.org>
Sent: Wednesday, January 31, 2001 4:03 PM
Subject: problems with sblive as well as 3com 3c905
> After I compiled kernel 2.4.1 on rh 6.2 I enabled module support for 2
> of those devices.
>
> However when I rebooted my machine both of those devices are not
> working.
>
> I don't know what's wrong since I did make moudle and make
> module_install.
>
> When I try to configure mdoule for the sound card, I get a message
> saying that module wasn't found.
>
> For the network card I get Delaying initialization
>
> any suggestions on how to fix it?
>
> - Lucas
>
>
>
>
>
> -
> 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/
-
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 prev parent reply other threads:[~2001-01-31 21:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-31 21:03 problems with sblive as well as 3com 3c905 Lukasz Gogolewski
2001-01-30 22:00 ` Michael B. Trausch
2001-01-30 22:01 ` Michael B. Trausch
2001-01-31 21:23 ` Timothy A. DeWees [this message]
2001-01-31 22:00 ` Mathieu Chouquet-Stringer
2001-02-01 10:06 ` rui.sousa
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='003701c08bcc$19b8bae0$7930000a@hcd.net' \
--to=whtdrgn@mail.cannet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas@supremedesigns.com \
/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