@Beber55 Looking at your screenshot and the wording, the reason for the RJ45 needing to be plugged is that you’ve got it set to DHCP instead of static IP.
For static IP, follow this guide: https://askubuntu.com/questions/766131/set-static-ip-ubuntu
The other option is, if Virtual Box supports it, set the interface as NAT’d so that you get another DHCP locally on your PC. I’ve not used Virtual Box in ages so I can’t confirm this.
@Uncle-Frank Had to disappear for a bit as I got buried for a bit but hopefully I’m not empty handed and I’ve got something.
@Tom-Elliott I took the make file from the SVN and went through a few compiles - started fat - with a lot of suspected options ticked and eventually one set worked.
A little bit of reading on eMMC interfaces and after going through a few posts in various places, I then took a different approach - add a few items and compile then recompile and retry. When I enabled a few extra options more towards the I2C and SPI interfaces, I ended up with one set that worked and my makefile is attached. There is an SPI and I2C bus involved but it took some digging to find the connection and unfortunately I didn’t bookmark the page before my browser crashed out.
I did try to pull the image and although there were a few errors (I don’t have the patch sets applied) but I also do think part of it may have been because the partitions are in fact bitlockered - still trying to figure that part out.
This post wouldn’t be complete without the pictures and a request:
I am betting if you recompile with the above make and the patches you applied, at least @d4rk3 should be up and running and myself, I am trying to figure out if I can sysprep the unit for the purpose of testing so that fog can read the partitions but I will need a little while for that.
@Uncle-Frank That was a good call on the single-disk multiple partitions.
Need a few moments to recompile the kernel will test it out as well.
By the way, my kernel is not patched - straight off the kernel site, along with Tom’s 32 bit config file, only magic was the ones you pointed out and possibly the little modification to the partition functions.
@Wayne-Workman Adapter is Level 1 USB-0301 v4 http://global.level1.com/Network-Card/USB-0301/p-3285.htm which uses a Realtek chip. The v3 used the AXIS chip which Dell puts in its docks.
I’m using the 32-bit ipxe and bzImage32 as well.
@Tom-Elliott Your kernel worked flawlessly. Downloaded and uploaded perfectly and managed to check everything just before the battery hit 0%.
@Uncle-Frank It will be a little while before I can test the changes you requested.
@reub_rester Please take a look at this thread: https://forums.fogproject.org/topic/5732/dell-venue-8-pro-imaging-emmc and give it a shot.
@Tom-Elliott I can definitely hold on for a little bit. I am not sure if a diff is sufficient to identify what changed but it has to do with SPI and I2C options mostly. Not sure if there is some sort of cheat sheet with all kernel options and path in menuconfig but if not, it will have to be side by side compare. I took the base and added only the SPI and I2C options but I will need a bit to pick the options again and document what I had to change exactly.
@Wayne-Workman Fingers crossed we can see this through to completion and put Bay Trail on FOG’s compatibility list. Poking around the forums, I did see a request from @reub_rester (https://forums.fogproject.org/topic/5238/trying-to-image-a-dell-venue-pro-11-5130-x64) and his issue was the same as mine so this should help it get further along. The only thing is that in the device basic options, he will need to put in /dev/mmcblk0 and at least inventory will work.
@Uncle-Frank If need be, I will grab the dmesg output. Just let me know.
Also it seems I misread the error message on image pull. I stripped bitlocker from one of the units only to find it would throw the same error. So I think what is happening is a mount point issue.
I am not sure where the relevant code is or how complicated it would be to modify but it looks like what is happening is that the enumeration is not expecting two character suffixes.
Typical setup is: /dev/sdXY where x is usually a and Y could be anything from 1 to 5.
MMCBLK setup is /dev/mmcblkXpY and unlike the above, X is a number and so is Y.
However it looks like partition resize input is not being fed Y although the script before it is showing the path correctly. Function input variable size too small?
I am poking around to figure where this comes out of but if anyone has any pointers, I can have a look.
@Tom-Elliott Here you go. It is 32-bit as the 64 bit kernel doesn’t seem to working with the Venue, crashes out right after iPXE gets done. 32-bit has been good to me so far.
Point taken on the cheat sheet - hopefully this does the trick.
MMCMod-TomElliotConfig.32.patch
On another note on the init_32.xz - I tried to get rpmb to stay out by using udev rules but then I noticed you have got part of the rules there. Is there any way to stop the unit from rebooting and drop to a shell to see what last happened before it failed?
@Tom-Elliott The upload and download on my compiled kernel worked - not so much as a hint of something being wrong. Everything works! Currently testing the kernel that you just uploaded and promising so far on upload. I think the unit has just enough battery to go through a download before it shuts off.
One point of note I should mention (in case someone comes across this post while looking for Venues and PXE booting) is that I am using Level One’s USB-301 Fast Ethernet adapter. I have both the AXIS (died after the first post!) and Realtek variants but all screenshots I’ve posted in this thread are using the Realtek variant.
@Tom-Elliott 64-bit didn’t work for me at all before - I will retest the latest build once more and see if there is a difference. I am currently running FOG with both the bzImage and init set to point to the 32-bit variant in FOG Configuration. I will hold back one unit from this lot for “testing” purposes so if you need me to test anything to fine tune things, I can help.
Also @d4rk3 how did you get single disk - resizable to work? I am still seeing errors. With the little patch on the ramdisk I applied, I can get further but not to the point I can image.
My init_32.xz is dated Aug 31 12:01 what is the date on yours?
@Uncle-Frank I think the patches have made Tom’s build a bit smoother than mine without the patches. Less chatter in front when it loads up. However I can confirm without any patches it works as well. I’m happy to help test any variants if you wish.
@Uncle-Frank Apologies for going AWOL…cleaned up the deployment and held back one unit for testing purposes and took a brief break to recover.
The efi files and ipxe files are straight from the SVN with no modifications. I only took the stock isc dhcpd.conf file and modified the items right after max-lease time as below:
default-lease-time 21600;
max-lease-time 43200;
# option domain-name-servers x.x.x.x;
# option routers x.x.x.x;
class "UEFI-32-1" {
match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00006";
filename "i386-efi/ipxe.efi";
}
class "UEFI-32-2" {
match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00002";
filename "i386-efi/ipxe.efi";
}
class "UEFI-64-1" {
match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00007";
filename "ipxe.efi";
}
class "UEFI-64-2" {
match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00008";
filename "ipxe.efi";
}
class "UEFI-64-3" {
match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00009";
filename "ipxe.efi";
}
class "Legacy" {
match if substring(option vendor-class-identifier, 0, 20) = "PXEClient:Arch:00000";
filename "undionly.kkpxe";
}
} <<< This one is the wrapping brace for the subnet x.x.x. netmask .x.x.x.x { at the beginning
Host Kernel: 4.2 x32 Sept 17 straight from FOG no mods
Host Primary disk: /dev/mmcblk0
Image type: Multi partition single disk (only one that works for me so far as I can’t build my own image due to the vendor’s preload)
bzImage32 - SVN 4586
init_32.xz: SVN 4586
In my fog configuration options (this is on a test box):
So far I’m using 32-bit for the Venue 8 and also other hardware I have and it works for me - we use mostly Dell gear with a dash of Lenovo in the mix.
I actually didn’t have to use the has usb nic parameter for any unit. I used the USB-0301 as mentioned earlier and it didn’t complain on any of the units I had imaged with FOG.