From: John Kacur <jkacur@home.com>
To: fdavis112@juno.com, gregrollins@telocity.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Tulip driver doesn't work as module on 2.4.6
Date: Sat, 07 Jul 2001 01:07:35 -0400 [thread overview]
Message-ID: <3B469917.8A334B6@home.com> (raw)
In-Reply-To: <3B4677EB.966BA972@home.com> <3B467FF6.A2D991E7@telocity.com>
Frank Davis wrote:
>
> John,
> What do the logs say?
> Regards,
> -Frank
> --
Jul 5 23:32:48 speedy kudzu: failed
Jul 5 23:32:48 speedy kudzu: Hardware configuration timed out.
Jul 5 23:32:48 speedy kudzu: Run '/usr/sbin/kudzu' from the command
line to re-
detect.
Jul 5 23:32:48 speedy sysctl: net.ipv4.ip_forward = 0
Jul 5 23:32:53 speedy lpd: lpd startup succeeded
Jul 5 23:32:48 speedy sysctl: net.ipv4.conf.all.rp_filter = 1
Jul 5 23:32:48 speedy sysctl: error: 'net.ipv4.ip_always_defrag' is an
unknown
key
Jul 5 23:32:48 speedy sysctl: error: 'kernel.sysrq' is an unknown key
Jul 5 23:32:48 speedy network: Setting network parameters succeeded
Jul 5 23:32:49 speedy network: Bringing up interface lo succeeded
Jul 5 23:32:49 speedy network: Bringing up interface eth0 succeeded
Jul 5 23:32:50 speedy portmap: portmap startup succeeded
Greg Rollins wrote:
>
> John Kacur wrote:
>
> > Hi
> >
> > With Kernel 2.4.6, when I compile the Tulip driver as a module, I don't
> > have network connectivity. I can ping myself, and netstat -rn gives the
> > same table as with earlier kernels, but I can't connect to any of the
> > other computers on my network. (network = 1 pentium 120, and 1 pentium
> > 133 running a 2.2.16 and a 2.0.36 kernel respectively.) (the module is
> > loaded correctly and I have all the correct levels of support programs
> > as listed in the Changes file.) When I compile the Tulip driver directly
> > into the Kernel, it works.
> >
> > I would be happy to provide more information to anybody who wants to try
> > to figure this one out, just ask me what you need to know.
> >
> > Thanks
> >
> > John Kacur
> >
> > jkacur@home.com
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
>
> I haven't had this problem. I did my compile last p.m. and so far my Compaq
> Deskpro is running better than ever. Which tulip based card are you
> running? Mine is a Linksys 10/100. More detail please. I'm doing a modular
> load also.
>
> Greg Rollins
> gregrollins@telocity.com
>
Mine is also a Linksys 10/100
prev parent reply other threads:[~2001-07-07 4:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-07 2:46 Tulip driver doesn't work as module on 2.4.6 John Kacur
2001-07-07 3:20 ` Greg Rollins
2001-07-07 5:07 ` John Kacur [this message]
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=3B469917.8A334B6@home.com \
--to=jkacur@home.com \
--cc=fdavis112@juno.com \
--cc=gregrollins@telocity.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