From: Svetoslav S. <ga...@st...> - 2003-05-05 23:59:36
|
Hi , this is sort of official bug report. Sort of because : 1.) because i do not use official kernel - i use backstreet ruby 2.) you clearly mention that under 2.4 PHYS can not be in the input device section in the XFConfig. - i'm running 2.4 but backstreet ruby which has PHYS for input devices why i'm writing this mail although i'm fully aware of the previous 2 facts: -because bruby uses the input system from 2.5.67 so the problem seems to be in the input.agent because XFree finds the devices on start-up, but the input.agent doesn't seem to do anything when i replug my USB mouse. I have to restart X in order to get the mouse back. I assume the same problem exist with keyboards as well. i think the reason is in "export VAL_SEP='\003'" i got to this idea trough extending your input.agent with 2 lines: echo $dev >> /etc/hotplug/input.agent.DEBUG /bin/sh -c 'echo -e "2.1${ARG_SEP}NAME${VAL_SEP}${NAME}${ARG_SEP}PHYS${VAL_SEP}${PHYS}${ARG_SEP}ACTION${VAL_SEP}${ACTION}" >> /etc/hotplug/input.agent.DEBUG2' & please find attached the resulting input.agent, input.agent.DEBUG, input.agent.DEBUG2 if you need more information, just drop a line :) best, svetljo -- |
From: Svetoslav S. <ga...@st...> - 2003-05-06 00:37:17
|
Hi again, Some more info, attached you'll find /proc/bus/input/devices, /proc/bus/input/handlers , and the output of the tests i runned with evtest from linux-console's cvs. One strange thing from the mouse i had the problems( i did't try replugging other devices) 'evtest /dev/input/event3 > evtest_event3` resulted in an empty file i had to move the mouse in order to get smth in the redirected output, but when i didn't redirected to file, i got the same information like in evtest_event3_ (the redirected file). best, svetljo Quoting Svetoslav Slavtchev <ga...@st...>: > Hi , > this is sort of official bug report. > > Sort of because : > > 1.) > because i do not use official kernel > - i use backstreet ruby > 2.) > you clearly mention that under 2.4 PHYS can not be in the input device > section > in the XFConfig. > - i'm running 2.4 but backstreet ruby which has PHYS for input devices > > why i'm writing this mail although i'm fully aware of the previous 2 facts: > -because bruby uses the input system from 2.5.67 > > > > so the problem seems to be in the input.agent because XFree finds the devices > on > start-up, but the input.agent doesn't seem to do anything when i replug my > USB > mouse. I have to restart X in order to get the mouse back. I assume the > same |
From: Svetoslav S. <ga...@st...> - 2003-05-06 00:56:19
|
Sorry, forgot the output from the other event devices . best, svetljo -- |
From: Svetoslav S. <ga...@st...> - 2003-05-06 11:51:10
Attachments:
XF86Config-4.mdk
XF86Config-4.X1.mdk
|
Hi again, some more info . this is under both Mandrake-9.1 and Debian Sid. also the keymapping is not correct on my USB keyboard (Logitech Cordless Desktop Pro). i can not type certain characters like "> ' | " and "#" brings me back to console, if i press "#" over a mozilla window, when i get back to X :( i have message, saying something like "pressing F7 ......" attached are the XFree configuration files under Mandrake - XF86Config-4.mdk primary X server - XF86Config-4.X1.mdk secondary X server if you need the Debian one's just drop a line. best, svetljo |
From: Svetoslav S. <ga...@st...> - 2003-05-09 11:14:11
|
Hi, Quoting Svetoslav Slavtchev <ga...@st...>: > Hi again, > > some more info . > > this is under both Mandrake-9.1 and Debian Sid. both problems exist under linux-2.5.69 too :( (of course only the first X server was started) some one with ideas for debuging ? best, svetljo > also the keymapping is not correct on my USB keyboard > (Logitech Cordless Desktop Pro). > > i can not type certain characters like "> ' | " and "#" brings me back to > console, > if i press "#" over a mozilla window, when i get back to X :( i have > message, > saying something like "pressing F7 ......" |
From: Zephaniah E. H. <wa...@ba...> - 2003-05-09 18:58:00
|
On Fri, May 09, 2003 at 01:10:02PM +0200, Svetoslav Slavtchev wrote: > Hi, >=20 > Quoting Svetoslav Slavtchev <ga...@st...>: > > Hi again, > >=20 > > some more info . > >=20 > > this is under both Mandrake-9.1 and Debian Sid. >=20 > both problems exist under linux-2.5.69 too :( >=20 > (of course only the first X server was started) >=20 > some one with ideas for debuging ? Ok, I'd like you to try something for the hotplugging problem, put the actual echo to the fifo in the background, & should do the trick nicely. That is about the only thing that comes to mind, the X side /should/ work, and does for me. :/ >=20 > best, >=20 > svetljo --=20 1024D/E65A7801 Zephaniah E. Hull <wa...@ba...> 92ED 94E4 B1E6 3624 226D 5727 4453 008B E65A 7801 CCs of replies from mailing lists are requested. Yes, Java is so bulletproofed that to a C programmer it feels like being in a straightjacket, but it's a really comfy and warm straightjacket, and the world would be a safer place if everyone was straightjacketed most of the time. -- Overheard in the SDM. |
From: Svetoslav S. <ga...@st...> - 2003-05-12 13:37:26
|
Quoting "Zephaniah E. Hull" <wa...@ba...>: > On Fri, May 09, 2003 at 01:10:02PM +0200, Svetoslav Slavtchev wrote: > > Hi, > > > > Quoting Svetoslav Slavtchev <ga...@st...>: > > > Hi again, > > > > > > some more info . > > > > > > this is under both Mandrake-9.1 and Debian Sid. > > > > both problems exist under linux-2.5.69 too :( > > > > (of course only the first X server was started) > > > > some one with ideas for debuging ? > > Ok, I'd like you to try something for the hotplugging problem, put the > actual echo to the fifo in the background, & should do the trick nicely. so you mean: not -> .... {VAL_SEP}${ACTION}" >> ${dev} ' & but -> .... {VAL_SEP}${ACTION}" >> ${dev} & ' is this correct? no changes under backstreet ruby, will check with latest BK in an hour(compile time :) ) > That is about the only thing that comes to mind, the X side /should/ > work, and does for me. :/ the X server detects the devices on start/restart, but repluging a mouse results in loosing the mouse until restart of the X server. ( still have to check what hapens if keyboard is replugged ) best, svetljo |
From: Svetoslav S. <ga...@st...> - 2003-05-12 15:41:51
|
Quoting Juan Pablo Sousa <jp...@ma...>: > Svetoslav Slavtchev wrote: > > >the X server detects the devices on start/restart, but repluging a mouse > results > >in loosing the mouse until restart of the X server. > >( still have to check what hapens if keyboard is replugged ) > > > > > > > I've noticed that switching to console and back into X makes X find > repluged mice, I use gpm so maybe that has something to do with it. I can confirm this when gpm is not used. But doesn't X re-initialize the devices when one switches from VT to X ? and this is really not an option for some cases when one can not switch to VT: - X running on dumbcon (using bruby) - loosing VT console with starting X (not happy owner of Matrox card :( ) ( - what if keyboard is replugged, how would one switch to VT and back ? ) svetljo |
From: Svetoslav S. <ga...@st...> - 2003-05-12 15:50:00
|
Quoting Svetoslav Slavtchev <ga...@st...>: > Quoting "Zephaniah E. Hull" <wa...@ba...>: > > Ok, I'd like you to try something for the hotplugging problem, put the > > actual echo to the fifo in the background, & should do the trick nicely. > > so you mean: > not -> .... {VAL_SEP}${ACTION}" >> ${dev} ' & > but -> .... {VAL_SEP}${ACTION}" >> ${dev} & ' > is this correct? > > no changes under backstreet ruby, will check with latest BK in an > hour(compile > time :) ) :( same with the older 2.5.69 (current BK seems brocken :( ) svetljo |