winter break
[this email is almost entirely useless.] I am off for winter break in a very short time. Once the debian web servers are back online, I am going to unsubscribe from debian-x -- best of luck to the regulars covering the myriad questions people manage to ask. :) I figured a heads-up was in order :) I hope to resubscribe again in about one month. Thanks again everyone. -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.''
usb mice in 4.0.1-12
Is anyone else using a USB mouse with 4.0.1-12? I have got it working with
gpm from console, so I know I have all the modules running (under 2.4.0-t12),
but when I stop gpm and try to use the device, /dev/input/mouse0 directly, it
dosen't work.
Now I have read and re-read /usr/share/doc/xserver-xfree86/README.mouse.gz,
part 6.2, and it says to use "Protocol" "usb" or "Protocol" "Auto". When
I use auto, the log file from gdm says "unable to detect protocol" or similar.
I get my gdm login, but my mouse won't wiggle a pixel.
More disturbing is that when I specify the protocol to be "usb", gdm crashes
repeatedly until it exceeds its refresh count, and then shuts down for
a few minutes before trying again. Looking at the log file says:
(EE) Mouse0: Unknown protocol "usb"
(EE) PreInit failed for input device "Mouse0"
Is there a trick here to using the USB driver in 4.0.1 that I have missed?
The Mouse itself is a M$ IntelliExplorer USB opticla mouse: four buttons,
and a wheel ("Buttons" "7"). This is an i386 boxen. X has been working
fine with the older /dev/ttyS0 serial mouse.
TIA.
James
--
James Bromberger www.rcpt.to/~james
IT, Pelican Manufacturing - www.pelicanmanufacturing.com.au
Snr Web Systems Admin, JDV - www.jdv.com * www.hartleypoynton.com.au
Remainder moved to http://www.rcpt.to/~james/james/sig.html
Re: usb mice in 4.0.1-12
On Sun, Dec 17, 2000 at 01:52:35AM +0800, James Bromberger wrote: > Is anyone else using a USB mouse with 4.0.1-12? I have got it working with > gpm from console, so I know I have all the modules running (under 2.4.0-t12), > but when I stop gpm and try to use the device, /dev/input/mouse0 directly, it > dosen't work. Read some more. :) /dev/input/mouse? and /dev/input/mice are PS/2 "compatible" interfaces. Please see /usr/src/linux/Documentation/usb/input.txt for details: you basically use /dev/input/mouse0 and protocol "ImPS/2" as well as the ZAxisMapping line to enable your scrolley thingy. -- charl p. botha | computer graphics and cad/cam http://cpbotha.net/ | http://www.cg.its.tudelft.nl/
Re: usb mice in 4.0.1-12
On Sat, Dec 16, 2000 at 07:00:52PM +0100, Charl P. Botha wrote: > On Sun, Dec 17, 2000 at 01:52:35AM +0800, James Bromberger wrote: > Read some more. :) /dev/input/mouse? and /dev/input/mice are PS/2 > "compatible" interfaces. > Please see /usr/src/linux/Documentation/usb/input.txt for details: you > basically use /dev/input/mouse0 and protocol "ImPS/2" as well as the > ZAxisMapping line to enable your scrolley thingy. For sale: one old serial mouse. Yippee. Thanks Charl; it's working like a charm: buttons on the side & wheel even bring up Settings and User Menu in Enlightenment! So if is the compatible device, where is the real device? Is it ? Is that speaking the 'usb' protocol as mentioned in the /usr/share/doc/xserver-xfree86/README.mouse.gz documentation? Ta, James -- James Bromberger www.rcpt.to/~james IT, Pelican Manufacturing - www.pelicanmanufacturing.com.au Snr Web Systems Admin, JDV - www.jdv.com * www.hartleypoynton.com.au Remainder moved to http://www.rcpt.to/~james/james/sig.html
Re: usb mice in 4.0.1-12
On Sun, Dec 17, 2000 at 02:11:43AM +0800, James Bromberger wrote: > On Sat, Dec 16, 2000 at 07:00:52PM +0100, Charl P. Botha wrote: > > On Sun, Dec 17, 2000 at 01:52:35AM +0800, James Bromberger wrote: > > Read some more. :) /dev/input/mouse? and /dev/input/mice are PS/2 > > "compatible" interfaces. > > Please see /usr/src/linux/Documentation/usb/input.txt for details: you > > basically use /dev/input/mouse0 and protocol "ImPS/2" as well as the > > ZAxisMapping line to enable your scrolley thingy. > > For sale: one old serial mouse. > > Yippee. Thanks Charl; it's working like a charm: buttons on the > side & wheel even bring up Settings and User Menu in Enlightenment! > > So if is the compatible device, where is the real device? > Is it ? Is that speaking the 'usb' protocol as mentioned > in the /usr/share/doc/xserver-xfree86/README.mouse.gz documentation? I'm glad it works. AFAICR, linux doesn't yet have a native usb mouse device abstraction, unless you count the generic usb input API. According to the mouse docs in XFree86 as well, the usb protocol support hasn't been tested/is unknown under linux. You're not losing anything by making use of the /dev/input/mouse? devices however. Enjoy the higher sampling rate of your usb mouse! -- charl p. botha | computer graphics and cad/cam http://cpbotha.net/ | http://www.cg.its.tudelft.nl/
Unidentified subject!
unsubscribe
Re: dpkg having serious trouble trying to upgrade xlibs
"Antonio M. D'souza" wrote: > Ok, now I'm at a total loss! > I tried to remove ghostview as it contained a symlink that was conflicting > with xlibs but it gave me this (meaning I can no longer remove anything): > > quikbox:/home/quik# apt-get remove ghostview > Reading Package Lists... Done > Building Dependency Tree... Done > You might want to run `apt-get -f install' to correct these: > Sorry, but the following packages have unmet dependencies: > libxaw6: Depends: xlibs (>= 4.0.1-11) but 4.0.1-4 is to be installed > libxaw7: Depends: xlibs (>= 4.0.1-11) but 4.0.1-4 is to be installed > twm: Depends: xlibs (>= 4.0.1-11) but 4.0.1-4 is to be installed > xbase-clients: Depends: xlibs (>= 4.0.1-11) but 4.0.1-4 is to be installed > E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify > a solution). > quikbox:/home/quik# > > On December 15, 2000 06:42 pm, you wrote: > > Hallo, > > > > If you have a symlink from /usr/X11R6/lib/X11/app-defaults to > > etc/X11/app-defaults, then remove this symlink and try the install > > again. > > > > This has worked for me. > > See the post (problem with your Debian packages) on the list > > > > Good Luck > > > > > > Reiner Stallknecht > > -- > Antonio M. D'souza > Math/CS 725-7651 > St. Pauls, rm 105 N2L 3G5 > http://quikbox.dyndns.org Well, something is very wrong, you have no X anymore:-( Please don't do it the hard-way, like i did (I've removed all the X-depending stuff incl. X itself) my fault, still catching up to woody This problem i got after upgrading X (from XF4.0.1-10 to XF4.0.1-11pre-version 2) from brandens site. Before the update i have made the symlink from /usr/X11R6/lib/X11/app-defaults to etc/X11/app-defaults. After reinstall of X (4.01-10.deb's) the same problem. And this is very strange because i had a running XF4.0.1-10 before the upgrade got wrong. The solution for me was: removing the symlink from /usr/X11R6/lib/X11/app-defaults to etc/X11/app-defaults. And mkdir /usr/X11R6/lib/X11/app-defaults. Then apt-get -f install Then apt-get update Did you tried 'apt-get -f install' ? I could be wrong with this "solution" but this worked for me. Anyone here who can verify this or has the right solution? Maybe it is not X-related? Good Luck Reiner Stallknecht
Re: dpkg having serious trouble trying to upgrade xlibs
Hello, all- I've had similar but sporadic dependency problems with the new X debs. apt-get hasn't been too successful in resolving things properly, even when the dependencies indicate a solution. My guess is that the complexity of X dependencies is really pushing apt-get, and apt-get -f is no help. But I'm no packaging expert If apt-get remove doesn't work right, due to what looks to be some sort of race condition while thinking too much, try dpkg -r instead. You should then be able to continue with apt-get install or update. Lastly, apt-get install the temporarily removed package once xlibs et al. have been completely setup. At least, that's what worked for me. -Dave Barnett On Sun, 17 Dec 2000, reiner wrote: > "Antonio M. D'souza" wrote: > > > Ok, now I'm at a total loss! > > I tried to remove ghostview as it contained a symlink that was conflicting > > with xlibs but it gave me this (meaning I can no longer remove anything): > > > > quikbox:/home/quik# apt-get remove ghostview > > Reading Package Lists... Done > > Building Dependency Tree... Done > > You might want to run `apt-get -f install' to correct these: > > Sorry, but the following packages have unmet dependencies: > > libxaw6: Depends: xlibs (>= 4.0.1-11) but 4.0.1-4 is to be installed > > libxaw7: Depends: xlibs (>= 4.0.1-11) but 4.0.1-4 is to be installed > > twm: Depends: xlibs (>= 4.0.1-11) but 4.0.1-4 is to be installed > > xbase-clients: Depends: xlibs (>= 4.0.1-11) but 4.0.1-4 is to be installed > > E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify > > a solution). > > quikbox:/home/quik# > >
Re: dpkg having serious trouble trying to upgrade xlibs
Dave, I had to put in this:
DPkg::Options {"--force-overwrite";};
into /etc/apt/apt.conf. It's worked quite well for me.
--
** Derek J Witt**
* Email: mailto:[EMAIL PROTECTED] *
* Home Page: http://www.flinthills.com/~djw/ *
*** "Houston, the Eagle has landed and laid an egg!" -- Unknown **
usb mice in 4.0.1-12
Is anyone else using a USB mouse with 4.0.1-12? I have got it working with
gpm from console, so I know I have all the modules running (under 2.4.0-t12),
but when I stop gpm and try to use the device, /dev/input/mouse0 directly, it
dosen't work.
Now I have read and re-read /usr/share/doc/xserver-xfree86/README.mouse.gz,
part 6.2, and it says to use "Protocol" "usb" or "Protocol" "Auto". When
I use auto, the log file from gdm says "unable to detect protocol" or similar.
I get my gdm login, but my mouse won't wiggle a pixel.
More disturbing is that when I specify the protocol to be "usb", gdm crashes
repeatedly until it exceeds its refresh count, and then shuts down for
a few minutes before trying again. Looking at the log file says:
(EE) Mouse0: Unknown protocol "usb"
(EE) PreInit failed for input device "Mouse0"
Is there a trick here to using the USB driver in 4.0.1 that I have missed?
The Mouse itself is a M$ IntelliExplorer USB opticla mouse: four buttons,
and a wheel ("Buttons" "7"). This is an i386 boxen. X has been working
fine with the older /dev/ttyS0 serial mouse.
TIA.
James
--
James Bromberger www.rcpt.to/~james
IT, Pelican Manufacturing - www.pelicanmanufacturing.com.au
Snr Web Systems Admin, JDV - www.jdv.com * www.hartleypoynton.com.au
Remainder moved to http://www.rcpt.to/~james/james/sig.html
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: usb mice in 4.0.1-12
On Sun, Dec 17, 2000 at 01:52:35AM +0800, James Bromberger wrote: > Is anyone else using a USB mouse with 4.0.1-12? I have got it working with > gpm from console, so I know I have all the modules running (under 2.4.0-t12), > but when I stop gpm and try to use the device, /dev/input/mouse0 directly, it > dosen't work. Read some more. :) /dev/input/mouse? and /dev/input/mice are PS/2 "compatible" interfaces. Please see /usr/src/linux/Documentation/usb/input.txt for details: you basically use /dev/input/mouse0 and protocol "ImPS/2" as well as the ZAxisMapping line to enable your scrolley thingy. -- charl p. botha | computer graphics and cad/cam http://cpbotha.net/ | http://www.cg.its.tudelft.nl/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: usb mice in 4.0.1-12
On Sat, Dec 16, 2000 at 07:00:52PM +0100, Charl P. Botha wrote: > On Sun, Dec 17, 2000 at 01:52:35AM +0800, James Bromberger wrote: > Read some more. :) /dev/input/mouse? and /dev/input/mice are PS/2 > "compatible" interfaces. > Please see /usr/src/linux/Documentation/usb/input.txt for details: you > basically use /dev/input/mouse0 and protocol "ImPS/2" as well as the > ZAxisMapping line to enable your scrolley thingy. For sale: one old serial mouse. Yippee. Thanks Charl; it's working like a charm: buttons on the side & wheel even bring up Settings and User Menu in Enlightenment! So if is the compatible device, where is the real device? Is it ? Is that speaking the 'usb' protocol as mentioned in the /usr/share/doc/xserver-xfree86/README.mouse.gz documentation? Ta, James -- James Bromberger www.rcpt.to/~james IT, Pelican Manufacturing - www.pelicanmanufacturing.com.au Snr Web Systems Admin, JDV - www.jdv.com * www.hartleypoynton.com.au Remainder moved to http://www.rcpt.to/~james/james/sig.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: usb mice in 4.0.1-12
On Sun, Dec 17, 2000 at 02:11:43AM +0800, James Bromberger wrote: > On Sat, Dec 16, 2000 at 07:00:52PM +0100, Charl P. Botha wrote: > > On Sun, Dec 17, 2000 at 01:52:35AM +0800, James Bromberger wrote: > > Read some more. :) /dev/input/mouse? and /dev/input/mice are PS/2 > > "compatible" interfaces. > > Please see /usr/src/linux/Documentation/usb/input.txt for details: you > > basically use /dev/input/mouse0 and protocol "ImPS/2" as well as the > > ZAxisMapping line to enable your scrolley thingy. > > For sale: one old serial mouse. > > Yippee. Thanks Charl; it's working like a charm: buttons on the > side & wheel even bring up Settings and User Menu in Enlightenment! > > So if is the compatible device, where is the real device? > Is it ? Is that speaking the 'usb' protocol as mentioned > in the /usr/share/doc/xserver-xfree86/README.mouse.gz documentation? I'm glad it works. AFAICR, linux doesn't yet have a native usb mouse device abstraction, unless you count the generic usb input API. According to the mouse docs in XFree86 as well, the usb protocol support hasn't been tested/is unknown under linux. You're not losing anything by making use of the /dev/input/mouse? devices however. Enjoy the higher sampling rate of your usb mouse! -- charl p. botha | computer graphics and cad/cam http://cpbotha.net/ | http://www.cg.its.tudelft.nl/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Unidentified subject!
unsubscribe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dpkg having serious trouble trying to upgrade xlibs
"Antonio M. D'souza" wrote: > Ok, now I'm at a total loss! > I tried to remove ghostview as it contained a symlink that was conflicting > with xlibs but it gave me this (meaning I can no longer remove anything): > > quikbox:/home/quik# apt-get remove ghostview > Reading Package Lists... Done > Building Dependency Tree... Done > You might want to run `apt-get -f install' to correct these: > Sorry, but the following packages have unmet dependencies: > libxaw6: Depends: xlibs (>= 4.0.1-11) but 4.0.1-4 is to be installed > libxaw7: Depends: xlibs (>= 4.0.1-11) but 4.0.1-4 is to be installed > twm: Depends: xlibs (>= 4.0.1-11) but 4.0.1-4 is to be installed > xbase-clients: Depends: xlibs (>= 4.0.1-11) but 4.0.1-4 is to be installed > E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify > a solution). > quikbox:/home/quik# > > On December 15, 2000 06:42 pm, you wrote: > > Hallo, > > > > If you have a symlink from /usr/X11R6/lib/X11/app-defaults to > > etc/X11/app-defaults, then remove this symlink and try the install > > again. > > > > This has worked for me. > > See the post (problem with your Debian packages) on the list > > > > Good Luck > > > > > > Reiner Stallknecht > > -- > Antonio M. D'souza > Math/CS 725-7651 > St. Pauls, rm 105 N2L 3G5 > http://quikbox.dyndns.org Well, something is very wrong, you have no X anymore:-( Please don't do it the hard-way, like i did (I've removed all the X-depending stuff incl. X itself) my fault, still catching up to woody This problem i got after upgrading X (from XF4.0.1-10 to XF4.0.1-11pre-version 2) from brandens site. Before the update i have made the symlink from /usr/X11R6/lib/X11/app-defaults to etc/X11/app-defaults. After reinstall of X (4.01-10.deb's) the same problem. And this is very strange because i had a running XF4.0.1-10 before the upgrade got wrong. The solution for me was: removing the symlink from /usr/X11R6/lib/X11/app-defaults to etc/X11/app-defaults. And mkdir /usr/X11R6/lib/X11/app-defaults. Then apt-get -f install Then apt-get update Did you tried 'apt-get -f install' ? I could be wrong with this "solution" but this worked for me. Anyone here who can verify this or has the right solution? Maybe it is not X-related? Good Luck Reiner Stallknecht -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dpkg having serious trouble trying to upgrade xlibs
Hello, all- I've had similar but sporadic dependency problems with the new X debs. apt-get hasn't been too successful in resolving things properly, even when the dependencies indicate a solution. My guess is that the complexity of X dependencies is really pushing apt-get, and apt-get -f is no help. But I'm no packaging expert If apt-get remove doesn't work right, due to what looks to be some sort of race condition while thinking too much, try dpkg -r instead. You should then be able to continue with apt-get install or update. Lastly, apt-get install the temporarily removed package once xlibs et al. have been completely setup. At least, that's what worked for me. -Dave Barnett On Sun, 17 Dec 2000, reiner wrote: > "Antonio M. D'souza" wrote: > > > Ok, now I'm at a total loss! > > I tried to remove ghostview as it contained a symlink that was conflicting > > with xlibs but it gave me this (meaning I can no longer remove anything): > > > > quikbox:/home/quik# apt-get remove ghostview > > Reading Package Lists... Done > > Building Dependency Tree... Done > > You might want to run `apt-get -f install' to correct these: > > Sorry, but the following packages have unmet dependencies: > > libxaw6: Depends: xlibs (>= 4.0.1-11) but 4.0.1-4 is to be installed > > libxaw7: Depends: xlibs (>= 4.0.1-11) but 4.0.1-4 is to be installed > > twm: Depends: xlibs (>= 4.0.1-11) but 4.0.1-4 is to be installed > > xbase-clients: Depends: xlibs (>= 4.0.1-11) but 4.0.1-4 is to be installed > > E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify > > a solution). > > quikbox:/home/quik# > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dpkg having serious trouble trying to upgrade xlibs
Dave, I had to put in this:
DPkg::Options {"--force-overwrite";};
into /etc/apt/apt.conf. It's worked quite well for me.
--
** Derek J Witt**
* Email: mailto:[EMAIL PROTECTED] *
* Home Page: http://www.flinthills.com/~djw/ *
*** "Houston, the Eagle has landed and laid an egg!" -- Unknown **
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
winter break
[this email is almost entirely useless.] I am off for winter break in a very short time. Once the debian web servers are back online, I am going to unsubscribe from debian-x -- best of luck to the regulars covering the myriad questions people manage to ask. :) I figured a heads-up was in order :) I hope to resubscribe again in about one month. Thanks again everyone. -- ``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really impressed down here, I can tell you.'' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
