Strange issue, but I've been running into problems with 10.3 since updating to beta 1 from 10.2. The kernel included on the install disc will not boot, it locks up at a random point but within 10-15 seconds after selecting install, although the safe kernel works and I managed to install. The system would not boot with the 10.3 B1 kernel unless I used kernel parameters (noapic etc.) which leads to a host of stability problems with my laptop. However, I was previously using 2.6.22 under 10.2 with no problems. Booted fine without requiring kernel parameters. I tried booting 10.3 B1 with that same kernel from 10.2 (since it still existed from my upgrade), and it would freeze 15-20s in, unless I used noapic. I even recompiled that same kernel using the same config file under 10.3, and the same problem exists. Downloaded and compiled 2.6.22.2 and ran into the same problem. Freezes during boot, works with noapic. I'm befuddled as to why this is an issue in 10.3 and not in 10.2. I suspect, but am not sure, that my issues are somehow related to the new modular mkinit process, it's more or less the only difference I can find in my boot logs as compared to 10.2. The lockups occur almost immediately after all the various xxx.sh scripts start running, but not always at the same point (which makes it harder to figure out where the problem is). It could be there's a fault with my hardware and kernel incompatibility that simply never came to light with 10.2 and only with whatever 10.3 does differently, but I want to track it down. I had similar issues in 10.2 initially that were related to 2.6.18.2 not supporting my hardware properly, but the issues more or less disappared with >2.6.20 and I was kernel-parameter free. Now I'm back to square one. Is there any source for docs on the specific changes made to mkinitrd for 10.3, as in, how to configure with various features and scripts are activated for boot? I went through the man docs, and there is info on how to enable additional settings (modules, features) but nothing on how to prevent things from being enabled, or whether there is a config file somewhere to control it all? Are there any other things that changed with the boot process I may have overlooked that could cause a previously hidden kernel problem to appear, when it remained dormant in 10.2? I'd like to roll up my sleeves (within reason ;) )and figure out what's going on, maybe by process of trial-and-error with poking and peeking various things, but am not sure where to start in this case. Sorry if this is a convoluted message, I'm not comfortable opening a bug report because I'm not sure I can reliably articulate where the actual problem is, so I'm looking for some diagnostic help before I do that. For reference's sake, the system is an HP dv9000 laptop with an AMD x2 1.8G and nvidia MCP51 chipset. Cheers, Kevin --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org