Re: NV r128 problems with 4.0.1-8
On Tuesday 28 November 2000 17:43, Seth Arnold wrote: Jelmer, I too have noticed this. I normally run mozilla instead of netscsape navigator 4.x, but it most definately corresponds to the browser -- click *poof*, drag *poof*, etc. I too am running a 2.4.0 kernel, 2.4.0-test10. I am running these on an SMP machine; I wonder if that has anything to do with it? I don't have SMP. So it must be going wrong somewhere else I guess. Let's hope someone on this list knows what we're talking about. Thanks for your reply though, makes my problem a little bit less frustrating now I know I'm not the only one :) Jelmer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
NV r128 problems with 4.0.1-8
Hi, This has been happening for quite some time now. X flies back into textmode every once in a while with a signal 11 caught. I really don't have a clue which could be causing this behaviour. The last 3 (or so) crashes were while I was using netscape. I'm running Linux kernel version 2.4.0-test8. I already posted something similar on this list and got a reply I had a Voodoo 3/4/5 which I obviously don't :) I checked the mailinglist archives but couldn't find what could be causing the signal 11's, I did find another problem I used to have, the X freezing because of having a fontserver entry in FontPath. Any ideas how to get rid of the random crashes ? Thanks in advance, Jelmer Feenstra
Re: NV r128 problems with 4.0.1-8
On Tuesday 28 November 2000 17:43, Seth Arnold wrote: Jelmer, I too have noticed this. I normally run mozilla instead of netscsape navigator 4.x, but it most definately corresponds to the browser -- click *poof*, drag *poof*, etc. I too am running a 2.4.0 kernel, 2.4.0-test10. I am running these on an SMP machine; I wonder if that has anything to do with it? I don't have SMP. So it must be going wrong somewhere else I guess. Let's hope someone on this list knows what we're talking about. Thanks for your reply though, makes my problem a little bit less frustrating now I know I'm not the only one :) Jelmer
Re: lockup when starting X
On Tuesday 07 November 2000 02:05, Danny Barron wrote: I also had the same problem (with xfs not being installed...I had it installed in the 3.x X windows) which resulted in X freezing on startup...I've been GUIless since the woody 4.x rollout. I'm now installing the font server. Just wanted to acclaim that Jelmer is NOT the only one. Btw, there are packaging problems, I had to go back and install utils as well (at least) to get things going minimally. I'm so glad to be in X again. Danny Barron Well actually my problems were even worse. I had X constantly crashing every once in a while, it would just fly back into textmode. I solved this by downgrading the packages, perhaps updated woody packages fix this as well. Jelmer Feenstra (I'm not on the list so please CC me if you reply to this) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: lockup when starting X
On Tuesday 07 November 2000 19:59, Zephaniah E. Hull wrote: On Tue, Nov 07, 2000 at 11:01:24AM +0100, Jelmer Feenstra wrote: snip Well actually my problems were even worse. I had X constantly crashing every once in a while, it would just fly back into textmode. I solved this by downgrading the packages, perhaps updated woody packages fix this as well. This is becoming a FAQ, you have a Voodoo 3 Voodoo4 or a Voodoo 5, and you have a line like 'Load "dri"' in your /etc/X11/XF86Config-4, I am currently working on fixing the drivers, but it takes time. Well actuall I have a RIVA128 card. So I hope this can still be fixed :) Jelmer Feenstra -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: lockup when starting X
On Tuesday 07 November 2000 02:05, Danny Barron wrote: I also had the same problem (with xfs not being installed...I had it installed in the 3.x X windows) which resulted in X freezing on startup...I've been GUIless since the woody 4.x rollout. I'm now installing the font server. Just wanted to acclaim that Jelmer is NOT the only one. Btw, there are packaging problems, I had to go back and install utils as well (at least) to get things going minimally. I'm so glad to be in X again. Danny Barron Well actually my problems were even worse. I had X constantly crashing every once in a while, it would just fly back into textmode. I solved this by downgrading the packages, perhaps updated woody packages fix this as well. Jelmer Feenstra (I'm not on the list so please CC me if you reply to this)
Re: lockup when starting X
On Tuesday 07 November 2000 19:59, Zephaniah E. Hull wrote: On Tue, Nov 07, 2000 at 11:01:24AM +0100, Jelmer Feenstra wrote: snip Well actually my problems were even worse. I had X constantly crashing every once in a while, it would just fly back into textmode. I solved this by downgrading the packages, perhaps updated woody packages fix this as well. This is becoming a FAQ, you have a Voodoo 3 Voodoo4 or a Voodoo 5, and you have a line like 'Load dri' in your /etc/X11/XF86Config-4, I am currently working on fixing the drivers, but it takes time. Well actuall I have a RIVA128 card. So I hope this can still be fixed :) Jelmer Feenstra
lockup when starting X
I'm sorry if I broke the thread, I'm not on the mailinglist. Having said that I noticed the following on the list : emails Branden Robinson [EMAIL PROTECTED] [001101 21:16] wrote: On Wed, Nov 01, 2000 at 08:56:59AM +0100, Torbjörn Andersson wrote: (By the way, my recent problems with X hanging at startup unless I either install xfs or remove "unix/:7100" from the font path seem to have gone away now. I don't know how or why. The CHANGELOG mentions a recent "infinite loop problem that can show up on server resets" but I don't know if that's even remotely related.) Hrm, as I understand it, if the X server doesn't find a font server there, it should drop that FPE (font path element) from the list and move on. Which, anecdotally, is what it seems to do for me. Can anyone else repro this problem? Does the X server get hung up if it's looking for a font server that isn't there? /emails Something like that. Well, I noticed the problem here too. Actually, I got my X working because I read the mail mentioned above, which suggested it could have to do with unix/:7100 being a fontpath element in my XF86Config-4. So I removed the line and X worked ! :) I'm running kernel 2.4.0-test8 and the first X4 packages that got into woody. Besided that being fixed now, I experienced random crashes of my X with my old configfile (that's why I wanted to try a new one). However, that configfile was rather dirty, so I hope the problem is fixed now with this fresh one :) Greetz, Jelmer Feenstra -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
lockup when starting X
I'm sorry if I broke the thread, I'm not on the mailinglist. Having said that I noticed the following on the list : emails Branden Robinson [EMAIL PROTECTED] [001101 21:16] wrote: On Wed, Nov 01, 2000 at 08:56:59AM +0100, Torbjörn Andersson wrote: (By the way, my recent problems with X hanging at startup unless I either install xfs or remove unix/:7100 from the font path seem to have gone away now. I don't know how or why. The CHANGELOG mentions a recent infinite loop problem that can show up on server resets but I don't know if that's even remotely related.) Hrm, as I understand it, if the X server doesn't find a font server there, it should drop that FPE (font path element) from the list and move on. Which, anecdotally, is what it seems to do for me. Can anyone else repro this problem? Does the X server get hung up if it's looking for a font server that isn't there? /emails Something like that. Well, I noticed the problem here too. Actually, I got my X working because I read the mail mentioned above, which suggested it could have to do with unix/:7100 being a fontpath element in my XF86Config-4. So I removed the line and X worked ! :) I'm running kernel 2.4.0-test8 and the first X4 packages that got into woody. Besided that being fixed now, I experienced random crashes of my X with my old configfile (that's why I wanted to try a new one). However, that configfile was rather dirty, so I hope the problem is fixed now with this fresh one :) Greetz, Jelmer Feenstra
