From: paule@ilu.vu
To: Andrew Morton <akpm@zip.com.au>
Cc: Chris Ball <chris@void.printf.net>, linux-kernel@vger.kernel.org
Subject: Re: 3com pcmcia modules.
Date: Sun, 10 Feb 2002 09:59:40 +0000 [thread overview]
Message-ID: <20020210095940.A1147@ilu.vu> (raw)
In-Reply-To: <20020209151533.A644@ilu.vu> <877kpmvetv.fsf@lexis.house.pkl.net>, <877kpmvetv.fsf@lexis.house.pkl.net>; <20020209160407.A1222@ilu.vu> <3C6584F3.D571C1CB@zip.com.au> <20020209220805.A383@ilu.vu>
In-Reply-To: <20020209220805.A383@ilu.vu>; from paule@ilu.vu on Sat, Feb 09, 2002 at 10:08:05PM +0000
On Sat, Feb 09, 2002 at 10:08:05PM +0000, paule@ilu.vu wrote:
> On Sat, Feb 09, 2002 at 12:22:11PM -0800, Andrew Morton wrote:
> > paule@ilu.vu wrote:
> > >
> > > root@paule:/lib/modules/2.5.3/kernel/drivers/net# insmod 3c59x
> > > Using /lib/modules/2.5.3/kernel/drivers/net/3c59x.o
> > > /lib/modules/2.5.3/kernel/drivers/net/3c59x.o: unresolved symbol
> > > del_timer_sync
> >
> > That can't happen :)
> >
>
> reconfigured kernel, re-made, and reconfigured rc.inet1 (under
> slackware8.0) to support multiple interfaces,
> and now it's all happy! *yay* :)
> (yes im being sick, and using a screen-less laptop to route
> two internal networks, but hey, it's less than 1u, and cheaper
> than a router :)
>
An old problem has re-appeared since I have done this,
On a soft-reboot ('reboot / shutdown -r now') the kernel
stops on its way back up stating
Socket Status 0x0000003
(or something similar)
and it then requires a hard-reset to clear.
This only seems to be under the 3c59x code / more-so the vortex module.
Any help would be appreciated.
Cheers,
next prev parent reply other threads:[~2002-02-10 10:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-09 15:15 3com pcmcia modules paule
2002-02-09 15:45 ` Chris Ball
2002-02-09 16:04 ` paule
2002-02-09 20:22 ` Andrew Morton
2002-02-09 22:08 ` paule
2002-02-10 9:59 ` paule [this message]
2002-02-10 10:13 ` Andrew Morton
2002-02-10 0:01 ` Jeff Garzik
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=20020210095940.A1147@ilu.vu \
--to=paule@ilu.vu \
--cc=akpm@zip.com.au \
--cc=chris@void.printf.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.