no keyborad with xorg on Pismo/unstable
Hi, I updated and migrated from xfree86 to xorg on my unstable Pismo. But I'm not able to keep a working keyboard similar with mac layout. The generated xorg.conf contains: Section InputDevice Identifier Generic Keyboard Driver keyboard Option CoreKeyboard Option XkbRules xfree86 Option XkbModel macintosh Option XkbLayout fr_new Option XkbOptionsctrl:nocaps EndSection (fr_new comes from http://www.linux-france.org/macintosh/clavier_v4.html) All attempts I made to change this setting leads to a non working keyboad in Gnome. Currently I'm writing from Xfe where I get a keyboard working, though without any accentuated chars. I don't get the pipe neither :/ Anyone already experienced an xorg switch on an old pwb with adb kbd ? -- Jean-Christophe Michel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: no keyborad with xorg on Pismo/unstable
(fr_new comes from http://www.linux-france.org/macintosh/clavier_v4.html) All attempts I made to change this setting leads to a non working keyboad in Gnome. Currently I'm writing from Xfe where I get a keyboard working, though without any accentuated chars. I don't get the pipe neither :/ Anyone already experienced an xorg switch on an old pwb with adb kbd ? Etienne (CC'd) has a working french keymap for X.org Ben. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: no keyborad with xorg on Pismo/unstable
On Tue, May 02, 2006 at 11:02:30PM +1000, Benjamin Herrenschmidt wrote: (fr_new comes from http://www.linux-france.org/macintosh/clavier_v4.html) All attempts I made to change this setting leads to a non working keyboad in Gnome. Currently I'm writing from Xfe where I get a keyboard working, though without any accentuated chars. I don't get the pipe neither :/ Anyone already experienced an xorg switch on an old pwb with adb kbd ? Etienne (CC'd) has a working french keymap for X.org I had the same problem on my spanish keyboard. Actually all keys work except the alphabetic ones, which is only about a quarter of the keys on my 108 key Apple Pro keyboard, but letters are somewhat important :-) One possible solution is that in /usr/share/X11/xkb/rules/xfree86, the line: $mac $macvendorlayouts = pc(pc105)+macintosh_vndr/%l%(v) should actually insert +macintosh_vndr/us(extended) before the last item. Another solution is to make the country specific files include some latin map (latin4 for Spain as done for the PC maps, I don't know for France). In macintosh_vndr/es it is explictly stated that it only describes the differences between american and spanish keyboards. And even that is wrong, it actually is a latin-american keyboard (latam for Debian, la for X.org AFAIR since la is now laotian in Debian). European spanish keyboards are completely different when it comes to punctuation and non-alphabetic symbols. This said, there are so many differences between Xorg and Debian source packages when it comes to keyboard description that I don't really know where to report these bugs. Regards, Gabriel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: no keyborad with xorg on Pismo/unstable
On Tue, 2006-05-02 at 15:30 +0200, Gabriel Paubert wrote: This said, there are so many differences between Xorg and Debian source packages when it comes to keyboard description that I don't really know where to report these bugs. There are differences between xkb-data (built from the source package xkeyboard-config) and xkeyboard-config upstream? If so, the bug should go to Debian, otherwise, upstream may be better, but Denis Barbier is pretty good at dealing with bug reports and forwarding them upstream as necessary anyway. Hope this helps, -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
Re: [PATCH] via-pmu: report powerbutton as proper input event
No. I don't see why his posting here should be something development *only* related. The patch obviously can be *used* and tested. I'm glad he posted it here: IINM it's a ppc patch, and I have good use for it for my self-compiled kernels .. :) The argument is that even that doesn't belong here since it is clearly not debian related. I agree, but we don't have a good linuxppc-users list that covers distribution-independent stuff, so we tend to abuse this one (see all the posts by ubuntu and sometimes gentoo users). Seconded. On top of that, I just figured my linuxppc-dev subscription lapsed for some reason ... Please keep cc:'ing debian-powerpc on relevant patches. Subject prefix like [linuxppc-dev] should be suitable for filtering. Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: no keyborad with xorg on Pismo/unstable
On 5/2/06, Jean-Christophe Michel [EMAIL PROTECTED] wrote: Hi, I updated and migrated from xfree86 to xorg on my unstable Pismo. But I'm not able to keep a working keyboard similar with mac layout. The generated xorg.conf contains: Section InputDevice Identifier Generic Keyboard Driver keyboard Option CoreKeyboard Option XkbRules xfree86 Option XkbModel macintosh Option XkbLayout fr_new Option XkbOptionsctrl:nocaps EndSection (fr_new comes from http://www.linux-france.org/macintosh/clavier_v4.html) All attempts I made to change this setting leads to a non working keyboad in Gnome. Currently I'm writing from Xfe where I get a keyboard working, though without any accentuated chars. I don't get the pipe neither :/ Anyone already experienced an xorg switch on an old pwb with adb kbd ? I had a similar problem on my ibook after upgrade from xorg6 to xorg7. I had to copy fr_new to /usr/share/X11/xkb/symbols/macintosh_vndr/fr. Using the name fr_new didn't work. My config : Section InputDevice Identifier Generic Keyboard Driver kbd Option CoreKeyboard Option XkbRulesxorg Option XkbModelmacintosh Option XkbLayout fr EndSection Regards, Bin -- Jean-Christophe Michel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: no keyborad with xorg on Pismo/unstable
Hi, Bin Zhang wrote: Anyone already experienced an xorg switch on an old pwb with adb kbd ? I had a similar problem on my ibook after upgrade from xorg6 to xorg7. I had to copy fr_new to /usr/share/X11/xkb/symbols/macintosh_vndr/fr. Using the name fr_new didn't work. My config : Section InputDevice IdentifierGeneric Keyboard Driverkbd OptionCoreKeyboard OptionXkbRulesxorg OptionXkbModelmacintosh OptionXkbLayoutfr EndSection Many thanks ! very good advice, it works now: éà|\ ! I digged into this for some hours without any result :/ I didn't find any doc about the place where kbds were placed; I thought they were in /etc/x11/xkb/symbols/macintosh :( The driver name changed from keyboard to kbd too. Why was there no warning in paquet install ? :(( -- Jean-Christophe Michel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
[RFC][Patch] Cirumvent appletouch fuzziness
Hi!
I frequently experience problems with the fuzziness of the touchpad
in my iBook, using the appletouch driver. From time to time the
pointer jumps around and clicks randomly and the touchpad becomes
unusable. The only way out is to reload the appletouch module.
Digging around in the appletouch sources, the problems seems to be
that the accumulated xy values increase over time (due to temperature
changes, sweat, or whatever reason ;-) ), eventually become bigger
than ATP_THRESHOLD and start to influence the pointer position.
Now, two main solution ideas come into my mind:
1) Increase ATP_THRESHOLD. This turns out to be a bad idea, as it
mainly just delays the effect and moreover badly affects fine
pointer-movements.
2) Counteract the slow growth of xy_acc. See appended patch for an
implementation of this idea. The values of xy_acc are slowly decreased
if they are under a certain threshold. To avoid decreasing real
values in xy_acc (i.e. values which are actually the result of a
finger on the touchpad, and not some fuzziness problem) big values
(which are more likely caused by some finger) are decreased slowly,
small values (which more probably result from fuzziness) are decreased
a bit faster.
So, some questions for you guys: I have never read a report on this
fuzziness problem. Am I the only one experiencing it? If yes, forget
about my patch, as I'd probably be the only happy user of it. ;)
The current patch should probably be called ugly but effective: it
kind of helps, but I guess there are better ways to implement this.
So, if someone comes up with some better algorithmic idea, let me
know.
Cheers,
Sven
--- linux-2.6.17-rc3.orig/drivers/usb/input/appletouch.c 2006-03-20 06:53:29.0 +0100
+++ linux-2.6.17-rc3/drivers/usb/input/appletouch.c 2006-05-02 18:49:31.0 +0200
@@ -99,7 +99,10 @@ MODULE_DEVICE_TABLE (usb, atp_table);
* Threshold for the touchpad sensors. Any change less than ATP_THRESHOLD is
* ignored.
*/
-#define ATP_THRESHOLD 5
+#define ATP_THRESHOLD 3
+
+#define ATP_SHRINK_THRESHOLD 20
+#define ATP_SHRINK_PENALTY_THRESHOLD 375 * (ATP_SHRINK_THRESHOLD - 1)
/* Structure to hold all of our device specific stuff */
struct atp {
@@ -118,6 +121,8 @@ struct atp {
signed char xy_old[ATP_XSENSORS + ATP_YSENSORS];
/* accumulated sensors */
int xy_acc[ATP_XSENSORS + ATP_YSENSORS];
+ /* penalty values for shrinking */
+ int xy_shrink[ATP_XSENSORS + ATP_YSENSORS];
int overflowwarn; /* overflow warning printed? */
int datalen; /* size of an USB urb transfer */
};
@@ -297,6 +302,23 @@ static void atp_complete(struct urb* urb
/* prevent down drifting */
if (dev-xy_acc[i] 0)
dev-xy_acc[i] = 0;
+
+ /* Fix fuzziness. If a value in xy_acc is less than ATP_SHRINK_THRESHOLD
+ * long enough to let the shrinking penalty grow beyond
+ * ATP_SHRINK_PENALTY_THRESHOLD, decrease that value in xy_acc.
+ */
+ if ((dev-xy_acc[i] 0) (dev-xy_acc[i] ATP_SHRINK_THRESHOLD ))
+ {
+ dev-xy_shrink[i] += ATP_SHRINK_THRESHOLD - dev-xy_acc[i];
+ if (dev-xy_shrink[i] = ATP_SHRINK_PENALTY_THRESHOLD)
+ {
+dev-xy_shrink[i] = 0;
+dev-xy_acc[i]--;
+printk(appletouch: trying to fix fuzziness. changed xy_acc[%d]: %d\n, i, dev-xy_acc[i]);
+ }
+ } else {
+ dev-xy_shrink[i] = 0;
+ }
}
memcpy(dev-xy_old, dev-xy_cur, sizeof(dev-xy_old));
Re: no keyborad with xorg on Pismo/unstable
On 5/2/06, Jean-Christophe Michel [EMAIL PROTECTED] wrote: Hi, Bin Zhang wrote: Anyone already experienced an xorg switch on an old pwb with adb kbd ? I had a similar problem on my ibook after upgrade from xorg6 to xorg7. I had to copy fr_new to /usr/share/X11/xkb/symbols/macintosh_vndr/fr. Using the name fr_new didn't work. My config : Section InputDevice IdentifierGeneric Keyboard Driverkbd OptionCoreKeyboard OptionXkbRulesxorg OptionXkbModelmacintosh OptionXkbLayoutfr EndSection Many thanks ! very good advice, it works now: éà|\ ! I digged into this for some hours without any result :/ I didn't find any doc about the place where kbds were placed; I thought they were in /etc/x11/xkb/symbols/macintosh :( Yes. It was used by package xlibs. I found the new place /usr/share/X11/xkb/symbols/macintosh_vndr/ by using package contents search: http://packages.debian.org/cgi-bin/search_contents.pl?word=frsearchmode=searchfilescase=insensitiveversion=unstablearch=powerpc The new package is xkb-data. Bin The driver name changed from keyboard to kbd too. Why was there no warning in paquet install ? :(( -- Jean-Christophe Michel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [RFC][Patch] Cirumvent appletouch fuzziness
Hi, On 5/2/06, Stelian Pop [EMAIL PROTECTED] wrote: Le mardi 02 mai 2006 à 18:52 +0200, Sven Henkel a écrit : Hi! I frequently experience problems with the fuzziness of the touchpad in my iBook, using the appletouch driver. From time to time the pointer jumps around and clicks randomly and the touchpad becomes unusable. The only way out is to reload the appletouch module. Digging around in the appletouch sources, the problems seems to be that the accumulated xy values increase over time (due to temperature changes, sweat, or whatever reason ;-) ), eventually become bigger than ATP_THRESHOLD and start to influence the pointer position. Hmm, xy_acc should be reset to 0 each time you stop touching the pad. You do raise your finger from the pad once in a while, don't you ? :) Heh, yes :) But that's exactly my problem: xy_acc _should_ be all zeros when there's no finger on the touchpad, but from time to time some entries in it grow to values 0, and even ATP_THRESHOLD. So, when I use the touchpad in such a failure scenario, it looks to the appletouch driver as if I had two fingers on the touchpad (one caused by me, the other one by the failures in xy_acc). Hence moving the pointer becomes quite ugly and taps result in the wrong mouse-buttons. Now, two main solution ideas come into my mind: 1) Increase ATP_THRESHOLD. This turns out to be a bad idea, as it mainly just delays the effect and moreover badly affects fine pointer-movements. 2) Counteract the slow growth of xy_acc. See appended patch for an implementation of this idea. The values of xy_acc are slowly decreased if they are under a certain threshold. To avoid decreasing real values in xy_acc (i.e. values which are actually the result of a finger on the touchpad, and not some fuzziness problem) big values (which are more likely caused by some finger) are decreased slowly, small values (which more probably result from fuzziness) are decreased a bit faster. So, some questions for you guys: I have never read a report on this fuzziness problem. Am I the only one experiencing it? If yes, forget about my patch, as I'd probably be the only happy user of it. ;) Do you use the synaptics X driver ? Yes. I think most of the appletouch users (including me) use it exclusively through the synaptics driver, which applies extra algorithms for fuzz and acceleration detection. Maybe you don't, and this could be a part of the explanation. Well, unfortunately not. I suspect that I'm the proud owner of an extremly sensitive touchpad. Note that I'm seeing the very same problem under MacOS from time to time: Eventually moving the pointer becomes impossible, but the MacOS driver usually recovers after a few seconds. Imho, the linux appletouch driver is currently missing such a recovery mechanism. Cheers, Sven
Re: [RFC][Patch] Cirumvent appletouch fuzziness
Hello Sven, Sven Henkel [EMAIL PROTECTED] wrote: So, some questions for you guys: I have never read a report on this fuzziness problem. Am I the only one experiencing it? If yes, forget about my patch, as I'd probably be the only happy user of it. ;) I would say yes. I've this problem, too. Mainly while charging the pointer jumps around when I hit on the trackpad. Bye, Jörg. -- Diskusion Pascal vs. Rest der Welt: 30 Aug 2000 00:13:11 GMT, Adrian Knoth [EMAIL PROTECTED] Und selbst wenn eure 10 Zeilen-Programme noch so oft unter Windows verwendet werden: mit einem Handwagen fährt man nicht Formel-1. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
New miboot-enabled d-i daily builds set up
Hi, I've set up miboot-enabled daily builds of d-i powerpc floppies, to go with my normal daily builds: http://people.debian.org/~cjwatson/d-i/powerpc-miboot/ Thanks to Sven Luther for the miboot package used to build these. Let me know if there are any problems; I haven't been able to test them myself. Cheers, -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: New miboot-enabled d-i daily builds set up
Colin Watson wrote: Hi, I've set up miboot-enabled daily builds of d-i powerpc floppies, to go with my normal daily builds: http://people.debian.org/~cjwatson/d-i/powerpc-miboot/ Thanks to Sven Luther for the miboot package used to build these. Let me know if there are any problems; sorry , boot.img can't change the initial gui to console. tested on 7200/90 regards, eugen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [RFC][Patch] Cirumvent appletouch fuzziness
On Tuesday 02 May 2006 23:58, Jörg Sommer wrote: Hello Sven, Sven Henkel [EMAIL PROTECTED] wrote: So, some questions for you guys: I have never read a report on this fuzziness problem. Am I the only one experiencing it? If yes, forget about my patch, as I'd probably be the only happy user of it. ;) I would say yes. I've this problem, too. Mainly while charging the pointer jumps around when I hit on the trackpad. This is very annoying, and renders tap unusable. Børge
Sound on newer PB
Hi. Finaly got the Ben Collins Ubunu kernel patch to work. It patches from 2.6.15 and up, but does only work with 2.6.17-rc3 and up and with alsa 1.0.11 on the PB5,7. Toonie is also fixed in 1.0.11 debian package of alsa-utils. However when I play a movie, sound output is reduced to: 1. Through ARTS it plays ok the first few seconds after a pause, then scrambles, volume sliders does not change volume. This is strange since music does not summon this behavior. 2. ALSA (and OSS emu output) does not scramble but rather makes it sound like played through a thincan. Anyone got a clue on this? Børge
Re: [PATCH] via-pmu: report powerbutton as proper input event
On Tue, 2006-05-02 at 17:30 +0200, Michael Schmitz wrote: No. I don't see why his posting here should be something development *only* related. The patch obviously can be *used* and tested. I'm glad he posted it here: IINM it's a ppc patch, and I have good use for it for my self-compiled kernels .. :) The argument is that even that doesn't belong here since it is clearly not debian related. I agree, but we don't have a good linuxppc-users list that covers distribution-independent stuff, so we tend to abuse this one (see all the posts by ubuntu and sometimes gentoo users). Seconded. On top of that, I just figured my linuxppc-dev subscription lapsed for some reason ... Maybe you didn't follow when it moved over to ozlabs.org ? :) Please keep cc:'ing debian-powerpc on relevant patches. Subject prefix like [linuxppc-dev] should be suitable for filtering. Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: The powerpc port should be removed from etch release candidates ...
Its not a mkvmlinuz problem, the problem is in the kernel itself, and will probably be fixed for 2.6.17. I am watching this, and will try to do a backport if something promising comes on. Not sure i will have the time to fix it myself though. Prep has been relegated to an embedded platform that builds only in arch/ppc for now. It should still work there though. We might move it over to powerpc one day... Ben. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: [RFC][Patch] Cirumvent appletouch fuzziness
On Tue, 2006-05-02 at 23:14 +0200, Sven Henkel wrote: Heh, yes :) But that's exactly my problem: xy_acc _should_ be all zeros when there's no finger on the touchpad, but from time to time some entries in it grow to values 0, and even ATP_THRESHOLD. So, when I use the touchpad in such a failure scenario, it looks to the appletouch driver as if I had two fingers on the touchpad (one caused by me, the other one by the failures in xy_acc). Hence moving the pointer becomes quite ugly and taps result in the wrong mouse-buttons. I think this actually happens when you *don't* touch the touchpad for quite a while. I've seen it happen too, will have to test your patch though. johannes signature.asc Description: This is a digitally signed message part
Re: Sound on newer PB
Hi, It patches from 2.6.15 and up, but does only work with 2.6.17-rc3 and up and with alsa 1.0.11 on the PB5,7. Anyone got a clue on this? Use snd-aoa, it correctly handles your machine. You can't expect that hack to actually work beyond there's something coming out of the speakers johannes signature.asc Description: This is a digitally signed message part
