Topic: Gigabit Module Unresolved Symbols

[David Oxilia]

I recently posted a message on the problem with the Intel gigabit ethernet
drivers in SME 5.5. Since this release is based in RH 7.2, the driver that
comes with 7.2 (e1000) apparently does not work with SMP and Enterprise
RH kernels (this is well documented).

I obtained the necessary RPM's to configure a 2.2.19 SMP kernel and
created the files needed in order to compile the Intel drivers. I am now
able to compile the drivers but an "insmod e1000" still complains about
"unresolved symbols" when attempting to load the driver. I have tried
the drivers supplied by Dell (SME is running on a PE 1500SC) which
are v3.1.22 and the latest ones I compiled, v4.2.17. I didn't expect
the former ones to work since they are intended for the default RH
kernel. The latter, although not configured for the running 2.2.19-7.0.8smp
kernel, are configured for a 2.2.19 smp kernel.

Here's the ouput from "insmod e1000".

Using /lib/modules/2.2.19-7.0.8smp/net/e1000.o
/lib/modules/2.2.19-7.0.8smp/net/e1000.o: unresolved symbol alloc_skb_Rsmp_2e387ab3
/lib/modules/2.2.19-7.0.8smp/net/e1000.o: unresolved symbol ether_setup_Rsmp_5659c977
/lib/modules/2.2.19-7.0.8smp/net/e1000.o: unresolved symbol unregister_netdev_Rsmp_51ede4c6
/lib/modules/2.2.19-7.0.8smp/net/e1000.o: unresolved symbol register_netdev_Rsmp_370aa5a6
/lib/modules/2.2.19-7.0.8smp/net/e1000.o: unresolved symbol proc_net_Rsmp_874c982c
/lib/modules/2.2.19-7.0.8smp/net/e1000.o: unresolved symbol free_irq_Rsmp_f20dabd8
/lib/modules/2.2.19-7.0.8smp/net/e1000.o: unresolved symbol pci_resource_len_Rsmp_1fa583fb
/lib/modules/2.2.19-7.0.8smp/net/e1000.o: unresolved symbol skb_under_panic_Rsmp_d1ae0e65
/lib/modules/2.2.19-7.0.8smp/net/e1000.o: unresolved symbol skb_realloc_headroom_Rsmp_e65f6606
/lib/modules/2.2.19-7.0.8smp/net/e1000.o: unresolved symbol netif_rx_Rsmp_511ee64d
/lib/modules/2.2.19-7.0.8smp/net/e1000.o: unresolved symbol pci_devices_Rsmp_3b428c78
/lib/modules/2.2.19-7.0.8smp/net/e1000.o: unresolved symbol eth_type_trans_Rsmp_38e312e9
/lib/modules/2.2.19-7.0.8smp/net/e1000.o: unresolved symbol iounmap_Rsmp_5fb196d4
/lib/modules/2.2.19-7.0.8smp/net/e1000.o: unresolved symbol pci_write_config_word_Rsmp_d9cc3b03
/lib/modules/2.2.19-7.0.8smp/net/e1000.o: unresolved symbol remove_proc_entry_Rsmp_5de096ff
/lib/modules/2.2.19-7.0.8smp/net/e1000.o: unresolved symbol request_region_Rsmp_6d32b2d7
/lib/modules/2.2.19-7.0.8smp/net/e1000.o: unresolved symbol skb_over_panic_Rsmp_26e81914
/lib/modules/2.2.19-7.0.8smp/net/e1000.o: unresolved symbol __kfree_skb_Rsmp_d0acf06a
/lib/modules/2.2.19-7.0.8smp/net/e1000.o: unresolved symbol pci_read_config_word_Rsmp_8764d15f
/lib/modules/2.2.19-7.0.8smp/net/e1000.o: unresolved symbol __ioremap_Rsmp_9eac042a
/lib/modules/2.2.19-7.0.8smp/net/e1000.o: unresolved symbol mod_timer_Rsmp_24685a70
/lib/modules/2.2.19-7.0.8smp/net/e1000.o: unresolved symbol mem_map_Rsmp_9b9816ae
/lib/modules/2.2.19-7.0.8smp/net/e1000.o: unresolved symbol printk_Rsmp_1b7d4074
/lib/modules/2.2.19-7.0.8smp/net/e1000.o: unresolved symbol kfree_Rsmp_037a0cba
/lib/modules/2.2.19-7.0.8smp/net/e1000.o: unresolved symbol synchronize_irq_Rsmp_143bb217
/lib/modules/2.2.19-7.0.8smp/net/e1000.o: unresolved symbol pci_set_master_Rsmp_040f6432
/lib/modules/2.2.19-7.0.8smp/net/e1000.o: unresolved symbol create_proc_entry_Rsmp_ac9141cb
/lib/modules/2.2.19-7.0.8smp/net/e1000.o: unresolved symbol sprintf_Rsmp_3c2c5af5
/lib/modules/2.2.19-7.0.8smp/net/e1000.o: unresolved symbol kmalloc_Rsmp_93d4cfe6
/lib/modules/2.2.19-7.0.8smp/net/e1000.o: unresolved symbol qdisc_reset_Rsmp_b4946d90
/lib/modules/2.2.19-7.0.8smp/net/e1000.o: unresolved symbol __const_udelay_Rsmp_eae3dfd6
/lib/modules/2.2.19-7.0.8smp/net/e1000.o: unresolved symbol pci_read_config_dword_Rsmp_2ca7e89f
/lib/modules/2.2.19-7.0.8smp/net/e1000.o: unresolved symbol pci_write_config_dword_Rsmp_f0fbd200
/lib/modules/2.2.19-7.0.8smp/net/e1000.o: unresolved symbol release_region_Rsmp_43bde9b1
/lib/modules/2.2.19-7.0.8smp/net/e1000.o: unresolved symbol jiffies_Rsmp_0da02d67
/lib/modules/2.2.19-7.0.8smp/net/e1000.o: unresolved symbol unregister_reboot_notifier_Rsmp_3980aac1
/lib/modules/2.2.19-7.0.8smp/net/e1000.o: unresolved symbol pci_read_config_byte_Rsmp_e5ceea13
/lib/modules/2.2.19-7.0.8smp/net/e1000.o: unresolved symbol request_irq_Rsmp_0c60f2e0
/lib/modules/2.2.19-7.0.8smp/net/e1000.o: unresolved symbol bh_active_Rsmp_fff9d0a3
/lib/modules/2.2.19-7.0.8smp/net/e1000.o: unresolved symbol del_timer_Rsmp_5811f067
/lib/modules/2.2.19-7.0.8smp/net/e1000.o: unresolved symbol register_reboot_notifier_Rsmp_1cc6719a
/lib/modules/2.2.19-7.0.8smp/net/e1000.o:
Hint: You are trying to load a module without a GPL compatible license
      and it has unresolved symbols.  Contact the module supplier for
      assistance, only they can help you.

