Posts made by AsGF2MX

@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.

@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.

MMCEnabledConfig.32

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.

@Tom-Elliott I gave it a shot and no dice. Something is amiss and I keep comparing the Clonezilla boot process and that of FOG. The only thing I do notice is that the boot process of FOG is a whole lot quicker than that of FOG and also the /proc/iomem from clonezilla is a lot longer.

I am wondering if we need to patch the initxz with a /lib/modules/modules.builtin to make this work as I don’t see modules loading and am not sure how to detect if a module compiled in is actually getting used or not.

@Uncle-Frank Not all of them but the SD and eMMC controllers are on die so being unable to address them correctly could explain why it doesn’t show. I would think that at least mmc0 would show in FOG but it doesn’t - there is no dev node for the micro sd card - the SD card shown as SDA1 is actually a USB SD card reader.

http://cdn.arstechnica.net/wp-content/uploads/2013/09/Screen-Shot-2013-09-13-at-6.32.07-PM-640x423.jpg

Thoughts?

@Uncle-Frank @Tom-Elliott the output of fdisk -l /dev/mmc* or lsblk with the same returns no such file or directory. This is even with the newest kernel.

Since we don’t even see the MMC device, I’ve been going through a few things over the weekend and I might have found something. The eMMC device is operating in ACPI mode per windows and also per Clonezilla. The HS200 device sits at ACPI\80860f41:0001 Comparing the dmesg outputs between clonezilla and fog, I don’t see the above address anywhere in the FOG dmesg output.

After a little poking around for Kernel issues with Baytrail, it turns out there is an extra kernel option needed to make Baytrail work in a sane manner: CONFIG_PINCTRL_BAYTRAIL=“y”

When I looked at the kernel options with your name in git, the above is not configured or even defined. Would you be able to set the above to “y” and recompile the 32-bit kernel once more please? If it is already there then something is a miss.

This seems to very specific to Baytrail which the Venue is using. I do not have any info on Cherrytrail. If this works then the patch sets applied earlier should also take out the rpmb issue so it should theoretically be the one kernel that just works!

References:
https://lists.debian.org/debian-kernel/2015/09/msg00023.html
https://bbs.archlinux.org/viewtopic.php?id=193180
https://embedded.communities.intel.com/thread/7507

@Tom-Elliott It says 4.2.0 i686

@Uncle-Frank Perhaps it’s not such a big issue after all:

• My understanding is the RPMB partition is effectively doing what regular desktops do with EEPROM chips - store OEM license keys
• AFAIK Windows does not treat this partition as mountable - it doesn’t show in disk manager (the tablet is out of battery at the moment - will post a pic in a bit)
• Theoretically if I could clone p1-p5 as listed above then I should be all set
• The license or OEM data in the rpmb can remain as is across each unit

So in theory, if we apply Nell’s patch to ignore the rpmb area, we should be able to make this work.

The question is what needs to be done to the initd to get it to work?

@Tom-Elliott

@Wayne-Workman

Hopefully this one cuts it. First up, clonezilla:

FOG:

The 8GB device is the SD card I’m using to boot clonezilla.

@Wayne-Workman

Are you referring to init scripts within the initrd or something else? Since there are no modules here I am not sure how to even get the mmc recognized in dmesg.

@Wayne-Workman

That did help me to get an active partition but it seems Ubuntu is a non-starter as I couldn’t even boot it. I was then able to just unzip the ISO contents of Clonezilla alternate stable (current off site) and boot.

It is on kernel 3.16.0-4-amd64 and there is an MMC block device shown.

There is indeed and mmcblk0 being shown in clonezilla but I can’t get the 4.2 kernels from yesterday to do the same. I tried to find the header file for the kernel build options but I couldn’t find it from the sourceforge portal.

How can I help troubleshoot this further?

@Uncle-Frank Did not spot the missing C - I thought it was MMC CONFIG. I was searching for mmc in dmesg and that’s all it showed. Searched for blk as well and got nothing. Do you know what kernel generated that particular output? I don’t have any custom settings in my FOG setup except that I am forcing the boot of the 32-bit kernel and not the 64-bit one via the UI so I have to ask if any specific switches or anything is needed anywhere? As usual, I have secure boot disabled as well.

On the ISOs, I did find the some info but I couldn’t make sense of where to put those lines in within the UI. On the other hand I did grab an SD card reader and I have a clean SD card so I will try to make a bootable drive or two in a few hours and hopefully get something back.

@Tom-Elliott I am on the latest git and Kernel 4.2.0 right now and it’s still showing the odd /dev/ram0-15. I ran through dmesg and I see the following points of interest:

multiple occureneces of Not using MMCONFIG

Then:

ACPI PNP0A08:00: _OSC: OSC failed (AE_ERROR); disabling ASPM
ACPI PNP0A08:00 fail to add MMCONFIG information, can’t access extended PCI configuration space under this bridge.

There is a Winbond W83L51xD SD/MMC card interface driver showing a bit further down but that looks like the MicroSD card on the side.

Sidebar - if I want to boot an ISO via iPXE, how would I do so? I’m currently at home and I just realized I haven’t got a single USB drive on me. I do however have ISOs on my ESXi box and also I got FOG. Not trying to go off topic but trying to see if Ubuntu iso or even clonezilla will identify the storage device.

I just updated the kernel in place and it seems that just like 4.1.6 kernel that the fdisk -l produces 15 devices named /dev/ram0 to dev/ram15 at 124MiB each.

I am going to run the install script just in case there are some other changes involved.

@Tom-Elliott Are you meaning to say that I should do a git pull first to get the new kernels? If so, I do have a test FOG environment and will do so on that. Just in case I need to break something :).

Please advise.

I am on SVN 4543. When you say debug upload, do you mean to use the CLI and see what dmesg shows?

If yes, using debug mode, I’m not seeing anything that starts with /sdX or /hdX or /mmcX I don’t see anything “Samsung” or “mmc” in dmesg as I understand the eMMC is from them.

I’ve been a long time user of FOG and although I got EFI and etc to work nicely, I have now run into a bit of a brick wall on imaging devices with eMMC instead of SSD.

I just received a lot of Venue 8 Pros and I cannot get FOG to recognize the storage in them because it uses eMMC. I am using kernel 4.1.6 from TomElliot and the Venue 8 Pro can PXE boot just fine up to the point where you try to get it to image and it will say no disk found OR run diagnostics and it says there is no disk.

Running diagnostics, I see a lot of /dev/ram0-14 but don’t see anything starting with mmc. Is there some modification needed to the kernel itself or to initrd or similar?

Unfortunately in this instance, I have no handle on the purchase or choice of this particular set of devices.