Firstly, try the command "cat /proc/modules"... this will show you if the ipx module is currently loaded (one of the lines should begin with "ipx" if so). If not, try these (as root): "modprobe ipx" followed by "/etc/init.d/ipx start". If this works, then edit /etc/modules and add a line for ipx (this will ensure that the module's automatically loaded whenever the system boots).
An alternate approach (assuming that the above commands work, of course), is to add "alias net-pf-4 ipx" to /etc/conf.modules (if there is an existing entry "alias net-pf-4 off", it should be replaced). This will allow kerneld to load/unload the module on demand, rather than always having it loaded. If you use this approach, /etc/modules should have the entry "auto" uncommented, and should not contain an entry for ipx. > I recalled that there were a number of optional modules that > could be installed in the kernel by the Debian installation > routines, and assumed I missed requesting IPX. So I did a clean > re-install, and saw that indeed, ncpfs support was an optional > module for inclusion in the kernel. I requested it and when > I later got to the dselect selections, I requested the ncpfs > and ipx packages. But even early on in the Debian installation > routine, I saw times when the scripts called ipx_configure themselves > and the same error appeared.
