On Sat, Jan 29, 2005 at 04:18:21PM -0200, Marcelo Tosatti wrote:
> Probably a task event is rescheduling itself repeatedly? e100 does not seem
> to schedule_task() events directly, so I wonder what is going on.
>
> Can you boot a machine with profile=2, then send the WOL packet causing
> keventd
On Fri, Jan 28, 2005 at 10:53:51AM -0800, Bukie Mabayoje wrote:
> Do you know the official NIC product name e.g Pro/100B. I need to identify
> the LAN Controller. There are differences between 557 (not sure if 557 can
> do WOL), 558 and 559 how they ASSERT the PME# signal. Even the same chip have
Hi,
we have about 70 P4 uniprocessor machines (some with Hyperthreading
capable CPUs) running linux 2.4.29, which are woken up on the weekdays
by sending a WOL packet to them. The machines all have a E100 nic with
WOL enabled in the bios. The E100 driver is compiled into the kernel
and not loaded
On Thu, Jan 27, 2005 at 10:59:20PM -0500, Dmitry Torokhov wrote:
> Thanks for noticing this. The following patch should fix timeout
> handling in libps2 and restore previous behavior:
This fixes it for me. I tested it with an unmodified atkbd.c and
the old firmware for my keyboard converter.
Than
Hi,
since the introduction of libps2 in the mainline 2.6 kernel I had the
issue that my keyboard[1] was no longer recognized.
The cause of this is that my "keyboard" responds to all commands with
an acknowledgement (0xFA), even if the command is not implemented. One
of those not implemented comman
5 matches
Mail list logo
