[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [K12OSN] Trouble with PXE Boot; Fedora 17

Hash: SHA1

On Jan 29, 2013, at 6:57 PM, Adrin Gharakhani wrote:

> Thank you Gianluca,
> I followed your instructions (similar to the instructions on the fedora site), and I was initially unable to read the initrd.img file. After a long set of experiments I finally found out that the read permissions were not set properly for the default initrd.img. So, heads up to others who might encounter a similar problem: change the read permission to allow all to read.
> So, finally, I passed the "golden gate", but now I have a hardware incompatibility problem. I don't know if I should continue this thread or create a new one. I'll continue, for now:
> I'm getting a message that my zero client is unable to boot because "This kernel requires an x86-64 CPU, but only detected an i686 CPU"
> My workstation is x86-64 and apparently the new zero client that I bought is i686. Any suggestions how to go about correcting this problem? (does fedora 17 provide i686 compatibility?)
> I have to add that my sole interest is to move my workstation to another building (on the same LAN), but I want my zero client set up such that I'm "in front of the workstation", with _full_ access to all capabilities of the x86-64 kernel (there is only myself; this is not a multi-client environment)
> Thanks all for your help and suggestions

You built a 64 bit environment for the clients too, which is almost never what you want to do. Make sure you set the chroot to 32 bit when you start building your clients.

Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]