When loading kernel module for my network card into memory I get syslog messages about trying to set IP properties with dhcpd.
syslog output
...
Intel(R) PRO/1000 Network Driver - version 5.6.
10.1-k2
dhcpcd[1234]: sending request DHCP_DISCOVER
....

Why is dhcpd automaticaly called ? How to disable this behaviour ? I've made sure dhcpcd is not running before modprobe call.

Any idea ?

Look at the content of the /etc/rc.d/rc.inet1.conf, see if dhcp is enabled just in case

For this device (eth0) is dhcp enabled in rc.inet1.conf but I can't get how this relates to modprobe command (module loading only).
In /etc/modprobe.conf is alias eth0 e1000 only.

I even tried to boot in a single user mode (runlevel 1) so hotplug and another services won't start. Typing modprobe e1000 resulted again in dhcpd calling.

I have to add I'm running Slackware-current with 2.6.11.12 kernel.

I esteemed myself as an advanced Linux user but I have to reconsider this. Now I'm completely lost

Sorry for asking but why enable dhcp in rc.inet1.conf if you don't want dhcp ?

After upgrades of Slack current in past month, dhcp network configs started to fail randomly at boot. I've begun to track down the bug and I found this weird behavior and I need a system working exactly as expected - no automat(g)ical nightmare.
I followed your recommendation and disabled dhcp in rc.inet1.conf and I were very surprised because modprobe started to work as I looked for.
But I still wonder how is modprobe related to /etc/rc.d/rc.inet1.conf ? I suspect module-init-tools must be patched to know about this Slackware-specific configuration file which I would found very sad and against Slackware philosophy as is known.

I believe it's caused by hotplug net agent so I'd suggest to check this path. Sources are exceptionally patched with unavoidable fixes and it's valid for module-init-tools too.