Re: lockup when starting X
On Tue, Nov 07, 2000 at 11:01:24AM +0100, Jelmer Feenstra wrote: > 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. Zephaniah E. Hull. > > Jelmer Feenstra > > (I'm not on the list so please CC me if you reply to this) -- 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. Wow GL runs like flaming crap in a window <>
Re: lockup when starting X
On Tue, Nov 07, 2000 at 11:01:24AM +0100, Jelmer Feenstra wrote: > 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. Zephaniah E. Hull. > > Jelmer Feenstra > > (I'm not on the list so please CC me if you reply to this) -- 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. Wow GL runs like flaming crap in a window Navidad.exe
Re: lockup when starting X
On Tue, 7 Nov 2000, Jelmer Feenstra wrote: > > 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. ..and I have a Tseng ET6000. I had exactly same problems, but was able to log in via ssh, and reboot (killing X didn't help, because keyboard wasn't responding and I couldn't switch to console). I removed all references to GL and DRI, and things began looking nice again... Xf86cfg couldn't run either, even with these configs. "Illegal instruction" my arse =) > So I hope this can still be fixed :) Me too..
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: > > > > 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
Re: lockup when starting X
On Tue, Nov 07, 2000 at 11:01:24AM +0100, Jelmer Feenstra wrote: > 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. Zephaniah E. Hull. > > Jelmer Feenstra > > (I'm not on the list so please CC me if you reply to this) -- 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. Wow GL runs like flaming crap in a window pgpk2iq7VhP3z.pgp Description: PGP signature
Re: lockup when starting X
On Tue, 7 Nov 2000, Jelmer Feenstra wrote: > > 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. ..and I have a Tseng ET6000. I had exactly same problems, but was able to log in via ssh, and reboot (killing X didn't help, because keyboard wasn't responding and I couldn't switch to console). I removed all references to GL and DRI, and things began looking nice again... Xf86cfg couldn't run either, even with these configs. "Illegal instruction" my arse =) > So I hope this can still be fixed :) Me too.. -- 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: > > > > 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 Tue, Nov 07, 2000 at 11:01:24AM +0100, Jelmer Feenstra wrote: > 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. Zephaniah E. Hull. > > Jelmer Feenstra > > (I'm not on the list so please CC me if you reply to this) -- 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. Wow GL runs like flaming crap in a window PGP signature
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 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
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
Re: lockup when starting X
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 -- 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 : 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? 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
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 : 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? 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]