> If /proc/config.gz exists when you boot from that image you could >> compare that to the .config file that you're using to see what the >> differences are. >> >> > I tried it. I spend much time on it.
For me the only way is to use a GUI diff program like Meld, otherwise i find it too difficult to notice the differences. :) > I also tried to use the config of the allround boot disks (in > /proc/config.gz of the running livecd system). I tried to figure out > differences and also tried to copy it to the Xen-Kernel and then started > 'make menuconfig' for the Xen kernel to fix dependencies cleared in 'make > menuconfig'. It leads to kernels that > * cannot be build due to compile errors, > * or kernels that run perfectly on G3 (generation 3 HP hardware) but not on > G4 or G6. > > Maybe this is an driver version issue for the 'Compaq SMART2 support' > and the 'Compaq Smart Array 5xxx support'. > But fixing a kernel, delivered by portage, is completly new to me. So i > tried to ship around this... > > Would you suggest to try this way? Should I try to fix the Xen-Kernel from > Gentoo with some HP driver source code? Or could it be a completly other > issue? > > I'd be very confident that the driver code will be identical in xen kernel to regular kernels of the same version. You could verify this by running md5sum against the modules source codes. If they are the same there's no need to worry about the driver code. Put your xen .config and the config from the boot disk that works up somewhere public - maybe we can spot the problem?
