Re: Re: [2.6.6] Synaptics driver is 'jumpy'

Re: Re: [2.6.6] Synaptics driver is 'jumpy'

[Len Brown]

On Mon, 2004-05-17 at 03:04, Jan De Luyck wrote:
2.6.6 dmesg:

ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 7 9 11 12) *10
ACPI: PCI Interrupt Link [LNKE] enabled at IRQ 12

Detected ipw2100 PCI device at 0000:02:04.0, dev: eth1, mem:
0xD0206000-0xD0206FFF -> e19e8000, irq: 12

You need this patch:
http://bugme.osdl.org/show_bug.cgi?id=2665
available also in the -mm patch
and also in the latest 2.6.7 tree:
http://linux.bkbits.net:8080/linux-2.5/gnupatch-GV/8B+QdpNe99h1UQWNUN51JT3bfCTL673V4Sm1hnq8@public.gmane.org

-Len




-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click

Re: [ACPI] Re: [2.6.6] Synaptics driver is 'jumpy'

[Len Brown]

On Mon, 2004-05-17 at 03:04, Jan De Luyck wrote:
2.6.6 dmesg:

ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 7 9 11 12) *10
ACPI: PCI Interrupt Link [LNKE] enabled at IRQ 12

Detected ipw2100 PCI device at 0000:02:04.0, dev: eth1, mem:
0xD0206000-0xD0206FFF -> e19e8000, irq: 12

You need this patch:
http://bugme.osdl.org/show_bug.cgi?id=2665
available also in the -mm patch
and also in the latest 2.6.7 tree:
http://linux.bkbits.net:8080/linux-2.5/gnupatch@409feaa6JGkUiF4JYRNP7snqaHH2RQ

-Len

Re: [2.6.6] Synaptics driver is 'jumpy' -- FIXED

[Jan De Luyck]

On Monday 17 May 2004 21:19, Len Brown wrote:
> On Mon, 2004-05-17 at 03:04, Jan De Luyck wrote:
> 2.6.6 dmesg:
>
> ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 7 9 11 12) *10
> ACPI: PCI Interrupt Link [LNKE] enabled at IRQ 12
>
> Detected ipw2100 PCI device at 0000:02:04.0, dev: eth1, mem:
> 0xD0206000-0xD0206FFF -> e19e8000, irq: 12
>
> You need this patch:
> http://bugme.osdl.org/show_bug.cgi?id=2665

Thanks Len, this does the trick. 

Jan

-- 
His life was formal; his actions seemed ruled with a ruler.


-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click

Re: [2.6.6] Synaptics driver is 'jumpy' -- FIXED

[Jan De Luyck]

On Monday 17 May 2004 21:19, Len Brown wrote:
> On Mon, 2004-05-17 at 03:04, Jan De Luyck wrote:
> 2.6.6 dmesg:
>
> ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 7 9 11 12) *10
> ACPI: PCI Interrupt Link [LNKE] enabled at IRQ 12
>
> Detected ipw2100 PCI device at 0000:02:04.0, dev: eth1, mem:
> 0xD0206000-0xD0206FFF -> e19e8000, irq: 12
>
> You need this patch:
> http://bugme.osdl.org/show_bug.cgi?id=2665

Thanks Len, this does the trick. 

Jan

-- 
His life was formal; his actions seemed ruled with a ruler.

[2.6.6] Synaptics driver is 'jumpy'

[Jan De Luyck]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello List,

Since installing 2.6.6 on my trusty laptop, I can't use the built-in synaptics
touchpad anymore. The tracking is totally broken:

When you touch-drag on the touchpad, the mouse cursor will jump to where you
stopped your action approx. 1/1.5 seconds _after_ your move. This makes using
the touchpad virtually impossible.

This problem is not present under 2.6.5, which I'm running right now.
Same .config.

Nothing seems to show up in the logs that could reflect any problem.

Any pointers?

Jan
- --
Q:	"What is the burning question on the mind of every dyslexic
	existentialist?"
