Can you change to a console and check the messages? Start a rescue system and look what the run of `hwinfo' produces and at which point it hangs. Try salvaging the yast logfiles of the installation. Did this machine work fine with older releases? Be more verbosive about the used hardware, specially the loaded kernel modules in the installation system, `lspci'. Change to tty2 and execute these commands - you can surely do that before the actual hang.

I forgot: try booting with ACPI=off, pci=routeirq, pci=noacpi and/or the `Safe setting' and see if it still results in a hang.

OK, the system is actually able to boot and complete runlevel 5, so collecting the data isn't too difficult :-)
running "hwinfo" works fine - see output attached.  However, once I've got KDE running, I log in, then start YaST2 and select "Keyboard Layout" - after this, the machine enters the same state as described earlier (single solid cursor in upper left corner), but it responds to keyboard input and a Ctrl-Alt-Delete does a normal shutdown (although I can't see it) and reboot. 
This is the first try with SUSE 10.x - this system previously ran 9.3 with no problems.
 

Created attachment 74263 [details]
Output of "hwinfo"

Created attachment 74264 [details]
List of loaded modules

Created attachment 74265 [details]
lspci output

Created attachment 74266 [details]
Output of "lspci -vv"

Created attachment 74270 [details]
/var/log/YaST2 - tarred and gzipped

This sounds like a hardware problem. Unfortunately you didn't answear to comment #2. Is this triggered only the the yast kbd-module? It's not likely because at the screen you mentioned, no kbd settings are applied. Does the system run stable that way? What gfx-card are you using?

1) Graphicscard - see the lspci listing.  It's an onboard ATI 3D Rage IIC.
2) I can't say if it's only triggered by the kbd module - which other modules do you suspect? 
3) Booting with ACPI=off, pci=routeirq, pci=noacpi - I'll get back to you.

Booting with acpi=off,pci=routeirq,pci=noacpi makes the system freeze up after a little while and it does complete the startup. 
Booting with the Failsafe option completes, but it cannot start kdm - on tty10 I see:  "kdm :0 IO error in XOpenDisplay" followed by 2-3 other messages saying kdm couldn't be started.

First sentence  should of course have read: "... a little while and it does NOT complete the startup." 

Is this a shared-memory card you are using? If so, apply the `mem=<...>M' append line to your kernel, whereas <...> is the amount of memory minus the amount of memory used by the gfxcard.

It's an onboard/builtin graphics chip - I don't know if it uses shared memory - I doubt it.  The box has 4Gb memory - I'll try booting with mem=3072M and see what happens.

OK, tried booting with mem=3072M - then Yast2->Hardware->Keyboard Layout - still ended up with a blank screen with a solid cursor in the upper left hand corner. 

Maby this is a SMP problem. Try booting with `numcpus=1' and check whether the system runs stable afterwards. Furthermore, if you encounter a crash, fetch the syslog messages before the hang. You can also check the syslog for oopses manually.

I tried booting with numcpus=1 - didn't seem to make any difference; in fact, the system still seems to run on four CPUs.  top shows 4, /proc/cpuinfo shows 4. 
The system overall appears to run fine - I ran a 24+ hour stress-test/burn-in of a disk-array with no problems.  
Only when I start YaST->Hardware->Keyboard Layout do I see this problem - isn't that worth looking into?  

OK then, Jiri?

*** This bug has been marked as a duplicate of 155018 ***

Reopening - bug 155018 has been closed, but it is not at all clear if and when a fix was created or applied.

You are probably right, this does not seem to be a duplicate - bug 155010 did not exhibit a solid cursor.

Marcus, the YaST log ends up in initializing X11 library.

This system contains an "ATI Rage IIC" card which is configured using
the ati driver. If this is a X11 problem you should be able to reproduce
it with the following workflow:

   - init 3
   - login as root
   - rm -f /var/log/X*   

   - start an X-Server with the fbdev based config from the installation system
  
     X -xf86config /etc/X11/xorg.conf.install &
     Ctrl-Alt-F1
     export DISPLAY=:0
     xterm
     Ctrl-Alt-F7

   - type the following command into the xterm

     sax2 -r

If the problem appears send the log files
  
   /var/log/Xorg*.log
   /var/log/SaX.log
  
if not it's not an X11 bug :-)

Thanks

After "sax2 -r", the screen blanks and I have a solid white cursor in the upper left hand corner.
Trying to leave with Ctrl-Alt-F1 doesn't work, killing the Xserver with Ctrl-Alt-Backspace does'nt work. However, Ctrl-Alt-Delete makes the system reboot.

Created attachment 79626 [details]
/var/log/X* /var/log/SaX.log tarred and gzipped

ok, so this seems to be an ati driver bug.
Stefan logs has been attached

  Model: "ATI 3D Rage IIC 215IIC [Mach64 GT IIC]"
  Vendor: pci 0x1002 "ATI Technologies Inc"
  Device: pci 0x4756 "3D Rage IIC 215IIC [Mach64 GT IIC]"

Looks like we need "fbdev" for this GPU. :-(

fixed for RC3.