Re: XF86 3.3-3
On Mon, 14 Jul 1997, Kevin M. Bealer wrote: [cut] > I found my keyboard/screen, and possibly the whole thing (don't > remember) would lock up when I had an S3, but adding the "nolinear" > option fixed the problem. This was with the older version, i.e. it > happened with 3.1 or 3.2. However, other things changed with my > config at 3.3, so maybe you might want to try turning options like > this on and off. Yeah...I've never had to use any special options before. I did try nolinear this time out of desperation, but it didn't help. In any event, I succesfully downgraded to 3.2 and I am happy again. [cut] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: XF86 3.3-3
Christopher Jason Morrone wrote: (clip) > >In any case, the XF86 3.3 packages are definitely broken. I'd fill out a >bug report, but unfortunately, I can't be any more specific than that >right now. > (clip) > >-- >TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to >[EMAIL PROTECTED] . >Trouble? e-mail to [EMAIL PROTECTED] . > > I found my keyboard/screen, and possibly the whole thing (don't remember) would lock up when I had an S3, but adding the "nolinear" option fixed the problem. This was with the older version, i.e. it happened with 3.1 or 3.2. However, other things changed with my config at 3.3, so maybe you might want to try turning options like this on and off. Video was an S3 on the mainboard, now I have upgraded both and "xf86config" got me a fairly good config, although my old compaq monitor can't keep up to the new video card frequency wise. (I know this post is a little light on the solution side, but noone seems to have "definitely hit the nail" yet, so.) [EMAIL PROTECTED]/GNU--1.3---Linux--2.0.30--- "You are in a maze of twisty little passages, all alike." -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: XF86 3.3-3
On Thu, 10 Jul 1997, Joost Kooij wrote: > > > On Wed, 9 Jul 1997, Ralph Winslow wrote: > > > Christopher Jason Morrone wrote: > > > > > [ Problems, "help!" ] > > > > > > > > This also reflects my experience exactly. HELP!! > > It works fine for me. I also did an upgrade from 1.2 to 1.3 and noticed > the following: Well, thats not exactly what I did...I upgraded to Debian 1.3 when it first came out. I just now upgraded my X 3.2 to 3.3 when IT came out. [cut] > have to do that), have you tried to remove (rename) the old configuration > files and then run either 'xbase-configure' or 'XF86Setup'? After that you Yep, tried that. > can always tweak the new file using parts of the old file (read the new > docs too before you do this). Tried that too, somewhat...I'm not doing anything radical in my old configs. They are standard XF86Setup stuff. I ran the new XF86Setup and things look damn similar to me. > > Good luck, > > Joost [cut] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: XF86 3.3-3
On Wed, 9 Jul 1997, Ralph Winslow wrote: > Christopher Jason Morrone wrote: > > [ Problems, "help!" ] > > > > This also reflects my experience exactly. HELP!! It works fine for me. I also did an upgrade from 1.2 to 1.3 and noticed the following: XFree86 3.2 servers are not exactly the same as XFree86 3.3 servers; The configuration that once worked fine might not be perfect anymore; The configuration tools in the new package might not be entirely flawless. I have an s3virge card and upgrading the virge server was not entirely succesfull. Changing to the new svga server solved the problems. Besides purging everything and reinstalling (you probably don't want to have to do that), have you tried to remove (rename) the old configuration files and then run either 'xbase-configure' or 'XF86Setup'? After that you can always tweak the new file using parts of the old file (read the new docs too before you do this). Good luck, Joost ps: here's something from a few days ago that I kept in my mailbox: On Tue, 1 Jul 1997, Tim Sailer wrote: > In your email to me, Dale Scheetz, you wrote: > > > > On Tue, 1 Jul 1997, Adam Shand wrote: > > > > > I have just installed all the X packages (xbase, xserver-svga etc) on my > > > Thinkpad laptop 755CX. I was having troubles and assumed it was my > > > inexperience with X that was doing it :) > > > > > > I now have a friend here who is familiar with X and now that we are > > > playing > > > properly with it we have found that it doesn't seem to be finding our > > > XF86Config file. The file is kept in /usr/X11 and there is a link to it > > > in > > > /usr/X11R6/lib/X11?? > > > > > > It is dying with the error that no appropriate screen resolutions can be > > > found. Does anyone know what this could be or do you need more details? > > > > > Sounds like you chose the wrong card information. Did you install this > > with dselect? Did you use the xbase configuration options? > > > > If you move your XF86Config file out of the way (save it under a different > > name) you should be able to run xbase-configure and rebuilt this file. You > > should change the Xserver file to point to VGA16 for the configuration, > > and then return to your prefered server after the configuration. If you > > choose the correct card from the list the problems should go away. > > I have found that XF86Setup and xf86config write to different files. > The GUI version writes into the /usr/x11r6/lib/x11 dir, where it moves > the existing config gile to .old . The only problem with this is that > the old 'file' is the other end of the symlink from /etc/x11, which is > where xf86config writes. > > Tim -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: XF86 3.3-3
Christopher Jason Morrone wrote: > > I've seen other messages about XF86 3.3 not working. I am also > experiencing problems. I upgraded from 3.2 using the 3.3-3 packages, and > now when I try to startx, the screen flickers and goes black, and the > keyboard locks up. Nothing else. > > Unfortunately, because of the screen blanking, I really have no idea whats > going wrong. Someone else I know is having the exact same problem, I'm > using the S3 server(#9 motion 771 card), and he's using standard SVGA for > his Trident I believe. This also reflects my experience exactly. HELP!! > > In any case, the XF86 3.3 packages are definitely broken. I'd fill out a > bug report, but unfortunately, I can't be any more specific than that > right now. > > Do the package maintainers know that something is wrong? I'd be happy to > supply any info that I can. > > -- > TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to > [EMAIL PROTECTED] . > Trouble? e-mail to [EMAIL PROTECTED] . -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: XF86 3.3-3
> My flicker > (or more nearly pulsing (of xdm repeatedly trying to start?)) was quite > nasty, so I quickly rebooted with the rescue disk, deleted > /usr/X11R6/bin/xdm, rebooted from the harddisk, and downgraded. Is 3.3 > choking on my old configs? Or could it have been the S3 server? I had a similar problem on a new install. Running /etc/init.d/xdm start just caused the current console screen to start blinking continuously. Keyboard would lock up. The only way I managed to get in was via telnet. Killing xdm solved the problem. This was almost new install - I was actually upgrading from 3.2 to 3.3 at the time. After poking around for a bit and not finding anything obviously wrong, I decided to restart the install using the newly available Debian 1.3.1. I've got things working now... sort of. Now, /etc/init.d/xdm start seems to just hang without adversly affecting the system. No log messages, no X startup, nothing However, I can startx from the prompt and everything works fine Go figure. If anyone has any ideas, I'd be glad to hear them. TIA. Video - S3 Trio64 Debian - 1.3.1 Later, Kevin Traas Systems Analyst Baan Business Systems -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: XF86 3.3-3
On Tue, 8 Jul 1997, H Huang wrote: [cut] > I think the problem has something to do with certain newly added features of > XFree86-3.3, some of which actually are still in beta test stage. Possible, but should beta options be enabled in a stable package by default? > > I've got a clgd 5428 card. Although X still works after the upgrade, the > showdow portions of some buttons, scrollbars and arrows are not drawing well. > The cause is that 3.3 adds some beta acceleration features in the Cirrus > driver, which does not work well with the 5428 card. I have to disable the > acceleration to make it work like it did before. > > Therefore, the correct procedure to upgrade X (any version) is: > > 1) stop X (xdm,startx) > 2) upgrade the package > 3) read docs > 4) configure X. Pretty much how I did it. I'm still searching the configs to try to find bad lines... Another bit of new info. I've found (by logging in from a remote terminal) that after the screen blanks and the keyboard locks up, the X processes appear to die off, because there aren't any running when I log in remotely... -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: XF86 3.3-3
Hi! On 9-Jul-97, H Huang wrote: > Are you asking the debian maintainer to provide a *stable* XF86Config > setup file for *every* X server? There's no way he/she could do that. It's clear that this is impossible. But if this acceleration code is really beta, there should be at least a warning, as You stated. Christian -- Christian Kauhaus University of Rostock, Dept of CS ---+- Linux-Sysadmin on |WWW-Homepage catalina patmos paxi | http://www.informatik.uni-rostock.de/~ckauhaus ---+- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: XF86 3.3-3
On Wed, 9 Jul 1997, Christian Kauhaus wrote: > Hi! > > On 8-Jul-97, H Huang wrote: > > I've got a clgd 5428 card. Although X still works after the upgrade, the > > showdow portions of some buttons, scrollbars and arrows are not drawing > > well. > > I've experienced the same effects as well with a 5426 card. Maybe turning > acceleration off will solve the problem, I'll try it out. But in my opinion > the package's stadard configuration should provide a *stable* setup that > works in most cases. The rest can go into debian/unstable. So there is a > need to fix the package. (Has someone already filled out a bug report?) > > Greetings > Christian > Are you asking the debian maintainer to provide a *stable* XF86Config setup file for *every* X server? There's no way he/she could do that. However, there's one area the debian package can improve. The current preinst and postinst scripts appear to be doing the following things: 1) stop xdm 2) unpack and setup the packages 3) restart xdm Step 3) obviously assumes the old XF86Config works for the new X version, which is not always the case. Therefore, instead of restarting xdm, the postinst should echo a message that warns the user the old configuration may not work and ask them to read the docs and reconfigure X. BTW, I've filed a bug report to www.xfree86.org against the Cirrus driver. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: XF86 3.3-3
Hi! On 8-Jul-97, H Huang wrote: > I've got a clgd 5428 card. Although X still works after the upgrade, the > showdow portions of some buttons, scrollbars and arrows are not drawing well. I've experienced the same effects as well with a 5426 card. Maybe turning acceleration off will solve the problem, I'll try it out. But in my opinion the package's stadard configuration should provide a *stable* setup that works in most cases. The rest can go into debian/unstable. So there is a need to fix the package. (Has someone already filled out a bug report?) Greetings Christian -- Christian Kauhaus University of Rostock, Dept of CS ---+- Linux-Sysadmin on |WWW-Homepage catalina patmos paxi | http://www.informatik.uni-rostock.de/~ckauhaus ---+- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: XF86 3.3-3
On Tue, 8 Jul 1997, Christopher Jason Morrone wrote: > > I've seen other messages about XF86 3.3 not working. I am also > experiencing problems. I upgraded from 3.2 using the 3.3-3 packages, and > now when I try to startx, the screen flickers and goes black, and the > keyboard locks up. Nothing else. > > Unfortunately, because of the screen blanking, I really have no idea whats > going wrong. Someone else I know is having the exact same problem, I'm > using the S3 server(#9 motion 771 card), and he's using standard SVGA for > his Trident I believe. > > In any case, the XF86 3.3 packages are definitely broken. I'd fill out a > bug report, but unfortunately, I can't be any more specific than that > right now. > > Do the package maintainers know that something is wrong? I'd be happy to > supply any info that I can. > I think the problem has something to do with certain newly added features of XFree86-3.3, some of which actually are still in beta test stage. I've got a clgd 5428 card. Although X still works after the upgrade, the showdow portions of some buttons, scrollbars and arrows are not drawing well. The cause is that 3.3 adds some beta acceleration features in the Cirrus driver, which does not work well with the 5428 card. I have to disable the acceleration to make it work like it did before. Therefore, the correct procedure to upgrade X (any version) is: 1) stop X (xdm,startx) 2) upgrade the package 3) read docs 4) configure X. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: XF86 3.3-3
Thanks for the suggestion, but thats not the problem. I should make it clear that X worked perfectly fine before the upgrade. I have a pretty much stock Debian system also. Someone also suggested that I do a: X -probeonly >out 2>&1 Its a good idea, but it doesn't show any errors that I can see. I've appended the output to the end of this message if anyone would like to take a look. I do notice that it says "Operating System: Linux 2.0.21 i486 [ELF]", but I'm using 2.0.27...maybe thats the system it was compiled on? On Tue, 8 Jul 1997, Igor Grobman wrote: > I had a similar problem. The reason was a corrupted ~/.Xauthority file. Try > deleting it, and relogging on. That fixed it for me. > > HTH [cut] XFree86 Version 3.3 / X Window System (protocol Version 11, revision 0, vendor release 6300) Release Date: Jun 2 1997 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (see http://www.XFree86.Org/FAQ) Operating System: Linux 2.0.21 i486 [ELF] Configured drivers: S3: accelerated server for S3 graphics adaptors (Patchlevel 0) newmmio, mmio_928, s3_generic (using VT number 7) XF86Config: /etc/X11/XF86Config (**) stands for supplied, (--) stands for probed/default values (**) XKB: rules: "xfree86" (**) XKB: model: "pc102" (**) XKB: layout: "us" (**) Mouse: type: MouseSystems, device: /dev/mouse, baudrate: 1200 (**) S3: Graphics device ID: "Primary Card" (**) S3: Monitor ID: "Primary Monitor" (**) FontPath set to "/usr/X11R6/lib/X11/fonts/misc:unscaled,/usr/X11R6/lib/X11/fonts/75dpi:unscaled,/usr/X11R6/lib/X11/fonts/100dpi:unscaled,/usr/X11R6/lib/X11/fonts/Type1,/usr/X11R6/lib/X11/fonts/Speedo,/usr/X11R6/lib/X11/fonts/misc,/usr/X11R6/lib/X11/f onts/75dpi,/usr/X11R6/lib/X11/fonts/100dpi" (--) S3: chipset: 968 rev. 3 (--) S3: chipset driver: newmmio (--) S3: card type: 386/486 localbus (--) S3: videoram: 4096k (--) S3: Detected an IBM RGB524 ramdac rev. e0 (--) S3: Ramdac type: ibm_rgb524 (**) S3: Ramdac speed: 220 MHz (--) S3: Using hardware cursor from IBM RGB52x RAMDAC (--) S3: #9 Motion 771 BIOS found (--) S3: Using IBM RGB52x programmable clock (MCLK 60.000 MHz) (**) S3: with refclock 16.000 MHz (probed 16.112 & 15.956) (--) S3: Maximum allowed dot-clock: 220.000 MHz (**) S3: Mode "1024x768": mode clock = 65.000 (**) S3: Mode "800x600": mode clock = 50.000 (**) S3: Mode "640x480": mode clock = 31.500 (--) S3: Operating RAMDAC in pixel multiplex mode (--) S3: Using 8 bits per RGB value (--) S3: Virtual resolution set to 1024x768 -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: XF86 3.3-3
I had a similar problem. The reason was a corrupted ~/.Xauthority file. Try deleting it, and relogging on. That fixed it for me. HTH > > I've seen other messages about XF86 3.3 not working. I am also > experiencing problems. I upgraded from 3.2 using the 3.3-3 packages, and > now when I try to startx, the screen flickers and goes black, and the > keyboard locks up. Nothing else. > > Unfortunately, because of the screen blanking, I really have no idea whats > going wrong. Someone else I know is having the exact same problem, I'm > using the S3 server(#9 motion 771 card), and he's using standard SVGA for > his Trident I believe. > > In any case, the XF86 3.3 packages are definitely broken. I'd fill out a > bug report, but unfortunately, I can't be any more specific than that > right now. > > Do the package maintainers know that something is wrong? I'd be happy to > supply any info that I can. > > > -- > TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to > [EMAIL PROTECTED] . > Trouble? e-mail to [EMAIL PROTECTED] . > -- Proudly running Debian Linux! Linux vs. Windows is a no-Win situation Igor Grobman [EMAIL PROTECTED] [EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: XF86 3.3-3
Christopher Jason Morrone wrote: > I upgraded from 3.2 using the 3.3-3 packages, and now when I try to startx, > the screen flickers and goes black, and the keyboard locks up. > > I'm using the S3 server(#9 motion 771 card), and he's using standard SVGA for > his Trident I believe. > > In any case, the XF86 3.3 packages are definitely broken. I'd fill out a > bug report, but unfortunately, I can't be any more specific than that > right now. I had the same problem with an S3 Trio 64 V+ graphics card. My flicker (or more nearly pulsing (of xdm repeatedly trying to start?)) was quite nasty, so I quickly rebooted with the rescue disk, deleted /usr/X11R6/bin/xdm, rebooted from the harddisk, and downgraded. Is 3.3 choking on my old configs? Or could it have been the S3 server? Greetings, Stefan -- Stefan Baums Universitaet Goettingen mailto:[EMAIL PROTECTED] -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: XF86 3.3-3
Christopher Jason Morrone <[EMAIL PROTECTED]> writes: > I've seen other messages about XF86 3.3 not working. I am also > experiencing problems. I upgraded from 3.2 using the 3.3-3 packages, and > now when I try to startx, the screen flickers and goes black, and the > keyboard locks up. Nothing else. Similar problem here, except that the keyboard doesn't lock up. The problem occurs when either the VGA16 or S3 server is launched -- the screen immediately goes into power saving mode. I can kill it with Ctrl-Alt-Backspace, but there's nothing in the log that looks suspicious. If anyone has any suggestions, I'd love to hear them. The relevant card in this case is a Powergraph 64 (i.e. Trio64+). [Mark: I'm cc-ing this to Mark in case you don't get the time to wade through debian-user] Thanks -- Rob -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
XF86 3.3-3
I've seen other messages about XF86 3.3 not working. I am also experiencing problems. I upgraded from 3.2 using the 3.3-3 packages, and now when I try to startx, the screen flickers and goes black, and the keyboard locks up. Nothing else. Unfortunately, because of the screen blanking, I really have no idea whats going wrong. Someone else I know is having the exact same problem, I'm using the S3 server(#9 motion 771 card), and he's using standard SVGA for his Trident I believe. In any case, the XF86 3.3 packages are definitely broken. I'd fill out a bug report, but unfortunately, I can't be any more specific than that right now. Do the package maintainers know that something is wrong? I'd be happy to supply any info that I can. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
