Hia S.u.S.E I just gota say SaX is very nice. Its the new XFree86 manager that SuSE uses. Its less trouble than XF86Setup and thats a breeze itself. And does away with Xvideotune with its own tune which does a pretty good job. Way to go SuSE ! (still running SuSE 5.2 tho, just ) (just upgraded XFree3.3.2.+ from ) (the SuSE FTP site............... ) But why do I get these errors(always had em) when I restart a wm such as fvwm2 from X. X Error of failed request: BadDrawable (invalid Pixmap or Window parameter) Major opcode of failed request: 62 (X_CopyArea) Resource id in failed request: 0x3400002 Serial number of failed request: 205 Current serial number in output stream: 205 X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 4 (X_DestroyWindow) Resource id in failed request: 0x300000f Serial number of failed request: 1823 Current serial number in output stream: 1826 I wish I could fix these.. Steven Udell hettar@teleport.com - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
fwiw, i could not get sax to properly configure X on my laptop (gateway2200/C&T65554/800X600), buy XFree86 did it in a snap. -- michael Thus Spake: Steven Udell (hettar@teleport.com):
Hia S.u.S.E
I just gota say SaX is very nice. Its the new XFree86 manager that SuSE uses. Its less trouble than XF86Setup and thats a breeze itself. And does away with Xvideotune with its own tune which does a pretty good job. Way to go SuSE !
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
On 08-Sep-98 Steven Udell wrote:
Hia S.u.S.E
I just gota say SaX is very nice. Its the new XFree86 manager that SuSE uses. Its less trouble than XF86Setup and thats a breeze itself. And does away with Xvideotune with its own tune which does a pretty good job. Way to go SuSE !
Hmmmm My experience so far has been the other way around, with XF86Setup always producing a working XF86config, where as SaX has failed on every machine I've tried it on. Luckily I kept copies of working XF86config files from Slackware installations. Maybe when SaX is more mature it may be better, but it didnt seem to have as larger database of cards as XF86Setup.
But why do I get these errors(always had em) when I restart a wm such as fvwm2 from X.
X Error of failed request: BadDrawable (invalid Pixmap or Window parameter) Major opcode of failed request: 62 (X_CopyArea) Resource id in failed request: 0x3400002 Serial number of failed request: 205 Current serial number in output stream: 205 X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 4 (X_DestroyWindow) Resource id in failed request: 0x300000f Serial number of failed request: 1823 Current serial number in output stream: 1826
I wish I could fix these..
They look like bugs in fvwm2 rather than a X config problem (I have seen a few too using fvwm95). So far I'm getting used to SuSE and look forward to the K tools getting better. ---------------------------------- E-Mail: Peter Onion <ponion@srd.bt.co.uk> Date: 09-Sep-98 Time: 09:37:49 This message was sent by XFMail ---------------------------------- - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Peter Onion wrote:
On 08-Sep-98 Steven Udell wrote:
Hia S.u.S.E
I just gota say SaX is very nice. Its the new XFree86 manager that SuSE uses. Its less trouble than XF86Setup and thats a breeze itself. And does away with Xvideotune with its own tune which does a pretty good job. Way to go SuSE !
Hmmmm My experience so far has been the other way around, with XF86Setup always producing a working XF86config, where as SaX has failed on every machine I've tried it on. Luckily I kept copies of working XF86config files from Slackware installations. Maybe when SaX is more mature it may be better, but it didnt seem to have as larger database of cards as XF86Setup.
Intresting, this was a first responce to how my setup went with useing SaX. But I did incounter what I think is a bug. Everything looked ok at first, actually it looked great. But I quit out of X after writting this orignal message. and after a few things I tried to restart X only to have it error 111 and error 3 on me, saying it couldn't load the mouse. I went back into SaX and looked if I did any- thing wrong. Looked ok..saved again and exited..tried to start it again same thing. So I did my faithfull xf86config (forgetting XF86Setup at the time) "wanting more control of the problem" I set it up and startx.. everything fine, exit and restart again..works..np.. then I notice I only getting partial screen size of the virtual screen I am used too and that SaX provided. So I think of XF86Setup, I again set all my stuff up the way I have been doing it all along, and it works, but again not the screen size of the virtual screens were again messed. So I went back to SaX, but this time I told SaX to use my current modes. (mouse was working from the other setups but not SaX) so I just messed with the screen sizes in SaX and saved..and everything was perfect.. So in the end I used SaX for everything but the mouse. Strange, maybe SuSE can look into the mouse setup in SaX a bit more. Just a story (heh)"well thats what it looks like" Steve Udell - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
On Wed, 09 Sep 1998 02:11:58 -0700, Steven Udell writes about Re: [SuSE Linux] SaX:
Everything looked ok at first, actually it looked great. But I quit out of X after writting this orignal message. and after a few things I tried to restart X only to have it error 111 and error 3 on me, saying it couldn't load the mouse. I went back into SaX and looked if I did any-
I'm branching off here from the original thread, but can anyone please tell me what errors 111 and 3 mean, as I get this every time when I try and fail to get X to startx? S.u.S.E. 5.2 from the recent PC Plus cover disk, previously running Slackware 2.0 just great, upgrade broke my system :( I tried just about everything I can think of with xf86setup [which does not go to graphic mode, grips all the VTs, then flunks on me with unable to connect to X server message, console says errno = 111 and err 3 no process] and xf86config [through every possible IMHO setting for my CTX SVGA monitor and CL5435 1 meg graphics card, mode line, vsync and hsync settings, same errors as above] but no joy. Sound familiar to anyone? Regards Tony <tonyd@mersinet.co.uk> - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Hi, On Wed, 9 Sep 1998, Tony Dunn wrote:
I'm branching off here from the original thread, but can anyone please tell me what errors 111 and 3 mean, as I get this every time when I try and fail to get X to startx? S.u.S.E. 5.2 from the recent PC Plus cover disk, previously running Slackware 2.0 just great, upgrade broke my system :(
I tried just about everything I can think of with xf86setup [which does not go to graphic mode, grips all the VTs, then flunks on me with unable to connect to X server message, console says errno = 111 and err 3 no process] and xf86config [through every possible IMHO setting for my CTX SVGA monitor and CL5435 1 meg graphics card, mode line, vsync and hsync settings, same errors as above] but no joy.
Sound familiar to anyone?
Unfortunately, errno 111 is just an error from an X client (see the XFree86-FAQ at <A HREF="http://www.xfree86.org/FAQ/"><A HREF="http://www.xfree86.org/FAQ/</A">http://www.xfree86.org/FAQ/</A</A>> for details), it is not the error that caused the X server to crash. If you start X with the command "startx", you will find a log file in your home directory, called ~/.X.err, which you can examine with "less", for example. It contains all the startup-messages from the X-Server, maybe you can find a hint in there, what's going wrong in your case. Also make sure, that you have installed the correct X-Server ("rpm -q xsvga" should give you a version number), and that the link /var/X11R6/bin/X is pointing to /usr/X11R6/bin/XF86_SVGA. You can check this with the "file"-Command. For technical notes about running XFree on Cirrus-based cards, see the release notes at /usr/X11R6/lib/X11/doc/README.cirrus. The contain some useful hints. HTH, LenZ ------------------------------------------------------------------ Lenz Grimmer S.u.S.E. GmbH <A HREF="mailto:grimmer@suse.de">mailto:grimmer@suse.de</A> Gebhardtstrasse 2 <A HREF="http://www.suse.de"><A HREF="http://www.suse.de</A">http://www.suse.de</A</A>> 90762 Fuerth, Germany - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
For the people who didn't voted yet, go now on this page ! ---> <A HREF="http://www.linuxjournal.com/1998Readers/"><A HREF="http://www.linuxjournal.com/1998Readers/</A">http://www.linuxjournal.com/1998Readers/</A</A>> <--- "Welcome to Linux Journal's fourth annual Readers' Choice awards! This years survey is bigger and better than ever before, so don't be left out. The voting will be open through September 30, 1998. Results will be featured in Linux Journal's January 1999 issue." Cheers, Olivier - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
On Wed, 9 Sep 1998 23:14:21 +0200 (MEST), Lenz Grimmer writes about Re: [SuSE Linux] SaX:
I tried just about everything I can think of with xf86setup [which does not go to graphic mode, grips all the VTs, then flunks on me with unable to connect to X server message, console says errno = 111 and err 3 no process] and xf86config [through every possible IMHO setting for my CTX SVGA monitor and CL5435 1 meg graphics card, mode line, vsync and hsync settings, same errors as above] but no joy.
Sound familiar to anyone?
Unfortunately, errno 111 is just an error from an X client (see the XFree86-FAQ at <A HREF="http://www.xfree86.org/FAQ/"><A HREF="http://www.xfree86.org/FAQ/</A">http://www.xfree86.org/FAQ/</A</A>> for details), it is not the error that caused the X server to crash. If you start X with the command "startx", you will find a log file in your home directory, called ~/.X.err, which you can examine with "less", for example. It contains all the startup-messages from the X-Server, maybe you can find a hint in there, what's going wrong in your case. Also make sure, that you have
I didn't realise that startx dumped to a file so I did it manually at first, with the same results! Been using that of course to try to figure out my problems - would there be any objections if I posted it here?
installed the correct X-Server ("rpm -q xsvga" should give you a version
Will give that a shot - I *did* wonder if the older version of XF86_SVGA from my once-working Slackware setup might be worth trying, as it worked before?
number), and that the link /var/X11R6/bin/X is pointing to /usr/X11R6/bin/XF86_SVGA. You can check this with the "file"-Command. For technical notes about running XFree on Cirrus-based cards, see the release notes at /usr/X11R6/lib/X11/doc/README.cirrus. The contain some useful hints.
I checked with ls -la and the sym_link is right. I know because I killed the link to X, startx'd and got no link errors, then re-did it with ln and back to sq. 1 :( Thanks for your thoughts - I'll get there... Regards Tony <tonyd@mersinet.co.uk> - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Tony Dunn wrote:
I'm branching off here from the original thread, but can anyone please tell me what errors 111 and 3 mean, as I get this every time when I try and fail to get X to startx?
ummmmThis dosent address your question but may help one thing I found regarding errors <no mode or expected mode> was to closley look at the xf86 file use pico and search for mode I found that somehow the config program diddnt place " " around the selected mode. it would look like 800 400 when it should look like "800 400" I have an ancient 386 that balked like hell about <mode expected> when I noticed other modes had " " I added them and wallah! ... no more balking. (it dosent like windows though) if Its a mode error check for quotation marks missing is your mouse ps/2 if so try /dev/psaux also my experience with saX wasnt good either. It looked nice.All my hardware is generic this and that even still I went back to XF86Config my 2cts rob - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
On Wed, 09 Sep 1998 18:14:20 -0400, Robert Metelsky writes about Re: [SuSE Linux] SaX:
I found that somehow the config program diddnt place " " around the selected mode. it would look like 800 400 when it should look like "800 400" I have an ancient 386 that balked like hell about <mode expected> when I noticed other modes had " " I added them and wallah! ... no more balking. (it dosent like windows though)
Just checked my XF86Config and the modelines in compact format all have the modes quoted.
also my experience with saX wasnt good either. It looked nice.All my hardware is generic this and that even still I went back to XF86Config my 2cts
I never used saX but am willing to try anything, as so far xf86Set and xf86config have failed me, the latter usually so reliable in my experience. Thanks Tony <tonyd@mersinet.co.uk> - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Op Wed, Sep 09, 1998 at 09:42:35AM +0100, schreef Peter Onion:
On 08-Sep-98 Steven Udell wrote:
I just gota say SaX is very nice. Its the new XFree86 manager that SuSE uses. Its less trouble than XF86Setup and thats a breeze itself. And does away with Xvideotune with its own tune which does a pretty good job. Way to go SuSE !
Hmmmm My experience so far has been the other way around, with XF86Setup always producing a working XF86config, where as SaX has failed on every machine I've tried it on. Luckily I kept copies of working XF86config files from Slackware installations. Maybe when SaX is more mature it may be better, but it didnt seem to have as larger database of cards as XF86Setup.
my experience with SAX is a little worse. Sure, it looks nice, is intuative, etc. But when it fails to make a working copy of my config file, all those nice things are a little useless ;-) 1 sax keeps complaining about no drivers for the Diamond sthealth video 2100 series. 2 when it scans my pci bus it in default picks a generic x server collection -- S3, but that one does not work (it cannot start the x-server). workaround: start sax, use the saved file, let it scan the pci-bus, select Diamond, select expert, xserver S3, let sax start the x server, save the config file and let it write /etc/XF86Config, exit SAX and YAST, startx. After every reboot i have to do the same config-blabla to get x working. anyone having ideas? grtz Bouke -- Well, it's September. All the new students getting their accounts. All the clueless newbies crashing in on the net. All of them surfing and looking at and downloading PIX. Everyone is unhappy for a while, and that includes the machines. Still wondering why the net is slow? :-) - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Bouke van der Voet wrote:
Op Wed, Sep 09, 1998 at 09:42:35AM +0100, schreef Peter Onion:
On 08-Sep-98 Steven Udell wrote:
I just gota say SaX is very nice. Its the new XFree86 manager that SuSE uses. Its less trouble than XF86Setup and thats a breeze itself. And does away with Xvideotune with its own tune which does a pretty good job. Way to go SuSE !
Hmmmm My experience so far has been the other way around, with XF86Setup always producing a working XF86config, where as SaX has failed on every machine I've tried it on. Luckily I kept copies of working XF86config files from Slackware installations. Maybe when SaX is more mature it may be better, but it didnt seem to have as larger database of cards as XF86Setup.
my experience with SAX is a little worse. Sure, it looks nice, is intuative, etc. But when it fails to make a working copy of my config file, all those nice things are a little useless ;-)
2 when it scans my pci bus it in default picks a generic x server collection -- S3, but that one does not work (it cannot start the x-server). workaround: start sax, use the saved file, let it scan the pci-bus, select Diamond, select expert, xserver S3, let sax start the x server, save the config file and let it write /etc/XF86Config, exit SAX and YAST, startx.
After every reboot i have to do the same config-blabla to get x working.
anyone having ideas?
Well, it's September. All the new students getting their accounts. All the clueless newbies crashing in on the net. All of them surfing and looking at and downloading PIX. Everyone is unhappy for a while, and that includes the machines. Still wondering why the net is slow? :-) - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Just a thought, but Yast already having some sort of problem in 5.3. I might suggest trying SaX outside of Yast from the command line. you@soinso:/home/you > SaX Dunno if it will help you tho. Can alway use XF86Setup or xf86config instead of SaX .. Steve Udell - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Op Wed, Sep 09, 1998 at 04:00:58AM -0700, schreef Steven Udell:
Bouke van der Voet wrote:
Op Wed, Sep 09, 1998 at 09:42:35AM +0100, schreef Peter Onion:
Hmmmm My experience so far has been the other way around, with XF86Setup always producing a working XF86config, where as SaX has failed on every machine I've tried it on. Luckily I kept copies of working XF86config files from Slackware installations. Maybe when SaX is more mature it may be better, but it didnt seem to have as larger database of cards as XF86Setup.
my experience with SAX is a little worse. Sure, it looks nice, is intuative, etc. But when it fails to make a working copy of my config file, all those nice things are a little useless ;-)
2 when it scans my pci bus it in default picks a generic x server collection -- S3, but that one does not work (it cannot start the x-server). workaround: start sax, use the saved file, let it scan the pci-bus, select Diamond, select expert, xserver S3, let sax start the x server, save the config file and let it write /etc/XF86Config, exit SAX and YAST, startx.
After every reboot i have to do the same config-blabla to get x working.
anyone having ideas?
Just a thought, but Yast already having some sort of problem in 5.3. I might suggest trying SaX outside of Yast from the command line.
you@soinso:/home/you > SaX
Dunno if it will help you tho. Can alway use XF86Setup or xf86config instead of SaX ..
Done that already. gives the same problems. Starting x gives a "mouse-error" en than fails to start te S3-x server. Using XF86Setup or xf86config is a workaround, not a bugfix ;-) Could anyone form SuSE give an update on what they think of it? grtz Bouke -- Well, it's September. All the new students getting their accounts. All the clueless newbies crashing in on the net. All of them surfing and looking at and downloading PIX. Everyone is unhappy for a while, and that includes the machines. Still wondering why the net is slow? :-) - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
Hi, On Wed, 9 Sep 1998, Bouke van der Voet wrote:
Starting x gives a "mouse-error" en than fails to start te S3-x server. Using XF86Setup or xf86config is a workaround, not a bugfix ;-)
This is unusual. SaX does nothing else than the other tools; it creates an /etc/XF86Config. Could you post the complete error log and the relevant part from the config file? Maybe we will find out, what's going wrong. LenZ ------------------------------------------------------------------ Lenz Grimmer S.u.S.E. GmbH <A HREF="mailto:grimmer@suse.de">mailto:grimmer@suse.de</A> Gebhardtstrasse 2 <A HREF="http://www.suse.de"><A HREF="http://www.suse.de</A">http://www.suse.de</A</A>> 90762 Fuerth, Germany - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
After reloading Suse 5.3 last night, I was having the same problem. X would not start and gave a fatal error message about the mouse. If I go into yast and configure the mouse, I can start X then. I'm using the S3-V server. -darrel ============================================ Darrel Davis darreld@his.com darreld@hotmail.com ============================================ On Wed, 9 Sep 1998, Lenz Grimmer wrote:
Hi,
On Wed, 9 Sep 1998, Bouke van der Voet wrote:
Starting x gives a "mouse-error" en than fails to start te S3-x server. Using XF86Setup or xf86config is a workaround, not a bugfix ;-)
This is unusual. SaX does nothing else than the other tools; it creates an /etc/XF86Config. Could you post the complete error log and the relevant part from the config file? Maybe we will find out, what's going wrong.
LenZ
------------------------------------------------------------------ Lenz Grimmer S.u.S.E. GmbH <A HREF="mailto:grimmer@suse.de">mailto:grimmer@suse.de</A> Gebhardtstrasse 2 <A HREF="http://www.suse.de"><A HREF="http://www.suse.de</A">http://www.suse.de</A</A>> 90762 Fuerth, Germany
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e
participants (9)
-
bouke＠xs4all.nl -
darreld＠mail.his.com -
grimmer＠suse.de -
hettar＠teleport.com -
mgx＠spruce.lsd.ornl.gov -
ponion＠srd.bt.co.uk -
reefkeep＠connix.com -
suseml＠orion.www-hosting.ch -
tonyd＠mersinet.co.uk