I wrote to Intel for advice but so far no reply. Any advice on how to
configure the 2.2.19 kernel in SME 5.5 to obtain a working e1000
module would be much appreciated.

Thanks, David.

[David Oxilia]

Further to the previous message, I recompiled the drivers for the
uniprocessor kernel. Again, the drivers installed by SME 5.5 for
the intel gigabit ethernet cards don't work. The latest compiled
drivers also give unresolved symbols (fewer but still there):

 Using /lib/modules/2.2.19-7.0.8/net/e1000.o
/lib/modules/2.2.19-7.0.8/net/e1000.o: unresolved symbol create_proc_entry_R0ca385ff
/lib/modules/2.2.19-7.0.8/net/e1000.o: unresolved symbol proc_net_R4d9a80b1
/lib/modules/2.2.19-7.0.8/net/e1000.o: unresolved symbol unregister_netdev_R114eb8e1
/lib/modules/2.2.19-7.0.8/net/e1000.o: unresolved symbol qdisc_reset_Rdb2f2b79
/lib/modules/2.2.19-7.0.8/net/e1000.o: unresolved symbol register_netdev_R42ecb5cd
/lib/modules/2.2.19-7.0.8/net/e1000.o: unresolved symbol skb_over_panic_R4a1520c7
/lib/modules/2.2.19-7.0.8/net/e1000.o: unresolved symbol skb_realloc_headroom_Ra9f7926d
/lib/modules/2.2.19-7.0.8/net/e1000.o: unresolved symbol ether_setup_Rce1695bf
/lib/modules/2.2.19-7.0.8/net/e1000.o: unresolved symbol iounmap
/lib/modules/2.2.19-7.0.8/net/e1000.o: unresolved symbol __ioremap
/lib/modules/2.2.19-7.0.8/net/e1000.o: unresolved symbol remove_proc_entry_Rc8a0ae1b
/lib/modules/2.2.19-7.0.8/net/e1000.o: unresolved symbol netif_rx_R7ebcf71a
/lib/modules/2.2.19-7.0.8/net/e1000.o: unresolved symbol mem_map_R3362b304
/lib/modules/2.2.19-7.0.8/net/e1000.o: unresolved symbol alloc_skb_R4ed7d200
/lib/modules/2.2.19-7.0.8/net/e1000.o: unresolved symbol eth_type_trans_Rb9709275
/lib/modules/2.2.19-7.0.8/net/e1000.o: unresolved symbol skb_under_panic_R21bd456c
/lib/modules/2.2.19-7.0.8/net/e1000.o: unresolved symbol __const_udelay
/lib/modules/2.2.19-7.0.8/net/e1000.o: unresolved symbol __kfree_skb_R707ed99b
/lib/modules/2.2.19-7.0.8/net/e1000.o:
Hint: You are trying to load a module without a GPL compatible license
      and it has unresolved symbols.  Contact the module supplier for
      assistance, only they can help you.

[elenezet]

I use a e1000 and after installing dev-tools package i compil the driver and now it seem work fine. I use it on my localnetwork and all seem fine. Do you try to compil it on sme5.5 with dev-tools ? I found the dev-tools on  http://www.myezserver.com/downloads/mitel/contrib/dev-tools/).
I have no problem with e1000 now.
May be i miss something but try it.
elenezet

[Yung-Yum Ang]

Hi David,

Are you able to successfully compile the latest e1000 driver for sme server 5.5? If you are, would you be able to send the compiled e1000.o file to me?

Thanks for you help.

Regards,
Yung-Yum

[David Oxilia]

Yung-Yum,

I successfully compiled UP (single processor) gigabit drivers.
The version I compiled is Intel's latest; v4.2.17. I plan to
continue attempts in compiling SMP drivers but I haven't had
the time lately.

The single proc drivers seem to work well after a week in
production. I do recommend that you follow Intel's recommendation
and set the parameter RxIntDelay to 0. The adapter seems
to hang occasionally when it is set to the default 64.
You can do this manually or in the startup scripts. It is
useful to test manually first by:

$ ifdown eth0
$ rmmod e1000
$ insmod e1000 RxIntDelay=0
$ ifup eth0; dmesg

I was unsuccessful in transferring data from one server
to another over these adapters using jumbo frames (I tried
mtu=6000 and mtu=9000) and scp but this may be due to my
switches. The default mtu=1500 works fine though. These
drivers work in both SME 5.0 and 5.5.

You can download the tarball from the following location:

ftp://ftp.arcop.com/swr/eth_drivers/

Best regards, David.