Problem changing monitor and mouse

[Fabio Massimo Di Nitto]

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

John wrote:

| Other times when I've had the mouse definition wrong, the mouse moved
| arratically. This time it didn't move at all.
|

It can happen that too if the protocol are way too different.


|>
|> I think we have been discussing this issue already once.
|> If something works for you, it does _not_ mean it works for everybody.
|
|
|
| Nore are we discussing everybody. I'm pretty sure I tried the info
| ddcprobe gave me - I useually do when there is a problem - but if
| ddcprobe can find it, I shouldn't need to specify it all.

I think you keep missing the point. ddcprobe does nothing more of what the X
driver does.

Both of them do a probe to the monitor.

If there are information back from the monitor it is good, but if there are none,
the 2 entries in the config will tell the driver: "Hey don't exceed this values!"
otherwise the driver will simply not know what to do.

What you are asking is simply impossible and the reason why we set sensible
(and more or less standard defaults) is to avoid to fry old monitors that
do not provide ddc information to the driver. And i am myself owner of such
pieces of hardware.

Now, since nobody wants to take a chance to kill somebody else monitor, i much rather
prefer to set this value and sleep quite at night, than having somebody knocking
on my door because his flat screen burned.

If you are aware that all your hardware can sustain certain configuration. you
are welcome to set them as such.

|>
|> |
|> | Had I done a fresh install it would almost certainly worked, and worked
|> | without me answering lots of Qs I should have to.
|> |
|> | Years ago, when RHL 7.2 was current I was changing monitors regularly -
|> | old ones too - and RHL reconfigured  automatically.
|> |
|> | Ditto with mice.
|> |
|>
|> The todo list hasn't changed.
|
|
| todo list?
| Getting this right should be on the done list:-((

How would you implement it?

A lot of people are worried about linux taking too long to boot.
How would you reconciliate another system probe during boot (that btw in certain
situation CAN hang your system) with the boot time?

If the user customizes the configuration, the probing system isn't allowed to
touch the config anymore. (Golden rule: always respect user changes)

How would you handle this?
This is a typical a non win to win situation. 50% of the people wants the configuration
automagically regenerated even with custom settings (how if changes are clashing?), the
other 50% will want it untouched. Considering all of this should be done automagically..
what path would you choose?

Also.. if the system is a remote system and it gets hardware changes.. you need
to teach the admin that it needs a flag to disable hardware probing otherwise
the machine will never come up again.

Whilst it looks like a simple thing to do, it involves a lot of different aspects
and a bit of design that simply takes time to decide and to implement to get it right.

Fabio

- --
Self-Service law:
The last available dish of the food you have decided to eat, will be
inevitably taken from the person in front of you.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iQIVAwUBQZxbwFA6oBJjVJ+OAQJA9BAAtV9yVcX24qceTgPjLq5DQUKq2sUff2NY
b+HtjoVD4RQ8d9SxN/1zBayzUHTpXqbJI5i4aBvfuf8mePaggddf/a8xmE9LzKIO
N8HS73h6SM7s11i6O1KqhWMa/iZdJPf4yOPteync64jqwMwehmWYqofehzy+wbE1
58bHlXJ3c4QP8QlvbWgIfo7EKg1yqgOtxtERhvxDWhZgLu/hJpMkBaqZgk+459Bw
Q13C9oEwWY8ENHg/Y3qI4KYQD0XPfIdyPhR9tg9ptZ9VT1oGZOtDbv9fARR1x+FJ
ALlnl0bJepOqPOvJqFfqJn1P2KLt8u7hMSAE3AtLavstkQg/+InKUXNhF/rmqlmf
dVqOFj0qe6LwQjmhRI2iYRS+zyUewUuNYFQT5kuVbDEKq5rUuQXiuD/oog7meuS5
WKM6pnGEROBfwBW+aciKqc6fQimeKI8bF9pgiPTWlRy/8Q+xLayaeMZYZeCZ661s
ncM11rMXUHKONGsMh60mj1Vc9OT/ujqOrqVkx4bsxoB0nzQiqhAGR2m8vZV64tMh
4RRU34+sQzITsVZJMXnpQIOTPxcF7kyXZGVSKJR2xZVOeQGvzf5wsPjURmluHSW4
3xPI686KF8Mc47CI4Fj57SeQIb8ULio4712F0FIVOrWsZKgLQFgvvf7VTT+r/vQ3
Y02k3naZTAE=
=Gk/m
-----END PGP SIGNATURE-----