[SOLVED] initrd/vmlinuz issues: Losing my mind...

[MultimediaMan]

(2013-06-08 20:29)robinsmidsrod Wrote:  Why would that matter, once the kernel and initrd is loaded, they are in memory, and the initrd behaves like a mounted filesystem. I can't imagine that anything in your kernel would actually care what your kernel or initrd is actually named, it only cares about the kernel cmdline you've specified.

You are absolutely sure that you don't have bad hardware?

Have you actually tried with a shorter path, and does that make any difference?

Haven't tried the shorter path yet; the behaviour is the same with a virtual server or a physical. I'm pretty sure it is the path length/ depth. I've pretty much ruled out iPXE... my thought is when the kernel goes looking for the path in the image arguments, it seems to lose it's way. I've put the ask out to find out of there are any limitations. I'll shorten the path and see how things go. But I wanted to couch this with the forum beforehand.