On Tue, 08 Aug 2000, Charles E. Gelm wrote about, Re: ethernet not working (part 2):
> On my old working kernel (2.2.13), boot messages were:
> ...
> FFreeing unused kernel memory: 32k freed.
> INIT: version 2.76 booting.
> request_module[net-pf-1] fork failed, errno 11
> NET4: Unix domain sockets 1.0 for Linux NET4.0
> ...
>
> What does the "request_module[net-pf-1] fork failed, errno 11" mean?
net-pf-1 = unix sockets.
According to you config file you have them defined as a module, as to howto
stop the message i am at the minute at a loss, i remember having the very
same problem a while back, but i did not have any further problems from it,
AFAIK.
>
> Also in this old kernel:
> depmod -a
> returned a ton of "Unresolved symbol..." messages. If this
> information can help you help me, I put them at
> http://gelm.net/depmod.txt
> I also put /var/log/messages at
> http://gelm.net/messages.txt
> & syslog at
> http://gelm.net/syslog.txt
The answer is in syslog, wrong modules for that kernel.
>
> modprobe ne
> can't locate module ne
>
> modprobe ne.o
> can't find module ne.o
>
> Then I edited 'Makefile's EXTRAVERSION=0
> make zImage modules modules_install install
> reboot
> Then
> depmod -a
> returned a prompt! No message.
>
> modprobe ne
> can't locate module ne
> ?
> So the new kernel behaves differently to the 'depmod -a' command,
> but I still don't have an eth0 interface.
It seems to do what it should now, the EXTRAVERSTION saves one a lot of
trouble as you can well see.
Module ne.o will possably only find the card IF you tell modprobe where to
attach the card, in /etc/modules.conf
The error is "Cant find" module ne, what happens when you give the full
path to modprobe, ?
Another thing to try is mv modules.conf to another name and create a new
one with only the following.
alias eth0 ne
options ne io=0x300
Change 0x300 for the cards address, the =irqX should not be required altho'
it is an option.
options ne io=0x300 irq=11
I have a ne2000 clone, it needs only the io address to be given.
Another problem which can cause havoc is having another kernel ethernet
driver compiled INTO the kernel or some hardware support which uses the same
io address.
My ne2000 card will not work when i install a distribution kernel from
slackware, i can only suspect what i said above to be the problem, however
after compiling a new kernel the card is found no problem.
> :-(
> Chuck
--
Regards Richard
[EMAIL PROTECTED]
http://people.zeelandnet.nl/pa3gcu/
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs
