Re: Unidentified subject!
On Sun, 2003-03-02 at 23:42, Branden Robinson wrote: The radeon module is a *sub*module of the ati module. You should probably be using the ati driver instead, which will autoload the radeon module for your hardware. If you had let debconf manage your XF86Config-4 file, this would have been autodetected, or you would have been given the option of using the ati module (but not radeon). Hi Branden, dpkg-reconfigure xserver-xfree86 lets me pick 'ati' or 'radeon', and since 'radeon' seems more specific to my hardware, I chose that one. I might change and see what happens, although I've not noticed any problems so far ... KUTGW. -- Paul J. Keenan [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Unidentified subject!
On Tue, Mar 04, 2003 at 10:20:59PM +, Paul J. Keenan wrote: Hi Branden, dpkg-reconfigure xserver-xfree86 lets me pick 'ati' or 'radeon', and since 'radeon' seems more specific to my hardware, I chose that one. I might change and see what happens, although I've not noticed any problems so far ... KUTGW. Oh, damn. I know why this is. It started showing up when I added the code that autodetected the video drivers. Damn damn damn. Now I'll have to manually exclude them, and force existing values of radeon and r128 to ati. Sigh. :-P Thanks for the heads-up. -- G. Branden Robinson| Life is what happens to you while Debian GNU/Linux | you're busy making other plans. [EMAIL PROTECTED] | -- John Lennon http://people.debian.org/~branden/ | pgp0.pgp Description: PGP signature
Re: Unidentified subject!
On Sun, 2003-03-02 at 23:42, Branden Robinson wrote: The radeon module is a *sub*module of the ati module. You should probably be using the ati driver instead, which will autoload the radeon module for your hardware. If you had let debconf manage your XF86Config-4 file, this would have been autodetected, or you would have been given the option of using the ati module (but not radeon). Hi Branden, dpkg-reconfigure xserver-xfree86 lets me pick 'ati' or 'radeon', and since 'radeon' seems more specific to my hardware, I chose that one. I might change and see what happens, although I've not noticed any problems so far ... KUTGW. -- Paul J. Keenan [EMAIL PROTECTED]
Re: Unidentified subject!
On Tue, Mar 04, 2003 at 10:20:59PM +, Paul J. Keenan wrote: Hi Branden, dpkg-reconfigure xserver-xfree86 lets me pick 'ati' or 'radeon', and since 'radeon' seems more specific to my hardware, I chose that one. I might change and see what happens, although I've not noticed any problems so far ... KUTGW. Oh, damn. I know why this is. It started showing up when I added the code that autodetected the video drivers. Damn damn damn. Now I'll have to manually exclude them, and force existing values of radeon and r128 to ati. Sigh. :-P Thanks for the heads-up. -- G. Branden Robinson| Life is what happens to you while Debian GNU/Linux | you're busy making other plans. [EMAIL PROTECTED] | -- John Lennon http://people.debian.org/~branden/ | pgpCB2r5YOQH8.pgp Description: PGP signature
Re: Unidentified subject!
On Sun, Mar 02, 2003 at 11:42:42AM -0500, Noah silva wrote: My X was working fine, then I did an update (running unstable, only because I wanted gnome2), and X magically stopped working. I get an error about Module XIE, and some unresolved symbols from the radeon driver. Kernel is 2.4.20-k7 I believe. You appear to have told debconf not to manage your XF86Config-4 file; if you hadn't, you might not be experiencing some of these problems. Locate finds no file with the name xie except for pixe=ie related stuff. I checked on a rh8.1 beta machine, and it has no xie in the config, so I suppose this was soething that has disappeared. I tried commenting it out, but X still doesn't start (the failed dependencies?) XIE is no longer supported by XFree86. If you had let debconf manage your XF86Config-4 file, that line would have been removed automatically. (Also, the mouse wheel works with PS/2 mouse, but not when I switched to my USB mouse, but this was some time ago...) I'm not sure what to tell you about that except that USB mice with wheels generally work with debconf-managed config files. Section Device Identifier Radeon 1 # Driver sis # Driver s3virge Driver radeon Screen 0 EndSection # 2002.09.29 NJS Added Section Device Identifier Radeon 2 Driver radeon Screen 1 EndSection The radeon module is a *sub*module of the ati module. You should probably be using the ati driver instead, which will autoload the radeon module for your hardware. If you had let debconf manage your XF86Config-4 file, this would have been autodetected, or you would have been given the option of using the ati module (but not radeon). [...] (WW) Symbol fbdevHWLeaveVT from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol fbdevHWRestore from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol fbdevHWSave from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol vgaHWFreeHWRec from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol XAADestroyInfoRec from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol xf86DestroyCursorInfoRec from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol fbdevHWEnterVT from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol vgaHWRestore from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol vgaHWUnlock from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol vgaHWGetIndex from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol vgaHWLock from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol vgaHWRestore from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol vgaHWUnlock from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol vgaHWGetIndex from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol vgaHWLock from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol vgaHWSave from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol vgaHWUnlock from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol vgaHWGetIndex from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol fbdevHWLoadPalette from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol fbPictureInit from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol fbScreenInit from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol fbdevHWModeInit from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol fbdevHWValidMode from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol fbdevHWAdjustFrame from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol fbdevHWSwitchMode from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol fbdevHWInit from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol vgaHWGetIOBase from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol vgaHWGetIndex from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol vgaHWGetHWRec from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol vgaHWFreeHWRec from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol fbdevHWUseBuildinMode from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol xf86I2CBusInit from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol xf86CreateI2CBusRec from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol fbdevHWGetVidmem from module
Re: Unidentified subject!
The strange thing is this: What fixed it was removing some unused (but valid) cruft, including the sections for the second monitor (which I don't have plugged in anyhow). How these sections (which validated fine before) could have led to unresolved symbols The wheel mouse I really don't get because I looked at the auto-configured mouse in redhat and the XF86Config file is identical in that respect. I will take your advice and play with debconf. thanks for your help, noah silva On Sun, 2 Mar 2003, Branden Robinson wrote: On Sun, Mar 02, 2003 at 11:42:42AM -0500, Noah silva wrote: My X was working fine, then I did an update (running unstable, only because I wanted gnome2), and X magically stopped working. I get an error about Module XIE, and some unresolved symbols from the radeon driver. Kernel is 2.4.20-k7 I believe. You appear to have told debconf not to manage your XF86Config-4 file; if you hadn't, you might not be experiencing some of these problems. Locate finds no file with the name xie except for pixe=ie related stuff. I checked on a rh8.1 beta machine, and it has no xie in the config, so I suppose this was soething that has disappeared. I tried commenting it out, but X still doesn't start (the failed dependencies?) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Unidentified subject!
On Sun, Mar 02, 2003 at 11:42:42AM -0500, Noah silva wrote: My X was working fine, then I did an update (running unstable, only because I wanted gnome2), and X magically stopped working. I get an error about Module XIE, and some unresolved symbols from the radeon driver. Kernel is 2.4.20-k7 I believe. You appear to have told debconf not to manage your XF86Config-4 file; if you hadn't, you might not be experiencing some of these problems. Locate finds no file with the name xie except for pixe=ie related stuff. I checked on a rh8.1 beta machine, and it has no xie in the config, so I suppose this was soething that has disappeared. I tried commenting it out, but X still doesn't start (the failed dependencies?) XIE is no longer supported by XFree86. If you had let debconf manage your XF86Config-4 file, that line would have been removed automatically. (Also, the mouse wheel works with PS/2 mouse, but not when I switched to my USB mouse, but this was some time ago...) I'm not sure what to tell you about that except that USB mice with wheels generally work with debconf-managed config files. Section Device Identifier Radeon 1 # Driver sis # Driver s3virge Driver radeon Screen 0 EndSection # 2002.09.29 NJS Added Section Device Identifier Radeon 2 Driver radeon Screen 1 EndSection The radeon module is a *sub*module of the ati module. You should probably be using the ati driver instead, which will autoload the radeon module for your hardware. If you had let debconf manage your XF86Config-4 file, this would have been autodetected, or you would have been given the option of using the ati module (but not radeon). [...] (WW) Symbol fbdevHWLeaveVT from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol fbdevHWRestore from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol fbdevHWSave from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol vgaHWFreeHWRec from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol XAADestroyInfoRec from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol xf86DestroyCursorInfoRec from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol fbdevHWEnterVT from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol vgaHWRestore from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol vgaHWUnlock from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol vgaHWGetIndex from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol vgaHWLock from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol vgaHWRestore from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol vgaHWUnlock from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol vgaHWGetIndex from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol vgaHWLock from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol vgaHWSave from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol vgaHWUnlock from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol vgaHWGetIndex from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol fbdevHWLoadPalette from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol fbPictureInit from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol fbScreenInit from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol fbdevHWModeInit from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol fbdevHWValidMode from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol fbdevHWAdjustFrame from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol fbdevHWSwitchMode from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol fbdevHWInit from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol vgaHWGetIOBase from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol vgaHWGetIndex from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol vgaHWGetHWRec from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol vgaHWFreeHWRec from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol fbdevHWUseBuildinMode from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol xf86I2CBusInit from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol xf86CreateI2CBusRec from module /usr/X11R6/lib/modules/drivers/radeon_drv.o is unresolved! Symbol fbdevHWGetVidmem from module
Re: Unidentified subject!
The strange thing is this: What fixed it was removing some unused (but valid) cruft, including the sections for the second monitor (which I don't have plugged in anyhow). How these sections (which validated fine before) could have led to unresolved symbols The wheel mouse I really don't get because I looked at the auto-configured mouse in redhat and the XF86Config file is identical in that respect. I will take your advice and play with debconf. thanks for your help, noah silva On Sun, 2 Mar 2003, Branden Robinson wrote: On Sun, Mar 02, 2003 at 11:42:42AM -0500, Noah silva wrote: My X was working fine, then I did an update (running unstable, only because I wanted gnome2), and X magically stopped working. I get an error about Module XIE, and some unresolved symbols from the radeon driver. Kernel is 2.4.20-k7 I believe. You appear to have told debconf not to manage your XF86Config-4 file; if you hadn't, you might not be experiencing some of these problems. Locate finds no file with the name xie except for pixe=ie related stuff. I checked on a rh8.1 beta machine, and it has no xie in the config, so I suppose this was soething that has disappeared. I tried commenting it out, but X still doesn't start (the failed dependencies?)
Re: Unidentified subject!
Please see: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=182687 -- G. Branden Robinson| It's not a matter of alienating Debian GNU/Linux | authors. They have every right to [EMAIL PROTECTED] | license their software however we http://people.debian.org/~branden/ | like. -- Craig Sanders pgpwrIAgIKjWf.pgp Description: PGP signature
Re: Unidentified subject!
On Tue, Oct 10, 2000 at 11:03:26PM -0500, Branden Robinson wrote: Dexter wouldn't detect my mouse (I with gpm on and gpm off, I tried linking /dev/mouse to both /dev/gpmdata and /dev/psaux ie. ln -sf /dev/psaux /dev/mouse. What do you mean it wouldn't detect your mouse? It doesn't try. (It uses a program called mdetect to do so, if that program is present.) mdetect is something we're using at Progeny and which I plan to package for Debian once I've got it un-automade. This is really confusing. Dexter should not present a can try again to detect your mouse dialog if the tool it uses to do so is not there. It does, currently. Confused the heck out of me when it told me I had no mouse. Dan /\ /\ | Daniel Jacobowitz|__|SCS Class of 2002 | | Debian GNU/Linux Developer__Carnegie Mellon University | | [EMAIL PROTECTED] | | [EMAIL PROTECTED] | \/ \/
Re: Unidentified subject!
On Wed, Oct 11, 2000 at 12:10:33AM -0400, Daniel Jacobowitz wrote: This is really confusing. Dexter should not present a can try again to detect your mouse dialog if the tool it uses to do so is not there. It does, currently. Confused the heck out of me when it told me I had no mouse. Gack! It shouldn't have done that! The problem is line 285. Of course an unset variable isn't equal to 0. Sorry about that. Fix will be in v16. -- G. Branden Robinson | Yesterday upon the stair, Debian GNU/Linux| I met a man who wasn't there. [EMAIL PROTECTED] | He wasn't there again today, http://www.debian.org/~branden/ | I think he's from the CIA. pgpruZm8Qc9H5.pgp Description: PGP signature
Re: Unidentified subject!
Chris, I have a logitech corded wheel mouse (the underside claims it is a model M-C48, but I *think* its retail name is ``first mouse+'') ps/2, that works quite well under XF864.0.1. I do not have gpm installed. Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "IMPS/2" Option "Device" "/dev/mouse" Option "ZAxisMapping" "4 5" EndSection /dev/mouse is a symlink to /dev/psaux. I am running an ABIT dual celeron machine, g400max with the matrox supplied drivers. HTH * Chris Hanlon [EMAIL PROTECTED] [001010 19:00]: Debian XFree86 4.0.x test notes I have being using 4.0.x on debian woody with the following hardware + software setup since Phase2 debs started to show up. Voodoo 3 2000 (pci) video card Logitech cordless wheel mouse (ps/2) Abit KA7 motherboard (RX and TY bios) Samsung SyncMaster 955SL monitor 2.4.0-test[1,5,6,8,9] kernel I have the following notes Mouse problems -- The mouse jumps allover the place and clicks randomly if I'm running X as a regular user and gpm is running The mouse will not move if I run X as root and gpm is running. The mouse occasionally clicked (while moving) until I upgraded my bios to the TY bios. BTW. The TY bios fixes a "win95 only" ps/2 mouse bug. My XF86Config-4 says the following Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "MouseManPlusPS/2" Option "Device" "/dev/psaux" EndSection DEXTER -- Dexter wouldn't run as /etc/X11/dexter-tmp didn't exist. This stoped phase2v14 xserver-xfree86 debs from installing. Dexter wouldn't detect my mouse (I with gpm on and gpm off, I tried linking /dev/mouse to both /dev/gpmdata and /dev/psaux ie. ln -sf /dev/psaux /dev/mouse. Dexter doesn't list any refresh rates between 60 and 85 for the resolution 1280x1024 (I use 79 (75 will do but 60 is yukky and 85 doesn't work)). -- Is anyone else having similar mouse problems? Does anyone have a similar mouse working corectly Chris -- 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: Unidentified subject!
On Mon, Oct 09, 2000 at 11:59:49PM -0700, Chris Hanlon wrote: DEXTER -- Dexter wouldn't run as /etc/X11/dexter-tmp didn't exist. This stoped phase2v14 xserver-xfree86 debs from installing. This is fixed in v15, available now. Dexter wouldn't detect my mouse (I with gpm on and gpm off, I tried linking /dev/mouse to both /dev/gpmdata and /dev/psaux ie. ln -sf /dev/psaux /dev/mouse. What do you mean it wouldn't "detect" your mouse? It doesn't try. (It uses a program called mdetect to do so, if that program is present.) mdetect is something we're using at Progeny and which I plan to package for Debian once I've got it un-automade. Dexter doesn't list any refresh rates between 60 and 85 for the resolution 1280x1024 (I use 79 (75 will do but 60 is yukky and 85 doesn't work)). These are example modes. If you're unhappy with the selection I suggest getting the monitor data and using expert mode. Is anyone else having similar mouse problems? Does anyone have a similar mouse working corectly Yes, on my box at home: Section "InputDevice" Identifier "Logitech Mouse" Driver "mouse" Option "Protocol" "MouseManPlusPS/2" Option "Device""/dev/psaux" EndSection -- G. Branden Robinson | What influenced me to atheism was Debian GNU/Linux| reading the Bible cover to cover. [EMAIL PROTECTED] | Twice. http://www.debian.org/~branden/ | -- J. Michael Straczynski PGP signature
Re: Unidentified subject!
On Tue, Oct 10, 2000 at 11:03:26PM -0500, Branden Robinson wrote: Dexter wouldn't detect my mouse (I with gpm on and gpm off, I tried linking /dev/mouse to both /dev/gpmdata and /dev/psaux ie. ln -sf /dev/psaux /dev/mouse. What do you mean it wouldn't "detect" your mouse? It doesn't try. (It uses a program called mdetect to do so, if that program is present.) mdetect is something we're using at Progeny and which I plan to package for Debian once I've got it un-automade. This is really confusing. Dexter should not present a "can try again to detect your mouse" dialog if the tool it uses to do so is not there. It does, currently. Confused the heck out of me when it told me I had no mouse. Dan /\ /\ | Daniel Jacobowitz|__|SCS Class of 2002 | | Debian GNU/Linux Developer__Carnegie Mellon University | | [EMAIL PROTECTED] | | [EMAIL PROTECTED] | \/ \/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Unidentified subject!
Chris, I have a logitech corded wheel mouse (the underside claims it is a model M-C48, but I *think* its retail name is ``first mouse+'') ps/2, that works quite well under XF864.0.1. I do not have gpm installed. Section InputDevice Identifier Mouse0 Driver mouse Option Protocol IMPS/2 Option Device /dev/mouse Option ZAxisMapping 4 5 EndSection /dev/mouse is a symlink to /dev/psaux. I am running an ABIT dual celeron machine, g400max with the matrox supplied drivers. HTH * Chris Hanlon [EMAIL PROTECTED] [001010 19:00]: Debian XFree86 4.0.x test notes I have being using 4.0.x on debian woody with the following hardware + software setup since Phase2 debs started to show up. Voodoo 3 2000 (pci) video card Logitech cordless wheel mouse (ps/2) Abit KA7 motherboard (RX and TY bios) Samsung SyncMaster 955SL monitor 2.4.0-test[1,5,6,8,9] kernel I have the following notes Mouse problems -- The mouse jumps allover the place and clicks randomly if I'm running X as a regular user and gpm is running The mouse will not move if I run X as root and gpm is running. The mouse occasionally clicked (while moving) until I upgraded my bios to the TY bios. BTW. The TY bios fixes a win95 only ps/2 mouse bug. My XF86Config-4 says the following Section InputDevice Identifier Mouse0 Driver mouse Option Protocol MouseManPlusPS/2 Option Device /dev/psaux EndSection DEXTER -- Dexter wouldn't run as /etc/X11/dexter-tmp didn't exist. This stoped phase2v14 xserver-xfree86 debs from installing. Dexter wouldn't detect my mouse (I with gpm on and gpm off, I tried linking /dev/mouse to both /dev/gpmdata and /dev/psaux ie. ln -sf /dev/psaux /dev/mouse. Dexter doesn't list any refresh rates between 60 and 85 for the resolution 1280x1024 (I use 79 (75 will do but 60 is yukky and 85 doesn't work)). -- Is anyone else having similar mouse problems? Does anyone have a similar mouse working corectly Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Unidentified subject!
I believe there is an SiS X server that you may need to download. I think it's called sis-xserver in apt-get (someone comfirm this for me?). If not, you can download the server from linux.tucows.com (or www.xfree86.org). Good Luck. ** 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: Unidentified subject!
I believe there is an SiS X server that you may need to download. I think it's called sis-xserver in apt-get (someone comfirm this for me?). If not, you can download the server from linux.tucows.com (or www.xfree86.org). Good Luck. ** 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: Unidentified subject!
On Wed, Sep 15, 1999 at 05:10:33PM +0200, Nils Lohner wrote: Someone has patches to allow XF86 to be built under Windoze with cygwin, and the XF people are reluctant to let them in due to commercial interestes, i.e. the finished X server binaries can't be bundled with other software. Where do I find a clue bat large enough to change this thinking? Please have a lok at the mail below and let me know what I can possibly do. Yes, I saw the gigantic flamewar on xfree86-devel about this, which was hopelessly entagled with what I'm sure is the thousandth iteration of a BSD vs. GPL licensing flamewar on that list. My thinking: the patches do not force you to use cygwin to compile, but rather just enable it for those who want it, and so I don't see any reason why the XF people should object to the patches. They enhance and do not limit in any way. If someone else wants to posrt it to a compiler with a different license, noone is stopping them. That's true. This is really frustrating me, people being this narrow minded (what's the politically correct term for that? :) and I'm hoping people here will have some useful suggestions. Uh, this mailing list is brand new and pretty limited in scope. (See the charter at http://www.debian.org/~branden/.) If some folks here want to form or join a coalition about this, I don't care, but I personally have too many irons in the fire as is and don't have much personal interest in such a thing (though you can be sure I'd use it if it saw the light of day). Ultimately I think the best way to change XFree86's mind on things like this is: 1) Make very sure all these cygwin changes are MIT-licensed. I don't see why this should be such a big deal as the X source base already supports tons of proprietary compilation environments already. 2) If they don't listen, fork. The sound of moving feet is a powerful motivator. When interests diverge, this is often the best thing to do. Point 2 has problems with the XFree86 membership agreement, though, especially if the current patches are based against the CVS version of the XFree86 code. Then again, with 3.9.16 out, how different can it be? I don't really have much more advice than that. I also don't feel this topic is terribly germane to this list, so if interested parties from this list would consider mailing each other about I'd appreciate it. Sorry to sound so uninterested but I really just have too much on my plate to concern myself with XFree86 for Windows. I hope you can sympathize. -- G. Branden Robinson | You don't just decide to break Kubrick's Debian GNU/Linux | code of silence and then get drawn away [EMAIL PROTECTED] | from it to a discussion about cough cartoon.ecn.purdue.edu/~branden/ | medicine. pgpWdamOl7sU8.pgp Description: PGP signature
