XServer fails after Yast Online Update
Dear list, I've upgraded my SuSE 8.0 through the Yast2 YOU tool. Source was ftp.leo.org. Apart from nicely insatlling all the new safety patches, it also messed with my XFree86 System and I'm back to 80s style text mode. Checking the package versions (which contain xfree86 in their description) reveals: Package Version isax 1.3-343 (XFree 3.X stuff) mesa 4.0.1-74 sax 2.9-450 (XFree 3.X stuff) sax2 4.3-408 xdevel 4.2.0-64 xf86 4.2.0.64 xf86_3x 3.3.6-375 (XFree 3.X stuff) xf86tools 0.1-221 xfntscl 4.2.0-64 xloader 4.2.0-64 xman 4.2.0-64 xmods_3x 3.3.6-375 (XFree 3.X stuff) xmodules 4.2.0-64 (Weird enough, Index of ftp://ftp.leo.org/pub/suse/i386/8.0/suse/x1 shows xf86 version numbers 4.2.0-107) My XF86Config and the log file from the attempted server startup is found at http://www-zeuthen.desy.de/~niessen/XFree86.0.log http://www-zeuthen.desy.de/~niessen/XF86Config I'm running this on an ACER (TM) Travelmate 260 with an Intel (TM) i830M chipset. In Yast2 itself, the system detects Current Settings: 1024x768, 16 bit / 65536 colo(u)rs Refresh rate: 60 Hz 3D acceleration disabled Monitor: LCD XGA 1024X768@60HZ: ,,Probe Hardware'' actually switches into graphics mode, and I see some remains of past sessions, but the it comes back and says it could not write the configuration. Grateful for any clues what's going on. Cheers, Peter. Peter Nießen (Peter Niessen for special character challenged displays) Bartol Research Institute University of Delaware Newark, DE 19716-4793 U.S. of America Tel (+1)302/831-8700 Fax (+1)302/831-1843 e-mail niessen@ifh.de www http://www.ifh.de/~niessen /"\ ASCII ribbon campaign \ / --------------------- X against HTML mail / \ and postings pgp public key at http://www.ifh.de/www_users/amanda/niessen/www/pgp_pubkey.asc
On Sun, 7 Dec 2003, Peter Niessen wrote:
Dear list,
I've upgraded my SuSE 8.0 through the Yast2 YOU tool. Source was ftp.leo.org. Apart from nicely insatlling all the new safety patches, [complete desaster nothing works anymore...]
The problem has been solved by re-installing all packages from the x-series. Nice side effect: cleaned up some trash. Cheers, Peter.
participants (1)
-
Peter Niessen