Hi,
on my only 2.4.16 system, modprobe 8139too gives the following errors:
/lib/modules/2.4.16/kernel/drivers/net/8139too.o: unresolved symbol flush_signals
/lib/modules/2.4.16/kernel/drivers/net/8139too.o: unresolved symbol eth_type_trans
/lib/modules/2.4.16/kernel/drivers/net/8139too.o: unresolved symbol __kfree_skb
/lib/modules/2.4.16/kernel/drivers/net/8139too.o: unresolved symbol alloc_skb
/lib/modules/2.4.16/kernel/drivers/net/8139too.o: unresolved symbol pci_register_driver
/lib/modules/2.4.16/kernel/drivers/net/8139too.o: unresolved symbol pci_free_consistent
/lib/modules/2.4.16/kernel/drivers/net/8139too.o: unresolved symbol pci_enable_device
/lib/modules/2.4.16/kernel/drivers/net/8139too.o: unresolved symbol pci_read_config_byte
/lib/modules/2.4.16/kernel/drivers/net/8139too.o: unresolved symbol alloc_etherdev
/lib/modules/2.4.16/kernel/drivers/net/8139too.o: unresolved symbol reparent_to_init
/lib/modules/2.4.16/kernel/drivers/net/8139too.o: unresolved symbol cpu_raise_softirq
/lib/modules/2.4.16/kernel/drivers/net/8139too.o: unresolved symbol free_irq
/lib/modules/2.4.16/kernel/drivers/net/8139too.o: unresolved symbol unregister_netdev
/lib/modules/2.4.16/kernel/drivers/net/8139too.o: unresolved symbol kill_proc
/lib/modules/2.4.16/kernel/drivers/net/8139too.o: unresolved symbol iounmap
/lib/modules/2.4.16/kernel/drivers/net/8139too.o: unresolved symbol pci_alloc_consistent
/lib/modules/2.4.16/kernel/drivers/net/8139too.o: unresolved symbol interruptible_sleep_on_timeout
/lib/modules/2.4.16/kernel/drivers/net/8139too.o: unresolved symbol __ioremap
/lib/modules/2.4.16/kernel/drivers/net/8139too.o: unresolved symbol pci_read_config_word
/lib/modules/2.4.16/kernel/drivers/net/8139too.o: unresolved symbol skb_copy_and_csum_dev
/lib/modules/2.4.16/kernel/drivers/net/8139too.o: unresolved symbol register_netdev
/lib/modules/2.4.16/kernel/drivers/net/8139too.o: unresolved symbol kfree
/lib/modules/2.4.16/kernel/drivers/net/8139too.o: unresolved symbol pci_release_regions
/lib/modules/2.4.16/kernel/drivers/net/8139too.o: unresolved symbol wait_for_completion
/lib/modules/2.4.16/kernel/drivers/net/8139too.o: unresolved symbol request_irq
/lib/modules/2.4.16/kernel/drivers/net/8139too.o: unresolved symbol netif_rx
/lib/modules/2.4.16/kernel/drivers/net/8139too.o: unresolved symbol pci_unregister_driver
/lib/modules/2.4.16/kernel/drivers/net/8139too.o: unresolved symbol skb_over_panic
/lib/modules/2.4.16/kernel/drivers/net/8139too.o: unresolved symbol pci_set_master
/lib/modules/2.4.16/kernel/drivers/net/8139too.o: unresolved symbol rtnl_unlock
/lib/modules/2.4.16/kernel/drivers/net/8139too.o: unresolved symbol pci_write_config_word
/lib/modules/2.4.16/kernel/drivers/net/8139too.o: unresolved symbol daemonize
/lib/modules/2.4.16/kernel/drivers/net/8139too.o: unresolved symbol jiffies
/lib/modules/2.4.16/kernel/drivers/net/8139too.o: unresolved symbol softnet_data
/lib/modules/2.4.16/kernel/drivers/net/8139too.o: unresolved symbol rtnl_lock
/lib/modules/2.4.16/kernel/drivers/net/8139too.o: unresolved symbol printk
/lib/modules/2.4.16/kernel/drivers/net/8139too.o: unresolved symbol complete_and_exit
/lib/modules/2.4.16/kernel/drivers/net/8139too.o: unresolved symbol kernel_thread
/lib/modules/2.4.16/kernel/drivers/net/8139too.o: unresolved symbol __const_udelay
/lib/modules/2.4.16/kernel/drivers/net/8139too.o: unresolved symbol pci_request_regions
/lib/modules/2.4.16/kernel/drivers/net/8139too.o: insmod /lib/modules/2.4.16/kernel/drivers/net/8139too.o failed
/lib/modules/2.4.16/kernel/drivers/net/8139too.o: insmod 8139too failed
The same kernel, with the only config change being "y" instead of "m"
for 8139too, works fine, and the network interface is useable.
Did I do something wrong?
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
W li?cie z wto, 27-11-2001, godz. 15:08, Marc Haber pisze:
>
> Hi,
>
> on my only 2.4.16 system, modprobe 8139too gives the following errors:
[...]
> The same kernel, with the only config change being "y" instead of "m"
> for 8139too, works fine, and the network interface is useable.
>
> Did I do something wrong?
maybe you did, works fine for me as a module, although this driver
doesn't want to compile with gcc 3.0.x (as said in another thread a few
days ago).
did you do the _full_ recompile of the kernel? (cp .config /tmp;make
mrproper;cp /tmp/.config .;make oldconfig dep install modules_install)
or did you just make modules modules_install after changing the config?
regards
--
Marek P?tlicki <[email protected]>
Linux User ID=162988
On Wed, Nov 28, 2001 at 12:31:15AM +0100, Marek P?tlicki wrote:
> W li?cie z wto, 27-11-2001, godz. 15:08, Marc Haber pisze:
> > on my only 2.4.16 system, modprobe 8139too gives the following errors:
> [...]
> > The same kernel, with the only config change being "y" instead of "m"
> > for 8139too, works fine, and the network interface is useable.
> >
> > Did I do something wrong?
>
> maybe you did, works fine for me as a module, although this driver
> doesn't want to compile with gcc 3.0.x (as said in another thread a few
> days ago).
*shrug*
> did you do the _full_ recompile of the kernel? (cp .config /tmp;make
> mrproper;cp /tmp/.config .;make oldconfig dep install modules_install)
> or did you just make modules modules_install after changing the config?
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.
Greetings
Marc
[1] which provides a comfortable way to produce self-contained .deb
packages including maintainer scripts that take care of modules,
System.map and the boot loader, from vanilla kernel sources. I repeat:
Using kernel package does not mean that vendor kernel sources are
used, the kernels are built with vanilla kernels from kernel.org.
--
-----------------------------------------------------------------------------
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
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