On Sun, Jun 08, 2003 at 10:20:36PM +0200, Julien wrote:
> On Sun, Jun 08, 2003 at 07:31:25PM +0200, Julien wrote:
> > Same issue here, before I restart the server to try getting rid of this
> > matter. Unfortunately, X did not came up at all... I tried to fallback by
> > downgrading xserver-common/xfree86, xfree86-common and all xlibs packages,
> > without any result.
>
> Correct version hereafter. Upgraded again all packages to 4.2.1-7, then
> downgraded xlibs and xserver-xfree86 to 4.2.1-6 -> X starting again. I
> tested with two drivers (two cards): nv and r128 (not using the generic one
> 'ati', since not 4.2.1-7), both are working after the fallback.
When I experienced this problem during while preparing 4.2.1-7[1], I was
able to use xdm 4.2.1-7 and xlibs 4.2.1-7 with xserver-xfree86 4.2.1-6.
Please try that scenario.
[1] People who read my changelogs might have noticed the following:
+ GCC 3.3 appears to produce bad code for PowerPC at the optimization
level required by Debian Policy (the X server cannot validate
XDM-AUTHORIZATION-1 keys); when building on PowerPC, set
DefaultGcc2OptimizeOpt to -O instead of -O2
I don't own an i386 machine, so I did not know that this bug affected
that architecture as well. GCC 3.3 has many regressions, though --
XFree86 4.2.1-7 will not even build with that compiler on arm, mips,
mipsel, and possibly m68k (reason for the latter's build failure is not
nailed down yet, it could be lack of disk space masquerading as
something more subtle).
--
G. Branden Robinson | The errors of great men are
Debian GNU/Linux | venerable because they are more
branden@debian.org | fruitful than the truths of little
http://people.debian.org/~branden/ | men. -- Friedrich Nietzsche
Attachment:
pgpTafA2cIkGT.pgp
Description: PGP signature