I'll have someone test it out. Thanks for the patch.
On 04/10/2013 01:40 AM, Chung-Yih Wang (王崇懿) wrote:
> Hi Eric Miao, James Leddy and Daniel Manrique,
>
> If possible, could you give it a try for the patch I have on your device(s)?
> https://patchwork.kernel.org/patch/2156601/
>
> I think we
seems to be significant. The
PSMOUSE_CMD_RESET_DIS is irrelevant to this issue after trying
several times. So we have only implemented this patch to issue
the PSMOUSE_CMD_GETID so far.
Tested-by: Daniel Manrique
Signed-off-by: James M Leddy
---
drivers/input/mouse/synaptics.c |2 ++
1 file
I meant to send this to linux-input
On 04/09/2013 08:30 PM, James M Leddy wrote:
> We have been using this patch in Ubuntu kernels for 5 months now
> without issue. Since patch author Eric Miao no longer works for us,
> I'm sending to the list so that other distros can take advan
seems to be significant. The
PSMOUSE_CMD_RESET_DIS is irrelevant to this issue after trying
several times. So we have only implemented this patch to issue
the PSMOUSE_CMD_GETID so far.
Tested-by: Daniel Manrique
Signed-off-by: James M Leddy
---
drivers/input/mouse/synaptics.c |2 ++
1 file
, and even though we have a wide range of
hardware, it is impossible to guarantee that it'll work on everything
out there. I will do it however if it's the way we need to go with
this.
Please let me know what you think, or if you need any additional
information or testing.
James M Leddy (1
15:44:24 windeath kernel: eth0: Transmit timeout
using MII device, Tx status 0003.
Followed by more of the same except with status 000b. Unlike the realtek
errors a network stop/start/restart doesn't help. Looking at the patch
for 2.4.4 shows one tiny change to epic100.
--
James M.
aka
Gert Wollny wrote:
>
> Hello,
>
> i think it got it nailed, please try the attached patch (it is against
> 11-pre4, but it should work against all test11).
>
> Explanation:
> with test7-pre6 in the imm-module the new scsi - code was enabled (see
> imm.h).
> This causes the locking of the io_re
Gert Wollny wrote:
>
> On Tue, 14 Nov 2000, James M wrote:
> >Was just trying to find out why I can mount in 11pre1 and 11pre2 when
> > Gert can't mount at all, so I removed my VFAT factory formatted zipdisk
> > and put in an Ext2 formatted one.**BOOM**
&
Gert Wollny wrote:
>
> Actually i never tried to mount in my testings, just did "modprobe imm". I
> did not even load sd.o, which reads the size of the medium. Output after
> successfull modprobe:
> kernel: imm: Version 2.04 (for Linux 2.4.0)
> kernel: imm_connect 1
> kernel: imm: Found device at
James M wrote:
Was just trying to find out why I can mount in 11pre1 and 11pre2 when
Gert can't mount at all, so I removed my VFAT factory formatted zipdisk
and put in an Ext2 formatted one.**BOOM**
Al, my original oops report is here:
http://boudicca.tux.org/hypermail/linux-k
James M wrote:
>
>My previously reported Parport/Zip Oops seems to have gone away. I
> suspect the SMP race fixs were the culprit...thank you.
>However my parport is still misdetected as SPP by the IMM driver when
> it is actually set to EPP. This is an Epox/SMP Xeon (400
Winbond Super I/O Multi controller.
Now if we could just do something about those 10 fps in quake that I
lost since 2.3.4x;=)
James M.
aka "Dart"
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Pl
Kernel test10-pre2, Dual Xeon PII(400 mhz), Mandrake 7.1, microde
updates enabled
Mounting my zipdrive(IMM) will result in something like this:
Sysrq does not work, machine is completely dead after 20-40 seconds.The
usual progession is CPU's lockup, modprobe dies, kflushed and syslogd
follow shor
13 matches
Mail list logo