Re: Bug#77130: dexter is not devfs ready
On Tue, 21 Nov 2000, Marc Martinez wrote: |a much simpler test than working out proper grep semantics is the following: | |[ -c /dev/.devfsd ] | |Marc That one works nicely for me and I don't use devfsd. :-) -- ** 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]
Re: Bug#77130: dexter is not devfs ready
On Tue, 21 Nov 2000, Marc Martinez wrote: |a much simpler test than working out proper grep semantics is the following: | |[ -c /dev/.devfsd ] | |Marc That one works nicely for me and I don't use devfsd. :-) -- ** Derek J Witt** * Email: mailto:[EMAIL PROTECTED] * * Home Page: http://www.flinthills.com/~djw/ * *** Houston, the Eagle has landed and laid an egg! -- Unknown **
Re: Bug#77130: dexter is not devfs ready
On Mon, Nov 20, 2000 at 11:00:34PM -0500, Branden Robinson wrote: I check for a mounted devfs using a check given to me. How about reading the source of dexter and telling me what's wrong with it? a much simpler test than working out proper grep semantics is the following: [ -c /dev/.devfsd ] Marc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#77130: dexter is not devfs ready
[EMAIL PROTECTED] (Branden Robinson) writes: On Mon, Nov 20, 2000 at 02:45:47PM +0100, Goswin Brederlow wrote: [EMAIL PROTECTED] (Branden Robinson) writes: On Mon, Nov 20, 2000 at 03:36:53AM +0100, Goswin Brederlow wrote: PS/2 is in /dev/misc/psaux. Serials are in /dev/tts/[0-9]*. Ah, you mean the exact paths I've been using since 4.0.1-2. Oh, so that should be fixed. Doesn't look right to me: % dpkg -l | grep xfree ii xfree86-common 4.0.1-2X Window System (XFree86) infrastructure ii xserver-xfree8 4.0.1-2the XFree86 X server % cat /proc/filesystems ... nodev devfs % mount ... none on /dev type devfs (rw) ... I check for a mounted devfs using a check given to me. How about reading the source of dexter and telling me what's wrong with it? The check looks right but doesn't work: # grep '\/dev\.*devfs' /proc/mounts # grep '/dev\.*devfs' /proc/mounts # grep '\/dev.*devfs' /proc/mounts # grep '/dev.*devfs' /proc/mounts none /dev devfs rw 0 0 # grep ' /dev .*devfs' /proc/mounts none /dev devfs rw 0 0 # grep '/dev.*devfs' /proc/mounts | hexdump %07.7_ 6f6e 656e 2f20 6564 2076 6564 6676 2073 %07.7_ 7772 3020 3020 000a %07.7_ You might want to check for instead of word start and end to circumvent the problem. MfG Goswin PS: You might also check for existing devices when using devfs. I don't have a /dev/tts/3, so theres no point giving me the choise. Altough care must be taken to handle not yet loaded modules. I might fill this as wishlist, since has nothing to do with this bug.
Re: Bug#77130: dexter is not devfs ready
On Tue, Nov 21, 2000 at 06:33:17PM +0100, Goswin Brederlow wrote: snip The check looks right but doesn't work: # grep '\/dev\.*devfs' /proc/mounts # grep '/dev\.*devfs' /proc/mounts # grep '\/dev.*devfs' /proc/mounts # grep '/dev.*devfs' /proc/mounts none /dev devfs rw 0 0 # grep ' /dev .*devfs' /proc/mounts none /dev devfs rw 0 0 # grep '/dev.*devfs' /proc/mounts | hexdump %07.7_ 6f6e 656e 2f20 6564 2076 6564 6676 2073 %07.7_ 7772 3020 3020 000a %07.7_ You might want to check for instead of word start and end to circumvent the problem. Actually, / is not a word char, also, / tends to be special. grep '\/dev[\t ]*devfs' /proc/mounts Zephaniah E. Hull. MfG Goswin PS: You might also check for existing devices when using devfs. I don't have a /dev/tts/3, so theres no point giving me the choise. Altough care must be taken to handle not yet loaded modules. I might fill this as wishlist, since has nothing to do with this bug. Don't try to open, just test for existence. Zephaniah E. Hull. -- 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. Microsoft is a cross between the Borg and the Ferengi. Unfortunately, they use Borg to do their marketing and Ferengi to do their programming. -- Simon Slavin in asr pgpR6A8Mlpgms.pgp Description: PGP signature
dexter in 4.0.1-7
what happened to dexter? it doesn't want to generate the XF86Config-4 file anymore (it goes for the v3 version, even though i don't have any v3 servers installed). actually i just figured this out. if the Xserver file still exists (and it doesn't get purged when you remove the v3 servers) and the first line in Xserver still lists the old v3 Xserver then dexter goes in v3 compatibility mode. once i changed the first line to /usr/X11R6/bin/XFree86 dexter started configuring the v4 server. i don't think dexter should be looking at the Xserver file to decide what mode (v3 vs. v4) to use for the config file. --alex-- -- | I believe the moment is at hand when, by a paranoiac and active | | advance of the mind, it will be possible (simultaneously with | | automatism and other passive states) to systematize confusion | | and thus to help to discredit completely the world of reality. |
Re: Bug#77130: dexter is not devfs ready
On Mon, Nov 20, 2000 at 11:00:34PM -0500, Branden Robinson wrote: I check for a mounted devfs using a check given to me. How about reading the source of dexter and telling me what's wrong with it? a much simpler test than working out proper grep semantics is the following: [ -c /dev/.devfsd ] Marc
using old config for information [Was: Re: Bug#77130: dexter is not devfs ready]
"Zephaniah E. Hull" [EMAIL PROTECTED] writes: On Mon, Nov 20, 2000 at 03:36:53AM +0100, Goswin Brederlow wrote: snip Goswin PS: Using the old V3 config file for defaults and the console keymap would be a good wishlist thing as well. Ow ow ow ow ow. No, you /really/ don't want those 'features'. Whats wrong with using the same device for the mouse and the same keyboard as in the V3 config file as defaults? (Wheres the keyboard selection anyway in dexter?) Why not look at the console keymap to guess what keymap to use for X when no old config is found? I'm not talking about skipping the question in dexter. But dexter could position the cursor in the mouse selection on the mouse device that was used in the old confg file. May the Source be with you. Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#77130: dexter is not devfs ready
[EMAIL PROTECTED] (Branden Robinson) writes: On Mon, Nov 20, 2000 at 03:36:53AM +0100, Goswin Brederlow wrote: PS/2 is in /dev/misc/psaux. Serials are in /dev/tts/[0-9]*. Ah, you mean the exact paths I've been using since 4.0.1-2. Oh, so that should be fixed. Doesn't look right to me: % dpkg -l | grep xfree ii xfree86-common 4.0.1-2X Window System (XFree86) infrastructure ii xserver-xfree8 4.0.1-2the XFree86 X server % cat /proc/filesystems ... nodev devfs % mount ... none on /dev type devfs (rw) ... % dexter Dexter -- Debian X Server Configurator qq lqq Mouse Port Selection qqk x x x Please choose your mouse port. x x x x lqqk x x x /dev/psaux PS/2 port x x x x /dev/ttyS0 Serial port COM1x x x x /dev/ttyS1 Serial port COM2x x x x /dev/ttyS2 Serial port COM3x x x x /dev/ttyS3 Serial port COM4x x x x /dev/input/mice USB mouse x x x x /dev/atibm Bus / inport mouse x x x x /dev/gpmdata gpm repeaterx x x mqqj x tqqu x OK x mqqj On my system none of those even exist. MfG Goswin
using old config for information [Was: Re: Bug#77130: dexter is not devfs ready]
Zephaniah E. Hull [EMAIL PROTECTED] writes: On Mon, Nov 20, 2000 at 03:36:53AM +0100, Goswin Brederlow wrote: snip Goswin PS: Using the old V3 config file for defaults and the console keymap would be a good wishlist thing as well. Ow ow ow ow ow. No, you /really/ don't want those 'features'. Whats wrong with using the same device for the mouse and the same keyboard as in the V3 config file as defaults? (Wheres the keyboard selection anyway in dexter?) Why not look at the console keymap to guess what keymap to use for X when no old config is found? I'm not talking about skipping the question in dexter. But dexter could position the cursor in the mouse selection on the mouse device that was used in the old confg file. May the Source be with you. Goswin
Re: Bug#77130: dexter is not devfs ready
On Mon, Nov 20, 2000 at 02:45:47PM +0100, Goswin Brederlow wrote: [EMAIL PROTECTED] (Branden Robinson) writes: On Mon, Nov 20, 2000 at 03:36:53AM +0100, Goswin Brederlow wrote: PS/2 is in /dev/misc/psaux. Serials are in /dev/tts/[0-9]*. Ah, you mean the exact paths I've been using since 4.0.1-2. Oh, so that should be fixed. Doesn't look right to me: % dpkg -l | grep xfree ii xfree86-common 4.0.1-2X Window System (XFree86) infrastructure ii xserver-xfree8 4.0.1-2the XFree86 X server % cat /proc/filesystems ... nodev devfs % mount ... none on /dev type devfs (rw) ... I check for a mounted devfs using a check given to me. How about reading the source of dexter and telling me what's wrong with it? -- G. Branden Robinson| Debian GNU/Linux | If ignorance is bliss, [EMAIL PROTECTED] | is omniscience hell? http://deadbeast.net/~branden/ | pgpYXGBnXElbU.pgp Description: PGP signature
Re: Bug#77130: dexter is not devfs ready
On Mon, Nov 20, 2000 at 03:36:53AM +0100, Goswin Brederlow wrote: snip Goswin PS: Using the old V3 config file for defaults and the console keymap would be a good wishlist thing as well. Ow ow ow ow ow. No, you /really/ don't want those 'features'. Zephaniah E. Hull. -- 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. Overfiend Oh God yes, please, Espy...let me mount your hard-driving SPARCbeast until I undulate in X-compiling ecstasy PGP signature
Re: Bug#77130: dexter is not devfs ready
[EMAIL PROTECTED] (Branden Robinson) writes: On Wed, Nov 15, 2000 at 09:55:30PM +0100, Goswin Brederlow wrote: All suggestions for the mouse device use the old device names, devfs has them in subdirectories. Please use the new names when devfs is used. You're going to have to tell me what these are. I asked on IRC what I should use, and I used what I was told. Have a look at the documentation about the devfs in linux/Documentation/filesystems/devfs/ PS/2 is in /dev/misc/psaux. Serials are in /dev/tts/[0-9]*. Framebuffer in /dev/fb/[0-9]*. Also for framebuffer the framebuffer to be used should be choosable, i.e. which of /dev/fb/* to use. This is a wishlist item and I'll get to it when I can. I don't even know how to get X to use the second framebuffer, never had a second one. MfG Goswin PS: Using the old V3 config file for defaults and the console keymap would be a good wishlist thing as well.
Re: Bug#77130: dexter is not devfs ready
On Mon, Nov 20, 2000 at 03:36:53AM +0100, Goswin Brederlow wrote: snip Goswin PS: Using the old V3 config file for defaults and the console keymap would be a good wishlist thing as well. Ow ow ow ow ow. No, you /really/ don't want those 'features'. Zephaniah E. Hull. -- 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. Overfiend Oh God yes, please, Espy...let me mount your hard-driving SPARCbeast until I undulate in X-compiling ecstasy pgpvso6F5hQ9f.pgp Description: PGP signature
Re: Bug#77130: dexter is not devfs ready
On Mon, Nov 20, 2000 at 03:36:53AM +0100, Goswin Brederlow wrote: PS/2 is in /dev/misc/psaux. Serials are in /dev/tts/[0-9]*. Ah, you mean the exact paths I've been using since 4.0.1-2. Please do more research before filing bugs in the future. -- G. Branden Robinson| Debian GNU/Linux |Mob rule isn't any prettier just because [EMAIL PROTECTED] |you call your mob a government. http://deadbeast.net/~branden/ | pgpnrlvIyBoJz.pgp Description: PGP signature
Re: Bug#77130: dexter is not devfs ready
On Thu, Nov 16, 2000 at 11:05:27AM -0800, Marc Martinez wrote: the real device for at least psaux is /dev/misc/psaux .. if you have the compatibility options enabled in devfsd it also makes a symlink back to /dev/psaux for you. looks like the ttyS* serial devices are now in the form of /dev/tts/0 .. I don't have any usb mice connected right now so that's all I can tell you offhand. Despite the version number in his bug report I don't think Goswin is using a recently version of xserver-common. I added devfs support a few versions ago. Dexter is a shell script. Feel free to read it to see what's wrong with the devfs support. I wrote that support based wholly on input from this list. -- G. Branden Robinson |You can have my PGP passphrase when you Debian GNU/Linux|pry it from my cold, dead brain. [EMAIL PROTECTED] |-- Adam Thornton http://www.debian.org/~branden/ | pgptgEstxtCPh.pgp Description: PGP signature
Re: Bug#77130: dexter is not devfs ready
On Wed, Nov 15, 2000 at 11:27:14PM -0500, Branden Robinson wrote: On Wed, Nov 15, 2000 at 09:55:30PM +0100, Goswin Brederlow wrote: All suggestions for the mouse device use the old device names, devfs has them in subdirectories. Please use the new names when devfs is used. You're going to have to tell me what these are. I asked on IRC what I should use, and I used what I was told. the real device for at least psaux is /dev/misc/psaux .. if you have the compatibility options enabled in devfsd it also makes a symlink back to /dev/psaux for you. looks like the ttyS* serial devices are now in the form of /dev/tts/0 .. I don't have any usb mice connected right now so that's all I can tell you offhand. while it's just personal preference, for any box that I use devfs on but don't use devfsd, I also don't let it mount as /dev, but rather keep it off on other directories just as a guide to know what devices are available at any given time (which was handy for example to see that the major for joystick devices got moved around in newer kernels). Marc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#77130: dexter is not devfs ready
Marc Martinez spake thus:
of /dev/tts/0 .. I don't have any usb mice connected right now so that's all
I can tell you offhand.
/dev/input/mouse{0,1,...}
/dev/input/mice lets all your mice talk ps/2 to you at the same time.
Oystein
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#77130: dexter is not devfs ready
On Thu, Nov 16, 2000 at 11:05:27AM -0800, Marc Martinez wrote: the real device for at least psaux is /dev/misc/psaux .. if you have the compatibility options enabled in devfsd it also makes a symlink back to /dev/psaux for you. looks like the ttyS* serial devices are now in the form of /dev/tts/0 .. I don't have any usb mice connected right now so that's all I can tell you offhand. Despite the version number in his bug report I don't think Goswin is using a recently version of xserver-common. I added devfs support a few versions ago. Dexter is a shell script. Feel free to read it to see what's wrong with the devfs support. I wrote that support based wholly on input from this list. -- G. Branden Robinson |You can have my PGP passphrase when you Debian GNU/Linux|pry it from my cold, dead brain. [EMAIL PROTECTED] |-- Adam Thornton http://www.debian.org/~branden/ | PGP signature
Re: Bug#77130: dexter is not devfs ready
On Wed, Nov 15, 2000 at 11:27:14PM -0500, Branden Robinson wrote: On Wed, Nov 15, 2000 at 09:55:30PM +0100, Goswin Brederlow wrote: All suggestions for the mouse device use the old device names, devfs has them in subdirectories. Please use the new names when devfs is used. You're going to have to tell me what these are. I asked on IRC what I should use, and I used what I was told. the real device for at least psaux is /dev/misc/psaux .. if you have the compatibility options enabled in devfsd it also makes a symlink back to /dev/psaux for you. looks like the ttyS* serial devices are now in the form of /dev/tts/0 .. I don't have any usb mice connected right now so that's all I can tell you offhand. while it's just personal preference, for any box that I use devfs on but don't use devfsd, I also don't let it mount as /dev, but rather keep it off on other directories just as a guide to know what devices are available at any given time (which was handy for example to see that the major for joystick devices got moved around in newer kernels). Marc
Re: Bug#77130: dexter is not devfs ready
Marc Martinez spake thus:
of /dev/tts/0 .. I don't have any usb mice connected right now so that's all
I can tell you offhand.
/dev/input/mouse{0,1,...}
/dev/input/mice lets all your mice talk ps/2 to you at the same time.
Oystein
Re: Bug#77130: dexter is not devfs ready
On Wed, Nov 15, 2000 at 09:55:30PM +0100, Goswin Brederlow wrote: All suggestions for the mouse device use the old device names, devfs has them in subdirectories. Please use the new names when devfs is used. You're going to have to tell me what these are. I asked on IRC what I should use, and I used what I was told. Also for framebuffer the framebuffer to be used should be choosable, i.e. which of /dev/fb/* to use. This is a wishlist item and I'll get to it when I can. -- G. Branden Robinson| Debian GNU/Linux | "Bother," said Pooh, as he was [EMAIL PROTECTED] | assimilated by the Borg. http://deadbeast.net/~branden/ | PGP signature
Re: Bug#77130: dexter is not devfs ready
On Wed, Nov 15, 2000 at 09:55:30PM +0100, Goswin Brederlow wrote: All suggestions for the mouse device use the old device names, devfs has them in subdirectories. Please use the new names when devfs is used. You're going to have to tell me what these are. I asked on IRC what I should use, and I used what I was told. Also for framebuffer the framebuffer to be used should be choosable, i.e. which of /dev/fb/* to use. This is a wishlist item and I'll get to it when I can. -- G. Branden Robinson| Debian GNU/Linux | Bother, said Pooh, as he was [EMAIL PROTECTED] | assimilated by the Borg. http://deadbeast.net/~branden/ | pgpxbWVVC3Ken.pgp Description: PGP signature
dexter and microsoft wheelmouse optical ?
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
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]
dexter and USB mouse
As an FYI, or if anyone is keeping a FAQ, 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... I also had to switch back to the built-in Nvidia driver - the one from Nvidia starts up, but has all kinds of video corruption on my GeForce card. I think this may be a function of running the 2.4 kernel, although again, I'm not sure... Thanks for all the hard work turning XF86 4.0 into deb packages. The upgrade went far more smoothly than I expected, since I had my own compile of XF86 4.0 stuffed on top of a previous 3.3.6 debian install... later, Kimball
Re: dialog version dependency for dexter
On Thu, 2 Nov 2000, Branden Robinson wrote: On Thu, Nov 02, 2000 at 03:01:12PM -0500, David I. Lehn wrote: dexter needs to depend on a recent version of dialog. I was installing on a machine with an old dialog version (sorry, not sure which) that didn't have the --nocancel option and dexter dies on this. An upgrade of dialog fixed it. Okay, thanks for mentioning this. I *think* the proper version to depend on is 0.9a-2425-1. Santiago, can you confirm this, please? Yes, this is correct.
Re: dialog version dependency for dexter
On Thu, Nov 02, 2000 at 03:01:12PM -0500, David I. Lehn wrote: dexter needs to depend on a recent version of dialog. I was installing on a machine with an old dialog version (sorry, not sure which) that didn't have the --nocancel option and dexter dies on this. An upgrade of dialog fixed it. Okay, thanks for mentioning this. I *think* the proper version to depend on is 0.9a-2425-1. Santiago, can you confirm this, please? -- G. Branden Robinson |"To be is to do" -- Plato Debian GNU/Linux|"To do is to be" -- Aristotle [EMAIL PROTECTED] |"Do be do be do" -- Sinatra http://www.debian.org/~branden/ | PGP signature
dialog version dependency for dexter
dexter needs to depend on a recent version of dialog. I was installing on a machine with an old dialog version (sorry, not sure which) that didn't have the --nocancel option and dexter dies on this. An upgrade of dialog fixed it. -dave -- David I. Lehn [EMAIL PROTECTED] | http://www.lehn.org/~dlehn/ Computer Engineering Graduate @ Virginia Tech in sunny Blacksburg, VA
Re: dialog version dependency for dexter
On Thu, Nov 02, 2000 at 03:01:12PM -0500, David I. Lehn wrote: dexter needs to depend on a recent version of dialog. I was installing on a machine with an old dialog version (sorry, not sure which) that didn't have the --nocancel option and dexter dies on this. An upgrade of dialog fixed it. Okay, thanks for mentioning this. I *think* the proper version to depend on is 0.9a-2425-1. Santiago, can you confirm this, please? -- G. Branden Robinson |To be is to do -- Plato Debian GNU/Linux|To do is to be -- Aristotle [EMAIL PROTECTED] |Do be do be do -- Sinatra http://www.debian.org/~branden/ | pgpXknMVmsiTd.pgp Description: PGP signature
Question about dexter
(Please CC: me as I'm not on this list). Hi all. I was helping a friend of mine install the X4 debs, and he noticed that dexter depends on dialog, but xserver-common, which gives dexter doesn't require it. Shouldn't it? (Or, dexter split off into another package, suggested by xserver-common, which depends on dialog). -- Tom Rini (TR1265) http://gate.crashing.org/~trini/
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
dexter making assumptions about font server (and screen resolution)
Dexter seems to assume that I am running a local font server, which I'm not. The problem is that as long as my XF86Config-4 contained the line FontPathunix/:7100 # local font server X refused to start. The screen went blank and then nothing happened. Commenting out the FontPath line above made it work again. 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. 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.) (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?) 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... dialog --cr-wrap --backtitle Screen Resolution \ --title Choose Max Screen Resolution --menu \ Select your desired maximum screen resolution from the list below. \ 20 75 9 \ 1 1920x1440 \ 2 1856x1392 \ 3 1792x1344 \ 4 1600x1200 \ 5 1280x960 \ 6 1152x864 \ 7 1024x768 \ 8 800x600 \ 9 640x480 \ 2 $DEXTERTMPDIR/prompt RESOLUTIONS=$(echo 1920x1440 1856x1392 1792x1344 1600x1200 \ 1280x960 1152x864 1024x768 800x600 640x480 | \ cut --delim=' ' --fields=$(cat $DEXTERTMPDIR/prompt)- \ $DEXTERTMPDIR/Resolutions) but I'm not really used to dialog. Or shell scripts. Or... 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. 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: rendition support in dexter
On Sat, Oct 21, 2000 at 02:04:18PM +0200, Hein-Jan Leliveld wrote: In the latest phase2 debs (v20) it isn't possible to choose a rendition x-server in dexter. If I manually edit the XF86Config-4 file to add the rendition video card everything works fine. Sorry, this was an oversight. It will be fixed in the next release. Thanks for pointing it out. -- G. Branden Robinson | If you have the slightest bit of Debian GNU/Linux| intellectual integrity you cannot [EMAIL PROTECTED] | support the government. http://www.debian.org/~branden/ | -- anonymous pgpbyBb1JLWLw.pgp Description: PGP signature
rendition support in dexter
Hello, In the latest phase2 debs (v20) it isn't possible to choose a rendition x-server in dexter. If I manually edit the XF86Config-4 file to add the rendition video card everything works fine. Greetings, Hein-Jan Leliveld
Re: Voodoo 5 (tdfx) at 24 bpp and dexter
On Thu, Oct 19, 2000 at 11:48:18PM +0100, Matthew Garrett wrote: I've noticed this here as well. However, I haven't seen it when using the server from linux.3dfx.com. Scratch that. I've managed to trigger it with both. -- Matthew Garrett | [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Voodoo 5 (tdfx) at 24 bpp and dexter
On Thu, Oct 19, 2000 at 11:48:18PM +0100, Matthew Garrett wrote: I've noticed this here as well. However, I haven't seen it when using the server from linux.3dfx.com. Scratch that. I've managed to trigger it with both. -- Matthew Garrett | [EMAIL PROTECTED]
dexter wishlist item
Hey Branden, Great work on X and dexter so far! I was hoping to get another little addition to dexter, though, or find out why it's not there already :) 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)? Thanks. -m -- Michael Urman [EMAIL PROTECTED] gpg: 1024g/55C56706 : C3D7 2A8F 6261 3DE4 F544 6DC3 A1D5 BEF6 156F 65A4 mwr#debian bsd is also responsible for porn nets, then, too? Groovy. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Voodoo 5 (tdfx) at 24 bpp and dexter
On Thu, Oct 19, 2000 at 04:03:39PM -0500, Branden Robinson wrote: It does support 24 bit color depth if your resolution is low enough. This appears to be a bug in the tdfx driver. IIRC I had to get down to 1152x864 before 24-bit would work on my Voodoo3 3000 PCI. IIRC, the DRI support only works in 16 bit colour depth on the Voodoo3 - given that many people are likely to want to use it if they have a tdfx card, defaulting to 16 may be sensible. (end of stuff that's directly related to the debs) Some combination of high resolution + depth gets things into a confused state. I get a corrupt screen even at 16-bit depth if I push the card up to really ridiculous resolutions (1920x1440 or something). I won't speculate on the possible causes of this so as to avoid sounding like a complete idiot. I've had the same problem (which is a pain, because I have a nice shiny new monitor that's capable of doing that). I haven't had a chance to find out why, but dropping to 1800x1440ish fixes it. I tried defining my own modelines, but they get deleted due to "Unknown reason" during X startup. I'd assumed that this was just me being an idiot in some way, so seeing someone else with the same problem is reassuring :) While I'm pestering Daryll in his inbox, there have been widespread reports (which I can personally confirm) of occasional VGA text font corruption upon switching away to a console VC from X when using the tdfx driver. Pieces of glyphs go missing. Perhaps something needs to wait longer before switching back to text mode? Note that this doesn't happen every single time (or perhaps it is simply hitting unusual characters that don't happen to be on the screen), but if you switch back and forth half a dozen times with something more than getty on the VC, you should be able to see this. I've noticed this here as well. However, I haven't seen it when using the server from linux.3dfx.com. Once the process has started (by switching to a text console from X), certain characters (mostly punctuation) are damaged and occasional flashing characters appear. Leaving it at the text console with no input gives more characters appearing over time. I've also been having problems with DRI and objects being rendered out of order when rendering to the root window and in some other applications (wine, for instance), while most windowed stuff works fine. This seems to happen with both the XFree and 3DFX drivers, so may be something specific to my setup. I haven't tried the stock XFree tree with this card, so my experiences are limited to the debs and the 3DFX packages. Please let me know what I can do to help test fixes for these problems, I have a Voodoo3 3000 PCI here at work and a 2000 PCI at home. This is with a V3 3000 AGP. I'm also happy to try stuff to fix this - I upgraded to the Voodoo because my G100 wouldn't go above 1800x1400 at 60Hz, so I'd quite like to have working higher resolutions :) -- Matthew Garrett | [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
dexter wishlist item
Hey Branden, Great work on X and dexter so far! I was hoping to get another little addition to dexter, though, or find out why it's not there already :) 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)? Thanks. -m -- Michael Urman [EMAIL PROTECTED] gpg: 1024g/55C56706 : C3D7 2A8F 6261 3DE4 F544 6DC3 A1D5 BEF6 156F 65A4 mwr#debian bsd is also responsible for porn nets, then, too? Groovy.
Voodoo 5 (tdfx) at 24 bpp and dexter
I've got a Voodoo 5, and dexter defaults to 24 bpp for the tdfx driver, which doesn't agree with the driver (I don't think it properly supports anything but 16 bpp at the moment) so I get pretty much nothing but garbage until I change DefaultDepth to 16 rather than 24. I think this might be a reasonable default, at least for tdfx. Also, somewhat off-topic: Has 3dfx sync'ed their trees for XF86 (ie: the X server on linux.3dfx.com) with the Xfree4 tree? I notice some jittering in 3d games, etc, and lack of performance, which isn't present in their XFCOM server.
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: Voodoo 5 (tdfx) at 24 bpp and dexter
On Thu, Oct 19, 2000 at 02:45:39PM -0400, Joe Drew wrote: I've got a Voodoo 5, and dexter defaults to 24 bpp for the tdfx driver, which doesn't agree with the driver (I don't think it properly supports anything but 16 bpp at the moment) so I get pretty much nothing but garbage until I change DefaultDepth to 16 rather than 24. I think this might be a reasonable default, at least for tdfx. Also, somewhat off-topic: Has 3dfx sync'ed their trees for XF86 (ie: the X server on linux.3dfx.com) with the Xfree4 tree? I notice some jittering in 3d games, etc, and lack of performance, which isn't present in their XFCOM server. It does support 24 bit color depth if your resolution is low enough. This appears to be a bug in the tdfx driver. IIRC I had to get down to 1152x864 before 24-bit would work on my Voodoo3 3000 PCI. Some combination of high resolution + depth gets things into a confused state. I get a corrupt screen even at 16-bit depth if I push the card up to really ridiculous resolutions (1920x1440 or something). I won't speculate on the possible causes of this so as to avoid sounding like a complete idiot. While I'm pestering Daryll in his inbox, there have been widespread reports (which I can personally confirm) of occasional VGA text font corruption upon switching away to a console VC from X when using the tdfx driver. Pieces of glyphs go missing. Perhaps something needs to wait longer before switching back to text mode? Note that this doesn't happen every single time (or perhaps it is simply hitting unusual characters that don't happen to be on the screen), but if you switch back and forth half a dozen times with something more than getty on the VC, you should be able to see this. Please let me know what I can do to help test fixes for these problems, I have a Voodoo3 3000 PCI here at work and a 2000 PCI at home. -- G. Branden Robinson |Convictions are more dangerous enemies Debian GNU/Linux|of truth than lies. [EMAIL PROTECTED] |-- Friedrich Nietzsche http://www.debian.org/~branden/ | pgpK1XiItlPCe.pgp Description: PGP signature
Re: Voodoo 5 (tdfx) at 24 bpp and dexter
On Thu, Oct 19, 2000 at 04:03:39PM -0500, Branden Robinson wrote: It does support 24 bit color depth if your resolution is low enough. This appears to be a bug in the tdfx driver. IIRC I had to get down to 1152x864 before 24-bit would work on my Voodoo3 3000 PCI. IIRC, the DRI support only works in 16 bit colour depth on the Voodoo3 - given that many people are likely to want to use it if they have a tdfx card, defaulting to 16 may be sensible. (end of stuff that's directly related to the debs) Some combination of high resolution + depth gets things into a confused state. I get a corrupt screen even at 16-bit depth if I push the card up to really ridiculous resolutions (1920x1440 or something). I won't speculate on the possible causes of this so as to avoid sounding like a complete idiot. I've had the same problem (which is a pain, because I have a nice shiny new monitor that's capable of doing that). I haven't had a chance to find out why, but dropping to 1800x1440ish fixes it. I tried defining my own modelines, but they get deleted due to Unknown reason during X startup. I'd assumed that this was just me being an idiot in some way, so seeing someone else with the same problem is reassuring :) While I'm pestering Daryll in his inbox, there have been widespread reports (which I can personally confirm) of occasional VGA text font corruption upon switching away to a console VC from X when using the tdfx driver. Pieces of glyphs go missing. Perhaps something needs to wait longer before switching back to text mode? Note that this doesn't happen every single time (or perhaps it is simply hitting unusual characters that don't happen to be on the screen), but if you switch back and forth half a dozen times with something more than getty on the VC, you should be able to see this. I've noticed this here as well. However, I haven't seen it when using the server from linux.3dfx.com. Once the process has started (by switching to a text console from X), certain characters (mostly punctuation) are damaged and occasional flashing characters appear. Leaving it at the text console with no input gives more characters appearing over time. I've also been having problems with DRI and objects being rendered out of order when rendering to the root window and in some other applications (wine, for instance), while most windowed stuff works fine. This seems to happen with both the XFree and 3DFX drivers, so may be something specific to my setup. I haven't tried the stock XFree tree with this card, so my experiences are limited to the debs and the 3DFX packages. Please let me know what I can do to help test fixes for these problems, I have a Voodoo3 3000 PCI here at work and a 2000 PCI at home. This is with a V3 3000 AGP. I'm also happy to try stuff to fix this - I upgraded to the Voodoo because my G100 wouldn't go above 1800x1400 at 60Hz, so I'd quite like to have working higher resolutions :) -- Matthew Garrett | [EMAIL PROTECTED]
Re: XF4 - small dexter(?) bug
On Tue, Oct 17, 2000 at 11:17:17AM -0400, Chris Gorman wrote: The font path gets unix:/7100 rather than unix/:7100 This is fixed in v18; thank you for pointing it out. -- G. Branden Robinson | Optimists believe we live in the best of Debian GNU/Linux| all possible worlds. Pessimists are [EMAIL PROTECTED] | afraid the optimists are right. http://www.debian.org/~branden/ | pgpfg9arnV2V4.pgp Description: PGP signature
XF4 - small dexter(?) bug
Hello All, Just a quick note about a little syntax error I got with dexter in XF4. Package... ii xserver-common4.0.1-0phase2v17 The generated /etc/X11/XF86Config-4 file has the font server path set incorrectly by default. (I don't know if this has been reported already. I did a quick scan of the mail archive and didn't find anything.) The font path gets unix:/7100 rather than unix/:7100 Otherwise the packages work great. Thanks. C -- The address in the headers is not the poster's real email address. Do not send private mail to the poster using your mailer's "reply" feature. CC's of mail to mailing lists are OK. Problem reports to "[EMAIL PROTECTED]". The poster's email address is "[EMAIL PROTECTED]". -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: XF4 - small dexter(?) bug
On Tue, Oct 17, 2000 at 11:17:17AM -0400, Chris Gorman wrote: The font path gets unix:/7100 rather than unix/:7100 This is fixed in v18; thank you for pointing it out. -- G. Branden Robinson | Optimists believe we live in the best of Debian GNU/Linux| all possible worlds. Pessimists are [EMAIL PROTECTED] | afraid the optimists are right. http://www.debian.org/~branden/ | PGP signature
XF4 - small dexter(?) bug
Hello All, Just a quick note about a little syntax error I got with dexter in XF4. Package... ii xserver-common4.0.1-0phase2v17 The generated /etc/X11/XF86Config-4 file has the font server path set incorrectly by default. (I don't know if this has been reported already. I did a quick scan of the mail archive and didn't find anything.) The font path gets unix:/7100 rather than unix/:7100 Otherwise the packages work great. Thanks. C -- The address in the headers is not the poster's real email address. Do not send private mail to the poster using your mailer's reply feature. CC's of mail to mailing lists are OK. Problem reports to [EMAIL PROTECTED]. The poster's email address is [EMAIL PROTECTED].
dexter and devfs
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. But not before; it's beyond my current knowledge since I have yet to play with USB or devfs myself. Remember, dexter needs to support those without devfs, too. I'm not going to break dexter to support only bleeding-edge devfs people. -- 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 signature
Re: How do you want non-i386 handled in dexter? (+ mouse types)
On Sat, Oct 14, 2000 at 06:03:12PM -0400, Ben Collins wrote: On Sat, Oct 14, 2000 at 02:23:49PM -0600, Joshua Shagam wrote: On Sat, Oct 14, 2000 at 09:03:20AM -0400, Ben Collins wrote: Obviously the server list in dexter needs to be different on non-i386, aswell as the generated keyboard lines (on sun there are two default possibilies, i386 and type5). How do you forsee this happening? There isn't a clean way right now, expect for outputting a complete list of servers for each arch (lots of duplication). I don't think it can be handled cleanly in shell, so will you change to perl (the var/string handling in shell loses in this case). Why not have dexter generate the list at runtime based on the files in /usr/X11R6/lib/modules/drivers? Sounds even better to me. Let me mull this over. Sounds good except that it's a little more complex because of the legacy 3.x servers supported on alpha and i386 (only, fortunately). -- G. Branden Robinson |Murphy's Guide to Science: Debian GNU/Linux|If it's green or squirms, it's biology. [EMAIL PROTECTED] |If it stinks, it's chemistry. http://www.debian.org/~branden/ |If it doesn't work, it's physics. 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: xserver-common phase2v15: dexter does not list /dev/gpmdata
On Thu, Oct 12, 2000 at 04:20:31AM -0700, [EMAIL PROTECTED] wrote:
I hadn't extensively played with it either, since I have a rather custom
config (dual head with fixed-frequency monitors). Though, it would be
nice if dexter could accept more monitor information, perhaps even a full
XFree86 modeline. Hopefully that kind of additional support could be
added later on.
Barring overwhelming demand, I'm just not going to add this functionality.
Dexter's success is going to depend on constraining its focus, which is
getting the naive user without any X server configuration into X with a
minimal requirement of knowledge about his/her hardware and certainly
without any knowledge of the syntax of the XF86Config{-4} file.
Modelines are the deepest of magic. If you want to play with them, then
you belong in a text editor with the XF86Config{-4} file.
At least it doesn't overwrite XF86Config. =)
Correct; the latest version will not overwrite without being told to do so.
--
G. Branden Robinson | If a man ate a pound of pasta and a
Debian GNU/Linux| pound of antipasto, would they cancel
[EMAIL PROTECTED] | out, leaving him still hungry?
http://www.debian.org/~branden/ | -- Scott Adams
pgpfgSHXVVMOs.pgp
Description: PGP signature
dexter and devfs
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. But not before; it's beyond my current knowledge since I have yet to play with USB or devfs myself. Remember, dexter needs to support those without devfs, too. I'm not going to break dexter to support only bleeding-edge devfs people. -- 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 pgpt3S88f4tsR.pgp Description: PGP signature
Re: How do you want non-i386 handled in dexter? (+ mouse types)
On Sat, Oct 14, 2000 at 06:03:12PM -0400, Ben Collins wrote: On Sat, Oct 14, 2000 at 02:23:49PM -0600, Joshua Shagam wrote: On Sat, Oct 14, 2000 at 09:03:20AM -0400, Ben Collins wrote: Obviously the server list in dexter needs to be different on non-i386, aswell as the generated keyboard lines (on sun there are two default possibilies, i386 and type5). How do you forsee this happening? There isn't a clean way right now, expect for outputting a complete list of servers for each arch (lots of duplication). I don't think it can be handled cleanly in shell, so will you change to perl (the var/string handling in shell loses in this case). Why not have dexter generate the list at runtime based on the files in /usr/X11R6/lib/modules/drivers? Sounds even better to me. Let me mull this over. Sounds good except that it's a little more complex because of the legacy 3.x servers supported on alpha and i386 (only, fortunately). -- G. Branden Robinson |Murphy's Guide to Science: Debian GNU/Linux|If it's green or squirms, it's biology. [EMAIL PROTECTED] |If it stinks, it's chemistry. http://www.debian.org/~branden/ |If it doesn't work, it's physics. pgp7kaaA3R7Cx.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 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] ' `---=--===-=-=-=-===-==---=--=---'
dexter, phase2v17
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? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: How do you want non-i386 handled in dexter? (+ mouse types)
On Sat, Oct 14, 2000 at 02:23:49PM -0600, Joshua Shagam wrote: On Sat, Oct 14, 2000 at 09:03:20AM -0400, Ben Collins wrote: Obviously the server list in dexter needs to be different on non-i386, aswell as the generated keyboard lines (on sun there are two default possibilies, i386 and type5). How do you forsee this happening? There isn't a clean way right now, expect for outputting a complete list of servers for each arch (lots of duplication). I don't think it can be handled cleanly in shell, so will you change to perl (the var/string handling in shell loses in this case). Why not have dexter generate the list at runtime based on the files in /usr/X11R6/lib/modules/drivers? Sounds even better to me. -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
How do you want non-i386 handled in dexter? (+ mouse types)
Obviously the server list in dexter needs to be different on non-i386, aswell as the generated keyboard lines (on sun there are two default possibilies, i386 and type5). How do you forsee this happening? There isn't a clean way right now, expect for outputting a complete list of servers for each arch (lots of duplication). I don't think it can be handled cleanly in shell, so will you change to perl (the var/string handling in shell loses in this case). Also, sunmouse is an option. Problem is, xf4 currently has no idea what Sun type is. On top of that, I tried a ppc build, and it has no idea what a USB mouse is. Known problem? -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---'
dexter, phase2v17
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?
Re: How do you want non-i386 handled in dexter? (+ mouse types)
On Sat, Oct 14, 2000 at 09:03:20AM -0400, Ben Collins wrote: Obviously the server list in dexter needs to be different on non-i386, aswell as the generated keyboard lines (on sun there are two default possibilies, i386 and type5). How do you forsee this happening? There isn't a clean way right now, expect for outputting a complete list of servers for each arch (lots of duplication). I don't think it can be handled cleanly in shell, so will you change to perl (the var/string handling in shell loses in this case). Why not have dexter generate the list at runtime based on the files in /usr/X11R6/lib/modules/drivers? Also, sunmouse is an option. Problem is, xf4 currently has no idea what Sun type is. On top of that, I tried a ppc build, and it has no idea what a USB mouse is. Known problem? -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---' -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Joshua Shagam /\ ASCII Ribbon Campaign [EMAIL PROTECTED] \ / No HTML/RTF in email www.cs.nmsu.edu/~joshagam X No Word docs in email mp3.com/fluffyporcupine/ \ Respect for open standards
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: How do you want non-i386 handled in dexter? (+ mouse types)
On Sat, Oct 14, 2000 at 02:23:49PM -0600, Joshua Shagam wrote: On Sat, Oct 14, 2000 at 09:03:20AM -0400, Ben Collins wrote: Obviously the server list in dexter needs to be different on non-i386, aswell as the generated keyboard lines (on sun there are two default possibilies, i386 and type5). How do you forsee this happening? There isn't a clean way right now, expect for outputting a complete list of servers for each arch (lots of duplication). I don't think it can be handled cleanly in shell, so will you change to perl (the var/string handling in shell loses in this case). Why not have dexter generate the list at runtime based on the files in /usr/X11R6/lib/modules/drivers? Sounds even better to me. -- ---===-=-==-=---==-=-- / Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \ ` [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] ' `---=--===-=-=-=-===-==---=--=---'
Re: xserver-common phase2v15: dexter does not list /dev/gpmdata
On Thu, Oct 12, 2000 at 07:34:21AM +0200, Morten B. Pedersen wrote: On Wed, Oct 11, 2000 at 05:26:09 -0700, [EMAIL PROTECTED] wrote: /dev/gpmdata is not on the list of mouse devices. /dev/gpmdata IS a valid mouse device. I think /dev/input/mice should be there too for USB mouse. It's this device that the USB guide on www.linux-usb.org refers to. And the one the kernel documentation (well linux/Documentation/usb/input.txt) suggests. there is also talk about all the /dev/input/mouse0, /dev/input/mouse1, ... but this would be usefull only for multiple mouses, and i have no experience with it. Friendly, Sven LUTHER -- Med venlig hilsen - Sincerely Morten B. Pedersen - [EMAIL PROTECTED] Copenhagen, Denmark. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xserver-common phase2v15: dexter does not list /dev/gpmdata
On Thu, Oct 12, 2000 at 07:34:21AM +0200, Morten B. Pedersen wrote: On Wed, Oct 11, 2000 at 05:26:09 -0700, [EMAIL PROTECTED] wrote: /dev/gpmdata is not on the list of mouse devices. /dev/gpmdata IS a valid mouse device. I think /dev/input/mice should be there too for USB mouse. It's this device that the USB guide on www.linux-usb.org refers to. And the one the kernel documentation (well linux/Documentation/usb/input.txt) suggests. there is also talk about all the /dev/input/mouse0, /dev/input/mouse1, ... but this would be usefull only for multiple mouses, and i have no experience with it. Friendly, Sven LUTHER -- Med venlig hilsen - Sincerely Morten B. Pedersen - [EMAIL PROTECTED] Copenhagen, Denmark. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: xserver-common phase2v15: dexter does not list /dev/gpmdata
I don't believe one of the immediate goals of dexter is to support multiple anything yet, but give it time. Drifting a little bit from topic, I'm thinking it would be nice to have a seperate user-mode input manager, that can communicate and pass input events across network connections. It should be able to handle any input device (keyboards, mice, game pads, dials and buttons, boxen, etc), map arbitrary events from one device type to another, forward or repeat events across the network, but I ramble. On Fri, 13 Oct 2000, Sven LUTHER wrote: On Thu, Oct 12, 2000 at 07:34:21AM +0200, Morten B. Pedersen wrote: On Wed, Oct 11, 2000 at 05:26:09 -0700, [EMAIL PROTECTED] wrote: /dev/gpmdata is not on the list of mouse devices. /dev/gpmdata IS a valid mouse device. I think /dev/input/mice should be there too for USB mouse. It's this device that the USB guide on www.linux-usb.org refers to. And the one the kernel documentation (well linux/Documentation/usb/input.txt) suggests. there is also talk about all the /dev/input/mouse0, /dev/input/mouse1, ... but this would be usefull only for multiple mouses, and i have no experience with it. Friendly, Sven LUTHER -- Med venlig hilsen - Sincerely Morten B. Pedersen - [EMAIL PROTECTED] Copenhagen, Denmark. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: xserver-common phase2v15: dexter does not list /dev/gpmdata
I hadn't extensively played with it either, since I have a rather custom config (dual head with fixed-frequency monitors). Though, it would be nice if dexter could accept more monitor information, perhaps even a full XFree86 modeline. Hopefully that kind of additional support could be added later on. At least it doesn't overwrite XF86Config. =) On Wed, 11 Oct 2000, Derek Witt wrote: I'm using devfs in my case. I didn't see /dev/misc/psaux in dexter's list. I had to link that to /dev/mouse to keep dexter happy. Then, I had to edit /etc/X11/XF86Config to point to /dev/misc/psaux. Just a minor inconvenience. But, I like the premise behind dexter (it reminds me of xconfigurator from redhat). -- Derek J Witt, [EMAIL PROTECTED] On Wed, 11 Oct 2000 [EMAIL PROTECTED] wrote: /dev/gpmdata is not on the list of mouse devices. /dev/gpmdata IS a valid mouse device. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xserver-common phase2v15: dexter does not list /dev/gpmdata
On Wed, Oct 11, 2000 at 05:26:09 -0700, [EMAIL PROTECTED] wrote: /dev/gpmdata is not on the list of mouse devices. /dev/gpmdata IS a valid mouse device. I think /dev/input/mice should be there too for USB mouse. It's this device that the USB guide on www.linux-usb.org refers to. -- Med venlig hilsen - Sincerely Morten B. Pedersen - [EMAIL PROTECTED] Copenhagen, Denmark.
Re: xserver-common phase2v15: dexter does not list /dev/gpmdata
I hadn't extensively played with it either, since I have a rather custom config (dual head with fixed-frequency monitors). Though, it would be nice if dexter could accept more monitor information, perhaps even a full XFree86 modeline. Hopefully that kind of additional support could be added later on. At least it doesn't overwrite XF86Config. =) On Wed, 11 Oct 2000, Derek Witt wrote: I'm using devfs in my case. I didn't see /dev/misc/psaux in dexter's list. I had to link that to /dev/mouse to keep dexter happy. Then, I had to edit /etc/X11/XF86Config to point to /dev/misc/psaux. Just a minor inconvenience. But, I like the premise behind dexter (it reminds me of xconfigurator from redhat). -- Derek J Witt, [EMAIL PROTECTED] On Wed, 11 Oct 2000 [EMAIL PROTECTED] wrote: /dev/gpmdata is not on the list of mouse devices. /dev/gpmdata IS a valid mouse device. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [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: xserver-common phase2v15: dexter does not list /dev/gpmdata
On Wed, Oct 11, 2000 at 05:26:09 -0700, [EMAIL PROTECTED] wrote: /dev/gpmdata is not on the list of mouse devices. /dev/gpmdata IS a valid mouse device. I think /dev/input/mice should be there too for USB mouse. It's this device that the USB guide on www.linux-usb.org refers to. -- Med venlig hilsen - Sincerely Morten B. Pedersen - [EMAIL PROTECTED] Copenhagen, Denmark. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
dexter, mouse port
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 --- PGP signature
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!
Dexter feedback
Hi, after using Dexter I get a configuration which contains: Section Files FontPathunix:/7100# local font server # if the local font server has problems, we can fall back on these FontPath/usr/lib/X11/fonts/misc FontPath/usr/lib/X11/fonts/cyrillic FontPath/usr/lib/X11/fonts/100dpi:unscaled FontPath/usr/lib/X11/fonts/Type1 FontPath/usr/lib/X11/fonts/Speedo FontPath/usr/lib/X11/fonts/100dpi EndSection but I don't have xfonts-100dpi installed, only xfonts-75dpi. Arround line 335 of dexter it reads: NetMousePS/2 Genius NetMouse or NetMousePro \ this is the protocol I need to use, yet my mouse is a Logitech one. The generated config file load every module on the system, including the dri one, which needs this somewhere: Section DRI Mode 0666 EndSection Mode 0666 means anyone with a current connection to the X server can create a direct rendering context. You can specify a Group and use mode 0660 instead, but doesn't make sense on a default Debain installation. Marcelo
dexter dialog
Just fyi, dexter needs dialog, but it isn't in the depends list so if it's not installed dexter breaks. :) Stephen pgpriDmdMMlzt.pgp Description: PGP signature
xserver-common phase2v15: dexter does not list /dev/gpmdata
/dev/gpmdata is not on the list of mouse devices. /dev/gpmdata IS a valid mouse device.
dexter, mouse port
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 --- pgpeJaOtOtP6v.pgp Description: PGP signature
dexter
Hey, Dexter looks pretty cool; 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. 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. :) Thanks Branden (and others, if others need thanking. :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
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
dexter
Hey, Dexter looks pretty cool; 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. 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. :) Thanks Branden (and others, if others need thanking. :)
