Re: 2.4.16, 8139too not loadable as a module - unresolved symbols

Marc Haber (mh+linux-kernel@zugschlus.de)
Fri, 7 Dec 2001 20:14:20 +0100


On Wed, Nov 28, 2001 at 08:39:50AM +0100, Marc Haber wrote:
> I am using Debian's kernel-package [1], and did the usual procedure for
> both kernels, that I usually do:
> make-kpkg clean
> make-kpkg --revision=3:today.0 build
> fakeroot debian/rules kernel-image-deb
>
> This procedure has resulted in a useable kernel .deb package for the
> last 18 months, and has resulted in a useable kernel .deb package for
> 2.4.16 with non-modularized 8139too.

Just for the record, my fault was not having modutils installed when I
built the kernel in a chroot. The kernel-image-deb step threw an
error, so I installed modutils and repeated that step which resulted
in an unuseable kernel.

A more in-depth investigation showed that the missing modutils had an
influence on the kernel build process that did not make it fail.
Repeating the whole process starting with the first step with modutils
installed resulted in a kernel with useable 8139too driver.

Greetings
Marc

-- 
-----------------------------------------------------------------------------
Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
Karlsruhe, Germany |  lose things."    Winona Ryder | Fon: *49 721 966 32 15
Nordisch by Nature |  How to make an American Quilt | Fax: *49 721 966 31 29
-
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/