Hi, On Sat, 25 Feb 2006, houghi wrote:

On Fri, Feb 24, 2006 at 10:47:19PM +0100, Stefan Dirsch wrote:

...

* X11 configuration during installation is totally broken in Beta5 due to a bug in package manager. Instead of the native X11 driver fbdev or even vesa driver will be configured. In order to create a valid X11 configuration stop xdm ("rcxdm stop") and use SaX2 for configuration ("sax2 -r"). ATI users should update the radeon driver first before executing SaX2. Otherwise the result will likely be a blank screen. Driver RPMs for i386/x86_64 are attached to Bug 153367.

Meanwhile I've added this information to http://en.opensuse.org/Bugs:Most_Annoying_Bugs

In Parallels (VM manager) I get after sax2 -r: Died at /usr/share/sax/init.pl line 630

Similar here (ATI Radeon Mobility X700, x86_64): Died at /usr/share/sax/init.pl line 620. /var/log/SaX.log says: /************* SaX2 log : SaX2 version 7.1 - SVN Release: 1.49 2003/03/17 ************** SVN RELEASE : 1019 : DESCRIPTION : X11 configuration log file to collect information : about detection, startup and configuration. : There are three parts of logging: : --- : 1) INIT ( detection, 3D ) : 2) STARTUP ( xorg.conf, X11 log, glxinfo ) : 3) CONFIG ( config actions ) : --- : VERSION : SaX2 compiled for: [SUSE LINUX 10.0.42 (X86-64)] PARAMETER : -r -r : LOG DATE : Sat Feb 25 02:12:19 CET 2006 *************/ ============================ Framebuffer Info: ---------------------------- Framebuffer not active 25-Feb 02:12:20 <I> Initializing... 25-Feb 02:12:21 <I> [ Sysp: Mouse detection data Mouse0 => Protocol : explorerps/2 Mouse0 => Device : /dev/input/mice Mouse0 => Buttons : 5 Mouse0 => Wheel : 1 Mouse0 => Emulate : 0 Mouse0 => Name : USB Mouse Mouse0 => VendorID : 0x062a Mouse0 => DeviceID : 0x0000 Mouse0 => Profile : <undefined> Mouse0 => RealDevice : /dev/input/event3 Mouse0 => NutShell : 0 Mouse1 => Protocol : explorerps/2 Mouse1 => Device : /dev/input/mice Mouse1 => Buttons : 5 Mouse1 => Wheel : 1 Mouse1 => Emulate : 0 Mouse1 => Name : ImPS/2 Logitech Wheel Mouse Mouse1 => VendorID : 0x0210 Mouse1 => DeviceID : 0x0013 Mouse1 => Profile : <undefined> Mouse1 => RealDevice : /dev/input/event2 Mouse1 => NutShell : 1 ] 25-Feb 02:12:21 <I> [ Sysp: Keyboard detection data Keyboard0 => XkbModel : pc105 Keyboard0 => XkbLayout : de Keyboard0 => XkbVariant : nodeadkeys Keyboard0 => Name : AT Translated Set 2 keyboard Keyboard0 => RealDevice : /dev/input/event0 ] 25-Feb 02:12:21 <I> [ Sysp: Server detection data Card0 => DomainId : 0x0 Card0 => BusId : 0x1 Card0 => SlotId : 0x00 Card0 => FuncId : 0x0 Card0 => Vendor : ATI Card0 => Device : Mobility Radeon X700 5653 (M26) (PCIE) Card0 => VID : 0x1002 Card0 => DID : 0x5653 Card0 => Module : radeon Card0 => BusType : AGP Card0 => Detected : 1 Card0 => Flag : DEFAULT Card0 => SUB-VID : 0x1462 Card0 => SUB-DID : 0x0291 Card0 => DrvProfile : Depth24,Radeon ] 25-Feb 02:12:22 <I> Sysp: XStuff detection data ... and nuts. Cheers -e -- Eberhard Moenkeberg (emoenke@gwdg.de, em@kki.org)

David Bolt writes:

On Fri, 24 Feb 2006, Stefan Dirsch wrote:-

...

* X11 configuration during installation is totally broken in Beta5 due to a bug in package manager. Instead of the native X11 driver fbdev or even vesa driver will be configured. In order to create a valid X11 configuration stop xdm ("rcxdm stop") and use SaX2 for configuration ("sax2 -r"). ATI users should update the radeon driver first before executing SaX2. Otherwise the result will likely be a blank screen. Driver RPMs for i386/x86_64 are attached to Bug 153367.

Meanwhile I've added this information to http://en.opensuse.org/Bugs:Most_Annoying_Bugs

Apparently, I managed to miss that bug due to performing an update from beta 3, rather than doing a fresh install. Running "sax2 -r" under runlevel 3 also worked. This was on an Acer Aspire 3002 notebook using an SiS 660 chip-set.

However, I did fall foul of another when the package manager decided it was going to install packages from the default selection even I told it not to bother adding them. Deselecting the games that would normally be installed during the update didn't appear to stop the package manager from installing them.

Please create a bugreport with complete log files! Thanks, Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj/ SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126