build setting error [finally fixed]

idella4 · Last edited by idella4 on Fri Aug 13, 2010 2:06 pm; edited 1 time in total

This should be a fairly simple one line answer to clean this up.
I'm rebuilding a kernel and on boot it puuls up with

can only load kernel built for generic loader or linux image.

Just don't know what a generic loader is, where it comes from or how to appease it.

NeddySeagoon · Posted: Wed Aug 11, 2010 8:04 pm Post subject:

idella4,

Do a binary search on the config file to locate the issue.
First remove the .config and see if make menuconfig runs.
If so, throw away the defualt .config, if you saved it and copy the original config back to the tree.
Edit the .config file directly and throw away the last half.

If menuconfig fails, the problem is in the remaining half, if it works, the problem in in the half you threw away.
Now try with half of the half with the error ...
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

idella4 · Posted: Thu Aug 12, 2010 12:57 am Post subject:

Neddy,
woa, that's the most interesting tip I have from you yet. I tried it a few times but couldn't follow.
By binary it take it you mean testing a half, the halving that half repeatedly.
Since sending you the IM, I've found more confounding info on this kernel.
It's intended to be a xem kernel. It's almost definitely a xensource origin kernel, or at least compatible to them.
The boot error aside, consider this.
On copying a gentoo xen kernel 2.6.31 config into the kernel's .config, I run menuconfig, or oldconfig.
Before doing so, the xen content of the kernel config gives this.

NeddySeagoon · Posted: Thu Aug 12, 2010 7:26 pm Post subject:

idella4,

Thats exactly what a binary search is. Consider searching for a name in a phone book, or a word in a dictionary.
Open the book in the middle. Work out which half your name/word is in. Look half way into the correct half ... and so on.

Its a very efficient search as a list of 2^n items needs only n tests.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

idella4 · Posted: Fri Aug 13, 2010 9:29 am Post subject:

Neddy,
thanks I'm with you there. I still appreciate your efforts. I recognize your method from a lecture in beginner programing way back in 2000 or so, Other than you now this thread had gone cold, and I've been in touch with pappy. In summary, the initial block I described for this is resolved. I will remember your tip, but that aside, I think the block was due to this xensource kernel having a dependency on PAE, which is one of those terms I see and wonder what's that all about. The block, as I suspected, required one setting to be set and it
1 - opened up the other required xen content that is xen,
2 - cured the cited block or wrror re the generic loader, wherever that is.

The problem now is twofold
1 - pappy declares me the xen expert and doesn't know
2 - the kernel loading issue has changed to a completely different block.

Now, as I pointed out to pappy, I have 3 gentoo xen kernels and 1 xensource kernel copied a couple of time, a real glut.
The 3 gentoo ones, all work in in gentoo64. In gentoo32, 2 work. The xensource one I have used for making xen guest kernels.
The current requirement is to finally get the xensource kernel to build a xen host kernel.
Having finally found the PAE setting [select 64 G in high mem in processor settings] to make active the xensource kernel components, I have yet to get there, this is despite using make copying a known good config from the closely related effective cousin kernels use make oldconfig and also make defconfig. I'm still trying, but I am currently quite stuck.
I don't want to make a new thread. In your style, you will return to this and view my reply to your last.
I think a new thread isn't worth it, let's just rely on you and stay with this one.

The current issue is the loading of the kernel image. Despite several attempts as above, my configs keep bringing up an unfamiliar error saying the prepared kernel image for dom0 doesn't have enough space to load. It cites a memory address. I've tried taking the cited memory address space and inserting it in the kernel config. which is only because I don't know what I'm doing.
Suffice to say, it was just 1 of several attempts that came to leading to an alternate error.
So, in all this is more of that steep learning curve.
I shall post now, edit later and more clearly cite this error and keep trying. You would think that I could take the gentoo good 2.6.31 config and use it as a base to build a good config in the selected kerne;, but it keeps getting derailed.
Rather than calling on your method to track it down from cold, I'm fairly confident the settings that require correct entries are narrowed down to

idella4 · Posted: Fri Aug 13, 2010 10:24 am Post subject:

Neddy,
thanks I'm with you there. I still appreciate your efforts. I recognize your method from a lecture in beginner programing way back in 2000 or so, Other than you now this thread had gone cold, and I've been in touch with pappy. In summary, the initial block I described for this is resolved. I will remember your tip, but that aside, I think the block was due to this xensource kernel having a dependency on PAE, which is one of those terms I see and wonder what's that all about. The block, as I suspected, required one setting to be set and it
1 - opened up the other required xen content that is xen,
2 - cured the cited block or error re the generic loader, wherever that is with my find.