Donn Washburn wrote:
Group;
1. Over the past 15 years I have downloaded and compiled about every kernel basic and git from www.kernel.org and gotten them to work. I have changed the CPU to match this one and the default name using make menuconfig. I have tried over and over recently with no luck and openSuSE. Using oldconfig and /proc/config.gz as .config and make menuconfig. Both work just fine but mkinitrd fails - even though the modules are built and installed in /lib/modules/. Both openSuSE supplied kernel source and kernel.org kernels fail and have even cause this system to need reloading from scratch.
2. I have gone through all gyrations looking for why at a login I get no hostname but (none). And Apache2 complains about (none) at boot time. The happened before and was fixed in 11.4 one of alpha/beta versions but it is again broken
I had similar problems when I upgraded, I think it was to the 11 series (as I also build my own kernel from kernel.org configed for my hw)... It was when they switched to grub and putting everything on a RAMDISK to boot from and started thinking they could totally go with file-labels instead of /dev/sda3 -- including at boot.... I never was able to get it to work right with the suse framework, because, in order to give the illusion of booting by the 'name' of the partition, rather than using /dev/sda3, they basically have to boot a miniroot of sorts to read the labels, and that all has to be on the boot-ram disk. Once I switched back to lilo, (I use XFS BTW, for all my disks, including the boot disk -- have since maybe suse 7-8 timeframe). I did run into a problem in some of the recent kernels with the boot code not fitting in the boot area, but a new version of lilo has solved that now as well. I'm not saying it can't be done -- I needed my system working again ASAP, so I didn't have weeks to look at debugging the issue. It's frustrating too -- since if I don't use their grub setup, I can't get the suse kernels to load (suse hasn't kept up lilo and was actually claiming a bug in grub was the fault of xfs -- so they dropped support for xfs for a while...until some people vehemently pointed out the bug was in grub (modifying a live-mounted file system?! You've got to be kidding!!).... Anyway, Would be nice if they had the resources to make everything play nice together, but it's a matter of them using the tools they are most familiar with and not having the cycles to do everything. Doesn't mean I don't continue to put in my voice about problems, because a lilo boot of my kernel happens in 1/2-1/3 the time of a standard suse boot from grub. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org