Re: IMPS/2 problems after kernel 2.4.1 update
Maybe you should try ExplorerPS/2 in XFconfig rather than imps/2. It all works great for me. On approximately Fri, Feb 16, 2001 at 08:06:46AM -0500, Tyler Braun wrote: I experienced the same problems with my intellimouse. What you're looking for is quite simple, I guessed at how I could get the new Zaxis line and it worked. =] Section InputDevice # Identifier and driver Identifier Mouse1 Driver mouse Option ProtocolIMPS/2 Option ZAxisMapping 4 5 Option Device /dev/psaux Good luck! Ty On Thu Feb 15/2001 @ 11:02:P -0500, Dave Bresson wrote: Hi there, I'm having a problem with my Microsoft Intellimouse (an intellimouse with two buttons and a scroll wheel that uses the ps/2 interface) since going from a 2.2.x kernel to 2.4.1. The way i have setup (and how everything worked perfectly before this upgrade) was that gpm was set to read from /dev/psaux using the imps2 protocol. It then repeats this to /dev/gpmdata which i then have /dev/mouse linked to. My XF86Config-4 is setup so that it knows the mouse is at /dev/mouse, and uses the imPS/2 protocol. I also have a line for the Zaxis stuff to get the scroll wheel to act like buttons 4 and 5 in X so that the wheel works. Anyway, all this is well and good because it was this exact setup that worked before the new kernel. Anyway, since upgrading the kernel, gpm no longer works on /dev/psaux with the imps2 protocol (hence, X doesn't work either...). The mouse just goes all crazy moving all over the place, and pushing random buttons and what not. So i set gpm and X to use the regular ps/2 protocol, and everything was fine, however i get no third button or scroll wheel anymore, which sucks. Just in case this was just a gpm problem, i tried having X read directly from /dev/psaux using the IMPS/2 protocol, but unfortunately got the same bad result. Does anyone have any idea what might be the problem here? It had to have been something i configured wrong in the kernel...however i don't know what, since it just made the IMPS/2 stuff not work, while the regular PS/2 still works...very strange. Any ideas, or tips? thanks, dave -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Tyler Braun [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: IMPS/2 problems after kernel 2.4.1 update
Okay, first of all, please use paragraphs. They exist for a reason :) Since it's too much trouble for me to break things up to present a nice clear, response, you'll have to deal with my babbling. First of all, if your mouse isn't initialized as an IntelliMouse, it pretends it's a regular PS/2 mouse. Second, gpm gets to your mouse before X, so you have to be positive that your mouse type is set to imps2 in /etc/gpm.conf . Third, it sounds like both GPM and X are trying to use /dev/psaux. Check to see what /dev/mouse is linked to. Since you're using GPM and X, specify explicitly in XF86Config[-4] that the mouse device is /dev/gpmdata, not /dev/mouse . Now, try rebooting, after making sure all those config options are set properly. If it still doesn't work, set X to use /dev/psaux, type ImPS/2, 'rm /etc/rc2.d/*gpm' to stop 'gpm' from being started on boot, and then re-boot. Hopefully that will work. If it doesn't, you have problems that arn't caused by X or gpm. The reboots are necessary, and they have to be hard-boots. This is because of the mouse initialization thing. Hope that helps :) To quote Dave Bresson [EMAIL PROTECTED], # # # Hi there, # # # I'm having a problem with my Microsoft Intellimouse (an intellimouse with # two buttons and a scroll wheel that uses the ps/2 interface) since going # from a 2.2.x kernel to 2.4.1. The way i have setup (and how everything # worked perfectly before this upgrade) was that gpm was set to read from # /dev/psaux using the imps2 protocol. It then repeats this to /dev/gpmdata # which i then have /dev/mouse linked to. My XF86Config-4 is setup so that # it knows the mouse is at /dev/mouse, and uses the imPS/2 protocol. I also # have a line for the Zaxis stuff to get the scroll wheel to act like # buttons 4 and 5 in X so that the wheel works. Anyway, all this is well # and good because it was this exact setup that worked before the new # kernel. Anyway, since upgrading the kernel, gpm no longer works on # /dev/psaux with the imps2 protocol (hence, X doesn't work either...). The # mouse just goes all crazy moving all over the place, and pushing random # buttons and what not. So i set gpm and X to use the regular ps/2 # protocol, and everything was fine, however i get no third button or # scroll wheel anymore, which sucks. Just in case this was just a gpm # problem, i tried having X read directly from /dev/psaux using the IMPS/2 # protocol, but unfortunately got the same bad result. Does anyone have any # idea what might be the problem here? It had to have been something i # configured wrong in the kernel...however i don't know what, since it just # made the IMPS/2 stuff not work, while the regular PS/2 still works...very # strange. Any ideas, or tips? # # # thanks, # # # # dave # # # # # -- # To UNSUBSCRIBE, email to [EMAIL PROTECTED] # with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] # David Barclay Harris, Clan Barclay Aut agere, aut mori. (Either action, or death.)
Re: IMPS/2 problems after kernel 2.4.1 update
On Fri, 16 Feb 2001, David B. Harris wrote: Okay, first of all, please use paragraphs. They exist for a reason :) Since it's too much trouble for me to break things up to present a nice clear, response, you'll have to deal with my babbling. Yeah, sorry about that...my babbling doesn't translate well to paragraphs. Ah well... First of all, if your mouse isn't initialized as an IntelliMouse, it pretends it's a regular PS/2 mouse. Right. What do you mean by 'initialized'? You mean initialized as in what gpm.conf and XF86Config-4 have it set as? Or something else? Second, gpm gets to your mouse before X, so you have to be positive that your mouse type is set to imps2 in /etc/gpm.conf . Yep, got that. Third, it sounds like both GPM and X are trying to use /dev/psaux. Check to see what /dev/mouse is linked to. Since you're using GPM and X, specify explicitly in XF86Config[-4] that the mouse device is /dev/gpmdata, not /dev/mouse . Well, since X wants to use /dev/mouse , i made it a sym link to /dev/gpmdata (since that is what gpm is set to repeat to) I guess i probably shoulda stated that it was just a link in my previous email. Now, try rebooting, after making sure all those config options are set properly. If it still doesn't work, set X to use /dev/psaux, type ImPS/2, 'rm /etc/rc2.d/*gpm' to stop 'gpm' from being started on boot, and then re-boot. Hopefully that will work. If it doesn't, you have problems that arn't caused by X or gpm. Okay, i had tried this before, however it was without the reboot, so i tried it again. As it turned out, this fixed it. Pointing X straight to /dev/psaux, and not starting gpm at all did it. Which leads me to believe that gpm doesn't work with the new kernel 2.4.1 i set up, since the old configuration worked just fine with 2.2.18...very strange. Any ideas on why this might be? thanks, dave
Re: IMPS/2 problems after kernel 2.4.1 update
I experienced the same problems with my intellimouse. What you're looking for is quite simple, I guessed at how I could get the new Zaxis line and it worked. =] Section InputDevice # Identifier and driver Identifier Mouse1 Driver mouse Option ProtocolIMPS/2 Option ZAxisMapping 4 5 Option Device /dev/psaux Good luck! Ty On Thu Feb 15/2001 @ 11:02:P -0500, Dave Bresson wrote: Hi there, I'm having a problem with my Microsoft Intellimouse (an intellimouse with two buttons and a scroll wheel that uses the ps/2 interface) since going from a 2.2.x kernel to 2.4.1. The way i have setup (and how everything worked perfectly before this upgrade) was that gpm was set to read from /dev/psaux using the imps2 protocol. It then repeats this to /dev/gpmdata which i then have /dev/mouse linked to. My XF86Config-4 is setup so that it knows the mouse is at /dev/mouse, and uses the imPS/2 protocol. I also have a line for the Zaxis stuff to get the scroll wheel to act like buttons 4 and 5 in X so that the wheel works. Anyway, all this is well and good because it was this exact setup that worked before the new kernel. Anyway, since upgrading the kernel, gpm no longer works on /dev/psaux with the imps2 protocol (hence, X doesn't work either...). The mouse just goes all crazy moving all over the place, and pushing random buttons and what not. So i set gpm and X to use the regular ps/2 protocol, and everything was fine, however i get no third button or scroll wheel anymore, which sucks. Just in case this was just a gpm problem, i tried having X read directly from /dev/psaux using the IMPS/2 protocol, but unfortunately got the same bad result. Does anyone have any idea what might be the problem here? It had to have been something i configured wrong in the kernel...however i don't know what, since it just made the IMPS/2 stuff not work, while the regular PS/2 still works...very strange. Any ideas, or tips? thanks, dave -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Tyler Braun [EMAIL PROTECTED]
Re: IMPS/2 problems after kernel 2.4.1 update
To quote Dave Bresson [EMAIL PROTECTED], # On Fri, 16 Feb 2001, David B. Harris wrote: # Yeah, sorry about that...my babbling doesn't translate well to paragraphs. # Ah well... :) # First of all, if your mouse isn't initialized as an IntelliMouse, it # pretends it's a regular PS/2 mouse. # # Right. What do you mean by 'initialized'? You mean initialized as in # what gpm.conf and XF86Config-4 have it set as? Or something else? Well, it depends on what gets to the mouse first. If X gets to the mouse first, then it'll be initialized as whatever XF86Config-4 has it set to. If gpm gets to it first, it'll be initialized to whatever gpm.conf thinks it is. Anyways, I'm sure this is all very confusing, and it took me nearly a month to figure out what was going on :) Basically, you *have* to make sure that whatever gets to the mouse first initializes it to the highest degree possible. The means using the protocol that most closely matches what the mouse actually uses. # Third, it sounds like both GPM and X are trying to use /dev/psaux. Check # to see what /dev/mouse is linked to. Since you're using GPM and X, # specify explicitly in XF86Config[-4] that the mouse device is # /dev/gpmdata, not /dev/mouse . # # # Well, since X wants to use /dev/mouse , i made it a sym link to # /dev/gpmdata (since that is what gpm is set to repeat to) I guess i # probably shoulda stated that it was just a link in my previous email. I had thought this ... but since 'gpm' and X were conflicting, I wasn't sure. Are you using devfs with devfsd? Double-check the /dev/mouse is a symlink to /dev/gpmdata. Using devfsd, changes arn't always kept over a reboot. # Now, try rebooting, after making sure all those config options are set # properly. If it still doesn't work, set X to use /dev/psaux, type # ImPS/2, 'rm /etc/rc2.d/*gpm' to stop 'gpm' from being started on boot, # and then re-boot. Hopefully that will work. If it doesn't, you have # problems that arn't caused by X or gpm. # # Okay, i had tried this before, however it was without the reboot, so i # tried it again. As it turned out, this fixed it. Pointing X straight to # /dev/psaux, and not starting gpm at all did it. Which leads me to believe # that gpm doesn't work with the new kernel 2.4.1 i set up, since the old # configuration worked just fine with 2.2.18...very strange. Any ideas on # why this might be? Yup, I figured a reboot would fix it. :) It's that bloody initialization thing. I don't think it's a problem with gpm and 2.4.x. I'm running 2.4.1-ac15, with devfs, but without devfsd and it works fine. I think that if gpm.conf is set to use the imps2 protocol, it should work. Just to humour me, try explicitly stating in /etc/X11/XF86Config-4 that X should use /dev/gpmdata. Make sure 'gpm' starts at boot time, and re-boot. If that doesn't work, feel free to contact me for more help :) David Barclay Harris, Clan Barclay Aut agere, aut mori. (Either action, or death.)
IMPS/2 problems after kernel 2.4.1 update
Hi there, I'm having a problem with my Microsoft Intellimouse (an intellimouse with two buttons and a scroll wheel that uses the ps/2 interface) since going from a 2.2.x kernel to 2.4.1. The way i have setup (and how everything worked perfectly before this upgrade) was that gpm was set to read from /dev/psaux using the imps2 protocol. It then repeats this to /dev/gpmdata which i then have /dev/mouse linked to. My XF86Config-4 is setup so that it knows the mouse is at /dev/mouse, and uses the imPS/2 protocol. I also have a line for the Zaxis stuff to get the scroll wheel to act like buttons 4 and 5 in X so that the wheel works. Anyway, all this is well and good because it was this exact setup that worked before the new kernel. Anyway, since upgrading the kernel, gpm no longer works on /dev/psaux with the imps2 protocol (hence, X doesn't work either...). The mouse just goes all crazy moving all over the place, and pushing random buttons and what not. So i set gpm and X to use the regular ps/2 protocol, and everything was fine, however i get no third button or scroll wheel anymore, which sucks. Just in case this was just a gpm problem, i tried having X read directly from /dev/psaux using the IMPS/2 protocol, but unfortunately got the same bad result. Does anyone have any idea what might be the problem here? It had to have been something i configured wrong in the kernel...however i don't know what, since it just made the IMPS/2 stuff not work, while the regular PS/2 still works...very strange. Any ideas, or tips? thanks, dave
