any hints?
i tried to make yast2 repair the already installed system (bootloader, and so forth) and after it did the automatic checks and repairs, the 9.0->9.1 upgraded system now boots all right. it seems that the bootlogo has also reappeared and been installed correctly. during the first bootup some cpufreqd or some similar service failed, and after login to kde some little window also complained about that. after a second bootup of that box, this error doesnt show up any more but there is a different error now: ----- <notice>startproc: execve (/usr/sbin/cpufreqd) [ /usr/sbin/cpufreqd -d ], [ CONSOLE=/dev/console TERM=linux SHELL=/bin/sh progress=35 INIT_VERSION=sysvinit-2.85 RED IRECT=/dev/tty1 COLUMNS=92 PATH=/usr/local/sbin:/sbin:/bin:/usr/sbin:/usr/bin vga=0x314 RUNLEVEL=5 PWD=/ PREVLEVEL=N LINES=32 SHLVL=2 splash=silent sscripts=46 _=/s bin/startproc DAEMON=/usr/sbin/cpufreqd ] Starting cpufreqd done Error: Could not open file for writing: /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor Error: No such file or directory ---- i have to admit, that i am somewhat frustrated with suse lately, i very rarely had unproblematic installations, not even clean ones for testing very basic standard/older stuff that actually shouldnt do any harm. most of the times its installation woes and yast crashes and/or problems. how should a basic clueless user (maybe i also belong amongst these :) handle suse/linux when facing such problems. maybe new releases of suse would need to get better/more/public testing before releasing stuff to the mass market. thanks, andy