| 1 |
One other thing: |
| 2 |
|
| 3 |
# hal-device|grep -C 10 \,ru |
| 4 |
net.linux.ifindex = 1 (0x1) (int) |
| 5 |
|
| 6 |
23: udi = |
| 7 |
'/org/freedesktop/Hal/devices/platform_i8042_i8042_KBD_port_logicaldev_input' |
| 8 |
linux.hotplug_type = 2 (0x2) (int) |
| 9 |
linux.subsystem = 'input' (string) |
| 10 |
input.device = '/dev/input/event2' (string) |
| 11 |
input.product = 'AT Translated Set 2 keyboard' (string) |
| 12 |
info.addons.singleton = { 'hald-addon-input' } (string list) |
| 13 |
input.xkb.rules = 'xorg' (string) |
| 14 |
* input.xkb.model = 'pc104' (string) |
| 15 |
input.xkb.layout = 'en_US,ru' (string) |
| 16 |
input.xkb.variant = ',winkeys' (string) |
| 17 |
input.x11_driver = 'evdev' (string)* |
| 18 |
info.subsystem = 'input' (string) |
| 19 |
input.originating_device = |
| 20 |
'/org/freedesktop/Hal/devices/platform_i8042_i8042_KBD_port' (string) |
| 21 |
info.product = 'AT Translated Set 2 keyboard' (string) |
| 22 |
info.udi = |
| 23 |
'/org/freedesktop/Hal/devices/platform_i8042_i8042_KBD_port_logicaldev_input' |
| 24 |
(string) |
| 25 |
linux.sysfs_path = |
| 26 |
'/sys/devices/platform/i8042/serio0/input/input2/event2' (string) |
| 27 |
info.parent = |
| 28 |
'/org/freedesktop/Hal/devices/platform_i8042_i8042_KBD_port' (string) |
| 29 |
input.xkb.options = 'grp:shift_toggle,grp_led:scroll' (string) |
| 30 |
info.category = 'input' (string) |
| 31 |
|
| 32 |
Perhaps HAL is responsible for generating the log messages? |
| 33 |
|
| 34 |
Amit |
| 35 |
|
| 36 |
|
| 37 |
|
| 38 |
On 05/17/10 09:42, Amit Dor-Shifer wrote: |
| 39 |
> # print modification TSs, to verify log refers to said conf file |
| 40 |
> # stat -c %y /etc/X11/xorg.conf /var/log/Xorg.0.log |
| 41 |
> 2010-05-16 11:01:33.231512534 +0300 |
| 42 |
> 2010-05-16 12:23:02.502995953 +0300 |
| 43 |
> |
| 44 |
> |
| 45 |
> On 05/16/10 22:15, walt wrote: |
| 46 |
>> On 05/16/2010 01:12 AM, Amit Dor-Shifer wrote: |
| 47 |
>>> |
| 48 |
>>> |
| 49 |
>> |
| 50 |
>>> Explicitly setting Driver to "evdev" (to both mouse and keyboard |
| 51 |
>>> sections) doesn't |
| 52 |
>> > fix the unexplained messages in Xorg.0.log. At least X manages to |
| 53 |
>> start, though. |
| 54 |
>> |
| 55 |
>> I'm expecting that your newest Xorg log will be different from the |
| 56 |
>> earlier ones. |
| 57 |
>> Which messages do you mean? |
| 58 |
> <Xorg.0.log> |
| 59 |
> (**) Option "xkb_rules" "evdev" |
| 60 |
> (**) Option "xkb_model" "pc104" |
| 61 |
> (**) Option "xkb_layout" "en_US,ru" |
| 62 |
> (**) Option "xkb_variant" ",winkeys" |
| 63 |
> (**) Option "xkb_options" "grp:shift_toggle,grp_led:scroll" |
| 64 |
> </Xorg.0.log> |
| 65 |
> |
| 66 |
> That quite the same as those I had in the beginning. |
| 67 |
>> |
| 68 |
>>> I'm now noticing another problem: X's CPU usage sky-rockets when |
| 69 |
>>> using input devices. |
| 70 |
>> > Especially mouse: If I move my pointer around the screen, hovering |
| 71 |
>> over some windows |
| 72 |
>> > in the process, I get >50% CPU in 'top'. |
| 73 |
>> |
| 74 |
>> I've never seen that before. Does hovering over xev print any messages? |
| 75 |
>> |
| 76 |
>> |
| 77 |
> Well, I'm less inclined to think now that X is responsible for the |
| 78 |
> high CPU load. I wasn't too knowledgeable about the relationships |
| 79 |
> between X and its clients when I made my initial assumption. It was |
| 80 |
> more like "I startx + I move mouse + CPU shoots-up => it's X". |
| 81 |
> |
| 82 |
> Looks more like kde is rocking my CPU. Indeed, xev doesn't print |
| 83 |
> anything while I'm generating high CPU with mouse movements. Also, I |
| 84 |
> had a notion twm didn't exhibit the phenomenon as long as I didn't |
| 85 |
> execute any kde apps. But I'm not 100% sure about the latter experiment. |
| 86 |
> |
| 87 |
> I'm runing KDE 3.5.10. |
| 88 |
> |
| 89 |
> Amit |
Archives