I got it working with 2.4.20, but unfortunately my sis900 was not
supported. However it was trivial to update sis900 to work with netconsole,
I simply made exactly the same modifications as the original patch did to
the tulip and the eepro100 driver. The result is here:
Now I have a few questions:
1) When it is so trivial to add support for another ethernet interface,
how come there are so few supported? Is there some potential problem,
I don't know about? In my case it certainly worked well enough for me
to actually get the message on another computer, and that was from an
Oops happening inside an IRQ which is if I understood it correctly one
of the most tricky contexts.
2) Why does netconsole require the interface to have an IP address?
Wouldn't it be possible to specify the source IP address as argument
for the module? IŽd like to do that to load the netconsole module
3) Would it be realistic to implement netconsole support for ethernet
cards connected through USB? I have a SB4100 cable modem using the
4) Would it be possible to implement a SysRq key to repeat the mesages
from the kernel buffer? This could be nice if the message got lost
due to network congestion or because the receiving computer was turned
off at the moment the crash happened.
-- Kasper Dupont -- der bruger for meget tid pć usenet. For sending spam use mailto:firstname.lastname@example.org for(_=52;_;(_%5)||(_/=5),(_%5)&&(_-=2))putchar(_); - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/