@george1421 I downloaded a copy from the kernel directory on a different PC and copied it over. They were just called bzImage and bzImage32. I will get the version in the morning and report back.

I did run the test before I left and it did fail network. I also wasn’t able to see the mac address or IP through the menu.

EDIT:

Also, running Ubuntu 14-04 LTS
I get bzImage: x86 boot sector

And I got the bzImage from here https://fogproject.org/kernels/

EDIT 2: Not sure why the edit from my main post vanished. Let me put that here again.

I took a video of the newest message. From reading the blurry video, this is what I can read before the fog text logo comes up.

mmc0: Unknown controller version (3). You may experience problems.
usb 1-5: device descriptor read\64, error -71
EXT4-fs (read): couldn’t mount as ext3 due to feature incompatibles
Starting logging: OK
Populating /dev using udev: udev[2612]: error creating spell? fd: Function not implemented
done

EDIT 3: Took bzImage files and init files from a test fog machine I was messing with. 1.3.0 FOG on there. Copied the to the FOG 1.2.0 server.

The compatibility test comes back with disk and network passing.

Trying to register a host and I get:
Unable to register host: Invalid MAC Address (/bin/fog.man.reg)
Arg Passed:

I think I am making some progress here.

@x23piracy Nothing. I think Panasonic has some components wired internally to the board to look as USB.

All I have plugged in is a network cable.

On the newest bzImage/bzImage32, I thinks the xkci got resolved, I am still trying to grab what the message is being thrown before the FOG txtimage scrolls down.

Is there a way to pause or slow down the messages?

EDIT: Main post updated.

Notebook Spec

UEFI w/ CSM enabled. Secureboot Off
i5-6300U
NIC: Intel I219-LM

Staring off, I am running v1.2.0. Isolated network install.

Notebook SPEC
UEFI with CSM enabled. Secure boot off.
Intel Corre i5-6300U
Intel I219-LM

I am going to be getting a new batch of these notebooks and I am running into some issues.
The mk1 series worked fine. The mk2 is kinda screwy.
I am unable to inventory via PXE.

Leaving the bios as UEFI, I am not able to LAN boot.
Messing with having CSM on, no luck.

Moving on, I changed the BIOS to not use UEFI. I can get to the main FOG splash screen and select Full inventory.
The following is what I was able to capture before it scrolled on past everything to tell me it has an issue with inventory.

tsc: Fast TSC calibration failed.
usb 1-5: device descriptor read/64, error -71
xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 3.
usb 1-5: hub failed to enable device, error -22

From here I deiced to update the bzimage and bzimage32 kernels manually.

It seems to go further, but I still can’t inventory. I see a message rush past (shorter than the above), but I am unable to capture what it reads.

Anyone know of any issues with this notebook? Or am I ahead of the curve here?

Found some software on the master for making recovery discs. Sorry for not looking for this sooner, I’m looking over the mountain instead of at the base.

If these work, I may remake the image quickly on the second to have an image.
Still wondering what Panasonic has on these causing fog to think the File Table is corrupt.

Thank you Tom.

Also, almost relevant for how I feel:
Quote from Simpsons, Ned Flander’s Mother:
[QUOTE]You gotta help us, Doc. We’ve tried nothin’ and we’re all out of ideas.[/QUOTE]

Update: Finished downloading the image with OS as Other with no avail.
It has tried startup repair and failed.

Something with the file table how Panasonic has set up needs to stay the same from time of taking image to deployment.
I have noticed fog looking at the file table and stating that it looks corrupt but the primary looks intact so it will use that.

Almost sounds like it is taking what looks like a file table from the reinstallation recovery partition and trying to reconfigure how it should be.

Would a dd Image be a good idea?

All software and drivers were already installed, would I have to go back and redo everything upon factory recovery and going into audit mode?

Throwing this out there, I have done HP desktops with OEM keys without having to go into audit mode and they image fine. They didn’t have full on recovery partitions though, they gave DVDs, which is nice.)
This has to be something with how the partitions are set up on these Panasonic laptops.

I am not seeing a way to try a fresh install while keeping the OEM key working. (Looks like Panasonic does not offer install DVDs for this model I have)

It would be nice if Panasonic gave installation DVDs.
I am missing the days when OEMs did this by default.

I was trying to figure out if there is a way to force fog to not check if the file table is correct upon deployment.

Reason I am looking into this is further testing from this original post: [url]http://fogproject.org/forum/threads/image-with-oem-recovery-partition.9920/[/url]

This is basically a fresh Windows 7 SP1 x64 install. Besides the point where I work off of what what on the machine from factory (recovery partitions).
I am trying to stay away from doing a fresh install as we want to keep the key that came installed and not use up the few we have left.
-The OEM preinstalled a OEM key that only works with their installation partitions. Also, the slapped the Windows 8 sticker on it not giving a windows 7 key sticker.

If we do use Windows Backup and Recovery, everything works fine. I would love to use fog on this to keep an images not stored on random externals.

So far I have tried the following:
-Multi-Part, Single Disk
-Multi-Part, Multi-Disk
-OS as Windows 7
-OS as Other (Currently downloading to second PC to see what happens*)

Any ideas?

*Reason for posting: I noticed fog check and notify me that the table looks corrupt. before restoring the partitions)

sda2 has * boot marked.
sda2 is the 300mb part.

Stopped mid way.

Cannot read file d1p3.img.001

Going to try again with a backup of the first attempt ever tried.