Menu
▾
▴
linuxconsole-dev
|
From: Kjetil K. <kj...@kj...> - 2003-11-06 20:14:03
|
Uhm,,,! Well, I'm apparently not quite there yet... My girlfriend just experienced that her keyboard and mouse locked up hard after a few hours' use. It could have been something like that I experienced too, but I did not investigate at that time. Locked hard means that the secondary mouse generates no events, and the LEDs on the keyboard can't be toggled. Now, I find that /dev/input/event2 is spewing out events persistently, even though no keys are hit. Well, it could be something else than the secondary keyboard, but it fits rather well with being this keyboard, right? Output from /proc/bus/input/devices: I: Bus=0003 Vendor=0d3d Product=0001 Version=0001 N: Name="Tangtop Generic USBPS2" P: Phys=usb-00:04.2-2/input0 H: Handlers=kbd event2 B: EV=120003 B: KEY=10000 7f ffe00000 7ff ffbeffdf ffffffff ffffffff fffffffe B: LED=1f On one hand, I've never seen this behaviour when using the keyboard on other ports, so perhaps it could be the driver, but OTOH, it is strange if the driver would generate keyboard events.... The scroll lock button sits in a somewhat awkward position, perhaps that could do it...? But then, I can't turn it off... Any ideas? Also, is it some way I can reset the keyboard without rebooting the box? Best, Kjetil -- Kjetil Kjernsmo Astrophysicist/IT Consultant/Skeptic/Ski-orienteer/Orienteer/Mountaineer kj...@kj... web...@sk... ed...@le... Homepage: http://www.kjetil.kjernsmo.net/ OpenPGP KeyID: 6A6A0BBC |
|
From: Andreas S. <an...@sc...> - 2003-11-06 23:22:49
|
* Kjetil Kjernsmo (kj...@kj...) [031106 21:16]: > My girlfriend just experienced that her keyboard and mouse locked up > hard after a few hours' use. It could have been something like that I > experienced too, but I did not investigate at that time. Locked hard > means that the secondary mouse generates no events, and the LEDs on the > keyboard can't be toggled. this is something that i experience, too. i assumed it was my usb hardware which was slighly broken, so i looked for ways to work around it. your usb setup doesnt seem to be too stable either, perhaps it is the same problem? however, here it is mostly the two mice and my keyboard dis- and reappearing. the problem with reappearing is that the xserver does not reclaim its hw automatically once it was gone. It does that only on special events, e.g. when you switch from the console to X. the Xserver in debian-experimental is able to regrab its hardware with help of the input.agent from http://people.debian.org/~warp/evdev/ , since it can react to events received from a pipe, which the input.agent writes to. the drawback with the event interface configuration is that it seems to have problems with mouse keypresses (the pressbutton event is generated at the same time as the releasebutton event, making dragging and marking things under X impossible). I still want to debug this so this is fully usable. the author of the x event interface can not explain this and never saw this phenomenon. |
|
From: Kjetil K. <kj...@kj...> - 2003-11-07 12:35:10
|
On Friday 07 November 2003 00:22, Andreas Schuldei wrote: > this is something that i experience, too. Good to hear we're not alone. ;-) > i assumed it was my usb hardware which was slighly broken, so i > looked for ways to work around it. your usb setup doesnt seem to > be too stable either, perhaps it is the same problem? however, > here it is mostly the two mice and my keyboard dis- and reappearing. Hm, ok, it could be. However, I see no evidence in any logs that it is actually having problems with loosing contact... What should I look for? But then, there are quite a lot of cables here; first the normal cable to a 5m extension cable, which again is connected to the Tangtop, which is connected to the USB port. If any of those gets displaced, obviously, it can happen easily. But then, she was just typing carefully when it happened. BTW, it happened a second time just after I wrote my post. Then, it didn't pour out events, it just sat there. Also, in the first case, DPMS didn't blank the screen, in the second case it did. > the problem with reappearing is that the xserver does not reclaim > its hw automatically once it was gone. It does that only on > special events, e.g. when you switch from the console to X. OK. > the Xserver in debian-experimental is able to regrab its hardware > with help of the input.agent from > http://people.debian.org/~warp/evdev/ , since it can react to > events received from a pipe, which the input.agent writes to. > > the drawback with the event interface configuration is that it > seems to have problems with mouse keypresses (the pressbutton > event is generated at the same time as the releasebutton event, > making dragging and marking things under X impossible). Ouch, yes, that's rather bad. >I still > want to debug this so this is fully usable. the author of the x > event interface can not explain this and never saw this > phenomenon. If there is anything I can try, please let me know! Best, Kjetil -- Kjetil Kjernsmo Astrophysicist/IT Consultant/Skeptic/Ski-orienteer/Orienteer/Mountaineer kj...@kj... web...@sk... ed...@le... Homepage: http://www.kjetil.kjernsmo.net/ OpenPGP KeyID: 6A6A0BBC |
|
From: Svetoslav S. <sv...@gm...> - 2003-11-07 18:13:17
|
Hi, > On Friday 07 November 2003 00:22, Andreas Schuldei wrote: > > > this is something that i experience, too. > > Good to hear we're not alone. ;-) > > > i assumed it was my usb hardware which was slighly broken, so i > > looked for ways to work around it. your usb setup doesnt seem to > > be too stable either, perhaps it is the same problem? however, > > here it is mostly the two mice and my keyboard dis- and reappearing. > > Hm, ok, it could be. However, I see no evidence in any logs that it is > actually having problems with loosing contact... What should I look > for? But then, there are quite a lot of cables here; first the normal > cable to a 5m extension cable, which again is connected to the Tangtop, > which is connected to the USB port. If any of those gets displaced, > obviously, it can happen easily. But then, she was just typing > carefully when it happened. isn't there a limitation of the length of usb cables ? smth between 5-10 meters ? > BTW, it happened a second time just after I wrote my post. > > Then, it didn't pour out events, it just sat there. Also, in the first > case, DPMS didn't blank the screen, in the second case it did. > > > the problem with reappearing is that the xserver does not reclaim > > its hw automatically once it was gone. It does that only on > > special events, e.g. when you switch from the console to X. > > OK. > > > the Xserver in debian-experimental is able to regrab its hardware > > with help of the input.agent from > > http://people.debian.org/~warp/evdev/ , since it can react to > > events received from a pipe, which the input.agent writes to. > > > > the drawback with the event interface configuration is that it > > seems to have problems with mouse keypresses (the pressbutton > > event is generated at the same time as the releasebutton event, > > making dragging and marking things under X impossible). > > Ouch, yes, that's rather bad. > > >I still > > want to debug this so this is fully usable. the author of the x > > event interface can not explain this and never saw this > > phenomenon. > > If there is anything I can try, please let me know! > have you tried ruby with linux-2.6.0-test9 ? :-) best, svetljo -- NEU FÜR ALLE - GMX MediaCenter - für Fotos, Musik, Dateien... Fotoalbum, File Sharing, MMS, Multimedia-Gruß, GMX FotoService Jetzt kostenlos anmelden unter http://www.gmx.net +++ GMX - die erste Adresse für Mail, Message, More! +++ |
|
From: Kjetil K. <kj...@kj...> - 2003-11-08 22:25:17
|
On Friday 07 November 2003 19:13, Svetoslav Slavtchev wrote: > isn't there a limitation of the length of usb cables ? > smth between 5-10 meters ? Dunno. But since you mention it, I couldn't find USB cables longer than 3 meters when I searched for it, and I found cables with amplifiers at 30 meters. It is reasonable to expect a limit, yeah, but I mean, five meters...? :-) However, I'm pretty sure I saw this problem, before I realized what the problems was, without the extension cables. > have you tried ruby with linux-2.6.0-test9 ? No, but I did try with, uhm, I think it was test8 (Andreas...?). Couldn't get it booted. Tried a few different things, and also a non-ruby test9 kernel without success. Seems to die at some APIC things. Since Linus seems to actually be soliciting the feedback of J. Random Desktop User in http://www.oetrends.com/news.php?action=view_record&idnum=277 I thought I'd wait a few days and give test10 a whirl and tell the hackers what I found, Best, Kjetil -- Kjetil Kjernsmo Astrophysicist/IT Consultant/Skeptic/Ski-orienteer/Orienteer/Mountaineer kj...@kj... web...@sk... ed...@le... Homepage: http://www.kjetil.kjernsmo.net/ OpenPGP KeyID: 6A6A0BBC |
|
From: Svetoslav S. <sv...@gm...> - 2003-11-10 08:38:06
|
> On Friday 07 November 2003 19:13, Svetoslav Slavtchev wrote: > > > isn't there a limitation of the length of usb cables ? > > smth between 5-10 meters ? > > Dunno. But since you mention it, I couldn't find USB cables longer than > 3 meters when I searched for it, and I found cables with amplifiers at > 30 meters. It is reasonable to expect a limit, yeah, but I mean, five > meters...? :-) > > However, I'm pretty sure I saw this problem, before I realized what the > problems was, without the extension cables. > i'm sure it's between 5m & 10m, i had strange issues with Mac OS X & a usb printer, and i had to google a bit, until i found it > > have you tried ruby with linux-2.6.0-test9 ? > > No, but I did try with, uhm, I think it was test8 (Andreas...?). > Couldn't get it booted. Tried a few different things, and also a > non-ruby test9 kernel without success. Seems to die at some APIC > things. Since Linus seems to actually be soliciting the feedback of J. > Random Desktop User in > http://www.oetrends.com/news.php?action=view_record&idnum=277 > I thought I'd wait a few days and give test10 a whirl and tell the > hackers what I found, it should be out pretty soon, unless Linus decides that 2.6.0 is ready :-) have you tried passing "acpi=off pci=noacpi" or even disabling acpi in the kernel configuration? i had to use it for a long time to get my KT400 based mobo up and running svetljo -- NEU FÜR ALLE - GMX MediaCenter - für Fotos, Musik, Dateien... Fotoalbum, File Sharing, MMS, Multimedia-Gruß, GMX FotoService Jetzt kostenlos anmelden unter http://www.gmx.net +++ GMX - die erste Adresse für Mail, Message, More! +++ |
|
From: Kjetil K. <kj...@kj...> - 2003-11-11 11:40:12
|
On Monday 10 November 2003 09:37, Svetoslav Slavtchev wrote: > i'm sure it's between 5m & 10m, OK. I tried to connect the primary keyboard to the USB Tangtop device and the secondary (which has to be on a long cable) on the PS/2 port, recompiled the kernel with atkbd and psmouse as modules, and got it up. Unfortunately, it didn't take many minutes before my keyboard, the one which was connected right on to the Tangtop with no extension cable, locked up. So it is definately not the long cable... :-( Any other ideas...? > it should be out pretty soon, unless Linus decides that 2.6.0 is > ready :-) Yup. And besides, it seems to be Andrew Morton's call now... :-) > have you tried passing "acpi=off pci=noacpi" or even disabling acpi > in the kernel configuration? i had to use it for a long time to get > my KT400 based mobo up and running Yep, didn't work... Best, Kjetil -- Kjetil Kjernsmo Astrophysicist/IT Consultant/Skeptic/Ski-orienteer/Orienteer/Mountaineer kj...@kj... web...@sk... ed...@le... Homepage: http://www.kjetil.kjernsmo.net/ OpenPGP KeyID: 6A6A0BBC |
|
From: Svetoslav S. <sv...@gm...> - 2003-11-11 13:07:19
|
> On Monday 10 November 2003 09:37, Svetoslav Slavtchev wrote: > > i'm sure it's between 5m & 10m, > > OK. > > I tried to connect the primary keyboard to the USB Tangtop device and > the secondary (which has to be on a long cable) on the PS/2 port, > recompiled the kernel with atkbd and psmouse as modules, and got it up. > Unfortunately, it didn't take many minutes before my keyboard, the one > which was connected right on to the Tangtop with no extension cable, > locked up. So it is definately not the long cable... :-( > > Any other ideas...? > sorry, but no idea :( it should be sort of usb problem, were there some strange messages when this happens ? hopefully it will be fixed in later 2.4 kernels, a number of usb bugfixes went in .2.4.23 pre series what was your mainboard ? > > it should be out pretty soon, unless Linus decides that 2.6.0 is > > ready :-) > > Yup. And besides, it seems to be Andrew Morton's call now... :-) > > > have you tried passing "acpi=off pci=noacpi" or even disabling acpi > > in the kernel configuration? i had to use it for a long time to get > > my KT400 based mobo up and running > > Yep, didn't work... :( my board seems to feeze with test9-bk8+ , but hopefully it will be fixed for test10/ 2.6.0 svetljo -- NEU FÜR ALLE - GMX MediaCenter - für Fotos, Musik, Dateien... Fotoalbum, File Sharing, MMS, Multimedia-Gruß, GMX FotoService Jetzt kostenlos anmelden unter http://www.gmx.net +++ GMX - die erste Adresse für Mail, Message, More! +++ |
|
From: Kjetil K. <kj...@kj...> - 2003-11-11 13:24:39
|
On Tuesday 11 November 2003 14:07, Svetoslav Slavtchev wrote: > sorry, but no idea :( OK, that's life. > it should be sort of usb problem, were there some strange messages > when this happens ? > hopefully it will be fixed in later 2.4 kernels, a number of usb > bugfixes went in .2.4.23 pre series OK, good! > what was your mainboard ? Asustek Computer, Inc. A7M266, which a CM8738 sound chip. > my board seems to feeze with test9-bk8+ , but hopefully it > will be fixed for test10/ 2.6.0 Yup! Cheers, Kjetil -- Kjetil Kjernsmo Astrophysicist/IT Consultant/Skeptic/Ski-orienteer/Orienteer/Mountaineer kj...@kj... web...@sk... ed...@le... Homepage: http://www.kjetil.kjernsmo.net/ OpenPGP KeyID: 6A6A0BBC |
|
From: Andreas S. <an...@sc...> - 2003-11-11 14:02:35
|
* Svetoslav Slavtchev (sv...@gm...) [031111 14:09]: > > On Monday 10 November 2003 09:37, Svetoslav Slavtchev wrote: > > > i'm sure it's between 5m & 10m, > > > > OK. > > > > I tried to connect the primary keyboard to the USB Tangtop device and > > the secondary (which has to be on a long cable) on the PS/2 port, > > recompiled the kernel with atkbd and psmouse as modules, and got it up. > > Unfortunately, it didn't take many minutes before my keyboard, the one > > which was connected right on to the Tangtop with no extension cable, > > locked up. So it is definately not the long cable... :-( > > > > Any other ideas...? > > > > sorry, but no idea :( > > it should be sort of usb problem, were there some strange messages when this > happens ? > hopefully it will be fixed in later 2.4 kernels, a number of usb bugfixes > went in .2.4.23 pre series i see it in 2.6, too. i think i even have usb debugging messages enabled, but one sees only the plugg- and unplugg events, nothing more or strange, as far as the OS is concerned. |
|
From: Andreas S. <an...@sc...> - 2003-11-13 11:28:21
|
* Andreas Schuldei (an...@sc...) [031111 15:04]: > * Svetoslav Slavtchev (sv...@gm...) [031111 14:09]: > i see it in 2.6, too. i think i even have usb debugging messages > enabled, but one sees only the plugg- and unplugg events, nothing > more or strange, as far as the OS is concerned. now i figured out what was wrong with my setup, and drag and drop works again for me with X's event interface, as described on http://people.debian.org/~warp/evdev/ (which is included in both the debian experimental X and also in the one on www.schuldei.org). one must not have Emulate3Buttons option active, that absorbs the button=ADdepress-event and releases it only together with the button-release-event.=20 this patch (on the above url) also features a fifo which the input.agent uses to alert the Xserver of hotplug events. this means that devices are regrabbed on the fly, without the need of switching to the console and back. there is an issue with the keyboard in that input-agent, though, i guess that is due to the format change in the later 2.6 kernels... you could try if it works properly on your 2.4. |
|
From: Kjetil K. <kj...@kj...> - 2003-11-13 11:45:52
|
On Thursday 13 November 2003 12:28, Andreas Schuldei wrote: > * Andreas Schuldei (an...@sc...) [031111 15:04]: > > * Svetoslav Slavtchev (sv...@gm...) [031111 14:09]: > > i see it in 2.6, too. i think i even have usb debugging messages > > enabled, but one sees only the plugg- and unplugg events, nothing > > more or strange, as far as the OS is concerned. > > now i figured out what was wrong with my setup, and drag and drop > works again for me with X's event interface, Great! >as described on > http://people.debian.org/~warp/evdev/ (which is included in both > the debian experimental X and also in the one on > www.schuldei.org). OK, good, so I have it allready, since I use your packages. > one must not have Emulate3Buttons option active, that absorbs the > buttondepress-event and releases it only together with the > button-release-event. OK. I have them off. > this patch (on the above url) also features a fifo which the > input.agent uses to alert the Xserver of hotplug events. this > means that devices are regrabbed on the fly, without the need of > switching to the console and back. Nice. Anyway, from the readme: input.agent: You need to put this in /etc/hotplug/, if you already have an /etc/hotplug/input.agent then you hopefully know enough to make it work. well, I haven't any input.agent, and I have no idea how it can be made to work... :-) Any clues for me...? > there is an issue with the keyboard in that input-agent, though, > i guess that is due to the format change in the later 2.6 > kernels... you could try if it works properly on your 2.4. Yup. I'll try. So, do I just dump the input.agent in /etc/hotplug...? There's no need for a new kernel or a new X binary, if I get you right. Since we have two set of keyboards, the config is somewhat different than in the readme, I presume, do I still need to set the "Dev Phys" and that stuff...? Also, is there any way to provoke the error to see if it is still there. Since the problem is that it blocks after some time of use, it would be great to just make it lock up or let it be, if it is happy with the current state of things... :-) Best, Kjetil -- Kjetil Kjernsmo Astrophysicist/IT Consultant/Skeptic/Ski-orienteer/Orienteer/Mountaineer kj...@kj... web...@sk... ed...@le... Homepage: http://www.kjetil.kjernsmo.net/ OpenPGP KeyID: 6A6A0BBC |
|
From: Andreas S. <an...@sc...> - 2003-11-13 13:08:24
|
* Kjetil Kjernsmo (kj...@kj...) [031113 12:47]: > Anyway, from the readme: > input.agent: You need to put this in /etc/hotplug/, if you already > have an /etc/hotplug/input.agent then you hopefully know > enough to make it work. > > well, I haven't any input.agent, and I have no idea how it can be made > to work... :-) Any clues for me...? cp input.agent /etc/hotplug/ chmod +x /etc/hotplug/input.agent i think that is all. perhaps, if you dont have hotplug installed yet, do an apt-get install hotplug. note that it will not work on most things since you complied your kernel statically, but for the input.agent this does not matter, since it does not load modules. it is possible to include this input agent into other input agents, withoug much effort, if others have other input needs besides X. > There's no need for a new kernel or a new X binary, if I get you right. you need to adjust your xf86config, yes. > Since we have two set of keyboards, the config is somewhat different > than in the readme, I presume, do I still need to set the "Dev Phys" > and that stuff...? yes, or the name. the phys stuff did not work for me on 2.4, but the name option worked fine. i will try the phys option on 2.6, too. that would be a major argument for this input method. > Also, is there any way to provoke the error to see if it is still there. not that i would know. it happens more often under heavy ide load. try doing some heavy i/o work. anyone have a good idea? |
|
From: Kjetil K. <kj...@kj...> - 2003-11-14 14:20:52
|
On Thursday 13 November 2003 14:08, Andreas Schuldei wrote: > * Kjetil Kjernsmo (kj...@kj...) [031113 12:47]: > > Anyway, from the readme: > > input.agent: You need to put this in /etc/hotplug/, if you > > already have an /etc/hotplug/input.agent then you hopefully know > > enough to make it work. > > > > well, I haven't any input.agent, and I have no idea how it can be > > made to work... :-) Any clues for me...? > > cp input.agent /etc/hotplug/ > chmod +x /etc/hotplug/input.agent OK. > i think that is all. > perhaps, if you dont have hotplug installed yet, do an apt-get > install hotplug. note that it will not work on most things since > you complied your kernel statically, but for the input.agent this > does not matter, since it does not load modules. OK, I did, and just replaced the input.agent with the file from above. I have no other hotplug devices now. Also, I discovered that I didn't have hotplug in my kernel, so I enabled that. > it is possible to include this input agent into other input > agents, withoug much effort, if others have other input needs > besides X. > > > There's no need for a new kernel or a new X binary, if I get you > > right. > > you need to adjust your xf86config, yes. OK. It seemed easy enough. Only thing that doesn't seem to work right now is the mousewheel on the USB... Any gotchas there? > > Since we have two set of keyboards, the config is somewhat > > different than in the readme, I presume, do I still need to set the > > "Dev Phys" and that stuff...? > > yes, or the name. the phys stuff did not work for me on 2.4, but > the name option worked fine. The name is the same on the keyboard and mouse for me, so probably, phys worked. > i will try the phys option on 2.6, too. that would be a major > argument for this input method. Yup. > > Also, is there any way to provoke the error to see if it is still > > there. > > not that i would know. it happens more often under heavy ide > load. try doing some heavy i/o work. anyone have a good idea? updatedb...? :-) It worked after pulling the tangtop from the USB socket, and still after heavy smashing on the keyboard while updatedb was running... :-) I guess that's a good sign. Nevertheless, further ideas on how to stress-test it is very much welcome! Cheers, Kjetil -- Kjetil Kjernsmo Astrophysicist/IT Consultant/Skeptic/Ski-orienteer/Orienteer/Mountaineer kj...@kj... web...@sk... ed...@le... Homepage: http://www.kjetil.kjernsmo.net/ OpenPGP KeyID: 6A6A0BBC |
|
From: Kjetil K. <kj...@kj...> - 2003-11-14 15:33:37
|
On Friday 14 November 2003 15:20, Kjetil Kjernsmo wrote: > It worked after pulling the tangtop from the USB socket, and still > after heavy smashing on the keyboard while updatedb was running... > :-) I guess that's a good sign. Well, how long was Adam in paradise...? :-) I'm back to the first error again; freeze-up and events are being generated to /dev/input/event2 I can't find anything in the logs that are relevant to the crash itself. However, I think I remember I saw something at bootup about not being able to find usb** hotplugs or something. I can't find that in dmesg, though, so I guess it wasn't important...? What may be of some importance is that I can't find any evidence that input.agent has been run. There's a usb.agent which came with the Debian hotplug package, and that seems to be called, this is from user.log: Nov 14 15:03:14 owl default.hotplug[1244]: arguments (usb) env (DEVFS=/ proc/bus/usb OLDPWD=/ PATH=/bin:/sbin:/usr/sbin:/usr/bin ACTION=remove PWD=/etc/hotplug HOME=/ SHLVL=2 DEVICE=/proc/bus/usb/001/002 INTERFACE=3/1/1 PRODUCT=d3d/1/1 TYPE=0/0/0 DEBUG=kernel _=/usr/bin/env) Nov 14 15:03:14 owl default.hotplug[1244]: invoke /etc/hotplug/usb.agent () Nov 14 15:03:14 owl default.hotplug[1246]: arguments (usb) env (DEVFS=/ proc/bus/usb OLDPWD=/ PATH=/bin:/sbin:/usr/sbin:/usr/bin ACTION=remove PWD=/etc/hotplug HOME=/ SHLVL=2 DEVICE=/proc/bus/usb/001/002 INTERFACE=3/1/2 PRODUCT=d3d/1/1 TYPE=0/0/0 DEBUG=kernel _=/usr/bin/env) Nov 14 15:03:14 owl default.hotplug[1246]: invoke /etc/hotplug/usb.agent () Nov 14 15:03:29 owl default.hotplug[1303]: arguments (usb) env (DEVFS=/ proc/bus/usb OLDPWD=/ PATH=/bin:/sbin:/usr/sbin:/usr/bin ACTION=add PWD=/etc/hotplug HOME=/ SHLVL=2 DEVICE=/proc/bus/usb/001/003 INTERFACE=3/1/1 PRODUCT=d3d/1/1 TYPE=0/0/0 DEBUG=kernel _=/usr/bin/env) Nov 14 15:03:29 owl default.hotplug[1303]: invoke /etc/hotplug/usb.agent () Nov 14 15:03:29 owl default.hotplug[1313]: arguments (usb) env (DEVFS=/ proc/bus/usb OLDPWD=/ PATH=/bin:/sbin:/usr/sbin:/usr/bin ACTION=add PWD=/etc/hotplug HOME=/ SHLVL=2 DEVICE=/proc/bus/usb/001/003 INTERFACE=3/1/2 PRODUCT=d3d/1/1 TYPE=0/0/0 DEBUG=kernel _=/usr/bin/env) Nov 14 15:03:29 owl default.hotplug[1313]: invoke /etc/hotplug/usb.agent () Nov 14 15:03:32 owl usb.agent[1303]: Setup keybdev for USB product d3d/1/1 Nov 14 15:03:32 owl usb.agent[1313]: Setup mousedev for USB product d3d/1/1 Nov 14 15:27:20 owl gconfd (kjetil-1768): starting (version 2.4.0.1), pid 1768 user 'kjetil' Nov 14 15:27:20 owl gconfd (kjetil-1768): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only config source at position 0 Nov 14 15:27:20 owl gconfd (kjetil-1768): Resolved address "xml:readwrite:/home/kjetil/.gconf" to a writable config source at position 1 Nov 14 15:27:20 owl gconfd (kjetil-1768): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only config source at position 2 As I said, if I just pulled the tangtop from the USB port, it would be redetected, but this didn't help here... Best, Kjetil -- Kjetil Kjernsmo Astrophysicist/IT Consultant/Skeptic/Ski-orienteer/Orienteer/Mountaineer kj...@kj... web...@sk... ed...@le... Homepage: http://www.kjetil.kjernsmo.net/ OpenPGP KeyID: 6A6A0BBC |
|
From: Andreas S. <an...@sc...> - 2003-11-16 00:22:34
|
* Kjetil Kjernsmo (kj...@kj...) [031114 16:35]: > On Friday 14 November 2003 15:20, Kjetil Kjernsmo wrote: > > It worked after pulling the tangtop from the USB socket, and still > > after heavy smashing on the keyboard while updatedb was running... > > :-) I guess that's a good sign. > > Well, how long was Adam in paradise...? :-) quite long, i think. we just get told about the sad last day... > I'm back to the first error again; freeze-up and events are being > generated to /dev/input/event2 you could disable the usb.agent, whitch might try funny things with modules etc... whitch you dont have. chmod -x or put in an exit 0 at the beginning? |
|
From: Kjetil K. <kj...@kj...> - 2003-11-16 11:03:01
|
On Sunday 16 November 2003 01:21, Andreas Schuldei wrote: > > I'm back to the first error again; freeze-up and events are being > > generated to /dev/input/event2 > > you could disable the usb.agent, whitch might try funny things > with modules etc... whitch you dont have. chmod -x or put in an > exit 0 at the beginning? OK, I'll try that some day! Unfortunately, I just had a hard deadline landing in my lap... :-( So, I have to go and focus on that, and settle for the setup I have now for the time being.... That's life, I'm afraid... Best, Kjetil -- Kjetil Kjernsmo Astrophysicist/IT Consultant/Skeptic/Ski-orienteer/Orienteer/Mountaineer kj...@kj... web...@sk... ed...@le... Homepage: http://www.kjetil.kjernsmo.net/ OpenPGP KeyID: 6A6A0BBC |
|
From: Andreas S. <an...@sc...> - 2003-11-10 15:00:21
|
* Kjetil Kjernsmo (kj...@kj...) [031108 23:27]: > > have you tried ruby with linux-2.6.0-test9 ? > > No, but I did try with, uhm, I think it was test8 (Andreas...?). yes, it was test8. |
|
From: Helge H. <hel...@ai...> - 2003-11-07 09:06:22
|
Kjetil Kjernsmo wrote: > > Also, is it some way I can reset the keyboard without rebooting the box? How about unplugging it? Ordinary ps2 keyboards resets this way. Helge Hafting |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X