From: David Dyck <david.dyck@fluke.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: unresolved symbols still in 2.4.30-rc2 (usbserial needs symbol tty_ldisc_ref and tty_ldisc_deref which are EXPORT_SYMBOL_GPL)
Date: Sat, 26 Mar 2005 12:39:01 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.62.0503261158220.206@dd.tc.fluke.com> (raw)
In-Reply-To: <20050326191306.GE3237@stusta.de>
On Sat, 26 Mar 2005 at 20:13 +0100, Adrian Bunk wrote:
> On Sat, Mar 26, 2005 at 10:52:30AM -0800, David Dyck wrote:
>>
>> I've been noticing that I'm still getting some "unresolved symbols"
>> with the 2.4.30 pre and rc series.
>> ...
>> ver_linux reports:
>> ...
>> modutils 2.4.2
>> ...
>
> A modutils upgrade should fix your problems.
Thanks for suggestion - I hadn't noticed that it had slipped out of date.
I took your advice and upgraded to 2.4.27 and rebuild (from clean)
the kernel and modules again.
$ bash scripts/ver_linux
...
Linux dd 2.4.30-rc2 #2 Sat Mar 26 11:37:17 PST 2005 i686
...
modutils 2.4.27
...
I'm still getting unresolved symbol tty_ldisc_ref and tty_ldisc_deref
dd:linux# insmod usbserial
Using /lib/modules/2.4.30-rc2/kernel/drivers/usb/serial/usbserial.o
...: unresolved symbol tty_ldisc_ref
...: unresolved symbol tty_ldisc_deref
After changing CONFIG_USB, CONFIG_USB_UHCI, and CONFIG_USB_SERIAL
from modules (=m) to built-in (=y) and another clean rebuild
I am able to boot cleanly and load modules that depend on usbserial
I would really like to get usbserial to be a module again
without getting the "unresolved symbols" for
tty_ldisc_ref and tty_ldisc_deref
next prev parent reply other threads:[~2005-03-26 20:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-26 18:52 David Dyck
2005-03-26 19:13 ` Adrian Bunk
2005-03-26 20:39 ` David Dyck [this message]
2005-03-27 0:31 ` upgrading modutils may have fixed: " David Dyck
2005-03-27 8:33 ` Jan Engelhardt
2005-03-28 4:20 ` Willy Tarreau
2005-03-28 11:00 ` Keith Owens
2005-03-28 11:37 ` Willy TARREAU
2005-03-28 14:53 ` Keith Owens
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=Pine.LNX.4.62.0503261158220.206@dd.tc.fluke.com \
--to=david.dyck@fluke.com \
--cc=bunk@stusta.de \
--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
all inboxes | Powered by JetHome®