public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: teunis <teunis@wintersgift.com>
To: linux-kernel@vger.kernel.org
Subject: various laptop nagles - any suggestions?   (note: 2.6.19-rc2-mm1 but applies to multiple kernels)
Date: Thu, 19 Oct 2006 09:05:49 -0700	[thread overview]
Message-ID: <4537A25D.6070205@wintersgift.com> (raw)

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

Setting the internal clock to 100 Hz stablizes the laptop - and the
synaptics touchpad stops "crashing"  (when "crashed" the pad reads out
all kinds of seemingly random values).   I would suspect the driver
needs adjusting for the variable clock.   Also - it's definitely nicer
on the laptop power use as far as I can tell - should this be in the
documentation?

I'm very grateful that compact flash-based booting on a SATA system
works well.   It hasn't been so reliable in 2.6.19-rc2-mm1 for IDE/CF
adaptors but I haven't yet solved why.   (tested with various laptops)

resume from "suspend to ram" (ACPI S3 mode) - the keyboard and mouse do
not recover on 945G chipset.   Note that otherwise the chipset works
well in 2.6.19-rc2-mm1 - and this is the first kernel that does work well).

LVM2 - when adding and removing physical volumes (again, on Compact
Flash cards via USB and Firewire adaptors) - it doesn't always remove
the volume properly (pvremove /dev/sda or equiv) from the device-mapper.
 This leaves me unable to plug in another.   I suspect this to be an
LVM2 problem (no hotplug?) rather than a compact flash or SCSI problem.

I would debug - but I'm not yet sure where to begin.   Feel free to
offer suggestions (to my mailbox directly - I've waited for two weeks to
post as I don't want to add noise to the kernel list)

oh - my job involves working with these systems
Thank you for everything!
	- Teunis Peters
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFN6JcbFT/SAfwLKMRAkDeAJ94FC1Zy0mS+y4jXpNHGSPIpGvc2QCfYl+D
oxLqfgqj0GUKOD/7iRXUPfs=
=6Gjc
-----END PGP SIGNATURE-----

             reply	other threads:[~2006-10-19 16:06 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-19 16:05 teunis [this message]
2006-10-20  2:41 ` various laptop nagles - any suggestions? (note: 2.6.19-rc2-mm1 but applies to multiple kernels) Andrew Morton
2006-10-20 16:30   ` teunis
2006-10-20 18:07     ` Andrew Morton
2006-10-20 18:13       ` Thomas Gleixner
2006-10-20 18:26         ` Andrew Morton
2006-10-20 18:37           ` Thomas Gleixner
2006-10-20 18:46           ` Thomas Gleixner
2006-10-20 19:15             ` Andrew Morton
2006-10-20 20:37               ` Ingo Molnar
2006-10-20 20:54                 ` Andrew Morton
2006-10-20 20:56                   ` Ingo Molnar
2006-10-21  1:25                     ` Andrew Morton
2006-10-21  9:49                       ` Thomas Gleixner
2006-10-22 21:22                         ` Thomas Gleixner
2006-11-08  7:19                           ` Andrew Morton
2006-11-08 22:28                             ` Thomas Gleixner
2006-10-21 14:52           ` Arjan van de Ven
2006-10-20 19:13       ` Dmitry Torokhov
2006-10-20 22:26         ` teunis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4537A25D.6070205@wintersgift.com \
    --to=teunis@wintersgift.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox