Re: dexter and microsoft wheelmouse optical ?
ok, the problem was, that the mouse won't work, if gpm is started. with /etc/init.d/gpm stop bevor startx the mouse works, shouldn't this done by startx? chris hi i use the microsoft wheelmouse optical and isntalled a new woody with 4.0.1-2 debs, didn't have 3.3.6 on this computer before! so gpm works without any problem, but under dexter none of the mouse drivers r working under X. the mouse worked for me under the pre2 4.0.1 debs, so the mouse works under X, so this is should not be an XF4.0.1 problem, more a dexter problem, or? thx chris p.s.: the mouse port is the same under gpm an X, so it must be correct :-) --- SPENER Christian e-mail: [EMAIL PROTECTED] snail-mail: A-8010 GRAZ, Schanzelgasse 19 tel: ++43 316 362283 cell phone: ++43 664 3846526 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: dexter and USB mouse
On Sat, Nov 04, 2000 at 09:21:03PM -0800, Kimball Thurston wrote: I upgraded to 4.0.1 packages in woody this morning and have had quite a few problems, but the one I thought I'd ask about is with my USB mouse (an Intellimouse Explorer). If I choose USB mouse, when I start X, it gives an unknown protocol error - I had this same problem with my own compile of XF86 4.0, and could never figure it out... If I use "ImPS/2", things work just fine... AIUI, USBmouse is effectively useless under Linux. The new input layer allows USB mice to appear as standard PS/2 ones to userspace apps. Incidentally, if ImPS/2 doesn't give you access to all the buttons on the mouse then try netmouseps/2 instead. -- Matthew Garrett | [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dexter making assumptions about font server (and screen resolution)
Branden Robinson wrote: FontPathunix/:7100 # local font server Yes. Read the next line as well. X refused to start. The screen went blank and then nothing happened. Commenting out the FontPath line above made it work again. I seriously doubt this. If the font server isn't running and there are other font path elements defined, the X server will try to use them. Yes, that's how I thought it would work, which is one of the reasons I thought the error was somewhere else. What can I say? I started with a basic, dexter-generated XF86Config-4. X hung. After trying several other things first I removed that line. X worked. I put the line back. X hung. And so on. Ok, so I jumped to conclusions. Since then I've repeated the above experiment with the same result. I've also tried putting the line back and installing the font server. X worked (once I remembered to actually start the font server). But I also tried it without the font server, but with kernel version 2.2.17 instead of 2.4.0-test9, and with that setup X also worked. I'm no longer sure what to believe. I'm not aware of any major differences in configuration between the two kernels. (Some pathetic testing with tcplisten/tcpconnect yielded the same result on both.) Ah, you mean something that which already exists as the medium option in the monitor configuration section? Exactly. I couldn't find any setting that affected the Modes line in the Screen section, and I didn't realize there were other ways to affect the screen resolution. I'm sorry, I made a foolish assumption. I plead insanity. Or incompetence. (Judging by your comments I should have an iron-clad case either way.) Torbjörn Andersson
Re: dexter making assumptions about font server (and screen resolution)
On Sun, Oct 22, 2000 at 03:45:41PM +0200, Torbjörn Andersson wrote:
Dexter seems to assume that I am running a local font server, which
I'm not.
It doesn't assume you do, it assumes you CAN, which is true.
The problem is that as long as my XF86Config-4 contained the
line
FontPathunix/:7100 # local font server
Yes. Read the next line as well.
X refused to start. The screen went blank and then nothing happened.
Commenting out the FontPath line above made it work again.
I seriously doubt this. If the font server isn't running and there are
other font path elements defined, the X server will try to use them.
While I view the output from dexter as friendly advice, rather than a
final decision, this was by no means obvious to me. Perhaps it should
have been, but... The last line in my /var/log/XFree86.0.log was
(II) XINPUT: Adding extended input device Generic Mouse (type: MOUSE)
which had me barking up the wrong tree since I thought it meant there
was something wrong with the mouse configuration.
If you think input device drivers and mice have anything to do with fonts,
then you're probably in need of more help than I or dexter can give you.
This happens both in phase2v17 and phase2v20. (I know this because at
first I thought it was a problem with the CVS snapshot that v20 is
based on, so I reverted back to v17 only to find that it still didn't
work. Had me worried for a while there, I can tell you.)
Dexter is icing. You don't need it at all. You're perfectly free to write
your own XF86Config{-4} file from scratch.
If you don't like what Dexter does, abort it when it runs and write your
own XF86Config file.
(I know this isn't a support list, but is there any reason I should
have a font server installed, considering that my computer isn't
connected to any network whatsoever?)
Yes. The X server won't hang all your clients while rasterizing a font.
I don't know what the future plans for Dexter are, but it would be
nice if it would let me choose maximum screen resolution since the
default behaviour apparently is to give me 1920x1440 which is far too
much for my taste. Maybe something as simple as this would work...
[...]
Ah, you mean something that which already exists as the medium option in
the monitor configuration section?
But apart from these problems, Xnest crashing, and some DRI-related issues
(which I shouldn't bring up here anyway), X has been working flawlessly. My
thanks to the XFree86 team, Branden, and whoever else is making this
possible.
I appreciate your thanks, but your criticism would be more constructive if
it were better informed.
--
G. Branden Robinson |
Debian GNU/Linux|It tastes good.
[EMAIL PROTECTED] |-- Bill Clinton
http://www.debian.org/~branden/ |
pgp1UBEYCvn8d.pgp
Description: PGP signature
Re: dexter making assumptions about font server (and screen resol ution)
Branden Robinson [EMAIL PROTECTED] writes: On Sun, Oct 22, 2000 at 03:45:41PM +0200, Torbjörn Andersson wrote: Dexter seems to assume that I am running a local font server, which I'm not. It doesn't assume you do, it assumes you CAN, which is true. The problem is that as long as my XF86Config-4 contained the line FontPathunix/:7100 # local font server Yes. Read the next line as well. X refused to start. The screen went blank and then nothing happened. Commenting out the FontPath line above made it work again. I seriously doubt this. If the font server isn't running and there are other font path elements defined, the X server will try to use them. I've had the same happen on me with 3.3.6-10 on an out-of-the-box potato. For some odd reason the font server (xfs-xtt) crashed and after I logged out, gdm never got around to showing a login dialog. Turned out that the X server kept crashing with a can't find font fixed message (well something to that extent). FYI, my XF86Config says amongst other things: Section Files RgbPath/usr/X11R6/lib/X11/rgb FontPath unix/:7100 FontPath /usr/X11R6/lib/X11/fonts/misc/ EndSection and I have at least the following fonts packages installed: ii xfonts-75dpi 3.3.6-275 dpi fonts for X ii xfonts-base3.3.6-2standard fonts for X ii xfonts-scalabl 3.3.6-2scalable fonts for X -- Olaf Meeuwissen Epson Kowa Corporation, Research and Development
Re: dexter wishlist item
On Thu, Oct 19, 2000 at 10:47:57AM -0500, Michael Urman wrote: Since the upgrade to X 4.0.1, my monitor wouldn't power off like it would under 3.3.6. Finally someone pointed me the way of Option DPMS on in Section Monitor Is this something that could either be added to dexter's default configuration file, or at least listed as an option (if it causes problems on some hardware or something)? Yes, this will be in the forthcoming v20; thanks for the suggestion. -- G. Branden Robinson | Debian GNU/Linux| If existence exists, [EMAIL PROTECTED] | why create a creator? http://www.debian.org/~branden/ | pgpFmN8KFv1lc.pgp Description: PGP signature
Re: dexter and devfs
On Mon, Oct 16, 2000 at 01:38:03AM -0500, Branden Robinson wrote: If someone gives me some (POSIX) shell scriptage, invoking no commands that aren't in essential packages, which will decisively determine whether or not a system is using devfs, I will add support for devfs filenames in the mouse configuration section. You mean something like 'grep devfs /proc/mounts 21 /dev/null echo Yes'? Zephaniah E. Hull. snip -- G. Branden Robinson | To stay young requires unceasing Debian GNU/Linux| cultivation of the ability to unlearn [EMAIL PROTECTED] | old falsehoods. http://www.debian.org/~branden/ | -- Robert Heinlein -- PGP EA5198D1-Zephaniah E. Hull [EMAIL PROTECTED]-GPG E65A7801 Keys available at http://whitestar.soark.net/~warp/public_keys. CCs of replies from mailing lists are encouraged. Welcome to [telco] hell. [...] You are in a maze of twisty little PVC's, all alike. A switching engineer throws a dart at you! -- Chris Saunderson [EMAIL PROTECTED] in the scary.devil.monastery PGP signature
Re: dexter and devfs
I also found this to work as well: === #!/bin/sh DEVFS=`grep devfs /proc/filesystems | cut -f2` [ $DEVFS = "devfs" ] echo "You're using devfs. :-)" === Looks like it's going to be a simple thing to test anyway we do it. :-) ** Derek J Witt ** * Email: mailto:[EMAIL PROTECTED] * * Home Page: http://www.flinthills.com/~djw/ * *** "...and on the eighth day, God met Bill Gates." - Unknown ** -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: dexter and devfs
On Mon, Oct 16, 2000 at 01:38:03AM -0500, Branden Robinson wrote: If someone gives me some (POSIX) shell scriptage, invoking no commands that aren't in essential packages, which will decisively determine whether or not a system is using devfs, I will add support for devfs filenames in the mouse configuration section. You mean something like 'grep devfs /proc/mounts 21 /dev/null echo Yes'? Zephaniah E. Hull. snip -- G. Branden Robinson | To stay young requires unceasing Debian GNU/Linux| cultivation of the ability to unlearn [EMAIL PROTECTED] | old falsehoods. http://www.debian.org/~branden/ | -- Robert Heinlein -- PGP EA5198D1-Zephaniah E. Hull [EMAIL PROTECTED]-GPG E65A7801 Keys available at http://whitestar.soark.net/~warp/public_keys. CCs of replies from mailing lists are encouraged. Welcome to [telco] hell. [...] You are in a maze of twisty little PVC's, all alike. A switching engineer throws a dart at you! -- Chris Saunderson [EMAIL PROTECTED] in the scary.devil.monastery pgpkNA68w7T6M.pgp Description: PGP signature
Re: dexter and devfs
I also found this to work as well: === #!/bin/sh DEVFS=`grep devfs /proc/filesystems | cut -f2` [ $DEVFS = devfs ] echo You're using devfs. :-) === Looks like it's going to be a simple thing to test anyway we do it. :-) ** Derek J Witt ** * Email: mailto:[EMAIL PROTECTED] * * Home Page: http://www.flinthills.com/~djw/ * *** ...and on the eighth day, God met Bill Gates. - Unknown **
Re: dexter and devfs
On Mon, Oct 16, 2000 at 02:41:00AM -0500, Derek J Witt wrote: I also found this to work as well: === #!/bin/sh DEVFS=`grep devfs /proc/filesystems | cut -f2` [ $DEVFS = devfs ] echo You're using devfs. :-) Needs to be more complex: #!/bin/sh # They may have more than one mounted, but always use the first DEVFS=$(egrep ' devfs ' /proc/mounts | head -1 | cut -f2) # No, devfsd does not have to be running for this to work. The file exists # for devfsd's usage, and is the same test that devfsd uses to make sure # it is operating on a devfs mount (did I say devfs enough?). if [ $DEVFS != ] [ -f $DEVFS/.devfsd ]; then # we have devfs mounted, use it fi # ---end--- This makes sure they have it, and it is mounted. Note, if they have devfsd actually running, then they should be able to use the old devices, but that isn't guaranteed. Good thing about devfs, if the device exists, that driver is installed and working. So things like this are then possible: [ -f $DEVFS/misc/sunmouse ] ... # add sunmouse as an option [ -f $DEVFS/misc/psaux ] ... # add the ps/2 options Also, if only one option is present then you can either use it blindly, or be nice enough to ask the user about it or an other entry. Branden, let me take this time to point out that sunmouse means either BusMouse or PS/2 (I'm adding a patch so we can actually say SunMouse or Sun, but it all points to BusMouse, just like in 3.3.6). PS/2 is just like the one on your Ultra. BTW, did you get the ati driver working? :) Ben -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---'
Re: dexter, phase2v17
On Sat, Oct 14, 2000 at 11:11:13AM -0700, [EMAIL PROTECTED] wrote: I may set up a second machine just for testing. So far, the mouse chooser can still use a few more defined devices. The default mouse type for /dev/gpmdata should be IntelliMouse as far as I know. What's the default mouse type for USB? is HID mouse all one protocol according to the mouse driver, or can it autodetect? USB mice (under 2.4) seem to work happily with either ImPS/2 or netmouseps/2. The first only lets me use 3 of the buttons on my Intellimouse Explorer, but netmouseps/2 gets them all working. I can't see any real reason not to make netmouseps/2 the default provided that it works in 2.2 as well. -- Matthew Garrett | [EMAIL PROTECTED]
Re: dexter, mouse port
I think I'm going to like dexter as well. I do have a couple of wish list recommendations with it while fully acknowledging that it is brand spanking new. Kudos to Branden for doing such a bangup job. I'd also like to mention my appreciation for his sometimes crass sense of humor, like having us type, I obey. when we install/upgrade the beta 4.0.1 debs. 1)The main thing I ran into has to do with my usb mouse. The dexter script offers /dev/usbmouse to handle the usb mouse under X but, per documentation at: http://www.linux-usb.org/USB-guide/book1.html I have had my USB mouse configured and set in my XF86Config to /dev/input/mice. I haven't had a chance to fix things after I upgraded to the latest beta last night but this momentarily has prevented me from getting X to work at home. While I bring this up, I haven't played with linux USB shite for any length of time and I might just be incredibly dense. ;-j 2)I'd love to see dexter offer a 60hz option for 1600x1200 as that's what I run my monitor at. Many other resolutions have the 60hz option already in dexter. This is not some pressing necessity, obviously, but I bet a number of users are like me and settle for a minimal refresh rate in order to get the higher resolution. I know, this is a petty recommendation but it might affect enough people to be considered anyway. * Florian Friesdorf ([EMAIL PROTECTED]) [001011 18:44] wrote: Hi, I think I'm going to like dexter, but at the moment it's missing /dev/gpmdata in the mouse port selection menu. -ff -- Florian Friesdorf [EMAIL PROTECTED] OpenPGP key available on public key servers -- Save the future of Open Source -- - Online-Petition against Software Patents - -- http://petition.eurolinux.org --- -- -Grant oio` See them clamber, these nimble apes! They clamber over one another, and thus scuffle into the mud and the abyss.--Nietzsche ioi`
Re: dexter
On Tue, Oct 10, 2000 at 08:00:57PM -0700, Seth Arnold wrote: Hey, Dexter looks pretty cool; Thanks. my one suggestion is it should have a ``I have a working XF86Config file already'' option near the front of it, or ``install a default and useless XF86Config file for me''. If you want them hidden behind an ``expert'' button, that would be fine by me. Well, Dexter has simply replaced the old script xserver-configure. It is only run if the config file is not present (you can confirm this by reading the xserver-* package postinst script). The confusing thing here is that the XFree86 4.x server uses XF86Config-4 preferentially, but will fall back to XF86Config (man XF86Config). The XF86Config file formats are not completely compatible between versions 3.x and 4.x, and we still have to support some of the old 3.x servers, so it is necessary to use XF86Config-4 for the new server. If you have already written a 4.x XF86Config file, I suggest moving it to /etc/X11/XF86Config-4. I do not support upgrades between versions of these experimental packages; that is the main problem that people are seeing. Upgraders from the potato X packages, and fresh installs, will work fine. When they install xserver-xfree86 for the first time it is pretty darn unlikely that they will already have a 4.x-style /etc/X11/XF86Config file. In the (also unlikely) event they already have a /etc/X11/XF86Config-4, Dexter won't run, figuring that someone has already configured the server. Likewise, the suriving 3.x X servers assume that an existing /etc/X11/XF86Config is valid for the 3.x X server(s) you are installing. This will be true (unless it was already broken) for the few people who are upgrading but having to stay with the 3.x server (mostly really old hardware). Everyone else will need to switch X servers to xserver-xfree86, which looks for /etc/X11/XF86Config-4, which won't yet exist, and Dexter will give them a jump start. In other words, I think the scenario you describe is pretty likely to be confined to people who have been using the phase2 packages. Somehow, I have this feeling that my setup is a bit too strange to expect dexter to handle it well (dualhead g400 using matrox's driver). (When I don't have homework to work on, I shall give dexter a proper test drive. :) It is not intended to be a general XF86Config file generator. It is a very rudimentary tool that is the result of some of my Progeny work. It is intended to generate a functional, single-screen X setup for North American users because that is all Progeny is targeting right now. Once XFree86 -configure stops core dumping on various chipsets, and xf86cfg is better developed, hopefully Dexter can be thrown out. It is a temporary, interim solution and is only intended to be better than xserver-configure. On balance, I think it succeeds at that. The only really weak spot relative to that old tool is keyboard configuration, which is kind of US/Canada PC keyboard chauvinistic. Thanks Branden (and others, if others need thanking. :) In its present (ugly) state, Dexter is all me. -- G. Branden Robinson | I came, I saw, she conquered. The Debian GNU/Linux| original Latin seems to have been [EMAIL PROTECTED] | garbled. http://www.debian.org/~branden/ | -- Robert Heinlein pgpr9mSdiuIYo.pgp Description: PGP signature
Re: dexter
* Branden Robinson [EMAIL PROTECTED] [001010 21:20]: If you have already written a 4.x XF86Config file, I suggest moving it to /etc/X11/XF86Config-4. I do not support upgrades between versions of these experimental packages; that is the main problem that people are seeing. Hey, this is just what I was looking for. :) Thanks Branden!
Re: dexter
On Tue, Oct 10, 2000 at 08:00:57PM -0700, Seth Arnold wrote: Hey, Dexter looks pretty cool; Thanks. my one suggestion is it should have a ``I have a working XF86Config file already'' option near the front of it, or ``install a default and useless XF86Config file for me''. If you want them hidden behind an ``expert'' button, that would be fine by me. Well, Dexter has simply replaced the old script "xserver-configure". It is only run if the config file is not present (you can confirm this by reading the xserver-* package postinst script). The confusing thing here is that the XFree86 4.x server uses XF86Config-4 preferentially, but will fall back to XF86Config (man XF86Config). The XF86Config file formats are not completely compatible between versions 3.x and 4.x, and we still have to support some of the old 3.x servers, so it is necessary to use XF86Config-4 for the new server. If you have already written a 4.x XF86Config file, I suggest moving it to /etc/X11/XF86Config-4. I do not support upgrades between versions of these experimental packages; that is the main problem that people are seeing. Upgraders from the potato X packages, and fresh installs, will work fine. When they install xserver-xfree86 for the first time it is pretty darn unlikely that they will already have a 4.x-style /etc/X11/XF86Config file. In the (also unlikely) event they already have a /etc/X11/XF86Config-4, Dexter won't run, figuring that someone has already configured the server. Likewise, the suriving 3.x X servers assume that an existing /etc/X11/XF86Config is valid for the 3.x X server(s) you are installing. This will be true (unless it was already broken) for the few people who are upgrading but having to stay with the 3.x server (mostly really old hardware). Everyone else will need to switch X servers to xserver-xfree86, which looks for /etc/X11/XF86Config-4, which won't yet exist, and Dexter will give them a jump start. In other words, I think the scenario you describe is pretty likely to be confined to people who have been using the phase2 packages. Somehow, I have this feeling that my setup is a bit too strange to expect dexter to handle it well (dualhead g400 using matrox's driver). (When I don't have homework to work on, I shall give dexter a proper test drive. :) It is not intended to be a general XF86Config file generator. It is a very rudimentary tool that is the result of some of my Progeny work. It is intended to generate a functional, single-screen X setup for North American users because that is all Progeny is targeting right now. Once XFree86 -configure stops core dumping on various chipsets, and xf86cfg is better developed, hopefully Dexter can be thrown out. It is a temporary, interim solution and is only intended to be better than xserver-configure. On balance, I think it succeeds at that. The only really weak spot relative to that old tool is keyboard configuration, which is kind of US/Canada PC keyboard chauvinistic. Thanks Branden (and others, if others need thanking. :) In its present (ugly) state, Dexter is all me. -- G. Branden Robinson | "I came, I saw, she conquered." The Debian GNU/Linux| original Latin seems to have been [EMAIL PROTECTED] | garbled. http://www.debian.org/~branden/ | -- Robert Heinlein PGP signature