A:	"Is there a dog?"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAp0D2UQQOfidJUwQRAj6LAJ9B+0XoTi2cgFgZ1nzwCDcBknK6jgCeJw4G
48iBfznIMUmS0nQ8duhmrE4=
=6OiP
-----END PGP SIGNATURE-----

Re: [2.6.6] Synaptics driver is 'jumpy'

[Jan De Luyck]

[-- Attachment #1: Type: Text/Plain, Size: 1684 bytes --]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sunday 16 May 2004 21:29, Dmitry Torokhov wrote:
> On Sunday 16 May 2004 02:06 pm, Jan De Luyck wrote:
> > On Sunday 16 May 2004 19:18, Dmitry Torokhov wrote:
> > > Hmm.. there was no changes to PS/2 processing between 2.6.5 and 2.6.6
> > > except for some Logitech tweaking, but it should not affect Synaptics
> > > handling in any way...
> > >
> > > Could you check if you still have DMA enabled on your disks, check your
> > > time source (TSC, ACPI PM timer, etc) and probably boot with acpi off?
> > >
> > > Thank you.
> >
> > Dmitry,
> >
> > Booting with acpi=off fixes the problem, although I'm curious to what the
> > problem actually is.
> >
> > I've attached the dmesgs from 2.6.6, 2.6.5, and 2.6.6 with acpi=off.
> >
> > There is a line that says "Invalid control registers" that I wonder where
> > it comes from, but you might see something more here than I do.
>
> It comes from speedstep-centrino module, could you please try booting with
> ACPI but without speedstep-centrino loaded? Also, does it help if you do
> not compile/ load ACPI battery module?

Neither has any effect. 

I've also disabled CONFIG_X86_SPEEDSTEP_CENTRINO_ACPI, figuring there might be 
some problem with that, but that doesn't change a thing. 

Also, I'm wondering if there's any point in using the CONFIG_X86_PM_TIMER 
timesource?

I'm including my .config for reference.

Jan

- -- 
Never give an inch!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAqFx9UQQOfidJUwQRAkjbAJsGy8emc2FsEAiBcZ2Y9lTqmSEzVgCfcTEI
agl2KG+OBZKRYmNEyUAm+Mo=
=JwSf
-----END PGP SIGNATURE-----

[-- Attachment #2: config --]
[-- Type: text/plain, Size: 7263 bytes --]

CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y

CONFIG_EXPERIMENTAL=y
CONFIG_BROKEN=y
CONFIG_BROKEN_ON_SMP=y

CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_POSIX_MQUEUE=y
CONFIG_SYSCTL=y
CONFIG_LOG_BUF_SHIFT=14
CONFIG_HOTPLUG=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_KALLSYMS=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y

CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
CONFIG_OBSOLETE_MODPARM=y
CONFIG_MODVERSIONS=y
CONFIG_KMOD=y

CONFIG_X86_PC=y
CONFIG_MPENTIUMM=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=6
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_HPET_TIMER=y
CONFIG_HPET_EMULATE_RTC=y
CONFIG_PREEMPT=y
CONFIG_X86_TSC=y
CONFIG_X86_MCE=y
CONFIG_MICROCODE=y
CONFIG_X86_MSR=y
CONFIG_X86_CPUID=y

CONFIG_NOHIGHMEM=y
CONFIG_MTRR=y
CONFIG_HAVE_DEC_LOCK=y

CONFIG_PM=y

CONFIG_ACPI=y
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_INTERPRETER=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_SLEEP_PROC_FS=y
CONFIG_ACPI_AC=m
CONFIG_ACPI_BATTERY=m
CONFIG_ACPI_BUTTON=m
CONFIG_ACPI_FAN=m
CONFIG_ACPI_PROCESSOR=m
CONFIG_ACPI_THERMAL=m
CONFIG_ACPI_BUS=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_SYSTEM=y


CONFIG_CPU_FREQ=y
CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
CONFIG_CPU_FREQ_GOV_POWERSAVE=m
CONFIG_CPU_FREQ_GOV_USERSPACE=m
CONFIG_CPU_FREQ_TABLE=m

CONFIG_X86_ACPI_CPUFREQ=m
CONFIG_X86_SPEEDSTEP_CENTRINO=m
CONFIG_X86_SPEEDSTEP_CENTRINO_TABLE=y

CONFIG_PCI=y
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_PCI_NAMES=y
CONFIG_ISA=y

CONFIG_PCMCIA=m
CONFIG_YENTA=m
CONFIG_CARDBUS=y
CONFIG_I82092=m
CONFIG_TCIC=m
CONFIG_PCMCIA_PROBE=y

CONFIG_HOTPLUG_PCI=m

CONFIG_BINFMT_ELF=y


CONFIG_FW_LOADER=y


CONFIG_PARPORT=y
CONFIG_PARPORT_PC=y
CONFIG_PARPORT_PC_CML1=m
CONFIG_PARPORT_PC_FIFO=y
CONFIG_PARPORT_1284=y

CONFIG_PNP=y


CONFIG_BLK_DEV_LOOP=y

CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y

CONFIG_BLK_DEV_IDEDISK=y
CONFIG_BLK_DEV_IDECD=m
CONFIG_IDE_TASKFILE_IO=y

CONFIG_IDE_GENERIC=y
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
CONFIG_IDEDMA_PCI_AUTO=y
CONFIG_BLK_DEV_ADMA=y
CONFIG_BLK_DEV_PIIX=y
CONFIG_BLK_DEV_IDEDMA=y
CONFIG_IDEDMA_AUTO=y

CONFIG_SCSI=m
CONFIG_SCSI_PROC_FS=y

CONFIG_BLK_DEV_SD=m
CONFIG_CHR_DEV_SG=m



CONFIG_SCSI_QLA2XXX=m





CONFIG_IEEE1394=m

CONFIG_IEEE1394_EXTRA_CONFIG_ROMS=y
CONFIG_IEEE1394_CONFIG_ROM_IP1394=y

CONFIG_IEEE1394_OHCI1394=m

CONFIG_IEEE1394_VIDEO1394=m
CONFIG_IEEE1394_SBP2=m
CONFIG_IEEE1394_ETH1394=m
CONFIG_IEEE1394_DV1394=m
CONFIG_IEEE1394_RAWIO=m
CONFIG_IEEE1394_CMP=m
CONFIG_IEEE1394_AMDTP=m


CONFIG_NET=y

CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_SYN_COOKIES=y

CONFIG_NETFILTER=y

CONFIG_IP_NF_CONNTRACK=m
CONFIG_IP_NF_FTP=m
CONFIG_IP_NF_IRC=m
CONFIG_IP_NF_TFTP=m
CONFIG_IP_NF_AMANDA=m
CONFIG_IP_NF_QUEUE=m
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_LIMIT=m
CONFIG_IP_NF_MATCH_IPRANGE=m
CONFIG_IP_NF_MATCH_MAC=m
CONFIG_IP_NF_MATCH_PKTTYPE=m
CONFIG_IP_NF_MATCH_MARK=m
CONFIG_IP_NF_MATCH_MULTIPORT=m
CONFIG_IP_NF_MATCH_TOS=m
CONFIG_IP_NF_MATCH_RECENT=m
CONFIG_IP_NF_MATCH_ECN=m
CONFIG_IP_NF_MATCH_DSCP=m
CONFIG_IP_NF_MATCH_AH_ESP=m
CONFIG_IP_NF_MATCH_LENGTH=m
CONFIG_IP_NF_MATCH_TTL=m
CONFIG_IP_NF_MATCH_TCPMSS=m
CONFIG_IP_NF_MATCH_HELPER=m
CONFIG_IP_NF_MATCH_STATE=m
CONFIG_IP_NF_MATCH_CONNTRACK=m
CONFIG_IP_NF_MATCH_OWNER=m
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
CONFIG_IP_NF_NAT=m
CONFIG_IP_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=m
CONFIG_IP_NF_TARGET_REDIRECT=m
CONFIG_IP_NF_TARGET_NETMAP=m
CONFIG_IP_NF_TARGET_SAME=m
CONFIG_IP_NF_NAT_LOCAL=y
CONFIG_IP_NF_NAT_SNMP_BASIC=m
CONFIG_IP_NF_NAT_IRC=m
CONFIG_IP_NF_NAT_FTP=m
CONFIG_IP_NF_NAT_TFTP=m
CONFIG_IP_NF_NAT_AMANDA=m
CONFIG_IP_NF_MANGLE=m
CONFIG_IP_NF_TARGET_TOS=m
CONFIG_IP_NF_TARGET_ECN=m
CONFIG_IP_NF_TARGET_DSCP=m
CONFIG_IP_NF_TARGET_MARK=m
CONFIG_IP_NF_TARGET_CLASSIFY=m
CONFIG_IP_NF_TARGET_LOG=m
CONFIG_IP_NF_TARGET_ULOG=m
CONFIG_IP_NF_TARGET_TCPMSS=m
CONFIG_IP_NF_ARPTABLES=m
CONFIG_IP_NF_ARPFILTER=m
CONFIG_IP_NF_ARP_MANGLE=m
CONFIG_IP_NF_TARGET_NOTRACK=m
CONFIG_IP_NF_RAW=m



CONFIG_IRDA=m

CONFIG_IRLAN=m
CONFIG_IRNET=m
CONFIG_IRCOMM=m
CONFIG_IRDA_ULTRA=y

CONFIG_IRDA_CACHE_LAST_LSAP=y
CONFIG_IRDA_FAST_RR=y
CONFIG_IRDA_DEBUG=y


CONFIG_IRTTY_SIR=m


CONFIG_IRPORT_SIR=m


CONFIG_NSC_FIR=m
CONFIG_BT=m

CONFIG_BT_HCIUSB=m
CONFIG_BT_HCIUART=m
CONFIG_BT_HCIDTL1=m
CONFIG_BT_HCIBT3C=m
CONFIG_BT_HCIBLUECARD=m
CONFIG_BT_HCIBTUART=m
CONFIG_NETDEVICES=y


CONFIG_NET_ETHERNET=y
CONFIG_MII=m

CONFIG_NET_PCI=y
CONFIG_B44=m




CONFIG_NET_RADIO=y





CONFIG_NET_WIRELESS=y


CONFIG_PPP=m
CONFIG_PPP_FILTER=y
CONFIG_PPP_ASYNC=m
CONFIG_PPP_SYNC_TTY=m
CONFIG_PPP_DEFLATE=m
CONFIG_PPP_BSDCOMP=m
CONFIG_PPPOE=m



CONFIG_INPUT=y

CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1400
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=1050
CONFIG_INPUT_EVDEV=y

CONFIG_SOUND_GAMEPORT=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y

CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=m
CONFIG_INPUT_MISC=y
CONFIG_INPUT_PCSPKR=m
CONFIG_INPUT_UINPUT=m

CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y

CONFIG_SERIAL_8250=m
CONFIG_SERIAL_8250_NR_UARTS=4

CONFIG_SERIAL_CORE=m
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
CONFIG_PRINTER=y


CONFIG_RTC=y

CONFIG_AGP=y
CONFIG_AGP_INTEL=y
CONFIG_DRM=y
CONFIG_DRM_RADEON=y


CONFIG_I2C=y

CONFIG_I2C_ALGOBIT=y







CONFIG_FB=y
CONFIG_VIDEO_SELECT=y
CONFIG_FB_RADEON=y
CONFIG_FB_RADEON_I2C=y

CONFIG_VGA_CONSOLE=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_PCI_CONSOLE=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y

CONFIG_LOGO=y
CONFIG_LOGO_LINUX_CLUT224=y

CONFIG_SOUND=m


CONFIG_SOUND_PRIME=m
CONFIG_SOUND_ICH=m

CONFIG_USB=m

CONFIG_USB_DEVICEFS=y

CONFIG_USB_EHCI_HCD=m
CONFIG_USB_EHCI_ROOT_HUB_TT=y
CONFIG_USB_OHCI_HCD=m
CONFIG_USB_UHCI_HCD=m


CONFIG_USB_PRINTER=m
CONFIG_USB_STORAGE=m

CONFIG_USB_HID=m
CONFIG_USB_HIDINPUT=y
CONFIG_USB_HIDDEV=y







CONFIG_USB_SERIAL=m
CONFIG_USB_SERIAL_VISOR=m
CONFIG_USB_SERIAL_MCT_U232=m



CONFIG_EXT2_FS=y
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_JBD=y
CONFIG_FS_MBCACHE=y
CONFIG_REISERFS_FS=y
CONFIG_XFS_FS=y
CONFIG_MINIX_FS=m

CONFIG_ISO9660_FS=m
CONFIG_JOLIET=y
CONFIG_UDF_FS=m

CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_NTFS_FS=m

CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_SYSFS=y
CONFIG_TMPFS=y
CONFIG_RAMFS=y


CONFIG_NFS_FS=m
CONFIG_NFS_V3=y
CONFIG_NFSD=m
CONFIG_NFSD_V3=y
CONFIG_LOCKD=m
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=m
CONFIG_SUNRPC=m
CONFIG_SMB_FS=m
CONFIG_SMB_NLS_DEFAULT=y
CONFIG_SMB_NLS_REMOTE="cp437"
CONFIG_CIFS=m

CONFIG_MSDOS_PARTITION=y

CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-15"
CONFIG_NLS_CODEPAGE_437=m
CONFIG_NLS_CODEPAGE_850=m
CONFIG_NLS_ISO8859_1=m
CONFIG_NLS_ISO8859_15=m
CONFIG_NLS_UTF8=m


CONFIG_DEBUG_KERNEL=y
CONFIG_EARLY_PRINTK=y
CONFIG_MAGIC_SYSRQ=y



CONFIG_CRC32=m
CONFIG_ZLIB_INFLATE=m
CONFIG_ZLIB_DEFLATE=m
CONFIG_X86_BIOS_REBOOT=y
CONFIG_X86_STD_RESOURCES=y
CONFIG_PC=y

Re: [2.6.6] Synaptics driver is 'jumpy'

[Dmitry Torokhov]

On Monday 17 May 2004 01:32 am, Jan De Luyck wrote:
> On Sunday 16 May 2004 21:29, Dmitry Torokhov wrote:
> > On Sunday 16 May 2004 02:06 pm, Jan De Luyck wrote:
> > > On Sunday 16 May 2004 19:18, Dmitry Torokhov wrote:
> > > > Hmm.. there was no changes to PS/2 processing between 2.6.5 and 2.6.6
> > > > except for some Logitech tweaking, but it should not affect Synaptics
> > > > handling in any way...
> > > >
> > > > Could you check if you still have DMA enabled on your disks, check your
> > > > time source (TSC, ACPI PM timer, etc) and probably boot with acpi off?
> > > >
> > > > Thank you.
> > >
> > > Dmitry,
> > >
> > > Booting with acpi=off fixes the problem, although I'm curious to what the
> > > problem actually is.
> > >
> > > I've attached the dmesgs from 2.6.6, 2.6.5, and 2.6.6 with acpi=off.
> > >
> > > There is a line that says "Invalid control registers" that I wonder where
> > > it comes from, but you might see something more here than I do.
> >
> > It comes from speedstep-centrino module, could you please try booting with
> > ACPI but without speedstep-centrino loaded? Also, does it help if you do
> > not compile/ load ACPI battery module?
> 
> Neither has any effect.
> 
> I've also disabled CONFIG_X86_SPEEDSTEP_CENTRINO_ACPI, figuring there might be
> some problem with that, but that doesn't change a thing.
>

Perhaps we need to check with ACPI guys as it seems that you are affected by
this code and there were some changes to ACPI subsystem between 2.6.5 and 2.6.6.

> Also, I'm wondering if there's any point in using the CONFIG_X86_PM_TIMER
> timesource?
>

It is supposed to be unaffected by frequency changes which is a good thing. I am
running with it, but I think I've seen couple of reports that it caused time go
twice as fast.
 
-- 
Dmitry

Re: [2.6.6] Synaptics driver is 'jumpy'

[Jan De Luyck]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 17 May 2004 08:42, Dmitry Torokhov wrote:
> On Monday 17 May 2004 01:32 am, Jan De Luyck wrote:
> > On Sunday 16 May 2004 21:29, Dmitry Torokhov wrote:
> > > On Sunday 16 May 2004 02:06 pm, Jan De Luyck wrote:
> > > > On Sunday 16 May 2004 19:18, Dmitry Torokhov wrote:
> > > > > Hmm.. there was no changes to PS/2 processing between 2.6.5 and
> > > > > 2.6.6 except for some Logitech tweaking, but it should not affect
> > > > > Synaptics handling in any way...
> > > > >
> > > > > Could you check if you still have DMA enabled on your disks, check
> > > > > your time source (TSC, ACPI PM timer, etc) and probably boot with
> > > > > acpi off?
> > > > >
> > > > > Thank you.
> > > >
> > > > Dmitry,
> > > >
> > > > Booting with acpi=off fixes the problem, although I'm curious to what
> > > > the problem actually is.
> > > >
> > > > I've attached the dmesgs from 2.6.6, 2.6.5, and 2.6.6 with acpi=off.
> > > >
> > > > There is a line that says "Invalid control registers" that I wonder
> > > > where it comes from, but you might see something more here than I do.
> > >
> > > It comes from speedstep-centrino module, could you please try booting
> > > with ACPI but without speedstep-centrino loaded? Also, does it help if
> > > you do not compile/ load ACPI battery module?
> >
> > Neither has any effect.
> >
> > I've also disabled CONFIG_X86_SPEEDSTEP_CENTRINO_ACPI, figuring there
> > might be some problem with that, but that doesn't change a thing.
>
> Perhaps we need to check with ACPI guys as it seems that you are affected
> by this code and there were some changes to ACPI subsystem between 2.6.5
> and 2.6.6.

Ok. Passing on to acpi-devel@lists.sourceforge.net.

I've looked in the archives, and the problem looks very much like the one in 
this thread:

http://sourceforge.net/mailarchive/forum.php?thread_id=4172848&forum_id=6102

And I've been noticing some keyboard glitches too, but these were to 
unfrequent, and usually occur only in one application (gaim) so I figured it 
might be a bug in gaim... guess not...

Unfortunately, the hints in this thread don't help. I've browsed the input 
system FAQ, but no dice.

The only thing that gives me a working synaptics touchpad is acpi=off.

It worked fine with 2.6.5.

Jan

- -- 
Those who do things in a noble spirit of self-sacrifice are to be avoided
at all costs.
		-- N. Alexander.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFAqGP3UQQOfidJUwQRAoXUAJ9nKMmfc6x72u3nJbJl+PZi3q0U3QCeO8N5
+KJEgm5HKq+gwOAh7A/Z3cA=
=ONlN
-----END PGP SIGNATURE-----

Re: Re: [2.6.6] Synaptics driver is 'jumpy'

[Karl Hegbloom]

Re:
http://sourceforge.net/mailarchive/forum.php?thread_id=4172848&forum_id=6102

A BIOS upgrade from the laptop manufacturer has cured the problem
entirely.  I am now able to run the battery monitor with no effect on
keyboard or touchpad pointer.  I don't know what they changed, but
whatever it was, it's fixed now.  I suppose that it could be a change to
the Linux ACPI code that fixed it, but I suspect it was the BIOS update.
It's a "you tell me and we'll both know" situtation -- I've only just
begun learning about the internals of how ACPI works.

-- 
Karl Hegbloom <hegbloom-tbDHPZwbsQQ@public.gmane.org>



-------------------------------------------------------
This SF.Net email is sponsored by: SourceForge.net Broadband
Sign-up now for SourceForge Broadband and get the fastest
6.0/768 connection for only $19.95/mo for the first 3 months!
http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click