I had a different problem from many of the people posting last week:
XFree 4.0.2 worked for me, but my virtual consoles were unusable after
X had run, even if X were killed. Well I just made a new kernel with
fb support and stuck a vga=791 into my lilo.conf. Now all is well,
even glxinfo says so
I had a different problem from many of the people posting last week:
XFree 4.0.2 worked for me, but my virtual consoles were unusable after
X had run, even if X were killed. Well I just made a new kernel with
fb support and stuck a vga=791 into my lilo.conf. Now all is well,
even glxinfo says s
On Wed, Feb 14, 2001 at 03:06:52PM +0300, Edouard GUIRCH wrote:
> > > > And -- oops -- today my X got the same deadly signal.
> > > > (although it took *much* longer than 30 seconds for X to die;
> > > > I guess, it was working for about 5 hours).
> > > > Recently (yesterday?), I upgraded libc from
On Wed, Feb 14, 2001 at 03:06:52PM +0300, Edouard GUIRCH wrote:
> > > > And -- oops -- today my X got the same deadly signal.
> > > > (although it took *much* longer than 30 seconds for X to die;
> > > > I guess, it was working for about 5 hours).
> > > > Recently (yesterday?), I upgraded libc fro
> > > And -- oops -- today my X got the same deadly signal.
> > > (although it took *much* longer than 30 seconds for X to die;
> > > I guess, it was working for about 5 hours).
> > > Recently (yesterday?), I upgraded libc from 2.2 to 2.2.1 (both from
> > > woody).
>
> no problems with X here. Are
> > > And -- oops -- today my X got the same deadly signal.
> > > (although it took *much* longer than 30 seconds for X to die;
> > > I guess, it was working for about 5 hours).
> > > Recently (yesterday?), I upgraded libc from 2.2 to 2.2.1 (both from woody).
>
> no problems with X here. Are you g
6 matches
Mail list logo
